The stock android clock on top right of my screen wont update! Say i turn phone on at 1:20, it wont update to 1:21 or ever change unless i reboot then it will have the correct time for that ONE minute. I haven't recently installed or changed anything like apps or anything. BUT the clock on my lockscreen(widgetlocker) updates and works fine and is accurate. I went in date and time settings and its set to automatic, in the greyed out "set time" it shows a correct updated time, however this time isn't being shown up on the top right of my phone. I tried putting it in "manual" mode instead of the automatic mode and it still wont update..Ive reboot and pulled the battery several times to no avail. Im runnning stock rom and kernel, just rooted. As i said before i havent touched any new apps or settings in several days. This is really annoying as i cant tell what time it is while on and using my phone without going to the lockscreen and it just now began happening. Anyone have a fix or also have this issue??
I'm having the same problem today with my HTC Inspire 4g. Like you I have done nothing to my apps and its getting annoying. My phone has Cyanogenmod 7 flashed onto it.
i had same issue . made a phone call to make the phone get the auto time change then rebooted for good measure
Wow, mine was related to the time change, apparently! As soon as it reached 2am where i am it started working fine again!!(Time change was at 2am here)
Related
Starting a new thread for this. I have upgraded to 2.3.3 via Kies. I have also rooted my phone.
I noticed now the system bar clock freezes and fails to work properly, as well, my time seems to be an hour off. I am using the update time automatically (using network provided values). Ironically (Likely because it uses an internet time source) beautiful widgets does not share that problem.
Very odd - is anyone else seeing the same problem?
My temporary fix is shutting off automatic and setting it explicitly myself.
Seems to have resolved itself - I essentially went to manual which meant picking the right timezone. I let that settle things down, then went back to automatic and everything was fine again.
I did see someone else posted that they did that and eventually the OS got confused again later - but right now everything is in working order - correct time, and system clock is not frozen.
Hey guys,
I'm hoping somebody here might have an idea for where I can start to look for this problem, I have had the SGS3 for around a year now, I put CM10 on it initially (from memory), upgraded to CM10.1 when that was released via the nightly releases and I have been running those since.
Recently I updated from a Feb / early March release (cant recall specifically which one) to the next latest (mid to late March I believe) to move from 4.2.1 to 4.2.2. I believe a little after that ( if not that day) I began to very occasionally have small lock up problems with the phone. It would lag out for a short amount of time, or would just completely lock up on the screen its on for a while (if I leave it, it can be between 30 minutes to an hour before it becomes responsive again)
Often I would need to use it so I just end up having to hold the power button in to force a reboot to clear it.
Initially I thought "ok just a bug in a nightly, that's cool, it'll be patched out soon enough", a few days later a nightly came down that fixed a notification bar drop down loop problem I was getting but this other thing has stuck around, depending on how my phone feels its occurring a lot or a little each day, generally seconds / a minute after I start to use it.
I have since jumped around on a few more CM10.1 roms and I have even reverted to the 4.2.1 roms I was using ( I still have them on the phone so I know they are the right ones) to test if its that, but now they are encountering this problem as well.
The phone is completely clear now of user data, I have done a full data clear via CWM and even the original Google "welcome" setup section has locked up more than once in my attempts to set the initial configuration of the phone....
Any thoughts? CWM etc has never had a problem so while it seems to lean toward hardware i'm still thinking its software, maybe a CM10.1 release has updated something else in the phone that's now causing problems, something more firmware related etc?
EDIT: to give some examples, just before I readded my exchange details and started to sync contacts etc, I went into contacts, opened the menu and selected "Settings" to change the first name last name sorting and it just stopped on the settings button, settings was still lit up etc but it was not responsive.
Just now (about 30 minutes later) I have pressed to turn the screen on and its on the lockscreen. Great its back I think, i'll grab the baseband / kernel etc to put in here, I slide it to the unlock and bam, frozen on that now.
more info
I had a play this morning and activated the CPU overlay etc as well as strict mode.
The phone has just done it again in the play store, however the CPU overlay shows nothing out of the ordinary and there was no screen flash to indicate a long run causing a problem.
Interestingly the cursor in the search bar for google play is still blinking, so the phone is still "alive" however i cant control it via the touchscreen or the hardware buttons.
I am trying to dump the log via ADB now however its gotten as far as finding the phone and seems to have stopped (though maybe its still going, i'll see soon hopefully)
Anybody got any ideas? This is driving me crazy and i'm not sure where to go with it now, i guess back to stock is the next option then maybe a warranty claim if thats still possible....
Log collected
Either it was still collecting or it collected after the last event in the log but i've uploaded the log to pastebin here:
http://pastebin.com/Cc20CYZH
The main thing seems to be this:
Code:
W/SQLiteConnectionPool( 6385): Requests in progress:
W/SQLiteConnectionPool( 6385): execute started 646409ms ago - running, sql="COMMIT;"
W/SQLiteConnectionPool( 6385): The connection pool for database '/data/data/com.android.email/databases/EmailProvider.db' has been unable to grant a connection to thread 237 (AsyncTask #2) with flags 0x1 for 646.44104 seconds.
W/SQLiteConnectionPool( 6385): Connections: 1 active, 0 idle, 0 available.
And also this:
Code:
W/InputEventReceiver( 3327): Attempted to finish an input event but the input event receiver has already been disposed.
FYI - that bit at the bottom of the paste about the screen turning off with timeout, the screen has now turned off but i still cant turn it back on etc, soon enough it'll probably reboot (which seems to be what it ends up doing) then it'll be ok again until a problem occurs again.
I'm currently trying a new baseband as recommended here:
http://forum.xda-developers.com/showthread.php?t=2133401
Will post the results after a few days, fingers crossed.
Did you had the same problem on any other aosp or aokp based roms?
Or just try flashing the stock rom
BHARGAV33 said:
Did you had the same problem on any other aosp or aokp based roms?
Or just try flashing the stock rom
Click to expand...
Click to collapse
I actually never ended up changing back, i flashed the new baseband as above, ran the dumm file generator app a few times (letting it lock up as it went), flashed a new rom a few times as well and after all of that it seems to have worked out all the bad sectors.
Definitely seemed like I was a victim of the beginning of the SDS problem, all due to the fact i had flashed this almost immediately after receiving it and had never updated the baseband.
For those with lock up problems, go to http://forum.xda-developers.com/showthread.php?t=2133401 and follow that for installing the baseband, then do the dummy file generator etc, i'm back to a phone that works properly
PS - It took a few weeks after for it to find and remove all the problems, remember your actual ROM install could be written to bad sectors so i would definitely recommend after you run the dummy file generator a few times to update your ROM at least once, it was after 2-3 updates mine had completely settled down.
PPS - If the dummy file gen fills up your storage then crashes, just go to app info (drag from launcher is the easiest way to get here) and clear the data, that'll delete all the dummy data
PPPS - The dummy file gen can make your phone run terribly as it gets close to full, be patient, its not necessarily the lock up problem but even if it is you need to let it sort it out itself, restarting will make it worse not better.
OK, this is really weird - after getting the 4.2.2 update, my phone reboots itself every night, not 100% sure it's exactly the same time, but it's been while sitting in my pocket or on the table, not even in use. At first I assumed it was Zooper, which I had installed right after the update, but I disabled it yesterday and got the reboot again tonight.
I even checked my Tasker to make sure some auto-reboot profile hadn't installed itself!
Any hints about how to diagnose this? Do I have no choice but to remove apps one by one? Most of the apps I run are the same ones I run on my TF300 tablet which also has 4.2.2, so don't know if it could be an app.
Did it again tonight and it is the exact same time - 9:19pm It's also interesting is that this is about the time of day I did the update to 4.2.2 It's like some daily thing going on. It must be some new app applied by default by the update, I've disabled some of the obvious new apps.
Does anyone know if I do a factory reset will it go back to 4.1 (which worked fine for me), or will it stay at 4.1?
PhysicalEd said:
Did it again tonight and it is the exact same time - 9:19pm It's also interesting is that this is about the time of day I did the update to 4.2.2 It's like some daily thing going on. It must be some new app applied by default by the update, I've disabled some of the obvious new apps.
Does anyone know if I do a factory reset will it go back to 4.1 (which worked fine for me), or will it stay at 4.1?
Click to expand...
Click to collapse
the Factory reset will erase all ur Apps and will stay in 4.2.2 ......
Looks like this update has really screwed up my phone. After a couple of more nights of trying to disable more apps, and trying to catch the error with logcat (nothing that makes any sense in the log, no error or crashes preceding the reboot) I decided to factory reset.
It rebooted again tonight, about 24 hours after the factory reset.
Also, intermittently now the power button will not suspend the phone, though I can hold it and reboot, I don't know any other way to put it to sleep.
Looking at the log some more, the only thing that gives any hint is that there was Location Services activity before the crash. Googling around about my problem showed there was a bug in Location Services early in 4.2 but the claim was that it was fixed. I guess tomorrow night I'll try turning off Location Services as well.
PhysicalEd said:
Looks like this update has really screwed up my phone. After a couple of more nights of trying to disable more apps, and trying to catch the error with logcat (nothing that makes any sense in the log, no error or crashes preceding the reboot) I decided to factory reset.
It rebooted again tonight, about 24 hours after the factory reset.
Also, intermittently now the power button will not suspend the phone, though I can hold it and reboot, I don't know any other way to put it to sleep.
Looking at the log some more, the only thing that gives any hint is that there was Location Services activity before the crash. Googling around about my problem showed there was a bug in Location Services early in 4.2 but the claim was that it was fixed. I guess tomorrow night I'll try turning off Location Services as well.
Click to expand...
Click to collapse
The update may have screwed up somewhere in the middle, you could try to re-ruu your phone or unlock the bootloader and flash a custom rom, also the thing about the power button not putting the phone to sleep or doing anything than reboot on long press happened to me on each and every custom rom and I never did any OTA, got my phone, unlocked bootloader and flash away from sense, my hboot is still the one that it came with, but for me that thing happens really randomly, like once every 1 or 2 weeks, and when that happens for me the volume buttons stop working also till reboot, I was thinking I was the only one facing it so I kinda decided not to talk about that as I saw no one say anything about it, but I am also one of those for who the phone turns off exactly when my phone goes to 6% battery whatever I do, on whatever rom I am and even in the recovery, so I was thinking that maybe vodafone modified something on it, that's an other reason I didn't say anything about the buttons becoming unresponsive...
So what I would recommend is to re-ruu your phone or go to a custom rom (or if none solves anything the phone may have some kind of hard brick).
Just to help out anyone else who ever has this problem.
It was not location services.
I can see clearly in two logs an HTC process crashing. This seems to cause a cascade that leads to reboot.
I contacted HTC tech support, they suggested I boot up in a recovery mode and try to wipe data cache. They were surprised to find that attempting to do that caused a reboot.
So as Ranomez suggests above, they want me to re-do the update with the RUU when they release it, which they said would be "soon" last weekend.
On the other hand, my battery life after this update is fantastic, so I've decided I can live with this to not have to worry about recharging by mid-afternoon!
Here's a screenshot. I would have cropped it down but I don't have all day to figure out how to do that from a tablet. Look at the top, next to the signal meter: http://i.imgur.com/OLBVoEg.jpg
I recently spent a week in Japan, and this first appeared while I was there. I thought it had something to do with the network over there, but after coming back to the US, it still appears. Whether in Japan or the US, I've had a perfectly acceptable signal, no loss of GPS connectivity, really no loss of anything as far as I can tell. I've rebooted multiple times since it first appeared and it always remains, and never goes away. I simply cannot figure out what that symbol is telling me, and Google has been no help. I've tried turning off and back on everything that I thought might be responsible, with no changes.
I'm running a Nexus 5 on stock Android 5.0.1. I haven't updated to 5.1 yet because I'm rooted and need to get home to my computer to manually flash the update.
I figured out what it was. The no icon means that I've turned off interruptions altogether (I must have accidentally hit something). There's also a star icon which means you're set for priority interruptions only.
Hey everyone!
I picked up a Gear S about a week ago and until today, I've had no problems. I took the watch off charge this morning and everything was working as fine, used some apps etc, no issues. Then I checked my phone for updates and saw that the Gear Manager app had an update and I installed it. Since then, the screen on my Gear S has been constantly turning on and off. It will turn for about 9 seconds, then switch off and back on 2 seconds later. Turning the screen on manually works but everything is pretty much frozen. I can periodically get as far as the pedometer (because there's an icon for it on the home screen) or to the Apps menu but no further and then the screen will switch itself off.
I'm not sure whether an update to the Gear Manager app should affect the watch itself but I know that when I wiped my phone a few days ago and went to set up the Manager again, it factory reset the watch so I assume there is a direct connection between the software. I've tried disabling both Bluetooth and the remote connection to check if Gear Manager is causing the screen to behave strangely but it's still turning on and off. It's impossible to do a soft reset through the Gear S itself as the screen switches off before I can get to settings and I've tried doing a hard reset but nothing works.
I tried searching on Google for anyone having similar issues and the only thread I can find was posted on Android Central (yesterday I think) with a few people saying that they're having the same problem which makes me thing that the update to Gear Manager is the issue.
Edit: The only screen that doesn't seem to be affected is the PIN lock screen. Screen switches off there as normal and does not come back on.
Edit 2: I've never reset the Gear S before (and I only noticed the factory reset mentioned above after it was finished) but when I attempt to do a hard reset, the watch just reboots as normal without anything happening and all info / data is still there. I presume this really shouldn't be the case?
UPDATE: I'm an idiot / Samsung's instructions on how to do a hard reset are awful.
I decided to Google how to do a hard reset and discovered that when in the Recovery Menu, you need to hold down the Power button to choose an option (Samsung's instructions just tell you to press the Power button until you highlight what you want and I assumed it would automatically choose that after a few seconds because the phone would restart for me). Watch is now factory reset and so far the screen issue appears to be resolved. Another four hours of transferring music it is then.
@BOZG can you post a link to that thread?
I have the Same problem. Sometimes changing a clock face or installing/uninstalling a program seems to make it stop. I have yet to find a good consistent solution. Restarts etc. don't help. Hard reset will fix it but last time I just changed settings on and off and powered the phone on and off and eventually it stopped.
It seems related to when the phone is connected remotely over a cell network. I have the AT&T unlocked with a T-Mobile regular line, not the wearable line since I have a 5 for $100 business plan and the 5th line was not being used. Doubt that makes a difference though.
Followup:
Just now I had the watch off and charged to 100%. Powered up with phone off. Same issue. Watch face loads, the hands change to the current time, then it slides down the screen and looks like a reload because when it comes back up the time isn't correct. The hands reset to the right time. This happens a few times. I power the phone up. Bluetooth connects. I open the gear manager on the phone and it stops.
Will try to repost if that's repeatable. I hope they fix it because it burns quite a bit of battery when it happens. It gets warm so it's running the CPU a lot whatever it is.
allow to power down
BOZG said:
Hey everyone!
I picked up a Gear S about a week ago and until today, I've had no problems. I took the watch off charge this morning and everything was working as fine, used some apps etc, no issues. Then I checked my phone for updates and saw that the Gear Manager app had an update and I installed it. Since then, the screen on my Gear S has been constantly turning on and off. It will turn for about 9 seconds, then switch off and back on 2 seconds later. Turning the screen on manually works but everything is pretty much frozen. I can periodically get as far as the pedometer (because there's an icon for it on the home screen) or to the Apps menu but no further and then the screen will switch itself off.
I'm not sure whether an update to the Gear Manager app should affect the watch itself but I know that when I wiped my phone a few days ago and went to set up the Manager again, it factory reset the watch so I assume there is a direct connection between the software. I've tried disabling both Bluetooth and the remote connection to check if Gear Manager is causing the screen to behave strangely but it's still turning on and off. It's impossible to do a soft reset through the Gear S itself as the screen switches off before I can get to settings and I've tried doing a hard reset but nothing works.
I tried searching on Google for anyone having similar issues and the only thread I can find was posted on Android Central (yesterday I think) with a few people saying that they're having the same problem which makes me thing that the update to Gear Manager is the issue.
Edit: The only screen that doesn't seem to be affected is the PIN lock screen. Screen switches off there as normal and does not come back on.
Edit 2: I've never reset the Gear S before (and I only noticed the factory reset mentioned above after it was finished) but when I attempt to do a hard reset, the watch just reboots as normal without anything happening and all info / data is still there. I presume this really shouldn't be the case?
Click to expand...
Click to collapse
I left mine to use up all the battery,then when it switched off, i left for 2 days and when i switched back on... all fine again.
theroblog.com said:
@BOZG can you post a link to that thread?
I have the Same problem. Sometimes changing a clock face or installing/uninstalling a program seems to make it stop. I have yet to find a good consistent solution. Restarts etc. don't help. Hard reset will fix it but last time I just changed settings on and off and powered the phone on and off and eventually it stopped.
It seems related to when the phone is connected remotely over a cell network. I have the AT&T unlocked with a T-Mobile regular line, not the wearable line since I have a 5 for $100 business plan and the 5th line was not being used. Doubt that makes a difference though.
Followup:
Just now I had the watch off and charged to 100%. Powered up with phone off. Same issue. Watch face loads, the hands change to the current time, then it slides down the screen and looks like a reload because when it comes back up the time isn't correct. The hands reset to the right time. This happens a few times. I power the phone up. Bluetooth connects. I open the gear manager on the phone and it stops.
Will try to repost if that's repeatable. I hope they fix it because it burns quite a bit of battery when it happens. It gets warm so it's running the CPU a lot whatever it is.
Click to expand...
Click to collapse
samsung gear s screen on and off..looping
There you go. Not much to read there though as it's just me and OP. The problem re-emerged for me after a few days again so I was forced to do another hard reset to actually use the watch. I noticed it when I woke up in the morning and noticed that another update had been pushed to the Gear app. That's twice now that this has happened shortly or immediately after the Gear app was updated.
I haven't been able to uninstall an app / change clock face to see if it works as the watch is completely unusable when it happens to me. The Gear app registers that it's connected but it's impossible to change anything from there either and if I turn the watch off and back on again, the Gear app will no longer connect.
petethepete2000 said:
I left mine to use up all the battery,then when it switched off, i left for 2 days and when i switched back on... all fine again.
Click to expand...
Click to collapse
Not sure if I've actually tried letting the battery drain. I'll try that the next time it happens (if it happens).
I had the same problem after the update, a reboot didn't solve the problem. Eventually the battery drained. After a recharge most is fine but I never know which watch face will suddenly appear.
Same issue again. Didn't see the Gear app updating but there was an update released the day before. Going to switch off auto-updates and see if it definitely the problem. Just seems too coincidental that this problem starts right after an update is released for the Gear App.
petethepete2000 said:
I left mine to use up all the battery,then when it switched off, i left for 2 days and when i switched back on... all fine again.
Click to expand...
Click to collapse
Started doing it again yesterday so let the battery die and charged it fully and it didn't help. Left it on the box overnight and brought it to a Samsung Service Centre this morning and of course it was working again when I took it out of the box! Left it with them anyway so I'll see what happens.
I've had my Gear S a few weeks and it has also started doing this, I will give some of the suggestions here a go.....
EDIT: So opening the Gear Manager App once Bluetooth was connected brought my Gear S back to life. Phew!
It's only entered this state after I turned it off at night and then turned it back on in the morning - so it had been off roughly 8 hours. Upon turning it on the screen would cycle from the right time and notification numbers and the wrong time and wrong notification numbers too off again.
@ BOZG - Just wondering if you got your S back yet and if so, were they able to tell you what was causing this on/off problem. Mine just started doing it yesterday.
Also, how did you find the "Samsung Service Centre"?
holding the screen seems to cause it...
Had to send mine to Samsung for a new charging cradle and they updated the software to latest, when i got it back it seemed fine. Then i was messing about with it and was holding the screen to my chest for a while and that seemed to cause it to happen. It seems to be the screens gets too much activation and it flips out. I think this is what started the problem last time it happened.1
Switching to power saving mode seems to fix it for me... have to wait until it gets low on battery and when the low bat warning comes on, switch then... leave for a bit then switch back to normal.
I called Samsung Thursday and they sent me a UPS label and told me to send the watch, charging cradle and AC charging cord back in for service. She told me it takes about 7-14 days. We shall see.
Happy to have found this. </rant>I'm starting to get enough of this Samsung stuff. I had the note 2 and now I have the note 4 and gear S. That is mote then 1000 euro of equipment. And today when I tried the restore to fix this, both the phone and the watch rebooted. Crazy that they can not build good software and hardware for this price. </rant>
To me it seems that is freezes somehow when this happens. It kept jumping back to 22:10 time and changed to the watch-face and settings keep rolling back. It seems to happen to me, when the watch is off for some hours. The samsung way... no update to fix this.
solved for me
hi first of all sorry if i do any mistakes because English is not my language
i had similar problem and i found the solution at least in my case . THE PROBLEM IS NOT WITH THE GEAR S
all was ok using 4.4.2 kitkat on my note 3 before few months i upgrade with lollipop 5 official from sammobile via odin
from that moment the problems begin with the reconnection of the gear with the note
long time to connect and no auto reconnection only manual by turning off-on the bluetooth
i was boring to do format to the note3 so i left it as it
few weeks ago probably of gear manager update the gear start freezing and the screen turning on and off
first i do a factory reset and the gear was ok for a while but after it do the same but the next time the screen was not ok the colors was different so i send to service in Athens
the service in Athens is very fast and very helpful , is one of the reasons that i will difficult go with other manufacture , so they return me the gear saying that they change the motherboard and now there is new imei
but the gear that they send me was brand new except the band and the box. BUT after some time the same problem ..... i call them and they tell me to send it back so i send it and i receive it again but this time the say that the watch is ok
GUESS NOW .... i turn it on and after a while of the connection with my note AGAIN the same problem the screen on and off and freezing plus was overheat underneath
i was ready to call them and to say few words but they was closed ..... then i search the net and i found this post and i thing probably is not the gear the problem ,no hardware problem, i decide to do a test
i download the last working rom to my phone 4.4.2 and magically the problem disappears .... but now there is a software update on my phone lollipop 5 so i do the update and i was ready if the phone cause again the same problem
to return and stay with 4.4.2 But now all is ok the problem solved .... now is more of 24h and all are ok
i hope this will work for you also
Same problem
I have the same issue exactly - Note 4 with latest lollipop upgrade - it is very frustrating......I don't particularly want to have to move back an OS just to use the watch !
JALUK said:
I have the same issue exactly - Note 4 with latest lollipop upgrade - it is very frustrating......I don't particularly want to have to move back an OS just to use the watch !
Click to expand...
Click to collapse
Ok but doing a downgrade and all working ok you can do update again.... i am not with 4.4.2 i went to the latest 5.0 for me now and all are ok.
Maybe something was wrong with the update procedure.
UPDATE
the touch function of the 2nd gear stop working so i send it back and they send me new device
for a few days all was ok . But today when i restart the phone while the gear was disconnected the problem with screen turning on repeatedly appears again .
for sure is not problem of the gear , this is the 3rd device in my hands, something is wrong with the gear manager software .
i have also reconnection problems .... if the phone is far away and they lost Bluetooth connection the most of the times i must reconnect manually , the gear say disconnected but the note think is still connected
I wonder has anyone tried to reset the watch as a stand alone device and see if the problem happens? I know you might lose a lot of the blue tooth functionality but I think I will test it and see if the problem still happens.