I recently bought a brand new DINC2, and almost every night while on the charger the phone shuts off on its own. Whats really annoying is that I use this phone for my alarm clock and have been late to work twice already. Dont want to get fired over this phone! Has anyone else had the same problem with this phone? What did you do to fix it?
Bohemus said:
I recently bought a brand new DINC2, and almost every night while on the charger the phone shuts off on its own. Whats really annoying is that I use this phone for my alarm clock and have been late to work twice already. Dont want to get fired over this phone! Has anyone else had the same problem with this phone? What did you do to fix it?
Click to expand...
Click to collapse
First I would recommend you buy an alarm clock till its fixed...
Are you rooted? What Rom
Are you stock? What version? Any otas?
Tried a factory reset?
This is all very important info I need to know
sent from my phone
HTC is suppose to release another OTA bug fix. I saw some info over at Droid-Life. HTC knows the alarm is broken. If you are unrooted most of us had to do a factory reset after the gingerbread ota update.
Completely stock, on froyo - unrooted. No OTA as of yet. Have not tried a factory reset at this point.
knipp21 said:
First I would recommend you buy an alarm clock till its fixed...
Are you rooted? What Rom
Are you stock? What version? Any otas?
Tried a factory reset?
This is all very important info I need to know
sent from my phone
Click to expand...
Click to collapse
I took a look at droid life, seems like the OTA is a minor update for server connections. I'm still on Froyo, so will apply the GB update first and factory reset after the update to see if that solves the problem.
stelv said:
HTC is suppose to release another OTA bug fix. I saw some info over at Droid-Life. HTC knows the alarm is broken. If you are unrooted most of us had to do a factory reset after the gingerbread ota update.
Click to expand...
Click to collapse
Just got the update. Didn't fix alarm clock.
sent from my inc2
Related
After the ICS update on my non-rooted phone, the phone seems to be freezing
up and becoming unresponsive. After a while it looks like the radio "resets", all
the icons disappear in the top bar (signal, wifi, data) and it shows no service.
Then slowly one by one they all come back and I can use the phone again.
Sometimes I receive the "System is not responding" dialog box, but not always.
There is not one particular program it is doing this in, it can be something as
simple as pulling down the notification bar that will cause the freeze.
Any suggestions are appreciated, I couldn't find anyone else with the same issue.
Thanks.
Try:
Turn off phone
Take out SIM
Put SIM back
Turn on
I've had my phone act weird with respect to signal, wifi and data when this was the issue. Worth a shot, at the very least.
Digital_Buddha said:
Try:
Turn off phone
Take out SIM
Put SIM back
Turn on
I've had my phone act weird with respect to signal, wifi and data when this was the issue. Worth a shot, at the very least.
Click to expand...
Click to collapse
Thank you for the response.
Tried this and had the system is unresponsive issue right on reboot. If I do a
factory reset, does it reset to the current firmware or what was originally on the
phone (probably a really stupid question). I wonder if some other program isn't
ICS compatible and is doing something in the background. Doesn't look like
anyone else is having this same issue.
jdscully said:
Thank you for the response.
Tried this and had the system is unresponsive issue right on reboot. If I do a
factory reset, does it reset to the current firmware or what was originally on the
phone (probably a really stupid question). I wonder if some other program isn't
ICS compatible and is doing something in the background. Doesn't look like
anyone else is having this same issue.
Click to expand...
Click to collapse
If you do a factory reset and it was the standard Kies legit update from Tmo, it won't downgrade your phone - will just re-install a fresh copy of your ICS. Did you do a restore of apps from your last version (gb?) with data? That could cause problems I would think..
VoiD_Dweller said:
If you do a factory reset and it was the standard Kies legit update from Tmo, it won't downgrade your phone - will just re-install a fresh copy of your ICS. Did you do a restore of apps from your last version (gb?) with data? That could cause problems I would think..
Click to expand...
Click to collapse
Yes I did the legit update on Kies, standard stock phone un-rooted.
Do I need to backup pictures before the reset, its been a while since
I had to do this.
At this point, I think its worth a try to wipe it clean and clear out all the
data.
jdscully said:
Yes I did the legit update on Kies, standard stock phone un-rooted.
Do I need to backup pictures before the reset, its been a while since
I had to do this.
At this point, I think its worth a try to wipe it clean and clear out all the
data.
Click to expand...
Click to collapse
wipe the dalvik cache and cache then reboot
I did a factory reset and that solved the issue.
Thanks for all the assistance.
I've done a factory reset and wiped the cache more than once already and i still get a force close or unresponsive, enough that its really irritating me now. Any advice? And also, when texting, the typing responds very slow.
Sent from my SGH-T989 using XDA
itsdamage said:
I've done a factory reset and wiped the cache more than once already and i still get a force close or unresponsive, enough that its really irritating me now. Any advice? And also, when texting, the typing responds very slow.
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
Are you letting it sit for like 10 minutes during first boot after factory reset then reboot again before setting up. Its likely that some scripts are running from the initial installation and you need to let it rot until its done..
I did exactly that, thanks for the advice. Hoping that may fix the problem. I wiped the cache and factory reset, then let the phone sit for a good while before going through the play store and re-installing everything.
This issue just resurfaced again. The last 2 days I am getting the freezing, radio reboot and android process not responding.
No one else having this issue?
I think I'm in the same boat. I was stock GB, and just did the mini OTA update (which was great). A few days later ICS became available via Kies from T-Mobile, and I "upgraded".
Since the upgrade my phone is laggy, screen is significantly less responsive and also my battery life is less than before.
I have NOT done a factory reset of my phone yes (plan on doing that today), but even with that I have read that performance does not improve.
Ideally, I would love to return back to the stock tmobile gb firmware. However, even after literally 2 hours of reading I can't find the "how-to" and files I need.
I would appreciate any assistance.
t989 chip lags
ive notice this happen on my tmobile galaxy s2. i think it has to do with the Qualcomm chip on tmobiles stock roms.
When i had sprint i bought my girlfriend a galaxy s2 on the sprint network which runs the samsung exynos chip. She never complained about any lag or freezing whatsoever. I then left sprint because of their garbage network and joined tmobile.
bought 2 galaxy s2s and i noticed the lag almost immediately. The phone has random lag spikes as well as freezing and force closes. It had it on stock gingerbread and it has it on stock ICS too.
My girlfriend complains about freezing all the time so i decided to root her phone too. Right now im testing DarkSides v7 rom and if its pretty good in performance i will flash her phone with it too. So far it has been pretty snappy and everything works.
jdscully said:
This issue just resurfaced again. The last 2 days I am getting the freezing, radio reboot and android process not responding.
No one else having this issue?
Click to expand...
Click to collapse
Yes i have the exact same problem...and the clock goes off too...if i don't reboot then this will keep happening...if you go into settings then development settings and tick off only let 4 process run in the background it should stop...try it and let me know
Sent from my SGH-T989 using xda premium
tonydetroit said:
I think I'm in the same boat. I was stock GB, and just did the mini OTA update (which was great). A few days later ICS became available via Kies from T-Mobile, and I "upgraded".
Since the upgrade my phone is laggy, screen is significantly less responsive and also my battery life is less than before.
I have NOT done a factory reset of my phone yes (plan on doing that today), but even with that I have read that performance does not improve.
Ideally, I would love to return back to the stock tmobile gb firmware. However, even after literally 2 hours of reading I can't find the "how-to" and files I need.
I would appreciate any assistance.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1668502
follow that first post. i went through exactly the same problems and found this guide and am now happy again and running stock GB on my Galaxy S2.
Because you are on stock ics (im guessing you are..), you can just follow that guide and flash the UVLDE update.
Yes clock resets to standard standard time.. I already did a factory reset and worked done for a couple weeks. My wife has same phone and she is getting the freeze ups now.
jdscully said:
Yes clock resets to standard standard time.. I already did a factory reset and worked done for a couple weeks. My wife has same phone and she is getting the freeze ups now.
Click to expand...
Click to collapse
Yeah really sux...it's random..I'm using a custom kernel and still having that problem....
Sent from my SGH-T989 using xda premium
Yup here too. Almost reminds me of XP. Really ticking me off & it never happened on gingerbread. Rooted now & before I'm on rogers 4.0.4. wondering if there's going to be fix? Haven't seen if Google / rogers /at&t have commented?
Sent from, The Eclectic Chair.
I'm getting the freezes as well even after doing a factory reset.
It sucks, I'm waiting for cyanogen to release a stable release and then I'm switching.
djtheraven said:
Yes i have the exact same problem...and the clock goes off too...if i don't reboot then this will keep happening...if you go into settings then development settings and tick off only let 4 process run in the background it should stop...try it and let me know
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Thanks for the suggestion, I'll give it a try. But it really shouldn't be necessary on a phone that's got more going for it than the stock nexus that 1st came out with ics.
There's something else going on.
Sent from, The Eclectic Chair.
Anyone else having sleep of death issues recently on JB? Im running the stock JRO03C Build rooted, busyboxed, and deodexed (http://forum.xda-developers.com/showthread.php?t=1737849), and only MOD I have on top of that is a battery percentage mod(http://forum.xda-developers.com/showthread.php?t=1738335). Recently in the past week or so I've had a few sleep of death incidents. This morning was one of them where my alarm didn't go off! My notification light was on, and my phone was plugged into the charger, but couldn't wake it. Anybody else experiencing this issue, or have any suggestions of things to look at/try? All the other threads on this are from ICS, so not sure if they would apply since this in on pretty much stock JB.
I don't know but think people either don't know the meaning of stock or I have to learn the meaning
What you described is not stock Rom.and to your answer no I don't get sod.
True. I'm not on stock, I guess I meant to say that my ROM was created from stock. Good to know that someone else is not experiencing this though. Thanks.
The only issue I have is that the phone freezes after recieving or making a call.
That happened about two times only.
I only have about two weeks with the phone and I upgraded to JB as soon I got the phone. I didn't even run the setup wizar in JB: just unlocked the bootloader and flashed 4.1.
I though it was a bad flash and applied the yakju 4.0.4 factory image and the flashed the OTA to get stock JB 4.1.1. I had the issue only one time with that setting.
Right now, my phone is completely yakju. I don't remember my variation. I just recall it came with 4.0.1 and upgraded itself to 4.0.2 and no more.
Cheers!
andrewhansen86 said:
Anyone else having sleep of death issues recently on JB? Im running the stock JRO03C Build rooted, busyboxed, and deodexed (http://forum.xda-developers.com/showthread.php?t=1737849), and only MOD I have on top of that is a battery percentage mod(http://forum.xda-developers.com/showthread.php?t=1738335). Recently in the past week or so I've had a few sleep of death incidents. This morning was one of them where my alarm didn't go off! My notification light was on, and my phone was plugged into the charger, but couldn't wake it. Anybody else experiencing this issue, or have any suggestions of things to look at/try? All the other threads on this are from ICS, so not sure if they would apply since this in on pretty much stock JB.
Click to expand...
Click to collapse
+1
I was having screen freeze while using the google reader app. Had to pull battery.
Am running the same ROM, with battery percentage mod as well. Stock kernel. Not sure why.
possible sleep of death fix?
andrewhansen86 said:
Anyone else having sleep of death issues recently on JB?.
Click to expand...
Click to collapse
I was running stock 2.3.2 on my Evo Shift and was experiencing this issue. try backing up your sd card onto your desktop and then formatting it. it worked for me. I run an unofficial version of cm9. the only issue i still have is that my htc logo that shows at boot is still gone, and with that gone I cant easily select items in hboot/fastboot on the device. but thats for another forum for another day.
chorner said:
I was running stock 2.3.2 on my Evo Shift and was experiencing this issue. try backing up your sd card onto your desktop and then formatting it. it worked for me. I run an unofficial version of cm9. the only issue i still have is that my htc logo that shows at boot is still gone, and with that gone I cant easily select items in hboot/fastboot on the device. but thats for another forum for another day.
Click to expand...
Click to collapse
1. 2.3.2 isn't JB.
2. The GNex doesn't have an SD.
3. It's also NOT an Evo shift.
4.Nice first post.
063_XOBX said:
1. 2.3.2 isn't JB.
2. The GNex doesn't have an SD.
3. It's also NOT an Evo shift.
4.Nice first post.
Click to expand...
Click to collapse
good point. i also was wrong about the sd card anyways. i flashed cm9 back on it. turned auto brightness off. it had the issue. rebooted. turned it back on. re-enabled autobrightness. no issue.
thanks for the compliment.
I'm on 4.2 and have the issue. A few times a day, I'll pull it out of my pocket and I see the "backlight" turn on but screen is on. (I'm not sure how there is a backlight if is amoled but i do see some kind of something very very faint )
In Developer Options put all animation scales to .5x.
el_charlie said:
The only issue I have is that the phone freezes after recieving or making a call.
That happened about two times only.
I only have about two weeks with the phone and I upgraded to JB as soon I got the phone. I didn't even run the setup wizar in JB: just unlocked the bootloader and flashed 4.1.
I though it was a bad flash and applied the yakju 4.0.4 factory image and the flashed the OTA to get stock JB 4.1.1. I had the issue only one time with that setting.
Right now, my phone is completely yakju. I don't remember my variation. I just recall it came with 4.0.1 and upgraded itself to 4.0.2 and no more.
Cheers!
Click to expand...
Click to collapse
I experienced a similar issue on 4.1, but it would happen almost once day (very annoying). I'm now on a 4.2 rom and I haven't seen the issue in weeks. :laugh:
This never used to happen but in the last week has.
While using it, whether I'm in GoSMS Pro, or Chrome or even in the homescreen the screen will fade to black then back one to three times. It almost feels like proximity detection but there's absolutely no obstruction nor am I in a call.
Running 4.0.4 stock unrooted, latest update from Rogers.
Has anyone had this? Getting a bit worried!
Screen blacking out randomly
I'm also having this problem. I'm also on Rogers but I'm am rooted. I am however still using the stock rom. It all started happening after I did the latest update. Any help would be appreciated.
dropzone01 said:
I'm also having this problem. I'm also on Rogers but I'm am rooted. I am however still using the stock rom. It all started happening after I did the latest update. Any help would be appreciated.
Click to expand...
Click to collapse
YES! Finally I'm not alone.
I was worried this was isolated. This confirms even more my suspicion it's a software not a hardware issue. The other reason why it would be so is because after it flashes off and on, the screen elements also do, which indicates the software is trying to refresh the display. If it were hardware it would likely not fade flash and nothing would change on the screen.
It sounds like the software update caused it as I noticed it started after installing it.
I ended up doing a hard reset yesterday after having had no responses. I am hoping it might help. I hate having to reinitialize so much crap while unrooted though. I was hoping to keep it stock and not worry about saving app data until Jelly Bean official stock is out. Oh well.
I also learned S Memo Samsung account syncing doesn't work. Good thing I made a Kies backup. Sigh...
Victorminator said:
YES! Finally I'm not alone.
I was worried this was isolated. This confirms even more my suspicion it's a software not a hardware issue. The other reason why it would be so is because after it flashes off and on, the screen elements also do, which indicates the software is trying to refresh the display. If it were hardware it would likely not fade flash and nothing would change on the screen.
It sounds like the software update caused it as I noticed it started after installing it.
I ended up doing a hard reset yesterday after having had no responses. I am hoping it might help. I hate having to reinitialize so much crap while unrooted though. I was hoping to keep it stock and not worry about saving app data until Jelly Bean official stock is out. Oh well.
I also learned S Memo Samsung account syncing doesn't work. Good thing I made a Kies backup. Sigh...
Click to expand...
Click to collapse
Update: unfortunately the hard reset did not fix it. Problem has returned as of Sunday. I hope Jelly Bean comes soon. :S
In the meantime I'm talking with Rogers about this and pointing them to this thread.
Temporary solution found
Victorminator said:
Update: unfortunately the hard reset did not fix it. Problem has returned as of Sunday. I hope Jelly Bean comes soon. :S
In the meantime I'm talking with Rogers about this and pointing them to this thread.
Click to expand...
Click to collapse
I think I've solved it, but this may not be a solution for most people experiencing this (my friend also had this issue). In my case removing the game Modern War solved it.
I remember that after I installed it, the system started doing these flashes. It now has been behaving ok for 4 days since uninstalling it.
I don't think the game itself is the cause, but rather there could be some background task from it (it does occasionally push game event updates as notifications) that doesn't like the 4.0.4 update. In this case I can't quite identify what nor do I know how to diagnose it.
Just thought I'd update people in case they still have this issue. It may be one of your apps, essentially. It sucks and it shouldn't happen, but alas unless we test with a new stock OS update, we won't have much to eliminate it without removing the offending app.
After upgrading from 4.0 to 4.1 I found that my phone won't switch on until I press the power button three times although sometimes it does switch on first go. Then, I installed the latest OTA patch to 4.1.1, software number 3.14.401.31 (international version) and found that accessing the camera from the lock screen, with security pattern enabled, is very slow. That is when you drag the camera to the unlock ring and release, the lock ring pauses for about 5 seconds before the camera starts up. This didn't happen before the last update.
So far I have taken the camera out of the unlock bar and rebooted the phone and turned off geo-tagging photos. None of these options helped.
If I turn off the pattern unlock then accessing the camera from the lock screen is normal so this appears to be something to do with accessing the camera with the pattern unlock enabled.
Hi,
I have encountered the same thing - seems like you're the only one who has reported it on these forums so far. I hadn't tried disabling the pattern unlock, thanks for the tip. I'll try this. But I'm quite unhappy about this new bug that just came out of nowhere with the 4.1 update, especially knowing that the camera quick start was one of the features HTC boasted about so much!
Yeah, not much on it at the moment but the upgrade is quite recent. Hopefully more people will find this thread and we can get some traction.
Same problem here, me and my wife. Wery annoing!
Sent from my HTC One X using xda app-developers app
I emailed HTC and they replied the next day which was good. They asked me to reset the camera app, reboot the phone and then factory reset the phone if the other things didn't work. It didn't fix it yet so I'll see what they come up with next.
exazonk said:
I emailed HTC and they replied the next day which was good. They asked me to reset the camera app, reboot the phone and then factory reset the phone if the other things didn't work. It didn't fix it yet so I'll see what they come up with next.
Click to expand...
Click to collapse
Exazonk,
please let us know if it works!
Thanks!
:good:
Pietje_1985 said:
Exazonk,
please let us know if it works!
Thanks!
:good:
Click to expand...
Click to collapse
No factory resetting my phone didn't work. HTC rang me back and said that I need to return it to who I bought it from. In other words no fix and returning certainly won't prove anything. I think I'll just have to wait it out until it is fixed with another update ... hopefully.
Or maybe we should looking at getting an app that provides the same functionality?
Have te same bug guys :/
Sent from my HTC One X using xda premium
I tried the factory reset too, to no avail. Seems like disabling the phone lock is the only solution, but that's not really what I would call a satisfactory solution, since I'm using a VPN on my phone and that requires a lock + I just don't want to go lock-free.
We need this issue to be known to HTC and hopefully a fix will come.
Ps I don't think this problem was present in the JB update, but only came in the small FW update that followed.
Sent from my HTC One X using Tapatalk 2
benitorios said:
I tried the factory reset too, to no avail. Seems like disabling the phone lock is the only solution, but that's not really what I would call a satisfactory solution, since I'm using a VPN on my phone and that requires a lock + I just don't want to go lock-free.
We need this issue to be known to HTC and hopefully a fix will come.
Ps I don't think this problem was present in the JB update, but only came in the small FW update that followed.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Yeah it only came in the small update after the JB update. But another problem that I'm having is that to turn my phone on via the power button, sometimes I have to press the power button three times. It doesn't always happen, but sometimes after the phone has been off for a while, I hit it once and nothing, hit it again, nothing and then on the third press it comes on. I'm not sure if they are related to the "quick" camera launch problem.
One work around for this bug, if you use your camera a lot, is to leave your camera in standby mode. That is turn your phone off while the camera is active and then when you hit the power button it will go straight to camera. I don't use this myself as I have the lock pattern on to prevent my phone from turning on in my pocket which is common on HTC phones
HTC support are a waste of space
I have this issue too. HTC told me to factory reset it, then when that didn't work they told me to return it to the store to be sent away for repair. They really don't have a clue at HTC support.
The phone was returned to Vodafone yesterday and the repair centre said "no fault found" What are they on!!! The Vodafone store confirmed the issue was still there.
I now have the phone back with no resolution.
Going to call Consumer and get some advice.
I have this problem too, quite annoying.
Sent from my HTC One X
Ok, they fixed this bug with the latest 30MB update that I got this morning.
exazonk said:
Ok, they fixed this bug with the latest 30MB update that I got this morning.
Click to expand...
Click to collapse
:good: Great news!
May I ask where you're based? I've got a UK CID and haven't seen this update yet. Did you do anything special or did it just come as OTA?
Thanks!
benitorios said:
:good: Great news!
May I ask where you're based? I've got a UK CID and haven't seen this update yet. Did you do anything special or did it just come as OTA?
Thanks!
Click to expand...
Click to collapse
I'm in Brisbane, Australia and ordered my phone through kogan.com.au. It popped up as an OTA on my phone.
Thanks. Looks like that 3.18 OTA is seeding at the moment, shouldn't be long before I get it. Fingers crossed....
Sent from my HTC One X using Tapatalk 2
This has happened to me twice while in my pocket since receiving the OTA a week ago. This never happened with ZV9 since getting the phone months ago.
Has anybody else seen this? Any ideas what this might be? Any apps to help figure out what's causing this? Is this related to the location service reboots that other phones on Jelly Bean like the Nexus were having?
I am not a big fan of Android version changes via "patching" for this very reason. I suggest doing a factory reset and see if it continues to happen.
Lokifish Marz said:
I am not a big fan of Android version changes via "patching" for this very reason. I suggest doing a factory reset and see if it continues to happen.
Click to expand...
Click to collapse
Good call, thanks for the input. I was considering doing that if it keeps up.
I'll probably root and unlock soon anyway once I have some time.
spackmanbr said:
Good call, thanks for the input. I was considering doing that if it keeps up.
I'll probably root and unlock soon anyway once I have some time.
Click to expand...
Click to collapse
I had this problem and it only happened after I had updated the Android Booster FREE app. I uninstalled Android Booster FREE (as it really wasn't useful, in my opinion anyway) and the problem disappeared. If you have this app installed maybe you can uninstall it and see if that solves your problem.
Thanks for the input, but I never use any apps of that nature, and no power saver apps either.