Need your help cause this is driving me nuts
Opening a new thread cause previous one subject may have been off putting
I got the x play for my wife which is running stock marshmallow and is rooted
We noticed once in a while her alarm wouldn't go off in the morning
I tried various clock apps and same result
We noticed that when this happens her phone is ususally plugged in so daydream clock is on and clock seems to be late a few hours as if it's not updating
I tried a few daydream clocks and noticed the same trend
Not sure but it seems when the phone is in deep sleep mode and sometimes it just does this
I checked the app battery saving features and turned them off for the clock and daydream app and same thing
issues are occurring with stock clock application as well stock Daydream options as well as 3rd party
Is this a known bug? Any ideas on how to fix this?
Thanks
Related
Anyone having issues with (system) clock after updating Xperia Play to 2.3.3?
I've missed couple of morning wake-up's since updating to latest firmware. When checking the handset , there's no any indication of error, but the "generic" clock on notification bar has frozen. Also, of course, the alarm does not occur.
I think this can be relate to flight mode which I use over night. When I disable the flight mode, the clock updates correctly to current time..
Otherwise I very much like this toy.. Playing Rainbox Six and Nova 2 and all those emulators
I'm on 2.3.2, and I'm having issues with the clock as well - the date and time simply do not update properly at random times.
And this may not be an exclusive problem to the Play, but when the time/date get all out of wack, it completely screws up your timeline of sms/mms messages.
Very strange problem to have, not to mention it makes me paranoid the phone is completely unreliable.
I used to have issues with the clock, it seemed to fail the updates via the service and gave me one hour less than the actual time (light saving thing if that applies in you countries)...I´m on 2.3.2
What I did was uncheck the automatic network updates...problem solved...I´ll have to adjust the time manually twice a year but I can live with that. HTH
I can confirm this on my UK sim free 2.3.3
Do you guys use task killers
Because it kills the clock at times stops it completly
Sent from my R800i using XDA Premium App
Yep, same issues.
No task killers.
No task killers here, unrooted unmodded etc...
Stock phone.
No task killers, completely stock R800a.
Probably problem in baseband with automatic clock updating, as mentioned by Bluero. X10 had same issue on one baseband version, where auto clock didn't work.
Please, all of you having issue, report here, and note that you have clock issue.
Read first post for reporting instructions.
I have a moto pure running 6.0. Recently I ran into an issue with the google search bar crashing every time i tried a search. I went an uninstalled the google app, rebooted and reinstalled. This resolved the crash with google search but started another issue.
I was having the google app being my number 2 battery user with high CPU pretty much spot on matching the screen time - the device was warm and battery life reduced by 3x from my normal. I installed a CPU monitoring app and noticed that the CPU usage was about 15% continuous for the google search bar googleqicksearchbox:search and googlequicksearchbox together take about 15% and don't stop.
I've tried:
uninstalling the google app, reboot, reinstall
cleared caches for the google app
cleared caches for the google now launcher
uninstalled and reinstalled the google now launcher
Nothing resolved the issue until i did this:
If i remove the google app 4x3 widget the CPU returns to normal - battery returns to normal.
So, it appears to be related to the widget. Does anyone have any other ideas on how to resolve this so i can use the widget? I figure I might be stuck with having to factory reset to resolve.
Google App update constantly listens to audio.
You see it too?
There seems to have been an update on 2/19/16 that broke it, and my own device seems to have picked up the update on 2/26. I noticed that the battery was draining very quickly for the past couple of days, even when idle with the screen off, though it wasn't warm or anything as is usually the case when something goes awry. GSam Battery Stats showed the usual mess of inexplicable Googleness chomping at things, using sensors, and being Googley, but nothing grossly out of the ordinary.
And with the screen on, doing the usual non-intensive things I do, I could watch the battery percentage drop precipitously: 4 percent in a few minutes.
I was using Google Now Launcher, and figured that might be related. I switched to a different launcher, no change. Rebooted for good measure and to make sure Google Now Launcher was definitely not running, no change.
Then I froze the Google App in TiBackup, and the problem went away.
I honed into it being Google App by using top. In a terminal: top -t -b 16. Screenshot: i.imgur.com/19bVXsG.png (no link because I'm too n00b here).
Of note in the screenshot is PID 14272. It's got a lot of threads going, which is not unexpected.
What was unexpected is that some of them were listening to audio. The thread names are abbreviated by top, but one of the threads (14582) is MicrophoneReade which occasionally showed some CPU usage. Another constantly-active thread (14581) is MicroRecognitio, a name which implies TTS. And PID 787, /system/bin/mediaserver, was pretty insistent on using CPU as well with its thread (14584) called AudioIn_2D, verifying that audio was being recorded.
All of this disappeared from top when I froze Google App.
To be clear, I don't use the "OK Google" always-listening function because it drains the battery quickly on my device, but I did have "OK Google" enabled on the home screen. However that shouldn't be happening with another launcher that has no (zero) widgets enabled at all.
So it shouldn't have been listening at all, but it was listening all the time. And this was apparently computationally expensive, and thus hungry for battery.
Samsung Galaxy S5, VZW, running MOAR and Xposed.
My particular issue seems to be related to the 4x3 google now widget. I can use the Google now launcher just fine, till I add that widget then a things go to hell... I really like that widget...
This same thing happened to me on my M9 starting on 2/26. It was getting seriously hot (110-120F) all the time and battery was draining at 33% an hour idle. Navigation was also very choppy and slow. Verizon actually sent me a replacement phone due to the constant over heating and factory resets. Once i got my new one I didn't restore from backup and loaded apps one by one. Sure enough as soon as the NOW widget was added, the phone slowed down and heated up.
With the widget off now for 2 days i am getting my usual 12 hours battery and the temp hasn't gone over 100 F.
Big news from my perspective. Last night I got a Google app update. Today the widget no longer slows down the phone /no more hot phone. Seems like the update fixed it for me... Time will tell.
That's why I don't use that crap! lol. Spies I tell you, spies.
Big news from my perspective. Last night I got a Google app update. Today the widget no longer slows down the phone /no more hot phone. Seems like the update fixed it for me... Time will tell.
Need your help cause this is driving me nuts
I got the x play for my wife which is running stock marshmallow and is rooted
We noticed once in a while her alarm wouldn't go off in the morning
I tried various clock apps and same result
We noticed that when this happenes her daydream clock seems to be late a few hours as if it's not updating
I tried a few daydream clocks and noticed the same trend
Seems when the phone is in deep sleep mode sometimes it just does this
I checked the app battery saving features and turned them off for the clock and daydream app and same thinf
Any ideas on how to fix this?
Thanks
Forgot to mention that the issues are occurring with stock clock application as well stock Daydream options as well as 3rd party
Hey all,
So I've had my S8 since launch and I've enjoyed it but I have an issue that I've been trying to pinpoint the cause of for a few weeks now. At a high level, if I reboot the phone in the morning, I can use it all day as I wish and it works perfectly, no slowdown anywhere and good battery life. I plug the phone in at night when I go to sleep and when I wake up I start using it again. Either right after I wake up or over the course of a few hours the phone begins to slow down with things like notification shade/app switcher crawling until I either a) reboot or b) change display resolution. Doing either of these "fixes" it until the next night and then again when I wake up I have the same issues.
I've been trying to figure out what's causing this. I've tried disabling features, uninstalling apps, etc.
One thing I have found is that when I'm having this problem if I force close 'System UI' in App Manager (this is just restarting that process since you can't kill it really) the smoothness comes back but it doesn't last as long as when I either reboot or change resolution.
My theory is that something is conflicting with the Android UI and over time it's causing it to slow down. Rebooting or changing display resolution restarts the Android UI so essentially same thing.
My first question is has anyone seen this behavior where the notification shade/app switcher (native UI not apps) slow down? I know there's at least some people on Reddit with same issue. If you have this issue does FC'ing System UI 'fix' it for you temporarily?
I'm trying to figure out what is running on my phone while I'm sleeping at night which is obviously causing this. Any ideas would be helpful. Oh also when I wake up and I go into app switcher it only shows like 3 cards where before I go to bed it would be like 10+ so something is killing apps at night too. I turned off Google backup for today and will reboot before tonight to see if maybe that's it.
Appreciate your help.
Thanks.
I've had my S8+ since the launch weekend on ATT, always connected to my Gear S3, and connected to my Misfit Ray. I've not noticed any slowdown of the UI. My AOD clock is slow to show the hands if the screen is off when I use the numerical clock AOD, but nothing else observed.
I would guess you've installed (or haven't uninstalled/disabled) some apps that are using a lot of background processes. I removed/disabled the few ATT apps on the device except Call Protect, and I don't use Gmail (resource hog). I actually use very few Google apps, they're just not very well coded, it seems (maybe a "goof off" day every week isn't such a great policy?)
In settings, go to Device maintenance, click on battery, and see if anything strange is going on there under App power monitor.
I've NEVER liked Samsung phones, and I've NEVER been interested in owning one, but I saw the Galaxy Gear S3 and fell in love, and truthfully, I bought the phone as an accessory to the watch, so I'm not an apologist for any shortcomings.
Instead of restarting, go to settings/device maintenance, what's the percentage here? go to optimize, does it help? which apps use the battery most? How much RAM is available. If nothing shows up, you probably would need something like wakelock detector (it needs root) to trace apps usage, especially at night. Also you could try to force stop other apps and see which one is interfering? For example phone is slow, force stop first 10 apps, if not fixed force stop next 10, if fixed, next time force stop one at the time from that batch of tens.
Mines just started doing this the other day. I think I have an idea if the problem, I'm just trying to find proof at this point. I recently downloaded this all to let me see the upload/download speeds if my network in the notification bar. It lets you set the refresh rate, to which I set it to 2 seconds, which I knew regardless would tax my system, I just didn't expect my ui to slow to a crawl.
Delete any Bixby remapping app as well, known to cause many issues including unpredictable lag.
Everyday on my battery usage, 2nd biggest user is the system clock, it's been kept awake for over 7 hours, I have no alarms set, I don't even have the clock widget.
Anyone ever seen this? Is it normal, or am I missing something?
markdexter said:
Everyday on my battery usage, 2nd biggest user is the system clock, it's been kept awake for over 7 hours, I have no alarms set, I don't even have the clock widget.
Anyone ever seen this? Is it normal, or am I missing something?
Click to expand...
Click to collapse
I had the same issue. As far as I know, it's a bug in Google Clock. If I recall correctly, there was an Android Police article about it on G+. Haven't noticed it as of lately though so I assumed it was fixed and another version. Make sure it's updated in the Play Store. If it is and you're still having the issue, I just made sure to force close the app every morning after my alarm went off. Issue was gone.