Related
Welcome to wilson3q's CM12 Unoffical Build!
As requested by some users, I started to build cm12 for I605. I don't own a I605, please help to test. If you like my work, you can donate here.
Disclaimer: I take no responsibility for bad things that happen as a result of flashing this.
My kernel source is standard cm12 kernel without any modifications.
SaberMod tool chain source is HERE.
All the rests are pretty standard cm12 stuffs, except a few patches I applied on top of them.
[Download]
ROM (please don't mirror):
build - 20150513
build - 20150602
Gapp:
http://forum.xda-developers.com/android/software/gapps-google-apps-minimal-edition-t2943330
Recommended launcher:
Nova Launcher (really like its JB zoom app animation, hate L slide up animation)
Recommended theme:
Deep Darkness
If you need enable soft buttons, flash this: View attachment softkeys.zip or soft+hardkeys.zip
[Flashing Guide]
1. Reboot to CWM/TWRP recovery
2. Flash ROM zip file
3. Flash Gapps
4. Reboot
* Wipe data first if you come from another rom *
* Newer boot loader, modem and recovery is highly recommended (don't use twrp 2.8.4, use 2.8.1 instead) *
* No other kernel will be supported, use the stock one, for your best experiences too *
[Patches]
My additional patches over cm12 includes:
Enhancements and bug fixes cherry-picked from other ROMs, including Slim LP, Nameless
SaberMod for ROM and kernel
O3, JustArchi optimization
Pthread enabled & strict aliasing
Latest sqlite db library
Added Boeffla sound engine 1.67
Added CPU governor zzmoove, smartassv2, savagedzen
Added io scheduler row, bfq, zen, vr
Disabled some useless Samsung processes
Fixed GPS
Fixed low in call volume
Video playback forward/backward fix
Removed all kernel debuging stuffs
Fixed keyboard not showing up during setup wizard
Fixed a crash of music app
Changed DPI to 280
Fixed Camera issue
Fixed Day Dream
Fixed Netflix streaming (one more reboot needed after installation of Netflix)
Enabled Multi-user
LMK minfree tweaks
Misc tweaks
more...
For better experience, change Nova animation/scroll speed to Fast...
[Known Bugs]
I am not sure what issues you will get, but one thing is for sure: YOUR PHONE WILL FLY!
chrome glitch: type chrome://flags as URL and disable GPU thank @bigmarv31)
Thank cm team for the amazing ROM.
Thank sabermod for the amazing toolchain.
Special thanks to: @DerTeufel1980, @sbrissen, @rogersb11, @TheBr0ken, @DreamFX, @frankie...
[Screenshots]
Always nice to see a new thread for i605. This doesn't happen often. Thank you!
Thanks again for building this for us we all appreciate it!
will be testing this out and see how it spars. thanks for this! I was going to try and "port" it over from the t0lte with replacing some libs and such, lol.
Thank you! I'm downloading right now. Looking like a slow day at work, so why not?
Downloaded files. Backed everything up. Rebooted to recovery. Wiped / Factory Reset using TWRP. Installed both zips sequentially. Apprehensive when I rebooted. Took a couple of minutes of sweating watching the CM Logo swirl around, and then bam! I'm up and running Lollipop. I'll update soon...
UPDATE
thefinancemaster said:
Downloaded files. Backed everything up. Rebooted to recovery. Wiped / Factory Reset using TWRP. Installed both zips sequentially. Apprehensive when I rebooted. Took a couple of minutes of sweating watching the CM Logo swirl around, and then bam! I'm up and running Lollipop. I'll update soon...
Click to expand...
Click to collapse
So, I've got it up and running. It's fast and smooth, but there's a couple of glaring issues stopping me from testing any farther. The first screen that comes up after you initially select your language, is a new (to me) "Activating Cellular Service" screen. It has a message on the screen saying this "can take up to 5 minutes". I let it go for longer than that, but I got an error that it was unable to activate and I was able to try again, or skip it. I'll skip it for now just to see how the rest of the ROM works. Next screen is Wifi login, works fine., but you still have to hit "skip" even after you sign in to wifi.
Then it checks connections, for updates, etc and I keep getting the error that google play services has stopped. I haven't even logged into it yet...
Next screen is Tap N Go. Option to transfer all of your stuff off your old phone using NFC. Great idea, but I'm not testing because my new phone IS my old phone.
Then, it's google login time. Worked fine, standard stuff we're used to with options to download/backup your apps using google. It takes a minute here, and I kept getting popups about all of the google apps stopping, each individually. Annoying a bit... I hit the "RESTORE" option, this is my second try, and the first time I didn't have Root, so I couldn't download Titanium to restore everything. I also skipped the google restore last time, so I tried it this time. This is a new screen for me, but it takes me to a "Restoring" screen for a bit. It's not as annoying as on previous Android versions, having to individually approve each app that was updating/downloading. I keep getting the popups about one Google app or another stopping.
I get past the restore page, and the phone locks up. Reboot... After reboot, I have to go into the play store to download Titanium. It seems quite a few apps were restored by Google, but not all. I looked at the "My Apps" section of the play store, and there's a ton of apps cued up to download. It's what I was trying to avoid... So I hit "Stop" at the top, and it stops them all.
**I mentioned earlier that this is my 2nd try, the first try was about the same, but I didn't have root access. I downloaded SuperSU, but it wouldn't update the binaries, so it was useless. I tried SuperUser, it didn't work either. So, I rebooted to recovery, wiped, flashed the ROM, GApps, and the SuperSU zip I had saved on my SD card from my previous Omni Rom. Then I rebooted and now you can read what happened.
At this point, I'm having problems downloading Titanium Backup, SuperSU, or anything I really want. The Play Store is hanging and force closing. I can't even open the SuperSU I flashed from TWRP. There must be compatibility issues. I read somewhere that Lollipop has issues with root somehow, but I'm not sure. On my first try, I was able to download Titanium Backup no problem, but it wouldn't work because I didn't have root access. SuperSU and SuperUser didn't help after downloading. CM has always been pre-rooted on all of the other devices I've installed it on.
For now, I'm just going to restore my backup of Omni Rom and be content with 4.4.4 for now.
I'll try again if anyone can help with actually being on the VZW Network and Root. I didn't get a chance to play with the other stuff in Lollipop yet, but I would love to.
thefinancemaster said:
So, I've got it up and running. It's fast and smooth, but there's a couple of glaring issues stopping me from testing any farther. The first screen that comes up after you initially select your language, is a new (to me) "Activating Cellular Service" screen. It has a message on the screen saying this "can take up to 5 minutes". I let it go for longer than that, but I got an error that it was unable to activate and I was able to try again, or skip it. I'll skip it for now just to see how the rest of the ROM works. Next screen is Wifi login, works fine., but you still have to hit "skip" even after you sign in to wifi.
Then it checks connections, for updates, etc and I keep getting the error that google play services has stopped. I haven't even logged into it yet...
Next screen is Tap N Go. Option to transfer all of your stuff off your old phone using NFC. Great idea, but I'm not testing because my new phone IS my old phone.
Then, it's google login time. Worked fine, standard stuff we're used to with options to download/backup your apps using google. It takes a minute here, and I kept getting popups about all of the google apps stopping, each individually. Annoying a bit... I hit the "RESTORE" option, this is my second try, and the first time I didn't have Root, so I couldn't download Titanium to restore everything. I also skipped the google restore last time, so I tried it this time. This is a new screen for me, but it takes me to a "Restoring" screen for a bit. It's not as annoying as on previous Android versions, having to individually approve each app that was updating/downloading. I keep getting the popups about one Google app or another stopping.
I get past the restore page, and the phone locks up. Reboot... After reboot, I have to go into the play store to download Titanium. It seems quite a few apps were restored by Google, but not all. I looked at the "My Apps" section of the play store, and there's a ton of apps cued up to download. It's what I was trying to avoid... So I hit "Stop" at the top, and it stops them all.
**I mentioned earlier that this is my 2nd try, the first try was about the same, but I didn't have root access. I downloaded SuperSU, but it wouldn't update the binaries, so it was useless. I tried SuperUser, it didn't work either. So, I rebooted to recovery, wiped, flashed the ROM, GApps, and the SuperSU zip I had saved on my SD card from my previous Omni Rom. Then I rebooted and now you can read what happened.
At this point, I'm having problems downloading Titanium Backup, SuperSU, or anything I really want. The Play Store is hanging and force closing. I can't even open the SuperSU I flashed from TWRP. There must be compatibility issues. I read somewhere that Lollipop has issues with root somehow, but I'm not sure. On my first try, I was able to download Titanium Backup no problem, but it wouldn't work because I didn't have root access. SuperSU and SuperUser didn't help after downloading. CM has always been pre-rooted on all of the other devices I've installed it on.
For now, I'm just going to restore my backup of Omni Rom and be content with 4.4.4 for now.
I'll try again if anyone can help with actually being on the VZW Network and Root. I didn't get a chance to play with the other stuff in Lollipop yet, but I would love to.
Click to expand...
Click to collapse
Did you flash the andriod 5 gapps? Do a full wipe?
You also need latest twrp recovery or philz touch recovery...
baseband unknown no data
bigmarv31 said:
baseband unknown no data
Click to expand...
Click to collapse
Will fix this today.
Keep a close look.
wilson3q said:
Will fix this today.
Keep a close look.
Click to expand...
Click to collapse
Yes Sir Thanks
New build online...
Giving this a try!! Downloading now
Update- Downloaded and installed without any problems. I did have to skip the network verification set-up as it never went anywhere and wifi set-up worked as with setting up my g-mail account,.
Everything seems good except for no service, baseband version still unknown and no service or apn's for data.
going back to Liquid till this gets updated.
LvnInOC said:
Giving this a try!! Downloading now
Update- Downloaded and installed without any problems. I did have to skip the network verification set-up as it never went anywhere and wifi set-up worked as with setting up my g-mail account,.
Everything seems good except for no service, baseband version still unknown and no service or apn's for data.
going back to Liquid till this gets updated.
Click to expand...
Click to collapse
Can you get a logcat?
I guess my proprietary blobs are not correct...
wilson3q said:
Can you get a logcat?
I guess my proprietary blobs are not correct...
Click to expand...
Click to collapse
I already went back to Liquid but I dont mind doing another try at it especially if it would benefit. let me get ir flashed and try to get you the Logcat
. give me a few
---------- Post added at 05:38 AM ---------- Previous post was at 05:10 AM ----------
ok so I got this flashed again strange this time after booting it said no sim card inserted and to insert my sim, it was not out and i skipped and moved to wifi , setup worked all the way and I got a log cat, hope I did it correct as this is new to me. I have to re-flash to Liquid for now so that I have a working phone as I go to work in an hour,
Again let me know if you need any more details
Same on this build baseband unknown so no data
wilson3q said:
Did you flash the andriod 5 gapps? Do a full wipe?
You also need latest twrp recovery or philz touch recovery...
Click to expand...
Click to collapse
Yes, I flashed the gapps from your post. gapps-lp-20141109 is what the file name was. I use TWRP, not sure if it's the latest but it works fine. I always do the "factory reset" wipe option in twrp, because I believe that's a full wipe with one swipe... Now, just to test it out and see if I was doing something wrong, I tried the Liquid Smooth build (latest nightly) from 1/7, and it loaded and booted just fine. Had to flash the ROM, Gapps, GPS Fix, and Super SU (so I can restore my apps in Titanium). It connected to data, and ran me through the setup in a flash. It's working well enough to be a daily driver. Do you have any other suggestions? I'm willing to help if you want me to try something else.
Going to give this a try. Thank you for giving this phone options. It is greatly appreciated.
"Chance Favors the Prepared"
glockman4519 said:
Going to give this a try. Thank you for giving this phone options. It is greatly appreciated.
"Chance Favors the Prepared"
Click to expand...
Click to collapse
You're like me you change roms by the hour.
DreamFX said:
You're like me you change roms by the hour.
Click to expand...
Click to collapse
I love to flash and then go through a process of testing. I actually got 2 gt-n5110s so I could test a couple builds at same time, kind of a back to back comparison.
I would love to pick up another i650 that still has unlocked bootloader for testing that way on this device as well.
Well back to this rom, I couldn't get past the getting data screen and had to abort. I did a clean flash and wiped everything with both philz and TWRP 2.8.3.0. I tried both stock and shift kernels.
Lets face it, I'm a flashaholic. lol.....
"Chances Favors the Prepared"
LineageOS Android Distribution 14
Lineage OS Android Distribution is the continuation of the now discontinued CyanogenMod.
Instructions1. Make a Nandroid backup using TWRP or similar custom recovery if flashing from a different ROM.
2. Download the latest LineageOS ROM (uploading) and copy it to either the internal storage, an SD card, or an OTG usb drive.
3. Download a Nougat (7.1) Google Apps Package (GApps) for ARM devices if desired (OpenGApps recommended).
4. Boot into the custom recovery to flash the ROM and/or GApps .
5. Factory reset if flashing from a different ROM.
XDA:DevDB Information
Unofficial LineageOS, ROM for the Sprint HTC EVO 4G LTE
Contributors
Source Code: https://github.com/LineageOS
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: HBOOT 2.10.0000 or 2.10.5555
Version Information
Status: Testing
Current Beta Version: lineage-14.1-20170302
Beta Release Date: 2017-03-02
Created 2017-01-22
Last Updated 2017-03-02
I'm going find this phone in one of the shoe box and install this thank you kind sir
Wow Los has finally arrived for the Jewel but my Jewel is no longer with me
I can't seems to use external sdcard as internal there's simply no option to do it while formatting. Other then this it's pretty snappy thanks again.
mecha2012 said:
I can't seems to use external sdcard as internal there's simply no option to do it while formatting. Other then this it's pretty snappy thanks again.
Click to expand...
Click to collapse
Thanks for testing! Try the new Nougat build—I wasn't able to move apps onto the SD card (that is a LineageOS bug), but I was able to format it as internal storage.
I couldn't install the latest build 14.1 well just keeps bootlooping at the HTC screen.
Wipe
Install latest build
Install Gapps 7.1 (tried without installing this also) still no go ?
mecha2012 said:
I couldn't install the latest build 14.1 well just keeps bootlooping at the HTC screen.
Wipe
Install latest build
Install Gapps 7.1 (tried without installing this also) still no go
Click to expand...
Click to collapse
There appears to be an error in the build. I will upload a new build within a day.
Edit: New build has been uploaded! Please report if it works.
Never thought my Jewel would ever see Nougat (let alone Lollipop or Marshmallow). Just flashed and all is working well so far. Awesome work!
God tier work here, I'm blown away. I misplaced my Moto G 3rd gen somewhere in my apartment, so I've given up and dusted off my Evo. I was set to just use the Viper 4.1.1 that was on there, but some apps weren't installing so I came on ol' XDA. This is much more than I expected, thank you.
With that said, any tips on getting this to activate on Sprint / Ting? It was working fine on the old rom, but not kicking in here.
I know this isn't totally related to this ROM, but maybe it can be. I'm having issue with this (and most other ROMs I try) where the per button works physically, but only the buttons light up. I have to press the power button several times to get the screen to wake. This isn't consistent though. Seems worse if the screen has been off for a while. Does anyone know of a fix, and if so, can it be incorporated into this ROM? I know there have other threads about this but it seems like they have been dropped.
idumych said:
God tier work here, I'm blown away. I misplaced my Moto G 3rd gen somewhere in my apartment, so I've given up and dusted off my Evo. I was set to just use the Viper 4.1.1 that was on there, but some apps weren't installing so I came on ol' XDA. This is much more than I expected, thank you.
With that said, any tips on getting this to activate on Sprint / Ting? It was working fine on the old rom, but not kicking in here.
Click to expand...
Click to collapse
I believe that the service must be activated on a stock ROM before flashing a custom ROM. Then, the correct APN has to be set according to the carrier under Settings > More > Cellular networks > Access Point Names.
Schiben said:
I know this isn't totally related to this ROM, but maybe it can be. I'm having issue with this (and most other ROMs I try) where the per button works physically, but only the buttons light up. I have to press the power button several times to get the screen to wake. This isn't consistent though. Seems worse if the screen has been off for a while. Does anyone know of a fix, and if so, can it be incorporated into this ROM? I know there have other threads about this but it seems like they have been dropped.
Click to expand...
Click to collapse
I am not sure of a fix, and I have not encountered this issue, but have you tried enabling Wake device using the Camera button under Settings > Buttons?
VitaTaf said:
I am not sure of a fix, and I have not encountered this issue, but have you tried enabling Wake device using the Camera button under Settings > Buttons?
Click to expand...
Click to collapse
I've tried that in the past. Forgot about it this time around. Tried it again and it seems to be about the same as the actual power button for getting the screen to come on correctly.
Good ol' Jewel. Is this rom working ok?
My wife is temporarily using my old Jewel because she dropped & broke her crappy samsung phone. can someone please tell me how this rom is working?
I appreciate your time!
King of the Couch said:
My wife is temporarily using my old Jewel because she dropped & broke her crappy samsung phone. can someone please tell me how this rom is working?
I appreciate your time!
Click to expand...
Click to collapse
The ROM is working fine for the most part. The battery is not great, but that may be due to the battery's age. Additionally, there is a bug with BoringSSL that sometimes prevents the Play Store or Gmail from working temporarily.
sounds good. yeah, I'm sure it's age. thanks man. take care-
Trouble with WiFi
Did a Full factory reset, installed rom, gapps, and supersu from TWRP, factory wipe again from TWRP; now the OS is installed and running but after connecting to my home network, says no internet access although the netork is up and running normally, all other devices connected. Any thoughts or suggestions. I have a backup of my previous state, so I can revert, but would like to keep this on 7.1 for consistency between this and my primary device. The primary use for this device is media streaming.
keysneptune said:
Did a Full factory reset, installed rom, gapps, and supersu from TWRP, factory wipe again from TWRP; now the OS is installed and running but after connecting to my home network, says no internet access although the netork is up and running normally, all other devices connected. Any thoughts or suggestions. I have a backup of my previous state, so I can revert, but would like to keep this on 7.1 for consistency between this and my primary device. The primary use for this device is media streaming.
Click to expand...
Click to collapse
I believe that the WiFi issue have been fixed in the latest build (20170522).
Thank you for this rom!
I had been using cyanogenmod 5.0 and dirtyunicorns 5.1 both were solid roms. Unfortunately the latest apps seem to run a bit slow on them. I thought it was the device but after installing this rom everything is snappy! It manages 1gig of ram better than any other rom and that 1.5ghz dualcore still runs strong. Snapchat is way more responsive on this rom, instagram and fb run without problems. GPS, 4g, sms, wifi, camera, sd storage, everything works! I've only noticed a few bugs. The wifi activity arrows don't show when something is downloading/uploading but wifi itself does work. Also, even tho I have working active cell service, it tries to activate itself again everytime I reboot and fails but calls-sms-data continue to work lol. The biggest bug is that auto-rotation stops working after 30-60 minutes and it stays stuck on portrait mode. Nothing but a full reboot will get it working again, a quick softboot won't fix it. I've tried changing the rotation settings and also added some lines to the build.prop but no solution thus far. I love this rom so much, if it's not fixed I might try some auto rotation apps. One last thing, it would be cool if the # in the status bar would go away after I close whatever app has root. The previous rom I had did that. Thank you so much to all the developers for bringing life to this phone!
familyjewels said:
I had been using cyanogenmod 5.0 and dirtyunicorns 5.1 both were solid roms. Unfortunately the latest apps seem to run a bit slow on them. I thought it was the device but after installing this rom everything is snappy! It manages 1gig of ram better than any other rom and that 1.5ghz dualcore still runs strong. Snapchat is way more responsive on this rom, instagram and fb run without problems. GPS, 4g, sms, wifi, camera, sd storage, everything works! I've only noticed a few bugs. The wifi activity arrows don't show when something is downloading/uploading but wifi itself does work. Also, even tho I have working active cell service, it tries to activate itself again everytime I reboot and fails but calls-sms-data continue to work lol. The biggest bug is that auto-rotation stops working after 30-60 minutes and it stays stuck on portrait mode. Nothing but a full reboot will get it working again, a quick softboot won't fix it. I've tried changing the rotation settings and also added some lines to the build.prop but no solution thus far. I love this rom so much, if it's not fixed I might try some auto rotation apps. One last thing, it would be cool if the # in the status bar would go away after I close whatever app has root. The previous rom I had did that. Thank you so much to all the developers for bringing life to this phone!
Click to expand...
Click to collapse
Thanks for trying out the ROM! The WiFi activity arrows are intentionally disable on LineageOS. I do not currently have an active cell service on this device, so I am unable to fix the activation bug for now. Could you flash the patch below in recovery and test if autorotation is working properly? It should also enable the option to hide the Superuser icon under "Status bar" > "System icons".
Hi everyone,
My phone has this restarting loop issue after flashing either Candy7 or CM13 ROM. Not sure if this is bootloop error because It got pass the Huawei booting logo, but as soon as it finish loading the Google App and go to the OS home screen it restart again and again. Worth noting that the phone restart from ROM loading logo (the blue face for CM13 or the Google Dot for Candy7), not all the way back from Huawei booting logo.
First I use TWRP to factory reset wipe, then advance wipe /system, /data, /cache / Dalvik, then install new ROM + Gapp, and got the sucess message, then reboot to system.
I also tried with out Gapp to save loading time, and it restart again when get to OS home screen.
Please advise what may cause this.
No issue when i restore back to B322 EMUI 3.1
I have US version unlocked MT2-L03, B322 version, unlocked bootloader, rooted, TWRP 3.1.1.0 installed.
I made a video clip of the looping: https://www.youtube.com/watch?v=Y7kRpdGN2qA
I'm going through the EXACT same thing. I tried CM13, CM14 and even CandyRom, and the same thing happened more or less. Even if I got the ROMs running for a while, eventually that LOD (Loop of Death) would hit and I'd have to again reflash. I'm now back to B322 (Lollipop) for stability.
Given that the SAME thing is happening on all those ROMs, it's leading me to think that perhaps there is a software issue with my phone. Not sure if this helps, but I do think it could be the way I updated to Lollipop (B322) from the original Jelly Bean (B148). I've done a LOT of digging, and it looks like the way I did it was not quite right, even though my phone has worked fine all this time.
Here is the XDA post that seems to detail the correct upgrade path to B322:
https://forum.xda-developers.com/ascend-mate2/help/how-to-update-unlocked-mt2-l03-to-t3422775
Basically, it looks like the correct path should be B148 (Jelly Bean) --> B309 (Lollipop) --> B322 (Lollipop)
Being rather new, I just flashed to B322 right off of B148. I am now wondering if this could be the source of my problems. Especially since I keep getting the "Error 7" for "unknown bootloader" whenever I use TWRP 3.1.1 to flash LineageOS or CandyRom.
But, if you successfully used TWRP 3.1.1 to flash, that means your bootloader was recognized (I got the Error 7). If that's the case, then we're both having the same issue and something else is indeed the culprit.
I strongly suspect that "something else" could be GAPPS. I've experimented with several GAPPS packages, and noticed that right before crashing and the dreaded infinite loop, something glitched involving Google apps.
Desperately want to leave Lollipop since Oreo is about to drop meaning we Android L users are in for a world of hurt if we can't migrate soon. :-\
I upgrade my phone B148-B309-B322. I also get error 7 whenever I flashed the ROM, so I have to manually delete '"assert" command line from ROM script to flash successfully.
Error screen shot: http://imgur.com/zzTbjRJ
hondaman82 said:
I upgrade my phone B148-B309-B322. I also get error 7 whenever I flashed the ROM, so I have to manually delete '"assert" command line from ROM script to flash successfully.
Error screen shot: http://imgur.com/zzTbjRJ
Click to expand...
Click to collapse
My phone has been rooted for over a year now, I've had many roms on it doing that time. This loop started with a app I updated from the play store. Not sure it may be substratum will look into it when I have more time..
These problems is because of the room. Try to install lineageOs.
Thanks Kevinoriej,
Same looping issue on LineageOS, after loading to OS homescreen , phone restart.
Also get error 7, and manually remove "assert" lines in the ROM script in order to flash.
hondaman82 said:
I upgrade my phone B148-B309-B322. I also get error 7 whenever I flashed the ROM, so I have to manually delete '"assert" command line from ROM script to flash successfully.
Error screen shot: http://imgur.com/zzTbjRJ
Click to expand...
Click to collapse
I believe the Error 7 message is because your bootloader is showing as "unknown". I downloaded an app from the Playstore that gave me my device's technical info, and sure enough, my bootloader is listed as "unknown". I forwarded a question to Huawei's EMUI team asking them if that happened due to unlocking it (using Huawei's official unlocking request). Still waiting for a replay. In order to get any of the ROMs to install, I had to downgrade TWRP to 2.8.7.0. Any version above that would trigger Error 7.
Out of curiosity, I then downgraded and flashed CandySix (with a corresponding GAPPS package) - and sure enough, the same looping happened. And again when I flashed CM13 AND LineageOS. The phone would successfully boot, get to the actual Start screen, and then boot again. I could NEVER predict exactly what triggered this. Also, I tried installing ROMs without GAPPS, and that didn't go well for me (couldn't get any of them to load properly without flashing a GAPPS package for some reason).
Something goofy seems to be happening between Google services and the custom ROMs on this phone. I'm not sure what's triggering it, but given the sheer number of different ROMs I've tried - ALL of which have the EXACT SAME ISSUE - I strongly suspect there is indeed a GAPPS problem lurking somewhere.
As a side note - I reflahsed B322 (restoring from backup) and the phone is again as stable as it has always been.
Is there an EMUI GAPPS package for Marshmallow and/or Nougat (i.e., pulled from Mate 7, 8 or 9) available for download? I'm game for testing.
RE: MT2 boot loop
(*** SEE POST #25 FOR UPDATED FIX!***)
I just noticed this thread, wish I found it earlier. I recently posted my discussion of the boot loop (and fix) here:
https://forum.xda-developers.com/ascend-mate2/orig-development/cm-nougat-mt2-t3478345/page14
Bratzilla was right when he said in his post, "I strongly suspect there is indeed a GAPPS problem lurking somewhere".
Thanks EndlessFall,
please help to check this link: github(dot)com/opengapps/arm/releases/download/20170811/open_gapps-arm-7.1-pico-20170811.zip
no files listed.
RE: dead link for Open GApps previous versions & boot loop fix
Strange, it seems that in the past day Open GApps has purged their GitHub archive. The "Older Releases" button at their website still redirects to the GitHub repo, but it no longer displays any version other than the current one.
As long as it does not violate any policy, I can always post a copy of the Open GApps 08/11/17 ARM 7.1 Pico package.
Although I have not tried other GApps distributions (Delta, Beans, etc), in theory there is no reason why they shouldn't work, as long as Google Play Services is not newer than v11.3.02. I recommend the minimal GApps available. Installing "pico" was an important part of isolating, and simplifying the search for, the culprit.
As I mentioned in my original post, I tested all versions of Google Play Services on apkmirror newer than v11.3.02 (build format 436 for MT2L03), up until 08/26. All newer builds induced an immediate boot loop. A future version may resolve the boot loop issue and work fine on the MT2L03, but it does not seem to be available as of today.
Have been running custom ROMs on my MT2L03 for years. Boot looping problem began for me two weeks ago when I completely wiped/formatted my CandyROMs v7.1.2 06/15 install and flashed MDMower's 08/19 LineageOS. Began digging deep into the cause (knowing MDMower would not release garbage) and discovered the connection to Play Services. Have been running MDMower's LineageOS & CandyROMs v7.1.2 ever since without any issues.
Remember to use MDMower's TWRP v3.1N0-0, it is much more stable on the MT2L03.
Thanks again Endless,
I follow your instruction to flash Candie ROM and the matching GAPP from 6/15, all went well, no more bootloop. I will check the phone from time to time to see if the Loop of death come back, maybe once GAPP get updated it may come back. LOL... hopefully not though.
RE: MT2 boot loop fix (workaround)
Great, hondaman82 - so glad it worked for you. Funny, the exact same environment that you are using (06/15 CandyROMs with the matching 06/15 Open GApps) is what served as my "proof of concept" that current Open GApps with updated Play Services was likely the problem.
Although the proper GApps package resolves the boot loop issue, it is important to point out that it's more of a workaround than a fix. The root cause might be a bug in the AOSP/LineageOS source code itself, preventing MT2L03 compatibility with the latest versions of Play Services.
MDMower has just released a new build of LineageOS dated 08/29/17. I'll continue to test the latest ROMs with the latest GApps & Play Services to see if new commits/updates fix the problem...
hondaman82 said:
Thanks again Endless,
I follow your instruction to flash Candie ROM and the matching GAPP from 6/15, all went well, no more bootloop. I will check the phone from time to time to see if the Loop of death come back, maybe once GAPP get updated it may come back. LOL... hopefully not though.
Click to expand...
Click to collapse
EndlessFall said:
Great, hondaman82 - so glad it worked for you. Funny, the exact same environment that you are using (06/15 CandyROMs with the matching 06/15 Open GApps) is what served as my "proof of concept" that current Open GApps with updated Play Services was likely the problem.
Although the proper GApps package resolves the boot loop issue, it is important to point out that it's more of a workaround than a fix. The root cause might be a bug in the AOSP/LineageOS source code itself, preventing MT2L03 compatibility with the latest versions of Play Services.
MDMower has just released a new build of LineageOS dated 08/29/17. I'll continue to test the latest ROMs with the latest GApps & Play Services to see if new commits/updates fix the problem...
Click to expand...
Click to collapse
Have you had the chance to try 0829 Build of Lineage OS with newer GApps? TIA.
Oh nooo.. the LOD (loop of death) come back, after 3 days of working OK... sigh.... back to EMUI stock
RE: new ROM builds, GApps, & boot loop issue
Yes, I tested MDMower's LineageOS 08/29 last night using the 08/29 Open GApps package. Unfortunately, the boot loop bug persists. However, the 08/29 LineageOS runs great with Open GApps 08/11 and is worth installing (at least for me). Hopefully MDMower will keep up the good work and release a build in the next week or two with the Sept security patch.
I'll continue to test and report back if there is any progress...
MT2-User said:
Have you had the chance to try 0829 Build of Lineage OS with newer GApps? TIA.
Click to expand...
Click to collapse
EndlessFall said:
Yes, I tested MDMower's LineageOS 08/29 last night using the 08/29 Open GApps package. Unfortunately, the boot loop bug persists. However, the 08/29 LineageOS runs great with Open GApps 08/11 and is worth installing. Hopefully MDMower will keep up the good work and release a build in the next week or two with the Sept security patch.
I'll continue to test and report back if there is any progress...
Click to expand...
Click to collapse
Thanks!
RE: return of boot loop
Sorry to hear that Hondaman82.
I can only speak from my own experience, which is that my MT2L03 has been stable for the past 2 weeks using Open GApps pico dated no later than 08/11. It is possible that your Google Play Services was auto-updated to a version newer than v11.3.02 (inducing the loop), but you won't be able to tell because you can't boot the corrupted OS to read the version number in app settings. If my boot loop returns, I'll do an ADB pull from TWRP to examine the Play Services package version (curious to see if there is an update correlation).
Goes to show what I mentioned yesterday, which is that the root cause is likely some incompatibility between the ROMs customized for MT2L03 and Play Services that can only be fixed by a commit to the ROM source code, a script, patch, or change to Play Services.
Let's see what happens, perhaps MDMower would be willing to offer his expertise? I visited Matt's website, GitHub and XDA profile, but it seems difficult to contact him directly....
hondaman82 said:
Oh nooo.. the LOD (loop of death) come back, after 3 days of working OK... sigh.... back to EMUI stock
Click to expand...
Click to collapse
RE: preventing Google Play Services auto-update
(***SEE UPDATED FIX IN POST #25!***)
For those of you willing to experiment further, there is a method that supposedly disables Google Play Services from updating. This might allow you to "lock in" v11.3.02 until there is a proper fix for the boot loop:
https://forum.xda-developers.com/android/help/delete-disable-downgrade-prevent-update-t3091832
Basically, this involves using a root file manager to create two empty folders entitled "com.google.android.gms-1.apk" and "com.google.android.gms-2.apk" in the "\data\app" directory, causing auto-update to fail.
I haven't used this hack, try at your own risk!
Of course, this works off of the assumption that updating Google Play Services beyond v11.3.02 is the only factor involved in the boot loop. I just haven't dug deep enough...
Mine (Candy 0725 build) went into LOD by itself a moment ago
Does anyone have a B322 TWRP backup ZIP? I as of this morning have 2 MT2 phones dead. One went into LOD about 3am and the other about 4am.
This ROM is Going to be Primary Based on LineageOS 15.0 source or ROM compiled with Base as LineagesOS 15.0
I am going to regularly compile it and going to share it with community over here
Features of This ROM Based on LineagesOs 15.0
Customizable Theme Engine (Blend with Substratum)
Picture in Picture Mode of Android Oreo
Notification Dots
New user interface in Settings
Split Screen
Improved battery life
Notification Snoozing
Android Oreo Navbar
New UI in Status Bar and Quick Tiles
New Emojis based on Android Oreo
And much more.
Download
For Nexus 6 Android file Host
Gapps For Oreo
Opengapps You can get that from Oppengapps.org
Gaapps For 8.1 Till Open gapps start official Build
The Build is from @Nezorflame And Gapps downlod from
Do NOT expect daily builds. I'll build when I'm free.
Do NOT use this unofficial build and ask for support at the official threads.
Do NOT be rude.
Respect all users
If you see a NOOB question and you don't feel like replying, DON'T, just ignore that post. If you do reply, good for you.....and be nice in your reply.
1st Time Installing
You Need To have Rooted and Custom Recovery Installed Phone To Use This ROM
If you are New Just Go To This Thread and Download Wug's Nexus Tool Kit And Follow Instructions.
Once Custom Recovery Installed. TWRP 3.1.x recommended
Download the zip
Download Gapps
WIPE DATA/FACTORY RESET
Install Modem/Firmware Update
Install the update zip from recovery
Install Gapps
flash Magisk14.1 or 14.0 .zip
Reboot
Already Using the Previous Version of Same ROM
Download the zip
Install latest zip from recovery
wipe Cache
Reflash Gapps
Flash Magisk
Reboot
Credits:
LineagesOs team
CRdroid Team
ScottHeart BTi
He][razor
Vortex 1969
neobuddy89
XDA Developers community
The users and all developer of XDA who has helped me direct or indirect way
Google for Android.
If I miss someone Here please point it out to me.
Source
https://github.com/LineageOS/
https://github.com/crdroidandroid
XDA:DevDB Information
SourceBuilt ROM for Nexus 6, ROM for the Nexus 6
Contributors
chineel, chineel
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
Based On: LineageOs
Version Information
Status: Beta
Created 2017-10-28
Last Updated 2017-10-28
Hi everyone The ROM Upload is still On
I have two build Ready One is LineagesOs unofficial and second One CrDroid4.0 which is also based on LineageOs 15.0
Both Got Uploaded
first is Crdroid
crDroidAndroid-8.0-20171028-shamu-v4.0.zip
Second One is LineagesOs-15.0
lineage-15.0-20171028-UNOFFICIAL-shamu.zip
Both Rom are unofficial nothing official about it.
For best error free opration you need to have it Clean Installed
means
Factory reset
wipe
System, Cache,
Flash ROM
Flash Gapps
Flash Magisk / Super Su for rooting
Wait for a while
let it get settled
Enjoy the New Oreo 8.0
11/07 Build Onwards forced encryption is removed so your data by default is not encrypted anymore.
For all those having trouble booting should follow below steps.
get ADB fastboot installer from here
Take back up of everything including DCIM and TWRP or TITANIUM or SMS contact backup or any other.
reboot to bootloader.
open command prompt.
fastboot format userdata (This will format everything on internal storage and will recreate data partition)
wait till success message.
reboot to recovery
wipe system cache data (if you like to but not needed this time)
flash ROM
Flash Gapps of your choice.
wipe dalvick and cache
Reboot
wait for a while
let your phone settle for some time.
reboot to recovery again
flash magisk
reboot
Enjoy your phone unencrypted and fresh as new. Connect to pc copy back your data
restore back whatever you want to restore enjoy.
3rd one
i may Need this one also
Great work! Had any issues with random reboots?
rebel1699 said:
Great work! Had any issues with random reboots?
Click to expand...
Click to collapse
No No reboot since yesterday on my phone
chineel said:
No No reboot since yesterday on my phone
Click to expand...
Click to collapse
Good deal. Will install in the morning and test it out. Again, great work to help keep shamu alive
Hey man thanks for the efforts, a little OT question tho, i saw you got a crDroid build on AFH, are you the new maintainer? edit: Oops, just read the 2nd post ^^ .
gr3ud said:
Hey man thanks for the efforts, a little OT question tho, i saw you got a crDroid build on AFH, are you the new maintainer? edit: Oops, just read the 2nd post ^^ .
Click to expand...
Click to collapse
I am going to request for that if I can continue compiling this ROM but till then Unofficial only
Downloading now. Pretty excited since I'm currently running crdroid.
Do you keep a changelog you're willing to share?
Schiben said:
Do you keep a changelog you're willing to share?
Click to expand...
Click to collapse
For CRdroid already in ROM About section attached here also
Lineageos changelog https://www.lineageoslog.com/15.0
Thank you very much for your great work ? I like this rom
I will try LOS version tonight. Any known bluetooth or Mobile data issues so far ?
Thanks for the effort and appreciate the continued update for Nexus 6.
Hi, I appreciate the effort. Mind telling us the differences between ROMs though? Does the CR one have more features than the stock based Lin one? Still going to test them both but was just wondering, thanks.
mobile data is ON by default, and even when you're connected with Wifi, it still uses your data. Blew thru my 200meg Free T-mobile trying to finish an install. Also, found that NFC is turned off. Might be a driver issue.
Battery life is OK. Sound is bad on my device. Playing some youtube videos, and the sound goes from very loud, to I can barely hear it, plus the only speaker working, is the top, the bottom one cuts in and out. (at least in youtube)
not a bug report, or any disrespect to the dev. but, its just what I've had happen while using this rom.
newsguy99 said:
mobile data is ON by default, and even when you're connected with Wifi, it still uses your data. Blew thru my 200meg Free T-mobile trying to finish an install. Also, found that NFC is turned off. Might be a driver issue.
Battery life is OK. Sound is bad on my device. Playing some youtube videos, and the sound goes from very loud, to I can barely hear it, plus the only speaker working, is the top, the bottom one cuts in and out. (at least in youtube)
not a bug report, or any disrespect to the dev. but, its just what I've had happen while using this rom.
Click to expand...
Click to collapse
Mobile data can be stopped from developer options and untick mobile data always on
steps
1 Open about Phone
2 Go to build number
3 Tap continuous till you got message you are now developer.
4 Tape on Back button
5 You will be seeing Developer options now
6 scroll down till you see mobile data always on toggle it off
Bluetooth issue was found for me when connected to my head unit in my truck. It connects, blurps sound out for half a second and then nothing the songs/videos(videos also go down to like 2 fps while paired) are still playing during but no audio. It's late I just got home will try to capture a log tomorrow. Other than that this rom is butter smooth, thanks for your hard work keeping our old whale swimming. Plz remove if it needs to be I won't be butthurt about it.
Xd great work!
About:
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), 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. You can also view the Changelog for a full list of changes & features.
Introduction:
This is an unofficial WIP LineageOS thread for the Motorola G7 Power, codename ocean.
We support all the T-Mobile, International, and Project Fi variants, as their bootloaders are unlockable, while we can't support the Verizon and AT&T variants, as their bootloaders are permanently locked.
Changelog:
20200516 (download from Drive) (download from AFH):
Using audio configuration from @Grim truth , which is confirmed to be working
20200514 (build pulled)[/URL]:
Using @Rondeau79's audio stack, which is currently incompatible
20200511 (download):
Builds are now signed. Please wipe data if you're coming from the previous build.
The May security patch has been merged in.
Audio issues have now been eliminated.
Hotspot now works.
Issues:
VoLTE not working prior to May 6 build
[*]Hotspot issues
[*]Garbled call audio on some devices
Headset issues and no audio from local files on May 11 build
ROM:
My Google Drive folder
Android File Host
Make sure to only download the latest build.
Stock Firmware:
Official Firmware
Recovery:
Use whatever recovery you want, but I'm linking OrangeFox (courtesy of @electimon) here
Copy Partitions (To setup slot_b):
copypartitions.zip
(courtesy of @filipepferraz)
GApps:
https://opengapps.org
Pixel GApps (optimized for ocean, Open GApps can have issues)
Preparation for A/B Roms:
Download a custom recovery and the stock firmware for your variant from the links above.
Remove your Google account under Settings > Accounts then factory reset your device, as FRP is enforced.
Unlock your bootloader on Motorola's official site.
Flash your factory firmware image on slot_a.
Hold power + Volume down untill you reach bootloader (fastboot mode).
In your extracted firmware folder, open a terminal or command prompt and flash your firmware files with these commands.
NOTE: This last step installs vendor.img to slot_b as well.
ROM - Installation:
LineageOS 17.1 requires some extra steps to install properly. These instructions are brought to you by @Bernie_nix.
Boot phone into bootloader
From a PC, use one of these command to boot custom recovery (TWRP/oFox). In Linux, use the following command:
Code:
sudo fastboot boot recovery.img
In Windows or macOS, use the following:
Code:
fastboot boot recovery.img
Replace 'recovery.img' with the filename for your recovery image.
If you are coming from stock, install the copy partitions zip after your phone boots into recovery.
In TWRP/oFox go to Wipe - Dalvik/Art Cache, Data, Internal Storage and System.
In TWRP go to the Reboot menu > Switch slots OR in oFox go to the Reboot menu > Switch Slots (press the grey one)
Wipe - Dalvik/Art Cache, Data, Internal Storage and System again.
Reboot into bootloader.
Boot TWRP/oFox with the fastboot command in step 2 above.
Install LineageOS.
Reboot.
It will bootloop 2x, then take you to factory data reset screen. Select Yes. It will reboot into LineageOS. At this point, if you don't want to install anything else, you're done.
Once Lineage boots, if you want to set up GApps, Magisk or another recovery, reboot into recovery mode, install TWRP/oFox, GApps, and/or Magisk.
Reboot into the bootloader and input this.
Code:
fastboot -w
Reboot. You're done.
Updating (AKA 'dirty flash') {do not follow these steps when going from unsigned to signed builds}:
Download the updated ROM.
Reboot to recovery
Install ROM.zip + the recovery, if you're using something other than Lineage Recovery.
Reboot into recovery
Flash gapps + Magisk (if you want)
Reboot into system.
Notes:
Any time your internal storage aka "userdata" is from a stock install you must use 'fastboot -w' to erase it before using any ROM, otherwise it won't boot.
Contributing:
If you have any patches you want to make to the device-specific code, do it at my GitHub, which will be linked at the bottom. I've conveniently pinned all the repositories.
If you want to contribute to LineageOS itself, go to the LineageOS GitHub at https://github.com/LineageOS .
XDA:DevDB Information
LineageOS 17.1, ROM for the Moto G7 Power
Contributors
yagyaxt1068, electimon, erfanoabdi, The people who contributed to LineageOS and the device sources
Source Code: https://github.com/yagyaxt1068
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: LineageOS
Version Information
Status: No Longer Updated
Current Beta Version: 20200516
Beta Release Date: 2020-05-16
Created 2020-05-09
Last Updated 2020-07-05
Nice! I'm looking through the git repos now. What's all this with switching between LineageOS and RevengeOS? Never heard of RevengeOS before.
Edit: Is it possible to keep the stock software installed in slot A, and install this in slot B?
Greek2me said:
Nice! I'm looking through the git repos now. What's all this with switching between LineageOS and RevengeOS? Never heard of RevengeOS before.
Edit: Is it possible to keep the stock software installed in slot A, and install this in slot B?
Click to expand...
Click to collapse
I based my device tree off of @Electimon's Revenge OS device tree.
And, it is possible to keep stock installed in slot A, but slot A would be useless without a data wipe in fastboot.
I'll give it a try sometime soon. Is there anything you need help with? I'm new to Android work, but I can take a stab at it.
edit: Installed, and it's working well for the most part! I'm going to record issues here as I come across them:
moto gestures missing Actually, they are included. There are two menus: one called "Gestures" and one called "Moto Gestures". They're both under the "System" category in settings.
notification LED constantly on battery was fully charged...
Android Setup crashes after agreeing to TOS
Bug Confirmation
Greek2me said:
I'll give it a try sometime soon. Is there anything you need help with? I'm new to Android work, but I can take a stab at it.
edit: Installed, and it's working well for the most part! I'm going to record issues here as I come across them:
moto gestures missing
notification LED constantly on battery was fully charged...
Android Setup crashes after agreeing to TOS
Click to expand...
Click to collapse
I can confirm that Android Setup is crashing. This occurs with both Pico/Nano Gapps. Also, I'm not sure if this is just the nature of Lineage, but after adding a google account, the only sync toggle option is listed as "People details." I am attempting to sync my contacts from my google account but this doesn't seem to be available. This would be under settings > accounts > google > contacts. There are also some frame rate issues, particularly when switching between applications or home screens. There does not seem to be any frame rate issues within the apps themselves, however.
I just want to add that everything I need seems to be working well. I've placed several calls and the quality was as expected. This will probably be my daily driver - nice work!
Bug report....
Installed nicely in Xfinity (Comcast) Phone.
Bug report - Local music files do not play from speaker or plugin headphones. Doesn't matter if stock player or other. (But works with Bluetooth device).
However speaker and plugin headphones work from browser and apps like Spotify.
nomadman1 said:
Installed nicely in Xfinity (Comcast) Phone.
Bug report - Local music files do not play from speaker or plugin headphones. Doesn't matter if stock player or other. (But works with Bluetooth device).
However speaker and plugin headphones work from browser and apps like Spotify.
Click to expand...
Click to collapse
Try updating to the latest build. If the problem persists, let me know.
Hello all! Considering upgrading to the G7 Power and replacing my aging LG V20 and throwing LOS on it. One single question: Does your LOS support WiFi Calling, and do other ROMs? This is the single factor forcing me off my beloved old tank, I moved to the middle of nowhere and I don't have any signal, and my only option is VoLTE and WiFI Calling, neither of which is supported in LOS on the V20.
Thanks so much for your work!
vectorvitale said:
Hello all! Considering upgrading to the G7 Power and replacing my aging LG V20 and throwing LOS on it. One single question: Does your LOS support WiFi Calling, and do other ROMs? This is the single factor forcing me off my beloved old tank, I moved to the middle of nowhere and I don't have any signal, and my only option is VoLTE and WiFI Calling, neither of which is supported in LOS on the V20.
Thanks so much for your work!
Click to expand...
Click to collapse
Most ROMs (including this one) support WiFi calling. I've tested it myself.
Sent from my moto g(7) power using Tapatalk
I'm not sure if this is just me, but wired headphones/mic don't seem to work while on a call. The audio still comes through the phone speakers.
Please note that I'm still on the May 6th build.
Greek2me said:
I'm not sure if this is just me, but wired headphones/mic don't seem to work while on a call. The audio still comes through the phone speakers.
Please note that I'm still on the May 6th build.
Click to expand...
Click to collapse
It's an issue on the May 11 build as well.
Sent from my moto g(7) power using Tapatalk
Glad you can confirm. Location services also seem to be nonfunctional at the moment.
I installed the latest build (May 14th) on my device and all audio output is now broken (including calls). I have a XT1955-2.
edit: I flashed the May 11th build over the top and audio is working again.
My Moto_G7_XT1955-5_ ocean is mute completely with May 14th build.
bluetooth speakers work.
fastness said:
My Moto_G7_XT1955-5_ ocean is mute completely with May 14th build.
bluetooth speakers work.
Click to expand...
Click to collapse
That was part of a test to see if there were audio issues. It will be reverted eventually.
Greek2me said:
Glad you can confirm. Location services also seem to be nonfunctional at the moment.
Click to expand...
Click to collapse
I'm on the May 11 build and my GPS locks faster than it ever has and it's very accurate on my device. I'd even go so far as to say its faster than stock. I haven't used maps ever on my 1955-5 except on rare occasions when testing a rom but when I saw your location is off post I flipped on location tile opened Google maps and probably 2 seconds after that the dot showed just outside my bedroom window at my house. Going to run a few tests now and see what the outcome is just for kicks but seems good on my end on the May 11th build.
Yes, location is working now on the May 11th build.
I'm not sure if this is the fault of the OS, but my SMS messages are being received late and in batches. It seems that I sometimes don't receive SMS messages until I unlock the phone and open the Messages app. Is anyone else experiencing that?
Greek2me said:
Yes, location is working now on the May 11th build.
I'm not sure if this is the fault of the OS, but my SMS messages are being received late and in batches. It seems that I sometimes don't receive SMS messages until I unlock the phone and open the Messages app. Is anyone else experiencing that?
Click to expand...
Click to collapse
I get that now and I'm not rooted yet
The night light / blue light filter doesn't seem to work in the May 11th build.