[10][OFFICIAL] CarbonROM | cr-8.0 [z3c] - Xperia Z3 Compact Original Android Development

[10][OFFICIAL] CarbonROM | cr-8.0 [z3c] - Xperia Z3 Compact Original Android Development

My feedback about CR8.0 (weekly build 20200513-0206) with gapps pico, magisk 20.4 and ~75 user apps.
Using TWRP 3.3.1-z3c-20191212-sar from here
Xposed (RiRu 20.2 from magisk repo, EdXposed-YAHFA-v0.4.6.2.4529 from here) works without problems (1st screenshot).
I'm not using internal data encryption because of compatibility problems between ROMs/versions, tired to restore backups each time I flash new ROM.
About 700MB of RAM free just after boot, with stock launcher.
Battery drain fast, but my battery is very old, no complain.
Pros:
+ reliably fast
+ everything works including GPS, BT, calls/data, hotspot and all my apps
+ no problems with audio routing and mic sensitivity
+ camera is ok but I use OpenCamera anyway
Cons/bugs:
- still no 5ghz wifi in Russia (I use my magisk-patch to fix this, may also help with other regions, try if you meet this bug)
- ongoing call can be hanged accidentally by double-tap in any place of turned off display (e.g. by cheek) if tap-to-wake feature is active (here is my workaround using Automate tool, works like a charm). I'm not sure if this bug belongs only to my phone or to any z3c, but it was like forever on any AOSP-based ROM, starting with Android 7.
- broken size for "Aeroplane mode" button/icon in power menu (see 2nd screenshot)
- ringtone sound become a bit quieter after half a second from start of incoming call
- overall loudspeakers volume is not loud enough
Features I'd like to have in this ROM:
1) choose clock position in statusbar (only at left in CR8.0)
2) brightness control by sliding in statusbar without opening it
3) mess up digits on the PIN unlock screen [Carbone Fibers > Buttons > Scramble PIN]
4) unlock instantly when entering last digit without confirmation
5) long press power button to turn on/off torch while display turned off [Carbone Fibers > Buttons > Toggle torch]
6) restrict/disable power menu while phone locked
7) disable notification panel while phone locked
8) set minimal time between notifications on per app basis
9) wake by volume rocker buttons
10) increasing ringing volume
11) debugging over network (settings in devs options, absent in CR)
Most of this stuff available in LOS and AEX roms, but also all (except: 7,10,11, with bugs: 6) can be achieved in CR by using GravityBox xposed module.
Thank you @Myself5 for continue work with our lovely z3c.

Thank you very much for supporting our cute device
Did anyone tried edxposed with xprivacylua, Viper4android, Netflix. Do they work?

Found a BUG: can't set PIN/pattern to lock screen, getting bootloop after try to set it and reboot.
I use z3c as my daily driver, so I need screen lock, can't use this ROM until fixed. Hope I'm not only one who faces this bug.
BigBrother84 said:
Did anyone tried edxposed with xprivacylua, Viper4android, Netflix. Do they work?
Click to expand...
Click to collapse
Not sure about these apps, but at least GravityBox[Q] and App Locale 2 I can NOT get working on this ROM with EdXposed v0.4.6.0_beta(4471) (YAHFA). As well as on latest february build of LOS 17.1 (but worked fine on january build). May be I should try some newer versions of EdXposed (like ones from "canary" repo or something), but I need screenlock bug fixed first to use this ROM and more of free time. Btw, everything works perfect on LOS16.

Hooin Kyoma said:
Wiped all except micro sd. Stuck at "Setup wizard keeps stopping", system unusable. With and without gapps.
Ok I just clean-reinstalled ROM and made first boot WITHOUT SIM CARD INSERTED and it's boot fine. Btw my SIM card PIN-locked (if it's important) and it never caused any problems in LOS17.
Also I reserve this post for my review.
Thank you @Myself5 for continue work with our lovely z3c.
Click to expand...
Click to collapse
The Setup Wizard is still work in progress, and we just discovered nobody tested it with a SIM so far. We'll take care of it, thanks.
As for your screen lock issue in the other message: are you encrypted by any chance? Also I assume that's not happening on the lineage17.1 builds you mentioned?

Myself5 said:
As for your screen lock issue in the other message: are you encrypted by any chance? Also I assume that's not happening on the lineage17.1 builds you mentioned?
Click to expand...
Click to collapse
Tried with and without encryption. With and without Gapps. With and without SIM card. Always same result. Everytrhing fine until you set screen lock PIN either from Setup Wizard or from Security settings. First of, unlock method stays "Swipe" after set PIN. And if you reboot, system's boot to desktop and auto-soft-reboot (without sony logo) after few seconds. And yes, this not happening on LOS17.1

Installation immediately fails for me.
Code:
Patching system image unconditionally...
E1001: Failed to update system image.
[COLOR="Red"]Updater process ended with ERROR: 7
Error installing zip file '/sdcard/CARBON-CR-8.0-PAX-UNOFFICIAL-z3c-20200208-1428.zip'[/COLOR]
Updating partition details...
[COLOR="red"]mount -o bind '/data/media/0' '/sdcard' process ended with signal: 6
Failed to mount '/appslog' (Invalid argument)[/COLOR]
...done
[COLOR="red"]mount -o bind '/data/media/0' '/sdcard' process ended with signal: 6
E:Error creating fstab[/COLOR]
Tried to update from your previous CR7 build (CARBON-CR-7.0-OPAL-UNOFFICIAL-z3c-20190819-2110), using TWRP 3.2.1 from here. Nothing actually got written, so previous installation is fine.

yxagasasgas said:
using TWRP 3.2.1
Click to expand...
Click to collapse
Try 3.3.1 from here, it support Android 10 with "system as root". And I'd recommend wipe all except internal storage and perform clean install.

Hooin Kyoma said:
Try 3.3.1 from here, it support Android 10 with "system as root". And I'd recommend wipe all except internal storage and perform clean install.
Click to expand...
Click to collapse
Doesn't work for me, just blackscreens and reboots. Tried installing it both via TWRP app and fastboot (although strangely enough, even though adb worked, fastboot didn't in Windows, had to boot to Linux), no dice, so went back to my previous TWRP for now.
Would be nice to know what's up with that, but I haven't fiddled with any of this in a long time. Ever since CarbonROM appeared, my Z3C pretty much "just worked" and I never had to do much of any fiddling.

New build uploaded just now has the SetupWizard fixed. The lockscreen bug is getting looked into right now.

Uploaded a new build. Contains some additional lockscreen clocks but more importantly, the PIN issue is fixed.
Code:
f8d3b9c5519b91baba7a917d99b7f09e CARBON-CR-8.0-PAX-UNOFFICIAL-z3c-20200225-1530.zip

Myself5 said:
PIN issue is fixed
Click to expand...
Click to collapse
I can confirm this. Also Google' Setup Wizard passed fine with SIM. Thank you!
What is bother me - the Carbon Fibers menu - as I recall, it usually have much more settings than I can see in this build (see screenshots). This is only to me or some global restriction?
Also camera app not working, this is odd. Though I didn't try it on fresh system (before google's backup restore). Someone please check.

Hooin Kyoma said:
I can confirm this. Also Google' Setup Wizard passed fine with SIM. Thank you!
What is bother me - the Carbon Fibers menu - as I recall, it usually have much more settings than I can see in this build (see screenshots). This is only to me or some global restriction?
Also camera app not working, this is odd. Though I didn't try it on fresh system (before google's backup restore). Someone please check.
Click to expand...
Click to collapse
the camera was not working for me as well, but after some restarts it fixed itself. i dont know how that happened (even tried the xperia camera port from magisc) but i cannot confirm weather that did the trick..

Hooin Kyoma said:
Also camera app not working, this is odd. Though I didn't try it on fresh system (before google's backup restore). Someone please check.
Click to expand...
Click to collapse
You could try if the camera starts working after deleting the folder /data/credmgr with a root file explorer and then rebooting. By doing this, the credmgr folder with the credmanager files are rebuilt by the system, which can help fixing camera issues.

okij said:
You could try if the camera starts working after deleting the folder /data/credmgr with a root file explorer and then rebooting. By doing this, the credmgr folder with the credmanager files are rebuilt by the system, which can help fixing camera issues.
Click to expand...
Click to collapse
Thanks for the tip mate. But it didn't help in this case.
Btw, today I installed (again) latest LOS17, tuned it, rebooted many times, played with microG/magisk/xposed modules - camera worked fine all the time.
Next (steps to reproduce): wiped cache, dalvik, data and system, installed only CR-8.0 (20200225), rebooted to system, skip anything, camera WORKS! Did nothing, just rebooted again, and got "Can't connect to the camera"! I think this is a BUG and hope I'm not the only one who faces it.
I still have a question about Carbon Fibers menu, why it lack items/options? I can't even reposition statusbar clock to right without using "third-party" apps like GravityBox xposed module.
Also, kind of "feature request": time to time I use adb from PC (we all do i think), and I hate to connect cable to micro-USB port, cuz it's weak and can break soon if use freqently. I use magnetic port/cable for charging and "ADB over network" toggle in Developer Options for ADB operations. One of the reasons why I prefer LOS is because of this "must have" thing, they even have tile in QS for toggle it quickly! Can it be added to CR?

the "cant connect to the camera" returned unexpectedly..

Hum this new OP looks interesting.
And what is this Twitter Post?
And did someone say May Security Patches?

Thank you for your hard work!
Does encryption work properly?
What works
Viper4android works
Sony Device Dummy works with official Sony apps
Spotify works

Myself5 said:
Hum this new OP looks interesting.
And what is this Twitter Post?
And did someone say May Security Patches?
Click to expand...
Click to collapse
Great, this looks interesting indeed!
Today cr-8.0 also was offered as an OTA update on my Z3c which so far I still have on cr-6.1 (because everything is working well and rock stable on this older version and thankfully you still release monthly security patches for it.)
Have you done some thorough testing of cr-8.0 on the Z3/Z3c devices before making it now official and is everything working (e.g. full camera support and proper in-call audio, which had problems on shinano devices on Android 9 and 10 before)?
If so, I might give it a try this weekend.
Thank you and keep up the great work! :good:

okij said:
Today cr-8.0 also was offered as an OTA update on my Z3c which so far I still have on cr-6.1
Click to expand...
Click to collapse
I tried dirty-flash on my cr-6.1, but without success - I can't boot my phone because it stuck in boot animation.

Related

[DISCONTINUED][AOSP][6.0.1] Fire Nexus ROM - [SUBSTRATUM] [M4B30X] [22 Oct 2016]

{
"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"
}
Fire Nexus ROM
Introduction
This ROM is based off AOSP marshmallow. I have merged changes from CAF and Cyanogenmod to enable this boot on our HDX devices.
Features
- AOSP with optimisations from CAF
- Open GAPPS nano is built-in
- Clear all recents
- Advanced Power Menu
- Substratum Theming Support
- Init.d Support
- SuperSU is built-in
Prerequisites for Installation
- Unlocked bootloader is a must
- TWRP 3.0.2-0 installed
- This does NOT work with Safestrap
Downloads
*** Please do NOT create any mirrors ***
- Fire Nexus ROM for APOLLO
- Fire Nexus ROM for THOR
Issue List
- Sideloading of some apps may be necessary
- Bluetooth
- LTE
- WiFi may need to be manually toggled after wakeup
Kernel Source Code
- https://github.com/CyanogenMod/android_kernel_amazon_hdx-common
Credits
- AOSP
- CodeAurora Forum
- Cyanogenmod
- Substratum Team
XDA:DevDB Information
mm-fire-nexus-rom, ROM for the Amazon Kindle Fire HDX 7" & 8.9"
Contributors
ggow
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Testing
Created 2016-10-22
Last Updated 2019-10-02

Release Notes / Change log
22 October 2016
- Initial Release
- Xposed needs testingConfirmed as working

Thank you for this new rom. I have testet it with the open camera app, but it showes me a picture whith a rotation error (180 degrees).

schr01 said:
Thank you for this new rom. I have testet it with the open camera app, but it showes me a picture whith a rotation error (180 degrees).
Click to expand...
Click to collapse
Yes, rotation is a problem. If I remember rightly it is the same issue as with other custom ROMS. Try locking the screen rotation in the correct aspect then running open camera again. The app should then appear correctly.

Thank you for your tip. It works.

Woohoo!
Initial findings after a quick 15 min test:
- clean flashed (Thor) with Xposed 23; booted fine (wiped system/data/cache/dalvik)
- installed a handful of essential apps from Play Store - no compatibility issues
- installed GravityBox 6.1.6 and tested a few tweaks that tend to be problematic on some devices/roms - no issues
- big test: installed my preferred messaging app which hates everything including no-SIM devices - worked perfectly!!
Very excited on first take! Sadly, rom hangs w/dirty flash or if CM 12.1 data partition restored after initial boot. Will need to fall back temporarily until I have time to perform a manual migration of existing app portfolio. No ding against the rom; dirty flashes are always a crap shoot and I have been bringing this one forward since Jelly Bean (yikes!). I have an old Fire Nexus KitKat build I may try too. Hate rebuilding from scratch.
The only (minor) suggestion is to include recovery and soft boot options to the Advanced Power Menu. No big deal as I can easily get this from Xposed; just seems a natural as it was noted in the feature set (not normally part of AOSP). Love having GAaps Nano and SuperSU built in; avoids many initial flash headaches and simplifies upgrades.
Really nice work, @ggow. Clean and simple.
Edit: I did need to enable 'all rotations' in GravityBox as expected on this device. Likely could achieve the same result via Nova or other third party tweak. Native setting was largely ignored.

Davey126 said:
Initial findings after a quick 15 min test:
- clean flashed (Thor) with Xposed 23; booted fine (wiped system/data/cache/dalvik)
- installed a handful of essential apps from Play Store - no compatibility issues
- installed GravityBox 6.1.6 and tested a few tweaks that tend to be problematic on some devices/roms - no issues
- big test: installed my preferred messaging app which hates everything including no-SIM devices - worked perfectly!!
Good to hear Xposed is working and your problematic messaging app
Very excited on first take! Sadly, rom hangs w/dirty flash or if CM 12.1 data partition restored after initial boot. Will need to fall back temporarily until I have time to perform a manual migration of existing app portfolio. No ding against the rom; dirty flashes are always a crap shoot and I have been bringing this one forward since Jelly Bean (yikes!). I have an old Fire Nexus KitKat build I may try too. Hate rebuilding from scratch.
I would expect CM 12.1 data restore to not work. The framework in this ROM is very different from CM 12.1.
You might also run into problems dirty flashing from the KitKat build of the ROM.
Clean flash would be recommended in both cases when coming from an older or different ROM.
The only (minor) suggestion is to include recovery and soft boot options to the Advanced Power Menu. No big deal as I can easily get this from Xposed; just seems a natural as it was noted in the feature set (not normally part of AOSP). Love having GAaps Nano and SuperSU built in; avoids many initial flash headaches and simplifies upgrades.
Kids sometimes use my tablet so having the reboot to recovery options etc can be a problem.
Really nice work, @ggow. Clean and simple.
Edit: I did need to enable 'all rotations' in GravityBox as expected on this device. Likely could achieve the same result via Nova or other third party tweak. Native setting was largely ignored.
Click to expand...
Click to collapse
Thanks for the detailed feedback :good:

Thank you for nexus rom.
Thank you for nexus rom.
It works almost good for me, but google contacts cannot synchronize gmail account.
In nexus5 (6.0.1), it can be synchronized by contacts->settings->accounts->google.
In thor, contacts->settings->accounts->(not shown google).

Will the install work with twrp 2.8.7 or is 3.0.2 a requirement?

rootnooby said:
Will the install work with twrp 2.8.7 or is 3.0.2 a requirement?
Click to expand...
Click to collapse
FWIW - install worked fine on 3.0.0.x (3.0.2 has permission issues)

ADB Backup/Restore
May have found a bug: adb backup and restore commands are ignored. Command is accepted (Win 10 x64 host) but no response from device. Other adb commands appear to work fine. Tinkered with the various USB modes but behavior is always the same. Also tried setting/clearing device debug password. With no password there is a 3-4 sec delay before returning to command prompt; with a password exit is nearly instantaneous. Did some searching online but not a lot of good info on the net. Works on CM 12.1 build (Thor).
Anyone else experiencing this?

I had no installations problemes with TWRP 3.02.

Davey126 said:
May have found a bug: adb backup and restore commands are ignored. Command is accepted (Win 10 x64 host) but no response from device. Other adb commands appear to work fine. Tinkered with the various USB modes but behavior is always the same. Also tried setting/clearing device debug password. With no password there is a 3-4 sec delay before returning to command prompt; with a password exit is nearly instantaneous. Did some searching online but not a lot of good info on the net. Works on CM 12.1 build (Thor).
Anyone else experiencing this?
Click to expand...
Click to collapse
Will take a look, before the next release.

ggow said:
Will take a look, before the next release.
Click to expand...
Click to collapse
Thanks. Two reasons for wanting this:
- transfer apps and all associated data between devices
- create targeted backups or nandroid clone on devices with limited internal storage
Titanium used to be the go-to choice but it hasn't been updated in nearly two years (struggles on Android 6+) and also utilises adb functions for transport.

FYI - I was able to get this rom to dirty boot a CM 13 build but that's as far as it went. Processor pegged on lock screen judging from heat and sluggish response (5+ sec per key press). Obviously a clean flash is highly recommended by dev but was looking for a path to bring my existing CM 12.1 build (apps and data) forward. Probably hang out on Lollipop for awhile as it meets my needs with no meaningful loss of functionality vs Marshmallow with Greenify, Nova and a few Xposed modules thrown in.
Might give Nexus 6 another whirl once adb backup/restore is working (see previous posts for background). I do miss AOSP ...
Also sad CyanogenMod can't get their act together and fix the ridiculous bug that throws up a fur ball when SIM access is requested on CM 13 if there ain't no SIM card installed (hello...tablets!!). Regression was introduced in a nightly build last March and never resolved.

Camera isn't working on apollo

@ggow Nice to see the work you're doing for the hdx. I'm just curious - before I decide to upgrade to this- are there any plans to get Bluetooth stable on this ROM or is it going to have the same issues as on other ROMs. Thanks.

chipsugar said:
@ggow Nice to see the work you're doing for the hdx. I'm just curious - before I decide to upgrade to this- are there any plans to get Bluetooth stable on this ROM or is it going to have the same issues as on other ROMs. Thanks.
Click to expand...
Click to collapse
I have been looking into Bluetooth as I need this working too. But with these new versions of android running with old binaries, it becomes really difficult to get everything working as it should.

Davey126 said:
FWIW - install worked fine on 3.0.0.x (3.0.2 has permission issues)
Click to expand...
Click to collapse
Installed with 2.8.7, Apollo, with no issue!

My Apollo was on 4.5.5.1, then installed with Safestrap v4, and then Fire Nexus KK ROM. After waiting weeks for the 1-Click bootloader unlock tool, I finally decided to go for the step-by-step unlock procedure and managed to have my Apollo unlocked yesterday afternoon.
I clean flashed your TWRP 3.0.2.0 and this Fire Nexus MM ROM immediately after unlock and am really pleased with the new ROM and the newly found freedom. The ROM works quite well so far except for 1) camera (tried Snap Camera and Camera MX), 2) Google Contacts cannot sync with Gmail account.
As I came over from SafeStrap v4, is there any old files and folders need to be tidy up?

[ROM][Pie][OFFICIAL] Resurrection Remix v7.0.2 [evert]

{
"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"
}
Resurrection Remix P
Code:
[SIZE="4"]/*
* 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, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/[/SIZE]
Resurrection Remix the ROM has been based on LineageOS, SlimRoms, Omni and original Remix ROM builds, this creates an awesome
combination of performance, customization, power and the most new features, brought directly to your Device.
Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy!
Special thanks to the LineageOS team, Omni team, SlimRoms and of course to all the supporters.

Make sure you have the latest TWRP.img
Download the latest RR-P zip and GApps zip (opengapps nano or smaller)
fastboot boot twrp.img (NEW!! See post #2 for info on installing TWRP)
If coming from stock for the first time, flash copy-partitions-AB.zip from second post (It takes a backup of active slot to inactive slot)
In TWRP, choose -> Wipe -> Format data and type "yes" at the prompt (Note: this will wipe internal storage)
Flash latest RR-P.zip
Reboot and let the ROM boot once (it is necessary to reboot between ROM flash and GApps/Addon flash due to slot-swap logic)
Reboot back to bootloader and fastboot boot twrp.img again
In TWRP, choose -> Wipe -> Format data and type "yes" at the prompt (You may be able to get away with just doing a factory reset at this point, but that's on you to try)
Flash Google Apps package (optional)
Flash Magisk (also optional) (Note: If Magisk doesn't stick after setting up your device, fastboot boot twrp.img one last time and flash it again, no need to wipe anything)
First boot may take up to 10 minutes.
ROM Download
GApps
Resurrection Remix Source
Device Source
Kernel Source
Vendor Source
XDA Developers
LineageOs Team
Omni Team
And Of Course To All The Supporters, Donators And Users
If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you, Team Resurrection Remix and me quite some time.
Download the MatLog app from the Play Store.
After downloading the MatLog app, go to the app settings, and change the log level to Debug.
Clear all previous logs and take the exact steps to produce the error you are receiving. As soon as you receive the error (probably a force close), go straight into MatLog and stop the log recording.
Copy and paste the entire log either to Hastebin or Pastebin
Save the log, and copy and paste the link into the thread with a brief description of the error.

XDA:DevDB Information
Resurrection Remix Pie v7.0.2, ROM for the Moto G6 Plus
Contributors
Jleeblanch, erfanoabdi, rahulsnair, RR Team
Source Code: https://github.com/ResurrectionRemix
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Based On: LineageOS
Version Information
Status: Beta
Beta Release Date: 2019-02-25
Created 2019-02-26
Last Updated 2019-04-21

Copy partitions zip & TWRP installation info
[size=+2]Important info, please read...[/size]
Starting from build 20190414, encryption is disabled (temporarily) and you must clean flash
The new TWRP version now supports decryption on Pie when booting twrp. However, I have updated TWRP to include the new magisk repacktools which allows users to download and install one twrp.img without the need of an installer zip. The reason behind releasing the ROM with encryption disabled? If you were to try to install TWRP while using an encrypted ROM, you would end up in a bootloop that would bring you back to TWRP. But, install TWRP on a ROM with encryption disabled, and everything works as expected.
[size=+1]TWRP Installation[/size]
-> TWRP download || twrp-3.3.0-v2-evert-jlb.img
->>> The twrp.img you download above will also be the same twrp.img you will install, so make sure to put a copy on your device as well
-> Boot twrp
Code:
fastboot boot twrp-3.3.0-v2-evert-jlb.img
-> In TWRP, choose Advanced / Install Recovery Ramdisk
-> Select the twrp-3.3.0-v2-evert-jlb.img
->>> At this point twrp will automagically unpack your boot.img and the twrp.img, swap out the recovery-ramdisk, and repack your boot.img. When this process completes, twrp will be permanently installed.
->>> Always flash Magisk AFTER you've installed twrp
-> Reboot and enjoy. You should now be able to reboot to recovery from the Power Menu!!
DO NOT try to install twrp on an encrypted rom. You will most likely end up in a bootloop, you have been warned!
Important
To keep TWRP installed between ROM updates, there is a Magisk Module named "TWRP A/B Retention Script" by @osm0sis. Search for it within Magisk Manager Downloads section. You'll want to flash this script zip after each OTA has installed, but before you install Magisk to the Inactive Slot from Manager.
[size=+1]Coming from stock?[/size]
Make sure to flash the copy-partitions-AB.zip in twrp before you do anything else. You can download it from the attachment below...

Reserved

Cool, i will test it now (im glad its official).
Ps dont do it "Perform a FULL factory wipe and wipe/system and dalvik cache as a precaution"
i meant wiping system.. even if we install custom rom after this it will be no os installed as twrp says.

Woks awesome, thank you dev

Excellent ROM.
Always loved RR ROMs.
Only downside I have is wondering if there will be anyway to get Google Pay working, as unfortunately it doesn't on this ROM.
Also, how can I disable the one button navigation style, as when I have a NAV bar on, I still have functions on my one button.
TIA.

WYPIERDAALAAC said:
Cool, i will test it now (im glad its official).
Ps dont do it "Perform a FULL factory wipe and wipe/system and dalvik cache as a precaution"
i meant wiping system.. even if we install custom rom after this it will be no os installed as twrp says.
Click to expand...
Click to collapse
The install instructions in the OP are generic, and don't necessarily apply for this device. You're better off following the install instructions from Lineage-16.0. I will update the OP with proper install instructions when I have some time asap.
LDMx96 said:
Excellent ROM.
Always loved RR ROMs.
Only downside I have is wondering if there will be anyway to get Google Pay working, as unfortunately it doesn't on this ROM.
Also, how can I disable the one button navigation style, as when I have a NAV bar on, I still have functions on my one button.
TIA.
Click to expand...
Click to collapse
For now, if you've flashed Magisk, you can flash my Magisk module (or any module) that will help pass safetynet and show device as being certified in Play Store. This is why Google Pay doesn't work.
I had updated some blobs and build fingerprint to match the stock Pie update, but it seems to be causing the device to fail safetynet. I will have this fixed in the next update.
As for the fingerprint gestures always being enabled. I'm looking into this too. I'm assuming this has something to do with an overlay I added to insure the navbar was enabled on first boot (as without it, it's not). I hope to have this fixed for the next update as well.

Jleeblanch said:
For now, if you've flashed Magisk, you can flash my Magisk module (or any module) that will help pass safetynet and show device as being certified in Play Store. This is why Google Pay doesn't work.
I had updated some blobs and build fingerprint to match the stock Pie update, but it seems to be causing the device to fail safetynet. I will have this fixed in the next update.
As for the fingerprint gestures always being enabled. I'm looking into this too. I'm assuming this has something to do with an overlay I added to insure the navbar was enabled on first boot (as without it, it's not). I hope to have this fixed for the next update as well.
Click to expand...
Click to collapse
No problem, I won't flash Magisk if you're looking at getting it fixed I will just hang fire, it's not a much needed thing anyway, as Google Pay isn't a much needed thing for me, was just handy.
As for the Fingerpring Gestures that's fine, it's not harmful, I just thought I'd mention it.
I'm loving it so far, not had any problems all good.

Awesome! I'm using magisk with Ainur Sauron and Viper, working flawlessly! Everything works pretty well so far. Thanks for the amazing job!
I flashed it over the stock pie without wiping system, only factory reset. I don't know if this helps because I'm still a newbie P, just sharing!
RR rocks!

LDMx96 said:
No problem, I won't flash Magisk if you're looking at getting it fixed I will just hang fire, it's not a much needed thing anyway, as Google Pay isn't a much needed thing for me, was just handy.
As for the Fingerpring Gestures that's fine, it's not harmful, I just thought I'd mention it.
I'm loving it so far, not had any problems all good.
Click to expand...
Click to collapse
I will fix it, yes. It seems I got it right on Beckham, but not so much on Evert lol. Anyway, I'll have an update ready for the weekend. I don't use Google Pay much myself either, although as you said, it is handy. I'd prefer things worked out of the box rather than needing workarounds to fix things.

Jleeblanch said:
I will fix it, yes. It seems I got it right on Beckham, but not so much on Evert lol. Anyway, I'll have an update ready for the weekend. I don't use Google Pay much myself either, although as you said, it is handy. I'd prefer things worked out of the box rather than needing workarounds to fix things.
Click to expand...
Click to collapse
No worries mate, I'll look forward to the update on the weekend then.
Thanks a bunch.

Excellent rom, I like it all of them, but it seems that it's only me who have trouble in calls, I can't hear nothing when I use headphones, it only works without headphones.
Pd. Sorry for my English

asesinodilusion said:
Excellent rom, I like it all of them, but it seems that it's only me who have trouble in calls, I can't hear nothing when I use headphones, it only works without headphones.
Pd. Sorry for my English
Click to expand...
Click to collapse
I've just tested this too, no call volume when earphones are connected, but fine once disconnected.

asesinodilusion said:
Excellent rom, I like it all of them, but it seems that it's only me who have trouble in calls, I can't hear nothing when I use headphones, it only works without headphones.
Pd. Sorry for my English
Click to expand...
Click to collapse
LDMx96 said:
I've just tested this too, no call volume when earphones are connected, but fine once disconnected.
Click to expand...
Click to collapse
Someone mentioned this on telegram as well. If this is the only bug anyone has encountered, that's kinda awesome [emoji6].
However, as I don't have a pair of headphones to test with and possibly reproduce the issue, can one of you (or both) please get a log? I just need someone to reproduce the issue while taking a logcat and attach it here so I can diagnose and fix the issue.

Jleeblanch said:
Someone mentioned this on telegram as well. If this is the only bug anyone has encountered, that's kinda awesome [emoji6].
However, as I don't have a pair of headphones to test with and possibly reproduce the issue, can one of you (or both) please get a log? I just need someone to reproduce the issue while taking a logcat and attach it here so I can diagnose and fix the issue.
Click to expand...
Click to collapse
There is a manual or some guide to do that? Please

asesinodilusion said:
There is a manual or some guide to do that? Please
Click to expand...
Click to collapse
There are basic instructions in the OP to take logs on the device using Matlog. There is also a decent tutorial here on xda: [Tutorial] How To Logcat

Jleeblanch said:
Someone mentioned this on telegram as well. If this is the only bug anyone has encountered, that's kinda awesome [emoji6].
However, as I don't have a pair of headphones to test with and possibly reproduce the issue, can one of you (or both) please get a log? I just need someone to reproduce the issue while taking a logcat and attach it here so I can diagnose and fix the issue.
Click to expand...
Click to collapse
https://www.dropbox.com/s/rqz2t7d57epq7i9/data.txt?dl=0
I hope this help

BT Calling not working
Hello together,
i installed th RR Rom on my phone and everything seems to be fine.
BUT the only thing is, "Bluetooth Calling" does not work. I tried it with to different Bluetooth devices, my oneplus wireless bullets, and my car.
No Microphone and no Sound is Working, very rare.
But when i do BT Calling with SIGNAL or VOIP app CSipSimple everthing is fine. It looks like, that the only problem is the telefone app itself from android pie.
Before i used the [ROM][UNOFFICIAL]LineageOS-16.0[Evert][Moto G6 Plus] and BT Calling was working fine!
Does someone have a tip for me, where i can take a look?
Thanks a lot.
Greetings

It works very well, except for the detail that sometimes there is lag and when making or receiving a call there is too much noise
Enviado desde mi Moto G6 Plus mediante Tapatalk

titofariasl said:
It works very well, except for the detail that sometimes there is lag and when making or receiving a call there is too much noise
Enviado desde mi Moto G6 Plus mediante Tapatalk
Click to expand...
Click to collapse
Is there any way of improving in-call audio quality? There is just too much background noise.

[ROM][H830,H850][UNOFFICIAL] LineageOS4Microg 15.1 [8.1] - 2020 Build (by Bernie_nix)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* I'm not responsible for bricked devices, damage, loss of Google services, you getting fired because the alarm app failed, etc. Do this at your own risk.
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications.
* Your warranty may/will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
About LineageOS4MicroG & LineageOS
LineageOS unofficial fork with built-in microG gapps implementation.
Full Play Services compatibility [Well-almost...YMMV]
Our ROM has built-in microG free-as-in-freedom re-implementation of Google's proprietary Android user space apps and libraries. This enables you to use every Google service you need without keeping another closed-source binary blob in your Android system.
Native F-Droid support
LineageOS for microG comes with F-Droid already installed. You can use it to access plenty of FOSS applications or even a Play Store bridge repository like Playmaker or GPlayWeb.
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 8 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Learn more at:
LineageOS: https://lineageos.org/
LineageOS4MicroG: https://lineage.microg.org/
Click to expand...
Click to collapse
Rom Built by Bernie_nixWhy build Oreo Now? What about other variants of the G5?:
Oreo is very stable on the h830 and works great with microg. I'm using this build now. This is also a build I am interested in maintaining and comparing to a future Pie build with microg built-in. Unfortunately, Android 17/Q is not yet fully compatible with microg.
Working:
5ghz WiFi, camera, calling, bluetooth, great battery life. USB-C audio earbuds work great. Reported that NFC works.
You tell me.
Known issues:
Please test WiFi, NFC. IR blaster not working for me but I may need to find a suitable app; please test. FM radio reported not working.
Automatic updates not yet implemented but will be in next build.
You tell me.
Install Instructions (If coming from another rom):
Prerequisites: Coming from another rom with Developer settings enabled, android debugging enabled.
(1) Boot into twrp (or ofox)
(2) Wipe your device. Select Wipe button, Advanced Wipe, Choose: Dalvik/ART Cache, Data, Internal Storage, System. Then Swipe to Wipe all of these (if in twrp. if in ofox, wipe system but do not wipe system 10)
(3) Select Format Data Button. Type yes
(4) Select Install button. Choose rom zip. Swipe to confirm flash.
(5) Install Magisk if you choose.
(5) Press back arrow button 2x to get back to main screen. Select Wipe button. Select format data button. Type yes.
(6) Reboot. Phone may or may not mention "no os installed." Ignore it. Proceed with reboot. Phone will boot twice, then boot into lineageos4microg.
DO NOT install twrp installer/orange fox installer until after phone boots into lineageos4microg or it will not boot. After you have setup lineageos, you can then reboot into twrp and install orange fox or twrp and magisk if you choose. Do not ever install any GAPPS on this ROM. Reinstall of TWP/Ofox should not be required if upgrading (at least on Ofox).
Upgrade Instructions (If coming from my previous build):
Prerequisites: Developer settings enabled, android debugging enabled.
(1) Boot into twrp (or ofox)
(2) Select Install button. Choose rom zip. Swipe to confirm flash.
(3) Wipe caches.
(4) Magisk should persist after reboot but if not, go back into twrp/ofox and flash it.
DO NOT install twrp installer/orange fox installer until after phone boots into lineageos4microg or it will not boot. After you have setup lineageos, you can then reboot into twrp and install orange fox or twrp and magisk if you choose. Do not ever install any GAPPS on this ROM. Reinstall of TWP/Ofox should not be required if upgrading (at least on Ofox).
Tips for Use
1. Root can be enabled in this build (if not installing Magisk) by going to Developer Settings->Manage Root Access->Apps and ADB
2. To turn off battery led when charging, Settings>Apps & notifications>Notifications>Battery Light
3. To set up Microg,
(1) open MicroG app,
(2) press self-check, press battery optimizations ignored and allow,
(3) go back one screen, select unified nlp settings, configure location backends, press the checkbox next to mozilla location service and ok, configure address lookup backends, press checkbox next to nominatum and ok,
(4) then go through Google services from top to bottom and enter your information.
(5) Enable location from pull-down shade. Open maps, get your location. Go back to Microg. Run self-check. All boxes should show a check.
(6) Microg is setup in less than 5 minutes and fully working.
(7) Turn off location from pull-down shade bc they're tracking you 4. Want a better GPS experience? Install Deja Vu Location Service, GSM Location Service and Radiocells.org Unified Network Location Provider Backend from F-Droid. Works great with Google Maps or OSM.
5. I've found Hypercam to take excellent pics with our cameras. Please download for the G5 here: https://gcambrasil.com.br/lg
Reporting bugs:
DO NOT Report bugs if you're running a custom kernel or you installed Xposed.
Please report bugs in this thread.
Logcats are helpful but not required. Grab a full logcat right after the problem has occurred.
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
Thread Purpose & Limits
This thread has been created to discuss the installation and use of this rom. If you have questions about building roms, this thread is not the place to do it. Please create a thread under Q/A; doing so allows many users to assist you and will help to keep this thread on-topic. Failure to follow this request will result in a warning followed by report to XDA if continued. Some excellent resources for building microg include https://lineage.microg.org/ and https://8192.one/post/lineage_build_with_docker/.
New Builds:
Mar. 5, 2020 Change log
1. Latest security update
Status: Stable
ROM OS Version: 8.x Oreo
Security Patch level: Mar. 5, 2020
H830 Download link: https://www.androidfilehost.com/?fid=4349826312261742170
H830 MD5: 8bd86770d84b94a5d999489c7f993db6
H850 Download link: https://www.androidfilehost.com/?fid=4349826312261742710
H850 MD5: 6fe7febb5b4f994a1f32af18390a988c
Older Downloads:
Feb 29, 2020 Change log
1. Latest sources
2. Root option enabled in development settings
Status: Stable
ROM OS Version: 8.x Oreo
Security Patch level: Feb. 5, 2020
H830 Download link: https://androidfilehost.com/?fid=4349826312261734920
H830 MD5: 017e4f8352f670e1d409bbce34490178
H850 Download link: https://www.androidfilehost.com/?fid=4349826312261735367
H850 MD5:fb428e8a245e06d66037a4254b519ebf
Source and Additional Links
https://github.com/LineageOS
https://github.com/LineageOS/android_device_lge_msm8996-common
Last Updated Mar. 11, 2020
Thanks to x86cpu's posts, Dark98, Electimon, Gabi and the countless others who helped me out!

Will test the h850 build as soon as you release it! :good:

I would love this for the h840! Oreo and security patches sounds great.

ml11ML said:
Will test the h850 build as soon as you release it! :good:
Click to expand...
Click to collapse
Build posted. See link in first post.

LollipopLover said:
I would love this for the h840! Oreo and security patches sounds great.
Click to expand...
Click to collapse
I would love to build for the h840, unfortunately it seems harder to build for. Not seeing a whole lot of sources or development on that variant.

Thank you anyway. I'll always have hope.

Thanks, @Bernie_nix this rom is super stable I was wondering how you build LineageOS4Microg the instructions on their website didn't make sense to me. Thanks so much for this rom. Will you make Pie builds?

ROMSG said:
Thanks, @Bernie_nix this rom is super stable I was wondering how you build LineageOS4Microg the instructions on their website didn't make sense to me. Thanks so much for this rom. Will you make Pie builds?
Click to expand...
Click to collapse
Yes I will continue forward to make an los 16 microg build. As far building yourself, please read the first post. I will not answer any questions related to building in this current thread after my response below.
I'm going to put together some info on GitHub with required files and some instructions to build on Ubuntu. In a nutshell, you install docker on Ubuntu, install the microg docker container and then supply a manifest file for the docker to download sources, etc.
I don't provide support for building in my threads because it's off-topic and really adds quite a bit of support that is better provided in its own unique thread where many members can help. I would be happy to answer questions in a Q/A thread of its own, on GitHub or in a telegram group.
If anyone is reading this and knows of an active telegram group for the g5 please message me and I'd be happy to provide assistance there. Otherwise wait until I update on GitHub. I have my reasons but do happily share in the spirit of open source. A ROM release thread is not the place to do it.

Amazing rom! Just installed on my h850 and it works great! The suggested GCAM is also very good. I have tested NFC and it does work fine (tested only between 2 phones). The IR however seems to work very strange... I tested with the app irplus which does seem to transmit something the first time you press a button but then it just starts loop blinking the IR led like a notification led on off on off on off about every second until a reboot. You can see this by pointing another camera at it. Also i was just wondering if it's possible for you to somehow add fm radio? It worked great on the stock rom but I noticed that no custom roms seem to have it. It isn't something that would cause me to not use this great rom but it would be nice to have. Also.. I wiped everything in orange fox before installing including system10 before I noticed the warning about keeping that but it works fine so far. Do I need to do something about it or can I just ignore it? What even is system10? First time I've ever seen it on any device.

ml11ML said:
Amazing rom! Just installed on my h850 and it works great! The suggested GCAM is also very good. I have tested NFC and it does work fine (tested only between 2 phones). The IR however seems to work very strange... I tested with the app irplus which does seem to transmit something the first time you press a button but then it just starts loop blinking the IR led like a notification led on off on off on off about every second until a reboot. You can see this by pointing another camera at it. Also i was just wondering if it's possible for you to somehow add fm radio? It worked great on the stock rom but I noticed that no custom roms seem to have it. It isn't something that would cause me to not use this great rom but it would be nice to have. Also.. I wiped everything in orange fox before installing including system10 before I noticed the warning about keeping that but it works fine so far. Do I need to do something about it or can I just ignore it? What even is system10? First time I've ever seen it on any device.
Click to expand...
Click to collapse
Thank you for your kind words! I've been testing it on my h830, and it really has brought some new life to my device. Even my pictures aren't coming out yellow like they were on stock! Thank you for testing NFC, and I am glad to hear that works for you. I had similar results with the IR blaster, and that's one of the features I love about this phone; I will try to see if I can improve the functionality as at least it does turn on but unfortunately can't give an ETA; this will involve looking into some lg and lineage sources if they are available. I will also look into fm radio. As most custom roms are built off of a similar base, that explains why it doesn't work in most. It may not be possible to pull the files and include them in the rom, but I may be able to create a magisk module with some lg files; again can't give an ETA as I don't know what I will find or how long it will take. I will investigate though. As for system 10 in ofox, I haven't been able to find much if any documentation on it. As I didn't erase it on install and it booted, I figured best to be on the safe side

Bernie_nix said:
Thank you for your kind words! I've been testing it on my h830, and it really has brought some new life to my device. Even my pictures aren't coming out yellow like they were on stock! Thank you for testing NFC, and I am glad to hear that works for you. I had similar results with the IR blaster, and that's one of the features I love about this phone; I will try to see if I can improve the functionality as at least it does turn on but unfortunately can't give an ETA; this will involve looking into some lg and lineage sources if they are available. I will also look into fm radio. As most custom roms are built off of a similar base, that explains why it doesn't work in most. It may not be possible to pull the files and include them in the rom, but I may be able to create a magisk module with some lg files; again can't give an ETA as I don't know what I will find or how long it will take. I will investigate though. As for system 10 in ofox, I haven't been able to find much if any documentation on it. As I didn't erase it on install and it booted, I figured best to be on the safe side
Click to expand...
Click to collapse
I see. Anyway thank you for looking into the IR issue as I agree that it's a great feature and also the fm radio. I would not have any problems with it being a magisk module if it can't be added to the rom. And yes, the phone runs great with this rom so far. Very responsive and minimal battery drain even with my half dead battery that dies at 50%. It is definitely my new daily driver.

New build released to update to March 2020 security update. See 1st post for download links.

Bernie_nix said:
New build released to update to March 2020 security update. See 1st post for download links.
Click to expand...
Click to collapse
Installed on my h850 over the old build and wiped cache and it works. :good:

ml11ML said:
Installed on my h850 over the old build and wiped cache and it works. :good:
Click to expand...
Click to collapse
Great to hear. Thanks for your feedback!

Cnt install googleplay store.

mie_ayam said:
Cnt install googleplay store.
Click to expand...
Click to collapse
Its microg....a Google play replacement. Read the first post. That's the whole point of this ROM! I think you may be looking for regular lineageos.

this rom have low mic issue and low sound issue?

Zorcnecrophades said:
this rom have low mic issue and low sound issue?
Click to expand...
Click to collapse
I know that Los usually has lower sound. Haven't experienced the lower mic myself but I could be wrong. You could probably easily edit some mixer_path volumes if it is not to your liking.

Hi, real cool rom. thanx a lot. But: PicoTTS does not work. App shuts down in test. And Hdmi (or Slimport??) on an OTG does not work.
And the LG Camera Plus add-on-piece is not recognized
Is H850_v2.2-mk2000.zip compatible with this rom? or maybe H850_v0.3-BETA2-mk2000.zip?
(after Test) No its not, camera is not working with both kernels and Android says, thats the Vendor Image is not right, when i reboot. What ever that means
P.S. The rest is really stable after 2 days of testing.#
P.P.S. Changing BT Connections from one (Airpods Gen 2) to another (JBL Charge 2) while playing music reboots the phone.

Bernie_nix said:
Its microg....a Google play replacement. Read the first post. That's the whole point of this ROM! I think you may be looking for regular lineageos.
Click to expand...
Click to collapse
yes. because I am accustomed to downloading apps on Playstore. and some applications when we want to log in using a google account. can't log in using a google account that is included in the Google Microg app.
Thank this rom great . mybe this is litel bug.

[ROM][10]Android Open Source Illusion Project[perseus][Official]

INSTALLATION PROCEDURE:
CLEAN (This is also solve Mi Logo Bootloops)
1) In TWRP, Format Data
2) Reboot TWRP
3) Wipe System, Data, Cache and Dalvik
4) Flash Xiaomi EU (Stable v11.0.2.0 or Weekly v20.5.7)
5) Format Data
6) Reboot TWRP
7) Wipe System, Data, Cache and Dalvik
6) Flash AOSiP
7) (Optional) Flash Gapps & Magisk
7b) Don't flash Gapps package if you chose to flash the Gapps AOSiP build
8) Reboot into the system, and enjoy the illusion!
DIRTY (At your own risk)
1) In TWRP, flash AOSiP
2) (Optional) Flash Gapps & Magisk
2b) Don't flash Gapps package if you chose to flash the Gapps AOSiP build
3) Wipe Dalvik & Cache only
4) Reboot into the system, and enjoy the illusion!
KNOWN ISSUES:
NONE! All sensors, slider function, and AI button are all working!
If you find an issue, please let me know. Either via Telegram or here.

Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
Include your firmware versions in reports.
Mention any and all Magisk modules you might be using along with the Magisk version
If it is a random reboot, grab dmesg . (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.

FREQUENTLY ASKED QUESTIONS:
COMMUNITY?
We have a community of over 600 helpful Mix 3 users around the world.
Join us on Telegram if you need help or want to chat: https://t.me/MiMix3Global
FIRMWARE?
AOSiP will not flash unless you are on any Android 10 based firmware.
xiaomi.eu ROM includes firmware, so this is not needed if you flashed that during a clean install (unless you want to try a different firmware version).
If you like to be on the latest firmware or try different versions, you can grab it here.
Personally, I like the latest available global variant (stable or beta).
You can flash firmware at any time, without affecting your current installation.
WHICH GCAM WORKS BEST?
Urnyx05 v1.7
WHICH TWRP SHOULD I USE?
Mauronofrio v3.3.1-17
CLEAN OR DIRTY?
If you're coming from unofficials, you'll need to clean flash since these builds are SIGNED.
Once you're in, you can just take OTAs, no more need to clean flash.

Great ROM! Congratulations on obtaining the "Official" status.

Hello, thanks for this Rom ! I have issues with Android Auto and screen laggy and flickering when my phone is connected to my car. Also some elements of the UI are missing like navigation bar on the screen of the car. No problem with ArrowOS which is CAF based Rom. Is there any solution ? I desactivate material superposition on develloper settings and it's not changing.
Thanks in avance

romano64 said:
Hello, thanks for this Rom ! I have issues with Android Auto and screen laggy and flickering when my phone is connected to my car. Also some elements of the UI are missing like navigation bar on the screen of the car. No problem with ArrowOS which is CAF based Rom. Is there any solution ? I desactivate material superposition on develloper settings and it's not changing.
Thanks in avance
Click to expand...
Click to collapse
]
Thanks for reporting, I will look into this issue.

Constrabus said:
]
Thanks for reporting, I will look into this issue.
Click to expand...
Click to collapse
Thank you

Hey guys, happy to announce AOSiP 10 Stable officials!
Please see the announcement on the Twitter post for changes and info about this release.

Hi everyone! been quietly following the community for quite some times already and I figured I could register and give you some insights on this rom.
I've wiped everything, installed the latest firmware, rom, gapp and magisks.
Everything went smoothly, except magisk giving me some headache about the ctsprofile... a ****ing nightmare... I've had custom rom for the last 10 years or so, I know my way around and always find the tricks to make things works... but this time I almost gave up.
I ended up on youtube and found this gem.
S-TaGmNfKMg
Use termux and manually assign the fingerprint for the mix 3 and there you go.
So far everything is working fine, Bluetooth, gps, selfie slider, dt2w, nfc.
Now I'm monitoring for a battery drain. if the battery could last a typical day, that'l be great.
And thank a lot for everyone involved!
I'll keep you posted

bearminator91 said:
Hi everyone! been quietly following the community for quite some times already and I figured I could register and give you some insights on this rom.
I've wiped everything, installed the latest firmware, rom, gapp and magisks.
Everything went smoothly, except magisk giving me some headache about the ctsprofile... a ****ing nightmare... I've had custom rom for the last 10 years or so, I know my way around and always find the tricks to make things works... but this time I almost gave up.
I ended up on youtube and found this gem.
S-TaGmNfKMg
Use termux and manually assign the fingerprint for the mix 3 and there you go.
So far everything is working fine, Bluetooth, gps, selfie slider, dt2w, nfc.
Now I'm monitoring for a battery drain. if the battery could last a typical day, that'l be great.
And thank a lot for everyone involved!
I'll keep you posted
Click to expand...
Click to collapse
Just tested this on 1 MiMix 3 with AOISP [Unofficial] and on another MiMix 3 with ArrowOS 10.0 and it works on both devices like a charm.
Finally: ctsProfile true
Thank you for the hint including the little gem :good:

bearminator91 said:
Hi everyone! been quietly following the community for quite some times already and I figured I could register and give you some insights on this rom.
I've wiped everything, installed the latest firmware, rom, gapp and magisks.
Everything went smoothly, except magisk giving me some headache about the ctsprofile... a ****ing nightmare... I've had custom rom for the last 10 years or so, I know my way around and always find the tricks to make things works... but this time I almost gave up.
I ended up on youtube and found this gem.
S-TaGmNfKMg
Use termux and manually assign the fingerprint for the mix 3 and there you go.
So far everything is working fine, Bluetooth, gps, selfie slider, dt2w, nfc.
Now I'm monitoring for a battery drain. if the battery could last a typical day, that'l be great.
And thank a lot for everyone involved!
I'll keep you posted
Click to expand...
Click to collapse
Awesome, so glad everything is working for you.
Yes that is the magisk props module. I recommend anyone who is having SN issues to use this (You can technically set to any device and it will work).
I am actually using the same fingerprint that it sets for persues. The reason you pass with the module, is that It also modifies your security patch date - another validation requirement for cts is that your fingerprint date and your security patch date must be within the same month. However, since this is an official build, we do not want to change the security patch date in the build.
Anyway...... I am coming up with a way to satisfy both requirements and will hopefully be implemented into the next build.
Until then please use the module + 'props' command via any terminal to set any fp if you need SN.

ctsProfile false
Constrabus said:
Awesome, so glad everything is working for you.
Yes that is the magisk props module. I recommend anyone who is having SN issues to use this (You can technically set to any device and it will work).
I am actually using the same fingerprint that it sets for persues. The reason you pass with the module, is that It also modifies your security patch date - another validation requirement for cts is that your fingerprint date and your security patch date must be within the same month. However, since this is an official build, we do not want to change the security patch date in the build.
Anyway...... I am coming up with a way to satisfy both requirements and will hopefully be implemented into the next build.
Until then please use the module + 'props' command via any terminal to set any fp if you need SN.
Click to expand...
Click to collapse
Unfortunately, it didn't work here. Tested it, using the latest AOSiP Version (5/6/2020), Magisk/Props/BusyBox/Termux >> picked Xiaomi Mi Mix 3 (Android 10) fingerprint >> reboot:
ctsProfile false
What did I miss/do wrong? Do I have to pick a fingerprint which is different from the Xiaomi Mi Mix 3 one?

chromanju said:
Unfortunately, it didn't work here. Tested it, using the latest AOSiP Version (5/6/2020), Magisk/Props/BusyBox/Termux >> picked Xiaomi Mi Mix 3 (Android 10) fingerprint >> reboot:
ctsProfile false
What did I miss/do wrong? Do I have to pick a fingerprint which is different from the Xiaomi Mi Mix 3 one?
Click to expand...
Click to collapse
I have done this with 3 different MiMix3 now always following *exactly* the video and all the devices are showing "ctsProfile true" after the procedure. The instructions is showing 6 - Google and at the step thereafter 23 - Google Pixel 4 XL (10) so I picked the same.
Worth noting that with one of the devices I had to repeat the process because after rebooting the first time it somehow failed and Magisk was still showing "ctsProfile false".

Great ROM, thanks so much. Everything seems solid, there is just one thing that spoils it for me - is it possible to add a toggle for the charging light? Keeps me awake at night.

Tamsy said:
I have done this with 3 different MiMix3 now always following *exactly* the video and all the devices are showing "ctsProfile true" after the procedure. The instructions is showing 6 - Google and at the step thereafter 23 - Google Pixel 4 XL (10) so I picked the same.
Worth noting that with one of the devices I had to repeat the process because after rebooting the first time it somehow failed and Magisk was still showing "ctsProfile false".
Click to expand...
Click to collapse
Thanks for your advice but it's still not working. I assigned the Google Pixel 4 XL - fingerprint as described (also re-checking the instructions from within the youtube gem), rebooted, ctsProfile: false > did the same again, still no success. Any (other) ideas?
Appreciate your help!

chromanju said:
Thanks for your advice but it's still not working. I assigned the Google Pixel 4 XL - fingerprint as described (also re-checking the instructions from within the youtube gem), rebooted, ctsProfile: false > did the same again, still no success. Any (other) ideas?
Appreciate your help!
Click to expand...
Click to collapse
Have you checked with Magisk --> Settings --> Magisk Hide (<-- this should be set to "ON")?
Also below Settings --> Magisk Hide I set Magisk to hide itself from "Google Play Services".
It is worth a try.

Tamsy said:
Have you checked with Magisk --> Settings --> Magisk Hide (<-- this should be set to "ON")?
Also below Settings --> Magisk Hide I set Magisk to hide itself from "Google Play Services".
It is worth a try.
Click to expand...
Click to collapse
That did the trick: Magisk Hide wasn't enabled.
Thanks a lot!!

Found a bug... Gboard needs camera permission to create minis (personalised stickers like mimoji) but doesn't request it and can't be given it.

Is it possible to remove the google search bar from the home screen with this rom?

[ROM][UNOFFICIAL-ABANDONED][11] LineageOS 18.1 for Samsung Galaxy Note 3 (hlte*)

Reserved -- just in case.

Link to gapps?

My device is hlte N9005
LOS 18.1 20201226
While using YouTube Vanced in background with audio only the ui freezes for 5 or 10 seconds.
Same issue on LOS17 official build

Thank you @haggertk and Happy New Year! Android 11 on Note 3, unbelievable I clean flashed this rom on my hltekor without gapps. Everything is working fine, but sometime System UI was not responding.

here are the logs regarding with bluetooth audio crashing when playback. specifically it crashes then you skip tracks/videos on any application with audio output
currently on initial 20201227 build on hltekor variant. freshly flashed with magisk and nanodroid, and youtube, matlog, and mixplorer to simulate the crash and extract the logs and the tombstone of the said crash
any help would be appreciated
p.s. this issue has been persisted since lineage 16.0, as far as my usage goes, and this issue is experienced not only by me but also with other peers outside xda.

haggertk said:
Reserved -- just in case.
Click to expand...
Click to collapse
Nice ROM!! Can't flash magisk with lineage or twrp recoveries. Can't install .img's on lineage recovery either. Dope ROM though. Would you happen to know where I can get a twrp zip? Images won't flash

Rootmaster906 said:
Nice ROM!! Can't flash magisk with lineage or twrp recoveries. Can't install .img's on lineage recovery either. Dope ROM though. Would you happen to know where I can get a twrp zip? Images won't flash
Click to expand...
Click to collapse
I am running the room with magisk flashed through TWRP.... No problem here

Working great ,didint sxperiance any mayor issue.there are some minor things but for a second build i must say impressive work!!
The only known issue is with background apps stop working (like youtube vanced or music app) also happend on official 17.1 (dont know if it was fixed in later offical builds)

Installed And Tested
Works Like A Charm With 0 Problem!
<Thanks A Million>
But Which Gapps Package Should We Install?
I Only Found Gapps For Arm64 Android 11 But Hlte Has Arm Architecture.

Thankyou very much!! You made the Note3 still rock!
I want to ask if the upcoming Google Android system are not support 32bit CPU..? If that happens what would the future of Note3 will be...? Thanks!!

This is a sick ROM! It was weird that 64 bit GApps worked on this 32 bit chip, but anyways, here are the issues:
1. Sometimes, out of nowhere, the system will stop responding from 5 to 20 seconds for no reason, and then show me a message box saying whatever app I was on, has stopped responding, especially SystemUI.
2. I can't set a lock screen except for swipe. When I set one, in the next reboot, it starts bootlooping the system every 5 seconds. To fix it, I either had to wipe Data from TWRP, or go to the file manager, go to the system folder and delete the 2 files that started with the word "lock". Then, the issue went away, but I fear setting a lock pattern now.
3. Sometimes, for no reason, it turns off the screen into just a square, colored box with the clock on the top. I assume this is for those folding cases with a magnet on it, so, after a hard reset (using the physical buttons), I opened a Sensor Multitool app to see my magnetization sensor going haywire. The values were literally off the charts, into the thousands. After a few seconds, it got back to normal though, so that was weird. When it goes to that mode, nothing is possible to do, not even the power menu shows up, other than turn it off with force. This has happened to me a few times now and started happening on the 1st day I installed the ROM.
These issues may be only applicable to my device, but I am not sure. I used to have Android 10 before(more specifically, HavocOS 3.7) and didn't have these issues. I know this is an unofficial ROM, and it is amazing for what it is.
By the way, I am daily driving this OS.
My device: SM-N9005, hlte
Using the kernel that the ROM includes, not Lolz or any of that.
Edit: wait.. I downloaded this ROM from a different site and not here. It linked to files that were from November 30th and now that I took a look at them, the parent directory said "LineageOS 18.0". I'll install the ROM from here now, see how it performs.

ZahedanBoy1995 said:
But Which Gapps Package Should We Install?
Click to expand...
Click to collapse
Please see my answer here: https://forum.xda-developers.com/t/discussion-lineageos-18-1-hlte-chn-kor-tmo.4197123/

Microprod said:
This is a sick ROM! It was weird that 64 bit GApps worked on this 32 bit chip, but anyways, here are the issues:
1. Sometimes, out of nowhere, the system will stop responding from 5 to 20 seconds for no reason, and then show me a message box saying whatever app I was on, has stopped responding, especially SystemUI.
2. I can't set a lock screen except for swipe. When I set one, in the next reboot, it starts bootlooping the system every 5 seconds. To fix it, I either had to wipe Data from TWRP, or go to the file manager, go to the system folder and delete the 2 files that started with the word "lock". Then, the issue went away, but I fear setting a lock pattern now.
3. Sometimes, for no reason, it turns off the screen into just a square, colored box with the clock on the top. I assume this is for those folding cases with a magnet on it, so, after a hard reset (using the physical buttons), I opened a Sensor Multitool app to see my magnetization sensor going haywire. The values were literally off the charts, into the thousands. After a few seconds, it got back to normal though, so that was weird. When it goes to that mode, nothing is possible to do, not even the power menu shows up, other than turn it off with force. This has happened to me a few times now and started happening on the 1st day I installed the ROM.
These issues may be only applicable to my device, but I am not sure. I used to have Android 10 before(more specifically, HavocOS 3.7) and didn't have these issues. I know this is an unofficial ROM, and it is amazing for what it is.
By the way, I am daily driving this OS.
My device: SM-N9005, hlte
Using the kernel that the ROM includes, not Lolz or any of that.
Edit: wait.. I downloaded this ROM from a different site and not here. It linked to files that were from November 30th and now that I took a look at them, the parent directory said "LineageOS 18.0". I'll install the ROM from here now, see how it performs.
Click to expand...
Click to collapse
I downloaded the Rom from here and I have been having the same exact issues , I thought it was my device acting up ...Now I'm sure its an issue with the ROM

faheem200 said:
take logs instead of blabbering
Click to expand...
Click to collapse
The guy was giving a review of his experience with the ROM which is very useful to other people who want to try the ROM. If you feel it's blubbering you have the right to ignore it and let people who find it useful find use.

Excuse me, I want to ask that is this rom have navigation gesture? Cuz all of my navigation buttons are dead and the last time I install a Lineage 17 rom, it's doesn't have the gesture.
Thank you for your works :>

tienze070601 said:
Excuse me, I want to ask that is this rom have navigation gesture? Cuz all of my navigation buttons are dead and the last time I install a Lineage 17 rom, it's doesn't have the gesture.
Thank you for your works :>
Click to expand...
Click to collapse
No unfortunately it doesnt have

Hi, just share the gapps here...

howeiying said:
Hi, just share the gapps here...
Click to expand...
Click to collapse
Thank you. Those gapps work including google maps not force closing.

Database Info

welcome