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
Related
Experienced a really annoying problem today. My phone was in my pocket and I heard the LG boot up sound, so I figured the phone just randomly rebooted (happens about once a month, so very rate). When I checked the phone, I was at the LG initial setup screen, and all my days was gone.
I was running KitKat D80220b, with root and twrp installed. Since G2 xposed was just updated, I tweaked for custom navigation buttons and bleed immersive mode. Has this happened to anyone ?
For now, I reinstalled D80220c and will only root, and probably wait till G2 xposed becomes more stable on KitKat. Thoughts, anybody ?
ganja_guru said:
Experienced a really annoying problem today. My phone was in my pocket and I heard the LG boot up sound, so I figured the phone just randomly rebooted (happens about once a month, so very rate). When I checked the phone, I was at the LG initial setup screen, and all my days was gone.
I was running KitKat D80220b, with root and twrp installed. Since G2 xposed was just updated, I tweaked for custom navigation buttons and bleed immersive mode. Has this happened to anyone ?
For now, I reinstalled D80220c and will only root, and probably wait till G2 xposed becomes more stable on KitKat. Thoughts, anybody ?
Click to expand...
Click to collapse
I also have the "G2 Xposed" and I've never had any problems ... probably the hard reset is enough to solve the problem
ganja_guru said:
Experienced a really annoying problem today. My phone was in my pocket and I heard the LG boot up sound, so I figured the phone just randomly rebooted (happens about once a month, so very rate). When I checked the phone, I was at the LG initial setup screen, and all my days was gone.
I was running KitKat D80220b, with root and twrp installed. Since G2 xposed was just updated, I tweaked for custom navigation buttons and bleed immersive mode. Has this happened to anyone ?
For now, I reinstalled D80220c and will only root, and probably wait till G2 xposed becomes more stable on KitKat. Thoughts, anybody ?
Click to expand...
Click to collapse
I think the same crap happened to me. Check THIS Post I made back at the AEON thread. I haven't been able to boot my phone correctly this last two days.It keeps rebooting after a minute or so after booting. Very annoying and even worse that I don't what caused this crap. If you got any possible solution and can help me get out of this reboot loop it would be very appreciated.
Kenepo said:
I think the same crap happened to me. Check THIS Post I made back at the AEON thread. I haven't been able to boot my phone correctly this last two days.It keeps rebooting after a minute or so after booting. Very annoying and even worse that I don't what caused this crap. If you got any possible solution and can help me get out of this reboot loop it would be very appreciated.
Click to expand...
Click to collapse
Maybe it's a stuck power button? If not, have you tried going back to stock using the LG flash tool?
Hi. I rooted my LG G2 (D802TA) using LG One Click Root a fortnight ago. Android 4.4.4 stock, no change in kernel or ROM. 5GB memory available. RootChecker shows that the rooting was successful.
The phone was performing beautifully before root. Since rooting the phone has had problems with briefly freezing frequently, occasional non-responsiveness of keyboard or apps, and sometimes the lockscreen. Is there anything I can do that might fix this, other than a factory reset? I realise this is a vague set of symptoms, sorry.
Hello people of the world,
after reading a lot of posts here I still can't fix my phone's issues, so I need to post. Bear with me...
I have an N910F which was entirely stock and functioning without problems. Two days ago I accepted the official update. After that, the phone regularly lost connection to the mobile net, froze, and restarted. It would work for a short while until it froze and restarted again and again. When I tried to use the camera, the live picture was completely distorted. The phone crashed and has then gone into a bootloop.
I pulled the battery, did a recovery start and wiped the cache. No difference. Factory recovery next, no difference.
I have since tried several stock and custom firmwares, always taking care to follow instructions and use the correct bootloaders, modems, etc. TWRP is working.
When I flash a stock firmware, it will go into a bootloop. With any custom ROM, it will crash during startup (logo) and switch off.
Any help would be greatly appreciated!
Protect the eMMC?
So, after more reading I began to suspect that the eMMC had moved on to the valhalla of electronics. Sent my phone to service where my suspicion was confirmed. Luckily, they were able to replace the chip without having to put in a new board.
Is there any way to prevent this kind of failure again, or at least make it less likely?
Yes this is a known issue after latest update you could you install only one application called wakelock so that your phone doesn't reboot and CPU keeps awake
nicholes said:
Yes this is a known issue after latest update you could you install only one application called wakelock so that your phone doesn't reboot and CPU keeps awake
Click to expand...
Click to collapse
Thanks! I had read about that.
Got my phone back from service today, they had flashed stock 5.0.1. After checking that it worked I flashed RR 5.8.4 and installed Wake Lock Powermanager. I searched for a comprehensive tutorial on what the settings do and which to use. Right now I set it to PARTIAL_WAKE_LOCK (4) but I'd like to read more about it. Any tips on that?
tullian said:
Thanks! I had read about that.
Got my phone back from service today, they had flashed stock 5.0.1. After checking that it worked I flashed RR 5.8.4 and installed Wake Lock Powermanager. I searched for a comprehensive tutorial on what the settings do and which to use. Right now I set it to PARTIAL_WAKE_LOCK (4) but I'd like to read more about it. Any tips on that?
Click to expand...
Click to collapse
installing power wakelock and setting up on partial wake lock is enough.if you get trouble in starting your phone remove its battery and put your phone in refrigerator for five min.and try to start your phone.this problem also related and happens after the latest update
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.
Hi,
Don't mean to cross post but the T-Mobile forums probably don't get as much traffic as this one. Anyway...
I got my H872 G6 in July of 2019. After unlocking the bootloader, installing TWRP, and rooting following the guide from @runningnak3d, I flashed this ROM and have been using it daily ever since. Unfortunately, the other night I took a Magisk update (20.2) that put my phone in a fastboot bootloop. After much freaking out I managed to get into TWRP - but I was still freaking out since it wouldn't boot the system no matter what I did. In my frantic panic I really borked my phone trying anything to get back up and running. My nandroid was no good either. As a last resort, I reflashed the same ROM and am back in business. Only problem is that the camera won't function (just a black screen) and a handful of user apps force close. Not sure why. I've attached a log for the camera and one for a user app (Jellyfin). Logs are in this link.
Any thoughts?
Thanks!
Solved...well, more like abandoned.
Tried a couple times to get the stock Oreo 20g rom to work but kept running into the same camera and app issues. Decided to format data, wipe everything, and install PE10 ROM. Been less than a day but it appears to be running fine. Camera works, apps aren't force closing. It's just a matter of getting used to Android 10 and setting the phone up to my liking.
Still curious why the stock Oreo ROM wouldn't function properly anymore.