How is this different to the 'Official' Build?
From October 17th onwards, the Official builds had merged N9 sources which has ridden users the chance of flashing custom kernels due to the new N9 dependency. These builds aim to backtrack that, reverting to S9(+)'s Oreo Vendor, to gain custom kernel support again. Also, the firmware source used in the 'Official' builds have become fairly antique, so it was time for a refresh and use the latest and final Oreo source (BSB1) Samsung had to give, and an upstreamed kernel of latest (almost always) ELS thanks to @Eamo5's Endurance Kernel being baked into the builds.
Aside from these factors and a few more listed below, this is the LineageOS you know and love. Although LineageOS' nightly-build system is great, there is only so much change that can happen over a night. You can expect these builds updating to cover latest Security Patch a.k.a Monthly Builds, but maybe more if a great change is required.
Simple motive: Have a solid daily driver before the Pie Tree sources are dropped.
Screenshots
If you are on the App they may instead be at the bottom of the post
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What's working:
As this build is based on the 'Official' LineageOS build, it complies with the device support requirements, which means including but not limited to these hardwares will work:
Wi-Fi
Bluetooth
Mobile Network (Calling, Data, etc.)
Audio
USB
GPS
NFC
Camera
Fingerprint Sensor - Noticeable speed improvement reverting to an S9(+) Vendor.
Software:
The build has overridden auto-generated fingerprint keys, with an official, whitelisted fingerprint from Samsung, which can also be found in MagiskHideProps. This ensures SafetyNet passes without the need for extra flashing - refer to above screenshot also.
F2FS Support - Instructions to switch from default ext4 to f2fs
Miscellaneous - Overlays:
- Dialer - Call recording enabled. If your country is not blacklisted (for legality reasons) you should see a 'Record' button during your call.
- Trebuchet - Notification Badges
- Files - File Operation Dialog Box, Default Show Internal Storage
- Settings - Default Enable Autobrightness for Night Time flashers; Default Disable Bluetooth and LED
- SystemUI - Button to Expand Notifications; Notifications fade on dismiss
- Snap: api v2 enabled for better quality pictures and remove green artefacts & flashing.
What's not working:
Samsung's own features such as Samsung Pay, KNOX, Theme Center, Game Launcher, etc. won't be ported to LineageOS. They may have their own implementation to similar functions, though.
Iris sensor does not work because AOSP upstream does not support that yet.
IMS services (VoLTE, VoWiFi, etc). Samsung has their own proprietary implementation. It is not really possible to easily port.
Encryption Support as of now, exploring for a workaround (if there is one).
Bugs:
Lock screen shortcut - Camera: Screen flashes white, and then Camera force closes using shortcut.
Work around: Install another app using Camera action (e.g. SnapChat) and set stock Camera to default for shortcut.
Instructions:
Make sure TWRP has been installed and is functional.
Download the latest build, Vendor and optionally GApps - Links found under the header below.
Reboot to Recovery
Wipe data and cache (required if you are not currently using LOS and are coming from OneUI or SamExp.)
Install Vendor image to Vendor partition.
Flash the latest build (and GApps if you downloaded it)
If you are on and beyond April Patch (OneUI), do not flash a found Oreo Firmware as you will lose Baseband (Sim, Network, RIL). There is also no need to change firmware.
Reboot to System.
If a new build is released, to update:
Downloading and flashing a later build, will automatically replace (wipe & install) the /system partiton and retain your compatible User /data partition and firewall due to LineageOS' addon.d supprort.
You also do not need to flash GApps again, as they too have addon.d support, backing up which GApps you have installed and holding them until after the /system partition wipe has been done.
Same applies to Magisk Root due to (you guessed it) addon.d support too. It holds your currently installed Modules until after the /system partition wipe has been done.
Therefore, due to these addon.d files surviving because of the way LineageOS.zip manipulates the wipe to the /system partition there is no need to wipe partitions manually. Just leave it to the lone flash.
However, do remove any system modified theme overlays (substratum) to ensure no loop on boot, which may then result needing to wipe.
Downloads:
Vendor: Included to the respective Device drives below
Samsung Galaxy S9 (G960F): https://drive.google.com/drive/folders/131WWohHbpeZroYaHISBPpPnhDKYA6kj2
Samsung Galaxy S9+ (G965F): https://drive.google.com/drive/folders/1cr-ivOdTj8lo3p9kYjGcxT1AvgFYy3M9
OpenGApps (Optional): https://opengapps.org/
Contact:
Telegram Group - Handle @invisibazinga2 a.k.a Lil' G-Raf
Contributors:
Big thanks to: @jesec ; @Synt4x.93 ; @Ivan_Meler ; @Eamo5 ; please check GitHub commit history for anybody that I may have missed out, you have all been great!
ROM Information
LineageOS Source: https://github.com/LineageOS
Android Security Patch: May
Android Version: 8.1.0
Kernel Version: ELS - 4.9.xx - Endurance Kernel - Version subjected to change with ELS updates.
Device Source: https://github.com/AzzyC
Thanks for the rom! What would be the best way of installing gcam here? I've tried installing the apk on the official build but the quality wasn't too nice. Tried to flash the libs as well and got a bootloop. Thanks for your work!!
enetzlsg said:
Thanks for the rom! What would be the best way of installing gcam here? I've tried installing the apk on the official build but the quality wasn't too nice. Tried to flash the libs as well and got a bootloop. Thanks for your work!!
Click to expand...
Click to collapse
Hey man! Yeh on the official build as the vendor was N9 based, our modded S9(+) libs wouldn't be compatible. Fortunately, just before writing this reply, I flashed the lib for my device (S9) and then installed GCam and it got going nicely! There is a 4.1_fix.apk (fixed for OneUI lib) and just a regular 4.1.apk (built on Oreo lib).
Let me know how it goes man! And appreciate your compliments ?
the screenshots look like pie roms... clock is on left side ..i thought finally a good lineage 16 build.. yet thanks for the 15.1 build though.. ??
i came from soldier rom pie and after installing the rom according to the instruction.
full wipe, vendor image than rom and gapps and lastly the firmware.
everything boots and works but the phone doesnt detect my sim card nor the latest wifi network i was connected too. it does sees my neighbors wifi, for some reason it doesnt detect mine. i tried to change the baseband for fixing the sim card problem but no luck.
please help me/ im on s9 g960f
kmo1997 said:
i came from soldier rom pie and after installing the rom according to the instruction.
full wipe, vendor image than rom and gapps and lastly the firmware.
everything boots and works but the phone doesnt detect my sim card nor the latest wifi network i was connected too. it does sees my neighbors wifi, for some reason it doesnt detect mine. i tried to change the baseband for fixing the sim card problem but no luck.
please help me/ im on s9 g960f
Click to expand...
Click to collapse
It seems as though you were on and beyond the OneUI April Patch, which in the description of the Firmware zip it clearly indicates a warning to not flash the zip. I can't say anymore than these warnings unfortunately, after that it is up to the User.
A common fix that people do, to get back to normal state, is flash the latest DevBase with all of its complementary files. The April Patch had introduced a version change from U2 to U3 which makes downgrading impossible, without side effects. Please heed to warnings more in the future. Thanks
AzzyC said:
It seems as though you were on and beyond the OneUI April Patch, which in the description of the Firmware zip it clearly indicates a warning to not flash the zip. I can't say anymore than these warnings unfortunately, after that it is up to the User.
A common fix that people do, to get back to normal state, is flash the latest DevBase with all of its complementary files. The April Patch had introduced a version change from U2 to U3 which makes downgrading impossible, without side effects. Please heed to warnings more in the future. Thanks
Click to expand...
Click to collapse
thank you and sorry. i installed back to soldier rom with his firmware and everything works fine. but i really want to try your rom, so what firmware should i install with it?
kmo1997 said:
thank you and sorry. i installed back to soldier rom with his firmware and everything works fine. but i really want to try your rom, so what firmware should i install with it?
Click to expand...
Click to collapse
Glad you're back to normal state!
Users has been able to boot and use the ROM just by installing the provided Vendor image and remaining on the same firmware. Let me know how it goes and if I can recommend other users to do the same, if they are in a similar situation. Thanks
AzzyC said:
Glad you're back to normal state!
If I remember correctly a User has been able to boot and use the ROM just by installing the provided Vendor image and remaining on the same firmware. Let me know how it goes and if I can recommend other users to do the same, if they are in a similar situation. Thanks and hope it works out!
Click to expand...
Click to collapse
yep, works like magic. thank you very much!
AzzyC said:
Hey man! Yeh on the official build as the vendor was N9 based our modded S9(+) libs wouldn't be compatible. Fortunately, just before writing this reply, I flashed the lib for my device (S9) and then installed GCam and it got going nicely! There is a 4.1_fix.apk (fixed for OneUI lib) and just a regular 4.1.apk (built on Oreo lib).
Let me know how it goes man! And appreciate your compliments ?
Click to expand...
Click to collapse
one ui lib didn't work out for me
I always noticed that oreo roms were laggy. I heard somewhere that it was a HWC bug, NOT that HWC was disabled. So... my question... does this unofficial version of lineageos lags like the other oreo roms?
Muntasir Mahmud Saif said:
one ui lib didn't work out for me
Click to expand...
Click to collapse
You tried a OneUI vendor lib, on an Oreo Vendor? Read the post again.
LavaSnake54 said:
I always noticed that oreo roms were laggy. I heard somewhere that it was a HWC bug, NOT that HWC was disabled. So... my question... does this unofficial version of lineageos lags like the other oreo roms?
Click to expand...
Click to collapse
Can assure there is no lag here, but you can find out by trying of course aha! The kernel definitely smoothens out the whole experience and with decent battery (see sceenshot for example result) and HWC is active.
AzzyC said:
Can assure there is no lag here, but you can find out by trying of course aha! The kernel definitely smoothens out the whole experience and with decent battery (see sceenshot for example result) and HWC is active.
Click to expand...
Click to collapse
Looks like a solid daily driver for me. Will definitely try it soon.
AzzyC said:
You tried a OneUI vendor lib, on an Oreo Vendor? Read the post again.
Can assure there is no lag here, but you can find out by trying of course aha! The kernel definitely smoothens out the whole experience and with decent battery (see sceenshot for example result) and HWC is active.
Click to expand...
Click to collapse
one ui lib bro..i am using that lib on my one ui currently for quite a few months..
Muntasir Mahmud Saif said:
one ui lib bro..i am using that lib on my one ui currently for quite a few months..
Click to expand...
Click to collapse
I don't see what is not to grasp here, you are flashing a Pie vendor lib on an Oreo Vendor. How would that work out? Didn't think I'd have to spell it out, but you've spammed this issue across 3 posts now:
Use the Oreo modded lib (not the Pie/OneUI lib), as this ROM is based on an Oreo Vendor, and the 4.1.apk (not the 4.1_fix.apk).
Hey guys!
I was doing a test run for a particular change and I thought I'd do a quick update for both devices. Starlte built just fine but I ran out of disk space when finishing star2lte so the compile failed (at 91% ?)
Not to fret, the May Security Patch has not yet been merged into LineageOS so this would have been just another build on April Patch. However, the included kernel has updated to latest of Endurance, though you can just flash Eamon's latest kernel zip to update and have the same effect.
Both devices will of course get an update when May Patch is out. Gracias bien
For starlte:
https://drive.google.com/drive/mobile/folders/131WWohHbpeZroYaHISBPpPnhDKYA6kj2
Gcam link please?
AzzyC said:
I don't see what is not to grasp here, you are flashing a Pie vendor lib on an Oreo Vendor. How would that work out? Didn't think I'd have to spell it out, but you've spammed this issue across 3 posts now:
Use the Oreo modded lib (not the Pie/OneUI lib), as this ROM is based on an Oreo Vendor, and the 4.1.apk (not the 4.1_fix.apk).
Click to expand...
Click to collapse
sorry if i did wrong or hurt your feelings but can you please provide those two files?
LavaSnake54 said:
Gcam link?
Click to expand...
Click to collapse
Muntasir Mahmud Saif said:
can you please provide those two files?
Click to expand...
Click to collapse
https://f.celsoazevedo.com/file/gcamera/GCam_5.1.018.177470874.41362666_IDan_N6_4.1.apk
AzzyC said:
https://f.celsoazevedo.com/file/gcamera/GCam_5.1.018.177470874.41362666_IDan_N6_4.1.apk
Click to expand...
Click to collapse
you are dope bro .thanks
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look, build, and use our code at CarbonROM's GitHub... and at CarbonROM Gerrit.
Disclaimer:
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash!
Support:
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Join our Discord server! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
We recommend MindTheGApps. OpenGApps should work, but please make sure you clearly mention the gapps you're using when reporting bugs.
Notice:
For this ROM to work you need to use the latest ODM Images. If you need additional guidance on how to do that, please refer to Sonys Guide on how to flash an ODM Image.
Get CarbonROM
Changelog
Join the CarbonROM Discord server
GitHub
Gerrit
Kernel source
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
XDA:DevDB Information
CarbonROM, ROM for the Sony Xperia XZ
Contributors
Myself5, CarbonROM
Source Code: https://github.com/CarbonROM
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Nightly
Created 2018-03-31
Last Updated 2018-07-19
No one tried this rom yet? I have a problem over here. It keeps asking for password after the CarbonROM logo even though I wipe everything clear, any ideas? What I was doing was flash 41.3.A.2.99 with everything wiped, flash ODM, flash TWRP, flash the rom and then Pico OpenGapps. Something wrong with my procedure? Thanks in advance.
EDIT1 : Oh yeah, forgot to mention my device is F8332, it isn't supported?
LuthfiKun said:
No one tried this rom yet? I have a problem over here. It keeps asking for password after the CarbonROM logo even though I wipe everything clear, any ideas? What I was doing was flash 41.3.A.2.99 with everything wiped, flash ODM, flash TWRP, flash the rom and then Pico OpenGapps. Something wrong with my procedure? Thanks in advance.
EDIT1 : Oh yeah, forgot to mention my device is F8332, it isn't supported?
Click to expand...
Click to collapse
Use the "format data" option in TWRP to get rid of encryption, wipe doesn't clear encryption. If coming from stock, thats necessary unfortunately due to differences in the encryption used. Otherwise (if coming from AOSP) the password its asking for would be the one you used before.
Dual sim support?
Myself5 said:
Use the "format data" option in TWRP to get rid of encryption, wipe doesn't clear encryption. If coming from stock, thats necessary unfortunately due to differences in the encryption used. Otherwise (if coming from AOSP) the password its asking for would be the one you used before.
Click to expand...
Click to collapse
Alright format it is.
agentsandy007 said:
Dual sim support?
Click to expand...
Click to collapse
No it isn't. At least out of the box. You can find a patch on Sony AOSP Build thread.
Volte Supported??
First of all, thanks alot @Myself5 and all other devs, who are working hard to bring this to our XZ :good:
My experiences after 1 day:
- rom is very smooth and snappy.
- root via Magisk v16 & Xposed 90.1-beta3 (systemless) works flawlessly
- the fp sensor always works, but it's not as sensitive as with stock
- night light worked - until I've installed Substratum and a Substratum theme, but after that it doesn't work anymore (even after deactivating, uninstalling the theme, a system restart and deinstalling the Substratum app it sill doesn't work). Also a dirty flash of the rom.zip didn't help to get it working again.
- the build-in camera takes acceptable pics (not as well as the stock camera, but acceptable); also focussing is a little slower than stock. Another thing is, it's not possible to chance the location to save the pics to the ext. sdcard.
- formatted as a portable storage, the ext. sdcard item on the left of the status bar can't be removed (see attachement)
- the battery consumption is a bit high (from 100 % to 98 % in 1 h - without doing anything)
But in the whole, it's really promising for th 1st official build :good::good::good:
Klaus N. said:
First of all, thanks alot @Myself5 and all other devs, who are working hard to bring this to our XZ :good:
My experiences after 1 day:
- rom is very smooth and snappy.
- root via Magisk v16 & Xposed 90.1-beta3 (systemless) works flawlessly
- the fp sensor always works, but it's not as sensitive as with stock
- night light worked - until I've installed Substratum and a Substratum theme, but after that it doesn't work anymore (even after deactivating, uninstalling the theme, a system restart and deinstalling the Substratum app it sill doesn't work). Also a dirty flash of the rom.zip didn't help to get it working again.
- the build-in camera takes acceptable pics (not as well as the stock camera, but acceptable); also focussing is a little slower than stock. Another thing is, it's not possible to chance the location to save the pics to the ext. sdcard.
- formatted as a portable storage, the ext. sdcard item on the left of the status bar can't be removed (see attachement)
- the battery consumption is a bit high (from 100 % to 98 % in 1 h - without doing anything)
But in the whole, it's really promising for th 1st official build :good::good::good:
Click to expand...
Click to collapse
Hello, is the battery life when used good ? As good as stock ?
And does it have that bug when if you record video the result will be green ?
Can you upload screen recording of rom from home to settings and other functions.
I plan on flashing this soon, but I figured I'd tell you, your link to the Carbon FAQ is broken.
ilininja said:
Hello, is the battery life when used good ? As good as stock ?
And does it have that bug when if you record video the result will be green ?
Click to expand...
Click to collapse
The battery consumption while in use is ok. But my device doesn't go into deepsleep while the screen is off. So I had lost about 23 % in 10 hrs - leaving the device untouched!
Video recording works; I haven't noticed that bug.
Saroj11488 said:
Can you upload screen recording of rom from home to settings and other functions.
Click to expand...
Click to collapse
Sorry, I went back to stock for now, as there's a new stock fw (41.3.A.2.107).
I have a few bugs to report. First, the fingerprint sensor is extremely slow, about half or even one third of the speed compared to stock. Second, could you guys please fix the deepsleep? That one is not working for now. And third, Night Light does not work at all...
Thank you for updating the XZ to Android 8.1 I am glad to see carbon rom on this device although it is not that stable for now.
Really nice ROM and I'm looking forward to make this my daily driver, I tried it for two days and these are the bugs I found:
1: GPU performance is really bad with 2d games and google maps lagging all the time when they never do on stock
2: CPU performance is inferior compared to stock, especially single threaded
3: enabling 120 hz display won't do anything and the settings or UI will crash when leaving the page
4: fingerprint seems to be sometimes less responsive, usable but can be improved
Camera is not so bad and the modded google camera works well, hopefully this will become the first proper AOSP based platform for this device that has only seen failures until now, keep up the good work.
Can I dirty flash this rom for just update?
I use Carbon Rom 3/31 version, but I can't use delta update because my device cannot receive the stock script.
I must change the rom script with Notepad+.
So...can I use dirty flash or....could you manage it?
Thanks for continously updating this rom and thank you for fixing the bug with the fingerprint sensor.
I'm not sure if deepsleep has been fixed but there is a big problem with playing music. I can't even play any music track at all...
Hello, looking forward to make this my daily driver, is it possible ?
What I would want is decent battery life and camera.
Hello. I tried to listen to music after installing the ROM, but the earphones are disconnected as soon as they are connected to the smartphone.
The earbuds pfe 132 and are made up of earphones with an iphone microphone.
L'ily said:
Clean flashed the 10th build along with Rytekk's dual-SIM patch, Pico Open GApps and Magisk 16.3 to my F8332 and other than that annoying SD notification (which can be banished to the notification drawer by making System UI notifications low priority) and Night Light not working, the only other major issue raised ITT of the CPUs not entering Deep Sleep is fixed according to Adiutor.
Great stuff. I haven't been able to standardise on one ROM since the CM days (interesting side note, it looks like you built the kernel for the NOCT build on my Z2 tablet).
I recommend this to anyone for daily use. Also, lower your expectations to realistic levels guise. I remember when XDA threads were for flagging major broken functionality, not complaining that a few amateur enthusiasts weren't putting out work that competed on every indicator against the finished product of a multibillion-dollar for-profit international conglomerate.
Sent from my Sony Xperia XZ using XDA Labs
Click to expand...
Click to collapse
Could you please give a link to that dual SIM patch?I have flashed this ROM on my F8332 successfully but none of my SIM cards works
Hello, with the 10th build I have a problem with the installation, it keeps telling me that Google services framework stopped.
Any help ?
(V11 vendor image odm, formated data)
BigMixman said:
Could you please give a link to that dual SIM patch?I have flashed this ROM on my F8332 successfully but none of my SIM cards works
Click to expand...
Click to collapse
Add these lines in build.prop, and reboot.
Code:
persist.multisim.config=dsds
persist.radio.multisim.config=dsds
ro.telephony.default_network=9,0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Moto Z2 Force
Code:
- Your warrenty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the official Lineage OS thread for the Motorola Moto Z2 Force, codename nash.
We support both the Sprint, International, and T-Mobile variants, as their bootloaders are unlockable, while we can 't support the Verizon and AT&T variants, as their bootloaders are permanently locked.
How to install:
Necessary Base Firmware: 8.0.0 (OCSX27.1.2, May 2018) (for TMO, or equivalent security patches for other variants)
Boot the newest TWRP .img from the Official TWRP Project Site.
In TWRP, click "Wipe", "Format Data", then type "yes" as prompted.
ADB sideload the newest weekly
(Optionally) You can flash the newest TWRP Installer also found at the Official TWRP Project Site if you wish to maintain TWRP, though the pre-installed Lineage Recovery instance will do everything you need it to in most cases. We don't recommend or support the use of the TWRP installer, as it is overwritten on every update (will need ot be re-installed every update), and has no addon.d-v2 persistence.
Click "Reboot, then choose "Recovery", this will boot you to either Lineage Recovery or TWRP depending on your choice to install TWRP or not. It is necessary to reboot between ROM flash and GApps/Addon flash due to verity/slot-swap logic.
(Optionally) Flash GApps - MindTheGApps arm64 are recommended, OpenGApps are compatible with A/B as of 09102018, but I still only reccoemend and support MindTheGApps.
(Optionally) Flash SU - you'll need to turn it on from in developer settings after first boot Lineage OS SU Addon. - Magisk works fine, though is not supported.
Reboot
Known Problems:
Audio Mods don't work (this includes headphone jacks on mods) -- We can't fix this, don't use custom ROM's if you care about these.
Official Lineage OS builds will not ever allow Moto's Battery Mod "Efficiency Mode" to work -- though these can be made to work unofficially, join our discord if you're interested in this feature.
Wi-Fi Calling won't work until either the International or T-Mobile variant gets 8.1 blobs.
Ultrasonic Proximity Sensor doesn't work -- likely won't ever. It is used my Motorola's Active Display, but by nothing in Lineage.
Compass doesn't work -- no clue why.
Stock Display Color Profiles (the ones in Settings, "Display", "Colors") -- The ones in Settings, "Display", "LiveDisplay" work.
The default LiveDisplay "Natural" setting in Settings, "Display", "LiveDisplay", will occasionally dispaly color corruption, to deal with this, just swap to the "SRGB" profile, and swap back to "Natural", or leave it on "SRGB if you don't mind, then you won't experience those infrequent issues.
Notes:
Official Lineage OS builds will not pass CTS/SafetyNet -- due to the AVB flag's "red" status.
Official Lineage OS builds ship with full treble compatibility, with VNDK runtime enforcement! This means that unlike most "ported treble" you'll see, ours is just as it would be from the OEM, and can run any GSI (yes, even Pie!) without need for hacks or additional flashable zips. We relabeled /oem as /vendor (as /oem isn't used in custom ROM's anyway). To use a GSI, flash official Lineage, then flash your GSI, it's that simple! Flashing a factory image will likely write over /oem and remove the mock vendor image. Please don't report GSI bugs here, report them instead to the GSI's maker.
Download:
LineageOS Updater
XDA:DevDB Information
[OFFICIAL] [WEEKLIES] [TREBLE] Lineage OS 15.1, ROM for the Moto Z2 Force
Contributors
npjohnson, invisiblek, erfanoabdi
Source Code: https://github.com/LineageOS
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: 8.0.0 (OCSX*)
Based On: LineageOS
Version Information
Status: Stable
Created 2018-07-15
Last Updated 2019-03-18
first (always wanted to do that)
thanks for this, nice work everyone!!!
Nice, I was wondering when we were going to get an official thread. I'll be waiting for the 17th to install the weekly.
I have the international version (-05) and have installed plenty of these version (since unofficial release from both invisiblek site and ods.ninja site) as well as the official weeklies (all versions already released) and everything works (based on the description here and known issues), so I'd say it's safe to say intl version had been tested and known to be working as well.
Let me know if you need additional/specific tests that I can do here.
Thanks the official post!
Also, how about volte support? Is it supposed to work?
felipevsw said:
I have the international version (-05) and have installed plenty of these version (since unofficial release from both invisiblek site and ods.ninja site) as well as the official weeklies (all versions already released) and everything works (based on the description here and known issues), so I'd say it's safe to say intl version had been tested and known to be working as well.
Let me know if you need additional/specific tests that I can do here.
Thanks the official post!
Also, how about volte support? Is it supposed to work?
Click to expand...
Click to collapse
If it isn't in the bugs list, its expected to work, it works on TMO and SPR. And I'll flag the international as compatible, thanks.
Since it isn't in known issues, I assume VoIP compression was fixed?
Edit: known workaround is use Bluetooth for video/VoIP calls. I don't know if USB audio would work or not.
Uzephi said:
Since it isn't in known issues, I assume VoIP compression was fixed?
Edit: known workaround is use Bluetooth for video/VoIP calls. I don't know if USB audio would work or not.
Click to expand...
Click to collapse
Added to OP as an issue.
??? for listing known accurate issues ???
I was pissed after installing Invictrix rom only to find out sound mods don't work.
I'm having an issue with video calls on Whatsapp and Duo. The other person can't hear me and I can't hear the other person.
Some other issues:
- Ok google not working with screen off (but it's fine to me)
- Overview is messy sometimes when using multi-window (doesn't show previews of multi-windowed apps)
- Even when installing Moto Camera the app does not show secondary camera functions (Portrait, B/W, etc)
For my daily usage the audio on video calls is the most serious issue that drives me back to stock. I hope they fix it soon.
fixed, can remove this.
DTHayakawa said:
I'm having an issue with video calls on Whatsapp and Duo. The other person can't hear me and I can't hear the other person.
Some other issues:
- Ok google not working with screen off (but it's fine to me)
- Overview is messy sometimes when using multi-window (doesn't show previews of multi-windowed apps)
- Even when installing Moto Camera the app does not show secondary camera functions (Portrait, B/W, etc)
For my daily usage the audio on video calls is the most serious issue that drives me back to stock. I hope they fix it soon.
Click to expand...
Click to collapse
Anything that uses VoIP compression is broken. Most video calling or internet calling apps in general use it.
DTHayakawa said:
I'm having an issue with video calls on Whatsapp and Duo. The other person can't hear me and I can't hear the other person.
Some other issues:
- Ok google not working with screen off (but it's fine to me)
- Overview is messy sometimes when using multi-window (doesn't show previews of multi-windowed apps)
- Even when installing Moto Camera the app does not show secondary camera functions (Portrait, B/W, etc)
For my daily usage the audio on video calls is the most serious issue that drives me back to stock. I hope they fix it soon.
Click to expand...
Click to collapse
1. Added to known bugs.
2. I don't experience this (and if it is present, its platform wide, and not our problem specifically).
3. I can't really easily support a prebuilt app all that easily. The B&W cam us supported in the default Snap camera.
Also, OTA will be broken until we figure out why signing server's aren't signing our payload zips right.
To work around this, you can update weekly by sideloading the nightly, rebooting to recovery (important), re-sideloading any mods you use (GApps, AddonSU, etc.).
fixed, can remove post now.
Uzephi said:
Anything that uses VoIP compression is broken. Most video calling or internet calling apps in general use it.
Click to expand...
Click to collapse
So I assume this would apply to hangouts and hangouts dialer?
npjohnson said:
Also, OTA will be broken until we figure out why signing server's aren't signing our payload zips right.
To work around this, you can update weekly by sideloading the nightly, rebooting to recovery (important), re-sideloading any mods you use (GApps, AddonSU, etc.).
Click to expand...
Click to collapse
Resolved.
Unable to install Lineage su addon (using TWRP 3.2.2-2)
_BEGIN_
Installing su addon...
set_metadata: Error on lstat of "/system/etc/init/superuser.rc": too many symlinks encountered
Updater process ended with ERROR: 7
_END_
Thoughts?
MattKilla said:
Unable to install Lineage su addon (using TWRP 3.2.2-2)
_BEGIN_
Installing su addon...
set_metadata: Error on lstat of "/system/etc/init/superuser.rc": too many symlinks encountered
Updater process ended with ERROR: 7
_END_
Thoughts?
Click to expand...
Click to collapse
I was literally plugging in to try this ROM until I read this. Have you tried Magisk yet?
Magisk Works
3's&7's said:
I was literally plugging in to try this ROM until I read this. Have you tried Magisk yet?
Click to expand...
Click to collapse
I have ran into this same issue when flashing build > lineage-15.1-20180721-nightly-nash-signed.zip
I can confirm that it happens with both TWRP 3.2.2-2 & TWRP 3.2.1-1
I flashed Magisk 16.4 and it works flawlessly no issues.
I am very happy with this ROM it works great for me. Thank You Devs! :good:
MattKilla said:
Unable to install Lineage su addon (using TWRP 3.2.2-2)
_BEGIN_
Installing su addon...
set_metadata: Error on lstat of "/system/etc/init/superuser.rc": too many symlinks encountered
Updater process ended with ERROR: 7
_END_
Thoughts?
Click to expand...
Click to collapse
was TWRP installed or did you just boot to it?
Melina Reborn
Melina returns for AOSP Support
If you loved Melina Kernel, you will be happy to hear that Melina Reborn has been developed with new V30A sources (as of rel_r5, Melina is now using more stable sources), with all of the features and performance you loved from Melina Kernel, but now with AOSP support! I did have to disable F2FS, if it is requested, I will try to re-implement it, but AFAIK it was never used on our devices anyway. Aside from F2FS everything else is available. Or should be
Tested on HavocOS-v3.2 on a US997 with BL 21E. (Note: My SD Card slot is broken. I cannot test any SDCard related issues. No issues are foreseen, but if any SDCard related issues happen to arise, please report them in as much detail as possible (dmesg, logcat, etc), as I cannot test SDCard functionality myself.)
Note: There have been reports of missing functionality under Pixel Experience Pie. This may occur on all Pie ROMs, but this is yet unknown. Pie was not tested, so consider this an Android 10 Only kernel for now.
"bootloop" note: Your G6 may reboot itself once after flashing my kernel, before reaching the OS boot animation. Do not panic, this is normal. I believe it is part of the Magisk recovery. If the bootloop occurs more than 1 time, even if it makes it to the OS, please report it here.
Primary Features:
Can now charge while powered off (offline charging) (rel_r5)
clang compiled and optimized kernel with extended armv8-a attributes (rel_r5) (for real this time!)
WiFi Hotspot working with properly configured ROM (rel_r5) (including 5ghz)
USB disconnect issues should be fixed (rel_r5)
Charging issues should be fixed (rel_r5)
Enabled FM Radio (requires supported ROM which currently there is none because it is still in testing, but looking promising)
Switched to more stable kernel sources (rel_r5) (see github readme)
Optimized and DEBUG editions (rel_r4)
Even more debug routines reduced (rel_r4)
Updated CPU optimizations one more time (tune for Kyro) (rel_r4) (this actually failed silently that is why rel_r4 was terrible)
More adjustments to reduce (and hopefully remove) the chance of random reboots (rel_r4)
Updated to AnyKernel 3, allows retaining Magisk when flashing kernel (rel_r3)
Module-less Kernel (rel_r3)
Removed old exFAT driver in favor of new sdfat driver (rel_r3)
Significantly reduce debugging messages/routines for performance enhancements (rel_r2)
Cleaner Kernel code, fixed all compiler warnings (with ubertc 6.x) (rel_r2)
Optimize compiler flags with big.LITTLE optimizations (rel_r2)
Updated AnyKernel Installer to place modules where they should be (rel_r2)
Fixed crashes due to missing 32-bit support (rel_r1.1)
Added maple iosched, enabled tcp westwood congestion sched
New kernel defaults: iosched (now: maple, was: cfq), tcp (now: westwood, was: bic) (Note: These default values may be overridden by the ROM. Be sure to use something like kernel adiutor to verify and set the values as desired.)
Binary releases built with ubertc aarch64-linux-android-6.x
DriveDroid CD-ROM Emulation Support
zzmove and elementalx governors
Various other improvements
Removes /sbin/rctd and related service entry in init.lge.rc if detected (for Stock ROMs, untested)
Remove forceencrypt (for Stock ROMs, untested)
Open source compatible replacement for Tuxera exFAT driver (removed in rel_r3, superseded by sdfat)
The following features from the original Melina Kernel are no longer available due to issues:
Flash Friendly FS (F2FS) Support
Downloads
Note: The difference between optimized and DEBUG is that the optimized version of Melina Kernel has extra debugging removed, which may increase battery life and performance slightly, but at the cost of making it harder to fix problems. The DEBUG kernel is more like most other kernels that are based on LGE official code, where LGE left on a lot of debug routines that aren't needed once the ROM is functional. However, those wanting to help fix issues, or ROM developers working on their ROM may want this extra information. This is why Melina Reborn now offers both kernels as an option.
rel_r5
US997: Optimized - DEBUG
H870 Optimized - DEBUG
H872 Optimized - DEBUG
rel_r4
US997: Optimized - DEBUG
H870 Optimized - DEBUG
H872 Optimized - DEBUG
rel_r3
US997
H870
H872
rel_r2
US997
H870
H872
rel_r1.1
US997
H870
H872
Known Issues
Some users have been reporting "random" reboots with rel_r1.1 and rel_r2. It seems linked to spi8 (fingerprint) and spi12 (touchscreen). An attempt to address this was added to rel_r3.
Attribution
For a full list of credits, please see the Github sources below, and browse the commit log. I try to keep commits as authentic as possible (except my own which I rebase and amend alot lol).
@TheWolfSVK for his work on the V30A sources, as well as for his incredible Havoc ROM
@osm0sis for AnyKernel3
Everyone who used and helped test the original Melina Kernel
When reporting any issues please be as detailed as possible. At a minimum, include your model and bootloader version. Any logs would be appreciated but I know sometimes it's not possible to get them (check for /sys/fs/pstore/console-ramoops). Also try to explain with as much detail as possible what you were doing when the problem happened (What app was active (running and on screen)? Which apps were in the background? Are you rooted? etc)
Github Sources
ROM Developers: You may include this kernel in your ROM so long as you link back to this thread in your release thread. If you modify any of the kernel or config, please also change the name from melinareborn to melinamodified in arch/arm64/configs/melina_common_android_intree_subconfig. This kernel can now be used in-tree while building Android, without clang, although ubertc may be required, untested (I built with ubertc in the tree, see here how to add Melina to a lineage-based G6 device tree.)
clang in-tree building now works and the bluetooth issue was found and addressed (don't ask, it was silly)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Guess who's back! Guess who's back! Haha welcome back! I know you thought about the song! Anyways to the point. Does this support stock as well? Since it uses 30A sources does that mean it can't be used on stock 8.0? It's essentially a pie kennel right? I loved custom ROMs but on TMobile using a phone as phone is hard without volte, vowifi. Still would love you to updateTWRP. It would also be nice if be you did it for v20 too. Since it's been basically the same phone. Although everyone with g5 would get jealous then. Haha! :silly::good::highfive:
Vortell said:
Guess who's back! Guess who's back! Haha welcome back! I know you thought about the song! Anyways to the point. Does this support stock as well? Since it uses 30A sources does that mean it can't be used on stock 8.0? It's essentially a pie kennel right? I loved custom ROMs but on TMobile using a phone as phone is hard without volte, vowifi.:
Click to expand...
Click to collapse
Stock is untested, I could not stand 21E long enough. Though Melina rel_o2 worked well for the 10 minutes I tried to deal with Stock
Have you tried Havoks? I don't have those services to test. If you can snag some logcats on Havoks' Android 10 of you trying to use the services, I will look at it but no promises)
Vortell said:
Still would love you to updateTWRP.
Click to expand...
Click to collapse
TWRP is in planning, since my SD is broken I can't test backups until my USB OTG arrive, should be tomorrow, but I have plans this weekend, and still have to try to fix the issue, so unknown ETA for TWRP.
Vortell said:
It would also be nice if be you did it for v20 too. Since it's been basically the same phone. Although everyone with g5 would get jealous then. Haha! :silly::good::highfive:
Click to expand...
Click to collapse
Depends on how technically it is the same phone. If it has the same hardware, perhaps a device config could be made.
zefie said:
Depends on how technically it is the same phone. If it has the same hardware, perhaps a device config could be made.
Click to expand...
Click to collapse
Both are msm8996 hardware and there is souces for the rest in older trwp page I think. It was just a wish I didn't think you would actually do it.
Vortell said:
Both are msm8996 hardware and there is souces for the rest in older trwp page I think. It was just a wish I didn't think you would actually do it.
Click to expand...
Click to collapse
I mean, if EVERYTHING was the same (except a few unique traits, kinda like the differences between H870, H872 and US997) then it wouldn't really be a problem. But if it even has a different camera, it becomes complicated.
zefie said:
I mean, if EVERYTHING was the same (except a few unique traits, kinda like the differences between H870, H872 and US997) then it wouldn't really be a problem. But if it even has a different camera, it becomes complicated.
Click to expand...
Click to collapse
I see I though blobs were easy, but I have yet to build for Android. If you want to take a look. After this post I promise no more off topic posts.
Here's a link to a kernel kind of like yours for v20:
https://forum.xda-developers.com/v20/development/kernel-gamma-kernel-t394011
Here's modified for stock kernel:
https://forum.xda-developers.com/v20/development/h918-h910-us996-ucl-mk2000-kernel-t3708330
Here's Los 17.1 for it from x86cpu who is same person who builds los for LG G6:
https://forum.xda-developers.com/v20/development/rom-unofficial-lineageos-17-0-lg-v20-t4010893
Here's TWRP for it:
https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239
One last thing do you want me to test this on stock 8.0 LG G6 us997? I swear if havoc had volte I would never use anything else. My favorite ROMs are havoc , aicp and crdroid. I had Samsung S5 and it had dozens of ROMs to try. My note 4 had probably a dozen. LG v20 has probably 10, but only 3 current ones.
Vortell said:
I see I though blobs were easy, but I have yet to build for Android. If you want to take a look. After this post I promise no more off topic posts.
Here's a link to a kernel kind of like yours for v20:
https://forum.xda-developers.com/v20/development/kernel-gamma-kernel-t394011
Here's modified for stock kernel:
https://forum.xda-developers.com/v20/development/h918-h910-us996-ucl-mk2000-kernel-t3708330
Here's Los 17.1 for it from x86cpu who is same person who builds los for LG G6:
https://forum.xda-developers.com/v20/development/rom-unofficial-lineageos-17-0-lg-v20-t4010893
Here's TWRP for it:
https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239
One last thing do you want me to test this on stock 8.0 LG G6 us997? I swear if havoc had volte I would never use anything else. My favorite ROMs are havoc , aicp and crdroid. I had Samsung S5 and it had dozens of ROMs to try. My note 4 had probably a dozen. LG v20 has probably 10, but only 3 current ones.
Click to expand...
Click to collapse
I'll look into the other device when I get a chance, but I'll be honest its pretty low priority. You can try the kernel on stock. I did score 3 months of Mint Mobile free during their (special american footbal game that has a huge trademark liability on its name) special and apparently they support VoLTE. No promises but I will try to look into it, as I am also working with the developer of Havoc.
Also be on the lookout for rel_r2, r1/r1.1 was kinda rushed, but I am working to further optimize r2, beyond even what the original Melina Kernel had.
zefie said:
I'll look into the other device when I get a chance, but I'll be honest its pretty low priority.
Click to expand...
Click to collapse
Either way always love a extra developer on any phone i own. If you are saying you hope to get volte working on custom ROMs for the g6 that's more impressive and should be a higher priority. I'm almost giddy just thinking about being able to use custom ROM with volte. It would open it up for at least g5 and v20. Assuming you open source it.
Also u will give it a try on stock and let you know.
Hey guys,
On stock pie V30B bluetooth isn't working on my h870 with all modified kernels I tried. Any suggestions? Thank you.
I'm glad that you're back zefie ?
Hi there . it doesn't work for me with the V30B Stock rum either. is there a modified kernel for stock pie?
Rothrex93 said:
Hi there . it doesn't work for me with the V30B Stock rum either. is there a modified kernel for stock pie?
Click to expand...
Click to collapse
It isn't for STOCK Rom this kernel is for AOSP ROMS. Stock kernel has a lot proprietary stuff.
SkylineDiT said:
It isn't for STOCK Rom this kernel is for AOSP ROMS. Stock kernel has a lot proprietary stuff.
Click to expand...
Click to collapse
Sorry you misunderstood. my Stock V30B rom to want a modified kernel. Has anyone done this already?
Rothrex93 said:
Sorry you misunderstood. my Stock V30B rom to want a modified kernel. Has anyone done this already?
Click to expand...
Click to collapse
Sorry, this is for AOSP and there is no plans for a Melina for stock Pie. You can thank LGE for abandoning the US997 Unlocked variant for the fact that I cannot make a Pie Stock kernel
Testing Melina Reborn kernel rel2 on H870 bootloader 20J ROM: PixelExpierence 2019-08-23-2221 (PIE). BT works fine battery is good performace great. Not working: camera, flashlight, NFC, and fastcharging. Will try to test rel3
I am using rl3 with havocOS 3.2 without issues.
I noticed that my device isn't heating as much as it used to.
Battery life is better.
H870.
I agree the melina kernel installation in TWRP preserved all magisk, viper settings in Havoc 3.2 07.02. All works from NFC to kernel adiutor settings e.g. cpu governor zzmove (very quick and more energy safe than performance) - no more powersave which mantained my phone very cool even during games, but was very slow in starting apps. Now my phone is slightly warm all the time, but very quick and responsive. Thank you very much zefie!
Hello, Sir can i install it on H870 with Havoc 2.9 ( Pie) with magisk installed ?
kurogami555 said:
Hello, Sir can i install it on H870 with Havoc 2.9 ( Pie) with magisk installed ?
Click to expand...
Click to collapse
There have been reports of it not working with PE Pie, not sure about Havoc Pie. The kernel may only work on Android 10, not sure yet.. If you do try it, be sure it have a backup of your current kernel.
Vortell said:
Either way always love a extra developer on any phone i own. If you are saying you hope to get volte working on custom ROMs for the g6 that's more impressive and should be a higher priority. I'm almost giddy just thinking about being able to use custom ROM with volte. It would open it up for at least g5 and v20. Assuming you open source it.
Also u will give it a try on stock and let you know.
Click to expand...
Click to collapse
Three things
1) What is the device model code (us996?) for a kernel for you to test
2) it won't work on stock and probably only Android 10 ROMs, if at all lol
3) still no eta
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/10.0/README.mkdn
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
gapps(NANO) (Download from here)
Magisk 20.0 or newer for root (after first boot) - (Download from here)
First time installation:
step 1 OEM UNLOCK
step 2 Flash twrp using ODIN
step 3 Wipe everything....Format DATA
step 4 Reboot to recovery
step 5 Flash Rom and Gapps...Flash magisk after first boot
Update installation:
step 1 Flash Rom and Gapps, Magisk should survive
Sources:
ROM: https://github.com/crdroidandroid
Others: Click Here
Download:
ROM Download
ROM Download via MEGA
Changelog: https://raw.githubusercontent.com/crdroidandroid/android_vendor_crDroidOTA/10.0/changelog_star2lte.txt
Known issues:
None so far
Visit official website @ crDroid.net
crDroid Exynos9810 Telegram
crDroid Community Telegram
Donate to help our team pay server costs
XDA:DevDB Information
crDroid, ROM for the Samsung Galaxy S9+
Contributors
vsoma
Source Code: https://github.com/vrnsoma?tab=repositories
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: OneUI 2.x
Based On: LOS
Version Information
Status: Stable
Current Stable Version: 1.x
Stable Release Date: 2020-04-30
Created 2020-04-30
Last Updated 2020-05-17
Reserved
Highlights & Device Specific Changes: Initial Support
Build type: Weekly
Device: Samsung Note 9 Exynos (crownlte)
Device maintainer: Varun Soma
Required firmware: OneUI 2.x
===== 05/05/2020 =====
- Initial Support
- Fixed Sim Loop issue
===== 05/09/2020 =====
-Testing OTA
-Faceunlock is still here
===== 05/12/2020 =====
CR Changes
~~~~~~~~~~~~~
Updated to 6.6
Device Specific Changes
~~~~~~~~~~~~~~~~~~~~~~~
Kernel Changes:
dts: set noatime flag for system + vendor
defconfig: regenerate
Linux 4.9.2 23
ALSA: hda: Match both PCI ID and SSID for driver blacklist
sctp: Fix SHUTDOWN CTSN Ack in the peer restart case
MIPS: perf: Remove incorrect odd/even counter handling for 16400
xprtrdma: Fix backchannel allocation of extra rperdma_reps
net: systemport: suppress warnings on failed Rx SKB allocations
net: bcmgenet: suppress warnings on failed Rx SKB allocations
lib/mpi: Fix building for powerpc with clang
net: dsa: b53: Rework ARL bin logic
scripts/config: allow colons in option strings for sed
cifs: protect updating server->dstaddr with a spinlock
net: stmmac: Fix sub-second increment
wimax/i2400m: Fix potential urb refcnt leak
===== 05/16/2020 =====
CR Changes
~~~~~~~~~~~~~~~~~~~~~~
Brought back face unlock
Fixed launcher issues
Device Specific Changes
~~~~~~~~~~~~~~~~~~~~~~~
Kernel Changes:
TOo many to list
Basically redesigned kernel with better perf, and better temps
Volte doesn't work! Please help! I can use LTE but Volte doesn't work .. i can't make calls with it .. i have an Samsung galaxy s9 plus ( g965f ) ..
I tried 5-6 roms ( including crdroid ) , both android 9 & android 10. None of them seems to be working ..
I can use the LTE, but i can't make calls with it...
I tried adding apn settings after watching some youtube videos but it didn't work!
It works on the stock rom, i also have backup of efi folder and baseband if somehow we can use it for fixing it .. i am not a developer so, please help!
Thanks!
ayush2609 said:
Volte doesn't work! Please help! I can use LTE but Volte doesn't work .. i can't make calls with it .. i have an Samsung galaxy s9 plus ( g965f ) ..
I tried 5-6 roms ( including crdroid ) , both android 9 & android 10. None of them seems to be working ..
I can use the LTE, but i can't make calls with it...
I tried adding apn settings after watching some youtube videos but it didn't work!
It works on the stock rom, i also have backup of efi folder and baseband if somehow we can use it for fixing it .. i am not a developer so, please help!
Thanks!
Click to expand...
Click to collapse
Yes... for volte start pestering Samsung forums for that and not xda... use oneui based Roms for volte Alexis or devbase...
New build is up
https://mega.nz/file/7t5SiaDa#8BerwtnprBzrfjwbcS6pI5sVXYTX991PWXpzI3WO1YE
Changelog (05/05/2020)
--------------------------------
Fixed Sim Loop Issue
Am stoked to see this ROM running for our device.
Before I get to carried away would I need to have a version of Android 10 already installed for this to work or will it work with the Android 9 files already installed??
Chris.cj72 said:
Am stoked to see this ROM running for our device.
Before I get to carried away would I need to have a version of Android 10 already installed for this to work or will it work with the Android 9 files already installed??
Click to expand...
Click to collapse
Please install the latest version of oneui (Samsung OEM firmware) For Android 10 and then come back to installing the rom....the installation of the latest Samsung firmware updates the firmware files on your phone and gets it ready for android 10.
Does this support OTA?
garettadrian said:
Does this support OTA?
Click to expand...
Click to collapse
yes, it is official, but i would not recommend using ota, its slower
vsoma said:
Please install the latest version of oneui (Samsung OEM firmware) For Android 10 and then come back to installing the rom....the installation of the latest Samsung firmware updates the firmware files on your phone and gets it ready for android 10.
Click to expand...
Click to collapse
Does this mean a complete update? If so is there a recommended one? I've only used an Android 10 Vendor image but, I noticed that a MicroG package, while it allows for Signature Spoofing, it does NOT actually ask me for location permission in the background despite being an option. This could be a build issue from said package, however.
EDIT: Issue resolved; it was the order of how I installed things that got it messed up.
I installed this on my s9+ exynos, and when im charging the phone says the battery's capacity is 3000 mA on the lock screen. The battery life was also not good, with around 3 hrs of SOT before i got to 10%. Is it detecting my battery wrong? I made sure to flash the star2lte version. Cheers.
I dont know what is the issue is it with me or anyone else
On all aosp roms i have tried
They work good no issues but i cant game
I play pubg or any game device heats a lot and battery drops even when charging and i use fast charger
And everything is normal on stock roms
I tried evo, cr droid, pixel experience with stock and white wolf kernel also nothing helped
Thank you
ayush2609 said:
Volte doesn't work! Please help! I can use LTE but Volte doesn't work .. i can't make calls with it .. i have an Samsung galaxy s9 plus ( g965f ) ..
I tried 5-6 roms ( including crdroid ) , both android 9 & android 10. None of them seems to be working ..
I can use the LTE, but i can't make calls with it...
I tried adding apn settings after watching some youtube videos but it didn't work!
It works on the stock rom, i also have backup of efi folder and baseband if somehow we can use it for fixing it .. i am not a developer so, please help!
Thanks!
Click to expand...
Click to collapse
Jio/VoLTE will never work w these ROMs. The only reason I'm not switching to AOSP roms.
happy3777 said:
I dont know what is the issue is it with me or anyone else
On all aosp roms i have tried
They work good no issues but i cant game
I play pubg or any game device heats a lot and battery drops even when charging and i use fast charger
And everything is normal on stock roms
I tried evo, cr droid, pixel experience with stock and white wolf kernel also nothing helped
Thank you
Click to expand...
Click to collapse
We are still looking into this issue
raghavsharmaxda said:
Jio/VoLTE will never work w these ROMs. The only reason I'm not switching to AOSP roms.
Click to expand...
Click to collapse
Guess what! VOLTE is in the works....But it may take some time!
Samsung voLTE strings attached
vsoma said:
Guess what! VOLTE is in the works....But it may take some time!
Click to expand...
Click to collapse
Hey, that's great! VoLTE proprietary implementation issue workaround would make almost every fast AOSP ROMs to be actually usable with no quirks compromised. Then again, every good rom needs time. Thanks for announcing that. I'll keep an eye on this thread.
VOLTE issue
Hi mate , try flashing this ROM, I am using this and VOLTE is working perfectly fine ... Best!
https://forum.xda-developers.com/ga...nt/alexis-rom-1-0dtb503-2020-patches-t4066911
[email protected] said:
Hi mate , try flashing this ROM, I am using this and VOLTE is working perfectly fine ... Best!
https://forum.xda-developers.com/ga...nt/alexis-rom-1-0dtb503-2020-patches-t4066911
Click to expand...
Click to collapse
This is a ONEUI based rom, ofc it will work! AOSP wont work!
What tweak can i use to boost the audio and sound quality?
And good camera app?
For this rom?
why are the mygalaxy, mysingtel, ubank and yandex apps on the system? And why can't I find them on debloat ??
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Rom Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Device specific Features:
kernel features:
sultan's cpu input boost & devfreq boost
custom ioched algos(maple,etc.)
msm8994(sd810) specific commits
boeffla's wakelock blocker(must be configured by the user)
a lot of backport commits from 3.18y/4.4 msm kernels
much more(see github repo)
custom power set-up(optimized cpuset,governor,iosched parameters)
z3fold for zram(as stock)
removed sony's debug stuff
Flashing Instructions:
Pre-installation:
TWRP
gapps (i advise you nikgapss or mindgapss)
Magisk 20.0 or newer for root (after first boot) - (Download from here)
First time installation:
reboot into recovery
format data
reboot in recovery
wipe data
install rom
install gapps(if you want)
reboot
Update installation:
reboot into recovery
wipe cache/dalvik cache
install rom
install gapps(if they were already present)
reboot
Sources:
ROM: https://github.com/crdroidandroid
Kernel & device-tree & vendor: https://github.com/linckandrea
Download:
ROM SINGLE & DUAL SIM
Known issues:
You tell me...
Contributors
tarkzim, berni-0815
Visit official website @ crDroid.net
crDroid Community Telegram
Donate to help our team pay server costs
Donate me a coffe
NOTES:
if you have a bug please send me a logcat and provide much informations as possible
(step to reproduce, you set-up(magisk, gapps,etc.))
Do NOT send me logcats if you installed weird magisk modules(bad audio mods, bad performance mods,etc.)
if you want you can join in my telegram group where i usually release things(roms, kernel, etc.) early
reserved 2
hello, any known issues? i can test.
Good job, thanks!
Hi, can you check if you guys happened some issues as me:
1. Charging so slow
2. Rebooting when open Youtube app
3. Cannot setup fingerprint
The others are ok, looking good with unlock by face
lctuan0807 said:
Hi, can you check if you guys happened some issues as me:
1. Charging so slow
2. Rebooting when open Youtube app
3. Cannot setup fingerprint
The others are ok, looking good with unlock by face
Click to expand...
Click to collapse
if you have a bug please send me a logcat and provide much information as possible
(step to reproduce, you set-up(magisk, gapps,etc.))
update version ? 13.07 los.
my device is e6683.
after flash lineageOs 18 v.20210713 there is a little problem for the microphone when using the whatsapp application, recording application and type by voice.
microphone like auto mute so that the other person cannot hear the sound, and when recording no files are generated.
the second problem is the camera results are not good,
although already using a third party, namely open camera.
third NFC not working.
For now, that's all I can feel, thank you
lctuan0807 said:
Hi, can you check if you guys happened some issues as me:
1. Charging so slow
2. Rebooting when open Youtube app
3. Cannot setup fingerprint
The others are ok, looking good with unlock by face
Click to expand...
Click to collapse
were you able to solve these problems?
New update
changelog(a lot of thing if you want more details go to see my github repos):
merged latest cr source (as 22/09/2021)
perfomace improvements (perf blobs from oneplus 2 + custom powerscript(took me a lot to figure how keep cool sd810 while maintening a decent "smothness)
added & enabled sdfat
nfc improvements(added extended length NFC support & disabled NfcF HCE)
reworked audio configs(i have no problem with BT audio now)
removed sony's blobs for debug(iddd, idd, etc.)
much more (see my github repos)
download link has been alredy updated in 1th post
mthree3 said:
my device is e6683.
after flash lineageOs 18 v.20210713 there is a little problem for the microphone when using the whatsapp application, recording application and type by voice.
microphone like auto mute so that the other person cannot hear the sound, and when recording no files are generated.
the second problem is the camera results are not good,
although already using a third party, namely open camera.
third NFC not working.
For now, that's all I can feel, thank you
Click to expand...
Click to collapse
kerimcem said:
update version ? 13.07 los.
Click to expand...
Click to collapse
ehm i think you are in the wrong thread
hi everybody
"ok google" works good? thanks u...
linckandrea said:
New update
changelog(a lot of thing if you want more details go to see my github repos):
merged latest cr source (as 22/09/2021)
perfomace improvements (perf blobs from oneplus 2 + custom powerscript(took me a lot to figure how keep cool sd810 while maintening a decent "smothness)
added & enabled sdfat
nfc improvements(added extended length NFC support & disabled NfcF HCE)
reworked audio configs(i have no problem with BT audio now)
removed sony's blobs for debug(iddd, idd, etc.)
much more (see my github repos)
download link has been alredy updated in 1th post
Click to expand...
Click to collapse
Hi, i'm new to this thread. After i read the posts, your latest update was september 28th and it is said the link has been updated in the first post. But after i open it the file naming date was 20210527, which is May 27th. Is this the correct file for the latest version or i'm missing something out?
Zenzarahis said:
Hi, i'm new to this thread. After i read the posts, your latest update was september 28th and it is said the link has been updated in the first post. But after i open it the file naming date was 20210527, which is May 27th. Is this the correct file for the latest version or i'm missing something out?
Click to expand...
Click to collapse
fixed, seems that xda ignored dowload's hyperlink edit
linckandrea said:
New update
changelog(a lot of thing if you want more details go to see my github repos):
merged latest cr source (as 22/09/2021)
perfomace improvements (perf blobs from oneplus 2 + custom powerscript(took me a lot to figure how keep cool sd810 while maintening a decent "smothness)
added & enabled sdfat
nfc improvements(added extended length NFC support & disabled NfcF HCE)
reworked audio configs(i have no problem with BT audio now)
removed sony's blobs for debug(iddd, idd, etc.)
much more (see my github repos)
download link has been alredy updated in 1th post
Click to expand...
Click to collapse
hey nice job ! this rom full of features
i ported boot.img and flashed this rom to my e6883{z5pd)
rom is smooth and nice
but there is some problems
main one is BT and 8mp camera !
i have no idea how to bug fix android 7+ roms
im planning to to replace all BT files of stable lineage os 11
for camera i replaced camera files but stuck in bootloop
and btw first boot camera is upside down !
pls help me or share any useful android 11 port/bugfix guide link !
TNX
update: the rom i ported was version 7.6 and dont know was it urs or i got it from somewhere else
this one gets bootloop from start even with ported boot.img
seems some drivers r missing
unfied remote program not work phone reset.
New update
changelog(a lot of thing if you want more details go to see my github repos):
merged latest cr source (as 14/11/2021)
fixed fingerprint sensor with enforced selinux
download link has been alredy updated in 1th post
newbiez5p said:
hey nice job ! this rom full of features
i ported boot.img and flashed this rom to my e6883{z5pd)
rom is smooth and nice
but there is some problems
main one is BT and 8mp camera !
i have no idea how to bug fix android 7+ roms
im planning to to replace all BT files of stable lineage os 11
for camera i replaced camera files but stuck in bootloop
and btw first boot camera is upside down !
pls help me or share any useful android 11 port/bugfix guide link !
TNX
update: the rom i ported was version 7.6 and dont know was it urs or i got it from somewhere else
this one gets bootloop from start even with ported boot.img
seems some drivers r missing
Click to expand...
Click to collapse
long story short, your port will never work
the only way to get a stable and fully working rom is compiling it from source.
I saw that z5pd share the same hardware of z5 and z5c so you will only need a specific repo for device tree and vendor
linckandrea said:
New update
changelog(a lot of thing if you want more details go to see my github repos):
merged latest cr source (as 14/11/2021)
fixed fingerprint sensor with enforced selinux
download link has been alredy updated in 1th post
long story short, your port will never work
the only way to get a stable and fully working rom is compiling it from source.
I saw that z5pd share the same hardware of z5 and z5c so you will only need a specific repo for device tree and vendor
Click to expand...
Click to collapse
tnx for info
i found another version of this rom in russ site i ported boot.img it works perfectly ! even battery life better than all other z5pd roms im planning to share it on xda but dont know to whom should i give credit there is no name in build prop or anywhere else !
After using this rom for a couple of days and some random crashes I can say is not stable enough for daily use, but for a secondary phone is ok. It looks pretty, smoth, the termals are great.
The UI doesn't show the LTE signal strengh correctly
Crashes opening the last version of youtube & youtube music.
whatsapp audio messages have a very long delay to play
opening the camara on whatsapp it is very laggy
fingerprint doesn't work (that's nor a problem for me)
everything else looks fine.