Anyone else having this problem. So far it's happened twice on me. I click the power button to lock the screen and then I come back to it a minute later and it's off. I try to turn it back on but it doesn't unless I remove and replace the battery.
I had this problem, even while running stock everything. The phone is very likely defective. I had to exchange it at the Sprint store.
I probably will do that if it happens more
Sent from my SPH-D700 using XDA App
Are you using SetCPU or anything like that? That happened to me one morning (because I set the minimum clock frequency too low: 100 MHz) and it wouldn't come back on save for a battery pull. I think the minimum safe frequency to prevent that from happening is around 400 MHz... but then there's no reason to have setCPU installed in the first place.
If that's not your case, then it's probably a defective phone, go and exchange it if that happens again.
Maybe related, maybe unrelated, but mine did the same thing after installing SetCPU and setting the profile to "OnDemand".
After actually reading the SetCPU info, it says on the Galaxy S phones the "OnDemand" will cause issues and you should use the "Conservative" setting to have it auto-scale the CPU to usage demand.
Swapped mine to that, and no issues since.
I've had this happen on occasion with an unresponsive program that is hogging the CPU. Mashing the power button repeatedly has little effect, so I just give it a few seconds, and try again. I don't think it has ever taken longer than 30 seconds to respond. Apps that can trigger this behavior include the AP News app, which is terribly-coded and even less responsive. Don't fault the device - it's just unresponsive software. As capable as the CPU and OS are, it's still possible to get a hangup like that.
Related
Hi.
This problem has been posted before, but there was no answer, that worked for me. I was wondering, whether anyone has found a fix in the meantime:
My MDA crashes almost every night when it's in standby and can't be woken up by pressing the POWER-button.
Sometimes, this even happens during the day when it's connected to the computer, goes to standby and then is disconnected.
Only a soft reset will solve the problem.
I don't really have that much software installed, especially no Today-screen plug-ins.
However, I had task switchers such as switch and tswitch installed, which didn't work for me and thus has been removed. I have the impression, that after uninstalling these, my problems started.
One of these - I don't recall which one - has a today plug-in which monitors battery and memory capacity.
However, it seems that programs on my MDA never get completely uninstalled. The unistaller always says that it can't completely uninstall the software and whether I'd like to remove the program from the list of programs installed. So what I did was clear the device manually... maybe that was a mistake...
Any thoughts on this?
sacha
I have exactly the same problem. First I had no battery charge and then after replacing the battery, I have this problem.
Any ideas please?
Is it a hardware fault and I need to return the device?
Cheers,
Joe
I have a same problem too, but until today i don't find any problem solving. Please help.
I've had exactly the same problem with my T-mobile MDA pro. I first returned it to the shop but the tech department could not find anything. Gradually the problem got worse; in the end it would not power-up at all and I had to perform a soft-reset each time. Even with only the factory default software running. Returned it the second time and got a new machine; problem solved. So it definitely is a hardware problem.
Could this be a battery problem?
This may be dumb, but ..........
This may be wildly off but I've had two problems that looked a bit like this with my XDA exec. Sometimes when I go walkabout with the wifi left on, even though I've switched off the pda, it will refuse to wake up afterwards. This has happened a few times, but never if I switched off the wifi before going on the move. I wondered if it was trying to connect and entering some hangup state. I have heard it beeping in my pocket as I walked past wifi points and it wakes up. Obviously it isn't consistent.
The other problem happened when I first got the pda while I was carrying it in trouser pockets with the on/off button exposed (ie not in the closed end of the leather cover. It appeared to be hung up and wouldn't wake up (apparently) but all that had happened was that the backlight had been switched off by an extended press on the on / off button. That may sound really stupid, but without the backlight in some lighting conditions the screen just appears dark. I sorted that one, by ensuring the end of the pda with the on / off switch is always in the pouch and safe from being squeezed in my trouser pocket.
Solution Found!!
its a problem with the voltage control Unit on the Mainboard. My solution for my Jasjar was to install Pocket Hack Master and then disabling the CPU scaling of the Bulverde in the settings. Before turning your unit off or closing the clamshell make sure the speed is underclocked at 312 mhz..you can always set it at 520 while using it. Hope this helps!!
clemsyn said:
Solution Found!!
its a problem with the voltage control Unit on the Mainboard. My solution for my Jasjar was to install Pocket Hack Master and then disabling the CPU scaling of the Bulverde in the settings. Before turning your unit off or closing the clamshell make sure the speed is underclocked at 312 mhz..you can always set it at 520 while using it. Hope this helps!!
Click to expand...
Click to collapse
same problem here. sometimes i just press meny meny times (very fast) the power button and the screen turns on. other times i have to soft reset.
clemsyn i'm not sure i understand your solution. do you say that every time i want to turn of the screen i have to start PHM before, and set the speed to 320?
if this is the solution, wouldn't it be very annoying?
I've got exactly the same Problem. I've already changed the battery, flashed Original Rom, WM6 and so on. The strange behaviour of my Mda Pro still exists. After a while, the Pro switches off (Standby-Mode) and most of the time, i can switch it on with pushing the Power-On-Button. But if the Pro stays in the Stand-By-Mode for a while, i cant't bring "him" back to me. Only a Hardreset works (most of the time, i have to put in the Power-Supply, otherwhise, only the red light flashes one time when i push the reset-button).
The problem first appears, when i flashed the original Rom to WM6 (with all steps i had to do: upgrade bootloader to 1.01 and so on). Downgrading to Bootloader 1.00 didn't solve the probs.
At this point, i'am a little bit confused.....i need help
P.S:
Hopefully, my first post is not the last one
Edit:
http://forum.xda-developers.com/showthread.php?t=267448&page=1
I've just read this Thread. Very good informations. So i'll try it with an original Battery...i will post my experience asap.
Not for me it worked
clemsyn said:
Solution Found!!
its a problem with the voltage control Unit on the Mainboard. My solution for my Jasjar was to install Pocket Hack Master and then disabling the CPU scaling of the Bulverde in the settings. Before turning your unit off or closing the clamshell make sure the speed is underclocked at 312 mhz..you can always set it at 520 while using it. Hope this helps!!
Click to expand...
Click to collapse
Hello Clemsyn,
I tried this with Pocket Hack master. First it worked and i started walking, and singing throough my house again.
And now, after a few days, it gives me the problems back. No difference if it is automatically set to standby or with the power button. sometimes I still need to reset.
Hack master gives an error when restarting, so I am sure it was switched on to this 312 speed and blocking the scaling of my Qtek.
I am tring to find a railway to put my head on!
Huib
I think we all have the same problem and no one has found the solution to it ? what a shame i-mate couldnt come up with a patch or upgraded ROM which will work hazzle free..
I have to soft reset everytime when my phone goes to standy mode and doesnt wake up.
I am sick of this **** , planning to sell my jasjar ....any takers ?not really here tho.
I had the Standby of Death SOD this is when the phone fails to come out of standby with a power button press. This issue only affects some people on some networks. I'm not sure if its a network problem or a software problem but as only a minority of people have it, I suspect its mainly a network problem there is a software solution.
The solution is to change the phone settings band option from auto 3G/2G to either 3G Only (WCDMA + UTMS 2100 in Europe) or 2G Only (GSM + AUTO) depending on your requirements.
Also read this thread http://forum.xda-developers.com/showthread.php?t=540943&highlight=standby&page=2 where the resolution was to get a new SIM.
Obviously this only solves the problem when the crash is because of the sim and/or settings which impact the sim. To rule out a software cause its best to start with a hard reset.
I know there might be a dozen threads about this, but its all gobbledygook and nobody seems to have a straight answer.
I just want to ask: What can we possibly do about Froyo draining our battery? Task manager auto-killers aren't working right now it seems.
Turn off 4G
Turn off WiFi
Turn off GPS
Turn down brightness
Stop opening crap
Problem solved.
Task Managers??? Are you kidding me? My battery life has doubled since Froyo because I dont use task managers or auto killers. Use Fresh Rom, with set cpu with perflock off, change the screen off to 245/245. Most important part is condition your battery...Trust me, i thought it was stupid as well, but it works.
drmacinyasha said:
Turn off 4G
Turn off WiFi
Turn off GPS
Turn down brightness
Stop opening crap
Problem solved.
Click to expand...
Click to collapse
haha thats funny and true so i like it. i am running froyo official and have noticed an increase in battery. but hey when you get near your computer plug your phone in when you get in your car plug your phone in.
Froyo Killed Your Parents??
Sorry To Hear About Your Parents
R.I.P.
theres not much else u can do..just wait for a fix
I have ota and its the worst batterie ever with out doing nothing not even a phone call it died under an hour i only have gps enable had 3g off 4g to app all close no auto killer
Htc Evil Phone
I have the same problem. I read reports that Facebook 1.3 will not release the partial wake lock. I took FB 1.3 off and the problem persisted.
Here is how to check if you have a problem with your partial wake lock:
goto settings > about phone > battery and compare the uptime and awake time. If they are the same or very very close you have a wake lock problem. A wake lock allows an app to prevent your phone from going to sleep, even if the screen is off. If these times match then an app is creating a wake lock and not releasing it, and therefore your phone never sleeps.
As I said removing FB 1.3 did not solve the problem, but I was able to prove it is a wake lock as using Advanced Task Killer to kill 21 tasks allowed my phone to actually sleep, as indicated by a corresponding difference in the two times. So now that I know this is an app doing it, I will try to narrow it down and figure out which and report back.
OK I just found it. It appears the LED Light widget also causes a partial wake lock. To alleviate you don't need to uninstall it, just remove the widget.
Which led light? From market or the one with 2.2?
Borg1982 said:
Which led light? From market or the one with 2.2?
Click to expand...
Click to collapse
The new "flashlight" app is not a widget...It's actually called LED Light, by picolyl.
I don't have a problem, for me is little better!!!! just buy a new battery that solve your problem
drmacinyasha said:
Turn off 4G
Turn off WiFi
Turn off GPS
Turn down brightness
Stop opening crap
Problem solved.
Click to expand...
Click to collapse
Problem NOT solved. Or maybe 15 extra minutes.
Or don't use it at all, you'll save plenty of battery
Check to make sure that your Google Talk app is not automatically signing in. Go to apps - talk - settings. This is a typical battery drainer
totally forgot about google talk. have flashed a few ROMs back and forth, and now running a stock rooted ROM, I forgot to shut this one off...
use a custom rom, something without sense and try not to have a f***ton of widgets. im running cyanogen nightly and i get about 10 hours before i hit 20%-30% thats when i quit doing stuff and start trying to make the battery last. screen eats most of the battery so turn the brightness down.
my average 10 hours is 75-125 txts 30 + or - min of talk time and 3+ hours of internet (facebook)
oh, and about your parents... they are gone, there isnt an app or a rom that can fix that.
Indeed, the title of this thread is goofy. Froyo has literally killed my parents....... and has done a bad job for my battery life on my phone. Haha!
I guess an apostrophe would not have hurt after the word "parents" eh?
Doing a factory reset will fix your problem... I had the same problem when I updated.
Sent from my PC36100 using XDA App
opie2l said:
Doing a factory reset will fix your problem... I had the same problem when I updated.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I'm having similar issues with my OMJ 2.2 froyo rom. poor battery life, plus it seems laggy and unresponsive. i was much happier with OMJ's 2.1 rom
My phone is not sleeping itself down after the time elapses.anyone else noticing this, its making me think its draining my battery.
Just tested this myself, and on a one minute sleep timer, my phone did properly go to sleep.
Mine sleeps fine too.
mine sleeps fine as well. Do you have any particular app running? For example, if you have AT&T Navigator running it will not sleep. There are a few other apps that provide the ability to prevent it from sleeping. So, are you on the main screen or in an app when it doesn't sleep?
Cannot say I've had this problem. Worked at its default of 1 min, and still works after I changed to 3.
I am trying to id the app if any that is causing it but with no task manager its impossible.
I do notice an issue with the camera app. If the camera button gets pressed then the phone will stay on and not sleep, for me at least.
It goes off on it's own mostly...thanks for the reports as I work through this. I may need a hard reset anyway, hey why not Ill add a microSD at that time.
Hey guys I have a rooted fascinate running jt1134 super clean done yesterday. Twice now since then the phone had shut down while idle. When I go to turn it on the phone doesn't respond. The only way to get it to come back to life is pulling the pulling the battery. Obviously something I did yesterday is causing it. Any ideas thanks...
Sent from my SCH-I500 using XDA App
Do you have SetCPU enabled at boot, or any active SetCPU profiles? My phone did the same thing when I used either of those features while on jt's clean.
Second the set CPU settings. I was having the same thing. I was trying to set profiles like I did on my D1 no go. I am still getting unable to auto detect after reboot, with no profiles. Nothing like learning it all over again.
I used the update.zip from the Samsung site to update to EB13, everything went off just fine except my Epic now takes an average of 2 seconds to wake from sleep after pressing the power button, sometimes going up to 4 or 5. Not the worst thing in the world, but pretty annoying.
I narrowed it down to my non-usage of the lock screen. I typically run without using a lock screen at all (disabled via SwitchPro Widget). If I turn the lock screen back ON, my Epic wakes from sleep either instantly or within 1/2 a second. With the lock screen disabled (no pattern lock either), it's super slow to wake.
Anyone have any ideas on what I could try?
Mine works just fine, but I'm using the lock screen, try uninstalling that widget and see if it corrects the problem when you use the lock screen.
Small update to this. I had an idea to move all the apps that I had moved to the SD card back to the phone to see if that helped. It does. With the lock screen on, my Epic comes back from sleep instantly every time. With lock screen off it varies between 1/2 and 1 second.
The apps I moved to SD were ones I hardly used.. I don't know why that would have an effect on the wake time?
Mine seems a bit slow too. But it's not the 4 or 5 seconds you described. It seems like it's about one second, when it used to be anywhere between instantly and half a second.
It's kind of annoying because the delay is just barely too long to where I start second guessing myself on whether or not I pushed the button in all the way or not.
Go to your display setting and reset your horizantal calibration accelerometer... that fixed my phone waking up issue...
Sent from my SPH-D700 using XDA App
Unfortunately, I had already tried recalibrating. I do, however, have no lock on and widget locker running. Do any of you use either of these?
toxicsociety said:
Unfortunately, I had already tried recalibrating. I do, however, have no lock on and widget locker running. Do any of you use either of these?
Click to expand...
Click to collapse
I use the same program as you do and I have the exact same problem So your not alone.
Mine is slow to wake also, about a second. When its plugged into the charger its instant, weird.
I'm glad we aren't alone though. Hopefully if this is a big enough issue, people will look into it. And also, they've pulled the EB13 update from Sprint and Samsung's website.
It's causing problems with reading media from the SD card and also has data issues. So hopefully in the new one, they will fix this problem too?
Looks like it's No Lock, from what I can tell. If you disable it, it comes on instantly. If it's enabled, it takes it a moment to wake up.