Database Develop

[Discussion / Poll] How successful was your unofficial upgrade to Nougat?

Hi! I am starting this discussion / poll in the hope that people will think twice before upgrading (unofficially) to Nougat. So far, what I see is 3 outcomes: 1) Device gets bricked 2) Unofficial Nougat has major bugs and people decide to downgrade back to Marshmallow 3) Upgrade is successful and user is pleased. I think that the latter scenario is actually quite rare and I feel for inexperienced people who brick their device. My question, before you try to upgrade unofficially: is it worth it?

People who brick their device doesn't follow the steps as there are written.
for example t hey flash the b370 version without the additional package and they reply 'bluetooth isnt working'
i encourage people upgrading to nougat because of the new ui, the better battery/ram management and the appearance of drawer
i rollbacked too many times to marshmallow, upgraded to nougat without any problem or brick, just follow the steps and the installation is successful.

StrangerWeather said:
Hi! I am starting this discussion / poll in the hope that people will think twice before upgrading (unofficially) to Nougat. So far, what I see is 3 outcomes: 1) Device gets bricked 2) Unofficial Nougat has major bugs and people decide to downgrade back to Marshmallow 3) Upgrade is successful and user is pleased. I think that the latter scenario is actually quite rare and I feel for inexperienced people who brick their device. My question, before you try to upgrade unofficially: is it worth it?
Click to expand...
Click to collapse
I have two p9 lites,and they are both running on b370,updated trough hicare (1.99gb),and it works perfectly.Battery life,camera,bluetooth,everthing works amazingly compared to older nougat betas.

L-31 P9, Battery life is much better used to get only 4 hours on screen time watching videos now i get 6 with 25% left so easily 7 (my screen is always at 60% brightness) I'm not rooted because i didn't flash it after but i will root soon using a PC (I'm new to rooting (came from IPhone) yet i can easily do it probably because I'm a very techy person) anyway it seems faster my camera and everything works fine i used to get 1.8gb 4am max now i get 2.2 (with no apps running) also split screen works very well and is not laggy at all, one complain i have is the live wallpaper i used for some reason stoped working after i updated (black hole stock love wallpaper) i went into settings to re apply it as it's happened once before on MM but i said there was no wallpapers at all not even still ones, if someone could give me a link to the live wallpaper I'd really appreciate that but other than that no complaints at all it's much better than MM it even has a F.LUX like function built in to reduce blue light levels to help late at night so you're​ not wide awake , the pull down menu has Many and i mean Many more functions not just 5-10 there's probably 20+ and you can have more than 5 at one time, notifications are good and work well, everything seems overly big to me but thats probably because i used to have my phone on a 300 DPI before de-rooting and updating, like i was saying it has almost no drawbacks it's very polished If you install it correctly (one package before the other and it only takes 20 mins max and you data is not deleted i used tarp not the one from this forum but it works the same i got logged out of apps and that's all that's happend when i updated)

simo255 said:
People who brick their device doesn't follow the steps as there are written.
for example t hey flash the b370 version without the additional package and they reply 'bluetooth isnt working'
i encourage people upgrading to nougat because of the new ui, the better battery/ram management and the appearance of drawer
i rollbacked too many times to marshmallow, upgraded to nougat without any problem or brick, just follow the steps and the installation is successful.
Click to expand...
Click to collapse
I agree 100%.
Upgrade to newer version of OS, official or unofficial, is one of the best thing of Android. But people need to be careful with their device, if it's not an OTA update obviously there are some steps to follow.. every device is different and just flashing whatever without attention may cause problem. Reading the steps to follow takes only 1 minute.

I'm on B132, is there a quick way to upgrade to B370? I've tried hi-care app but says no updates
Thanks

simo255 said:
People who brick their device doesn't follow the steps as there are written.
for example t hey flash the b370 version without the additional package and they reply 'bluetooth isnt working'
i encourage people upgrading to nougat because of the new ui, the better battery/ram management and the appearance of drawer
i rollbacked too many times to marshmallow, upgraded to nougat without any problem or brick, just follow the steps and the installation is successful.
Click to expand...
Click to collapse
sirjohnrl said:
I have two p9 lites,and they are both running on b370,updated trough hicare (1.99gb),and it works perfectly.Battery life,camera,bluetooth,everthing works amazingly compared to older nougat betas.
Click to expand...
Click to collapse
bghyt said:
L-31 P9, Battery life is much better used to get only 4 hours on screen time watching videos now i get 6 with 25% left so easily 7 (my screen is always at 60% brightness) I'm not rooted because i didn't flash it after but i will root soon using a PC (I'm new to rooting (came from IPhone) yet i can easily do it probably because I'm a very techy person) anyway it seems faster my camera and everything works fine i used to get 1.8gb 4am max now i get 2.2 (with no apps running) also split screen works very well and is not laggy at all, one complain i have is the live wallpaper i used for some reason stoped working after i updated (black hole stock love wallpaper) i went into settings to re apply it as it's happened once before on MM but i said there was no wallpapers at all not even still ones, if someone could give me a link to the live wallpaper I'd really appreciate that but other than that no complaints at all it's much better than MM it even has a F.LUX like function built in to reduce blue light levels to help late at night so you're​ not wide awake , the pull down menu has Many and i mean Many more functions not just 5-10 there's probably 20+ and you can have more than 5 at one time, notifications are good and work well, everything seems overly big to me but thats probably because i used to have my phone on a 300 DPI before de-rooting and updating, like i was saying it has almost no drawbacks it's very polished If you install it correctly (one package before the other and it only takes 20 mins max and you data is not deleted i used tarp not the one from this forum but it works the same i got logged out of apps and that's all that's happend when i updated)
Click to expand...
Click to collapse
Potato997 said:
I agree 100%.
Upgrade to newer version of OS, official or unofficial, is one of the best thing of Android. But people need to be careful with their device, if it's not an OTA update obviously there are some steps to follow.. every device is different and just flashing whatever without attention may cause problem. Reading the steps to follow takes only 1 minute.
Click to expand...
Click to collapse
I take your points but looking at the answers and questions forum again today, I still think the number of people bricking or downgrading is quite high. I love Nougat too, but I am warning newbies that it might be worth waiting for an official update or if not, concentrating on what you're doing. My penny's worth...

StrangerWeather said:
I take your points but looking at the answers and questions forum again today, I still think the number of people bricking or downgrading is quite high. I love Nougat too, but I am warning newbies that it might be worth waiting for an official update or if not, concentrating on what you're doing. My penny's worth...
Click to expand...
Click to collapse
I updated to B370 but had to downgrade to mm because my camera wasn't working, but overall it was a great experience. Can't wait to get an update where my camera works.
Sent from my HUAWEI VNS-L31 using Tapatalk

I see a lot of people have camera issue on l31 but for l21 everything seems to be OK. I have B370 on my l21 and I don't even think about rolling back to MM. Newest firmware is (at least in my opinion) stable and for now it runs flawlessly

JaccaPL said:
I see a lot of people have camera issue on l31 but for l21 everything seems to be OK. I have B370 on my l21 and I don't even think about rolling back to MM. Newest firmware is (at least in my opinion) stable and for now it runs flawlessly
Click to expand...
Click to collapse
+1

I have not managed to update my phone to Nougat. Everytime i try to use firmware finder or Hi suite , it keeps downloading the 1,24GB package and not the 1,99GB so i end up with a generic a15 Test Key phone

kourkoubas1981 said:
I have not managed to update my phone to Nougat. Everytime i try to use firmware finder or Hi suite , it keeps downloading the 1,24GB package and not the 1,99GB so i end up with a generic a15 Test Key phone
Click to expand...
Click to collapse
Try the TWRP method.

zgomot said:
Try the TWRP method.
Click to expand...
Click to collapse
I think that you must be bootloader unlock and rooted to use TWRP method . Too complicated for me :/
I have L21C900B170 after the fifth or sixth failure to go to 370 .
Whatever I try through Firmware Finder or HiSuite it keeps downloading the 1,24GB file and not the 1,99 Gb upgrade so I always and up with ND90 test key .
Something is blocking it but no one knows what

kourkoubas1981 said:
I think that you must be bootloader unlock and rooted to use TWRP method . Too complicated for me :/
I have L21C900B170 after the fifth or sixth failure to go to 370 .
Whatever I try through Firmware Finder or HiSuite it keeps downloading the 1,24GB file and not the 1,99 Gb upgrade so I always and up with ND90 test key .
Something is blocking it but no one knows what
Click to expand...
Click to collapse
It's really not all that difficult and there are several guides around here. Unlocking the bootloader and rooting MM is pretty much without risks. I'd say go for it.

kourkoubas1981 said:
I think that you must be bootloader unlock and rooted to use TWRP method . Too complicated for me :/
I have L21C900B170 after the fifth or sixth failure to go to 370 .
Whatever I try through Firmware Finder or HiSuite it keeps downloading the 1,24GB file and not the 1,99 Gb upgrade so I always and up with ND90 test key .
Something is blocking it but no one knows what
Click to expand...
Click to collapse
First this: https://forum.xda-developers.com/huawei-p9lite/how-to/root-root-recovery-bootloader-unlock-t3457564
Then this: https://forum.xda-developers.com/huawei-p9lite/how-to/nougat-official-firmware-t3512932

Looks like there is a majority of successful upgrades after all!

Well I did an upgrade and although at first I thought I 'borked it' - the build I have is 'NRD90M test-keys'
But I have to say after manually installing google keyboard and getting a few play store updates installed, it feels like an absolute rocket compared to the old EE B132 version

StrangerWeather said:
First this: https://forum.xda-developers.com/huawei-p9lite/how-to/root-root-recovery-bootloader-unlock-t3457564
Then this: https://forum.xda-developers.com/huawei-p9lite/how-to/nougat-official-firmware-t3512932
Click to expand...
Click to collapse
OK i managed to do the unlocking of bootloader - root but the first try of upgrading went me again to N90RDM test keys something :/
During the installation of the b370 files throught TWRP i got a message that there is /system

kourkoubas1981 said:
OK i managed to do the unlocking of bootloader - root but the first try of upgrading went me again to N90RDM test keys something :/
During the installation of the b370 files throught TWRP i got a message that there is /system
Click to expand...
Click to collapse
Did you flash both files?

StrangerWeather said:
Did you flash both files?
Click to expand...
Click to collapse
If he made the same mistake as me then he didn't flash the second file, doh!:silly:
i'm thinking of trying to get twrp back on and having another go......

Problem with lockup / display not turning on across various roms, rooted droid

I successfully rooted my droid (that came with lollipop), using this guide
https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
installed twrp backed up the stock OS and installed resurrection remix lollipop rom. I did not install any different modems or radios as I planned to stay on lollipop.
Everything worked great yet after a day or two the display/phone would appear to lock up. I can press power, the display doesn't come on and when (usually) moving the the volume up/down I do hear sounds. Sometimes at this point it will reboot by itself, other times I have to reboot it.
When it comes up it goes through the android is upgrading thing, and sometimes works fine after, sometimes not, regardless eventually this problem repeats.
Thinking it was perhaps RR I tried straight Cyanogenmod, and eventually the rooted stock OS, both have this same problem.
I've tried using it with very minimal installed in the way of apps, same issue.
I've tried saving the log to SD to peer at later, but going through it I don't really see anything obvious to show what the problem is.
I"m wondering if there's a problem with the phone itself (it's a refurb) and am considering unrooting it and returning it.
Anyone seen this or thoughts on what might be the issue?
p.s.
if you happen to have a good link handy to an unrooting guide you might shoot it my way thanks.
thanks in advance!

What versions of the other ROMs did you use? Lollipop also, or Marshmallow? Nougat? For rooted stock ROM did you upgrade to Marshmallow? None of the Lollipop ROMs are supported anymore, so hard to answer for those.
There are ways to grab logs after a reboot, but here's another suggestion...
I use Auto Reboot app (needs root) to schedule a reboot my phone every day while I'm asleep.
This seems to keep the cobwebs cleared out, so the phone runs better. I know you want to find the issue, but maybe it's an accumulation of apps not releasing RAM orb something. This might help prevent that.

thanks for the reply
ChazzMatt said:
What versions of the other ROMs did you use? Lollipop also, or Marshmallow? Nougat? For rooted stock ROM did you upgrade to Marshmallow? None of the Lollipop ROMs are supported anymore, so hard to answer for those.
Click to expand...
Click to collapse
I tried the last released CM lollipop snapshot, as well as the last nightly.
For RR it was last released, "ROM OS Version: 5.1.x Lollipop"
ChazzMatt said:
There are ways to grab logs after a reboot,
Click to expand...
Click to collapse
Yeh I've been saving it to the SD so I can view it after a reboot, I've looked at 4 or 5 of them after the problem occurred and at least to me nothing really stood out
ChazzMatt said:
but here's another suggestion...
I use Auto Reboot app (needs root) to schedule a reboot my phone every day while I'm asleep.
This seems to keep the cobwebs cleared out, so the phone runs better. I know you want to find the issue, but maybe it's an accumulation of apps not releasing RAM orb something. This might help prevent that.
Click to expand...
Click to collapse
Yeh I expect it might periodically need a reboot but if it's just unpredictiably locking up or rebooting on its own it's not very usable.
I think I'm just going to have to try to unroot and return, maybe I'll go with a LG V20 as I don't want to have pay to re-root another one of these and possibly have same issue. Also the whole pay to have some app do something secret to my phone does leave me a bit uneasy.
Kind of a bummer as I'm actually pretty impressed with this device, fast, good battery, takes nice photos, only drawbacks for me are no removable SD and lack of LED notification, but I was willing to live without those given how good everything else was.
thanks

Same here,
I tried with different Roms 7.X, still blocking and display not turning on.
I'd appreciate some help.
Thanks!
Android Version: 7.1.2
Current Rom: AOKP
Kernel: 3.10.107-Stock-bhb27-nougat-kerneL

MrN00b said:
Same here,
I tried with different Roms 7.X, still blocking and display not turning on.
I'd appreciate some help.
Thanks!
Click to expand...
Click to collapse
FWIW and in case it helps you or someone else, I seem to have fixed mine finally, here's what I did.
First I installed latest twrp (mod 4) https://androidfilehost.com/?w=files&flid=39562 (there's a thread on this twrp if you want tor read on it). That in itself didn't fix the issue but did finally let me format and got rid of an 'mkfs.f2fs: invalid option -- r, ERROR=1' type error I used to get.
I installed this stock zip from twrp as described in thread:
https://forum.xda-developers.com/droid-turbo/development/rom-su4tl-49-100-stock-t3390041
It would never actually boot it would shut my phone off not long after showing the boot screen, and I'm not sure if doing that was necessary or not.
Taking some suggestions from here:
https://forum.xda-developers.com/droid-turbo/help/help-request-custom-rom-phone-unlocked-t3767070
I dug up the last official CM 13 snapshot:
https://www.google.com/search?q=cm-13.0-20161221-SNAPSHOT-ZNH5YAO3Y5-quark.zip
sha1: 9a219dd487c27e51b0c5c4922812838f394099c5
Wipe and installed with no gapps and voilà it would boot consistently. Without reinstalling I tried installing pico gapps and it would still boot though it took maybe 15 mins initially.
I want Nougat so I wiped and installed lineage-14.1-20180612-UNOFFICIAL-quark.zip from https://forum.xda-developers.com/moto-maxx/development/rom-t3494646 again no gapps and it also booted fine, whereas previously it would hang on booting. Without reinstalling ROM I tried installing opengapps nano and it would just hang.
I could then no longer get it to boot again, so I reinstalled CM13 no gapps, which booted fine, wipe and install lineage-14.1-20180612-UNOFFICIAL-quark.zip no gapps, and now it boots fine though currently it's taking a while.
I should perhaps note I took twrp backups inbetween steps whenever I had a working boot, (ex before installing gapps), but once the phone went back to hanging on boot, those restores didn't help. Only reflashing CM13 seemed to clear things up.
My ultimate goal is a LOS ish Nougat/Oreo ROM with no gapps using microg, and running tmobile, I'll see what I end up with.

Missing product code

I have installed a couple of roms to test, but last night I got screwed up, I don't know what I did wrong why the product code went missing. I installed @_alexndr's [ROM][N950F/DS/N][ALEXNDR] * U5CRHA * DevBase v5.9 * Encryption support [Sep-16] rom. After it booted up, i noticed that it as so sluggish, I did wipe everything before installing the rom. so I decided to go back to stock. I noticed when I went to download mode the
"carrier id" is now blank whereas it was PAK before it was gone, also I went to settings it displayed XTC/XTC/ .
I did backup my efs
How do I restore my original product code?
Please help

Excuse me, off topic, but what font are you using?

winol said:
Excuse me, off topic, but what font are you using?
Click to expand...
Click to collapse
I'm using Googlesans

upbeatwrench said:
I have installed a couple of roms to test, but last night I got screwed up, I don't know what I did wrong why the product code went missing. I installed @_alexndr's [ROM][N950F/DS/N][ALEXNDR] * U5CRHA * DevBase v5.9 * Encryption support [Sep-16] rom. After it booted up, i noticed that it as so sluggish, I did wipe everything before installing the rom. so I decided to go back to stock. I noticed when I went to download mode the
"carrier id" is now blank whereas it was PAK before it was gone, also I went to settings it displayed XTC/XTC/ .
I did backup my efs
How do I restore my original product code?
Please help
Click to expand...
Click to collapse
This minor issue is NOT related to my ROM and has been disscussed in my thread long time ago
See below disscussion (#252 - #256), especially @dr.ketan's statement (#256):
https://forum.xda-developers.com/showthread.php?p=76121821&postcount=256

_alexndr said:
This minor issue is NOT related to my ROM and has been disscussed in my thread long time ago
See below disscussion (#252 - #256), especially @dr.ketan's statement (#256):
https://forum.xda-developers.com/showthread.php?p=76121821&postcount=256
Click to expand...
Click to collapse
also, after flashing stock firmware, I had the data erased (didn't used the HOME_CSC), after I enable developer options, OEM Unlock is already there and the option is ticked

_alexndr said:
This minor issue is NOT related to my ROM and has been disscussed in my thread long time ago
See below disscussion (#252 - #256), especially @dr.ketan's statement (#256):
https://forum.xda-developers.com/showthread.php?p=76121821&postcount=256
Click to expand...
Click to collapse
I have later more studied and found this code is in bootloader and strongly believe this specifically happens when you flash BL and modem with TWRP instead of odin. I request users to check this. Though this seems purely a cosmetic glitch and yet haven't found any ill effect practically.

dr.ketan said:
I have later more studied and found this code is in bootloader and strongly believe this specifically happens when you flash BL and modem with TWRP instead of odin. I request users to check this. Though this seems purely a cosmetic glitch and yet haven't found any ill effect practically.
Click to expand...
Click to collapse
Is this because of some ROMs with such options to update BL/CP before installing the rom may have cause the issue?

upbeatwrench said:
Is this because of some ROMs with such options to update BL/CP before installing the rom may have cause the issue?
Click to expand...
Click to collapse
This is what is my speculation, if someone don't have this issue and flash BL and Modem with TWRP and if he/she get this error, we can confirm it.
But this code is simply a cosmetic and I haven't seen any issue related to this.

upbeatwrench said:
I have installed a couple of roms to test, but last night I got screwed up, I don't know what I did wrong why the product code went missing. I installed @_alexndr's [ROM][N950F/DS/N][ALEXNDR] * U5CRHA * DevBase v5.9 * Encryption support [Sep-16] rom. After it booted up, i noticed that it as so sluggish, I did wipe everything before installing the rom [...]
Click to expand...
Click to collapse
BTW: Side note - my ROM is NOT sluggish but you just experienced latest Magisk's issue after clean install. More info you will find in similar S8's thread (post #280):
https://forum.xda-developers.com/showthread.php?p=77657344&postcount=280
... I just forgot to put same info in N8 thread

dr.ketan said:
This is what is my speculation, if someone don't have this issue and flash BL and Modem with TWRP and if he/she get this error, we can confirm it.
But this code is simply a cosmetic and I haven't seen any issue related to this.
Click to expand...
Click to collapse
I see, if that's the case, I did tick those options cause I thought it would be better to update BL/CP
anyways, I thought missing the product code or the 3rd csc was a huge problem because as I was installing different roms after I lost it and reinstall the stock FW, there was a lot of lag and every rom that I install, I did wipe/format data,cache before installing a new one.
Another one problem I encountered was everytime I download root explorer app and try to modify some cscfeatures, the SystemUI stops, sometimes even after a few minutes after it restarted, the SystemUI stops.
anyway, I thought these problems was related to the product code being missing, but it's all good now, everything is working just fine :good:

I have had this problem for ages, over 6 months, had flashed a number of roms and different country stock files before I noticed it had changed.
I had not used Dev-Base at the point of realising the change though.
I have never had any issues in functionality despite this. Not seeing anyone else with it, I assumed Samsung maybe updated something for unlocked phones.

_alexndr said:
BTW: Side note - my ROM is NOT sluggish but you just experienced latest Magisk's issue after clean install. More info you will find in similar S8's thread (post #280):
https://forum.xda-developers.com/showthread.php?p=77657344&postcount=280
... I just forgot to put same info in N8 thread
Click to expand...
Click to collapse
Yup, sorry about that, I thought it was only yours,
thanks for letting me know that Magisk was responsible for that extreme lag

upbeatwrench said:
I see, if that's the case, I did tick those options cause I thought it would be better to update BL/CP
anyways, I thought missing the product code or the 3rd csc was a huge problem because as I was installing different roms after I lost it and reinstall the stock FW, there was a lot of lag and every rom that I install, I did wipe/format data,cache before installing a new one.
Another one problem I encountered was everytime I download root explorer app and try to modify some cscfeatures, the SystemUI stops, sometimes even after a few minutes after it restarted, the SystemUI stops.
anyway, I thought these problems was related to the product code being missing, but it's all good now, everything is working just fine :good:
Click to expand...
Click to collapse
Nope, None of such issue is related to missing code.
this error I have on my N8 and I remember once I had flashed BL and modem via TWRP , though at that time I have no idea otherwise I can confirm it. I have made small tool to restore missing code too but never shared (Nor I am using) because t requires to patch on every boot. So my suggestion is just forget it.

It is slow, slow, slow...

Hi guys,
I'm a bit concerned about my mi8. Since several weeks now the phone is getting so slow to boot, even into recovery mode !
For exemple, today before starting to see the havoc logo spinning I count more than 20 spins. Months ago it took only 5 or 6, 2 weeks ago : more than 8... Etc.
When phone is started first apps tha usualy open really fast (Viper4fx, gsam battery monitor, magisk notifications) are so slow to open. Some other apps same thing the moment I open them.
What do you think about that ? At first I thought my battery is dead. It charges as fast as usual. Discharging is like before I'd way. Not worst for sure So I hope Its nor that.
I'm using battery charge limit (the app, nor from havoc sertings) to stop at 81% and charge it always when the minimum reaches 40%. So for battery life I think I'm doing things well.
I'm still on pie. Please, see the attached picture to look at my version.
I'm wondering what could cause this big issue.
I'm used my make lot of backups with twrp 3.3.1-1. Sometimes 2 per days, sometimes none in 2 or 3 days and so from the day I unlocked the phone and installed my first and only rom : havoc. Sure I installed several updates but no other ROM and I stopped updating it cause it worked really as I expect it should. So...
Also, making twrp backups are Soooo slow. Generaly it tooks depending of the size, between 90 sec and 140. Now it takes more than 6 min !!
So before doing a last backup and do anything I wanted to ask what you all think about that before doing a clean install update/upgrade.
Do you think it worth the try ?
I tried to clear caches (both) in twrp. Nothing :/
I'm afraid I killed my phone memory or battery. Don't really know.
Last thing, maybe an important one but don't know why it would... I installed notify & fitness and sleep as Android for my mi band 4 and I noticed my phone getting slow during this period. About N&F it was on 12.27.2019.
The firmware was updated way after that issue... And of course I cleaned all app caches manualy, not using some weird app to do the job.
Sorry me for this long SOS, and please forgive my bad english. I'm starting to being crazy. OK, the phone works but oooh boy, Its slow.
Cheers

Your rom software is out of date. if you truly want the best experience on a daily basis. There is no doubt in my mind that Xiaomi.EU is still the absolute best experience overall.
It is light years better than the Global stock Rom, all of the bloat has been removed and it has some of the Pixel AOSP features integrated into the Rom. but yes it's still miui. For me that is a good thing because I am a fan. It sounds like you have never tried Xiaomi.EU so give it a shot. I guarantee, that if you keep it installed for a few days, you will not want anything else unless you are just bored. Wait until the new update comes out, it should be late today or tomorrow. by the way, you will average about 7.5 -8.5 hours SOT.
On the other hand, if you are content with Havoc, then migrate to the latest, Its pretty great but the battery SOT time is bad right at 4 hours. This can be improved by changing the kernel. I tested the LawRun_x5.0-60hz kernel and it improves SOT to 5.5 hours, and the OS gennnerally runs better. Other Roms are also good, but lack the abundance of features that Havoc has. A comparable heavily feature rich rom is CRDroid.
If you want to stay on your current rom, then clean your caches, and at least upgrade the kernel. That alone may be enough to improve your recent performance. i dont think you phone is going bad. You likely just have some corruption, or too many processes running in the background.

@tsongming Hi and cheers for replying.
To start, I forget to mention that I'm using a global version.
That being said, I did clean all caches including from all my apps. Manualy of course.
I did use Xiaomi MIUI for very long time. Since I got my first Redmi Note 4. As you well said, I did switch to custom ROMs for what you said.
Regarding SOT... And the reason why I didn't update anything on my Mi8 its because with this version of havoc and this kernel. Gsam bat monitor tells me now : 9h41 (5h58 Max) and before my issue it was 11h !
So, to answer you : before asking here I also trying to update the Rev kernel but lot of things didn't work anymore. Like unlock the phone with my fingers and I think its pretty much normal as Havoc as evolved so kernel did the same and is not compatible with older version I think. At least, mine...
Honestly I tried lot of things to make my havoc super speed, smooth with a great battery and I was happy with that
I do hope I answered to all your questions.
I don't know what to do cause I'm not 100% sure that starting from clean MIUI or custom rom will fix it. What if not ? I'll "forced" to reinstall "everything" (I'm aware of backup apps but dont wanna use them) even if I saved all important stuffs
And if I badly revert to the last MIUI (I never reinstalled MIUI after a custom ROM. I know there is good tuto, but...) I could break it and I'll loose everything. For now it works, slowly OK ^^' but I rather that than taking a risk and found what is the cause of my problem.

Erpe7 said:
@tsongming Hi and cheers for replying.
To start, I forget to mention that I'm using a global version.
That being said, I did clean all caches including from all my apps. Manualy of course.
I did use Xiaomi MIUI for very long time. Since I got my first Redmi Note 4. As you well said, I did switch to custom ROMs for what you said.
Regarding SOT... And the reason why I didn't update anything on my Mi8 its because with this version of havoc and this kernel. Gsam bat monitor tells me now : 9h41 (5h58 Max) and before my issue it was 11h !
So, to answer you : before asking here I also trying to update the Rev kernel but lot of things didn't work anymore. Like unlock the phone with my fingers and I think its pretty much normal as Havoc as evolved so kernel did the same and is not compatible with older version I think. At least, mine...
Honestly I tried lot of things to make my havoc super speed, smooth with a great battery and I was happy with that
I do hope I answered to all your questions.
I don't know what to do cause I'm not 100% sure that starting from clean MIUI or custom rom will fix it. What if not ? I'll "forced" to reinstall "everything" (I'm aware of backup apps but dont wanna use them) even if I saved all important stuffs
And if I badly revert to the last MIUI (I never reinstalled MIUI after a custom ROM. I know there is good tuto, but...) I could break it and I'll loose everything. For now it works, slowly OK ^^' but I rather that than taking a risk and found what is the cause of my problem.
Click to expand...
Click to collapse
The current version of Havoc already uses the Revolution kernel, and its part of the current problem so use something else. The Law kernel that I mentioned is extremely good. but so are the others latest release such as Mipa and Twisted. and no fingerprint issues with these kernels.
As a longtime user you do know that anytime you switch the kernel that you should remove all passkeys, screenlocks, face unlock etc.? This could explain the slowness, you have encryption issues.
Android 10 is much improved over pie, except for the battery 11 hours SOT is unheard of on Android 10. Except for 1 guy claiming 11 hours on the ION rom. I tried the rom and it is good. but I am only getting 7 hours Sot, and the Rom is like Lineage, just the basics. No fingerprint issues.
You truly need a full clean install, including formatting storage. just backup your files first.
Xiaomi Miui? Did you mean Xiaomi.EU? if not Xiaomi.EU , then you really should try it, you wouldn't know from a past experience. This is Miui 11 on Android 10 and its flawless.

thx again @tsongming
Yep, I note all what you said to me. But to be honest last year anytime I switched from kernels to kernels I never had to reset screenlock etc. Last year cause as I said once I found the kernel which suits me I stuck with it.
So I can state its note related to that cause I didn't change it since month trust me, just tried the last kernel one or week ago to be sure if it was the cause or not. Just installed and uninstalled apps since.
look at this screenshot you'll see what I meant about SOT which was better month ago. :/ Maybe I didn't explain well...
I'm not against trying any roms including xiaomi.eu perhaps (I do have links for this I think but any link is appreciated just in case. I just download the lastest stable 11 from xiaomi.eu if its what you have in mind) but I want to be sure if it'll fix what I'm facing. You know ?
I'm afraid that doing a clean install with any rom won't fix my beautiful Mi8 ^^

Erpe7 said:
thx again @tsongming
Yep, I note all what you said to me. But to be honest last year anytime I switched from kernels to kernels I never had to reset screenlock etc. Last year cause as I said once I found the kernel which suits me I stuck with it.
So I can state its note related to that cause I didn't change it since month trust me, just tried the last kernel one or week ago to be sure if it was the cause or not. Just installed and uninstalled apps since.
look at this screenshot you'll see what I meant about SOT which was better month ago. :/ Maybe I didn't explain well...
I'm not against trying any roms including xiaomi.eu perhaps (I do have links for this I think but any link is appreciated just in case. I just download the latest stable 11 from xiaomi.eu if its what you have in mind) but I want to be sure if it'll fix what I'm facing. You know ?
I'm afraid that doing a clean install with any rom won't fix my beautiful Mi8 ^^
Click to expand...
Click to collapse
You posted a question asking for help, but then you dont want to try anything because you tried things before. Yes, its true that Magisk is sometimes persistent, but it depends on the release. it is safer to remove the passkeys.
But if you really think about it, what would cause the phone to cool down, ignore the battery stats especially from Gsam it's often very wrong, I use it too, for years and in your case you are getting good SOT because you have a zero % for the phone. It's almost like a Sim card isn't installed? Every rom will provide extremely fantastic SOT when a sim card isn't being used. If you have an active sim card then something is wrong with the monitoring because Gsam is showing 0%, it should show something even if you havent made a phone call for days.
Do whatever you want it's your phone:
I still think that you have encryption or corruption issues and its bad enough for your to make a post about it. FYI : The battery dying doesnt slow down the phone. Yes, some stock roms, notably Apple intentionally by choice changed the kernel core settings automatically on aging batteries. Hence the huge controversy a couple of years ago, that isn't happening to you.
A dying battery doesn't slow down the phone, evn cold solder joints do not slow down the phone, they keep a phone from booting to system and to recovery. The only thing left is corruption or thermals, which on this phone good luck editing thermals because they are mostly encrypted. The remaining possibility is corruption, post your log files and lets see what's actually going on.
Again, what would slow down your phone even in recovery?
It's always thermals, or corruption. Slow to start up, even in recovery.: We can rule out thermals unless your battery temp or cores temps are extremely high. This leaves corruption. if its slow while booted into the system, then you may have apps or processes crashing and you are not aware of it. If that is true, then eventually the phone may stop booting up altogether. If its thermals causing overheating you should truly resolve this issue immediately before actual heat damage occurs. Did you ever flash display refresh rate mods? If so your DTBO partition could be the issue....corruption.
Use this program to provide an app list : https://play.google.com/store/apps/details?id=de.onyxbits.listmyapps ( Weed out any unknown programs that you may not realise are installed. Post the list along with complete logs. Once you see these crashes, that I am sure the logs will show: Do as I suggested earlier: wipe and "format" your phone. Then later use best practices and remove passwords before changing kernels

Cheers. I'll try what you suggest.
I might have some questions in the future regarding format and some other things.
Never flashes display refresh rate and never noticed any overheat issue on my phone.
Sure, I'll do something like you said as soon as possible.
PS : you said "before remove passwords". You mean in the parameters of the phone like schema/diagram, pin, etc ?
Cheers

Erpe7 said:
Cheers. I'll try what you suggest.
I might have some questions in the future regarding format and some other things.
Never flashes display refresh rate and never noticed any overheat issue on my phone.
Sure, I'll do something like you said as soon as possible.
PS : you said "before remove passwords". You mean in the parameters of the phone like schema/diagram, pin, etc ?
Cheers
Click to expand...
Click to collapse
You could remove password under data/system/locksettings.bin But it's better to just go the settings//security/ *.* < remove whatever you have setup : prints and face unlock first before, pattern or pin.
Another good practice for Android 10, should you go there is :
Extract the boot image from the rom
Place it inside the downloads folder.
When ready to flash root, patch to the boot image first, ( this links the existing system binary credentials into the boot image)
Boot to recovery flash boot to boot
Then flash magisk > then boot to system and you will have no issues whatsoever with root.
Afterwards, if you decide to flash different kernel, Magisk is more likely to stay stay persistent.
I hope everything is good from this point forward take care.

@tsongming Thanks for reminding me the locksettings.bin thing because I used it once on my old phone and I forgot that.
Never installed 10 yet. But I take carefuly your advice.

Hello!
Did you fix it? Because it's happening to my Mi 8 too. It's exactly the same issue, the phone takes a long time to boot up, to open apps and even to boot into TWRP

I have that issues on my mi8
I had this problem with me before and I solved it by flashing the last official ROM, Now the problem happened to me again and I do not know what is the reason behind it @tsongming
Sent from my MI 8 using Tapatalk

ahmadbasher011 said:
I have that issues on my mi8
I had this problem with me before and I solved it by flashing the last official ROM, Now the problem happened to me again and I do not know what is the reason behind it @tsongming
Sent from my MI 8 using Tapatalk
Click to expand...
Click to collapse
I recently had some issues with my phone as well. I was able to get my phone back to normal functioning by flashing the latest stable fastboot rom using the flashall.bat method. (dipper_global_images_V11.0.3.0.QEAMIXM_20200118.0000.00_10.0_global)
I kept everything stock for a few days even recovery, to ensure once that everything was back to normal.
Next I flashed the latest OrangeFox beta recovery, and I highly recommend the latest beta build over any other version of Recovery, it will decrypt when official Twrp will not. It is now more up to date than the LR Team version, and all of the bugs have been solved by DarthJabba. In fact, he even added a script to work around poorly designed startup scripts, which are suprisening not consistent between the wide range of custom roms for the Mi8.
Today, I am still using Orange Fox, ( OrangeFox-R10.1_002-Beta-dipper) and the latest stable Magisk. I no longer have freezing, unexpected shutdowns, slow starts, or poor battery life. My issue was without a doubt corruption, and bugs with the mid february version of Xiaomi.EU. The last 2 releases have been solid.

Since this weekend I face the same problem. Every action seems to bit slower than before. And I don't know what I did that resulted in this problem. The last thing I remember I installed was the new Miui12 live backgrounds. But I deleted them again.
I'm on stock since some weeks.
But I don't want to install everything from the beginning again.
Do you know how to solve the problem without wiping everything?
Edit: As I think about it, it seems as if the caching of the apps doesn't work as good as before and the killing of apps is too aggressiv.
But what did affect it?
Edit: I found the solution for my problem.
With Android Battery Historian was able to find the process that made the trouble.
It was the Miui wallpaper carousel app. After deleting it the problems were gone.

Erpe7 said:
Hi guys,
I'm a bit concerned about my mi8. Since several weeks now the phone is getting so slow to boot, even into recovery mode !
For exemple, today before starting to see the havoc logo spinning I count more than 20 spins. Months ago it took only 5 or 6, 2 weeks ago : more than 8... Etc.
When phone is started first apps tha usualy open really fast (Viper4fx, gsam battery monitor, magisk notifications) are so slow to open. Some other apps same thing the moment I open them.
Click to expand...
Click to collapse
it's a hardware issue and it's going to keep coming back, i spent the last two months trying to resolve it but i gave up.
it seems that UFS chip malfunctions on a lot of F1 and mi8 phones.

danielnavarrowo said:
Hello!
Did you fix it? Because it's happening to my Mi 8 too. It's exactly the same issue, the phone takes a long time to boot up, to open apps and even to boot into TWRP
Click to expand...
Click to collapse
Sorry for repling only now guys...
Thx to all who proposed to solve my issue, I will tell you what I did to fix my mi 8.
I did a crystal clean flash :
- downloaded & installed last miui image using miflash
- used "clean all" at the bottom right (be careful to not choose something else like "lock boot loader ")
- then you'll need to flash recovery (twrp), then format data by typing yes. Then copy from where you want your custom rom, flash it flash magisk and boot.
I did this several months from now and my phone is like just new!
No issue at all since.
I guess installing lot of different kernels like I did before must have broken something and hopefully this could help if you dont have more serious issues.
Ps: battery is more than ok and there is no hardware problem.
Thx again to Dexer125 for his help!
Sent from my dipper using XDA Labs

Erpe7 said:
Sorry for repling only now guys...
Thx to all who proposed to solve my issue, I will tell you what I did to fix my mi 8.
I did a crystal clean flash :
- downloaded & installed last miui image using miflash
- used "clean all" at the bottom right (be careful to not choose something else like "lock boot loader ")
- then you'll need to flash recovery (twrp), then format data by typing yes. Then copy from where you want your custom rom, flash it flash magisk and boot.
I did this several months from now and my phone is like just new!
No issue at all since.
I guess installing lot of different kernels like I did before must have broken something and hopefully this could help if you dont have more serious issues.
Ps: battery is more than ok and there is no hardware problem.
Thx again to Dexer125 for his help!
Sent from my dipper using XDA Labs
Click to expand...
Click to collapse
I can confirm this.
I have been unrooted on stock for a few months now and have had no problems since then.

Hello, I have the slow issue (Androbench app with poor performances) after several dates when I have rooted my phone: Mi8 Chinese version with stock global ROM.
After unroot the phone, several days after, the phone works fine with Androbench app with good performances.
I need root my phone to use Magisk hide for Google Pay in order to avoid the Google block for contactless payment.
Can anybody help me about the understanding of this behaviour?
I do not know the reason why the phone is slow after root and why the phone works fine after several days after rooting.
Thanks in advance. Regards

roberbas said:
Hello, I have the slow issue (Androbench app with poor performances) after several dates when I have rooted my phone: Mi8 Chinese version with stock global ROM.
After unroot the phone, several days after, the phone works fine with Androbench app with good performances.
I need root my phone to use Magisk hide for Google Pay in order to avoid the Google block for contactless payment.
Can anybody help me about the understanding of this behaviour?
I do not know the reason why the phone is slow after root and why the phone works fine after several days after rooting.
Thanks in advance. Regards
Click to expand...
Click to collapse
Hi,
Mine has hardware issue (rooted).
Didn't try to unroot it if there is a difference like you describe.
Can't help you with magisk hide. I don't use it.

I have this issue with my mi 8 guys, just happened yesterday
So flashing the latest official rom via miflash is the way to fix it?

Irish_Dude said:
I have this issue with my mi 8 guys, just happened yesterday
So flashing the latest official rom via miflash is the way to fix it?
Click to expand...
Click to collapse
Hello, yes in my case. Sometimes, with wipe all, internal storage included, the problem it solved.
Recently I have the issue again without root: only with custom rom flashed. Several times the issue was reproduced out of my habitual site during vacances.
Thanks

Note8 Random Restarts when Idle

I have searched all over the place for anything that works with no luck, so asking sharper minds.
My Note8 phone started restarting randomly if left idle. The deets:
Have tried settings, updates, safe mode, cache wipes, factory resets etc multiple times. Not better even without loading backed up data and apps.
A reboot is usually every 3-10 minutes
Reboots in full; functions properly when not restarting
Can stay on as long as there is battery unless lock screen is dismissed
Stays on connected to the laptop/charger.
I concluded this may be a faulty battery as I let it run dry a few times since upgrading to a newer Note.
BUT
If I let Audible (ebook reader) or YouTube run in the background. It is a continuous operation and the phone does not restart until the app is closed. (Phone restarts with or without Audible installed so the app does not seem to be the problem).
Does it seem like the battery to anyone else, with the apps functioning?
Or should I reflash Samsung stock ROM. Those seem like the only options to me. Anything?
Thanks for taking the time.

Tried flashing the official Samsung ROM again to see if it helped.
Odin: 3.14.1
ROM: Official N950FXXSCDTF1 (Australian)
As long as the phone was downloading updates after the flash, there were no resets. As soon as it went idle it rebooted within a couple of minutes.

Hi, have you solved the problem? Have you tried to change the battery?

ok.

Install wakelock v3 from play store.
My galaxy note 8 had the same problem and it got fixed after installing it.

AVMY said:
Install wakelock v3 from play store.
My galaxy note 8 had the same problem and it got fixed after installing it.
Click to expand...
Click to collapse
Can you show settings of this app?

Plbeat said:
Can you show settings of this app?
Click to expand...
Click to collapse
USE 4th option: Processor: known to fix Galaxy note 4 issues.

AVMY said:
USE 4th option: Processor: known to fix Galaxy note 4 issues.View attachment 5765945
Click to expand...
Click to collapse
This works!!! Thanks alot!

The OP is since 2 years inactive, therefore I don't quote his message.
But according to my understanding, this is an issue with deep-sleep and should be properly fixed in kernel via an OTA update from Samsung or by trying to flash latest stock ROM from sammobile.com with ODIN or alternatively (recommended) you can try to flash a custom kernel. I've made one for Note8 and so far nobody reported such a deep-sleep issue to me.
I don't recommend at all to use that wakelock app, since it's only a workaround and will prevent your Note8 to enter in deep-sleep mode. That means higher battery usage without working deep-sleep.

ace2nutzer said:
The OP is since 2 years inactive, therefore I don't quote his message.
But according to my understanding, this is an issue with deep-sleep and should be properly fixed in kernel via an OTA update from Samsung or by trying to flash latest stock ROM from sammobile.com with ODIN or alternatively (recommended) you can try to flash a custom kernel. I've made one for Note8 and so far nobody reported such a deep-sleep issue to me.
I don't recommend at all to use that wakelock app, since it's only a workaround and will prevent your Note8 to enter in deep-sleep mode. That means higher battery usage without working deep-sleep.
Click to expand...
Click to collapse
Thank you for the advice Sir. I did flash stock rom via Odin but no luck. Wakelock v3 is the only app that worked for me. As you said it drains 2 to 3 percent battery per hour.

Plbeat said:
This works!!! Thanks alot!
Click to expand...
Click to collapse
Sir, the app drains 2 to 3 percent battery per hour even when the screen is off.

@AVMY
Yup, because phone stays awake. Honestly I can't believe that even on latest Samsung kernel it's not fixed. Strange, unfortunately I don't have an Note8 for testing. I've only S8 phone but the hardware is almost the same and there is no deep-sleep issue, no matter if I use latest stock kernel from Samsung or if I use my custom kernel.
Try with A2N kernel, if it'll still reboot, just post last_kmsg (see post #3 how-to provide last_kmsg) in the Note8 thread, then I'll check what's wrong. But as I said, so far nobody reported this.