{
"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.
Related
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
{
"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
YAPR [YET ANOTHER PIE ROM]
{
"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"
}
ABOUT
ArrowOS is an AOSP/CAF based project started with the aim of keeping things simple, clean and neat.
Website: https://arrowos.net
Telegram: Channel | TG Portal/Links
Github: https://github.com/ArrowOS
Code Review: review.arrowos.net
E-mail: arrowos.contact
PayPal: Click here (read more on our website)
Checkout more documentation at (maintainership/contributing): Check this out
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
You tell me
Be sure to include a log : check how to
DOWNLOADS
ROM:
ArrowOS 9.x
Arrow-v9.0-axon7-UNOFFICIAL-20191117
LATEST Arrow-v9.0-axon7-UNOFFICIAL-20200126
Gapps: Click Here for GApps
Note : Pico, Nano or Micro Gapps are recommended.
ROM Source: https://github.com/ArrowOS
--------------------------------------------------------------------------------------------------------------------------------------
Installation :
1. wipe system, vendor, data, cache
2. install ROM
3. GApps, Magisk
4. reboot
Contributors
@raystef66
Credits to
ArrowOS Team
LOS Team
KERNEL SOURCE: https://github.com/OrdenKrieger/andr...el_zte_msm8996 thnx @OrdenKrieger
ROM OS Version: 9.x PIE
ROM Kernel: Linux 3.18.x
ROM Firmware Required: Unlocked Bootloader, Latest TWRP Recovery
Based On: LineageOS device, vendor, kernel
Version Information : 9.x
Status: Pure & Stable...afaik
Sec. Patches : 2020.01.05
Created : 2019.10.12
Last Updated : 2020.01.26
Thanks Raystef66, I'm using this ROM as of tonight. I have successfully upgraded from AOSP 6.5 (May) on my A2017 (chinese).
Much smoother and quicker, although that is expected with a new ROM install after so long! I hope to give you more feedback.
Dungeon Maker had issues installing, which i think may be due to CTSmismatch in magisk (v20). I still have not been successful in passing it.
Do you have a kernel recommended? Or which kernel do you have with this ROM?
Thank you for all of your hard work in keeping the Axon7 ROMs active.
darth_antz said:
Thanks Raystef66, I'm using this ROM as of tonight. I have successfully upgraded from AOSP 6.5 (May) on my A2017 (chinese).
Much smoother and quicker, although that is expected with a new ROM install after so long! I hope to give you more feedback.
Dungeon Maker had issues installing, which i think may be due to CTSmismatch in magisk (v20). I still have not been successful in passing it.
Do you have a kernel recommended? Or which kernel do you have with this ROM?
Thank you for all of your hard work in keeping the Axon7 ROMs active.
Click to expand...
Click to collapse
Install MagiskHidePropsConfig and Busybox and run "props" via terminal and choose f.e. the axon7 oreo FP. You'll pass cts. I run magisk 20.0 and all ok.
I suggest installing the RC1.2 kernel which you can find HERE.
In my next build I was planning to take that one within the ROM. But you can install it without probs tho
Btw, picture below is on new crDroid but MHPC should give u the same results on ArrowOS
Thanks Ray, I appreciate your reply and knowledge of this.
The app updated and worked without needing the ctsmismatch pass, so i'll just wait for your update.
In the 3 days since I've been using this ROM, I can appreciate the following coming from AEX 6.5. A freshly installed ROM does have some of these benefits so I'm probably biased.
1. Arrow has a faster boot into the rom. the loading screen is awesome and the loading effect is great.
2. Arrow uses half as much ram, 1.7gig compared to 3.2gig. This is probably a fresh install thing though, as i have a lot less apps now.
3. quicker and cleaner.
Thanks, the only thing i hope you have in future builds is the cts, and the option for when you reset the phone, there are the extra options to boot into recovery.
*found this option under 'buttons' in the android menu, apologies.
Ive been using this for a month now and its been awesome.
The only bug or issue I've had is the dictionary and auto-correct. Auto-correct does not work at all, and it doesnt recognise mis-spelt words. Android keyboard seems to have limited option.
Thank you for developing this ROM.
NEW ARROW BUILD 2019.11.17
Arrow-v9.0-axon7-UNOFFICIAL-20191117
changelog :
* november sec. patches
* added RC1.2 baddar kernel
* added proper thermal fix
Hi raystef66,
Thank you so much for your great efforts and sharing with this amazing ROM.
The only issue for me is so far - Gesture Typing of AOSP Keyboard is not working.
I have checked its setting to make sure the gesture typing function turned on, but still not working.
Is it experiencing only me? how about other people?
I'm sure that this is an ignorable minor bug for me, otherwise this ROM is finely matured exquisite PIE ROM.
In the next update, however, would you mind adding the advanced settings option?
Thanks again.
BUILD 2019.11.17 First Impressions
Pretty happy with this ROM coming from the most recent (now deprecated) Lineage 15.1 Official Nightly and really loving Arrow.
The only thing I'm missing is the ability to slide finger on status bar to adjust brightness.
I noticed the battery life seems noticeably better. I was hours away from replacing my Axon due to the battery just being horrible, even after being recently replaced. Everything seems buttery smooth besides the Gcam app I'm using. It works, but very sluggish.
Please do recommend your favorite camera app for this ROM.
I'm passing SafetyNet after installing Pixel Android 9 Props.
GPS took over a minute to get a lock the first time around, but now works within 15 seconds as expected.
USB tethering has been temperamental. I disabled hardware acceleration via Developer Settings and it seems to be working better.
I can confirm that swipe texting on AOSP keyboard does not work, however works fine with Gboard.
Hardware keys work as expected however even with the home button Long Press Action set to activate Google Assistant it does nothing. It seems that the Google Assistant action does not work with any of the button settings including the on screen navbar.
I haven't been able to get USB-OTG to work on any ROMs since ditching stock. Maybe someone knows a fix. It doesn't work in TWRP either, so maybe it's my hardware.
Besides a few minor quirks, I am hugely grateful for this ROM providing Pie and rekindling my love for this aging Axon. Thank you!
Swipe typing on the aosp keyboard just means it's missing the libs. Seen it before. Last I checked open gapps aroma let you restore the libs.. But using a different keyboard is a better idea.
Thank you for the update and fixes! Still using this since September.
As above, the keyboard (and in my case, autocorrect doesnt work as well as other roms) is the only thing thats not going so great.
Apart from that, its flawless. Thank you again!
Hi,
Thank you for this very good ROM!
Tested several days, I only noticed a bug in the Google camera with the GAPPS stock. When the application is updated, it stops working.
I also wonder if wifi calls work. Maybe I didn't find the right option to activate them.
(and the GPS sometimes remains blocked at a location and does not update itself).
Everything else is perfect!
Wi-Fi access point and usb modem do not work ....
Wi-Fi access point and usb modem do not work .... sometimes attempts to turn on those options cause a system lock and forced hard reset
PS I turned off hardware acceleration as someone wrote here - USB tethering works ... the problem with the wireless hot spot remains ...
PS2 I don’t know why, but during a 10-kilometer trip, GPS is lost several times, and somewhere near the final destination of the trip, the phone suddenly starts to show the right way this is already becoming a tradition.....
I my location on this ROM i have a problem with conersation. Before i used AOSP 5.7 based on Oreo and in my room i could talk by phone. Acctually i must go to kitchen because only there i can normally talk.
It's look like worse signal or not all bands compatible. My Axon have B20 (it isn't china version). Sometimes i have problem with internet - connecting by LTE isn't possible. When i was in London i couldn't use internet. Phone found transmitter, about 3/5 signal strange but any page or facebook lite no load.
NEW ARROW BUILD 2020.01.26
Arrow-v9.0-axon7-UNOFFICIAL-2020.01.26
changelog :
* Merge branch 'android-9.0.0_r52'
* jan 2020 sec. patches
Thank you for not abandoning our dear Axon 7. Please continue to develop ROMs for him!
Thank you very much for the rom, my Axon 7 is now back to life.
Dark mode isn't forced in other apps, like google photos.
larsky said:
BUILD 2019.11.17 First Impressions
Pretty happy with this ROM coming from the most recent (now deprecated) Lineage 15.1 Official Nightly and really loving Arrow.
The only thing I'm missing is the ability to slide finger on status bar to adjust brightness.
I noticed the battery life seems noticeably better. I was hours away from replacing my Axon due to the battery just being horrible, even after being recently replaced. Everything seems buttery smooth besides the Gcam app I'm using. It works, but very sluggish.
Please do recommend your favorite camera app for this ROM.
I'm passing SafetyNet after installing Pixel Android 9 Props.
GPS took over a minute to get a lock the first time around, but now works within 15 seconds as expected.
USB tethering has been temperamental. I disabled hardware acceleration via Developer Settings and it seems to be working better.
I can confirm that swipe texting on AOSP keyboard does not work, however works fine with Gboard.
Hardware keys work as expected however even with the home button Long Press Action set to activate Google Assistant it does nothing. It seems that the Google Assistant action does not work with any of the button settings including the on screen navbar.
I haven't been able to get USB-OTG to work on any ROMs since ditching stock. Maybe someone knows a fix. It doesn't work in TWRP either, so maybe it's my hardware.
Besides a few minor quirks, I am hugely grateful for this ROM providing Pie and rekindling my love for this aging Axon. Thank you!
Click to expand...
Click to collapse
##############################
1- To enable assistant you have to choose the google app for the default assistant in the default apps settings.
2- I have trsted nearly 80% of all gcam apks, and the best one so far and the newest is Urnyx05 latets version, you can find it here
https://1-dontsharethislink.celsoazevedo.com/file/filesc/GCam_7.3.018_Urnyx05-v2.2-fix.apk
3- Aosp keyboard is a just terrible, just get Gboard.
4- Clean flashing the rom will solve GPS and USB problems, always clean flash.
{
"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 thread is discontinued
Your 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.
Click to expand...
Click to collapse
Features
Floko-specific features:
OmniSwitch included
Switch "Recents" style (now you can choose QuickStep or OmniSwitch as default recents!)
Remove Music Player (install what you like)
Remove "non-free" Font Packages
Disable ADB when gaming mode (optional)
crDroid and LineageOS features:
Network traffic monitor
Switch 4G/LTE icon
Battery bar
Statusbar Quick/Smart pulldown
QS columns
Notification Ticker
Smart Charging
Rounded corners
Style(Theming)
Volume panel customization
Hardware-specific Features
I myself have a XT1541,
Internal: 16GB 2GB RAM
Stable
How to Install
MAKE A BACKUP OF ALL YOUR DATA.
(First time) Wipe Data, System, Cache, Dalvik/ART Cache
Flash ROM, GApps, Magisk(optional), ...
Reboot to System
Enjoy.
Thanks
love. respect. and love.
crDroid
LineageOS
OmniROM
Team
@1indwurm
@TheForce (device maintainer)
Downloads
Sourceforge.net
AFH:
Source Codes
FlokoROM:
device:
device-common:
kernel:
Changelog:
You can see the changelog on your device. Open: Floko Settings → About FlokoROM → Current changelog.
For more info about: FlokoROM:
Reserved
Great Rom im using it its good perfomance i have the 1gb of ram variant
New build: Floko-v3.0-osprey-20200807-UNOFFICIAL
Android-OS Security patch-level: 2020-08-05.
Downloads:
Sourceforge.net
AFH:
New build: Floko-v3.0-osprey-20200916-UNOFFICIAL
Android-OS Security patch-level: 2020-09-05.
Downloads:
Sourceforge.net
AFH:
Once again continued thanks and respect to all of the Developers
I've been running this Rom for a couple of days now on-and-off and it's the first Custom Rom I've ever installed(I've installed loads) that everything works out-of-the-box!
Tested:
Calls/Text/Mobile phone Data/FM Radio/WiFi/WiFi Hotspot/USB tethering/GPS(Google Maps)/Bluetooth to BT Speakers/Push notifications/OTP notifications / Open-Camera saving to SD card/Mp3 Players VLC(Multimedia) and Pulsar saving Playlists.
Have not found anything not working except stock camera saving to SD card.
Great Rom
orangesunshinewalker said:
what a nice rom has so much customizing options sadly on my xt1542 stock camera and other camera apps dont work, the app closes and airplane mode dont work too. What called my attention is that the lastest versions of opengapps arm pico dont work on crdroid and floko so i have to download the 10 of june version that its managed but in others roms like havoc 3.9/3.6 this don't happen. My problem really was that on stock firmware the camera flash stopped working so i switched to a rom (havoc) and worked again fine but in flokorom and crdroid i cant open the camera and the flash is broken too with the airplane mode. I hope i can find a solution thanks for reading
Click to expand...
Click to collapse
Gapps:
I have used OpenGapps pico from 20200925 which worked fine.
Now I use Bitgapps R17 which also is working fine: [ARM][Q] BiTGApps-arm-10.0.0-R17_signed.zip
https://forum.xda-developers.com/android/software/custom-bitgapps-android-t4012165
and Downloads: https://forum.xda-developers.com/showpost.php?p=81060605&postcount=4
---------------------------------
I have searched for camera issues.
I noticed that this is / was a serious issue especially after updating to android-10.
People with several phones and roms have issues - but surely not everyone.
I have read some solutions I will share. I am sure that these will not help in every situation.
But maybe it is worth trying. On my phone I only can use the internal memory for storage.
Solution 1:
Clear camera application data.
Settings >Apps >Camera >Storage >Clear Data
Solution 2: Someone wrote:
I had this problem too, but I solved it. Just for the case that you also like to play around with the developer options, here's what happened to me:
My camera didn't work, the app opened sometimes, but only partially, complained about missing rights of Google Play, which I allowed but which didn't help, in WhatsApp the camera didn't work, too. WhatsApp suggested to reboot (which didn't help). But my flashlight worked.
Then I remembered that I have seen after the update a new control in the developer options, a toggle for sensors to turn them on and off, which I put into my quick settings, enabled them and then deleted them from the quick settings and forget about them. Seems like the camera is a sensor, too, because after I turned this toggle off the camera worked again : )
Hope this helps anybody else!
Solution 3: Another one wrote:
I had the exact same issue. Rebooting phone helped for a little while and was not a very good solution. After I uninstalled snapchat my camera has been working fine for three days now. So it's highly possible snapchat causes the camera to malfunction.
Solution 4: Again someone else wrote:
I found a way to solve this problem, the camera crashes when an app with camera permission tries to access the location and crashes the camera.
Try disabling the camera and location permission for the apps which have both the permissions (i.e, camera & location). Do this for apps one by one and see which apps cause the problem and see whether the camera crashes or not.
In my case I the apps are Snapchat, Instagram and GCam are the apps having permission to Camera and Location. Finally disabling the permission for Insta worked for me. And my camera didn't crash for the past week.
Hope this helps.
I've had no Camera problems using Flokorom/crDroid etc on my xt1541 1gb ram/8gb.
I always do an ultra clean/safe install of new roms. If the present rom being used has been rooted using Magisk I had problems installing different roms until I started using the system below e.g uninstalling Magisk root before installing the new Rom.
Open Magisk in current booted phone.
Choose uninstall Magisk > Restore Images.
Reboot phone and check phone is not rooted,
https://play.google.com/store/apps/details?id=com.clivin.rootchecker&hl=en_GB
Reboot to Recovery > Factory wipe.
Install new rom > Wipe Dalvik/Cache and then Factory wipe again.
Install Gapps if required and then Factory wipe again.
By doing this I've always had good installs.
HTH
R1ffR4ff said:
I've had no Camera problems using Flokorom/crDroid etc on my xt1541 1gb ram/8gb.
I always do an ultra clean/safe install of new roms. If the present rom being used has been rooted using Magisk I had problems installing different roms until I started using the system below e.g uninstalling Magisk root before installing the new Rom.
Open Magisk in current booted phone.
Choose uninstall Magisk > Restore Images.
Reboot phone and check phone is not rooted,
https://play.google.com/store/apps/details?id=com.clivin.rootchecker&hl=en_GB
Reboot to Recovery > Factory wipe.
Install new rom > Wipe Dalvik/Cache and then Factory wipe again.
Install Gapps if required and then Factory wipe again.
By doing this I've always had good installs.
HTH
Click to expand...
Click to collapse
Thanks for your info, very helpful.
That's where I later thought off. I myself always have a clean install changing roms.
But then again, I have also read about camera-issues. Can be very annoying.
TheForce said:
Thanks for your info, very helpful.
That's where I later thought off. I myself always have a clean install changing roms.
But then again, I have also read about camera-issues. Can be very annoying.
Click to expand...
Click to collapse
I'm running Flokorom as my fave now as it's given me no problems using previous clean install procedure
Still can't save photos to SD card with stock Camera but that's no deal-breaker for me.
Again excellent/superb work by you and the the team.
I do hope there's an Android 11 version soon
R1ffR4ff said:
I'm running Flokorom as my fave now as it's given me no problems using previous clean install procedure
Still can't save photos to SD card with stock Camera but that's no deal-breaker for me.
Again excellent/superb work by you and the the team.
I do hope there's an Android 11 version soon
Click to expand...
Click to collapse
According to developer: FlokoROM Version 4 will come in winter.
TheForce said:
According to developer: FlokoROM Version 4 will come in winter.
Click to expand...
Click to collapse
It should be based on Android Go right? Due to google's policy. I used to have stock pixel android GO 8.1 on Osprey and it was great.
@VelcronSpecter said:
It should be based on Android Go right? Due to google's policy. I used to have stock pixel android GO 8.1 on Osprey and it was great.
Click to expand...
Click to collapse
FlokoROM is based on crDroid, which is lineage based.
Bad news. I've had to abandon Flokorom. Just did a soft reset e.g hold in power button for around 10/15 seconds until the the phone restarts which emulates taking the Battery out and the phone booted but became unusable. All icons from Notification bar disappeared until I rebooted a couple of times but phone still unusable as the,"Settings" app keeps crashing
Tried Safemode and same there. Clearing Cache etc from Recovery no good. Re-tried Soft Reset still no good. As I consider this operation important it's a,"Deal Breaker" for me on this rom
Back to crDroid and Havoc for now
R1ffR4ff said:
Bad news. I've had to abandon Flokorom.
Back to crDroid and Havoc for now
Click to expand...
Click to collapse
Bad news indeed. I will ask the developer for info.
I hope the phone is working again, with another rom.
TheForce said:
Bad news indeed. I will ask the developer for info.
I hope the phone is working again, with another rom.
Click to expand...
Click to collapse
Thank you for your concern but as I keep my Nandroids on my portable formatted SD card(and backed up on my Laptop) so it only takes a few mins to re-install. Get the developers to try a,"Soft Reset" and see what they get as they can then generate a crash log with luck
orangesunshinewalker said:
Happened the same but i can enter to my phone normaly just all the configurations i did like notification bar, lockscreen customanimation, 24h clock, battery bar all reset to default don't know why... my settings are working fine but i had to configure all again.
Click to expand...
Click to collapse
Thanks for testing and posting back
I've had problems with some Custom roms using a,"Soft Rest" whereby the system App stops so I cannot enter the settings(FlokoRom) and on others similar to you whereby I can use the Settings to reset anything that has got wiped.
I can live with it using my Nandroid backups
R1ffR4ff said:
Thanks for testing and posting back
I've had problems with some Custom roms using a,"Soft Rest" whereby the system App stops so I cannot enter the settings(FlokoRom) and on others similar to you whereby I can use the Settings to reset anything that has got wiped.
I can live with it using my Nandroid backups
Click to expand...
Click to collapse
Hi, I have asked the developer for a reaction about the issue of emulating a soft reset.
"I've never heard it before. that's strange..." : was his answer.
I myself tried it on crDroid-ten: I got the following 'problem'. All my apps crashed iow they fc. I had to make a dirty install, then all was fine again.
I don't think I will do it again, I get no profit of it.
TheForce said:
Hi, I have asked the developer for a reaction about the issue of emulating a soft reset.
"I've never heard it before. that's strange..." : was his answer.
I myself tried it on crDroid-ten: I got the following 'problem'. All my apps crashed iow they fc. I had to make a dirty install, then all was fine again.
I don't think I will do it again, I get no profit of it.
Click to expand...
Click to collapse
Did you not have a Nandroid backup you could have used?
It's strange as it works as it should on my crDroid 6.10 install :/
It works on my Havocs I've used including my present 3.9 but I do have to reset my Network settings on that one.
It is an important function that was included on all Android phones AFAIK for ones that have fixed batteries so the user can emulate taking the Battery out. It can fix locked phones/apps and even phones that won't boot.
Huawei
https://helpandroid.com/how-to-reset-huawei-p20-pro/
The procedure differs from phone to phone e.g Samsungs it's usually Press and hold the “Power” and “Volume Down” buttons for eight to twenty seconds and the device will eventually turn off.
{
"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?