Related
Happened this morning, I noticed that my diamond2 is not responding when pressing the power button as usual... black screen!
It wakes-up in two cases:
1. soft reset with the stylus.
2. removing the battery and putting it back then pressing the power button.
This happens after I leave it turned off for 5 minutes. It is working fine as long as I don't turn it off. When it is off 5 minutes then no response!
Note: I am using the latest htc rom.
Don't know if this is a software or hardware problem. Any help is much appreciated.
I have actually had a fairly similar problems with my TD2. Not regular and not at spercific times like after 5 minutes but there have been times when my screen doesn't want to turn back on, the device is still on because it still make some of the regular sounds, eg the ping on the home button but the screen is dead.
Like you it will only wake again after a battery out reset, sometimes after several attempts.
I'm pretty sure this is hardware related as like you i'm on an official rom. The first time this happened was after using the phone as a modem and it got quite hot so i think perhaps heat is loosening the connection to the screen, only a guess though so any other opinions welcome.
After trials for 8 hours, I figured out a work around.
I Forced the mobile to work in the GSM only band, from that moment, it is back to normal... 3G is important to me, but I think I will wait until the WinMobile 6.5 is out for our TD2... may be this will solve the issue!
Hard reset it at least once..... That may take care of the freezing issue.
tomtommy306 said:
Hard reset it at least once..... That may take care of the freezing issue.
Click to expand...
Click to collapse
did not solve the problem! could this be a network problem or the device's radio rom?
My phone did the same, i disabled the TouchFLO and it worked Fine
mkh1983 said:
My phone did the same, i disabled the TouchFLO and it worked Fine
Click to expand...
Click to collapse
This one also did not solve the problem. Any other suggestions!
Problem solved
As I guessed, it was a network error and problem sovled after changing my Sim Card and getting a new updated one from the Service Provider!
Now my TD2 can sleep well and get back whenever called
6.5 is out, has been out for a while now for the TD2...What are you waiting for, might solve this issue...gogogo!
Free Man said:
6.5 is out, has been out for a while now for the TD2...What are you waiting for, might solve this issue...gogogo!
Click to expand...
Click to collapse
I have the same problem and i notice that sleep everytime who i use Alarm(clock)...
Noticed that??????
Some times alarm clock sound doesn't work.... the audio level is high...
Free Man said:
6.5 is out, has been out for a while now for the TD2...What are you waiting for, might solve this issue...gogogo!
Click to expand...
Click to collapse
I am afraid I have to bump the thread.. I received my device from the HTC service with a new 6.5 ROM installed, and I started having this problem. The deviced sleeps and does not react to pressing Power button, neither to pulling the stylus. The only way how to wake it is to remove the battery and switch it on again. Any idea how to solve this?
The same problem
cassper1 said:
I am afraid I have to bump the thread.. I received my device from the HTC service with a new 6.5 ROM installed, and I started having this problem. The deviced sleeps and does not react to pressing Power button, neither to pulling the stylus. The only way how to wake it is to remove the battery and switch it on again. Any idea how to solve this?
Click to expand...
Click to collapse
My TD2 starts the same problem . After some standby time the power button stops working. I tryed to re-flash ROMs , Hard Reset, Change the battery, and nothing solve the problem. The Power Button not working! The only way is soft reset... Any idea?
This is referred to as the "Standby of Death"
The only fix I am aware of is to flash a custom ROM.
hello guys. there is no need to flash a new rom. i had same issue, but hard reset and backup restore helped me. try this on your phone. for back-up, use sk tools
http://www.s-k-tools.com/index.html?sktools/m_feat.html
This is my second SGS with this problem and I am trying to determine if it is common or if I am just monumentally unlucky.
During normal use the bottom soft keys (menu and back) will become non-functional. One will stay lit and one will go out, but both will cease to work. Everything else on the phone is still responsive, sometimes the keys 'revive' themselves after a short period of time, other times I need to lock the phone to get them back.
I got this phone (a replacement) on the 6th, and this started on the 12th and has been happening more and more often ever since. Has anyone else seen this or have an idea what it may be? Or is this phone is destined to be my 2nd DOA in a month?
Here is a video showing the problem: '
you tube.com/watch?v=1s-wqWsHaIs
That is definitely not normal behaviour.
Exact same problem here; it seems to happen when I'm using the phone quite a bit but when I leave the phone alone for awhile, problem seems to go away then return because I'm using it too much.
// galaxy s
hol17 said:
Exact same problem here; it seems to happen when I'm using the phone quite a bit but when I leave the phone alone for awhile, problem seems to go away then return because I'm using it too much.
// galaxy s
Click to expand...
Click to collapse
FYI: Samsung support told me to return my phone.
It is almost like one of the soft keys gets stuck 'down', because it is the same behavior if you just hold down one of the keys. Mine seems to happen more when bluetooth is on and it comes and goes in spurts; good for an hour, bad for an hour, etc.
ETA: I am sure now that the soft keys are getting 'stuck down'. I have seen it 3 times now where I would press the left soft key and the light on the key will remain out, then after a second or so the quick search screen comes up and the left soft key light is still out.
any solution to this problem? i seem to have a slightly different issue
this just happened to me recently everything was working fine until this morning when i tried to press the menu and back buttons it wouldnt work, although the buttons light up and is registering my actions when i press them the light turns off and let go is lit up again.
could this be a software issue or something conflicting with my lednotification mod?
please reply ^_^
I've got the exact same issue with my soft keys getting stuck too. Just started a couple days ago, phone's less than a month old. I was also told to take my phone in for repairs.
Oh one tech support guy told me that Froyo might fix it... I'm kinda hoping for that, seeing as how this issue isn't exactly 100% reproducible for the warranty service department
I have the same problem its almost like the soft key is being held down, anyone find a fix for this?
Add me to the list
Add another one to the list. I too am experiencing this problem and I'm unfortunately screwed because of it. I attempted to return the phone, however the store in question refused to accept it because they tested it and found it had been unlocked. Two week old phone on stock FW bought outright ($600) and they won't replace it.
Unbelievable!
robcarey said:
Add another one to the list. I too am experiencing this problem and I'm unfortunately screwed because of it. I attempted to return the phone, however the store in question refused to accept it because they tested it and found it had been unlocked. Two week old phone on stock FW bought outright ($600) and they won't replace it.
Unbelievable!
Click to expand...
Click to collapse
Lock it back and go again.
I know this post it's a bit old, but i was harvesting the web looking for an answer to my problem that seems to be the same posted here.
I have a i9000T with eclair 2.1 and soft keys get stuck now and then. I couldn't find a way to reproduce this behaviour.
Recently (yesterday) i flashed a new 2.3.3 firmware hoping this curse to end. The problem seems to persist, but in some situations that i asume for a bad flashing (i didn't repartition neither wipe the phone before flash).
Anyway, can anybody tellme if this is a software or hardware issue? I'll have to return my phone or this is going to be 'fixed' with a nice flash?
Thanks.
cknu said:
I'll have to return my phone or this is going to be 'fixed' with a nice flash?
Thanks.
Click to expand...
Click to collapse
Only one way to find out mate.
You need to flash a 2.1 rom that consists of 3 files. 512 pit and re-partition.
Should get you back on track again.
I did flash it again with the 2.3.3 JVH, a few moments ago. Also did a repartition and wipe data and cache. It seems nice, but in a few minutes the same happend. Now, when i press the menu button it takes a nice screenshot of the phone. xD
I need to flash to a 2.1 version? Why is this? I thought flashing with any rom will work.
Thanks.
Solution to this problem!
Hey all - I found a solution to this problem - I can confirm this has fixed the problem on TWO phones for me - read the whole thread as this fix doesn't like custom firmwares, but works fine with all the regular FWs I've downloaded.
Works perfect - and simple fix!
http://forum.xda-developers.com/showthread.php?t=869492
^^^
Do not do this unless you have a i9000m. You will break your buttons.
electrotune1200 said:
^^^
Do not do this unless you have a i9000m. You will break your buttons.
Click to expand...
Click to collapse
Too bad i didn't see this before
I have I9000T used this 2663 method and now my soft buttons doesn't work anymore...
Didn't find a clear solution in the forums so i want to ask, like i said my phone is a I9000T with official 2.2.1 (UBPJA) rooted using SuperOneClick and unlocked editing the nv_data.bin file.
I was thinking on doing a hard reset to get back to the factory defaults but i see many ways of doing it that it gets confusing... i see peolple doing it through the privacy menu but i think that only erase data and doesn't restore anything OS wise, also see other people doing it using volume + home + power and selecting later clear storage, i think this is the same that the option in the privacy menu, and finally i see some people typing this code *2767*3855# what is the proper way to get back to the original OS in my case?
Thanks in advance...
hi,
For starters I've had my G1 since it came out, been rooted for a while so i know what I've been doing.
Anyways.. I've checked the forums and I've seen similar problems like mine but not exactly the answers I need.
Basically my Digitizer is being unresponsive randomly and when this happens my entire phone just FC's everything. The first time i noticed this was when I would Charge my G1 using a Blackberry Charger when id text, the Screen would be unresponsive to touch on all of the screen and just lag on everything. So I would have to unplug it and re-plug it continually. Recently I switched to the new Cyan Rom (i forgot the number) and now it will just randomly be unresponsive with the touchscreen id go on apps and it will FC. Ive wiped and rebooted many times, ive switched roms multiple times as well. So I'm on my last resort and asking for help.
Any help is highly appreciated.
thelistening said:
hi,
For starters I've had my G1 since it came out, been rooted for a while so i know what I've been doing.
Anyways.. I've checked the forums and I've seen similar problems like mine but not exactly the answers I need.
Basically my Digitizer is being unresponsive randomly and when this happens my entire phone just FC's everything. The first time i noticed this was when I would Charge my G1 using a Blackberry Charger when id text, the Screen would be unresponsive to touch on all of the screen and just lag on everything. So I would have to unplug it and re-plug it continually. Recently I switched to the new Cyan Rom (i forgot the number) and now it will just randomly be unresponsive with the touchscreen id go on apps and it will FC. Ive wiped and rebooted many times, ive switched roms multiple times as well. So I'm on my last resort and asking for help.
Any help is highly appreciated.
Click to expand...
Click to collapse
Try to upgrade to the 27.08 Radio/SPL combo. Follow all of the instructions contained within that post. It will suggest you also re-install your recovery. Do it. Once all of this is said and done, if its a software issue, it should be solved.
I had this same issue prior to the upgrade, and all is fine now. Mine didn't FC tho. If I touched the bottom of the screen, it would select something at the top. any questions or a perfect walkthrough, my direct email to my cell is in my info on the left.
<<<<<<<<<< Over there.
ah! thanks! Im actually going to try this now, and hopefully i don't fail and mess up my phone even more than what it already is. and yeah the FCs are really annoying i cant really do anything like make calls, which is ridiculous. Im also having problems with the camera as well i got those really funky colours in it. and then my regular speaker for calls isnt working unless i put it on speaker, i think my G1 is telling me it wants to die. lmfao.
thelistening said:
ah! thanks! Im actually going to try this now, and hopefully i don't fail and mess up my phone even more than what it already is. and yeah the FCs are really annoying i cant really do anything like make calls, which is ridiculous. Im also having problems with the camera as well i got those really funky colours in it. and then my regular speaker for calls isnt working unless i put it on speaker, i think my G1 is telling me it wants to die. lmfao.
Click to expand...
Click to collapse
Oh crap. You have the funky color camera?! That might actually be a hardware issue. But we can certainly try this out. I have the gTalk PC app, and it's up and running now if you wanna run through this.
Hi,
I have a I9000 on TMobile in the UK. Not rooted, just been upgraded to ICS with the official firmware.
Ever since then I've been randomly getting a black screen - i.e. phone doesn't respond to any of the buttons to turn the screen on. Only way to get the phone to work again is a battery pull. Haven't installed any apps from prior to ICS, and prior to ICS I didn't have this problem.
I'm guessing no one's going to have a simple answer to this (although it would be great if anyone does, I've searched and haven't found anything) - but any tips on trying to identify what the cause is? Could it be a bad app maybe?
I tried logcat but didn't really understand it (!) and I wasn't sure if it would record what happened before a battery pull anyway.
Any tips to help get the bottom of this would be much appreciated
Many thanks
Andrew
magosalas said:
Hi,
I have a I9000 on TMobile in the UK. Not rooted, just been upgraded to ICS with the official firmware.
Ever since then I've been randomly getting a black screen - i.e. phone doesn't respond to any of the buttons to turn the screen on. Only way to get the phone to work again is a battery pull. Haven't installed any apps from prior to ICS, and prior to ICS I didn't have this problem.
I'm guessing no one's going to have a simple answer to this (although it would be great if anyone does, I've searched and haven't found anything) - but any tips on trying to identify what the cause is? Could it be a bad app maybe?
I tried logcat but didn't really understand it (!) and I wasn't sure if it would record what happened before a battery pull anyway.
Any tips to help get the bottom of this would be much appreciated
Many thanks
Andrew
Click to expand...
Click to collapse
Samsung isn't making ICS for galaxy S .. how were you able to get an official ICS update?
B*gger, wrong thread, meant the Galaxy S2. Sorry, more haste less speed and all that.... Will ask in there instead.
Apologies./
Hi,
I have a brand new Xperia SP, manufactured on 2013/W50, so it's really new. It contains the latest stock firmware.
After I start or answer a call and put the phone to my ears, it's screen doesn't came back and remains off until the call is ended by the other party. No matter if I'm moving the phone away from my head, not even the hard buttons are turning the screen back on. The touchscreen is not working either. It's just stuck as if it's near to my head. I can't even hang up the call...
It happens about 80% of time. Sometimes it works as expected without any problems. Happens more often when having an incoming call after a longer period (30+ mins) or if the call takes more than 1 minute (auto screen disable time?).
As a workaround, I turned on the function that power button hangs up call, but I cannot use my touchscreen while call.
I checked the proximity sensor with the phone's diagnostic function and with cpu-z and the sensor is just working fine 100% of the time.
Is it a known bug or a hardware problem? Does it have a workaround?
hmmm
carlosmeldano said:
Hi,
I have a brand new Xperia SP, manufactured on 2013/W50, so it's really new. It contains the latest stock firmware.
After I start or answer a call and put the phone to my ears, it's screen doesn't came back and remains off until the call is ended by the other party. No matter if I'm moving the phone away from my head, not even the hard buttons are turning the screen back on. The touchscreen is not working either. It's just stuck as if it's near to my head. I can't even hang up the call...
It happens about 80% of time. Sometimes it works as expected without any problems. Happens more often when having an incoming call after a longer period (30+ mins) or if the call takes more than 1 minute (auto screen disable time?).
As a workaround, I turned on the function that power button hangs up call, but I cannot use my touchscreen while call.
I checked the proximity sensor with the phone's diagnostic function and with cpu-z and the sensor is just working fine 100% of the time.
Is it a known bug or a hardware problem? Does it have a workaround?
Click to expand...
Click to collapse
I have the same problem. It is one of the few bugs in 12.0.a.2.254 build. Guys using unofficial release of 4.3 are not facing such problems. I suggest you to wait for the official 4.3 update which will be released soon according to SONY. :good:
really?
madhukarmohan said:
I have the same problem. It is one of the few bugs in 12.0.a.2.254 build. Guys using unofficial release of 4.3 are not facing such problems. I suggest you to wait for the official 4.3 update which will be released soon according to SONY. :good:
Click to expand...
Click to collapse
thanks!
so, this is surely a known bug in the 254 firmware? I'm just wondering because I asked this on other xperia sp forums but no users complained about it.
is there a workaround for it?
yes
carlosmeldano said:
thanks!
so, this is surely a known bug in the 254 firmware? I'm just wondering because I asked this on other xperia sp forums but no users complained about it.
is there a workaround for it?
Click to expand...
Click to collapse
Yeah, few r experiencing that. i hv seen complaints in sony blog and here too. I asked this question few days back. but, I didnt get reply.
I experienced this problem once.I think it was fixed after performing a SEUS repair...Not sure though :silly:...
Try performing a factory data reset on even reset app datas
thx
UltraWelfare said:
I experienced this problem once.I think it was fixed after performing a SEUS repair...Not sure though :silly:...
Try performing a factory data reset on even reset app datas
Click to expand...
Click to collapse
thanks to both of you, I'll do factory reset and repair via PC software, and some more factory resets. that should solve the problem.
I'm wondering why an out-of-the-box phone needs a reset, but let's see
carlosmeldano said:
thanks to both of you, I'll do factory reset and repair via PC software, and some more factory resets. that should solve the problem.
I'm wondering why an out-of-the-box phone needs a reset, but let's see
Click to expand...
Click to collapse
Don't forget to backup.First of all clear the data of the Settings -> Apps(or reset them)
UltraWelfare said:
Don't forget to backup.First of all clear the data of the Settings -> Apps(or reset them)
Click to expand...
Click to collapse
thanks. I won't backup as I installed only a few apps and the phone is almost factory state. but I'll do everything else.
hope it works. thanks to all, I'll report the results.
carlosmeldano said:
thanks. I won't backup as I installed only a few apps and the phone is almost factory state. but I'll do everything else.
hope it works. thanks to all, I'll report the results.
Click to expand...
Click to collapse
I hope everything goes fine
no success
I reset applications, did a factory reset, reinstalled phone's software with sony pc application, checked after each step, but no success...
sometimes working, sometimes not (mostly not) but the proximity sensor works fine.
out of ideas...
carlosmeldano said:
I reset applications, did a factory reset, reinstalled phone's software with sony pc application, checked after each step, but no success...
sometimes working, sometimes not (mostly not) but the proximity sensor works fine.
out of ideas...
Click to expand...
Click to collapse
Bring it to a sony service(or how's it called to your country)
it seems it's related to deep sleep. when I am called after the phone was left for 30+ minutes, it's more willing to not turning on the screen, but it turns it on after a while if having a long call. when I start the call, it mostly works. not always, but most of the time.
so it seems it's not sensor-related but something like the software is bugging.
what I don't really understand, why the hardware buttons are disabled while phoning when the phone is put to the face. it'd be enough to code that power button turns on/off the screen no matter what the proximity sensor says. I'd program it like that as a backup solution.
I wouldn't send it for repair, here in Hungary I always hear that mobile phone services just reinstall software and don't care about testing or finding the problem (if not deterministic), and do it again and again while you get tired and accept the failure. yes, it's sad but in the time of MNCs, the user doesn't matter at all after bought the product.
carlosmeldano said:
it seems it's related to deep sleep. when I am called after the phone was left for 30+ minutes, it's more willing to not turning on the screen, but it turns it on after a while if having a long call. when I start the call, it mostly works. not always, but most of the time.
so it seems it's not sensor-related but something like the software is bugging.
what I don't really understand, why the hardware buttons are disabled while phoning when the phone is put to the face. it'd be enough to code that power button turns on/off the screen no matter what the proximity sensor says. I'd program it like that as a backup solution.
I wouldn't send it for repair, here in Hungary I always hear that mobile phone services are just reinstall software and don't care about testing or finding the problem (if not deterministic), and do it again and again while you get tired and accept the failure. yes, it's sad but in the time of MNCs, the user doesn't matter at all after bought the product.
Click to expand...
Click to collapse
Try flashing custom firmware(not sure if it will work try it)...
If it doesn't work again then it's a hardware fault and not a software bug
UltraWelfare said:
Try flashing custom firmware(not sure if it will work try it)...
If it doesn't work again then it's a hardware fault and not a software bug
Click to expand...
Click to collapse
yes, that's another option. the other option is to cry off from purchase (I can do it within a week), they return the money, and I buy another one. I'll see as this is not that disturbing problem and I have no other problems with the phone like wifi bug or anything else.
someone said it's a bug so I hope 4.3 next month will solve it.