Related
I flashed the android 5.0 image from google website using NRT and then rooted the device. I have TWRP 2.8.1.0.
The problem is that my nexus 7 2012 12GB is giving me unbelievable lag. I have cleared cache and all but it is of no help.
I have no idea about F2FS but I read that changing to F2FS might help. So can any of you tell me what to do.
Falcon_Eyes said:
I flashed the android 5.0 image from google website using NRT and then rooted the device. I have TWRP 2.8.1.0.
The problem is that my nexus 7 2012 12GB is giving me unbelievable lag. I have cleared cache and all but it is of no help.
I have no idea about F2FS but I read that changing to F2FS might help. So can any of you tell me what to do.
Click to expand...
Click to collapse
I had that problem when I first flashed the factory 5.0 Image, without wiping data. It was horrid. The situation didn't improve after wiping data.
Later I flashed the ROM in my sig, and it is working very good. Occasional lag, but nothing worse than kit-kat. Overall the performance is much better than kit-kat.
I made sure to wipe, format, and repair data, cache, and system. In fact, that ROM wouldn't even boot until I did.
I wiped, formatted, and repaired, then loaded the ROM and GAPPS manually via ADB and flashed both normally using the TWRP interface.
Bootloader: 4.23
TWRP: 2810
Falcon_Eyes said:
I flashed the android 5.0 image from google website using NRT and then rooted the device. I have TWRP 2.8.1.0.
The problem is that my nexus 7 2012 12GB is giving me unbelievable lag. I have cleared cache and all but it is of no help.
I have no idea about F2FS but I read that changing to F2FS might help. So can any of you tell me what to do.
Click to expand...
Click to collapse
Factory reset does wonders. Lollipop works great after
I was having the same issue, then uninstalled Facebook and it has been fine since.
I had lag issue with google launcher. I am using launch came with Rom and nexus is much better. I am using f2fs Rom w/o google launcher. It's very usable.
I turned on Develop Options then scrolled to the bottom and checked off "Kill all activities when you leave them" and I really don't have the lag anymore.
FSRBIKER said:
I turned on Develop Options then scrolled to the bottom and checked off "Kill all activities when you leave them" and I really don't have the lag anymore.
Click to expand...
Click to collapse
Thank you for this tip. I did this and now its like having a whole different tablet. It is usable again. The only thing is in my developer options it is called "Don't Keep Activities."
I was writing the post from memory but your correct on the name. Glad it helped.
Sent from my Z3 Compact
piratesscareme said:
Thank you for this tip. I did this and now its like having a whole different tablet. It is usable again. The only thing is in my developer options it is called "Don't Keep Activities."
Click to expand...
Click to collapse
Also, scale all the animation speeds down to 0.5x in Developer Options and you'll love the snappiness It works great on my Nexus 7.
wiped cache, 'Don't Keep Activities' and whatever i could find still laggy as sh*t. Will wait for 5.0.1 OTA if that doesn't work back to 4.4.4. Any other suggestions without resetting/wiping ?
Try to run fstrim on /cache and /data
try this fix
I was able to fix my nexus 7 2012 lagging problem after the lollipop update and now it is as fast as before. I posted a video on how I did it and there is no downgrade or rooting required. Here is the link youtube.com/watch?v=OH2iYdr91DE
jamesmat said:
I was able to fix my nexus 7 2012 lagging problem after the lollipop update and now it is as fast as before. I posted a video on how I did it and there is no downgrade or rooting required. Here is the link youtube.com/watch?v=OH2iYdr91DE
Click to expand...
Click to collapse
u captured and uploaded a whole video just to tell us that the lag was fixed after turning location service off?!
I just received my nexus 7 2012, bought it from someone and it had 5.0.2 already installed on it.
This thing is sooo slow that i was wondering if i made a bad buy by getting this model.
Everything is super laggy, for example,.. 9gag or facebook, when it finally loads i cant scroll through it, its so slow it crashes the application before scrolling down.
I tried the wipe cache, enabled "dont keep activities" and set all animations to .5 in dev mode. i tried disabling location.
It all made it a bit more usable,.. but i read people having a smooth and fast device... which i dont have still.
what else could i try? as far as i know its not rooted and has the stock rom.
I really want to like this device but its not happening so far.
Any help is really appreciated
Most of the custom roms fix this issue. very fast now!
I am waiting for 5.0.3 and hoping it helps!
rbeavers said:
I am waiting for 5.0.3 and hoping it helps!
Click to expand...
Click to collapse
I am not going to hold my breath. After I did a full wipe & installed 5.02 that did seem to help.
I had really bad lag after flashing 5.0.2. I discovered (while trying to install Busybox) that the system partition was full. I deleted a few system apps (stuff I could get from Google Play if I ever needed it down the road), freed up a few megs, and things got instantly better.
Lost 1/2 my storage space
After factory resetting & flashing LRX22G on my 16Gb nakasi/grouper Nexus 7, it has turned into an 8Gb device... I've just spent the past 7 hours setting it all up again, so I am less than keen on factory resetting it all yet again to try & get it working as well as it did under Kitkat before I was stupid enough to upgrade to Lollipop. On the plus side, the horrible lag has finally gone (I think that it is the factory resets & cache wipes that fixes it, but I could be wrong). Now all I need to do is to find out how to convince it that it is a 16Gb version without having to factory reset it. Does anyone have any good advice on that please?
JustinSB said:
...On the plus side, the horrible lag has finally gone...
Click to expand...
Click to collapse
No, I take it all back! The horrible lag & frequent crashes are still here on 5.0.2 & exactly the same as they were on 5.0, & after an afternoon trying to use my tablet I am having no luck. Now my problem is that because I have lost half of my storage space, I don't have enough space to copy back my nandroid backup of my lovely, fast, & fully functional Kitkat installation.
Thanks to XDA, I've been running LineageOS 14.1 on my LEX727 for months now, updating to most nightly releases with no issues. However, when the phone rebooted after updating to the 10/20/17 nightly, it got stuck on the boot animation screen (green circle moving right to left on the arc) and would go no further. I rebooted into TWRP and flashed back to 10/13 which has been working fine. Same results after attempted updates to the 10/27 and 11/3 releases. I even tried a manual update from TWRP using USB OTG with the same result.
Any ideas of what's gone wrong here? Anything I can try? All I know to do at this point is wipe and install clean but I'd rather not if possible. Thanks!
fraxby79 said:
Thanks to XDA, I've been running LineageOS 14.1 on my LEX727 for months now, updating to most nightly releases with no issues. However, when the phone rebooted after updating to the 10/20/17 nightly, it got stuck on the boot animation screen (green circle moving right to left on the arc) and would go no further. I rebooted into TWRP and flashed back to 10/13 which has been working fine. Same results after attempted updates to the 10/27 and 11/3 releases. I even tried a manual update from TWRP using USB OTG with the same result.
Any ideas of what's gone wrong here? Anything I can try? All I know to do at this point is wipe and install clean but I'd rather not if possible. Thanks!
Click to expand...
Click to collapse
I'd say do a clean install. If i have any issues with a rom booting i'll factory reset and install again. If i still have issues i'll just use another rom.
fraxby79 said:
Thanks to XDA, I've been running LineageOS 14.1 on my LEX727 for months now, updating to most nightly releases with no issues. However, when the phone rebooted after updating to the 10/20/17 nightly, it got stuck on the boot animation screen (green circle moving right to left on the arc) and would go no further. I rebooted into TWRP and flashed back to 10/13 which has been working fine. Same results after attempted updates to the 10/27 and 11/3 releases. I even tried a manual update from TWRP using USB OTG with the same result.
Any ideas of what's gone wrong here? Anything I can try? All I know to do at this point is wipe and install clean but I'd rather not if possible. Thanks!
Click to expand...
Click to collapse
I am in the same situation. Have tried all combinations of wiping and resetting with all 3 of the latest nightlies and still cannot boot. I can successfully boot into a stock rom but, I'd rather not. I guess I will go back to the 10/13 nightly since it worked (mostly) before this debacle. Hopefully next week's update will solve this problem.
Thanks for your reply, islandlife98. I'm not super-confident at this ROM thing yet so backing up, wiping and reinstalling is something I'd undertake reluctantly. I was hoping this was a common situation with a simple fix that I just had been unable to find. Always prefer to actually solve a problem if possible rather than just wipe it out. (Although when it comes to tech, wiping it out is often the best or only solution. Almost always the quickest.)
JBealZy, thank you for letting me know you're in the same boat! After seeing no mention of this issue here, I assumed it was some weird glitch with my phone rather than a problem with the updates. If you've done a full wipe and re-install but still haven't been able to boot into any of the last three releases then I'm glad I hesitated. (That was a concern I'd had: that it might not work even after a clean install.) Think I'll stick with 10/13 for now and keep trying the new releases; easy enough to roll back if it fails now that I've figured it out.
Lmao same problem here with the 2017-11-11 and 2017-11-03 udpate. Not tested yet with 2017-10-27 or 2017-10-20 but that's my last choice because after 2017-10-13 update all links are removed. I do a clean install every time .. What other rom is better ?
Problem resolved .. i have wiped internal storage too and able to install the last version. I think i'm gonna use another ROM because i don't really want to reinstall all of my applications everytime i do an update. :/
Deediezi said:
Lmao same problem here with the 2017-11-11 and 2017-11-03 udpate. Not tested yet with 2017-10-27 or 2017-10-20 but that's my last choice because after 2017-10-13 update all links are removed. I do a clean install every time .. What other rom is better ?
Problem resolved .. i have wiped internal storage too and able to install the last version. I think i'm gonna use another ROM because i don't really want to reinstall all of my applications everytime i do an update. :/
Click to expand...
Click to collapse
I am using Paranoid ( latest version) and everything works flawlessly.
Sent from my LEX727 using XDA Labs
Deediezi said:
Lmao same problem here with the 2017-11-11 and 2017-11-03 udpate. Not tested yet with 2017-10-27 or 2017-10-20 but that's my last choice because after 2017-10-13 update all links are removed. I do a clean install every time .. What other rom is better ?
Problem resolved .. i have wiped internal storage too and able to install the last version. I think i'm gonna use another ROM because i don't really want to reinstall all of my applications everytime i do an update. :/
Click to expand...
Click to collapse
Another victim! So weird, I wonder what's going on there. None of the updates since my original post have worked so I've come to the conclusion that I'm going to have to do a clean install. Just need to find a time do it. Good to hear it worked for you.
LineageOS is the only ROM I've tried but since I have to wipe my phone anyway I may try some others. Paranoid Android looks interesting and Tsongming says it's working well.
fraxby79 said:
Another victim! So weird, I wonder what's going on there. None of the updates since my original post have worked so I've come to the conclusion that I'm going to have to do a clean install. Just need to find a time do it. Good to hear it worked for you.
LineageOS is the only ROM I've tried but since I have to wipe my phone anyway I may try some others. Paranoid Android looks interesting and Tsongming says it's working well.
Click to expand...
Click to collapse
Yea i'm downloading Paranoïd right now for testing it .. Don't want a broken operating system on my phone haha
If anyone's still interested, I first tried flashing Lineage after wiping all but internal storage and still couldn't get past the boot animation. Then did a full factory-reset wipe including the internal storage, re-flashed, and it finally booted. The first OTA update since then came through today and went off without a hitch so all seems well for now.
I did take a look at Paranoid before going back to Lineage. One big reason I use a custom ROM is to get security updates quickly and LOS reports the security patch level in the settings; I couldn't find this info in PA. Also, I use a pattern to unlock my phone and there didn't appear to be a way use a larger grid than the default 3x3. On the plus side (sort of), PA includes the LeEco remote control app, which seems to be the only way to use the IR hardware on this phone, but it asks for more permissions than I want to give (which, of course, is not PA's fault). So admittedly I didn't really give it a full and fair trial but those few little issues sent me back to the (usually) reliable familiarity of LOS.
I received a new LEX722 yesterday. The TWRP for zl1 is working fine, but I cannot get lineagos working.
I deleted:
- dalvik,
- system,
- cache
- data
- and also the internal storage
after rebooting into twrp I enabled usb debugguung and pushed the lineageos and gapps images via adb push to the phone.
I installed lineageos and gapps nano, but after booting to system, I get stuck in a black screen looping to a dark grey luminated display (no graphics at all).
Heistergand said:
I received a new LEX722 yesterday. The TWRP for zl1 is working fine, but I cannot get lineagos working.
I deleted:
- dalvik,
- system,
- cache
- data
- and also the internal storage
after rebooting into twrp I enabled usb debugguung and pushed the lineageos and gapps images via adb push to the phone.
I installed lineageos and gapps nano, but after booting to system, I get stuck in a black screen looping to a dark grey luminated display (no graphics at all).
Click to expand...
Click to collapse
Sorry, can't help you with that since I have a LEX727 which is apparently quite different from the LEX722. Official LineageOS is only supported on the LEX720 and LEX727: [ https://wiki.lineageos.org/devices/zl1 ]. The LEX722 (Elite) has it's own section here on the LeEco Pro 3 forum so check that out and see what they've come up with.
Hello everyone,
I have random soft reboots on my LG G6 Europe variant.
Bootloader is unlocked and custom Rom Fulmics Rom 4.2 is installed.
Does anybody experiencing the same problem?
The reboots happens after some days randomly....
Thx and regards
it is necessary to speak about it in the dedicated subject, more chances to cross someone in the same situation or who can help you
aking007 said:
Hello everyone,
I have random soft reboots on my LG G6 Europe variant.
Bootloader is unlocked and custom Rom Fulmics Rom 4.2 is installed.
Does anybody experiencing the same problem?
The reboots happens after some days randomly....
Thx and regards
Click to expand...
Click to collapse
Had the same problem on stock ROM, but the last update with january security patch fixed it.
Maybe a factory reset fixes the issue?
Krysdyan said:
Had the same problem on stock ROM, but the last update with january security patch fixed it.
Maybe a factory reset fixes the issue?
Click to expand...
Click to collapse
I did make a clean install through TRWP. WIPED cache and dalvik cache. deleted internal data and system data.
I had random soft reboots before I was on fulmics Rom as well. so I think it's not specific to this Rom....
how many times did your device rebooted?
aking007 said:
I did make a clean install through TRWP. WIPED cache and dalvik cache. deleted internal data and system data.
I had random soft reboots before I was on fulmics Rom as well. so I think it's not specific to this Rom....
how many times did your device rebooted?
Click to expand...
Click to collapse
On which base is Fulmics yet?
The reboots happened once a week, or sometimes even twice a day.
I had this happen on stock. After much reading of logcat output I was able to determine some kind of system table was getting exhausted. Proceeding on the theory that some app must be misbehaving to cause this, I disabled or uninstalled as many apps as I reasonably could, concentrating on what I could remember having installed or updated recently, and the reboots went away (I am paying close attention as I gradually re-enable or re-install stuff but haven't found a definitive culprit yet).
jdock said:
I had this happen on stock. After much reading of logcat output I was able to determine some kind of system table was getting exhausted. Proceeding on the theory that some app must be misbehaving to cause this, I disabled or uninstalled as many apps as I reasonably could, concentrating on what I could remember having installed or updated recently, and the reboots went away (I am paying close attention as I gradually re-enable or re-install stuff but haven't found a definitive culprit yet).
Click to expand...
Click to collapse
I had the same thoughts.....cause the issue is not taking place continously.... so I don't think it is ha hardware issue.... still couldn't find the app which may lead to a random soft reboot
Hey all, I've had my phone for almost a month, in the most recent OTA (.11) and no root etc. Noticed the phone go to the boot screen 3x today. This is my first OnePlus device. Just wanted to know if there is any simple troubleshooting I can do without a full wipe.
Check to make sure Scheduled Turn off/on didnt get enabled. It is in Utilities section of settings.
After that i would try just a cache wipe -- shouldnt effect any of your data
I've been getting the same, it is just random, like a soft reboot right? After I updated to 9.0.11 this started happening once in a while.
Dedzdedz said:
I've been getting the same, it is just random, like a soft reboot right? After I updated to 9.0.11 this started happening once in a while.
Click to expand...
Click to collapse
Morpheus991 said:
Hey all, I've had my phone for almost a month, in the most recent OTA (.11) and no root etc. Noticed the phone go to the boot screen 3x today. This is my first OnePlus device. Just wanted to know if there is any simple troubleshooting I can do without a full wipe.
Click to expand...
Click to collapse
I regret the inconvenience. Its a known issue and will be fixed in the up-comming build. Please report the same from the community app feedback section from your end.
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.