[OFFICIAL] LineageOS 19.1 for Moto G6 Plus - Moto G6 Plus ROMs, Kernels, Recoveries, & Other De

[OFFICIAL] LineageOS 19.1 for Moto G6 Plus - Moto G6 Plus ROMs, Kernels, Recoveries, & Other De

Can I upgrade from the unofficial build to the official - or do I need to wipe all and start from scratch?

I prefer you start clean, but you can try, if you flash mindthegapps as Gapps package, it will be the same as shipped on unnoficial build

works great

Unofficial builds are still the best

@jeferson1979 hola bro es que la rom instalo correctamente pero al arrancar se queda cargando en el logo y dura mas de 5 horas alli y no sigue que hago

FlySwit Designer said:
@jeferson1979 hola bro es que la rom instalo correctamente pero al arrancar se queda cargando en el logo y dura mas de 5 horas alli y no sigue que hago
Click to expand...
Click to collapse
You can press power button with vol - and enter recovery mode, then select format data (hint: you will loose your data), then things should work.
Make sure to follow wiki steps before install anything.

I am on the official build with the recommended gapps (MindtheGapps-latest version) installed.
I am getting the following error with I try to run Google Opinion Rewards:
google opinion rewards won't run without google play service which are not supported on your device
I have tried clearing data/cash for Google Play, Google Play Services and the Opinion Rewards, restarting and that doesn't help.
Any ideas/suggestions? Thank you in advance for your assistance.

ew said:
I am on the official build with the recommended gapps (MindtheGapps-latest version) installed.
I am getting the following error with I try to run Google Opinion Rewards:
google opinion rewards won't run without google play service which are not supported on your device
I have tried clearing data/cash for Google Play, Google Play Services and the Opinion Rewards, restarting and that doesn't help.
Any ideas/suggestions? Thank you in advance for your assistance.
Click to expand...
Click to collapse
How was the install procces? Some people said about similar stuff ( another kind of gapps issues) and what fixed was install rom, finsish this install, reboot to recovery and then install gapps. Otherwise, send us a log here if still remains bugging

jeferson1979 said:
How was the install procces? Some people said about similar stuff ( another kind of gapps issues) and what fixed was install rom, finsish this install, reboot to recovery and then install gapps. Otherwise, send us a log here if still remains bugging
Click to expand...
Click to collapse
Thanks for the assistance. For background, I was coming from the unofficial and upgraded to the official. I believe it was working, but I may have done something (and I don't know what) and it stopped working.
I even tried wiping the system partition and reinstalling - and that didn't help.
I wound up wiping my entire system (flashing back to stock) - and installing the official (including the recommended gapps) - and all is good.
And (by the way) I did reboot to recovery before installing gapps.
Thanks for the help. I guess this one will remain a bit of a mystery (as to what happened) but it is all working now.

ew said:
Thanks for the assistance. For background, I was coming from the unofficial and upgraded to the official. I believe it was working, but I may have done something (and I don't know what) and it stopped working.
I even tried wiping the system partition and reinstalling - and that didn't help.
I wound up wiping my entire system (flashing back to stock) - and installing the official (including the recommended gapps) - and all is good.
And (by the way) I did reboot to recovery before installing gapps.
Thanks for the help. I guess this one will remain a bit of a mystery (as to what happened) but it is all working now.
Click to expand...
Click to collapse
It's the annoying part of a release early days XD

Hi, I've installed both the mod and Gapps following the instructions on the website (I had a PixelExperience ROM before) and - from what I am seeing - all went smooth.
Thanks a lot for your effort.
P.S. Is there a Telegram channel for LineageOS?
edit: the only "weirdness" I've seen: two apps warn me that phone is rooted. For one I can continue the installation, for the other is not possible. Not a big issue, but this did not happen with the Pixel Experience ROM.
Thanks again.

Hello, guys!
I recently installed the official 1.19.1 ROM and the Gapps provided and I'm getting "Offline" even if I am connected on WiFi. Browsing on internet works perfecly, but I get the messages as on the image below:
Also, when I click in Google, from the Settings Menu, I get the message: Unable to start the App.
I think its something related to the Gapps.. Maybe?
Or the issue is because I'm not using a simCard at the moment?
Imma using the MindTheGapps-12.1.0-arm64-20220416_174313, on my Moto G6 Plus Evert, and used lineage-19.1-20220426-nightly-evert-signed zip package to format.
Is this a common issue?
I reinstalled the ROM just to be sure, but I still get this.

I have been on this ROM for a day now - and it is very smooth. No major issues and thanks to the OP for the time and support!
A few small items that I have mostly found workarounds for but wanted to mention them for anybody that is interested:
I really like TWRP over the lineage recovery. On LOS 18.1 I was able to flash TWRP and use it. That doesn't seem to be an option for 19.1. Even though I have turned encryption off (so the encryption is not an issue) - it seems like it doesn't boot properly after installing TWRP. So, I guess I need to live with lineage recovery.
The green flash & dot that comes up when location is used is really annoying. The dot not as much as the flash - especially since I have apps that use location all of the time and the flash is distracting and removes other elements on the notification bar. I was able to use the information https://forums.oneplus.com/threads/android-12-little-green-dot-location.1572637/ and https://forum.xda-developers.com/t/...nsor-indicator-microphone-and-camera.4388359/ to help things, however sometimes after a reboot I have to turn the switch back off in developer options. Bit of a pain, and I have not found a way to turn it off automatically through tasker.
Auto brightness - in dark my screen gets too dark. I have to raise it - and it doesn't seem to be learning to use a higher minimum - like some other versions of android.
Relatively speaking - these are minor and maybe just things that bug me. The ROM is very smooth, fast and much appreciated!

I also want to report what seems a minor bug: when the display auto-rotation is enabled, no icon is shown in the status bar, but instead an icon is shown when it is not. In stock version and Pixel Experience mod the feature had the opposite behavior (so an icon was shown only when auto-rotation was enabled).
Thanks again, all seems to work pretty well.

Mattew Rockstone said:
Hello, guys!
I recently installed the official 1.19.1 ROM and the Gapps provided and I'm getting "Offline" even if I am connected on WiFi. Browsing on internet works perfecly, but I get the messages as on the image below:
View attachment 5604917
Also, when I click in Google, from the Settings Menu, I get the message: Unable to start the App.
I think its something related to the Gapps.. Maybe?
Or the issue is because I'm not using a simCard at the moment?
Imma using the MindTheGapps-12.1.0-arm64-20220416_174313, on my Moto G6 Plus Evert, and used lineage-19.1-20220426-nightly-evert-signed zip package to format.
Is this a common issue?
I reinstalled the ROM just to be sure, but I still get this.
Click to expand...
Click to collapse
Same issue for me and my evert.

For the guys with the "offline" issue: flash rom, then reboot to recovery, then flash mindthegapps. This will solve your connection issue

now, 3 month later finish guarantee, my charger burned out
happy, becase i was in the same room and stop fire, if i wasnt-maybe burnt all house!!!!!
be carefull-when are you charging everething

ew said:
The green flash & dot that comes up when location is used is really annoying. The dot not as much as the flash - especially since I have apps that use location all of the time and the flash is distracting and removes other elements on the notification bar. I was able to use the information https://forums.oneplus.com/threads/android-12-little-green-dot-location.1572637/ and https://forum.xda-developers.com/t/...nsor-indicator-microphone-and-camera.4388359/ to help things, however sometimes after a reboot I have to turn the switch back off in developer options. Bit of a pain, and I have not found a way to turn it off automatically through tasker.
Click to expand...
Click to collapse
It is possible to disable the "green dot" when geolocation is used using the developers' options. I have an Italian-localized OS but it should be the last option in the menu, named sort of "Location indicator in the status bar". When the option is disabled, the green dot doesn't appear anymore and when an app uses the GPS only the standard icon is shown.
This thing has come handy with the last update (2022-05-17) since it introduces an annoying bug that should be fixed with the next update
Phone Services using location even when its turned off. (#4674) · Issues · LineageOS / issues / android · GitLab
Expected Behavior No app should be able to use location when its turned off and phone services app should not keep...
gitlab.com

the_15th said:
It is possible to disable the "green dot" when geolocation is used using the developers' options. I have an Italian-localized OS but it should be the last option in the menu, named sort of "Location indicator in the status bar". When the option is disabled, the green dot doesn't appear anymore and when an app uses the GPS only the standard icon is shown.
This thing has come handy with the last update (2022-05-17) since it introduces an annoying bug that should be fixed with the next update
Phone Services using location even when its turned off. (#4674) · Issues · LineageOS / issues / android · GitLab
Expected Behavior No app should be able to use location when its turned off and phone services app should not keep...
gitlab.com
Click to expand...
Click to collapse
Thanks for your help. I found that the switch in the developer options got reset after reboot.
The following is my solution as implemented in Tasker. I run this at system start.
Task: Green Dot Location Suppress (A12)
<need to have the following commands in the following sequence for it to work:
-device_config put privacy location_indicators_endabled false default
-device_config put privacy camera_mic_icons_enabled false default
-device_config put privacy camera_mic_icons_enabled true default
Per my testing, the commands need to be executed in the sequence listed above - otherwise it does not work.
see https://forums.oneplus.com/threads/android-12-little-green-dot-location.1572637/
https://forum.xda-developers.com/t/...nsor-indicator-microphone-and-camera.4388359/>
A1: Anchor
A2: Run Shell [
Command: device_config put privacy location_indicators_enabled false default
Timeout (Seconds): 0
Use Root: On
Use Global Namespace: On ]
A3: Run Shell [
Command: device_config put privacy camera_mic_icons_enabled false default
Timeout (Seconds): 0
Use Root: On
Use Global Namespace: On ]
A4: Run Shell [
Command: device_config put privacy camera_mic_icons_enabled true default
Timeout (Seconds): 0
Use Root: On
Use Global Namespace: On ]

Related

[ROM][STABLE][R7S/R7Sf][OFFICIAL][9.0] LineageOS 16.0 (Qualcomm)

*reserved*

Please make sure before upgrading to LineageOS 16.0 to read the Official Instructions here in LOS Wiki carefully!
Make sure before flashing you upgrade the TWRP version with the one provided in the instructions page due to changes to support hardware accelerated encryption on our R7S!
You will run into issues if you do not upgrade to the provided TWRP version!
I recommend a clean install due to above changes.

Followed the instruction exactly but wifi does not work (mac address 02:00:00, it can not find any AP...)
If someone has this issue like me, flash back to Spectrum then boot into it and connect to some AP, then flash LineageOS again, but do not wipe anything.

Does Pixel Launcher work for you?
It crashes on my phone. A workaround: https://www[.]reddit[.]com/r/LineageOS/comments/awjvnk/lineageos_16_stock_open_gapps_pixel_launcher/

Working well so far even though I updated using twrp 3.2.3
Only issues are, app permissions seem to show up when they want and bluetooth connection can be ropey depending on device. Have one receiver with no issues but my Sennheisers cant keep a connection from two feet. Will try re-pairing.
Thanks to you all. :highfive:
I needed this for root, so for anyone who needs it...
https://mirrorbits.lineageos.org/su/20190304/addonsu-16.0-arm64-signed.zip
Edit.....Just updated to latest build and root disappears so the above will be needed.
Will the SU binaries be reinstalled for future builds?

LordAlberto said:
I needed this for root, so for anyone who needs it...
https://mirrorbits.lineageos.org/su/20190304/addonsu-16.0-arm64-signed.zip
Edit.....Just updated to latest build and root disappears so the above will be needed.
Will the SU binaries be reinstalled for future builds?
Click to expand...
Click to collapse
Why not use Magisk?

trmdi said:
Why not use Magisk?
Click to expand...
Click to collapse
I do use magisk, I need to install this beforehand or magisk doesn't work.
When I first installed 16, I read that lineage removed the su binaries so there is no root out of the box.
Bit of a pain really.

When the screen is locked, you're still able to swipe down from the status bar to expand it to show buttons. Is there any way to disable expanding the status bar when the screen is locked?

Just tried the recommended TWRP image and it screwed it up. Now i have no recovery! I'll have to attach to a computer to see if I can reflash it to get back in. Anyone else try this with the same result?

Hi, is there any difference between the build 16-04 and 17-04 ? No changelog is shown.
https://download.lineageos.org/r7sf/changes/

Luuta said:
Just tried the recommended TWRP image and it screwed it up. Now i have no recovery! I'll have to attach to a computer to see if I can reflash it to get back in. Anyone else try this with the same result?
Click to expand...
Click to collapse
The recommended TWRP image is actually a lower version than the official image through the TWRP app, and that's why my recovery got screwed up. I'd flashed an earlier image onto a later one. The recommended one would probably be the one to use if you were switching to Lineage for the first time, maybe? Just to warn people not to be as careless as I am!
I spent half a day messing about with getting the tools again to perform a flash from my pc. Every time, I end up relying on "Minimal ADB & Fastboot" because I have no luck getting any other driver package to work. But this package really is the smallest pack to get it done and it makes it easy to use, thank goodness.
Thanks to the developers for continuing to work on the phone. I'm loving Android 9/Lineage 16. There isn't much of a visual change, which is great. Under the hood, it's more obvious, but it's definitely running much smoother than L15 already.
---------- Post added at 08:41 PM ---------- Previous post was at 08:39 PM ----------
trmdi said:
Hi, is there any difference between the build 16-04 and 17-04 ? No changelog is shown.
https://download.lineageos.org/r7sf/changes/
Click to expand...
Click to collapse
There will, of course, be changes, or it wouldn't be offered. Most changes are bug fixes or security updates, so you wouldn't necessarily notice any change.

Maybe the gestures are sensitive but every time I go out, the phone always opens my music player at destination. Have turned them off see if it happens again.
Never happened on 15.

Bluetooth seems to be a mixed bag so far. When it works it's fine, but when connection is lost re-pairing and forget/connect can be hit and miss. It will show the device but not be connected so you have to go deeper into settings to fix it.
More often I always end up going the long way round just to get connection.
BT ended up rock solid on 15 so I'm confident it'll improve.
Update. So clearing storage and cache in 'App info' seems to have fixed connection issue. Let's see how we get on...

LordAlberto said:
Bluetooth seems to be a mixed bag so far. When it works it's fine, but when connection is lost re-pairing and forget/connect can be hit and miss. It will show the device but not be connected so you have to go deeper into settings to fix it.
More often I always end up going the long way round just to get connection.
BT ended up rock solid on 15 so I'm confident it'll improve.
Update. So clearing storage and cache in 'App info' seems to have fixed connection issue. Let's see how we get on...
Click to expand...
Click to collapse
1
Mine keeps connecting, disconnecting, connecting... But only when there's no music playing, like it's trying to save power (so maybe it's one of the battery saving services under Android 9). Mine isn't forgetting, though. At least not yet...

Luuta said:
1
Mine keeps connecting, disconnecting, connecting... But only when there's no music playing, like it's trying to save power (so maybe it's one of the battery saving services under Android 9). Mine isn't forgetting, though. At least not yet...
Click to expand...
Click to collapse
Tried again today, it has the device listed but wont connect. Have to go all the way in BT menu to connect manually.
It's a problem with Pie on the whole apparently.

LordAlberto said:
Tried again today, it has the device listed but wont connect. Have to go all the way in BT menu to connect manually.
It's a problem with Pie on the whole apparently.
Click to expand...
Click to collapse
Ah, yes, it loses the pairing in our car, too. It's a small annoyance, can live with that!

is anyone success to install magisk on this rom ?

spongelovers said:
is anyone success to install magisk on this rom ?
Click to expand...
Click to collapse
yes. I flashed it right after flashing the rom without any problem.

spongelovers said:
is anyone success to install magisk on this rom ?
Click to expand...
Click to collapse
On page one of this thread I've linked the su code to get magisk to install.

[10][OFFICIAL] CarbonROM | cr-8.0 [z3c]

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.

[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][11][flox][OFFICIAL] crDroid 7.31Google Nexus 7 2013 repartitioned

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:
Flox is how LineageOS has chosen to name the repartitioned version of flo, which means that if you haven't repartitioned your Nexus 7 2013 you must repartition it before even trying to flash this. Please read LineageOS instructions here before trying anything.
Pre-installation:
Recovery (TWRP Lineage Recovery)
gapps arm (MindTheGapps OpenGapps)
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/mantinan/android_kernel_google_msm
Device: https://github.com/LineageOS/android_device_asus_flox
Download:
ROM
Known issues:
When scanning the face unlock the camera shows left side of video Ok but right side darkened, cameras seem to work ok on other apps.
Visit official website @ crDroid.net
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs

bestiatester said:
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/10.0/README.mkdn
Flashing Instructions:
Flox is how LineageOS has chosen to name the repartitioned version of flo, which means that if you haven't repartitioned your Nexus 7 2013 you must repartition it before even trying to flash this. Please read LineageOS instructions here before trying anything.
Pre-installation:
Recovery (TWRP Lineage Recovery)
ROM (Download from here)
gapps arm (MindTheGapps OpenGapps)
Sources:
ROM: https://github.com/crdroidandroid
Download:
ROM
Known issues:
Battery is shown as charging at 0 mA.
When scanning the face unlock the camera shows left side of video Ok but right side darkened, cameras seem to work ok on other apps.
Visit official website @ crDroid.net
crDroid <device> Telegram
crDroid Community Telegram
Donate to help our team pay server costs
Click to expand...
Click to collapse
OH MY GAWD I'M IN LOVE everything working great here. This rom is surprisingly smooth with MicroG installed. Long live the Nexus 7!

Mr.Conkel said:
OH MY GAWD I'M IN LOVE everything working great here. This rom is surprisingly smooth with MicroG installed. Long live the Nexus 7!
Click to expand...
Click to collapse
Can you share the steps you used to get microG to work? I am having a hard time getting them to work on LOS 18.1 and This ROM as well!

GeekyTanuj said:
Can you share the steps you used to get microG to work? I am having a hard time getting them to work on LOS 18.1 and This ROM as well!
Click to expand...
Click to collapse
Well the steps can be different on Los 18.1 because Signature spoofing is not built in to Los but it is on Crdroid which makes it was less of a pain because you don't need Xposed for things to work correctly.
So starting with Crdroid go about your normal setup and install Magisk per normal. Afterwards you're going to need to select a package from this link normally minimalAP or the Standard package should be just fine. These packages have everything you need to get MicroG working with the Google Play store the only difference between minimal is Aurora Services and the location backends which a tablet doesn't necessarily need but it depends on what you use it for.
After flashing this through recovery follow these steps..
Initial Setup:
- Complete the setup wizard actions as you prefer
- Open the app drawer and long-press on Play Store to choose the App Info button
- Go to Permissions, then Additional permissions and change Spoof package signature to Allow, go back to home screen afterward
- Run the microG Settings app — The rest of these instructions are taken almost directly from https://gitlab.com/Nanolx/NanoDroid/-/blob/master/doc/microGsetup.md
- Choose Self-Check at the top of the list, and start tapping on the second item, System grants signature spoofing permission which should prompt a permission request
- Everything should now be checked on the Self-Check screen, go back to main microG Settings screen
- Choose Google device registration and enable the Register device switch, then go back
- Choose Cloud Messaging and enable the Receive push notifications switch, then go back
- SafetyNet doesn't actually work or pass right now, but you can try enabling it in the same manner as above
- Choose Location modules and enable at least one "Network-based Geolocation module" and one "Address lookup module". I usually only turn on Deja Vu Location Service from the top list; it seems to work well enough for driving directions here, and of course choose Nominatim from the lower list because it's the only one there
- This is important: Reboot now before you add a Google account or do anything else to the Play Store app
- After rebooting, go back into microG Settings app and make sure that all of the Self-Check items are still checked, and then make sure that Google Device Registration, Cloud Messaging, and SafetyNet are still enabled — if they were not, enable them.
- Now get app info for Play Store, clear cache (yes, again), then launch the app
- Add your Google account, and verify that it will show your app library — Purchased apps won't show as paid-for yet, this will take approximately 24 hours until Google decides it likes your new Android ID
- Open Settings app, then Accounts then choose your Google account, then chose Personal info & privacy, and make sure Allow apps to find accounts is enabled
- That should be everything!
Then after a few hours (a day or so) you should have complete access to you paid apps and you're good to go. Let me know if you need anything else!

Mr.Conkel said:
Well the steps can be different on Los 18.1 because Signature spoofing is not built in to Los but it is on Crdroid which makes it was less of a pain because you don't need Xposed for things to work correctly.
So starting with Crdroid go about your normal setup and install Magisk per normal. Afterwards you're going to need to select a package from this link normally minimalAP or the Standard package should be just fine. These packages have everything you need to get MicroG working with the Google Play store the only difference between minimal is Aurora Services and the location backends which a tablet doesn't necessarily need but it depends on what you use it for.
After flashing this through recovery follow these steps..
Initial Setup:
- Complete the setup wizard actions as you prefer
- Open the app drawer and long-press on Play Store to choose the App Info button
- Go to Permissions, then Additional permissions and change Spoof package signature to Allow, go back to home screen afterward
- Run the microG Settings app — The rest of these instructions are taken almost directly from https://gitlab.com/Nanolx/NanoDroid/-/blob/master/doc/microGsetup.md
- Choose Self-Check at the top of the list, and start tapping on the second item, System grants signature spoofing permission which should prompt a permission request
- Everything should now be checked on the Self-Check screen, go back to main microG Settings screen
- Choose Google device registration and enable the Register device switch, then go back
- Choose Cloud Messaging and enable the Receive push notifications switch, then go back
- SafetyNet doesn't actually work or pass right now, but you can try enabling it in the same manner as above
- Choose Location modules and enable at least one "Network-based Geolocation module" and one "Address lookup module". I usually only turn on Deja Vu Location Service from the top list; it seems to work well enough for driving directions here, and of course choose Nominatim from the lower list because it's the only one there
- This is important: Reboot now before you add a Google account or do anything else to the Play Store app
- After rebooting, go back into microG Settings app and make sure that all of the Self-Check items are still checked, and then make sure that Google Device Registration, Cloud Messaging, and SafetyNet are still enabled — if they were not, enable them.
- Now get app info for Play Store, clear cache (yes, again), then launch the app
- Add your Google account, and verify that it will show your app library — Purchased apps won't show as paid-for yet, this will take approximately 24 hours until Google decides it likes your new Android ID
- Open Settings app, then Accounts then choose your Google account, then chose Personal info & privacy, and make sure Allow apps to find accounts is enabled
- That should be everything!
Then after a few hours (a day or so) you should have complete access to you paid apps and you're good to go. Let me know if you need anything else!
Click to expand...
Click to collapse
Thanks for this guide! Really helped me get things going smoothly! Love this ROM.

Hi,
I need dt2w but i can't activate it, does thé kernel support it?
Can you Hello me please?
Thanks you

jojo33680 said:
Hi,
I need dt2w but i can't activate it, does thé kernel support it?
Can you Hello me please?
Thanks you
Click to expand...
Click to collapse
you need to use the Exkernel to enable dt2w. Here's the latest one: Link.

I am running an old 7.0 Resurrection ROM on my N7.
TWRP is installed & bootloader unlocked so I suspect I would just need to repartition & install?
No clue why ADBgives me these errors in powershell.
fastboot : The term 'fastboot' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ fastboot
+ ~~~~~~~~
+ CategoryInfo : ObjectNotFound: (fastboot:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

For those who have partition with a different method like me that is NOT flox so they can flash other ROMs, replace this in the ROM zip. All I did was remove assert get prop that checks to make sure your tablet is the right one for the ROM. It won't flash if you're not using flox repartition so I changed it to allow it to flash. I have 1.6gb of system space and am able to flash this ROM, opengapps pico, magisk and custom kernel with no issues running a non flox repartition.
updater-script
drive.google.com

Hi!
In the known issues I descrived:
When scanning the face unlock the camera shows left side of video Ok but right side darkened, cameras seem to work ok on other apps.
Can anybody please confirm that this is happening also for you?
And if you know why it is failing or even better, how to fix it... that would be great
Thanks in advance.

bestiatester said:
Hi!
In the known issues I descrived:
When scanning the face unlock the camera shows left side of video Ok but right side darkened, cameras seem to work ok on other apps.
Can anybody please confirm that this is happening also for you?
And if you know why it is failing or even better, how to fix it... that would be great
Thanks in advance.
Click to expand...
Click to collapse
I confirm I have the same problem

Hello all,
I follow the guides and the installation went smoothly, thanks for the really good job you've done.
I'm new in the crDroid world so sorry if the question seems stupid: As the power button of the Nexus 7 is not easy to access, how can I activate the double tap to wakeup ?
Some years ago the tablet was installed with aicp, and the DT2W was working. So I'm a little bit disappointed if it is not working now.
Thanks.

Davidtre07 said:
DT2W
Click to expand...
Click to collapse
This material will help you: 01 ... 02 ... 03 ... 04

lyushiK said:
This material will help you: 01 ... 02 ... 03 ... 04
Click to expand...
Click to collapse
With Anykernel installed works like a charm !
Thanks.

Davidtre07 said:
With Anykernel installed works like a charm !
Thanks.
Click to expand...
Click to collapse
If you have a patch or pointer to the code that makes it work... just let me know and I'll try to add it.

I'm testing a patch for the charge current to be shown ok, seems to work, if all the tests are ok I'll ship it in with the next release.

No I don't have any patch to propose, I just followed the links provided by @lyushiK.
As far I understood, to work you have to recompile a kernel with DT2W hability and you have to activate it with the right flag in the kernel.
From my side what I've done:
Installed Magisk (patched boot.img)
Installed this kernel: https://androidfilehost.com/?fid=7161016148664820402
And to finish added to magisk this module: https://github.com/ipdev99/mModule_dt2w
Reboot and it works !

In Magisk I see the module is looking in /sys/ for "doubletap*" or "dt2w*" or "wake_gesture".
If it found one of the files then activate it (echo 1 in the file)
But still, you have to have the right kernel !

Thanks very much, this Rom is so smooth and running great. The only thing I've noticed is that the icon size and text is very small when using the tablet in landscape mode but fine in portrait mode. Any changes I make to the icon size from the settings apply in portrait but when switched to landscape stay as really small, is there any setting I have missed to enlarge them?

Thank you for the great work!
Just for feedback: I can confirm the camera issue, too, though it doesn't bother me.
Another small thing I noticed: during the initial setup my device was called Pixel 6 Pro (first I thought, I chose the wrong image) but in the settings it says correctly "Nexus 7".

Database Info

welcome