Database Develop

Paranoid Android 6.0.1 - AOSPA - OnePlus X

{
"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"
}
We are launching brand spanking fresh. All new features. New team members. New everything and we have made sure that everything that we are releasing has been polished to our best.
A lot went into this version of Paranoid Android, specially on the CAF side (OnePlus / Non-nexus devices). We ship with custom in-house kernels tweaked to provide the best power-battery combo, new functionalities and designs for hardware-specific options like the alert slider and advanced controls just for OnePlus devices - so feel pretty.
The main features and enhancements that you will probably end up noticing are our custom Quick Settings tile reordering functionality, floating window support, immersive mode, the new on-the-spot interface and CM Theme Engine. There's much more to come, so sit tight!
Feature highlights
Floating mode
Immersive mode
On-the-spot controls
Quick settings re-order
Paranoid OTA (Updates)
Battery styles
Advanced power dialog
Quick pull-down
Theme engine
CAF specifics
Enhanced kernel + control
Advanced buttons control
Advanced gesture control
Alert slider support
Ambient display support
Download
Get our latest OnePlus X build here.
Changelogs
As we're getting back into the thread game, keeping up with threads and updating them as per changelogs can be too hectic given our schedule. However, very detailed changelogs always go up on our Google+ page, follow us for constant updates!
Instructions & requirements
We highly recommend you to follow these instructions very carefully. Users usually tend to skip a few steps and eventually fall in trouble. Are you with me? Good. Let's get this train going.
Just a few things to keep in mind first -
If you're coming from another ROM / Stock, your system data (not internal storage) will have to be wiped. This includes apps, accounts, messages, call logs etc.
There's been some users complaining about different GAPPS variants messing up installs and causing a ton of issues. Upon investigating it seems OpenGapps Mini/Nano and Banks GAPPS work best.
Understand that Paranoid Android is a custom ROM and it might lead to addiction as it's relatively good. We shouldn't be accused of anything just incase your cat starts drinking wine. Things get a little woozy in the Paranoid World.
Some brain might be involved if things go wrong. Not a lot though, as much to solve what's 1+1.
Okay let's get to the main bit -
Once you have all the required files - boot into recovery and wipe the bananas out of your device. Get into the wipe menu and wipe data, system, cache and dalvik cache (basically everything except Internal Storage).
Once wiped, get into the "Install from zip" menu and select the ROM zip. (pa_bacon_6.x...). Once added to the install queue, TWRP will ask you if you want to add more zips into the queue - Click on "add more zips" and select the GAPPS package.
Swipe the bar on the bottom to flash/install zips. Once both zips are done installing - Reboot into system and set-up your device, do not do anything else.
Once you're done setting up your device - well that's when you're done. One thing though - Make sure you DO NOT INSTALL any other zip in the same queue as the ROM & GAPPS. Meaning, do not flash anything like a kernel or a root package while installing the ROM. We recommend you do that AFTER you're done setting up your device.
Important / Useful links
OpenGapps / Banks GAPPS
SuperSU root package
Paranoid Android Community (G+)
Our kernel sauce (OP2)
As always, we listen to what you have to say. Help us make PA better by submitting good bug reports possibly with a log attached. Learn how to take logs here. Submit bug reports and we'll try to iron out issues as soon as possible - it really helps a lot.
Mention me if you need any assistance and/or when reporting bugs or if you just wanna chat.
Cheers and #StayParanoid!
XDA:DevDB Information
Paranoid Android 6.0.1 - AOSPA - OnePlus X, ROM for the OnePlus X
Contributors
xboxfanj, arzbhatia
Source Code: https://github.com/AOSPA
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: The Novel Push by Sapphire
Version Information
Status: Stable
Created 2016-06-17
Last Updated 2016-06-18

Finally. Thanks

Nice one. Latest build running really smooth and is bug free.
@xboxfanj which app can you recommend to control the enhanced kernel?

crian said:
Nice one. Latest build running really smooth and is bug free.
@xboxfanj which app can you recommend to control the enhanced kernel?
Click to expand...
Click to collapse
Kernel Adituor is pretty good and made by Willi, who's on our team.

"Based on: God"
Can we get one based off of Satan too or are there too many thermal issues?
But seriously, I appreciate you're work here!

Great man. Hope to see ota updates are supported in your next build
Sent from my ONE E1003 using XDA-Developers mobile app

It seems not support f2fs

Web browser is crashing after a complete clean install - wipe data, cache and system. With last OpenGapps nano.
And no swipe with the google keyboard.
Back to CM.

All work good except for the camera, it lags, before and after flash sultan HAL, it need a lot of time for focus too.

Flashed the ROM and there was no sound in calls
Both the caller and receiver had no sound

Doesn't boot on my white E1003, stuck on one+ logo. I have to flash a custom kernel.
Double tap to sleep doesn't work.
Envoyé de mon ONE E1003 en utilisant Tapatalk

Definitely the best ROM or there. It's just works perfectly. The only bad thing is the camera. It's lagging and not performing well. And if I flash Sultan HAL is even worse. I don't use the camera too much so I can live with it. I wonder how did Sultan made the camera perform that well on his ROM, but.when flashing the HAL on other Roms it isn't nearly the same. It would be awesome to have AOSPA with sultans Roms camera performance.
Anyways, as I said, by far the best rom I tried for Onyx.
Glad to have PA back. Congrats!!!!

Low ear piece volume... Couldn't hear in crowded place... Cm theme doesn't have boot animation option. Gonna try new build...
Sent from my X using Tapatalk

Menu button
how i open the menu from app? Holding back or recents button doesn't work.

feligoni said:
Definitely the best ROM or there. It's just works perfectly. The only bad thing is the camera. It's lagging and not performing well. And if I flash Sultan HAL is even worse. I don't use the camera too much so I can live with it. I wonder how did Sultan made the camera perform that well on his ROM, but.when flashing the HAL on other Roms it isn't nearly the same. It would be awesome to have AOSPA with sultans Roms camera performance.
Anyways, as I said, by far the best rom I tried for Onyx.
Glad to have PA back. Congrats!!!!
Click to expand...
Click to collapse
Aren't you having any issue with calls ?
I am not having any sound on calls not even when I switch to speaker

Adesh15 said:
Aren't you having any issue with calls ?
I am not having any sound on calls not even when I switch to speaker
Click to expand...
Click to collapse
,Nope, not a single problem with calls. I don't use the phone as a phone too much though hehe, ironic right? But the few time I call my family through the day not a single problem. Maybe gapps conflict? I used banks as is the one they recommend.

feligoni said:
,Nope, not a single problem with calls. I don't use the phone as a phone too much though hehe, ironic right? But the few time I call my family through the day not a single problem. Maybe gapps conflict? I used banks as is the one they recommend.
Click to expand...
Click to collapse
I tried both open gapps nano and bank gapps but still no sound on calls

@xboxfanj,
Is the CMTE ready for use on AOSPA? I've been using Swift Dark theme with multiple ROMs previously and it always worked flawlessly. With AOSPA (the first onyx release) multiple UI elements remained unthemed. This happened with other themes as well.

thanks for the rom @xboxfanj !
just a minor (actually formal) thing: ur install instructions appear to be quite noob proof. therefore i think "install pa_bacon_..." might cause confusion for such

tet-bundy said:
thanks for the rom @xboxfanj !
just a minor (actually formal) thing: ur install instructions appear to be quite noob proof. therefore i think "install pa_bacon_..." might cause confusion for such
Click to expand...
Click to collapse
Yeah sorry, clearly I am not good at copy-pasting.

[ROM][7.0][T810][ABANDONED] CyanogenMod 14.1 for Tab S2 9.7 wifi

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.

[DISCONTINUED] [8.1.x][OFFICIAL][DISCONTINUED] CarbonROM | cr-6.1 [kagura]

{
"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

[ROMs][TREBLE] OpenKirin AOSP Collection

{
"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"
}
Welcome to Team OpenKirin AOSP Project. Our goal is to provide
a overall stable AOSP experience across all Huawei/Honor phones
utilizing a Kirin SoC and EMUI 8.0 - either updated or shipped.
So far most of the bugs have been fixed and the ROMs are fully usable
as daily driver - and fully Kirin optimized.
This is the device support section for: Huawei P10 Plus.
Any bugs found on this device(s) can be reported here, please include proper logs if you encounter any issues.
We support 3 ROMs in total as of now - LineageOS (Unofficial), ResurrectionRemix OS (Official from Beta 2+), OmniRom
You can find all needed guides/roms on our official website: https://openkirin.net
Requirements: basically full stock EMUI 8.0, with stock recovery/ramdisk
Support: Telegram - https://t.me/joinchat/EeDpi02ekfeJSBeaV4eqOw
XDA:DevDB Information
OpenKirin Treble ROMs, ROM for the Huawei P10 Plus
Contributors
OldDroid, XePeleato, surdu_petru
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: EMUI 8.0
Based On: LineageOS, CarbonROM, ResurrectionRemix OS, OmniRom
Version Information
Status: Beta
Created 2018-08-13
Last Updated 2018-08-27

Has anyone tried any of the ROMs?

osscar said:
Has anyone tried any of the ROMs?
Click to expand...
Click to collapse
I have currently installed on my p10 vtrl29c432b375 RR os beta 2 and from all the ones I tried I find this one to be the most complete rom, have proto kernel on it with spectrum profiles and magisk 16.4 as my daily driver.

osscar said:
Has anyone tried any of the ROMs?
Click to expand...
Click to collapse
Device: Huawei P10-Plus
Model: VKY-L29 C636
I mostly tried the Resurrection Remix ROM and it works very good. I still have it on my device.
There are some issues that i encountered. I also wrote them on the Telegram support group:
The battery has a problem. I noticed it with every battery monitoring app. Looks like that i have 1000mAh of capacity, while i have really a ~4000mAh. There is also a huge battery drain (with the stock ROM i had almost 20 hours of battery. With any of the treble ROMs, i have a maximum of 12 hours on standby). I'll explain later how i almost solved this problem.
Changing the theme looks not possible on RR. When i press "change theme" to "dark" or "black", nothing happens. I solved the need of having a dark theme with Substratum.
Sometimes the screenshots are VERY pixelated, like a quarter of the resolution of the screen.
The dialer has a huge problem: the "mute" button does not mute. The rest of the call is good.
Everytime i boot my phone, there is the "Android is booting..." text on the screen. Nothing more. The System interface just loops the "Android is booting..." text. I fixed it locking the screen, unlocking it with the power button, sliding up from the "dialer" icon, entering the padlock and pressing the "back" button. The text is gone and the phone is ready to work. (check attachments for a demo).
The battery drain can be fixed with three solutions.
1st solution:
The first solution is with Kernel Adiutor. If the scenario is identical as mine, you will notice that the phone is not going into the Deep Sleep state. You can however try to reduce the power consume setting the High CPUs governor on "powersave", while setting the Little CPUs governor on "interactive" or "conservative". That helped me to reduce the battery consume.
This solution has one problem: is ALWAYS active.
To avoid this situation, you can use Tasker, which is the second solution.
2nd solution:
With Tasker, i set two profiles: "Screen Off" and "Screen On".
I added two activities, each one for each profile.
The first activity, the "Screen Off" activity, sets every CPU on "powersleep" mode, saving energy.
The "Screen On" activity sets the little CPUs at "interactive" mode, making the phone smoother and not lagging.
Then i set the profile "Screen On" that has to be activated ONLY if the screen is on the state "ON". Same with "Screen Off", but obviously when screen is on state "OFF".
3rd solution:
The third solution is a something that you can use in addiction with the previous ones.
Just use Greenify to hibernate apps once they are closed. It helped me a lot with old Android phones with a small battery.
WHAT TO DO IF YOUR RESURRECTION REMIX ROM GOES INTO A "ANDROID IS BOOTING..." LOOP
Here's the bootloop example. It just goes on forever:
Here's how to troubleshoot it. Just do it every reboot:

Hey, Why is there no Location Service Icon in the taskbar when using resurrection remix rom?. That's a really big thing for me as i use it alot.

osscar said:
Has anyone tried any of the ROMs?
Click to expand...
Click to collapse
Yesterday installed OMNIrom Alpha2 on my VKY-L29 and... actually i don't have what to blame.
I'm not a power user, but for daily use it's more than capable. Phone works, internet (wifi/data) works, youtube vanced works, fingerprint gestures works, camera works, no lag. Android 9.
I'm happy AF, epecially when i know, that several weeks before i had locked device with no prospect to get a root, not mentioning Android Pie.

keturidu said:
Yesterday installed OMNIrom Alpha2 on my VKY-L29 and... actually i don't have what to blame.
I'm not a power user, but for daily use it's more than capable. Phone works, internet (wifi/data) works, youtube vanced works, fingerprint gestures works, camera works, no lag. Android 9.
I'm happy AF, epecially when i know, that several weeks before i had locked device with no prospect to get a root, not mentioning Android Pie.
Click to expand...
Click to collapse
Hi there, any issues after a while? Are you still using it? (like, is BT working, is the dialer fully functional?)
best,
-r

Rooted P10 Plus with TWRP 3.1.0-0
Dear Sir,
Thank you for the ROMs.
Please inform me if I can install either of your ROM's via TWRP or are there "hoops and whistles" to go through before I can install.
My phone model number is: VKY-L09
Build number: VKY-L09C02B102
EMUI version: 5.1
Android: 7.0
Kernel: 4.1.18-gfd75bb
TWRP: 3.1.0-0

rodalvas said:
Hi there, any issues after a while? Are you still using it? (like, is BT working, is the dialer fully functional?)
best,
-r
Click to expand...
Click to collapse
Ok, today i'm going to reinstall this rom. Not because i didn't like it, but i want to try openkirin 8.0 roms, how do hey work. I would go back later to this rom for sure.
Minuses of alpha version - i saw somewhere that original camera is not ported, so quality may be not so good. sometimes camera app glitches and some functions doesn't work (portrait mode).
sorry about bluetooth, haven't used it at all. also, i'm not a mobile gamer, so i don't know if game's speed is the same as original.
Don't see any problems with calling. Battery works as expected for ~2 days with simple use of several hours browsing, few calls and always wifi+data.
In my opinion it's not alpha version, but stable beta.

keturidu said:
Ok, today i'm going to reinstall this rom. Not because i didn't like it, but i want to try openkirin 8.0 roms, how do hey work. I would go back later to this rom for sure.
Minuses of alpha version - i saw somewhere that original camera is not ported, so quality may be not so good. sometimes camera app glitches and some functions doesn't work (portrait mode).
sorry about bluetooth, haven't used it at all. also, i'm not a mobile gamer, so i don't know if game's speed is the same as original.
Don't see any problems with calling. Battery works as expected for ~2 days with simple use of several hours browsing, few calls and always wifi+data.
In my opinion it's not alpha version, but stable beta.
Click to expand...
Click to collapse
OK so I bit the bullet; it works very well (more stable than the RR build AFAIC), with a few glitches:
no NFC
install doesn't offer to restore content from elsewhere
graphics seem to flicker a bit now and then
Some highlights:
battery consumption appears to be at least on par with EMUI 8 (getting more than a full day)
this rom does include the Huawei Camera app, which works similarly to EMUI
I'm keeping it

keturidu said:
Yesterday installed OMNIrom Alpha2 on my VKY-L29 and... actually i don't have what to blame.
I'm not a power user, but for daily use it's more than capable. Phone works, internet (wifi/data) works, youtube vanced works, fingerprint gestures works, camera works, no lag. Android 9.
I'm happy AF, epecially when i know, that several weeks before i had locked device with no prospect to get a root, not mentioning Android Pie.
Click to expand...
Click to collapse
how did you install it?
When i try to install a treble android 9 rom i just get a black screen at boot (not even boot anim) and then it just reboots, i followed the openkirin's guide step by step and same result
EDIT: Nvm i got it working

Hi, I think I messed up, I try installing by fastboot the system image, but know my phone is on bootloop, i cannot make the twrp be recognized to the computer at least to try uploading to the internal memory another rom to flash.
Can someone, explain to me in details, how can I install this rom? as my phone is bricked now, and I don't know how to solve this. I can only flash things via fastboot, because the twrp is not recognized.
If someone, could help me, I would be so thankful
i dont know if i have to install the a-only version or the A/B version, can someone help me with that?

Hi, I finally can install the ROM, OmniROM Pie Alpha 3, the camera app is working very bad, it's slow and when you took a picture with the front camera it is like you never took it, as it is not in the gallery. There is a fix for this?

Hi,
I see there are some improvements like: Camera: fixed save to external SD card and other good things on 5.2.
Code:
[U]OmniROM Pie Alpha 5.2[/U]
Changes from Alpha 5 to Alpha 5.2 are marked with NEW
OmniROM Pie changes through Feb. 8 with February security patch (NEW: Was Feb. 5 with January security patch.)
Fixed crash in Smart Key settings on Honor 8. (NEW: Derp on my part. This is now saving it’s value properly.)
Added persistent toggle to device settings for disable HW overlays; defaults on for hi3650 devices.
[B]Camera: fixed save to external SD card[/B].
Camera: hi3650 tweaks (beauty mode causing app crash should be resolved)
Minor tweaks to sd card support (exfat seems to work a little better now)
Bluetooth tweaks for Huawei BLE timeout error (NEW; Thanks @Hackintosh5)
Tweak to libc for dealing with certain Huawei vendor libs; fixes crashes on certain devices [Mate 10 Pro exhibited this] (NEW)
Note: If you are using Substratum, please disable overlays before updating.
[U]OmniROM Pie Alpha 4[/U]
Updated to current security patch (2019-01-05)
Added Google Setup Wizard & restore function. (Minor known issue: if you choose to not restore, the restore step sticks around and leaves a persistent notification until reboot. Reboot or force stop the app from notifications to clear.)
Added fast charging toggle in device settings
Added smart key support for Honor 8
Added extended display size support (Settings / OmniGears / Bars / Enable Scaling)
I would possibly update from Pie Alpha 3, but I really don't know how to do it. Following OpenKirin ROM Installation Instructions maybe, without step 15? I wouldn't like to re-install all apps and settings. Please, someone who has updated openkirin in the past, advice.

Hello,, is that possible at Time to flashing Treble Rom to P10 Plus with Emui 9.0.1??? I dont have the Bootloader Code. How can i get to my Code ?? Huawei dont give the Code since any Weeks.

Simon G said:
Hello,, is that possible at Time to flashing Treble Rom to P10 Plus with Emui 9.0.1??? I dont have the Bootloader Code. How can i get to my Code ?? Huawei dont give the Code since any Weeks.
Click to expand...
Click to collapse
check chimera tool, if remember correct it can do the job (paid app)

I tried using potatoNV and it works but getting out of COM mode is a problem. DC unlocker will work but is paid(and not working in PR China)

I have never installed a custom rom before; I am a little bit of a power use but basically the only reason I want a custom rom on my Huawei P10 Plus is for the latest android updates.
Is there anyone here that knows if it is still possible to get a custom rom for this phone? I clicked the open kirin link and it looks like the site is down.
Can anyone help me or am I just a little late to the party?

[ROM][11.0][OFFICIAL][Vanilla & GApps]Havoc OS v4.x Sofiar

{
"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.