Hello,
I have an issue with my Pixel 6 Pro that is rooted with Magisk. When the always on screen is on and there is a timer or stopwatch running for example, it freezes for multiple seconds.
This only happens when the phone is not moving, if I pick it up from the table it starts working again...
Also, the fingerprint scanner doesn't light up when it is in this state.
I suppose it's not normal because my friend who has a Pixel 7 doesn't have this issue
Any idea of what could be causing this?
Edit: Here's a video of it happening
Edit 2: It can also be seen on screen recordings so i don't think it's a hardware issue (on these it just jumps to the next update so it doesn't hang but it skips multiple seconds at once)
I get all sorts of problems with my rooted 6 pro, including this. I've almost actually come close to snapping the device in half in my rage at the malfunction of it.
Is clock battery optimized? I can't remember if i had this issue, if i remember in thr morning i might try. What the shortest timer you've experienced this with?
fil3s said:
I get all sorts of problems with my rooted 6 pro, including this. I've almost actually come close to snapping the device in half in my rage at the malfunction of it.
Click to expand...
Click to collapse
Yeah I agree that this is really annoying, root shouldn't cause issues like this...
Nergal di Cuthah said:
Is clock battery optimized? I can't remember if i had this issue, if i remember in thr morning i might try. What the shortest timer you've experienced this with?
Click to expand...
Click to collapse
It always starts at 00:59 and it struggles to roll over to 01:00
I tried it with battery optimization off for the Clock app and turning off Adaptive battery but it didn't help
KszKristof said:
Yeah I agree that this is really annoying, root shouldn't cause issues like this...
Click to expand...
Click to collapse
After reading the post again and watching the video, this doesn't happen on my p6 pro.
How do you flash your updates? What was your experience like without magisk?
Good point in your reply, it's been so long since I've actually been non rooted
fil3s said:
After reading the post again and watching the video, this doesn't happen on my p6 pro.
How do you flash your updates? What was your experience like on stock?
Good point in your reply, it's been so long since I've actually been non rooted
Click to expand...
Click to collapse
I actually got the phone about a week ago and I rooted it instantly so I didn't use stock at all. But I flashed a13 through fastboot first to prevent bricking it due to the bootloader version.
Related
So, I bought it on launch day and I'm getting desperate...
1) Wake screen after receiving notification (text etc). Pull down notification bar, back and multitask soft buttons grey out and phone will not respond. If I'm listening to music when this happens, the song keeps playing until I pull the battery or the phone reboots itself.
2) General lag is awful... More than half the time it has noticeable hangs switching apps or opening anything. I'm down to next to no apps that i've installed and have even tried removing just about everything I have with no improvement. Scrolling stutters about half the time as well. And the image you see with the camera open stutters badly also. Every once in a while it's buttery smooth for a few seconds then slows again.
Battery life is great and I love the form factor of this phone. I REALLY don't want to get rid of it but I'm at the point where it's more important to have a phone that's usable than have the extra screen size etc.
It's bone stock and I haven't tried a factory reset.
Suggestions?
Try the factory reset then go from there.
sonspot said:
Try the factory reset then go from there.
Click to expand...
Click to collapse
Or reflash the whole firmware using LGFlashTool. Might help.
Sent from my LG-D851
Well, I did the factory reset and no lockups or reboots yet. It's still really laggy though :-/
Gonna give it a while longer but I'm thinking it's time to root. What's the "hot setup" for the tmo version of this phone?
beyondinferno said:
Well, I did the factory reset and no lockups or reboots yet. It's still really laggy though :-/
Gonna give it a while longer but I'm thinking it's time to root. What's the "hot setup" for the tmo version of this phone?
Click to expand...
Click to collapse
Hot setup? Just use PurpleDrake.
Sent from my LG-D851
Skizzy034 said:
Hot setup? Just use PurpleDrake.
Sent from my LG-D851
Click to expand...
Click to collapse
I meant rom/mods. I've seen people mention 60fps mod for the camera but I was wondering if there was an international rom that worked with the d851 since we haven't seen any of the updates for this phone yet.
beyondinferno said:
I meant rom/mods. I've seen people mention 60fps mod for the camera but I was wondering if there was an international rom that worked with the d851 since we haven't seen any of the updates for this phone yet.
Click to expand...
Click to collapse
Delete.
beyondinferno said:
I meant rom/mods. I've seen people mention 60fps mod for the camera but I was wondering if there was an international rom that worked with the d851 since we haven't seen any of the updates for this phone yet.
Click to expand...
Click to collapse
We have the only unlocked bootloader. There are no international roms. SkyDragon is a good rom tho.
Sent from my LG-D851
Have had the Huawei Watch for a few days and it seems to have a deal-breaking bug. Frequently, after the watch has been in ambient mode for a while, it won't come out of it. If I touch the screen, the ambient display gets brighter, but that's all. No response from swiping or button presses. Sometimes, after a very long pause (a minute or so) it'll come back to life, but usually I have to hold the button until it restarts. Anyone run into this before? Ideas? Any help is greatly appreciated.
Using it with a Nexus 6. Android wear version 1.3.0.2176821.
Thanks!!!
Sent from my Nexus 6 using XDA Free mobile app
Forgot to mention that the time sticks at whatever time it freezes and so it doesn't even tell the correct time. Sigh.
Have tried a factory reset. Didn't fix it.
Sounds like it's maybe in need of replacing. Like any new product release, there's bound to be a certain percentage of failures. Depending on how you look at it, you're either really lucky, or really unlucky
Well, just in case anyone else encounters this issue, I called Huawei tech support and described my issue. After a few minutes, they came back and said it was a known issue that effects some but not all watches. They said it would be corrected in a future software update but he was unable to tell me when that would be. So I could either wait for that update or send it back for an exchange. Since it happens frequently and renders the watch temporarily unusable, I opted to exchange it. They send an RMA label next day. The joys of new tech. Hope this helps someone else.
gyromiterob said:
Well, just in case anyone else encounters this issue, I called Huawei tech support and described my issue. After a few minutes, they came back and said it was a known issue that effects some but not all watches. They said it would be corrected in a future software update but he was unable to tell me when that would be. So I could either wait for that update or send it back for an exchange. Since it happens frequently and renders the watch temporarily unusable, I opted to exchange it. They send an RMA label next day. The joys of new tech. Hope this helps someone else.
Click to expand...
Click to collapse
I have absolutely same issue. In ambient mode it freezes from the first day I bought this watch. Thank you for investigation and info.
got my hwatch and experienced the ambient mode freeze. to unfreeze, i enter and exit theater mode. it works. but now i'm never sure if the ambient time i'm glancing at is accurate or not...
Similar problem with an HTC M8. I'll try the theater mode to see if that helps. I still can't trust the time any more.
+1 on the Huawei Watch freeze. Sometimes after 15 minutes, sometimes after several hours. It has frozen with ambient mode disabled and with wrist gestures disabled as well.
Sent from my LG-V500 using Tapatalk
Two watches and no freezes here. Are you guys testing with no Wear apps installed and with a built-in Huawei face?
brizey said:
Two watches and no freezes here. Are you guys testing with no Wear apps installed and with a built-in Huawei face?
Click to expand...
Click to collapse
Yes, after factory reset with no additional apps and with original buil-in Huawei faces and used to freeze. I returned it to the shop, got new one and problem is fixed.
lukhof said:
Yes, after factory reset with no additional apps and with original buil-in Huawei faces and used to freeze. I returned it to the shop, got new one and problem is fixed.
Click to expand...
Click to collapse
Good to hear you got it fixed!
how are you sure that the problem is fixed as opposed to it not showing yet? the freeze seems to be random and i don't know of a way to replicate it on demand. thanks
maximus96 said:
how are you sure that the problem is fixed as opposed to it not showing yet? the freeze seems to be random and i don't know of a way to replicate it on demand. thanks
Click to expand...
Click to collapse
Before it froze every day several times. Now i have new one and it has been running non-stop for one week with ambient mode on and no freeze at all.
lukhof said:
Before it froze every day several times. Now i have new one and it has been running non-stop for one week with ambient mode on and no freeze at all.
Click to expand...
Click to collapse
thanks, good to know. i'm curious if your replacement watch has the red-tint issue. i wonder if the two are somehow related.
maximus96 said:
thanks, good to know. i'm curious if your replacement watch has the red-tint issue. i wonder if the two are somehow related.
Click to expand...
Click to collapse
None of them had red-tint issue. It seems this is not related with the freezing ambient mode.
Thanks, that solve my problem as well.
Happening to me too. Was using 3rd party skymaster watch face.
Got a replacement from amazon and it hasn't froze yet in the past two days of using it. The last one froze several times a day
Hello
Im having the strangest bug of all i think that were exposed in here.
I have huge issues with P2's clock/time. After a week of usage just like that, without any interfering, it just stopped progressing. It's 17:21 and that's it.
When i reboot it start to count time again for short while, then it stops again. Clearing cache from recovery helped for several hours. You know what helps ? Changing screen orientation. Somehow it refreshes time lol, but then again when 17:21:59seconds come, it wont jump onto 17:22
Wha the hell ?
I havent had this problem before. It started 2 days ago, just like that...
ps: i would prefer not to hard reset and for sure not upgrade to N
Where do you see the seconds?
Normally you can only see the minutes, right?
If it is some kind of extra setting, did you try to disable it?
Best regards
Using 3rd party launcher...?
No i dont see seconds, it was just to ilustrate the issue.
azeemzuhair said:
Using 3rd party launcher...?
Click to expand...
Click to collapse
Yes (Nova), but i switched to lenovo stock launcher and it was the same
Antaroo said:
Yes (Nova), but i switched to lenovo stock launcher and it was the same
Click to expand...
Click to collapse
My hypothesis is that any 3rd party launcher(s) has screwed the stability of the stock Firmware in general.
My unit is using the stock launcher from day 1 and until now after upgraded to Nougat, no issues which some owners claim to have in their units...
I was scratching my head when some owners claim to have "funny" issues when I cannot duplicate these issues in my unit...
As for your case, hard reset is the last resort once you have give up to find alternative solutions...
Or just buy a watch
Hey guys, I have updated to Android 10 from quite a sometime now(was a beta tester) and was noticing that device practically become usable after a few days of usage. Keyboard stops popping up, apps get killed in background and so on..
This issue gets fixed by a restart though. Has anyone else noticed something similar?
I am also facing issues after Android 10 update. Please let me know if you find permanent fix or solution.
Yes, same here. I reverted back to Pie. I thought I was the only one!
Sent from my SM-G960F using Tapatalk
Nope, you are not alone :crying:
i can confirm the exact same issue since OTA update to Android 10 on S9 (DBT). currently with second minor Update to DTAD build problem still there. Tried different things to work around but yet nothing helped. i assume it has something to do with memory leak on swap partition. memoryinfo & swapcheck app always show 0 byte free swap memory which cannot be freed again when this occurs. As stated before, only reset phone helps, but after 24h its the same. struggling with this since the first Q Update Version. Any suggestions highly appreciated.
Olioaglio
Auto-restart every morning
I didn't find any issue, and I didn't factory reset my device after installing the update. My phone runs quite smoothly, no issues whatsoever.
The only minor bug is that the transition animation of the clock from the lock screen to the always on display is laggy, and sometimes the instructions like "hold your phone more upright" get stuck on the always on display. I hope this will get fixed in the next update.
@icoolguy1995
any news on this issue? Perhaps it's any app or launcher or tool some of us use in common, since it seems not everyone is affected. i have to admit, that i have really a ton of apps on my device and freqently use it. But I already had the same conditions on Pie and there never run in this lag problem,so....
Cheers, Olioaglio
Olioaglio said:
@icoolguy1995
any news on this issue? Perhaps it's any app or launcher or tool some of us use in common, since it seems not everyone is affected. i have to admit, that i have really a ton of apps on my device and freqently use it. But I already had the same conditions on Pie and there never run in this lag problem,so....
Cheers, Olioaglio
Click to expand...
Click to collapse
Well I am still researching about this issue. I reported this issue couple of times to Samsung during beta testing; they said, they are unable to reproduce this issue neither they are able to see it on logs which I have sent. For me, the issue starts to appear after 91 hours of usage without a restart. Weirdly, using any keyboard other than Samsung Keyboard seems to help somewhat. I tried using Gboard and the issue somewhat mitigated but still annoying enough.
Did you guys tried reflashing the firmware using Odin?
icoolguy1995 said:
Did you guys tried reflashing the firmware using Odin?
Click to expand...
Click to collapse
No, i didn't. But, out of sudden since a few days the low memory bug seems gone However, i am not aware that i did something to affect this
how about you?
Olioaglio
Olioaglio said:
No, i didn't. But, out of sudden since a few days the low memory bug seems gone However, i am not aware that i did something to affect this
how about you?
Olioaglio
Click to expand...
Click to collapse
I have reflash the firmware because it was getting unbearable. It's been 3 days, no issues yet. Will keep you guys updated.
I just cleared the System Chache and my phone is working fine now.
Same issue here. After android 10 update it's laggy as hell. Android auto crashes randomly. Spotify stops working..
Olioaglio said:
No, i didn't. But, out of sudden since a few days the low memory bug seems gone However, i am not aware that i did something to affect this
how about you?
Olioaglio
Click to expand...
Click to collapse
No effect of reflashing. Same issue popup up after 4-5 days. I wonder if this is more like a hardware related issue then software?
No, i don't think so.
Got a new update, it made issue worse. Now, instead of 90 hours free of system killing spree I am getting 70 around-ish hours with good ram management. So my workaround for this is now to set auto restart in 3 days interval.
Olioaglio said:
No, i didn't. But, out of sudden since a few days the low memory bug seems gone However, i am not aware that i did something to affect this
how about you?
Olioaglio
Click to expand...
Click to collapse
Did you change your default keyboard?
icoolguy1995 said:
Did you change your default keyboard?
Click to expand...
Click to collapse
yeah, i use SwiftKey since ages.
Two updates passed (currently on G960FXXS9DTD7), so far so good (despite no mention in the changelog).
after each lock when i turn the screen on with double tap or power button screen is unresponsive for good 3 seconds. This started happening after the latest camera fix update. When if i use aod and use the fingerprint through the aod this doesnt happen. tried reboot and factory reset with fresh install (no backups) tried safe mode. Same thing happens.
S20 plus exynos.
Yup happening to me too (s20+ exynos). For me the time of unresponsiveness is around 1-2 seconds. Happened after the latest update.
Yes, have been facing the same issue since "ATCH" update.
Yeah has been driving me nuts. Same problem.
I'm surprised this isn't gaining more traction? Can't be the only few experiencing this!?
Glad to see it's not only my device. Waiting for fix.
I have similar situation
I'ne noticed the same after the last update.
Chris_c81 said:
Yeah has been driving me nuts. Same problem.
Click to expand...
Click to collapse
Seriously when it happens(which it does like 90% of the time i wake the screen) i feel like i'm using a cheap 100$ phone and not a 1000$+ flagship.
Chris_c81 said:
I'm surprised this isn't gaining more traction? Can't be the only few experiencing this!?
Click to expand...
Click to collapse
This. I'm afraid if it goes unnoticed by samsung we may have to face this issue for longer.
BTW any user here with Snapdragon that has this issue. Or is this exynos only ?
anfederin said:
I have similar situation
Click to expand...
Click to collapse
Mine is Exynos
sjandroiddeveloper said:
Seriously when it happens(which it does like 90% of the time i wake the screen) i feel like i'm using a cheap 100$ phone and not a 1000$+ flagship.
This. I'm afraid if it goes unnoticed by samsung we may have to face this issue for longer.
BTW any user here with Snapdragon that has this issue. Or is this exynos only ?
Click to expand...
Click to collapse
Is there any channel to communicate this bug to Samsung? Anyone know?
Chris_c81 said:
Is there any channel to communicate this bug to Samsung? Anyone know?
Click to expand...
Click to collapse
There is an app called samsung member where you can send error reports. I have already done it, its currently under review. I suggest everyone affected to do it.
sjandroiddeveloper said:
There is an app called samsung member where you can send error reports. I have already done it, its currently under review. I suggest everyone affected to do it.
Click to expand...
Click to collapse
Seems like a pertaining issue for Note 10 Users too. They found a trick and seems it works better now. Can you try this and let me know if it works better?
turn off the battery optimized for apps: com.samsung.android.biometric.
Go to Settings>Apps>Select "Special Access" from three dot menu>Optimise Battery Usage>select All from drop down menu>Search for "com.samsung.android.biometric"> Turn it off and Restart.
Click to expand...
Click to collapse
Report back if it works? I didn't check it yet because, I'm on root and didn't update it yet. (G985F/Exynos)
Original Thread
Credits to @wj_johnson
eaglerazor123 said:
Seems like a pertaining issue for Note 10 Users too. They found a trick and seems it works better now. Can you try this and let me know if it works better?
Report back if it works? I didn't check it yet because, I'm on root and didn't update it yet. (G985F/Exynos)
Original Thread
Credits to @wj_johnson
Click to expand...
Click to collapse
Did accordingly as above.
For a moment it felt like the issue is resolved!
But after checking several times I can confirm the issue still exists.
eaglerazor123 said:
Seems like a pertaining issue for Note 10 Users too. They found a trick and seems it works better now. Can you try this and let me know if it works better?
Report back if it works? I didn't check it yet because, I'm on root and didn't update it yet. (G985F/Exynos)
Original Thread
Credits to @wj_johnson
Click to expand...
Click to collapse
Unlock is now super faster. Issue is completely gone. Thanks [emoji4]
Sent from my SM-G986B using Tapatalk
verynuclear said:
Unlock is now super faster. Issue is completely gone. Thanks [emoji4]
Click to expand...
Click to collapse
While using the sidekey and turning off and on the screen and checking consecutively, the unresponsiveness persists in mine.
Virgo_Guy said:
While using the sidekey and turning off and on the screen and checking consecutively, the unresponsiveness persists in mine.
Click to expand...
Click to collapse
Have you restarted the phone? It didn't work until I restart mine.
Sent from my SM-G986B using Tapatalk
verynuclear said:
Have you restarted the phone? It didn't work until I restart mine.
Click to expand...
Click to collapse
Ofcourse I did. In fact restarted one more time since it didn't resolve after the first restart, post disabling the optimization.
eaglerazor123 said:
Seems like a pertaining issue for Note 10 Users too. They found a trick and seems it works better now. Can you try this and let me know if it works better?
Report back if it works? I didn't check it yet because, I'm on root and didn't update it yet. (G985F/Exynos)
Original Thread
Credits to @wj_johnson
Click to expand...
Click to collapse
I did this already and while it feels like fingerprint is faster, unfortunately this is a screen issue. You see if the screen is off and i put the finger in the correct spot it always scans my finger without any lag. The issue is occurs when -
a) I have unlocked the phone using above way, then the screen becomes unresponsive right after unlocking.
b) The screen is off and i either press the power button or double tap to wake, then the screen will be unresponsive and its during this time the fingerprint scanner doesn't scan (because the scanner doesn't know it needs to scan since the touch is unresponsive)
so TL;DR its not a FP scanner issue.
I am quiet sure Samsung is already addressing this issue for next update.