Phone suddenly unusably slow. Problem persists after re-image. - Essential Phone Questions & Answers

2 days ago, for no apparent reason, my phone suddenly became extremely slow. I rebooted it, and it was fine for a few minutes, then it became slow again. I was running stock 8.1 rooted. I uninstalled any recently installed apps, and ran a virus scan. The thing that seemed really odd to me was that the boot animation was slow. I wiped the phone and installed LineageOS, which was not any faster. I have now wiped and installed the latest factory image, downloaded from essential's website, and it is still so slow as to be unusable. Anybody have any thoughts on this? I purchased the phone on prime day 2018, so it's like 3 months past it's warranty.

Well, @thesomnambulist after using speed reading techniques to carefully read that foreign policy and about 12.2 seconds there Ali I immediately inclined to tell you that your phone is not bricked. Message me.

thesomnambulist said:
2 days ago, for no apparent reason, my phone suddenly became extremely slow. I rebooted it, and it was fine for a few minutes, then it became slow again. I was running stock 8.1 rooted. I uninstalled any recently installed apps, and ran a virus scan. The thing that seemed really odd to me was that the boot animation was slow. I wiped the phone and installed LineageOS, which was not any faster. I have now wiped and installed the latest factory image, downloaded from essential's website, and it is still so slow as to be unusable. Anybody have any thoughts on this? I purchased the phone on prime day 2018, so it's like 3 months past it's warranty.
Click to expand...
Click to collapse
Did you get the Essential resources & services updates last week via Google? Several people on the news forum threads related to the Android 10 update have also experienced very slow phones. Could it be related? Eg conflict with another app or the network you are connected to etc?
Though yours could be hardware issue.

At the time it happened, I was on 8.1, and not taking any updates. I'm leaning towards a a hardware issue since it persisted past a wipe and re-image on stock Android 8.1, Lineage OS 16.0, and stock Android 10.

I've been getting slowdowns with my essential since Android 10 update. I'm also rooted with Magisk and did the updates with the momentary restoring of stock image, then OTA with patching the OTA partition prior to reboot method (Magisk OTA method).
I keep thinking it's the Nova beta launcher slowing me down. But I did get the slowdown once with QuickStep 10 launcher. It's mostly been Nova beta updates; 6.2.2 update seemed much better for just a day and started slowing until I just couldn't launch any apps again. Weird! Reboot and switch home default again.
I haven't been aggressive with wiping user data or trying other Android versions. I did freeze a few apps with no significant result. Currently, I'm hoping things are stable and fast with the stock launcher. That's only been since last night though.
I mentioned this in one of the Android 10 threads but not getting much feedback there. I've sent txt files to Nova development through the Nova beta app but got no response yet.
And I have diagnostics sharing disabled for essential and Nova. Thinking about reenabling those.
Sent from my PH-1 using Tapatalk

samep said:
I've been getting slowdowns with my essential since Android 10 update. I'm also rooted with Magisk and did the updates with the momentary restoring of stock image, then OTA with patching the OTA partition prior to reboot method (Magisk OTA method).
I keep thinking it's the Nova beta launcher slowing me down. But I did get the slowdown once with QuickStep 10 launcher. It's mostly been Nova beta updates; 6.2.2 update seemed much better for just a day and started slowing until I just couldn't launch any apps again. Weird! Reboot and switch home default again.
I haven't been aggressive with wiping user data or trying other Android versions. I did freeze a few apps with no significant result. Currently, I'm hoping things are stable and fast with the stock launcher. That's only been since last night though.
I mentioned this in one of the Android 10 threads but not getting much feedback there. I've sent txt files to Nova development through the Nova beta app but got no response yet.
And I have diagnostics sharing disabled for essential and Nova. Thinking about reenabling those.
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
Magisk 19.3 or canary? 19.3 doesn't play well with Android 10. If you are on 19.3, Update to canary or Banks version:
https://forum.xda-developers.com/showthread.php?p=80249962
Sent from my PH-1 using Tapatalk

freshlysqueezed said:
Magisk 19.3 or canary? 19.3 doesn't play well with Android 10. If you are on 19.3, Update to canary or Banks version:
https://forum.xda-developers.com/showthread.php?p=80249962
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
Magisk 19.3 carried over from Pie is what I'm using.
Doesn't play nice, how? I've not lost root but the slowness I've experienced seems to be with Nova beta launcher.
Thanks in advance. I'm looking for clarification is all. I have read what you're saying elsewhere but not understanding the issue.
Also I see that Banks doesn't support OTA; right there in your link. Does Canary? Not sure how to switch either? I was even considering no root for a while but steady so far with QuickStep 10 launcher. If I give it minimum of two days without the slowdown, I may just leave it as is longer to see if I'm the clear with the slowness. But I can read up on the Magisk issues in the meanwhile too.
I have a good ad blocker; it didn't require root. The things I'm patching seem to be things to just have root. I've ran out ideas for root I guess. I haven't had gravity box since nougat. Stock ROM and kernel and a desire to update security patches quickly without having to plug in is where I've been since finally abandoning nougat.
I even had a banking app tell me to disable developer options to securely sign in. I uninstalled the app and went online to sign in. Unlocks were done in adb so disabling developer mode and rebooting shouldn't lock them back down, should it? It just concerns me because oem unlock is in developer settings. I see Essential phone bricks in these threads so I'm not going to forcibly lock my bootloader. I'd rather avoid things that may jeopardize my phone. And I'd rather wait another year before upgrading.
Sent from my PH-1 using Tapatalk

samep said:
Magisk 19.3 carried over from Pie is what I'm using.
Doesn't play nice, how? I've not lost root but the slowness I've experienced seems to be with Nova beta launcher.
Thanks in advance. I'm looking for clarification is all. I have read what you're saying elsewhere but not understanding the issue.
Also I see that Banks doesn't support OTA; right there in your link. Does Canary? Not sure how to switch either? I was even considering no root for a while but steady so far with QuickStep 10 launcher. If I give it minimum of two days without the slowdown, I may just leave it as is longer to see if I'm the clear with the slowness. But I can read up on the Magisk issues in the meanwhile too.
I have a good ad blocker; it didn't require root. The things I'm patching seem to be things to just have root. I've ran out ideas for root I guess. I haven't had gravity box since nougat. Stock ROM and kernel and a desire to update security patches quickly without having to plug in is where I've been since finally abandoning nougat.
I even had a banking app tell me to disable developer options to securely sign in. I uninstalled the app and went online to sign in. Unlocks were done in adb so disabling developer mode and rebooting shouldn't lock them back down, should it? It just concerns me because oem unlock is in developer settings. I see Essential phone bricks in these threads so I'm not going to forcibly lock my bootloader. I'd rather avoid things that may jeopardize my phone. And I'd rather wait another year before upgrading.
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
I would suggest no root then.
Sent from my PH-1 using Tapatalk

That's interesting, as I was initially rooted with Magisk as well, using Novo launcher. I'm not sure either of those are related to my issue though, since I've installed LineageOS without root or Novo launcher as well as stock Android 10 without root or Novo launcher, and the problem has persisted with all of them. Essential support has been absolutely no help, and as much as I liked this phone, I will not be doing business with them again simply because of their attitude in responding to me. That being said, I think I'm going to try to wipe everything manually, and go through the flashing process one partition at a time, and see if I can get anything working.

Just as an update, I've gone back and flashed stock android 8.1. The only errors I'm seeing in flashing this is when I go to format the userdata partition, I get the following:
sudo fastboot format userdata
Couldn't parse erase-block-size '0x'.
Couldn't parse logical-block-size '0x'.
mke2fs 1.44.1 (24-Mar-2018)
/tmp/TemporaryFile-snLbLs: Unimplemented ext2 library function while setting up superblock
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
Click to expand...
Click to collapse
I've gone into the stock recovery and wiped/factory reset the partitions there, which I believe does the same thing, and it still is running so slow as to be entirely unusable.
At this point, I'm about to call it dead, but I'm open to any suggestions anyone might have.

thesomnambulist said:
Just as an update, I've gone back and flashed stock android 8.1. The only errors I'm seeing in flashing this is when I go to format the userdata partition, I get the following:
I've gone into the stock recovery and wiped/factory reset the partitions there, which I believe does the same thing, and it still is running so slow as to be entirely unusable.
At this point, I'm about to call it dead, but I'm open to any suggestions anyone might have.
Click to expand...
Click to collapse
Didn't the bootloader change in Android 10? I've seen partitions change with bootloaders but bootloaders aren't downgradeable for security reasons. Maybe that's ok but wiping partitions in another Android version may throw those errors?
Maybe our problems were similar with Android 10? I was using Magisk 19.3 and waited it out for 19.4 but I likely should have been on Canary build or switched immediately to Magisk 19.4 Slowdown with Nova until I couldn't launch apps anymore. With QuickStep 10, I only got to the point that I couldn't launch apps. Either case, reboot was a temporary fix that would restore UI speed.
I eventually realized I couldn't update BusyBox module with Magisk 19.3 so I updated to 19.4 through beta channel. Besides, I was having a similar issues getting to a point that I couldn't launch apps and having to reboot even with the QuickStep 10 launcher. BusyBox module updated without issue after Magisk beta update.
I'm hoping other issues may be resolved. I know I read many were using Canary build for across Android Q beta builds.
I'm just getting started with Magisk 19.4 so I may have more to add later. In your case, have you Android 10 again and see if the recovery wipes are still returning errors? If my phone doesn't improve, I may be upgrading sooner than expected. But there is a spare unlocked Essential PH-1 on my account now.
Sent from my PH-1 using Tapatalk

samep said:
Didn't the bootloader change in Android 10? I've seen partitions change with bootloaders but bootloaders aren't downgradeable for security reasons.
Click to expand...
Click to collapse
That's a good question. I don't think this is the case, as part of my flashing process was to flash the bootloader (for 8.1) to both slot_a and slot_b, neither of which had any errors. I believe this means that I successfully downgraded to the older bootloader (assuming that it changed in 10). I know very little about filesystems, but the error message I'm getting appears to be some kind of conflict between ext2 and f2fs. At one point in this process, I know I formatted the partitions in TWRP, and I wonder if that formatted the userdata partition with the wrong filesystem. All of that being said, I have my doubts about whether the slowness is at all related to the userdata partition, as a reboot does nothing to help. The thing that really makes me think it's not software related is that the boot animation is extremely slow, and has been regardless of what rom I have installed.

@thesomnambulist, Are you confusing the boot.img with the bootloader?

ktmom said:
@thesomnambulist, Are you confusing the boot.img with the bootloader?
Click to expand...
Click to collapse
I might be. I guess I always assumed that the boot.img was the bootloader. Please educate me.

thesomnambulist said:
I might be. I guess I always assumed that the boot.img was the bootloader. Please educate me.
Click to expand...
Click to collapse
The boot.img is also referred to as the kernel. This is the central control center for an actively booted OS (or ROM).
The bootloader is the initial bit of firmware that manages the startup up from the power off state. You go through the bootloader to get to recovery or to the system/OS/ROM.
https://forum.xda-developers.com/wiki/Bootloader
https://forum.xda-developers.com/wiki/ROM-VS-Kernel

ktmom said:
The boot.img is also referred to as the kernel. This is the central control center for an actively booted OS (or ROM).
The bootloader is the initial bit of firmware that manages the startup up from the power off state. You go through the bootloader to get to recovery or to the system/OS/ROM.
https://forum.xda-developers.com/wiki/Bootloader
https://forum.xda-developers.com/wiki/ROM-VS-Kernel
Click to expand...
Click to collapse
Awesome! Thanks for that clarification. I'm not new to Android, but I have a lot to learn!

It's been more than 2 days since upgrading Magisk to 19.4 beta on Android 10 for me.
No slowdowns or freezes. Magisk Log appears error free since update but date changed from 09-24 to 10-29? Maybe not a MM-DD date?
The last error only showed the apps I was last running before it wouldn't launch another app. But did note: beginning of crash...
Anyway, my data was kept from the OTA update from Pie to Android 10, including Magisk 19.3 until beta update. Only issue appeared to be the need to update Magisk through beta channel or switch to Canary. I said I'd have more to say later.
Next step is to switch back to Nova beta launcher and see if that remains fluid and doesn't bring back any slowness I was experiencing before the crashes. Hopefully no slowness and crashes have ceased.
Sent from my PH-1 using Tapatalk

new screen
the screen itself is likely the issue. just fixed my brothers ph-1 that started taking minutes to do anything with a new screen. hopefully this helps.

blap017 said:
the screen itself is likely the issue. just fixed my brothers ph-1 that started taking minutes to do anything with a new screen. hopefully this helps.
Click to expand...
Click to collapse
I'm not thinking my issue was the display but using the wrong Magisk version for Android 10. This issues weren't present in Pie.
Initially I did suspect Nova launcher because the app switcher was slow and Nova just lagged until I couldn't launch apps. Stock launcher wasn't so slow but eventually I kept getting to a point no apps would launch. Magisk log did record one crash but only showed the apps I was trying to launch.
Updated Magisk and the issues were totally gone with the stock launcher for nearly 3 days. Not that I saw any issue but switched back to Nova beta launcher. Not long after that, the phone did a soft reboot (SystemUI reboot). I didn't give up on Nova but stuck with it anyway. It's been fluid since and Magisk log is clear.
Not sure if you meant my phone or OP. But consider it an update on my issue. My display glass is pristine and phone hasn't been dropped. Maybe displays go bad but I've never lost one or had it go bad.
One last issue I had with Android 10 on stock ROM, I posted my simple solution here:
https://forum.xda-developers.com/showthread.php?p=80434297
I haven't had anyone issues with Nova beta launcher since I posted last in this thread. Happily, I think all issues are resolved for me now!
Sent from my PH-1 using Tapatalk

I can tell you that "formatting data" is the only option to fix the issue that slow boot happens after system upgraded.

Related

Nexus 10 Random Reboots

'My Nexus 10 started to randomly reboot several times a day after the Kitkat update and because it is outside the warranty period I cannot get it replaced.'
It reboots no matter what is running and sometimes it reboots immediately after a power up but never enters a reboot loop.
I've tried a factory reset and running it in safe mode but that didn't stop it.
I've not been able to replicate the reboot fault until yesterday when I ran the BBC iplayer and downloaded a 1-hour Horozon video of about 650Mb and when I tried to play it I got a reboot and that happened consistantly.
I tried a complete power down and reboot then tried to play the downloaded video but it always rebooted.
I tried deleting and re-saving the video incase it was corrupt but it still rebooted.
I tried deleting the video and streaming it and I could watch it that way without any reboot.
I've tried downloading three 1-hour Horizon videos of about the same size and only one plays without rebooting.
A check of running apps shows just the keyboard and a couple of system apps but I still get the reboot when I try to play the saved video.
I thought about removing apps one at a time to see if that would solve it but I've basically got the same apps I had before the Kitkat update.
I wondered if I could undo the Kitkat update and flash the previous rom to see if that would solve it for Kitkat was not a big improvement.
I've never used a custom rom and not run anyting other than stock software.
I would be most grateful for any suggestions on how to fix this rebooting problem and whether going to an earlier version of Android is feasable and how would I do it.
PS. There is a BBC iplayer option to download videos using less resolution and when I choose that option the Horizon file size falls to 344Mb which is about half the size of the original and it solves the reboot problem when playing the saved video.
So it would seem that the BBC iplayer reboot problem is related to file size.
It's fairly easy to downgrade, just Google "nexus factory images" and you should find all the old versions of android straight from Google. There should be guides online for how to flash a factory image. Just make sure to back up all your files to your computer as it will wipe everything.
Sent from my SGH-I747M using xda app-developers app
gc84245 said:
It's fairly easy to downgrade, just Google "nexus factory images" and you should find all the old versions of android straight from Google. There should be guides online for how to flash a factory image. Just make sure to back up all your files to your computer as it will wipe everything.
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
Thanks for your help.
I've found the factory images and I'm now looking for a simple detailed guide how to do the downgrade.
My Nexus 10 is on 4.4.2 (KOT49H) and I think I'll try downgrading one level to 4.4 (KRT16S) to see if that solves the reboots problem and if not then I'll try downgrading further to 4.3 (JWR66Y).
Gaugerer said:
Thanks for your help.
I've found the factory images and I'm now looking for a simple detailed guide how to do the downgrade.
My Nexus 10 is on 4.4.2 (KOT49H) and I think I'll try downgrading one level to 4.4 (KRT16S) to see if that solves the reboots problem and if not then I'll try downgrading further to 4.3 (JWR66Y).
Click to expand...
Click to collapse
Here is a good guide (sorry, I would have posted it earlier but I didn't have my computer with me at the time and was posting from my phone):
http://forum.xda-developers.com/showthread.php?t=1907796
gc84245 said:
Here is a good guide (sorry, I would have posted it earlier but I didn't have my computer with me at the time and was posting from my phone):
http://forum.xda-developers.com/showthread.php?t=1907796
Click to expand...
Click to collapse
Thanks for the guide link.
Unfortunately, my laptop is running Windows 8.1 and it is difficult to install the USB driver and Android Development Kit needed to flash previous Android versions, so I've given up until I can find the way to do it.
PS. I've found a way of installing the ADB and Fastboot drivers on my Windows 8.1 laptop and here is a link:
http://forum.xda-developers.com/showthread.php?t=2588979
So I'm back on track to solve my random reboots using an earlier version of Android.
I noticed the iPlayer hard crash thing too. I can play downloads, but as soon as I pause it and attempt to restart, or just slide the progress bar to move to a different part of the video, the tablet hangs then reboots. It's completely reproducible, and doesn't happen on any of my other devices.
Apart from that, my n10 has now gone 20 days since the last random reboot, so it's a lot more stable in general than it used to be!
I've found a easy way to downgrade to 4.3 and would be grateful for any opinion on how safe it is and if anyone has tried it.
http://forum.cyanogenmod.com/topic/83985-nexus-factory-images-to-revert-to-stock/
AleT said:
Apart from that, my n10 has now gone 20 days since the last random reboot, so it's a lot more stable in general than it used to be!
Click to expand...
Click to collapse
Arghh...this thing is a POS. I haven't used it in 2 months. Today I fired up chrome for some browsing. It hard locked within 5 minutes. I left it for an hour plus with the screen on and still locked up. Just frustrated. Worst Android device I've owned.
Sent from my XT1053 using Tapatalk
Either you have a faulty app or your tablets have a hardware defect. The random reboot issue, where the GPU driver would leak memory and force a kernel panic, has been fixed since Android 4.3 in July. This includes the Chrome reboot issue. I've had 2 reboots over 13 months, and both were cause by a ROM issue. I assure you, there is nothing wrong with the Nexus 10. Try a 4.4.2 factory image and see if that solves anything.
Koopa777 said:
Either you have a faulty app or your tablets have a hardware defect. The random reboot issue, where the GPU driver would leak memory and force a kernel panic, has been fixed since Android 4.3 in July. This includes the Chrome reboot issue. I've had 2 reboots over 13 months, and both were cause by a ROM issue. I assure you, there is nothing wrong with the Nexus 10. Try a 4.4.2 factory image and see if that solves anything.
Click to expand...
Click to collapse
I still get random re-boots in `safe mode` which is supposed to only allow apps installed with the system to run which leaves a bad 4.4.2 which could be checked by a re-flash of the factory image or faulty hardware.
I was planning to downgrade to 4.3 to see if that solved the re-boots but I might try a re-flash of 4.4.2 first to see if that works..
I'm not very confident about flashing and I've had the additional problem of working on windows 8.1 on my laptop.
I am running the factory image, 2nd one with same issues. I'm not necessarily disputing what you are saying but there were plenty of people telling me they had a perfect tablet when the memory leak wasn't fixed.
Sent from my XT1053 using Tapatalk
rxnelson said:
I am running the factory image, 2nd one with same issues. I'm not necessarily disputing what you are saying but there were plenty of people telling me they had a perfect tablet when the memory leak wasn't fixed.
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
The memory leak was fixed but apparently, it's reappeared for me with the latest kitkat update. Quite frustrating, you'd think Google would be on top of these things. What's the point of fast updates if you're waiting months on end for a fix. If I don't powerdown my tablet when I'm finished using it I can guarantee a reboot during use. In the last 24hrs, it has rebooted on me twice while using Chrome. Quite irritating to be honest
It seems from previous posts that re-flashing 4.4.2 does not solve the reboots and I've not found a way to downgrade to 4.3 on Windows 8.1 to see if that works.
So I've tried another factory reset, but this time I've not allowed any non-Google apps to be installed other than the Photon browser which I need for flash Websites and the Re-boot logger app to record any reboots.
I'm using my Note 3 for the rest of my apps as that is still on 4.3 and doesn't have the reboot problem, but that might change after the KitKat upgrade.
I was getting at least 2 or 3 reboots a day so I should soon know if running 4.4.2 after a factory reset with just two 3rd party apps solves the problem and if so then that will suggest a rougue app. which I can reveal by re-installing the apps piecemeal.
I've just had another random reboot so I've done another factory reset but not signed in to Google so there have been no downloads and the only program I've run is Settings to increase the screen timeout to 30 - minutes.
If I still get random reboots then it is nothing to do with 3rd party apps or updates for I've not downloaded any.
That just leaves the hardware or the original 4.4.2 assuming the factory reset returns to that.
I didn't experience any reboots when not signed into google after a factory reset so I signed in and restored my tablet using Google backup.
I soon started to get reboots again, but I noticed that since the KitKat upgrade a website I use very often was sometimes automatically loading the Play store to try and get me to use their much inferier app. It doesn't happen on my Note 3 which is still on 4.3.
If I tried to close the Play store app to get back to the browser by swiping it away then it crashes and keeps trying to load over and over. If I hit the home button the Play store automatically re-appears still loading over and over, but after swiping it away several times it goes away or stops with an error message asking me to report the crash which I did and the browser is closed.
In order to fix this I disabled the Play store app so that it did not appear in my list of apps.and the website instead of loading the Play store app re-directed the browser to the Play store website which was better for I was still in the browser.
Since I stopped this particular website loading the Play store by removing it, I've just had one re-boot instead of several and my tablet is no longer overheating. I am a heavy user and have my tablet on many hours a day, so one re-boot is acceptable to me.
I've downloaded a Play store apk which I can install if needed but always remove it before using the website which tries to automatically load it.
It is a nuisance and I wish I'd stayed with 4.3, but I can live with the occaisional re-boot that might not be noticed if I only used my tablet lightly.
I'm annoyed that a website can automatically load the Playstore without me requesting it and that KitKat allows it.
I hope my experience helps others who are getting several re-boots a day.
PS
I did a factory reset then removed the Play store app before using the problem website so that it never loaded it in case that was needed.
Flashing the 4.3 factory image downgrades everything. For what it's worth, I noticed that the userdata partition is constructed differently than in 4.2.2(my last factory flash). That could have something to do with it. But also, I've been on custom ROMs since I got the tablet, yet I've never rebooted on 4.4.X. I guess try a vanillish ROM(like RastaKat) to see if that reboots.
Koopa777 said:
Flashing the 4.3 factory image downgrades everything. For what it's worth, I noticed that the userdata partition is constructed differently than in 4.2.2(my last factory flash). That could have something to do with it. But also, I've been on custom ROMs since I got the tablet, yet I've never rebooted on 4.4.X. I guess try a vanillish ROM(like RastaKat) to see if that reboots.
Click to expand...
Click to collapse
Now that I'm just getting one reboot a day and my tablet is running cooler I can live with that and I don't mind re-installing the Play store when needed for continuous updates can be a nuisance.
I finally managed to downgrade to 4.3 and I'm hoping that will solve all the problems I had with 4.4.2
But all seems well at the moment.
I'm not being booted from websites to the Play store, I can use the BBC iPlayer to download and run 1-hour videos and flash player works better.
Google has downloaded 4.4.2 (KitKat) but I'm not going to install it.

Anyone else get a system update 10 Aug 2015?

Received notification of a system update today, 10 August 2015. I'm a little leery of installing this. I'm at 5.1.1 and after installing 5.1.1, I have the dreaded unannounced deaths where the phone will turn itself at random. Sometimes it will reboot if you hold the power button down for about 15 seconds. Sometimes the charger needs to be plugged in before it will reboot. Sometimes it cycles through all apps before completing the reboot. Sometimes not. If the new update will fix this, I'm all for it. But, I don't want to get fooled again with these updates. So, anyone else get an update? What does it do? Any problems after the update? Thanks.
dmkozak said:
Received notification of a system update today, 10 August 2015. I'm a little leery of installing this. I'm at 5.1.1 and after installing 5.1.1, I have the dreaded unannounced deaths where the phone will turn itself at random. Sometimes it will reboot if you hold the power button down for about 15 seconds. Sometimes the charger needs to be plugged in before it will reboot. Sometimes it cycles through all apps before completing the reboot. Sometimes not. If the new update will fix this, I'm all for it. But, I don't want to get fooled again with these updates. So, anyone else get an update? What does it do? Any problems after the update? Thanks.
Click to expand...
Click to collapse
It's the first update of Google's announced security patch program. Expect frequent OS updates now to address security issues. This one patches the well publicized Stagefright MMS exploit.
That was my guess. I rarely text, or other, message, so I'm not too worried about Stagefright. My gut tells me to wait until others have installed. I have enough memory leak auto turn-off issues, that I'm afraid of making my phone worse than it is.
If Google would be so kind as to include a memory leak resolution in these updates, I'd jump all over it.
Well I had been postponing updating to Lollipop for months... (was still on 4.4.4 cuz I didn't quite like the new UI) and decided to update Sunday morning.
Big mistake.
The OTA 5.1.1 5.0.1 update made my phone become unstable, lag, and crash at random. Constantly get "X ins't responding", where X can be anything from Launcher to System UI to Chrome!
I currently can't even use my N4, and I'm trying to find a way to revert the upgrade, My 4.4.4 was rooted, and now it's not and I can't even enter Recovery mode.
Not sure if it's 100% related to your troubles, but I've been having similar random reboots lately and just general instability.
Edit: my bad, I just realized it was 5.0.1 I upgraded to.
update aug 10, 2015
I saw the update and thought it would be a good idea but I now have a tablet stuck in reboot loop. Have tried everything (clearing data, factory reset, etc) and still not able to get past looping. Might want to wait before you update.
robpoth said:
I saw the update and thought it would be a good idea but I now have a tablet stuck in reboot loop. Have tried everything (clearing data, factory reset, etc) and still not able to get past looping. Might want to wait before you update.
Click to expand...
Click to collapse
You have to lock your bootloader for Ota to work.
Sent from my Nexus 4 using XDA Free mobile app
Stevica Smederevac said:
You have to lock your bootloader for Ota to work.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
I don't think your bootloader has to be locked, but since 5.+ you do have to be unrooted with no changes to your /system partition. I know I have sideloaded the OTA after flashing stock images. Just did not want the poster to lock their bootloader and brick themselves thinking they will be able to boot the OTA if they have modified /system at all.
ariesgodofwar said:
I don't think your bootloader has to be locked, but since 5.+ you do have to be unrooted with no changes to your /system partition. I know I have sideloaded the OTA after flashing stock images. Just did not want the poster to lock their bootloader and brick themselves thinking they will be able to boot the OTA if they have modified /system at all.
Click to expand...
Click to collapse
Yeah,you're right. Everything stock +locked bootloader for ota to work. I assumed he knew thhat part about everything stock.
Sent from my Nexus 4 using XDA Free mobile app
I have unlocked bootloader and still I updated successfully thru OTA. No problems at all.
Sent from my Nexus 4 using Tapatalk

V20 laggy after rooting

I rooted my v20 simply for viper4android and to enable the google assistant. Nothing else was done.
Ever since rooting, before even installing v4a, the notifications pull down was lagging when trying to swipe things away (it would leave a blank white space). Now, tons of things lag:
When trying to setup Google Voice
When opening Poweramp
When trying to pause or skip tracks in Spotify
When closing Chrome
The phone will hang; if I pressed a soft menu button, it will stay lit until the phone recovers.
I have factory reset, installed busybox and supersu only and still received the lag.
Is there something I can check or something I missed?
Faustous said:
I rooted my v20 simply for viper4android and to enable the google assistant. Nothing else was done.
Ever since rooting, before even installing v4a, the notifications pull down was lagging when trying to swipe things away (it would leave a blank white space). Now, tons of things lag:
When trying to setup Google Voice
When opening Poweramp
When trying to pause or skip tracks in Spotify
When closing Chrome
The phone will hang; if I pressed a soft menu button, it will stay lit until the phone recovers.
I have factory reset, installed busybox and supersu only and still received the lag.
Is there something I can check or something I missed?
Click to expand...
Click to collapse
Sorry for reviving a year and a half old thread, but did you find any solution? I am facing the exact same problem. I have one unrooted G5 and rooted V20 and another rooted G5, and the rooted ones lag horribly. Im in the exact same situation as yours, but I have magisk instead of SuperSU installed.
Hadi99 said:
Sorry for reviving a year and a half old thread, but did you find any solution? I am facing the exact same problem. I have one unrooted G5 and rooted V20 and another rooted G5, and the rooted ones lag horribly. Im in the exact same situation as yours, but I have magisk instead of SuperSU installed.
Click to expand...
Click to collapse
are you still running the ROM that was on the phone, after rooting? if i remember correctly (this was a year n a half ago... memory is **** nowadays.) some folks had problems when not flashing a new ROM after rooting.
maybe try a new ROM flash? .... I'm a nuke-n-pave kinda guy, so this is what i tend to resort to when in doubt.
Hadi99 said:
Sorry for reviving a year and a half old thread, but did you find any solution? I am facing the exact same problem. I have one unrooted G5 and rooted V20 and another rooted G5, and the rooted ones lag horribly. Im in the exact same situation as yours, but I have magisk instead of SuperSU installed.
Click to expand...
Click to collapse
Have you removed rctd? It may help...worth a shot.
https://labs.xda-developers.com/store/app/com.zacharee1.rctdremoverforlg
pistacios said:
Have you removed rctd? It may help...worth a shot.
https://labs.xda-developers.com/store/app/com.zacharee1.rctdremoverforlg
Click to expand...
Click to collapse
Thanks for the suggestions. Actually removing CCMD from RCDT tool did help a bit. It went from completely unusable to barely usable. Previously, it occasionally used to pause for about 20 seconds or so. But I still wonder what did LG implement to make the phone this laggy over time. Sure I have an enormous amount of apps installed, but they work just fine on the unrooted G5.
What variant do you have?
Have you tried flashing stock image with an updated kernel? Then update with kdz writer.
Guys after i did something stupid like factory reseting through settings (kept entering into twrp after that) i lguped to stock. Umm hello, is this my V20? I feel like i have a new phone! Previously i struggled with AKT performance profiles and diffenrent kernels but i wasn't happy, it always felt sluggish in some tasks. That is why i tried to f. reset in the first place, to see if it would feel fresh again. Currently i'm fully stock and the phone is flying! Only thing i'm missing is the mod that unlocks the high impedance hi-fi mode. For the time being i'll manage without it, i prefer having a phone that flies! I doubt it was the rctd because all custom kernels afaik include the removal script. Anyway thought i should chime in on this, as this happend a few days ago.
Lg doesn't wants us to have root access, simple as that, after rooting I got issues of lag, heating of phone and green hang screen. I too got a brand new fast flying v20 after flashing it with stock kdz via lgup with no root. So I guess, if factory reset wipe, cache, dalvik doesn't help you with lag issues you better flash it with stock rom for best performance

h910 crashing, even after factory reset

UPDATE: Please read the next post.
A while back, I rooted my v20 with magisk using this method and everything worked fine for a few months, except for a few issues that reflashing the system would fix. Last night, SystemUI kept crashing (the status bar and the buttons would disappear). After a while, the phone crashed, and then it completely refused to boot. It would very rarely get to the lock screen, but it usually crashes soon after I unlock it. I tried everything I know of that could fix it, such as restoring the boot partition and reflashing magisk, reflashing the system partition, and wiping the cache and dalvik/ART cache. I eventually gave up with this and just reset it through the wipe menu in TWRP. I was able to get the phone to work for about a day without any issues, and then the same thing started happening again. It would take a really long time to boot and the system would crash. I tried using that ~1 minute it gives me before crashing to enable core mode in magisk to prevent any modules from loading, but that didn't do anything. I am really confused as to why this would happen considering that I reset the boot and system partitions multiple times in this process, and eventually did a full reset. It should be like a brand new phone. I really don't know what could possibly be the issue. Any help would be greatly appreciated.
Update: It turns out that Magisk Core Only Mode did not properly apply because of yet another crash. I cleared my cache once more, which gave me enough time to properly apply it, and now my phone is staying on and not crashing. But this still is concerning to me. I was able to run Magisk modules perfectly fine in the past, including after the most recent Magisk zip update, so why is it that I can no longer run modules, and that this issue persists after a factory reset? It can't be an update, because, as I stated, I was able to run modules just fine for at least a week before these issues occurred. Please correct me if I'm wrong, but this makes absolutely no sense and I want to be able to run modules again. I even deleted the modules through TWRP but the only thing that seems to fix this issue is completely disabling all other features via Magisk Core Only Mode.
Update 2: A Magisk update came out recently and I tried updating to that to see if it would fix the issue. This only brought back the original crashes. I tried using the Magisk uninstaller zip (because I found that simply reflashing Magisk isn't enough, there are other files which magisk uses to store data.) After doing this and reflashing Magisk, it worked for a little bit, but, me being me and wanting busybox installed, I managed to bring back the crashes. After that, uninstalling and flashing magisk would work, but only until a reboot. I am at a complete loss. I am currently backing up my internal storage (manually since TWRP doesn't) and I will try a full /data format.
Ok, it has been a few days since I wrote the previous section but I decided not to post it because if the /data format worked, I didn't want to have bumped it for no reason. At first, it worked, and I decided to leave it like that without rebooting it for a few days or messing with Magisk, and my phone worked perfectly. I had to restart my phone because Google photos was acting up, and it started crashing again. I am genuinely confused. I completely formatted my phone and reflashed Magisk several times, and it is still crashing. I just reset my phone again because I attempted to just restore a stock boot backup from before I installed Magisk, which made my phone completely unbootable. I pulled the battery and found that it tried re-encrypting the phone (AFAIK, TWRP doesn't support encrypted data on the v20, which really sucks) so I had to wipe it and flash Magisk so it wouldn't re-encrypt it. I will try to do this again, but I don't want to not be able to restart my phone (which is so far the only thing that's working for me). This time, not even uninstalling and re-flashing Magisk worked this time, as it has all of my previous attempts. I had to completely reset it. Again. I really need this issue fixed. I probably already said this, but I would greatly appriciate any possible help I could get. I really want my phone back.
Ok I forgot to include some basic information about my phone.
Model number: LG-H910
Android version: 7.0
Android security patch level: April 1, 2017
Kernel version: 3.18.55
Build number: NRD90M
Software version: H91010m
According to Kernel Auditor:
Kernel: Linux version 3.18.55-Werewolf-2.0-Basilisk ([email protected]) (gcc version 6.3.1 20170430 (GCC) ) #1 SMP PREEMPT Sat Jun 24 00:56:07 CDT 2017
Bump/Update: This is a small one, but, despite not restarting my phone, Magisk is showing an error "Magisk is not installed". Root access also disappeared. I don't know how much longer I can keep it on without having to restart it due to random issues like these that usually fix themselves with a reboot. I would appreciate any help.
Seems like your phone is all sorts of wacked out. I noticed from the specs your using the werewolf kernel. I had all sorts of performance issues as well as random reboots using that kernel. Since you're losing root and the system is overall unstable I recommend wiping clean and starting over. Wipe system, data, cache, and dalvik in twrp and flash the full stock 10r zip by runningnak3d. It will put you on the latest security patch with the newest firmware available. I recommend installing askerm2000 1.4 kernel as it is very stable and works well on the h910. Flash magisk last (latest 15.3 works great for me) and reboot. Hopefully will solve your problems. The 10r zip for the h910 plus askermk2000 kernel and magisk has served me well for a while now.
toastyp said:
Seems like your phone is all sorts of wacked out. I noticed from the specs your using the werewolf kernel. I had all sorts of performance issues as well as random reboots using that kernel. Since you're losing root and the system is overall unstable I recommend wiping clean and starting over. Wipe system, data, cache, and dalvik in twrp and flash the full stock 10r zip by runningnak3d. It will put you on the latest security patch with the newest firmware available. I recommend installing askerm2000 1.4 kernel as it is very stable and works well on the h910. Flash magisk last (latest 15.3 works great for me) and reboot. Hopefully will solve your problems. The 10r zip for the h910 plus askermk2000 kernel and magisk has served me well for a while now.
Click to expand...
Click to collapse
Thank you. Before I do this, I have a few questions.
1. How do I disable force encrypt with Magisk? I remember when I flashed Magisk 14.0, that managed to disable force encrypt, but any other version of Magisk wouldn't do that when installing fresh (updates kept this setting). AFAIK TWRP is unusable on the v20 for things such as backups, file browser, etc because it isn't compatible with the encryption algorithm used by the v20. How would I turn off force encrypt with the latest Magisk zip
2. Should I do a full format data (where you have to actually type "yes" to confirm it) or just wipe those partitions using advanced wipe?
3. Will the askerm2000 kernel hide modified boot, unlocked bootloader, etc from safetynet just as Werewolf kernel did, and will it get rid of the static boot issue?
4. Will this increment ARB? If anything goes wrong, I want to be able to roll back.
5. If it was working perfectly fine before, what suddenly made everything come crashing down, even after multiple wipes? This is not as important as the other ones, I am just curious.
Sorry if these questions seem over excessive and/or obvious. Doing stuff like this tends to make me a bit nervous and I want to think of everything I can that might affect the outcome.
NullBite said:
Thank you. Before I do this, I have a few questions.
1. How do I disable force encrypt with Magisk? I remember when I flashed Magisk 14.0, that managed to disable force encrypt, but any other version of Magisk wouldn't do that when installing fresh (updates kept this setting). AFAIK TWRP is unusable on the v20 for things such as backups, file browser, etc because it isn't compatible with the encryption algorithm used by the v20. How would I turn off force encrypt with the latest Magisk zip
2. Should I do a full format data (where you have to actually type "yes" to confirm it) or just wipe those partitions using advanced wipe?
3. Will the askerm2000 kernel hide modified boot, unlocked bootloader, etc from safetynet just as Werewolf kernel did, and will it get rid of the static boot issue?
4. Will this increment ARB? If anything goes wrong, I want to be able to roll back.
5. If it was working perfectly fine before, what suddenly made everything come crashing down, even after multiple wipes? This is not as important as the other ones, I am just curious.
Sorry if these questions seem over excessive and/or obvious. Doing stuff like this tends to make me a bit nervous and I want to think of everything I can that might affect the outcome.
Click to expand...
Click to collapse
Twrp can properly decrypt the v20. Twrp backup and restore works just fine for me. Never had an issue with this. You format data and then type yes. Wipes the data partition but this is only needed once. Decrypts the device and twrp can then do it's thing. Encryption problems stem from booting into system with a stock boot image that has force encryption enabled without flashing magisk or supersu. They modify the kernel to prevent the device from rencrypting. Latest magisk 15.3 has zero issues keeping the phone decrypted. The modified boot warning has nothing to do with the kernel. This is caused by the debug bootloader used to achieve root on the US carrier v20's. Nothing can be done to change that. ARB has not been incremented on the h910 so that isn't an issue currently. Potentially in the future, but not right now. The problems you're having could stem from a multitude of issues. Could be modifications you made, bad flashes, etc. If you're having issues with encryption and stuff sounds like magisk wasn't functioning properly at the end. I've been rooted since last January and haven't experienced anything like that before so I'm not sure
toastyp said:
Twrp can properly decrypt the v20. Twrp backup and restore works just fine for me. Never had an issue with this. You format data and then type yes. Wipes the data partition but this is only needed once. Decrypts the device and twrp can then do it's thing. Encryption problems stem from booting into system with a stock boot image that has force encryption enabled without flashing magisk or supersu. They modify the kernel to prevent the device from rencrypting. Latest magisk 15.3 has zero issues keeping the phone decrypted. The modified boot warning has nothing to do with the kernel. This is caused by the debug bootloader used to achieve root on the US carrier v20's. Nothing can be done to change that. ARB has not been incremented on the h910 so that isn't an issue currently. Potentially in the future, but not right now. The problems you're having could stem from a multitude of issues. Could be modifications you made, bad flashes, etc. If you're having issues with encryption and stuff sounds like magisk wasn't functioning properly at the end. I've been rooted since last January and haven't experienced anything like that before so I'm not sure
Click to expand...
Click to collapse
Ok, I cannot possibly thank you enough for this. After this started happening, I seriously thought my phone was at the end of its life. If this were to happen, I wouldn't be able to get a new phone anytime soon. Not only did it fix the crashes (I only restarted it once, I'm not going to try to intentionally make it crash), It ALSO managed to fix my FM radio and (I think) the Google Assistant Voice Match unlock thing, both of which I never even thought I would be able to get back. Let's just hope that it stays this way. I have one last question. Would you say it's safe to download and install Magisk modules now?
NullBite said:
Ok, I cannot possibly thank you enough for this. After this started happening, I seriously thought my phone was at the end of its life. If this were to happen, I wouldn't be able to get a new phone anytime soon. Not only did it fix the crashes (I only restarted it once, I'm not going to try to intentionally make it crash), It ALSO managed to fix my FM radio and (I think) the Google Assistant Voice Match unlock thing, both of which I never even thought I would be able to get back. Let's just hope that it stays this way. I have one last question. Would you say it's safe to download and install Magisk modules now?
Click to expand...
Click to collapse
Yes. I use a few modules myself without an issue. If you're unsure of the stability of a module, you can always take a nandroid backup in twrp prior to installation. If things are stable, and then you flash something and the phone freaks out, it's most definitely the mod you have flashed causing problems. Some modules make changes to the system partition that have the potential to problems. But I haven't had a module cause my device to bootloop or reencrypt. So I think you're good to go. Glad you're phone is up and running as it should. Very strange that it was in such a bad way, but crap happens. I have had zero issues with this setup (10r + 1.4 askermk kernel + magisk 15.3).
I have the stock firmware on the H990 version, I end up on the Crash LK screen error. I can access TWRP, how can I restore access to my device without losing data? Thanks.

To start android, enter your PIN

i successfully downgraded my A2017G to Oreo b02 from b03 about a week ago. I had to do a factory reset, then set it up with my Google account and after that it allowed to install b02.
After that I've only installed a few basic apps for my bank and so on while waiting for b04 to show up through OTA.
Anyway, fast forward to today. I haven't had any issues with it. But all of a sudden when coming back from working in another town its rebooted and ask me to enter PIN to start Android. After that when it's done rebooting I got some weird double spacing between rows of icons.
So, I reboot again and once more i have to enter pin to start Android.. But it looks better when finished. However, this Enter PIN to start Android feels a bit annoying. Apparently it's because Android thinks my phone is behaving strange. Is there a way to find out what it thinks is strange and stop it?
It may be a security requirement for your banking app. It's secure boot.
This is part of the options with lock screen method. Maybe try setting the phone back to a swipe unlock and restart, see if it stops the problem. If so, set up you preferred lock arrangement again.
Thanks. Sounds reasonable although I've been running these apps on this phone since I bought it back in 2016(maybe it's time for a new phone) with various Android versions and never had this before. The phone has also been running for about a week with the same ROM and app version before this happened.
I'd backup data and reset it. See if it runs better, but you could try going to stock recovery and clear the cache first, just in case that helps.
There may be some junk from flashing it.
Seems like a factory reset did the trick. It's been running smoothly for some time nu despite installing the same apps again. I even got the b04 upgrade through OTA. Thanks!
Cool, so you're happy with the A7 again?
I regressed mine from B03 to B02 and did forced update to B04 from stock recovery. Had a few hiccups but sorted them and it works ok now. Do want to reset it when practical though. I use it for work so not in a huge hurry, setup is a big deal........
RobboW said:
Cool, so you're happy with the A7 again?
Click to expand...
Click to collapse
Sort of happy I guess. There are still a few things like it not automatically mounting my sdcard after reboot and I'm a little thoughtful about how many more updates it will receive. But it works rather well now and I haven't found a suitable replacement yet so I'm happy with it for the moment.

Categories

Resources