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.
Related
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)
Hello all,
I installed CM7 on my vibrant a few weeks ago and have really been enjoying it.
I ran in to some trouble yesterday and my phone will not complete booting.
I ran adb logcat and have attached my logs. The SQLite exceptions related to settings keep printing in a loop.
I am able to boot in to recovery, so I'm sure I can recover the phone by reinstalling CM7. I would very much prefer not to do this, because I had just now got things setup how I want. Unfortunately, I had not setup Titatnium backup on a schedule, so my latest backup is prior to my CM7 update. Reinstalling would be pretty painful for me at this point.
This is what happend to my phone prior to getting in to this state. Not sure if any of this is related:
I installed a bunch of new apps (google $0.10 promo) including Beutiful widgets
At some point Go Launcher became unresponsive and I had to force close
Go launcher restarted but lost my config/layout, I tried restoring an old config but this was not waht I wanted. So I reset to default
I added a Wifi toggle widget from Beutiful widget to my home screen
Turned wifi off with it,
Decided that it was redundant since I have CM7's widget in the notficiations tray.
Uinstalled the wifi widget
Tried to turn wifi back on with notification tray widget
Wifi would not turn on, went to settings and tried it there and was still not turning back on
Gave up fighting wifi, tried a reboot
Got stuck on CM7's boot animation.
I am hoping to recover my phone's state and would appreciate any help with the following:
1. Any ideas as to what could cause this?
2. Is it possible just to reset only the system settings? It looks like the sqlite db related to settings (if there is one) has got corrupted.
3. Is this the best forum for this post?
Edit: fixed a typo.
Mods, can you verify my account please?
Hey guys,
I've been reading the forums for the past few weeks and have been enjoying the discussions here, yet not having too much to add (constructively). Apologies if there is a thread on this already. I have done a couple of quick searches but nothing came up that seemed to fit the bill.
I got in this evening and took my S2 out of my pocket to find something wrong with it. I'll explain below. First of all software details:
Baseband Version:
I9100XXKI4 (up to date as far as Kies is concerned - stock ROM)
Apologies in advance if I'm missing any important information (I'm trying to sift through and try pick what I think are the relevant points).
Issue:
I felt my phone vibrate twice and took it out of my pocket (expecting a text). Instead I found the "Desk Clock" part of the stock "Clock" app flashing on and off the screen. When I tried to close it I came to the lock screen, unlocked it and then the desk clock opened again. It reloaded every time I attempted to close it. I tried to end it using the task manager but it didn't show up on the active applications list. I restarted the phone.
When I restarted it didn't seem to load properly with app icons all over the screen and the home screen numbers in the middle of the screen. I have a screenshot which I'll try to upload later. I restarted again.
This solved the arrangement issue but didn't stop the desk clock popping up. I also became aware of another problem. The battery was showing 12% (down from ~35% it was showing before - when checking battery usage). I plugged it into my laptop via the USB lead I have (which I had used earlier in the day to charge it). It didn't recognise immediately that it was charging. I swapped to AC, it started charging.
It then started showing "driving mode activated" and asked me whether I wanted to complete the task with UlysseSpeedometer or Voice Talk. I didn't press anything. When I pressed back it then asked me again a few seconds later. I restarted the phone again.
This time it showed 37% battery! I switched to the USB charger to try to back the phone up. It had trouble connecting but did eventually. I left it perfectly still as it tried to back up but failed twice partway through doing so.
Recent changes:
Only real changes are installing Super Compass today, which when (re)reading reviews didn't seem suspicious. I have uninstalled just in case.
Additional information:
I updated to 2.3.5 through Kies about a month ago (the first time it was available for me after checking for updates every few weeks - I have friends with the same phone on 2.3.4 and 2.3.3). Since then the countdown timer on the clock app sometimes shows the preprogrammed 1 minute countdown even when I have a timer running. The timer alarm still goes off at about the right time (haven't tested it properly) though.
In addition to this I have customised the apps that stay at the bottom (can't think of the terminology at this time of night) by swapping the Phone for GMail. Every time I restart the phone the GMail app is removed but the Phone app doesn't replace it. On a similar note I keep getting asked to choose my default PDF reader after ticking the box to select it multiple times.
My thoughts:
It appears to be a software issue to me. It's late now but tomorrow I plan to attempt to back up again (perhaps just by copying all the files on the phone using Windows Explorer if need be) and attempting to reinstall the firmware through Kies. If that doesn't work I'll do a factory reboot. After that I'll contact my carrier (O2 UK) to get some support.
Question:
I was wondering whether anyone has any insight, has experienced similar problems, or has any other advice regarding this?
Thanks in advance for any help you can offer
Regards
T
It sounds like it might actually be a hardware fault - basically what's happening is that something on the phone (whether hardware or software related) is triggering it to think it's being connected to a dock. The desk clock is what pops up as soon as you put the phone in a Samsung desktop dock and car mode similarly pops up when you use the vehicle dock, so there may be something funny going on with your phone's connecter that leads it to think these events are happening. (The weirdly arranged home screens tie in to this, as they can be a slightly buggy result of unplugging the phone from the one of the docks while in landscape mode - the launcher tries to load the home screens in landscape and just makes a mess.)
As a bit of a bodge-job fix you can install an app from the market called 'NoDock' if you're rooted, as this stops the phone ever being triggered in to dock mode, but to be honest id say your best bet is to speak to O2 or a Samsung service centre about getting it fixed or replaced!
Anyway, I hope this helps and you manage to get it sorted - I don't know what I'd do without my Galaxy S2!
Sent from my GT-I9100 using xda premium
Hello, quite a late night here as well but I'll try to give you my insight (and then slam myself to the bed )
It seems that the widget in your device went corrupt and perhaps then some more... I recommend backing up your data and then doing a factory reset and eventually re-flashing thru kies (come to think of it, i don't really know if KIES supports full-wipe reflash ). Also, for customizing the quicklaunch bar, use GO Launcher EX (free from the market) - its customizability far surpasses that one of the TouchWiz
If a factory reset doesn't help, you can help yourself by reflashing the original firmware by yourself via ODIN (but be sure to read tutorials and know your firmware first!), you'll find all the needed information here
Hope you get your problem resolved
TUnit said:
Hey guys,
I've been reading the forums for the past few weeks and have been enjoying the discussions here, yet not having too much to add (constructively). Apologies if there is a thread on this already. I have done a couple of quick searches but nothing came up that seemed to fit the bill.
ITS a question = Q&A so well done that man for posting in the right section .
I got in this evening and took my S2 out of my pocket to find something wrong with it. I'll explain below. First of all software details:
Baseband Version:
I9100XXKI4 (up to date as far as Kies is concerned - stock ROM)
Thats the modem not the firmware .
Issue:
When I restarted it didn't seem to load properly with app icons all over the screen and the home screen numbers in the middle of the screen. I have a screenshot which I'll try to upload later. I restarted again.
My thoughts:
It appears to be a software issue to me. It's late now but tomorrow I plan to attempt to back up again (perhaps just by copying all the files on the phone using Windows Explorer if need be) and attempting to reinstall the firmware through Kies. If that doesn't work I'll do a factory reboot. After that I'll contact my carrier (O2 UK) to get some support.
Rule one is backup data and factory reset the phone then test .
Follow that with a Kies upgrade if available .
jje
Click to expand...
Click to collapse
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.
I honestly don't know where to post this so I'm going to post it under "General" in hopes that someone far smarter than me can help (!)!...
ScreenShot:
https://drive.google.com/open?id=0Bx8wdr_asZMFZXE1dGFWSnZ2NmM
I've had the following issue for the past 30 days (at first I thought it was some glitch that caused the UI to crash when phoning-home to Cyanogenmod for updates). It SEEMS to have happened right when I first started screwing around with TitaniumBU... that may be a total coincidence, also...
The phone works just fine but will suddenly start showing things in Landscape instead of Portrait (and vise-versa). After I reboot the phone boots to a black screen with just the status bar at the top (showing the time, wifi, etc...) with absolutely NOTHING ELSE except for what appears to be a "back" arrow at the bottom of the screen (that does nothing when pressed).
WTH?! Please. Because I've tried everything (to include wiping internal and ext-SD). :crying: I have, of course, searched other forums but "Android UI Crashing" returns a ton of unrelated results...
:cyclops:I'm still having this issue so I'm gonna bump this thread... Any help is much-appreciated!:cyclops:
I'd wipe the whole internal storage (including ROM) and reinstall the ROM.
Dude - WAY ahead of ya - already did. To the extent that I accidentally soft-bricked the stupid phone!
We all know, as engineers and troubleshooters, that the first step to solving a problem is duplicating it.... and I cannot seem to consistently duplicate the problem! And the crux of it is that this started at the end of December when I was bored around the holidays and playing with my phone (making several different changes).
Obviously I'm not restoring anything from a previous backup... I've even blown away my backed-up App settings in my google account... Formatted Internal and External... Installed latest OS and GApps...
Gun to my head; if I had to guess I'd say that it has something to do with the "System Profiles" feature... I started using it to disable my Lock Screen whenever it detected my home wifi, and to return to the System Default (with the Lock Screen enabled) whenever it no longer detected my home wifi... Because I swear that the crashed-phone looks the same as the screen where you enter your PIN with the addition of the status bar at the top...
The issue has to do with System Profiles to use wifi-detection for toggling the lock screen. Not sure what it is about this that causes the issue, but that was the cause.