Related
Hey guys, is this a thing yet? Haven't had much luck in my search, might be too early.
The majority of the custom ROMs have been on 7.1.1 for quite some time now, and pretty much all the kernels have been updated to support it. I wouldn't imagine there are any crazy changes in official released 7.1.1 to break compatibility with existing kernels. So pick your poison. My go to is Singularity right now.
edit: unless you mean't the "stock kernel" with no force encryption enabled. In which case just use the FED patcher before you boot, it will unpack the kernel and ram disk, disable dm verity and some other voodoo, and repack the kernel and ramdisk and allow you to boot. I've used it on Marshmallow on CM to try the stock kernel without force encrypting and it worked great. Pretty sure it works for Nougat too but haven't used it in a while.
Dopamin3 said:
The majority of the custom ROMs have been on 7.1.1 for quite some time now, and pretty much all the kernels have been updated to support it. I wouldn't imagine there are any crazy changes in official released 7.1.1 to break compatibility with existing kernels. So pick your poison. My go to is Singularity right now.
edit: unless you mean't the "stock kernel" with no force encryption enabled. In which case just use the FED patcher before you boot, it will unpack the kernel and ram disk, disable dm verity and some other voodoo, and repack the kernel and ramdisk and allow you to boot. I've used it on Marshmallow on CM to try the stock kernel without force encrypting and it worked great. Pretty sure it works for Nougat too but haven't used it in a while.
Click to expand...
Click to collapse
An issue I just came across with custom kernels is that I get no sound whatsoever out of my N6, not even in calls. I tried Elite and ElementalX and both did this. I'm thinking something must have changed in the official 7.1.1 image involving the way it handles sound. Really weird!
H4X0R46 said:
An issue I just came across with custom kernels is that I get no sound whatsoever out of my N6, not even in calls. I tried Elite and ElementalX and both did this. I'm thinking something must have changed in the official 7.1.1 image involving the way it handles sound. Really weird!
Click to expand...
Click to collapse
Thanks for info, and I read fed patcher v8 doesn't work with Nougat but dev working on v9. So for now I guess no kernel that doesn't force encrypt is available.
Dopamin3 said:
Thanks for info, and I read fed patcher v8 doesn't work with Nougat but dev working on v9. So for now I guess no kernel that doesn't force encrypt is available.
Click to expand...
Click to collapse
I ended up using magisk for my issue, it disables dm-verity and turns off forced encryption, hopefully new kernel will be around soon and I have a good feeling they will be!
H4X0R46 said:
Hey guys, is this a thing yet? Haven't had much luck in my search, might be too early.
Click to expand...
Click to collapse
I was curious about this as well since I recently unencrypted my phone. Turns out SuperSU fixes forced encryption so as long as you flash it in your recovery before booting your phone back up you should be good. On 7.1.1 stock at the moment without encryption and all I did was flash the new radio, boot, and system images in Fastboot. I then booted into recovery, flashed SuperSU and rebooted. So far, so good.
I've been seeing constant complaints around the OnePlus 3's development section of the forums regarding an unusual high CPU usage and massive battery drain on different ROMs. These reports are posted in the custom kernels thread.
flar2's ElementalX kernel thread (now locked unlocked):
[link removed]
eng.stk's blu_spark kernel thread:
[link removed]
The reports mostly state that "(insert kernel name) gives high CPU usage, battery drain, etc." flar2 and eng.stk both say it's not the kernel, yet every custom ROM seems to have issues with this strange "bug". Even stranger, it only affects some users.
So what gives?
To preface, I'll be as verbose as I can about my experience with this: I had this exact issue with the CPU nearly maxing out and massive battery drains on LOS/AOSP-based ROMs. I clean-flashed Resurrection Remix, DU, Citrus, and CypherOS, and I even tried flar2's EX kernel, blu*spark, and stock kernel that ships with the ROMs; every one of them had this problem. On average, I use my phone daily, but not really heavily (I don't play games, but I either web browse, Youtube, or calling/text), so I found it odd that my phone's battery drops from 100% to 72% every time I get up in the morning and down to 15% after only 2 hours of using my phone. I thought this was strange since I never had this problem before. I checked my phone's battery stats (Settings -> Battery) and didn't find anything strange. I blamed CM/LOS and switched to AOSP, same issue. From there was a full day and half of switching ROMs, swearing, and confusion. What I should've done from the start was check the logcat because the solution was literally written all over the logcat.
Something related to the modem was silently crashing in the background.
It would restart again and again, crashing every 5-10 seconds or so. It would comment something about com.phone.android - I forgot to save a screenshot of the message
but nevertheless this error was 5-6 lines long and was scattered all over the logcat. Again, silent crash: no (processes) has stopped, unfortunately, (processes) has stopped, etc). This would explain why my device never entered deep sleep and sky-rocketed the CPU frequency.
To conclude, I firmly believe the high battery drain and CPU usage is actually caused by Oxygen OS's 4.0.x firmware, NOT THE KERNEL. When I switched to 3.2.8 firmware or 3.5.5CE my issue was completely fixed - 10 hours of SOT and very good performance using the EX kernel +AKT combo. I think the reason why some people have this problem and others don't is because they're on different firmwares. Through testing, 4.0.x has these problems whereas 3.5.5CE and 3.2.8 does not.
I want to note that I did not test stock Oxygen OS. The firmware downgrade solution may also not work for you - hence why the thread's title name is "a potential fix". Some users on FreedomOS, Experience, or other custom Oxygen-based ROMs have reported two approaches to fix battery and CPU usage:
The modem/phone errors on firmware 4.0.x could be limited to custom AOSP/LOS ROMs. Using an older firmware may cause Oxygen OS Nougat to not boot anymore, so backup everything and make sure you have a restore point before trying my fix.
TL;DR: This is NOT a kernel issue. Don't blame flar2, eng.stk, or anyone but OnePlus. I believe this is a bug in OnePlus' Nougat firmware. Until OnePlus fix this, I urge everyone to flash either 3.2.8 or 3.5.5 firmware and see if the High CPU usage and battery drains are gone on custom AOSP/LOS ROMs. You can try downgrading firmware on Oxygen OS - but please backup and make a restore point if the ROM does not boot (I did not test stock Oxygen OS). If you're on Oxygen OS, I suggest you try using phhh's root and changing SELinux Policy to permissive first (though SELinux should be enforced) before downgrading firmwares. OnePlus needs to fix their unstable firmwares (and release Camera blobs, etc)!
STEPS:
0. If you're on Oxygen OS, try phhh root and changing SELinux policy to permissive first. If that doesn't work, or if you're not on Oxygen OS, go to the next step.
1. Go to jamal's firmware/modem collection: (link removed)
2. Click the Android 6.x button.
3. Click link to download Firmware + Modem zip 3.2.8 OR 3.5.5CE (I recommend 3.2.8).
4. Flash in TWRP recovery (any recovery version works).
5. Reboot and enjoy better battery life and no high CPU usage
5a. If you set a lockscreen with PIN, chances are that you won't be able to get pass the lockscreen; in that case, reboot back to TWRP recovery, mount /system, use the built-in filemanager to navigate to /data/system, and delete the 5 gatekeeper/lockscreen files.
5b. If your ROM kernel panics after flashing firmwares (screen suddenly goes black, reboots), delete the init.d folder.
UPDATE:
I've been doing some testing with the OOS 4.0.x firmware and I think I found out the issue!
I kept getting the same battery drain on LOS/AOSP-based ROMs. Reading the thread, it seems hardly anybody has this issue on newer firmwares. At first, I thought it was an F2FS issue. I started from scratch by wiping everything (including the internal storage), changed the /data partition to ext4, and upgrading TWRP. When I booted the ROM afterwards and let my phone sit for a few hours, I still had that strange error with the CPU behaving abnormally and battery drain. So I took to the logcat and started searching.
The error that generated heat and battery drain from OOS 4.0.x's firmware is the following:
Code:
Sending non-protected broadcast com.android.imsconnection.DISCONNECTED from system 2019: com.android.phone
com.android.phone? That's familiar....remember how I said in the OP it was a modem issue? But just above the error has this message:
Code:
ImsSenderRxr : Response data: [12, 13, -1, ...
That's Enhanced 4G LTE Mode! All I needed to do was flip the switch OFF and viola! All errors gone, CPU stable and minimal battery drain. Oxygen OS does not error out like this, so I'm certain this "issue" is exclusive to just LOS/AOSP.
Looking at the OP I realize how silly this thread is. I could've just attached the logcat into the Q/A thread and asked for help, done deal. My apologies everyone. If you downgraded the firmware to try this "fix", upgrade back!
For people running Oxygen/Freedom/Experience OS: if you have drain, this fix still applies to you:
Use phh's superuser instead of SuperSU
Using the command:
Code:
su
setenforce 0
or using init.d scripts to change SELinux's policy to permissive
If /data is F2FS, try changing it to EXT4
I'm open to discussion - did this solution work for you? Anyone try this on Oxygen OS? Or perhaps you have a different solution? Comment below, or use the poll! That will help me when I create future OP threads
Instead of complaining appreciate the efforts of eng.stk and flar2. Some are spoonfeed they don't want to search. Thank you for posting this!
madsponge26 said:
Instead of complaining appreciate the efforts of eng.stk and flar2.
Click to expand...
Click to collapse
To the contrary. I really appreciate their work for the OnePlus 3. They're extremely talented developers that I definitely look up to. I just blame OnePlus for the bugs
madsponge26 said:
Some are spoonfeed they don't want to search.
Click to expand...
Click to collapse
I completely agree with this, and it's sad, really. I remember when new XDA members were collaborating with developers and innovating (sorry, Apple). Now it seems like too many members are treating XDA like a technical support site.
madsponge26 said:
Thank you for posting this!
Click to expand...
Click to collapse
You're welcome
I've had this issue as well. I went from Experience Rom to Stock 4.0.2 since when I used Xceed the CPU load didn't go below 60%. But this is not a kernal issue.
I have flashed the 3.2.8 firmware+modem over OB11 and did not experience any bootloops. We'll see how battery fares.
The issue is in 99℅ of the cases the one described by @NevaX1 here, do his solution and all will be perfect my CPU finally dropped to 300mhz.
Edit link: https://forum.xda-developers.com/oneplus-3/development/rom-freedomos-1-0-t3409348/page546
TLR: run in terminal
Su
Setenforce 0
peshellas said:
The issue is in 99℅ of the cases the one described by @NevaX1 here, do his solution and all will be perfect my CPU finally dropped to 300mhz.
Edit link: https://forum.xda-developers.com/oneplus-3/development/rom-freedomos-1-0-t3409348/page546
TLR: run in terminal
Su
Setenforce 0
Click to expand...
Click to collapse
Well I tried this fix and it doesn't seem to work.. I'm currently on Oos 4.0.2 rooted and bluspark r32 kernel and I still have the hand warmer.. Heat is just reeks from all parts of phone :/
That's just a workaround and for example flar2 didn't recommended to run SELinux in that mode.
@kentexcitebot, did you tested stock ROM provided by OP? I might try it because I don't see in OP foruns people complaining about this battery drain and I'm curious how this relates to custom ROMs only, when in the end they are based on stock.
sarus_b said:
Well I tried this fix and it doesn't seem to work.. I'm currently on Oos 4.0.2 rooted and bluspark r32 kernel and I still have the hand warmer.. Heat is just reeks from all parts of phone :/
Click to expand...
Click to collapse
When you send the su command did it ask you, and you gave root permissions? Also if you use ARISE you must go to titanium backup and freeze an app called something like arkansysaudio, my spelling might be little off. I clean flashed Experience 10.1 then bluespark r32, then magisk and then phh root for magisk(latest) all was perfect but there was heat etc, after the nevax1 solution that was also gone. Phone is now perfect and passes safetynet security (snapchap, pay, etc)
Edit: In order to use magisk and phh root, you must completely remove supersu(it has an option in the app). So best way should be
0.flash the twrp 3.0.4
1.Flash rom
2.Flash bluspark r32
3.Reboot
4.Extract stock boot.img feom the rom you flash(open it via file Manager, its the first file you see)
5.Go to SuperSU app settings and completely remove it, and say no when it asks to restore boot.img
6.reboot to recovery
7.select install and change to image install, choose the boot.img you extracted and flash it in boot partition when it asks.
8. Flash kernel
9. Flash latest magisk(10.2 at the moment)
10. Flash latest "phh for magisk"
11.reboot
12. Install phh app from play store
13.open magisk and it should ask for root via phh Interface and then show you that magisk a d root are functional (you can test safetynet security on there too with one button)
14. Open terminal and run "su"( it will ask permission), and after that run "setenforce 0"
15. Profit, all should be perfect and you can enjoy it even safetynet free
Optional: download AKT PROFILES 1.2 app(not zip) and install. Run it give it root, and restart it. After that run it choose ballanced or battery saving profile of your choice for even greater battery and smoothness.
peshellas said:
When you send the su command did it ask you, and you gave root permissions? Also if you use ARISE you must go to titanium backup and freeze an app called something like arkansysaudio, my spelling might be little off. I clean flashed Experience 10.1 then bluespark r32, then magisk and then pph for magisk(latest) all was perfect but there was heat etc, after the nevax1 solution that was also gone. Phone is now perfect and passes safetynet security (snapchap, pay, etc)
Click to expand...
Click to collapse
Yes there was a prompt, obviously I won't be using kernel without being rooted..
Anyway I don't use any mods you mentioned yet the problem is still there... It has just decreased now.. Now it depends on my phones mood when to start heating up..
Same here, after the workaround I can't feel that much the heat but the drain is clearly there. Android System was taking 45% of the drain. Using FreedomOS with blu_spark kernel and no mods except Adaway.
peshellas said:
The issue is in 99℅ of the cases the one described by @NevaX1 here, do his solution and all will be perfect my CPU finally dropped to 300mhz.
Edit link: https://forum.xda-developers.com/oneplus-3/development/rom-freedomos-1-0-t3409348/page546
TLR: run in terminal
Su
Setenforce 0
Click to expand...
Click to collapse
Yup, I have that in the OP.
lxxs said:
That's just a workaround and for example flar2 didn't recommended to run SELinux in that mode.
@kentexcitebot, did you tested stock ROM provided by OP? I might try it because I don't see in OP foruns people complaining about this battery drain and I'm curious how this relates to custom ROMs only, when in the end they are based on stock.
Click to expand...
Click to collapse
Like I wrote in the OP, I do not recommend changing the SELinux policy. I also mentioned in the OP that I did not test Oxygen OS, reason being that OOS 4.x seems like a rushed product (so I put no time investing to flash OOS). Since I haven't flashed OOS, I wrote on the bottom of the OP if anyone has modem errors popping up in the logcat. My "fix" is to simply downgrade to a stable firmware (3.2.8 preferably).
Looking at the comments so far, I think Oxygen OS may not be affected by the modem bug. I'll wait and see what people write in the comments and will edit the OP if necessary. Maybe try flashing the firmware, then clean flash the ROM?
EDIT: I just edited the OP so the phhh root workaround is more visible!
lxxs said:
That's just a workaround and for example flar2 didn't recommended to run SELinux in that mode.
@kentexcitebot, did you tested stock ROM provided by OP? I might try it because I don't see in OP foruns people complaining about this battery drain and I'm curious how this relates to custom ROMs only, when in the end they are based on stock.
Click to expand...
Click to collapse
Yes he doesn't recommend it for safety reasons, but it is far worse to run the phone in a max cores overheating state, it will at some point damage the motherboard and other components. So either this for now or downgrade to another version. Also people with stock op rom have it too, not all though, same with custom roms guys, not all face the issue. And im also suspecting it cam be related yo the kernels not managing selinux properly, but again, some people with custom kernels said ot worked out of the box.
---------- Post added at 10:54 AM ---------- Previous post was at 10:52 AM ----------
sarus_b said:
Yes there was a prompt, obviously I won't be using kernel without being rooted..
Anyway I don't use any mods you mentioned yet the problem is still there... It has just decreased now.. Now it depends on my phones mood when to start heating up..
Click to expand...
Click to collapse
Try all steps, they are not mods, its alternative root. I just did all those as mentioned exactly and problem is gone, I spent hours to come down to this. :fingers-crossed:
After writing:
su
setenroce 0
shall i get any feedback message? or just a new line to write a command?
Hello OP, thanks for getting this point out. I never liked blaming on things which we use for free , plus the devs put a lot of effort.
I have few questions. I'm kind of novice.
I'm on Experience ROM v9.6 with SuperSu 2.78 and modified twrp.
Can I flash the 3.5CE modem over it? I'm kind of scared with Op3.
I don't have anything beside it.
Thanks
AvivEliyahu said:
After writing:
su
setenroce 0
shall i get any feedback message? or just a new line to write a command?
Click to expand...
Click to collapse
There won't be any feedback, but if you go into Settings and to About Phone, then scroll to the bottom, you'll see that SELinux policy changed from "enforcing" to "permissive".
shubhaemk said:
I'm on Experience ROM v9.6 with SuperSu 2.78 and modified twrp.
Can I flash the 3.5CE modem over it? I'm kind of scared with Op3.
Click to expand...
Click to collapse
Try using phh root and changing SELinux first before downgrading the firmware. Don't worry about hard-bricking your OnePlus 3 - I've done bad things like flashing a OnePlus 3t version of custom ROMs (not unified) and I got out of it
Instead of updating old firmware and all, try the following to fix the issue permanently. Will persist across reboots as well -
Extract ElementalX / blu_spark kernel zip
append the following to cmdline parms
Code:
androidboot.selinux=permissive
Repackage and flash from TWRP
File is present at following location in the either zips -
ElementalX - boot/cmdline.sh
blu_spark - kernel/blu_spark_tweaks.sh
Before
Code:
androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x237
After
Code:
androidboot.hardware=qcom user_debug=31 androidboot.selinux=permissive msm_rtb.filter=0x237
Its possible swith this with seLinuxModeChanger
Sent from my ONEPLUS A3003 using XDA-Developers Legacy app
Hey @kentexcitebot.
U really saved up many ppl's life with this...
After applying Ur fix my overnight drain is 1-2%, unlike b4 when it was >15%.
It really works , I really appreciate Your work.
Currently my device running Freedom Os 2.2, no kernal, only magisk+phh super su.
and battery is awesome .
Thanks,
Cheers!!!!!!!!!!!!!!!!!
I am using RR build 20170116 and firmware 4.0.2. Never had this problem. It occasionally does not go to deep sleep after screen off. Clear data of Google Play service or reboot always fix the problem.
How can I explain it if there's a problem with firmware 4.0.x?
Firstly, I apologize if this is posted in the wrong place and topic has been covered before, but I really need your help!
I got the A6 brand spanking new 4 days ago, and have managed to flash TWRP (TWRP-3.2.3-TwrpBuilder-a6ltexx-2018-11-26_20-43.tar) successfully and get RMM-State_Bypass_Mesa_v2.zip, Magisk-v18.0.zip & no-verity-opt-encrypt-6.0.zip (in that exact order) and I thought was all good.... BUT here lies the problem, after I have flashed the above files, I need to update Magisk to the latest version to be able to use the Magisk Hide & Superuser functions.. Whenever I have updated Magisk, either by direct install or download only then install in TWRP, it makes the phone reboot at random intervals..
it can be hours between reboots or it can be minutes, it goes blank and restarts from the android boot animation, where I have to enter my pins to be able to use it again.. WHY is Magisk causing this random reboot and how can I fix it??
Ive re-flashed the A600FNXXU3ARL1_A600FNOBE3ARL1_EVR (Android 8.0.0) a good few times now, but this random reboot bug Isn't present since I flashed it back to stock..
Also, a separate question; WHY are certain android apps refusing to run due to phone being rooted?? I thought once you re flash official stock firmware the phone appears "warranty intact"?
I used to be up-to-date with android rooting & modifying back in the day, but I have been out of the loop for a long time.
Thanks for your patience reading this and thanks in advance for any help/answers/time taken by me.
Arty.
Magisk on Oreo doesn't work well if you don't have the one with anti defex version as the kernel keeps avoiding you to use superuser commands as part of security feature even after rooting.
About the stock apps refusing to work after flashing the stock rom, you already tripped knox while flashing twrp which once gone you won't be able to turn back. But flashing a custom kernel would fix such problems most of the time.
henok.gk said:
Magisk on Oreo doesn't work well if you don't have the one with anti defex version as the kernel keeps avoiding you to use superuser commands as part of security feature even after rooting.
About the stock apps refusing to work after flashing the stock rom, you already tripped knox while flashing twrp which once gone you won't be able to turn back. But flashing a custom kernel would fix such problems most of the time.
Click to expand...
Click to collapse
Thank you for your reply!
How do I get said anti defex version? Ive tried googling it but only found unrelated results, could you please point me in the right direction in how to proceed please? thanks
Arty.
I can't point you a direct link with a magisk version you need to flash to get rid of defex. If you're lucky you may get a custom kernel built including it. Try one of the oxygen/phoenix kernels through this A6 thread.
The kernels will also help you byass all knox security related stuff which in turn will help most stock apps get back to working state expect for samsung pay and secure folder.
Hey!
I have always rooted my android phones, but after flashing last update and bricking my OnePlus 3T (and since I haven't used anything that needs root lately) I decided to revert everything to stock and lock my bootloader (no problem).
The problem is that after I fixed everything and installed all of my apps I noticed that I am failing safetynet . A little bit of testing and I realized that I set SELinux to permissive when my phone was still rooted....
So now I have a locked stock phone with permissive SELinux, is there any way to change this without having to unlock the phone (and deleting everything...)? Maybe if I could temporarily install SU binaries? Is that possible? (Running OxygenOS 9.0.4 .)
Thanks!
If you need root you have to unlock the bootloader... I think there was a locked bootloader hack to install root on old OxygenOS, but I doubt that works now.
But, are you sure about SELinux? If you've returned everything to stock it should be enforcing by default.
Didgeridoohan said:
If you've returned everything to stock it should be enforcing by default.
Click to expand...
Click to collapse
You are right: it SHOULD be that way. Sadly, this is the third report of selinux is permissive after crossing the 5.0.x to 9.0.x barrier - at least; two more can be found at the official los thread.
This proceduere has been reported to fix this (havn't tried myself, since I havn't faced the issue): https://forum.xda-developers.com/showpost.php?p=79816636&postcount=2670
Alright, I guess I'll just have to unlock the bootloader and fix that. Thanks for the help!
Update: I did something similar to the guide nvertigo67 sent:
1.Used the unbrick tool.
2.Sideloaded 5.0.8.
3.OTA:ed to 9.0.3.
(Haven't followed the other steps since I do not want a custom rom and don't need to flash any nandroid backup.)
Now, everything is completely stock but SELinux is still permissive and I am still uncertified... about to go crazy :crying:.
Yuvve said:
Update: I did something similar to the guide nvertigo67 sent:
1.Used the unbrick tool.
2.Sideloaded 5.0.8.
3.OTA:ed to 9.0.3.
(Haven't followed the other steps since I do not want a custom rom and don't need to flash any nandroid backup.)
Now, everything is completely stock but SELinux is still permissive and I am still uncertified... about to go crazy :crying:.
Click to expand...
Click to collapse
If your 3 steps doesn't work, perhaps sticking to the guide and only skipping to flash los and gapps is a solution. l could imagine the exact order and the reboots may play in. Otherwise I've no clue why it has worked for @zezinho7 but not for you.
Has 5.0.8 been enforcing before the ota to 9.0.3? If so, you can always use my modded fw to work around until you've found the solution.
LineageOS is a free, community built, aftermarket firmware distribution of Android 12, 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. A direct link to kernel sources can be found here. 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.
Instructions:
https://wiki.lineageos.org/devices/sake/install
Download:
https://download.lineageos.org/sake
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.)
If it is a random reboot, grab /proc/last_kmsg. (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.
Thank you for that!!
Pre install of stock android 12 needed?
thanks pro
NisseGurra said:
Pre install of stock android 12 needed?
Click to expand...
Click to collapse
Yes, I'll update description to clarify that. If you try and boot into the LOS 19 recovery with Android 11 firmware it will crashdump.
GMS = Google ? Service?
I'm trying this right now. Hopefully I make it functional before I have to head to bed.
eVen123 said:
GMS = Google ? Service?
I'm trying this right now. Hopefully I make it functional before I have to head to bed.
Click to expand...
Click to collapse
Google Mobile Services, basically google apps and services
Also @ZVNexus, the google drive folder for the build without GMS seems to be empty, has it been removed?
Update:
I had a clean flash of:
WW-ZS590KS-31.0803.0403.54-DEV-2109-M3.13.24.46-SM8350_0000110-1.1.25-user_20210831-release_for_google
I was able too boot to TWRP. It wouldn't allow me to flash your zip. I rebooted to bootloader and flashed vendor_boot. After that, I was unable to get to TWRP recovery. I flashed boot and got to some sort of LOS-like recovery (purple color).
Flashing the image now.
UPDATE: Success. However, I was in a bootloop. Got back to recovery, it suggested to wipe data. It looks like LOS is now performing it's first boot.
UPDATE 2: First boot successful! Got into language and network selection. Seems to be stuck on "Getting your phone ready" step. Scratch that, we got past that! Big success!
UPDATE 3: Got past that bit, it was in "Getting your phone ready" process a long time. Booted now!
AWESOME, thank you for your work!
For anyone else reading, the TLDR:
Installed the above zip (downloaded from official ASUS site). https://www.asus.com/Mobile/Phones/ZenFone/Zenfone-8/HelpDesk_Manual/
Downloaded all the files provided by the author
Flashed boot and vendor_boot
Went to recovery, flashed the ROM zip with "apply update" and "sideload"
Bootloped a couple more times
Recovery suggested I clean data. I did.
...
Works
UPDATE 4: Note - it seems that fingerprint still makes full screen go max brightness + it doesn't work with screen off.
Adaoh said:
Google Mobile Services, basically google apps and services
Also @ZVNexus, the google drive folder for the build without GMS seems to be empty, has it been removed?
Click to expand...
Click to collapse
Nothing was ever uploaded to it. I haven't made a build without GMS yet.
eVen123 said:
Update:
I had a clean flash of:
WW-ZS590KS-31.0803.0403.54-DEV-2109-M3.13.24.46-SM8350_0000110-1.1.25-user_20210831-release_for_google
I was able too boot to TWRP. It wouldn't allow me to flash your zip. I rebooted to bootloader and flashed vendor_boot. After that, I was unable to get to TWRP recovery. I flashed boot and got to some sort of LOS-like recovery (purple color).
Flashing the image now.
UPDATE: Success. However, I was in a bootloop. Got back to recovery, it suggested to wipe data. It looks like LOS is now performing it's first boot.
UPDATE 2: First boot successful! Got into language and network selection. Seems to be stuck on "Getting your phone ready" step. Scratch that, we got past that! Big success!
UPDATE 3: Got past that bit, it was in "Getting your phone ready" process a long time. Booted now!
AWESOME, thank you for your work!
For anyone else reading, the TLDR:
Installed the above zip (downloaded from official ASUS site). https://www.asus.com/Mobile/Phones/ZenFone/Zenfone-8/HelpDesk_Manual/
Downloaded all the files provided by the author
Flashed boot and vendor_boot
Went to recovery, flashed the ROM zip with "apply update" and "sideload"
Bootloped a couple more times
Recovery suggested I clean data. I did.
...
Works
UPDATE 4: Note - it seems that fingerprint still makes full screen go max brightness + it doesn't work with screen off.
Click to expand...
Click to collapse
Updated OP to specify the exact version you need to be on [31.1004.0404.81 (or .71)]. Basically just a public release, not a beta.
What I was able to test now, it's pretty good. Very usable already!
Bugs I notice:
The GMS seems to be a bit slower than expected.
Fingerprint doesn't work with screen off.
Fingerprint request location is not marked.
Fingerprint maxes brightness of whole display.
Task switcher sometimes doesn't work.
Bottom navigation sometimes disappears.
It keeps warning me about SELinux not enforcing issue. Not sure if that's intended/known.
More bugs I noticed after a day of use:
Google account data doesn't want to sync. Perhaps android 11 -> 12 mismatch?
Touch reader stopped working (required forced reboot).
Can't log in certain applications (don't know if it's a ROM issue).
eVen123 said:
What I was able to test now, it's pretty good. Very usable already!
Bugs I notice:
The GMS seems to be a bit slower than expected.
Fingerprint doesn't work with screen off.
Fingerprint request location is not marked.
Fingerprint maxes brightness of whole display.
Task switcher sometimes doesn't work.
Bottom navigation sometimes disappears.
It keeps warning me about SELinux not enforcing issue. Not sure if that's intended/known.
More bugs I noticed after a day of use:
Google account data doesn't want to sync. Perhaps android 11 -> 12 mismatch?
Touch reader stopped working (required forced reboot).
Can't log in certain applications (don't know if it's a ROM issue).
Click to expand...
Click to collapse
SELinux isn't enforcing because it's one of the first builds right after a bringup.
Put up a new build with some things resolved, notably SELinux is now Enforcing.
I also switched from stock's prebuilt NXP NFC stack to the open source stack. Anyone who is able to make payments with Google Pay or something like that, let me know if it works.
Added a vendor_dlkm partition to hold vendor kernel modules so you can flash a different vendor regardless of the kernel situation as the modules are no longer held there.
Enabled automatic brightness by default.
Fixed night light by correct PIxelworks device detection.
Switched from QTI BT to AOSP BT until it gets merged.
Put out a new build.
Upped kernel target level from 5 to 6. The new minimum requirement of level 6 is a minimum kernel version of 5.4.86. To comply with this I updated kernel to LA.UM.9.14.r1-16300-LAHAINA.0.
Also dropped Snapdragon Camera overlays in /vendor as it won't be supported this cycle. Just Camera2 unless I can somehow figure out getting ASUS Camera working.
Automatic brightness is now enabled by default.
Synced with latest lineage-19.0 sources which last I checked now include some theming stuff(?).
Alright, just thought I'd ask here.
I unlocked my BL and disabled some apps. Was running on stock rom!
Just tried to upgrade to Android 12 to be able to flash this rom but it is now stuck on a ramdump screen. Note: it is stuck on this screen with the Official Asus image! I had LOS18 on this device before but was running it for a few months with the stock rom (because of the camera in LOS).
It gets stuck in a loop. When I power down the phone (all 3 buttons for ~10s) it just gets me back to the ramdump.
Even using ASUS recovery RAW image and the instructions from this thread does not work: https://forum.xda-developers.com/t/full-recover-to-stock-if-things-went-really-bad.4337467/ .
After going to fastboot I am NOT able to flash the official ASUS Android 12 image, it just stops on 1/2 and does not give any details.
I am able to flash LOS recovery, LOS18 (latest) and AFTER that I am able to flash back to stock Android 11 (NOT 12, that gives me a ramdump again).
This cost me about half a day to figure out.
Anyone know what is going on and what I can do to get my phone to some kind of normal state when installing roms???
EDIT:
Just got completely stuck on ramdump.
Only thing that helped was: erase vendor_boot, boot_a/b partitions and do fastboot snapshot-update cancel . After that I was able to recover using the link above. Actually got scared there for a sec...
Uploaded a build without GMS for people who don't like using GMS.
Tap to wake functional?, installed "no gms", runs nicely
ZVNexus said:
Put out a new build.
Upped kernel target level from 5 to 6. The new minimum requirement of level 6 is a minimum kernel version of 5.4.86. To comply with this I updated kernel to LA.UM.9.14.r1-16300-LAHAINA.0.
Also dropped Snapdragon Camera overlays in /vendor as it won't be supported this cycle. Just Camera2 unless I can somehow figure out getting ASUS Camera working.
Automatic brightness is now enabled by default.
Synced with latest lineage-19.0 sources which last I checked now include some theming stuff(?).
Click to expand...
Click to collapse
Working great so far. I am having one issue where once I unlock the phone (and the screen gets really bright to read the fingerprint), it stays bright. If I tap the brightness slider, it doesn't move but it adjusts the brightness to what it should be according the slider.
This is the case with and without Adaptive Brightness enabled.
NisseGurra said:
Tap to wake functional?, installed "no gms", runs nicely
Click to expand...
Click to collapse
NisseGurra said:
Tap to wake functional?, installed "no gms", runs nicely
Click to expand...
Click to collapse
No, Tap to Wake does not work.
Mecallie said:
Alright, just thought I'd ask here.
I unlocked my BL and disabled some apps. Was running on stock rom!
Just tried to upgrade to Android 12 to be able to flash this rom but it is now stuck on a ramdump screen. Note: it is stuck on this screen with the Official Asus image! I had LOS18 on this device before but was running it for a few months with the stock rom (because of the camera in LOS).
It gets stuck in a loop. When I power down the phone (all 3 buttons for ~10s) it just gets me back to the ramdump.
Even using ASUS recovery RAW image and the instructions from this thread does not work: https://forum.xda-developers.com/t/full-recover-to-stock-if-things-went-really-bad.4337467/ .
After going to fastboot I am NOT able to flash the official ASUS Android 12 image, it just stops on 1/2 and does not give any details.
I am able to flash LOS recovery, LOS18 (latest) and AFTER that I am able to flash back to stock Android 11 (NOT 12, that gives me a ramdump again).
This cost me about half a day to figure out.
Anyone know what is going on and what I can do to get my phone to some kind of normal state when installing roms???
EDIT:
Just got completely stuck on ramdump.
Only thing that helped was: erase vendor_boot, boot_a/b partitions and do fastboot snapshot-update cancel . After that I was able to recover using the link above. Actually got scared there for a sec...
Click to expand...
Click to collapse
Same happenning here, booting to Android12 ramdumps me... I was able to update before but now it does not work... Also the flash script gives me an error that it did not give me before.
Code:
Project ZS590KS matching success!
Start erase misc
Erasing 'misc' FAILED (remote: 'Erase of misc is not allowed in snapshotted state')
fastboot: error: Command failed
misc flash failed!
Press any key to exit the script.
. I guess I will be staying on Android 11 then...
EDIT: Ran fastboot snapshot-update cancel like you did, and now the raw image file script works to reset the phone. Very weird. Also thank you so much, without your post, I would have never figured a way to make the script work again I am so glad you posted this
EDIT 2: After running the script (And everything working and passing) and getting everything back to normal, I was able to install Android 12 like I normally would without ramdumps