Latest update (8/13): I've been busy recently and haven't had the time or motivation to spend much time on this. Personally, I flashed over to x86cpu's builds (https://forum.xda-developers.com/lg-...lg-g6-t3789468) as they're almost the same as what I was building anyway and he definitely knows what he's doing more than I do. If you decide to move from mine to his, make sure to flash the "to-x86" conversion zip, as his are signed differently and will corrupt your data if you flash directly over mine. Feel free to use my old builds if you want, I'll keep the thread and download links up for now in case I decide to resume development at some point in the future. Thanks for the support, it was fun, hopefully 15.1 for G6 goes official soon
{
"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"
}
DisclaimerYour warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Project descriptionLineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
With the help of many in the Telegram channel, I have build LOS 15.1 from source for the US997.
I’ve been using these builds for a few weeks and have been happier than when I was using 14.1 official builds, but of course your mileage may vary.
How to install:
Wipe Data/Factory reset.
Format System.
If you're coming from stock Oreo, flash the nougat bootloader or fingerprint won't work on this ROM
Flash the ROM.
Flash 8.1 Gapps.
(Optional) Flash root method of choice. (As of 0325, you can use magisk, superSU or other root methods)
Known Bugs:
5 GHz Wi-Fi hotspot broken
4K video recording broken
Always on display doesn't use the low power screen - it will drain battery quickly when its on
USB MTP (file transfer) is broken (it works in recovery so you can switch to that to copy file if needed) **
VoLTE broken
Encryption - Reports that enabling encryption leads to bootloops - Needs further testing
CDMA on Verizon must make call out after reboot in order to have incoming calls/txt working
Poor mic quality when using speakerphone
Possibly more
Working Features:
Oreo 8.1 with June security update
Boots
RIL (Calls, SMS, Data)
Wi-Fi
Bluetooth playback and mic (I made a call successfully and until proven otherwise, it seems the BT mic issues are isolated to H870 and does not affect US997)
NFC
GPS
Camera, including Gcam, and wide cam in apps that support it like the built-in LOS Snap cam and Open Camera (except 4k video recording)
Video Playback (L1/HD DRM playback working, unlike 14.1)
Audio (Audio levels have been tweaked but may still need further adjusting)
Fingerprint (currently only works on Nougat bootloader)
Flash
Quick charging (PD and QC and wireless chargers)
Off-mode charging (plugging the phone in when its off/dead properly boots into charging only mode)
SD cards including exfat
No CPU stuttering bug like 14.1 has
Downloads:The ROM - lineage-15.1-20180618-NateVM-UNOFFICIAL-us997.zip changelog
https://www.androidfilehost.com/?fid=962339331459001292
md5: d97392e7f7b9f91cce760ee572483d5b
Older versions available here
**Modded TWRP recovery - recovery_melina-TWRP_v3.2.1_18-03-10_NateVM_LGUS997_CacheAsVendor_rel1.img
ecb5f0a062bd26e87eaa0e206ec71d6e
**As of 0325, this is unneeded and likely to cause different issues, use any other us997 compatible recovery.
http://opengapps.org - ARM64
CStark27’s GCam mod recommended (and supports wide angle)
**Fixed in 0618 release
Screenshots:https://imgur.com/a/2T7pd
Credits:
Lineage OS team
Rashed97 and x86cpu, the official LOS maintainers
EvilHowl
Rc420Head
J0SH1X
CPL593h
Imaginovskiy
Zefie
And everyone else in Telegram helping test builds and report bugs
About Me:
I am very much a newb at ROM building. I've been using CM/LOS for years and one of the main reasons I bought the us997 was that it is "officially" supported by LOS. But I was disappointed to find that the official 14.1 builds for G6 had some major issues (like CPU performance) and after using it for a few months it felt like I took a big step backwards when I upgraded from my Nexus 5x. So I started searching around to see if anyone had been able to fix those issues and found Evilhowl's unofficial H870 14.1 builds had CPU performance fixed. Since nobody seemed to care about building a version for us997, in January I took it upon myself to attempt to learn how to compile the ROM myself.
While learning how to do my first build, Evilhowl and others in telegram started making some breakthroughs on getting 15.1 builds to run. Since I was attempting to build from source anyway, I decided to see if I could build LOS 15.1. After many attempts of trial and error, I got 15.1 to build and worked with the H870 guys to get some additional fixes merged. By cherry-picking specific fixes from h870 and other devices on the LOS gerrit, I got a ROM that I'm happier with than the 14.1 official release.
Since I've been using this ROM as my daily driver for a few weeks and multiple people in telegram had been asking about it, I figured I would post it here on xda to share once I got everything uploaded to github. I'll do my best to keep the list of features/bugs in this post up to date, and I'll see what I can do to try to fix some of the things, but since I'm still quite new at this, I can't promises I'll actually be able to fix much myself. If anyone has any clues or potential fixes from other devices that may help fix any of the known bugs, please let me know. I'm just hoping some things get fixed upstream by the LOS team or some of the H870 devs figure out a fix and I can copy stuff from them.
LineageOS 15.1 unofficial, ROM for the US997 LG G6
Source Code: https://github.com/natemckn/android_kernel_lge_msm8996/
https://github.com/natemckn/android_device_lge_msm8996-common/
https://github.com/natemckn/android_device_lge_g6-common/
https://github.com/natemckn/android_device_lge_us997/
ROM OS Version: 8.1 Oreo
ROM Kernel: Linux 3.18.102
Based On: LineageOS 15.1
Version Information
Latest Version: lineage-15.1-20180618
Created 2018-03-11
Last Updated 2018-06-18
FAQ
Q. First time setup wizard crashes:
A. Get latest official gapps from opengapps.org. Older unofficial gapps are known to crash setup wizard.
Q. All the H870 Oreo releases talk about flashing a kernel after the ROM, do I do that here?
A. Everything is in the built in kernel now.
Q. Wifi and/or BT don't work! In about system, mac address shows as all 0s
A. You wiped your /misc which overwrote your mac address. Other LG devices have been able to fix this with the follow procedure, but I have not tested it on G6: https://forum.xda-developers.com/showpost.php?p=70474540&postcount=12
Q. How do I know if I'm using your old modded recovery? You're dumb for not making any interface changes to identify it!
A. You're right, in hindsight that was dumb to release a modded version with no distinguishing features. Go to the Mount menu in TWRP. Look for "Cache" or "Vendor". If your TWRP version shows "Vendor" then you have my old modded one, switch to a different TWRP in order for any new builds to flash properly. If your TWRP version shows "Cache" as a mountable partition then you have a normal good recovery
Q. Fingerprint doesn't work! The option is missing from the menus
A. This ROM assumes you have the Nougat baseband/firmware since we were working on this before Oreo became available. If you updated to stock Oreo prior to flashing this ROM, then you have the Oreo baseband/firmware, which is known to break fingerprint. The only fix right now is to flash back to Nougat baseband in order for this ROM to work properly. You can flash the 17A (Nougat) baseband from here:
https://files.persona.cc/zefie/files/cell/LGG6/US997/ROMs/bootloader-only/
Using the US997 , updated today but phone wont charge while on, i have to charge in twrp, any idea? last version was fine.
Raidel™ said:
Using the US997 , updated today but phone wont charge while on, i have to charge in twrp, any idea? last version was fine.
Click to expand...
Click to collapse
I noticed when I first switched to this type of build my battery stats were really messed up for a bit and when I plugged it in it wouldn't act like it was charging. After using it for a few hours and doing a restart, I noticed the started working correctly again and when I plugged it in it charged as normal and has worked fine since. So I think give it a few hours and a restart or two to re-calibrate and see if it starts charging?
I see you already edited OP, but just wanted to document that SuperSU does not work in this version. Is the link for the last version still up somewhere? Specifically for US997?
sc4s2cg said:
I see you already edited OP, but just wanted to document that SuperSU does not work in this version. Is the link for the last version still up somewhere? Specifically for US997?
Click to expand...
Click to collapse
Here's the download link for the last no treble build I did from a few weeks ago:
https://www.androidfilehost.com/?fid=673956719939826837
natemckn said:
Here's the download link for the last no treble build I did from a few weeks ago:
https://www.androidfilehost.com/?fid=673956719939826837
Click to expand...
Click to collapse
Thanks!
Couple things to report on the build in OP for US997: booting up goes straight to bootloop unless I manually go to twrp and make it do a system reboot from there. So far that method worked 1/3 times. When it doesn't work it goes into a bootloop once and then just turns off. Also, it might be turning off at random times (turned off during class while charging) and if I try to turn it back on it says that it doesn't enough power to boot. Plugging it into a charger will let it turn on (again, into a bootloop until I go to twrp manually) and once in the OS it showed 75% battery level.
sc4s2cg said:
Thanks!
Couple things to report on the build in OP for US997: booting up goes straight to bootloop unless I manually go to twrp and make it do a system reboot from there. So far that method worked 1/3 times. When it doesn't work it goes into a bootloop once and then just turns off. Also, it might be turning off at random times (turned off during class while charging) and if I try to turn it back on it says that it doesn't enough power to boot. Plugging it into a charger will let it turn on (again, into a bootloop until I go to twrp manually) and once in the OS it showed 75% battery level.
Click to expand...
Click to collapse
Damn, sorry that its not working for you. I did a couple wipe and flash tests over the weekend to make sure things were working as expected before posting here and I never had a problem getting it to boot (except when I tried Magisk). I did notice some battery stat weirdness for a while but it went back to working normally and charging normally after about an hour and a reboot and hasn't been a problem for me since.
Can you try the 0208-noTreble build linked to see if the same problems happen there, or if its related to the experimental changes that were added since then?
natemckn said:
Damn, sorry that its not working for you. I did a couple wipe and flash tests over the weekend to make sure things were working as expected before posting here and I never had a problem getting it to boot (except when I tried Magisk). I did notice some battery stat weirdness for a while but it went back to working normally and charging normally after about an hour and a reboot and hasn't been a problem for me since.
Can you try the 0208-noTreble build linked to see if the same problems happen there, or if its related to the experimental changes that were added since then?
Click to expand...
Click to collapse
Actually I've been using the February version for a couple weeks with no major issues, just some minor bugs like sometimes the screen turns on blank (just turn off and on again) and the touchscreen is not responsive if the phone turns off b/c of battery levels (just reboot again).
sc4s2cg said:
Actually I've been using the February version for a couple weeks with no major issues, just some minor bugs like sometimes the screen turns on blank (just turn off and on again) and the touchscreen is not responsive if the phone turns off b/c of battery levels (just reboot again).
Click to expand...
Click to collapse
Same boat here; been using the 2/8 build for a while with no major issues. Wasn't able to get the new build to boot yesterday, but now that I know there's an extra step or two I'm going to try flashing the new build again sometime this week.
OK, I've got a lead on the battery weirdness. It seems that every time you boot into this recovery, it does something to the battery stats, so when you boot into system it bugs, and for me appears stuck at 50%. A single reboot seems to fix it (until you go into recovery again). I'll poke around the recovery some more to see if I can get that fixed since I'm pretty sure its a result of something I did.
What bugs are fixed in this new build compared to the Feb build?
Thanks again for bringing 8.1 to the us997. Be awesome if u or somebody else capable got the time to build a ResRemix Oreo for us997
So, oddly enough I wasn't having any issues with battery weirdness (I've been using the latest build for about 5 hours now) but wireless charging doesn't seem to work; the phone goes from charging to not charging on a second-to-second basis. Charging via cable seems to be working fine. Also, not sure if this is a Modded Gcam specific issue, but it seems like accessing the front facing camera causes crashes.
BigBrad75 said:
What bugs are fixed in this new build compared to the Feb build?
Thanks again for bringing 8.1 to the us997. Be awesome if u or somebody else capable got the time to build a ResRemix Oreo for us997
Click to expand...
Click to collapse
Changes in 0311 build:
offmode charging fixed
broke camera, then fixed it again
updated graphics blobs. feels smoother, but might be placebo since benchmarks are the same
fixed time sync bug
encryption is enabled, but I have no clue if it works
merged a bunch of experimental treble stuff Rashed posted on gerrit
some haptics related fixes
march security patch
upstream stuff from LOS, too much to list
KaLiBLeeK said:
So, oddly enough I wasn't having any issues with battery weirdness (I've been using the latest build for about 5 hours now) but wireless charging doesn't seem to work; the phone goes from charging to not charging on a second-to-second basis. Charging via cable seems to be working fine. Also, not sure if this is a Modded Gcam specific issue, but it seems like accessing the front facing camera causes crashes.
Click to expand...
Click to collapse
I guess wireless charging is broken, so I put it in OP as known bug. I don't have a charging pad to test with. Can you grab a logcat when its happening? Maybe that'll give a hint as to whats broken.
natemckn said:
I guess wireless charging is broken, so I put it in OP as known bug. I don't have a charging pad to test with. Can you grab a logcat when its happening? Maybe that'll give a hint as to whats broken.
Click to expand...
Click to collapse
I've attached a partial LOGCAT here. Let me know if there's enough information here to work with, or if I should pull another.
does it support exfat tf card？
VoLTE? pls? sir?
ErickG233 said:
does it support exfat tf card？
Click to expand...
Click to collapse
Not sure. If you test it let me know and i'll update op.
Anyone have a link to the 14.1 LOS SU addon? Tried to find on XDA but couldn't. As listed, SuperSu lets me boot back into system, but not installed or rooted.
Sobek5150 said:
Anyone have a link to the 14.1 LOS SU addon? Tried to find on XDA but couldn't. As listed, SuperSu lets me boot back into system, but not installed or rooted.
Click to expand...
Click to collapse
https://mirrorbits.lineageos.org/su/addonsu-14.1-arm64-signed.zip
Related
As Cyanogen pulled the plug on CyanogenMod, this project will continue under Lineage OS
{
"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"
}
This ROM is Alpha and not ready for daily use at the moment
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community
First I would like to thank the following developers :
@RaymanFX
@CTXz
I used @RaymanFX's T815 image to base my cm 13.0 build on, which in turn is the base of this cm-14.1.
Before you start
THIS ROM IS ONLY FOR THE SM-T810
Code:
*
* Your warranty will be voided !
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
About the ROM
Current state of ROM : testing
Everything except what's reported below is working (or not yet reported as not working).
What is Fixed
In '20-09' build reboot to recovery triggers message 'Factory reset'. (wrong messagem not resetting)
Camera not working in selinux enforcing
Front facing camera unable to save image
Bluetooth not working
Hardware codecs not working (fallback to software for mp3/flac works)
Limited wifi 5GHz support (channels above 100 give issues)
Video recording not working? (not tested on T810, reported not working on T815)
What is not working
Important
Fingerprint scanner not working
Minor
Compass is 180 degrees mis-aligned
Mic not working (no input routing)
Instructions
How to install CM13.0
If you haven't run stock Android 6.x, flash that first with odin. (image won't boot without this step)
If you don't have TWRP yet, get it from here : TWRP by ashyx
Download the ROM and the Gapps that are located below to your device
Reboot into TWRP by holding VOL UP + POWER + HOME on boot
In case things go wrong make a backup
After the backup has completed return to home and select Wipe and then Advanced Wipe
Now ONLY tick Dalvik Cache, System, Data and Cache
After ticking those, Swipe below to wipe
Once the wipe has completed return to home and select the ROM
After you selected the ROM swipe below to install it
After the ROM has installed flash the Gapps
When all of this is done, reboot into system, wait, and enjoy CM12.1
How to ROOT
In CM 14.1 Enable the developer options
Select Root access
Select Apps Only
Done
Questions and bug reporting
The following questions will be ignored
Inappropriate questions
Forced orders, EX. : "PLS FIX!!!!!!"
ETA's
Often repeated questions usually by the same user
Requests that are out of CM's framework (Ex. Adding Samsung Apps)
How to report a bug/issue
Explain exactly what happens
Mention a log if you can (Please use hastebin or any other paste site to keep the thread clean)
If you can't mention a log, explain as precise as possible when, why and where it occurs!
Changelog
Code:
**********
08-12-2016 - Compile with curren cm-14.1 source and [URL="https://review.cyanogenmod.org/#/c/173951"]this patch[/URL].
**********
25-11-2016 - Cm-14.0 is abandoned upstream, limiting uploads to cm-14.1.
- Recompile with camera fix merged in cm sources.
**********
21-11-2016 - Fixed camera (again).
**********
20-11-2016 - Broke camera in enforcing mode (unable to save picture).
**********
17-11-2016 - Recompile from clean tree, camera and youtube work now.
- Confirmed lock-screen-rotate fixed, but only after clean flash and [b]no restore of device ID[/b].
**********
14-11-2016 - First succesful cm-14.1 boot. (Switched project to cm-14.x)
**********
31-10-2016 - Selinux set to enforcing.
**********
12-10-2016 - Disabled telephony that got included regardless specifying I don't want it.
- Fixed several bluetooth issues
- Removed use of old api (v1) by camera
**********
03-10-2016 - First build with cm-14.0 release (previous were staging builds)
- Fixed bluetooth
**********
25-09-2016 - Fixed selinux contexts for camera so it works in enforcing mode
- Fixed front facing camera so it is able to save images.
**********
22-09-2016 - Reboot to recovery now triggers correct message
- 2nd build selinux permissive.
**********
20-09-2016 - 1st cm-14.0 build
**********
Downloads
Latest CM 14.1 build : https://www.androidfilehost.com/?fid=673368273298915423
All CM 14.1 releases can be found here : https://www.androidfilehost.com/?w=files&flid=128488
Recommended GAPPS by opengapps.org : http://opengapps.org/ (I use pico)
Source
Special Thanks to @RaymanFX for releasing his Exynos 5433 source, and already patching the common sources to cm-14.0, without him this ROM would most likely not be possible!
All my sources can be found here : https://github.com/CyanogenMod/android_device_samsung_gts210wifi
Screenshots
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
XDA:DevDB Information
CyanogenMod 14.1 for Tab S2 9.7 wifi, ROM for the Samsung Galaxy Tab S2
Contributors
T_I, Raymanfx, CTXz
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock Android 6.x flashed at least once before install
Based On: Cyanogenmod
Version Information
Status: Alpha
Created 2016-09-22
Last Updated 2016-12-29
Nice! Thank your very much for this early build!
I will try it as soon as I am able.
Sent from my SM-T810 using XDA-Developers mobile app
GO hard brother, thanks for all your efforts!
I've been using cm-14 since the 20-9 build, it's running pretty stable, although it's even more stable with selinux in permissive. Looks like some contexts have changed a bit in cm-14. (or the camera and some other routines ignore them)
I found 1 game not playing nicely with Nougat, CSR Classics, but the racing set from CSR work nicely, so I think that's a CSR related bug.
Fixed camera so it'll work in selinux enforcing (not yet activated) and front facing camera is able to save images.
Updated OP.
Awesome thank you!
@T_I Thought you might like 2 comments re your really great adaptation of CM14. Have been using your CM13 nightly downloads for about the last 5 weeks on my T810 and was so pleased with the result that I was slightly hesitant about trying CM14, however this afternoon I took the plunge and installed it as per your instructions. First impression is that I can hardly believe how problem free the installation of the Rom and the Open Gapps 7.0 pico proved to be.
I don't have a huge number of apps installed, about 30, but with one exception they are all performing as scheduled and I couldn't be more pleased, the one app that doesn't work is "Set CPU", there is no "forced closure", no error message, it just doesn't work. There are no forced closures of any other app including the Google Play & Services.
One point which might interest you as you mentioned it in your "OP" notes. I play mp4 movies using the app "MX Player Pro" with the Arm 7 codec installed and they play using the HW+ codec perfectly,
Was initially disappointed that "Theme Chooser" was missing from "Settings" but I can live with that considering how well everything else performs.
Once more congratulations on a really superb "port".
EDIT on 09.27.... @T_I I know this point is insignificant and pure "eye candy" but I love the touch ..... I'm talking about when one connects a usb connection from PC to S2 then the "icon" displayed at top left is now "N" (for Nougat ?) instead of the normal CM icon.
planning to attempt with the t710 again?lol
NalNalas said:
I've had this flashed since last night, and the battery so far has been great. Thanks a ton for this.
Click to expand...
Click to collapse
How much better would you say the battery life has been?
Would also appreciate input from anyone else whos noticed a difference (good or bad) with the battery life.
This ROM is working great so far!!
samsung_xoom said:
planning to attempt with the t710 again?lol
Click to expand...
Click to collapse
I can run a cm-14 build for T710 to see if that one boots.
I can test it and let you know , in my limited time I have lol
This rom is very stable, fast and reliable. The battery life is excelent. I use it as my daily driver since sept. 22!!! (Now i have a sept. 27 update)
Thanks T_I for your hard work!!!
Uploaded new image. @RaymanFX got bluetooth working on his device and the fix works on T810 as well. Also CM switched cm-14.0 from staging to release. There is still work to be done, but build shows working bluetooth (at least I can connect a keyboard and that one works).
I noticed crashing phone app and saw one ExchangeServices crash. (don't use both) Updates OP.
Latest build works wonders after I deleted from /system/app and /system/priv-app all the apks related to telephony/SMS/MMS/etc. for my T810.
EDIT: After some time, it all came crashing down, Play Services didn't like the removal of the packages, and some apps auto-removed themselves. Better wait until dev ships out another build.
Just tried to install the Oct 3 version of this ROM and as soon as it boots a box appears saying "com.android.phone has stopped". No matter how many times I click OK, the message just reappears and I can't get past it. Even have to use the power-home-vol- button combination to power off. This is on a T810 after full wipe, install ROM and install 7pico gapps. Tried the install three times. Coming from cellular south 6 ROM.
Please don't forget T710....
lewmur said:
Just tried to install the Oct 3 version of this ROM and as soon as it boots a box appears saying "com.android.phone has stopped". No matter how many times I click OK, the message just reappears and I can't get past it. Even have to use the power-home-vol- button combination to power off. This is on a T810 after full wipe, install ROM and install 7pico gapps. Tried the install three times. Coming from cellular south 6 ROM.
Click to expand...
Click to collapse
I got the same message, but can mute. Don't know where it comes from. I was working on the staging version of cm-14 and switched to the release version. Looks like there are some bugs left. (it's now less stable then with the staging cm-14)
T_I said:
I got the same message, but can mute. Don't know where it comes from. I was working on the staging version of cm-14 and switched to the release version. Looks like there are some bugs left. (it's now less stable then with the staging cm-14)
Click to expand...
Click to collapse
Just by clicking the OK button? Message just pop right back up when I do that.
lewmur said:
Just by clicking the OK button? Message just pop right back up when I do that.
Click to expand...
Click to collapse
I get the message with the 2 options 'stop application' and 'Mute until reboot'. The Mute option silences the warnings, but the app will still misbehave.
Exchange services I've been able to freeze, the phone app is also used for syncing contacts and I think calendar.
{
"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
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
{
"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...
What is R?
Our release of Android 11, titled CR-9.0.
It provides you with the features you need while keeping the focus on delivering an elegant, smooth, and well polished experience. R delivers a set of unique features, like a system-wide font engine that also allows for applying fonts on user apps while supporting user fonts through custom APKs generated on fonts.carbonrom.org. We are confident you'll love it, and there's many more things to discover
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! As always, make sure to do backups.
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 addressed it already. Especially if you're even close to new at this.
2) 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.
3) Join our Discord server or Telegram group! 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.
Install Instructions:
You should start off with the latest Android 11 OxygenOS stable build on both slots and then proceed to flash Carbon.
The easiest way to do that is by installing the latest Version and then copy it by flashing the copy-partitions script made by LineageOS in the recovery. (See install Instructions for the recovery)
The recommended way to install is using the CarbonRecovery linked below.
Download the ROM and optionally GApps, reboot to recovery by flashing the boot.img using
Code:
fastboot flash boot fajita-YYYYMMDD-HHMM-boot.img
followed by booting to recovery through the bootloader.
Sideload the ROM. (Apply Update -> Apply from ADB -> Connect to PC ->
Code:
adb sideload CARBON-CR-9.0-R-WEEKLY-fajita-YYYYMMDD-HHMM.zip
Reboot recovery (to switch between slots)
Flash GApps/MicroG through sideload like above (optional)
Factory reset -> Format data/factory reset (Make sure to have a backup of your data)
Done
Followup builds can be updated through the builtin CarbonDelta Updater or by dirtyflashing.
Download
Download CarbonRecovery
Homepage
Join the CarbonROM Discord server
Meet us on Telegram
GitHub
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!
FINALLY! YES! WOOHOO!
I just want to confirm based on the top post, that for the 6T we are indeed using the A10 base since that is still the "Latest Stable Build"?
Void4ever
void4ever said:
I just want to confirm based on the top post, that for the 6T we are indeed using the A10 base since that is still the "Latest Stable Build"?
Void4ever
Click to expand...
Click to collapse
Indeed, the current required base is the latest Android 10 stable.
Thx @Myself5 I appreciate the info. Hopefully I don't run into the same Android Auto issues I did with 8.0. However to be 100% fair I ran into those issues with multiple other roms as well. Something to do how OxygenOS handles the detection of USB vs ASOP I assume on the 1+ hardware. Literally the only thing thats kept me from running custom roms.
Found and fixed the issue with video playback in Apps. New builds coming within the next 2 hours.
void4ever said:
Thx @Myself5 I appreciate the info. Hopefully I don't run into the same Android Auto issues I did with 8.0. However to be 100% fair I ran into those issues with multiple other roms as well. Something to do how OxygenOS handles the detection of USB vs ASOP I assume on the 1+ hardware. Literally the only thing thats kept me from running custom roms.
Click to expand...
Click to collapse
I havn't had issues with Android Auto in the VW Discover Pro on any devices so far. Unfortunately the only car I can test it with, and the Emulator is working fine as well. If it's still broken for you I'd greatly appreciate if you can provide logs of the issue and I'll try to take a look
Myself5 said:
Found and fixed the issue with video playback in Apps. New builds coming within the next 2 hours.
I havn't had issues with Android Auto in the VW Discover Pro on any devices so far. Unfortunately the only car I can test it with, and the Emulator is working fine as well. If it's still broken for you I'd greatly appreciate if you can provide logs of the issue and I'll try to take a look
Click to expand...
Click to collapse
I would be happy to provide logs if/when i run into an issue.
I can give some background right now, which may not be very useful since we don't know if 9.0 is going to have the same issue. I don't recall if it was you @Myself5 or the dev from Paranoid, but we had a short discussion about this a while ago. If I recall one of you suggested it might be the modules you were using from the ASOP libs maybe? I'd have to go search through the old threads.
The only car I have to test with is my 2019 Traverse. AA works perfect everytime with stock Oxygen, and the only other ROM I ever ran into that seemed to work fine was AOSIP, however the rom itself was unstable on my hardware and I had to remove it due to my alarm not going off cuz the phone would crash overnight. So perhaps there's something in the way they implemented USB detection.
The last rom I tested (I forget which) I noticed that the phone wasn't even popping up the USB notification (where you can select File Transfer, USB tethering, MIDI, PTP, No data transfer) when connecting to the car.
Anyways this is far more info than we need until I can test it. Hopefully this weekend if not sooner.
Bit rusty running custom Rom
I was able to install perfectly fine, running perfectly just a bit iffy on Rooting afterward.
Can we install Magisk through CarbonRecovery? Do we need to keep the Carbon Recovery as the defacto Recovery for this Rom? Can I go back TWRP?
Mckillagorilla said:
Bit rusty running custom Rom
I was able to install perfectly fine, running perfectly just a bit iffy on Rooting afterward.
Can we install Magisk through CarbonRecovery? Do we need to keep the Carbon Recovery as the defacto Recovery for this Rom? Can I go back TWRP?
Click to expand...
Click to collapse
Yes you can install Magisk through Carbon Recovery. TWRP should be just fine, especially as the Recovery isn't used for updates etc as that is all done through Seamless updates in CarbonDelta on the system itself.
When i installed the rom i had to install the gapps after i was done with the phone setup. Otherwise the Android Setup would crash as soon as android booted.
The screen would then go cracy (blinking button icons) and I couldn't do anything.
I also can't update using the ota update.
Just tells me "Update could not be installed".
Other than that it works great
Edit: I didn't see the message about the video playing fix in some apps.
Updated from to latest version and now all videos work
Myself5 said:
Found and fixed the issue with video playback in Apps. New builds coming within the next 2 hours.
I havn't had issues with Android Auto in the VW Discover Pro on any devices so far. Unfortunately the only car I can test it with, and the Emulator is working fine as well. If it's still broken for you I'd greatly appreciate if you can provide logs of the issue and I'll try to take a look
Click to expand...
Click to collapse
Thank you for this great rom .
I had a problem with Android Auto, It's solved but I report if someone faces the same issue.
With Nikgapps basic on cr-9.0, Android Auto was not working: the phone was detected by the car (Peugeot 2008 from 2018), but when I initiated the connection the phone hangs and freeze, nothing happens on the car and I often had to reboot the phone.
It was an error related to usb permission in the logs.
It was solved using the stock package of Nikgapps (the problem is reported on other other devices as well). I was using the basic package of nikgapps on carbonrom cr-8.0 without problem, I don't know what changed that made the stock package needed.
I did not try for other gapps providers, but at first glance, this problem doesn't seems related to the rom itself but more to the gapps package.
My facebook and insta videos r not playing.. can't able to see them .. how to fix it
Prabhuraj 0 said:
My facebook and insta videos r not playing.. can't able to see them .. how to fix it
Click to expand...
Click to collapse
By updating to the latest build as mentioned a few posts above yours.
On that note:
I've found and fixed an issue where the device would not be reported as an A/B device properly which resulted in the integrated updater being broken. It will be fixed in wednesdays build (along with August ASBs) but you will need to manually update (through recovery) to that build.
So I haven't had a chance to install because I had to be OnCall for my job this week, no messing with my phone...... BUT that may have been a blessing?
I see the Stable A11 was released today for the 6 and 6T. Are there plans to rebase Carbon 9.0 to this?
Void4ever
Solid ROM! I haven't used Carbon since the Epic 4g phone. I'm running latest without Gapps, and I have to ask is there a better camera available outside of the play store? I know its a long shot but thought I'd try.
Google Camera, just google up gcam ports
only reason fr nt using Carbon is there is no
face unlock
Why is there no new download link from 25/8 for fajita. I can see the update on my phone but I want to flash the update.zip file from recovery.
Thanks
Wishmasterflo said:
Why is there no new download link from 25/8 for fajita. I can see the update on my phone but I want to flash the update.zip file from recovery.
Thanks
Click to expand...
Click to collapse
The last version also took a while (~4-7 days, not sure) until it was available on the website
I see it now. Probably didn't wait long enough!
Also @Myself5 is this by chance based on A11 now, or still A10?
{
"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"
}
Havoc-OS 4.x is based on AOSP, inspired by Google Pixel.Has a refined Material Design 2 UI crafted by @SKULSHADY.Many useful features that provide a smooth premium experience.Just flash and enjoy...
Founder & Lead Developer:SKULSHADY (Anushek Prasal)DevOPS & Scaling:Irongfly (Sukeerat Singh Goindi)
If you like our work and would like to support this project then please consider donating.
PayPal: https://www.paypal.me/ANUSHEK
UPI: [email protected]
Download ROM: https://havoc-os.com/device#sofiar
About Havoc-OS: https://havoc-os.com
Recovery: Vache's unofficial TWRP
Magisk: https://github.com/topjohnwu/Magisk/releases
FlameGApps: https://flamegapps.github.io/
Official Havoc-OS Telegram Group: https://t.me/havocofficial
Official Rav/Sofia-R-P Havoc-OS Telegram Group: https://t.me/+ioAiJwr1DKZiMjJl
Havoc-OS Announcements Telegram Channel: https://t.me/Havoc_OS
Code Review: https://review.havoc-os.com
1. Download the ROM, GApps (Optional), Magisk (Optional) from the links above.
2. Wipe System, Data, Dalvik, Cache.
3. Flash the ROM, GApps (Optional), Magisk (Optional).
4. Reboot and Enjoy.
LineageOS (https://github.com/LineageOS)
Crdroid (https://github.com/crdroidandroid)
Pixel Experience (https://github.com/PixelExperience)
And all the other Developers, Testers, Donators and Users.
https://github.com/Havoc-OS
https://github.com/Havoc-Devices
Known Issues
• FM Radio doesn't work
• USB tethering doesn't work on first boot
• Must use android 10 vendor like other sofiar roms
• Android Auto doesn't work on android 10 vendor
• Stylus actions dies between reboots, just open it within settings
Havoc-OS, ROM for Rav/Sofia-R-P(commonly shortened to sofiar)
Devices: Sofiap (Moto G Stylus/G Pro), Sofia/Sofiar (Moto G Power/G⁸ Power), and Rav (Moto G⁸/G Fast)
Maintainer: ph4n70m
Build Type: Official
Credits
- Vache: The initial device and vendor tree
- Beetle84: Giving me a ton of help
Any plans to fix FM radio?
Leroy_Sparks said:
Any plans to fix FM radio?
Click to expand...
Click to collapse
Yeah I'll attempt a few things to try and fix it, worse case scenario I'll just remove it.
Keeping an eye on your releases. If you manage to fix FM radio I'll be making the jump immediately. Glad to see some development resume for this device!
xStealth said:
Keeping an eye on your releases. If you manage to fix FM radio I'll be making the jump immediately. Glad to see some development resume for this device!
Click to expand...
Click to collapse
Theres been development just mostly on the telegram, currently FMRadio works on my corvus build but that is also SELinux Permissive, although its not the best solution you can likely get it to work on any rom by setting the rom to SELinux Permissive.
Funciona no a02s?
ph4n70m-404 said:
Theres been development just mostly on the telegram, currently FMRadio works on my corvus build but that is also SELinux Permissive, although its not the best solution you can likely get it to work on any rom by setting the rom to SELinux Permissive.
Click to expand...
Click to collapse
Yeah, I've been watching the Telegram. I'd been waiting on an update from Beetle but it appears they've stopped development on this device. I'd been using their most recent for over a month when suddenly Android system started using tons and tons of battery for no apparent reason so I shelved the phone and went back to my old one while waiting.
ph4n70m-404 said:
Theres been development just mostly on the telegram, currently FMRadio works on my corvus build but that is also SELinux Permissive, although its not the best solution you can likely get it to work on any rom by setting the rom to SELinux Permissive.
Click to expand...
Click to collapse
I installed Arrow to get FM radio (had been on Beetle's havoc before that). I'd like to have the radio but I do like havoc better. One thing I've encountered on the arrow ROM is a lot of stations have distorted audio (not all), even ones that usually have great reception on an old htc phone. I wonder if the moto radio is maybe not the greatest? Anyone notice similar? (I never tried fm radio while I had oem ROM).
Thanks for the work on this ROM. I've been using Beetle84's build of Havoc 4.8 and I figured this might be the best place to post about bugs, since the other thread is now labeled "discontinued"? I'll probably post this there too. I'm gonna install your 4.10 build soon regardless. Here are some bugs I found that are possibly still present in your build:
Ambient display is a little buggy. Trying to enter your PIN from the ambient display will suddenly hide the keypad and show the regular lock screen. If you do this quickly, this will all happen and also the screen will turn off (probably because tap to wake/sleep or whatever is enabled too)
Metadata doesn't update normally when listening to audio via Bluetooth. My car will just display the metadata for the first song until it randomly switches to a new song like 10 songs later, and be stuck on that song for a while too.
I put my phone on airplane mode a lot, and sometimes when I take it off, it doesn't receive texts until I enable and disable airplane mode again. Sending texts, using data, and sending/receiving phone calls still all work during this time, as far as I can tell but I haven't tested thoroughly yet. I have US Mobile using Verizon's network if that helps.
When I boot the phone (either cold boot or restart), there is a period between the time the phone is on and the time I've entered my password to "log in". During that time, I technically receive texts, but android deletes them automatically and there's no trace of ever having received them. This is an especially bad bug as it was difficult to even know it was happening. I was told by multiple people that I never responded to a text, when in reality I never saw it. Took forever to figure out what conditions were actually causing me to not receive them. My temporary solution to this is to always put the phone on airplane mode if I ever have to turn it off, because that way I'll have already logged in before I connect to the network.
Hotspot does not work, just immediately turns back off after turning it on
If this isn't the right place to post about bugs, I apologize. I had been using Havoc on this phone for about a month and only made this account to make this post.
Edit: Should probably mention which phone I am using: it's Moto G Power 2020 (sofia)
Thanks dude for ur work! UwU
luke.leheny said:
Thanks for the work on this ROM. I've been using Beetle84's build of Havoc 4.8 and I figured this might be the best place to post about bugs, since the other thread is now labeled "discontinued"? I'll probably post this there too. I'm gonna install your 4.10 build soon regardless. Here are some bugs I found that are possibly still present in your build:
Ambient display is a little buggy. Trying to enter your PIN from the ambient display will suddenly hide the keypad and show the regular lock screen. If you do this quickly, this will all happen and also the screen will turn off (probably because tap to wake/sleep or whatever is enabled too)
Metadata doesn't update normally when listening to audio via Bluetooth. My car will just display the metadata for the first song until it randomly switches to a new song like 10 songs later, and be stuck on that song for a while too.
I put my phone on airplane mode a lot, and sometimes when I take it off, it doesn't receive texts until I enable and disable airplane mode again. Sending texts, using data, and sending/receiving phone calls still all work during this time, as far as I can tell but I haven't tested thoroughly yet. I have US Mobile using Verizon's network if that helps.
When I boot the phone (either cold boot or restart), there is a period between the time the phone is on and the time I've entered my password to "log in". During that time, I technically receive texts, but android deletes them automatically and there's no trace of ever having received them. This is an especially bad bug as it was difficult to even know it was happening. I was told by multiple people that I never responded to a text, when in reality I never saw it. Took forever to figure out what conditions were actually causing me to not receive them. My temporary solution to this is to always put the phone on airplane mode if I ever have to turn it off, because that way I'll have already logged in before I connect to the network.
Hotspot does not work, just immediately turns back off after turning it on
If this isn't the right place to post about bugs, I apologize. I had been using Havoc on this phone for about a month and only made this account to make this post.
Edit: Should probably mention which phone I am using: it's Moto G Power 2020 (sofia)
Click to expand...
Click to collapse
Okay so I've tested your 4.10 build and pretty much all of these bugs are gone. Ambient display is still a little weird when trying to unlock but I tested on another phone and it seems like a Havoc OS bug rather than a bug with this build/phone. Haven't had a chance to check the bluetooth audio one yet. But the last 3 on this list all seem to be resolved by this build.
Decided to give this a go because I was having untold amounts of problems with your Lineage build and getting GApps to work. Zero issues on the first install and everything is good. Other than radio not working, everything else seems to be just fine. I'll be sticking with Havoc.
xStealth said:
Decided to give this a go because I was having untold amounts of problems with your Lineage build and getting GApps to work. Zero issues on the first install and everything is good. Other than radio not working, everything else seems to be just fine. I'll be sticking with Havoc.
Click to expand...
Click to collapse
Yeah LOS is having lots of issues with GApps lmao, I've been told a possible fix and i might try doing GApps included builds but im waiting for when I have a decent amount of time to try some of these. I did a Corvus build that has FMRadio fixed but thats only because Corvus is in SELinux Permissive and as i mentioned before you can likely fix FMRadio on every newer rom by setting it to SELinux Permissive via a magisk module.
@ph4n70m-404 I'll be keeping an eye to see if you somehow manage to fix the radio without having to go permissive. While radio isn't the most important of things, it's just a nice thing to have in case service goes down or I'm in the middle of nowhere.
Just wanted to add, overnight I only lost about 1.5% battery during idle (GApps version on 2.4GHz WiFi) in around 10 hours. That's absolutely astounding! Beetle's build did that to begin with, but after a few months Android System began to chew through battery nonstop. Excellent work!
I have a Moto G8 Power 2020 (XT02041-4), and I flashed Beetle84's Havoc ROM the day I received it. I've used it for several months. Initially, the battery life was great, but I recently found that I was getting slightly more than one day. Some on this forum associate it with Android apps, but I've had essentially the same apps installed from day 1.
So, I decided to install a new ROM and selected LineageOS 18.1 (LOS18), with which I'm very familiar. However, I couldn't install GAPPS regardless of the GAPPS I selected. Also, something weird troubled me. I was running TWRP 3.5.0_10-0 and tried to flash TWRP-3.5.0-0-rav-sofia.img which the OP of the LOS18 suggested. I flashed it in TWRP seemingly successfully, but TWRP 3.5.0_10-0 was still installed .when I rebooted Recovery. I thought I had screwed everything up and used the Lenovo Rescue Tool to flash the stock ROM.
But then I discovered this thread, and decided to go back to Havoc by flashing this ROM. However, although the OP suggests initially wiping System, Data, Dalvik, Cache, System is not available when I do an Advanced Wipe. So, I used the Lenovo Rescue Tool and flashed the stock ROM again.
That's where I am, and I'd appreciate some guidance with this. Much appreciated. Thanks
Any chance this will go to version 5.x? Would be nice to keep this going, but I don't now if Havoc is planning on putting A12 on this device.
jhford said:
I have a Moto G8 Power 2020 (XT02041-4), and I flashed Beetle84's Havoc ROM the day I received it. I've used it for several months. Initially, the battery life was great, but I recently found that I was getting slightly more than one day. Some on this forum associate it with Android apps, but I've had essentially the same apps installed from day 1.
So, I decided to install a new ROM and selected LineageOS 18.1 (LOS18), with which I'm very familiar. However, I couldn't install GAPPS regardless of the GAPPS I selected. Also, something weird troubled me. I was running TWRP 3.5.0_10-0 and tried to flash TWRP-3.5.0-0-rav-sofia.img which the OP of the LOS18 suggested. I flashed it in TWRP seemingly successfully, but TWRP 3.5.0_10-0 was still installed .when I rebooted Recovery. I thought I had screwed everything up and used the Lenovo Rescue Tool to flash the stock ROM.
But then I discovered this thread, and decided to go back to Havoc by flashing this ROM. However, although the OP suggests initially wiping System, Data, Dalvik, Cache, System is not available when I do an Advanced Wipe. So, I used the Lenovo Rescue Tool and flashed the stock ROM again.
That's where I am, and I'd appreciate some guidance with this. Much appreciated. Thanks
Click to expand...
Click to collapse
I'm the same builder as los one, the twrp image is just the same vache one everyone recommends so you just reinstalled the same twrp, los has been weird with getting gapps working so I've been trying to resolve that. The install instructions are just the ones the rom provides for their template and should really just be loosely followed, the only reason i dont change those is because i would probably write way too much about the install process and possible fixes to issues like the fact you should be on stock a10 before flashing when i and others provide far better support on telegram.
My advice is to use the vache moto flash tool, grab the firmware from lolinet, and flash back to stock a10, then after you make sure stock is working and everything install the twrp, wipe the data using wipe - format data on twrp, then proceed to just flash the rom via twrp.
JPutz said:
Any chance this will go to version 5.x? Would be nice to keep this going, but I don't now if Havoc is planning on putting A12 on this device.
Click to expand...
Click to collapse
No clue on Havocs plans for a12, this isn't official so it isn't havoc's decision if it gets put on this device or not, after there is a good a12 tree for this device that's stable and havoc releases stable 12 then yes most likely.
ph4n70m-404 said:
No clue on Havocs plans for a12, this isn't official so it isn't havoc's decision if it gets put on this device or not, after there is a good a12 tree for this device that's stable and havoc releases stable 12 then yes most likely.
Click to expand...
Click to collapse
That's cool. I am happy where I am at. Rock stable and works flawlessly. I just think it is cool that I have a phone this old and it has recent updates on a custom rom.
I still say this should be stock. I had to redo my phone back to factory (flashed the update to the wrong slot. Oops!) and the stock rom was so annoying. I though I just hated iOS and the Samsung roms.