I have an Motorola G6 Play XT1922-3 and after the Pie update the screen becomes randomly unresponsive, every 3-5 minutes or so. Locking and unlocking the phone fixes the issue but it's really annoying, especially if you have some kind of security on the lock screen; also I don't think is a hardware issue since only this method works, nothing 'physical' works (like slaps, bumps, etc. :laugh: ).
Do you know some kind of fixes for this?
When my Moto G6 got the first Pie update it was laggy. All over the place random laggy. The fix that was suggested (and it worked) was to reflash the phone with the RSD lite tool and the same OTA rom from https://mirrors.lolinet.com/firmware/moto/ali/official/RETUS/. Note make sure you grab the correct rom from https://mirrors.lolinet.com/firmware/moto/ and the correct channel for you specific device.
-Chris
I've been struggling with the same issues as the first poster - random screen freeze until the phone is locked and unlocked which I also think is some sort of software issue since updating to Pie. Has anyone managed to find a fix for this at all?
richtee74 said:
I've been struggling with the same issues as the first poster - random screen freeze until the phone is locked and unlocked which I also think is some sort of software issue since updating to Pie. Has anyone managed to find a fix for this at all?
Click to expand...
Click to collapse
A friend of mine had his G6 lagging a lot, factory reset did the trick for him.
I and currently using Descendant 3, but in my experience it has other issues, so, I would suggest the factory reset, or rooting stock Pie, if you are into that sort of thing.
Related
I have a 2013 MotoX. I haven't done anything special to it (eg, I haven't rooted it or installed a custom OS on it).
It runs fine most of the time. However, every so often, it reboots and goes through the "optimizing apps" thing that usually happens after an update. However, it doesn't seem like this is for a real update since the Android version doesn't change when I look in the settings and since it's supposed to ask before installing an update.
Does anyone have any ideas why this might be happening or how to fix it? I don't have an easy way to reproduce it, but it's been happening off and on for years.
Thanks!
meviin said:
I have a 2013 MotoX. I haven't done anything special to it (eg, I haven't rooted it or installed a custom OS on it).
It runs fine most of the time. However, every so often, it reboots and goes through the "optimizing apps" thing that usually happens after an update. However, it doesn't seem like this is for a real update since the Android version doesn't change when I look in the settings and since it's supposed to ask before installing an update.
Does anyone have any ideas why this might be happening or how to fix it? I don't have an easy way to reproduce it, but it's been happening off and on for years.
Thanks!
Click to expand...
Click to collapse
Factory reset it or try clearing cache
Hello experts,
Since Oreo was pushed to my S7 Edge through OTA, it has been nothing but trouble. My phone is extremely sluggish and unresponsive, to the point that when I get a call, the phone rings but doesn't come on so I cant answer the phone. I have wiped out cache multiple times and even factory reset it couple of times and the phone is still very slow. I have been reading here trying to find a solution, but have not been very successful.
The Baseband Version on my phone is "G935AUCS8CRK1". From reading all the threads here, it looks like I am on BB8 and stuck and wont be able to upgrade or downgrade. But still I thought I post the question here and one of you experts can confirm and/or suggest a solution for the problem I am experiencing.
If it is not possible to flash any rom once on BB8, is there anything I can do to improve the performance of my S7 edge after Oreo upgrade? As mentioned above, I have wiped and cache and done a factory reset multiple times with no luck. Am I the only one experiencing the lag/sluggishness?
Thanks in advance for your suggestions and support!
I have had occasional slowdowns on Oreo, but nothing like what you are describing. There is a bit of lag when an incoming call comes in that wasn't there before, and I often see a purple screen for a second before it pulls up the contact info, but it is ringing as this happens. I have never had an issue answering a call, etc. I am CRK2, though, not CRK1. Overall, the lack of keyboard lag, which made me despise Nougat on this phone, makes up for the occasional lag elsewhere.
Unfortunately, you can't downgrade the bootloader/baseband, so you can only run software builds that are based on that version - all of which, I believe, are Oreo builds now.
Mine is running very well, very improved. The only problem that I have is the battery drain, I can hardly reach 4 hours of screen on time on battery, but the normal average is 3, 3.5 hours of screen on time. So sad that actually is not a way to downgrade to B8
Hello i have a Moto G6 that i brought from ebay for $30 originally $50 because i wasn't told it was google locked so i bypass it and made him give me a discount. It's in flawless condition but it freezes which is why i brought it thinking of just flashing back a rom for a easy fix but the phone never stop freezing. I flashed pie which most people complain was causing the freezing but it actually froze less than when it was on oreo which is weird. I than unlock the bootloader flash back pie after flashing multiple oreo/pie revisions without any luck. Also i install the nova launcher which help just like lineage but eventually it will freeze/bootloop. When i flashed pie i flashed lineage os 16 which did help but the phone still freezes. Since i really need a reliable phone coming from a Z2 play with proximity sensor issues but i can't say it wasn't reliable or not very strong. I got a broken Moto G6 with a crack screen but the device still works and doesn't freeze or bootloop yet so i am going to take the board and put it on my like new Moto G6. I just want a tip that will prevent the device to start freezing or bootlooping in the future. I am thinking flashing pie than flashing lineage os 16 for the long run just like i did with the old board because from my understanding leaving the phone stock on oreo or pie eventually it will cause it to freeze/bootloop and even though you do a factory reset or flash a stock rom it seems like stock firmware over time does permanent damage to the board in some way. That is just my theory, a crazy one but after reading all of this i might be on to something
I have a G6 (XT1925-6) on the latest stock rom (pie). It never freezes or bootloops on me. It runs for weeks at a time without issue.
I suspect you do have a bad board, but I suppose you could maybe try flashing the latest stock rom and see if anything changes.
I can confirm that there are no issues.
Guys,
try to install Chrome Beta and use it as default WebView provider (settings in Developer Options).
For me was a silver bullet: stopped a lot of force closing and random boots.
Good luck!
On my Verizon Note 9, not rooted. Holding down the power button doesn't help. I have to hold the power and vol down key to reboot phone.
Has anyone else had this issue, or have a solution?
Try booting into Recovery Mode and wipe the cache partition. If that doesn't work. Then I would manually reinstall the stock OS back onto your device as there is a chance something went wrong during the OTA installation process.
n960f exynos, im also experiencing random freezes after android 10 update. Once-twice a week. First screen doesn't show any updates, but i can feel haptic feedback, so i presume everything works underneath freezed screen, and shortly after that phone freezes completly( with screen still on) , only holding down power for 30sec seems to helps.
Unfortunately clearing cache nor fresh odin flashing of full firmware helped. I noticed it is happening while phone is warm from charging or just plain using.
wodzini said:
n960f exynos, im also experiencing random freezes after android 10 update. Once-twice a week. First screen doesn't show any updates, but i can feel haptic feedback, so i presume everything works underneath freezed screen, and shortly after that phone freezes completly( with screen still on) , only holding down power for 30sec seems to helps.
Unfortunately clearing cache nor fresh odin flashing of full firmware helped. I noticed it is happening while phone is warm from charging or just plain using.
Click to expand...
Click to collapse
N960u, not a single issue with 10. Been using it since beta. So maybe the exynos version has bugs
Nope, Op has a Verizon phone...
That's US only isn't it?
Maybe Canada...
My Exynos Note 9 hasn't had any problems since I updated to 10 either but then again, different set-ups may cause different issues...
ultramag69 said:
Nope, Op has a Verizon phone...
That's US only isn't it?
Maybe Canada...
My Exynos Note 9 hasn't had any problems since I updated to 10 either but then again, different set-ups may cause different issues...
Click to expand...
Click to collapse
I'm in the US (Michigan), and have a snapdragon version.
So the question is, anyone with an Exynos Chipset experiencing the same problem as this may indeed be a Snapdragon related problem( with this, admittedly limited, sample it seems so)...
ultramag69 said:
So the question is, anyone with an Exynos Chipset experiencing the same problem as this may indeed be a Snapdragon related problem( with this, admittedly limited, sample it seems so)...
Click to expand...
Click to collapse
Maybe. All I know now is I'm beginning to regret updating. At first my phone was fine. But after a few days, it's sluggish. And to let me know it's not just an isolated problem, my wife's S-9 (on a different carrier) has begun to experience the same issues as my Note 9.
I swear, if it wasn't for the S-pen, I'd have gone over to Apple by now. Android is just one headache after another.
Kamau54 said:
Maybe. All I know now is I'm beginning to regret updating. At first my phone was fine. But after a few days, it's sluggish. And to let me know it's not just an isolated problem, my wife's S-9 (on a different carrier) has begun to experience the same issues as my Note 9.
I swear, if it wasn't for the S-pen, I'd have gone over to Apple by now. Android is just one headache after another.
Click to expand...
Click to collapse
You can just downgrade back to pie it's not that big of deal.
wodzini said:
n960f exynos, im also experiencing random freezes after android 10 update. Once-twice a week. First screen doesn't show any updates, but i can feel haptic feedback, so i presume everything works underneath freezed screen, and shortly after that phone freezes completly( with screen still on) , only holding down power for 30sec seems to helps.
Unfortunately clearing cache nor fresh odin flashing of full firmware helped. I noticed it is happening while phone is warm from charging or just plain using.
Click to expand...
Click to collapse
Well.. After march security updates, random freezes stopped.
I couldnt find a solution or the same issue on the forums.. so here is my problem:
Pixel 4XLs face unlock is so bad. After a few unlocks the phone says "clean sensor". Rebooting usually does the job for a few hours.
I browsed the web and this error is common on so many Pixel 4/XL devices.
Is there a solution to this? Any CustomROM or Kernel solving this issue?
I am on stock kernel/ROM and wiped the whole thing before freshly installing Android 12.
Thanks!
Matzeus said:
I couldnt find a solution or the same issue on the forums.. so here is my problem:
Pixel 4XLs face unlock is so bad. After a few unlocks the phone says "clean sensor". Rebooting usually does the job for a few hours.
I browsed the web and this error is common on so many Pixel 4/XL devices.
Is there a solution to this? Any CustomROM or Kernel solving this issue?
I am on stock kernel/ROM and wiped the whole thing before freshly installing Android 12.
Thanks!
Click to expand...
Click to collapse
Probably a hardware issue. Find one of the many sensor testing apps and run it several times to identify a weak or defective sensor. There is not going to be a cleaning or software solution. If you do find a sensor not working 100%, do another clean wipe and test again before looking into replacement. Normally the FR on the P4 is extremely fast and accurate.
Thanks @v12xke for your reply!
To be honest, i dont think it's an hardware issue. See this link on the google forums: https://support.google.com/pixelpho...ing-the-dreaded-clean-the-top-of-screen?hl=en
There are countless other posts and threads about this error.
I should mention that the issue was there from time to time on Android 11 too. Looking at googles changelog, they tried to "fix" the issue in their updates. Nothing helped yet.
Matzeus said:
Thanks @v12xke for your reply!
To be honest, i dont think it's an hardware issue. See this link on the google forums: https://support.google.com/pixelpho...ing-the-dreaded-clean-the-top-of-screen?hl=en
There are countless other posts and threads about this error.
I should mention that the issue was there from time to time on Android 11 too. Looking at googles changelog, they tried to "fix" the issue in their updates. Nothing helped yet.
Click to expand...
Click to collapse
Google forums are a joke, this issue has *nothing* to do with Android11 or 12... and no, there is not a fix coming from anywhere. You're going to have to fix it yourself. Have you removed and re-added your facial profile at least once or twice since this started? Have you been able to replicate in safe mode? How can you know it is not a hardware issue if you don't test the sensors? It's just one step in the process of elimination. Try these and you may discover something you didn't know before.
v12xke said:
Google forums are a joke, this issue has *nothing* to do with Android11 or 12... and no, there is not a fix coming from anywhere. You're going to have to fix it yourself. Have you removed and re-added your facial profile at least once or twice since this started? Have you been able to replicate in safe mode? How can you know it is not a hardware issue if you don't test the sensors? It's just one step in the process of elimination. Try these and you may discover something you didn't know before.
Click to expand...
Click to collapse
How can you say google forums are a joke when literally hundreds of people are having the same issue? I dont want to believe that we all have hardware issues. Otherwise the hardware would be some hot garbage.
I removed and readded the face multiple times already.
I booted into safe mode. It works there. But like I said, it also works after a normal reboot for some hours/days before it needs a reboot again.
I also did test the sensors, no errors there. However my next step is to run the test when the error is present.
Any specific suggestion on which app I should use for testing?
Thanks again.
@Matzeus
No specific sensor app. Facial data is stored on the Titan M chip, and the only way I know to wipe that facial data and potentially fix it is by doing a factory reset from the stock recovery. Fastboot flashing will not wipe the Titan data and even from recovery is only a partial wipe. If you've ever had TWRP installed, there is a looong thread on broken face lock there. FDR from both recovery and setup would be my next suggestion.
@v12xke
In the past i ran the factory default from the system settings, didnt help. After that I used Googles "Android Flash Tool", which didnt help either.
Additional information: the device has never been rooted or anything. Always been on stock firmware.
Anyways, small update on the whole thing:
The issue occured again, I ran the app "Soli Sandbox" and it simply didnt do anything. So far so good.
After closing Soli Sandbox and clicking on the face unlock option in the system settings, magically everything worked properly again. Even without a reboot.
I am not sure what solved the error now..
I guess its safe to say, that all motion gestures stop working once the problem occurs.
Will keep this thread updated as I find out more.
I've had absolutely no major issues with my Pixel 4 XL's face unlock. I've upgraded from android 11 to 12 and still working perfectly. Yeah, i get the odd clean the bar notification but goes away after a bit and it just works.
The face unlock is fantastic on the Pixel 4 XL
The march update claims to have brought some improvements to Pixel 4s face unlock feature. At least thats what they say in the official changelog.
Biometrics
General improvements for face unlock stability & performance *[4]
Lets see if the problem is gone now. Will keep this thread updated.
sufy1000 said:
I've had absolutely no major issues with my Pixel 4 XL's face unlock. I've upgraded from android 11 to 12 and still working perfectly. Yeah, i get the odd clean the bar notification but goes away after a bit and it just works.
The face unlock is fantastic on the Pixel 4 XL
Click to expand...
Click to collapse
It's uncannily good. I keep the phone upright in a cradle by my PC so I can monitor it, and all I have to do is turn my head to peek, and it unlocks every time. It's pretty amazing. I've never had a problem with it.
The last official update didnt help either. My hope for a fix from Google is gone.
-------------------
I have now installed LineageOS. Its been a week and Face Unlock is now working perfectly fine.
Will keep this thread updated in case anything stops working
Matzeus said:
The last official update didnt help either. My hope for a fix from Google is gone.
-------------------
I have now installed LineageOS. Its been a week and Face Unlock is now working perfectly fine.
Will keep this thread updated in case anything stops working
Click to expand...
Click to collapse
Still going strong? And did you notice this issue on Android 10?
@puzzlefighter
Still on LineageOS 18.1, no Face Unlock issues since I installed the ROM.
I am honestly not quite sure if this issue occured on Android 10 already. But i think so, yeah.
Matzeus said:
@puzzlefighter
Still on LineageOS 18.1, no Face Unlock issues since I installed the ROM.
I am honestly not quite sure if this issue occured on Android 10 already. But i think so, yeah.
Click to expand...
Click to collapse
Thanks. I've got a new 4 XL that definitely has this issue but I didn't spend much time with it before updating to 12 from 10. It's a real PITA. I've never installed a custom ROM, but thinking I may need to do what you've done as this is irritating af.
@puzzlefighter
Just go for it man.
I was so upset about face unlock and i regret that i didnt install a custom ROM earlier.
Share your results afterwards please if you installed a custom ROM
this is not a hardware problem, but a software one, it started with the release of android 12, the problem is not in the face unlock sensor, but in the proximity sensor, it sticks, as if it was closed with a finger, I use Pixel experience + 12, this firmware does not have this problem, I'm disappointed with google developers(