Captivate not waking from sleep. - Captivate General

Hey, starting to panic here.
Recently rooted my captivate and did a few simple things with it. (Market Enabler, PDAnet) and every time the phone goes to sleep, it won't wake up when I hit the power button. Each time I'm forced to do a complete reset holding the volume rocker and power button at the same time. Anyone else having this issue?

I had the same problem today.
I believe it is SetCPU. After a reboot it does not detect the proper clocks for the CPU.

This kinda stuff is why I'm apprehensive about rooting it. I hope you figure it out and it goes back to normal for you.
I was able to put PDAnet on mine just by putting in airplane mode and turning wifi on. That bypasses AT&T's filter of the Market. You probably already knew that, but some others might not so I figured I'd throw that out there.

waltah! said:
This kinda stuff is why I'm apprehensive about rooting it. I hope you figure it out and it goes back to normal for you.
I was able to put PDAnet on mine just by putting in airplane mode and turning wifi on. That bypasses AT&T's filter of the Market. You probably already knew that, but some others might not so I figured I'd throw that out there.
Click to expand...
Click to collapse
Simply rooting your phone isn't going to cause problems.

dalingrin said:
Simply rooting your phone isn't going to cause problems.
Click to expand...
Click to collapse
+ 1 million.
If people actually understood what rooting does, there wouldn't be so much baseless speculation. But that's asking too much I guess.
As for the OP: it sounds like an app is hosing the phone after sleep. As dalingrin said, SetCPU is a good example. I couldn't get a setting that didn't make the phone fail to wake at least some of the time. To be honest, though, I don't see much of a need for it anyway--you can't use it to overclock the Captivate yet, and if you install a CPU monitoring widget, you'll see the phone's native CPU scaling system works well.
If the only app you've installed is PDAnet, I'd try uninstalling it and testing again. If not, you might want to look for other apps that could cause it, especially anything like a power manager or CPU scaling app.

Related

Random Shutdowns and LauncherPro

I've been very careful not to point a finger at a particular app as a cause of random shutdowns (other than aggressive user settings within SetCPU). Before I continue, let me say that I believe there is more than one culprit responsible for shutdowns and that most are caused by non-app related issues.
I've had my third device for 2-1/2 months. No shutdowns whatsover...until I installed LauncherPro last week. Then they started. I removed LauncherPro and - back to normal. Another user on another forum experienced the same effect and caused me to start this thread. I hereby declare an official suspicion that LauncherPro is one of the causes of random shutdowns. Before you react, I understand that many use LauncherPro with no problems. Great. I'm not saying that the app itself is poorly coded, but rather that it may begin a chain reaction in some devices that causes random shutdowns. I have not taken this declaration lightly. I waited a long time before openly stating my theory. I hope it proves of interest.
Are you using Task Killer? I was having the same issue and thought it was Launcher Pro for a while but when I stopped using Task Killer my random shutdown problems stopped.
Captivate Cog 2.2 Beta 9
No task killers.
I've recently had some extended freezes and one force close with launcher pro, and one shutdown when I was launching Vlingo and/or starting bluetooth, can't recall which step. Might be something to do with the recent update.
Sent from my SAMSUNG-SGH-I897 using XDA App
I suppose I can test this out on mine. I'll let you know what I find.
I was using LauncherPro on my previous handset which experienced random shutdowns, but the shutdowns continued even after reflashing to factory with no add-ons or apps. Not saying that LP isn't causing problems of it's own, but power issues exist regardless.
I've been using LauncherPro (and upgraded to Plus when that came out) since release. No random shutdowns. Actually no random shutdowns at all. But I guess I'm lucky
pezx44 said:
I suppose I can test this out on mine. I'll let you know what I find.
Click to expand...
Click to collapse
Your device would have to be inherently susceptible to shutdowns caused by the action of LauncherPro for your test to work. If your internals are solid, nothing will happen.
pfroo40 said:
I was using LauncherPro on my previous handset which experienced random shutdowns, but the shutdowns continued even after reflashing to factory with no add-ons or apps. Not saying that LP isn't causing problems of it's own, but power issues exist regardless.
Click to expand...
Click to collapse
Agree. LP, IMHO, is simply offered as one possible culprit.
tysj said:
I've been using LauncherPro (and upgraded to Plus when that came out) since release. No random shutdowns. Actually no random shutdowns at all. But I guess I'm lucky
Click to expand...
Click to collapse
You are fortunate, as there are multiple scenarios under which shutdowns have occurred...e.g., during high charge percentages as experienced repeatedly by some. My LP experience is being offered as my phone has served as an otherwise stable environment.
Jack45 said:
Your device would have to be inherently susceptible to shutdowns caused by the action of LauncherPro for your test to work. If your internals are solid, nothing will happen.
Click to expand...
Click to collapse
Oh I'm quite susceptible. I get it regularly until my battery is down to about 82. I've used LP the whole time I had the phone. Currently I am using Captivate Keep Alive and it seems to work. I also started another thread where I found that running Grooveshark keeps the phone alive for me. I can guarantee that my phone will shut off within a couple of minutes of unplugging it without these things.
I'm charging now. I have already backed up and removed LP and CKA. When it is fully charged I will unplug it and leave it alone for a bit and report back. I agree with people who say "hardware issue - return it" but I can't do that and don't mind testing different workarounds. So far CKA has been working pretty well for me but I'm open to running less instead of more to solve it.
pezx44 said:
Oh I'm quite susceptible. I get it regularly until my battery is down to about 82. I've used LP the whole time I had the phone. Currently I am using Captivate Keep Alive and it seems to work. I also started another thread where I found that running Grooveshark keeps the phone alive for me. I can guarantee that my phone will shut off within a couple of minutes of unplugging it without these things.
I'm charging now. I have already backed up and removed LP and CKA. When it is fully charged I will unplug it and leave it alone for a bit and report back. I agree with people who say "hardware issue - return it" but I can't do that and don't mind testing different workarounds. So far CKA has been working pretty well for me but I'm open to running less instead of more to solve it.
Click to expand...
Click to collapse
Excellent. Two separate potential culprits - charge level and LP. I'm looking forward to your assessment.
I decided to reinstall LP to get a baseline. 6 minutes after unplugging it I tried to turn the screen back on and found that it had shut down. I recharged and repeated. Again I found it had shut down when I checked after 6 minutes.
I then recharged and removed LP. I waited 6 minutes and found that it was still on. I am recharging and will try again after a longer period of time but it looks promising. I will let you know when I have more info.
Well, no dice. I checked after a half hour and it was off. I'm open to any other experiments though.
pezx44 said:
Well, no dice. I checked after a half hour and it was off. I'm open to any other experiments though.
Click to expand...
Click to collapse
You have no complaints, my friend. A half hour of uptime is better than 6 minutes!
So, yours is a power-related issue and it looks like CKA is the answer. I wonder if Froyo will address this.
But it was only a half hour when I saw it was off. It could have been 6.5 minutes in.
I'm currently running Froyo (Cognition 8.1). This has been an issue for me since before that though. One thing I can't quite remember is if it happened before I unlocked my phone. Is yours unlocked? I needed to do this because I do not live in the US.
pezx44 said:
Is yours unlocked? I needed to do this because I do not live in the US.
Click to expand...
Click to collapse
Unlocked, rooted, and stable (which is more than I can say for myself).
On a more serious note, when I first received my replacement I created the following settings to try to avoid the shutdowns until I was confident that the phone was o.k.
For your consideration:
1. Wi-Fi was always on and is set to never sleep. The "never sleep" settings can be accessed via the Wi-Fi settings page menu, Advanced tab at the bottom. Reason: I'm attempting to generate additional under-the-cover activity (plus I do use Wi-Fi). As I'm not a technician, this may be nonsense.
2. Power saving mode was not checked. Reason: "Don't do me any favors, Captivate. Your idea of power saving may get out of hand."
3. I never let the phone go into sleep mode on its own (that's still the case). Default is 30 minutes, but I always push the button to get it to sleep and get it to wake. Reason: Just in case the built-in sleep timer thinks that "sleep" and "coma" are synonymous.
You can try these three mods to see if they work for you. Remember to uninstall CKA for now to make the above a valid test.
Don't forget to write.
Jack45 said:
Unlocked, rooted, and stable (which is more than I can say for myself).
On a more serious note, when I first received my replacement I created the following settings to try to avoid the shutdowns until I was confident that the phone was o.k.
For your consideration:
1. Wi-Fi was always on and is set to never sleep. The "never sleep" settings can be accessed via the Wi-Fi settings page menu, Advanced tab at the bottom. Reason: I'm attempting to generate additional under-the-cover activity (plus I do use Wi-Fi). As I'm not a technician, this may be nonsense.
2. Power saving mode was not checked. Reason: "Don't do me any favors, Captivate. Your idea of power saving may get out of hand."
3. I never let the phone go into sleep mode on its own (that's still the case). Default is 30 minutes, but I always push the button to get it to sleep and get it to wake. Reason: Just in case the built-in sleep timer thinks that "sleep" and "coma" are synonymous.
You can try these three mods to see if they work for you. Remember to uninstall CKA for now to make the above a valid test.
Don't forget to write.
Click to expand...
Click to collapse
1. I have the same setting for wifi (I use my phone for SIP calls often).
2. I absolutely agree with you on this and it is also already my setting.
3. I always turn off my screen too, but I will set it to 30 minutes to see if that makes a difference and test again without LP/CKA. I can't see how it would be related but I certainly don't mind trying it if for no other reason than to rule it out.
I'll let you know how things go.
And just in case, by unlocked we are talking SIM unlocked right?
>>> I always turn off my screen too, but I will set it to 30 minutes to see if that makes a difference and test again without LP/CKA. I can't see how it would be related but I certainly don't mind trying it if for no other reason than to rule it out.
As the timeout for sleep mode is power-related, I wanted to take that out of the Captivate's hands. The on-off switch is OURS to deal with at will. Want the room light on? Turn it on. Etc. Basically, I wanted to generate persistent under-the-cover activity (WiFi) while eliminating decision making activity on the part of the device.
>>> And just in case, by unlocked we are talking SIM unlocked right?
I can place any non-AT&T SIM in the phone and it will work.
No LP issues here since I've owned the phone.
I've had LP on with full charge all the way down to 30% +/- and still ran like a champ.
Currently on Cognition beta 9 - still the same story.
I truly think you have a lemon phone. And I just flashed and haven't tweaked any of the default settings that are "out of the box" after a flash... so I assume they are all default.
The only FC/shutdown issues I've had recently were with Cognition beta 7 and advanced audio manager. I removed it and *poof* no more FC's. And since I was never that concerned with my sound settings (it's on vibrate 99% of the time anyways due to work environment and a lil' guy) I didn't care.
I'd look into getting a refurb - or flashing to Cognition's latest and greatest (hmm... well I would wait for 9.2 as he is having some "growing pains" with his new kernel) and see how it goes then. Can always Odin back to stock if needed.

[MOD]Stay Awake for eb16

Here you go! This will give you back the option in Applications\Development have your phone stay awake while it's pluged in.
[Insert Disclaimer Here]
Blah Blah Blah
Mess your phone up don't come crying! Do at own risk.
You've been told.
Thanks to Phidelt82 for putting up with me.
Stay Awake Mod
http://db.tt/2r3LTH4
Don't forget to hit that thank button if you like this.
Nice! Would this work on the showcase?
Sent from my SCH-I500 using XDA App
donno. I will talk with phidelt and i will see if it will.
Very cool. If you want to play it safe, download the StayAwake app from the Market. Doesn't give you the option back in the menus, but it allows you to choose in the app whether or not to keep the screen on when plugged in or not, or to keep the screen on all the time (don't know why you'd do that, the battery would be dead pretty fast).
ganzhimself said:
Very cool. If you want to play it safe, download the StayAwake app from the Market. Doesn't give you the option back in the menus, but it allows you to choose in the app whether or not to keep the screen on when plugged in or not, or to keep the screen on all the time (don't know why you'd do that, the battery would be dead pretty fast).
Click to expand...
Click to collapse
I (and a few others) have already tried this, so if you don't want an extra app taking up memory - use this mod, it works great .
ganzhimself said:
Very cool. If you want to play it safe, download the StayAwake app from the Market. Doesn't give you the option back in the menus, but it allows you to choose in the app whether or not to keep the screen on when plugged in or not, or to keep the screen on all the time (don't know why you'd do that, the battery would be dead pretty fast).
Click to expand...
Click to collapse
It's something that was previously there and was removed. He just added it back in. The reason a developer, or anyone, would want to do this is because while you have your phone plugged in to the USB cable and are working with it, your computer, and many other things at once, it gets annoying having to keep turning the screen back on and unlocking your phone.
As for killing your battery, if it's plugged in to the USB port and charging but still going dead, I believe you have a problem with your phone. While charging, you should never lose battery power..... that's why it's called charging.
The app has the option to keep the screen all the time, regardless of it being on the charger as well as just keeping it on while on the charger. What I meant is that if you have the screen on all the time and aren't charging the phone the battery is going to die in a pretty short amount of time. I really missed that option in FroYo, so I'll probably flash this when I have a chance to. Thanks to everyone, it's really nice to get this back in the OS options.
This is a handy thing for those who use there phone as an alarm clock. Screen stays on so when you wake up you just have to look at it to get the time vs. Looking for it an fumbling for the lock button when you half a sleep.
___________________________________
Just when you think you have it idiot proof, they come out with a better idiot.
It doesn't seem like anyone else has had this issue but when I flashed this mod I could no longer access any of the settings menus they all would cause a FC upon opening. I restored a backup from before I flashed this mod and I could once again access settings.
Swyped using USCC Mesmerize
did you guys base this off the mod adrynalyne did for the fascinate?
Really someone did this for the fascinate? I wish I knew that.
___________________________________
Just when you think you have it idiot proof, they come out with a better idiot.
ehoba said:
Really someone did this for the fascinate? I wish I knew that.
___________________________________
Just when you think you have it idiot proof, they come out with a better idiot.
Click to expand...
Click to collapse
just out of curiousity what had to be edited to get this to work?
Had to edit the development slalom in the settings apk. I cussed the code from our 2.1 version to add it back in.
___________________________________
Just when you think you have it idiot proof, they come out with a better idiot.
will this get a EC10 revival?
Yes
___________________________________
Just when you think you have it idiot proof, they come out with a better idiot.

[Q] DIP Switch

Does anyone know what the DIP switch located in the transformer is for? The only thing I found is a post mentioning a different wifi setup.
My experience messing with it is that the transformer won't turn on when it is in the up position unless the tablet is plugged into its charger.
Please see post 7 for the issue I am experiencing and how the Dip switch is involved.
thatton13 said:
Does anyone know what the DIP switch located in the transformer is for? The only thing I found is a post mentioning a different wifi setup.
My experiance messing with it is that the transformer won't turn on when it is in the up position unless the tablet is plugged into its charger.
Click to expand...
Click to collapse
Search Been discussed before
I did search, here and Google many times over the past month. Only found 1 post with the info that I mentioned.
"The only thing I found is a post mentioning a different wifi setup"
If I overlooked something I would appreciate a push in the rite direction. Or is that all the info there is?
Off the top of my head, I thought it was the switch that disables the battery? Somewhere, in a galaxy far, far away, there is a thread, and buried deep in that that thread, someone speculated that the ASUS techs use that switch to shunt the battery when they service bricked TFs so that the flux capacitor doesn't blow up and send us all back to the 80s. OK, maybe that's a bit of a strech, but I do think it has something to do with the battery.
gee one said:
Off the top of my head, I thought it was the switch that disables the battery? Somewhere, in a galaxy far, far away, there is a thread, and buried deep in that that thread, someone speculated that the ASUS techs use that switch to shunt the battery when they service bricked TFs so that the flux capacitor doesn't blow up and send us all back to the 80s. OK, maybe that's a bit of a strech, but I do think it has something to do with the battery.
Click to expand...
Click to collapse
While the OP might not...I found your response highly amusing
Post 90-94
http://forum.xda-developers.com/showthread.php?p=16812367#post16812367
Its use is still unknown, but at least the post confirms the behavior that the OP is seeing.
gee one said:
Off the top of my head, I thought it was the switch that disables the battery? Somewhere, in a galaxy far, far away, there is a thread, and buried deep in that that thread, someone speculated that the ASUS techs use that switch to shunt the battery when they service bricked TFs so that the flux capacitor doesn't blow up and send us all back to the 80s. OK, maybe that's a bit of a strech, but I do think it has something to do with the battery.
Click to expand...
Click to collapse
Nice! Especially the Back to the Future reference. Allow me to explain my situation and why I am so interested in that tiny switch.
I purchased my Transformer from Newegg back in July or August. It was an open box and I saved around $150 because of that. Unfortunately that means it only had a 1 month warranty, this brings us to my problem. It runs great but every once in a while a lot of the apps, including the browser, will force close. Also if I go in to settings once this problem starts and shut off the WiFi and then try to turn it back on it just says error. Trying to turn on Bluetooth also does not work.
The solution is to reboot, however, it will only run for a short while before the problem returns. I have tried the stock rom rooted and unrooted, I have tried various roms, revolution, prime, revolver. After flashing a rom or doing a factory reset the transformer will run for around 12 hours without the above mentioned problem but it always comes back and it happens more and more frequently until I do a factory reset.
I have tried countless things. Various roms as mentioned, factory resets, freezing as much as I can using titanium backup, not adding a Google account, turning off gps, different wireless networks, assigning a static ip address, using ExtSd2InternalSd v2.1 to install apps on an sd card. All of this with no success.
Enter that dip switch. I decided since my warranty was over I would open it up and do some poking around. I discovered if I put that switch in the up position and boot the transformer with it plugged into the charger it runs perfectly stable. The issue is gone. only problem is that I can only use it plugged in. This situation lead me to the conclusion that it is a power supply issue, maybe a defective battery (Not getting the full 1.21 gigawatts . So.... I switched out the battery in my dock with the one in the transformer and put the dip switch in its original down position..... No Luck, the problem persisted. Return the switch to up and plug it in, runs great.
Anyone have an idea?
How does it run while the switch is down (in the crappy position) and plugged in?
gee one said:
How does it run while the switch is down (in the crappy position) and plugged in?
Click to expand...
Click to collapse
The problem is still there. I even tried it in the down position with the battery disconnected and the transformer plugged into the charger but the problem continued.
I guess it could be a power/hardware issue or maybe a sleep/software issue. Perhaps it doesn't sleep while it's plugged in?
Regardless, it's quite an interesting problem.
gee one, thanks for your help. Maybe someone will come up with a fresh idea, I have tried most of what I can think of.
I might try the dual boot Ubuntu thing to see if I have the problem in Ubuntu. I figure that mite help narrow down if it is a software or hardware problem. I lean towards hardware because I have not been able to find others with this issue. Then again, maybe others that have had this problem had a warranty and returned it for an exchange.
gee one said:
Perhaps it doesn't sleep while it's plugged in?
Click to expand...
Click to collapse
Forgot to mention, I tried setting the screen to never shut off in hopes that it would prevent the transformer from sleeping. Not sure if there is another way to prevent it from sleeping? Whatever the case leaving the screen on did not prevent the problem from surfacing.
Install ROM Manager and tell it to Fix Permissions?
I've had extensive FCs on some devices I've rooted and fixing the permissions has helped.
Col.Kernel said:
Install ROM Manager and tell it to Fix Permissions?
I've had extensive FCs on some devices I've rooted and fixing the permissions has helped.
Click to expand...
Click to collapse
Thanks for the suggestion. Unfortunately I have cwm installed and have ran fix permissions and while it did help with some of the apps force closing it did not fix my problem.
I was about to ask where this switch was at because I've never seen it, then I read that it's inside the unit. I have no reason to crack this bad boy open yet so that's why I had no idea about it.
It is a battery kill switch, makes it easier to work on without blowing the **** out of the unit by bridging the wrong points on the board for what ever reason. basically with the switch up it is a "service mode"
Need Help with ASUS TF101 back light Out . ! An dip witch . ?
So did u ever find out what the Dip Switch was my friend . ? I'm working on the same unit as this at the min with the back light out so Screen is Dark But it works sound shining a Torch on it, . ? Fing is I'm a Self Tougt Tablet fixer an not bad at it, . But this 1 is full of stuff I've never seen before lol . So im looking to see if any 1 can shed some light on this . lol . ( sorry for the pun there ) . & To help me get this back light for the screen working again on this TF101, . ! An then I find this dip Switch Fing an a Small battery like a Com's battery in a lap top that I've Never seen in a tablet before, . ? So if u can help or any 1 else i would be so Greatfull . Nice 1 . DAY . ! But what is this DIP SWITCH 4 . . ?

Atrix 2 dying in sleep (freezing)

Hi all
Sometimes, my Atrix 2 will just freeze when the screen is off, and obviously won't come back on until the battery is pulled and reinserted. (draining it at the same time). It seems to have happened the most when airplane mode was turned on.
I'm afraid all this battery pulling will make the cover loose.
Does it happen with anyone of you?
thanks
EDIT: I'm on 2.3.6 stock, non root.
thenext1 said:
Hi all
Sometimes, my Atrix 2 will just freeze when the screen is off, and obviously won't come back on until the battery is pulled and reinserted. (draining it at the same time). It seems to have happened the most when airplane mode was turned on.
I'm afraid all this battery pulling will make the cover loose.
Does it happen with anyone of you?
thanks
EDIT: I'm on 2.3.6 stock, non root.
Click to expand...
Click to collapse
I have never experienced such a problem... So it just freezes while it sleeping? I have one idea but it's kind of stupid, there is an option under display, that says lock in pocket. Try unchecking that, I've had other people tell me that their phone freezes up afterwards...
You might have to do a warranty exchange.
Sent from my MB865 using xda premium
tmease1 said:
You might have to do a warranty exchange.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
I've written "drain" but it's not much of a drain - from 100 to 60% in a whole night. A true drain would be with the phone going from full to empty in a couple hours and getting very hot in the process.
I think the phone locks up for some reason during sleep and the cpu never goes into low power mode. As far as I can remember, this has happened only when it was bedtime, with the phone already put in airplane mode, and never in the long standby hours of the day while I work.
I hope this has something to do with software, and not hardware.
(A warranty replacement is out of question, as I'm not from the US...)
I'll try posting in the motorola forum, too.
100-60 overnight is a bit on the high side for drain if you are not using the phone. I would do a warranty swap.
thenext1 said:
I've written "drain" but it's not much of a drain - from 100 to 60% in a whole night. A true drain would be with the phone going from full to empty in a couple hours and getting very hot in the process.
I think the phone locks up for some reason during sleep and the cpu never goes into low power mode. As far as I can remember, this has happened only when it was bedtime, with the phone already put in airplane mode, and never in the long standby hours of the day while I work.
I hope this has something to do with software, and not hardware.
(A warranty replacement is out of question, as I'm not from the US...)
I'll try posting in the motorola forum, too.
Click to expand...
Click to collapse
It's probably something to do with the CPU govener. Try rooting, install bootstrap, then flashing the deodexed version of 2.3.6 found here. Just be sure to flash as a backup by placing it in \sdcard\clockworkmod\backup\. Select restore in clockwork and it should be there.
See if that gets rid of the problem You don't mid rooting right
Yes I mind rooting! Sorry!
I was just seeking for your experience, to know if you did by chance notice this behaviour/glitch... you keep telling me to do an exchange but it's obvious it's not an option for me, as you can see from the flag under my user name. Otherwise I would have got me a new atrix already. (Because of other minor annoyances)
I once had an acer liquid that started getting nuclear-fusion-hot and discharged in 2 hours each time, without the software taking a hit. Now that was hardware related.
As to my atrix2, I am sure it's not hardware related, because it happens only sometimes and in certain circumstances. One time, I turned it off and back on 5 secs after and it was already frozen. No way, we're not talking of hardware fault here.
Thats major drain overnight! I leave my phone on overnight and generally get about 1% drain per hour.
Sent from my MB865 using XDA App
WTF, either I can't speak my mind, or you don't read my posts!
It's not that I get a 40% drain every night. In fact I got it only once, last night, when I decided to leave the phone in deep coma after I found it unresponsive after just a few minutes it was turned off and in airplane mode (the time of brushing teeth and coming back to bed, FYI). In that circumstance I got the 40% drain, but otherwise i get a normal 5% drain like yours.
This thread is not on the battery drain, but on finding what causes the phone freezing while screen-off.
Thank you.
I have never heard of this happening on the A2.
When the phone freezes up, does it get hot at all? It's possible that your problem is hardware-related, but the only way to be sure of that is to make sure that it's not software-related...
It may possibly be one of the apps that you're using. If you're OK with it, then I highly recommend to begin with a hard reset. I write down all of the apps that I know I will need and then I reinstall them after the reset, then if I realize I need to use an app I don't have I install it.
Another thing to try is flashing the fxz. This will clear every single bit of data on your phone and reinstall stock 2.3.4. Then you can update to 2.3.6 and gradually regain your (necessary) apps as with the hard reset.
Sounds kinda like these reported bugs below:
http://forum.xda-developers.com/showpost.php?p=21817704&postcount=36
and
http://forum.xda-developers.com/showpost.php?p=21819590&postcount=37
thenext1 said:
WTF, either I can't speak my mind, or you don't read my posts!
Click to expand...
Click to collapse
You must not be able to communicate your thoughts very well then cause the post I responded to didn't make any mention of the fact it only happened once. And your first post said it happens "sometimes", meaning more than once. Sorry guy, i'm not a mind reader.
thenext1 said:
I've written "drain" but it's not much of a drain - from 100 to 60% in a whole night.
Click to expand...
Click to collapse
thenext1 said:
This thread is not on the battery drain, but on finding what causes the phone freezing while screen-off.
Click to expand...
Click to collapse
I know what the thread is about, but you chose to share your experience with the battery draining issue not only in the first post but also in the once I quoted above which led me to believe this thread was about that as well so that's what I chose to respond to.
Thanks
kirkgbr said:
Sounds kinda like these reported bugs below:
http://forum.xda-developers.com/showpost.php?p=21817704&postcount=36
and
http://forum.xda-developers.com/showpost.php?p=21819590&postcount=37
Click to expand...
Click to collapse
Yeah, sounds like that. What did you do to overcome it?
Do you use airplane mode at all?
916x10 said:
You must not be able to communicate your thoughts very well then cause the post I responded to didn't make any mention of the fact it only happened once. And your first post said it happens "sometimes", meaning more than once. Sorry guy, i'm not a mind reader.
I know what the thread is about, but you chose to share your experience with the battery draining issue not only in the first post but also in the once I quoted above which led me to believe this thread was about that as well so that's what I chose to respond to.
Thanks
Click to expand...
Click to collapse
I think I made sufficiently clear that the draining was secondary to the freezing issue, and, in turn, that the freezing issue happened only sometimes... which, in my (surely flawed) understanding, is more often not the case than it is.
Anyways no problem man!
thenext1 said:
Yeah, sounds like that. What did you do to overcome it?
Do you use airplane mode at all?
Click to expand...
Click to collapse
Not sure what fixed it. I have done a couple things since then.
1.) Rooted <- not sure how this could fix a problem like this.
2.) Froze several apps with Titanium Backup. <- This one makes the most sense.
I never use airplane mode.
The other user (dk-v1) says that his softkey lights come on while the screen stays black.
I don't remember about the lights, probably one time they turned on, but don't remember right now.
About the black screen, I'm not sure what he means, but mine stays black and with backlight off.
From reading the OP...I would suspect that it could be an app that is trying to sync while in airplane mode. I would try troubleshooting (uninstalling one by one to see if the problem goes away) apps that sync, preferably the ones you installed. But if it still persists do a factory reset and start over. Good luck man!!!
my wife actually started having this problem with her inspire recently. I tracked it down to the no led app she was using. deleted it and everything has been fine since. so your issues could most definitely be app related.
thenext1 said:
I think I made sufficiently clear that the draining was secondary to the freezing issue, and, in turn, that the freezing issue happened only sometimes... which, in my (surely flawed) understanding, is more often not the case than it is.
Anyways no problem man!
Click to expand...
Click to collapse
I never said it was the primary issue......u said this thread wasnt about the draining issue, but since u brought it up in your op and subsequent posts its clear it was an issue so when somebody responds to one of the issues you're having, don't be a douchebag about it by saying "thats not what this thread is about". Trying to insult me by insenuating I don't read before I respond is no way to show appreciation for my attempt at helping you. It seemed you were under the impression that a 40% discharge overnight wasnt a major drain so I shared with you my experience thinking it would put yours into perspective.
But apparently explaining my thought process and posting your own quotes for you to see how/why I'd think what I thought isnt enough to knock you off your high horse so I'm over it, carry on. If you feel the need to respond any further you can pm me, no sense cluttering the thread any further.
Sent from my MB865 using XDA App

Issues with my S3

So Im a little new to this, and hopefully I won't be asking things that can be easily found, since i did try looking for answers..after having my verizon s3 for over a month now (still stock), im having a few different issues/annoyances, and can't figure out how best to resolve them.
1) Whenever i restart my phone, i get voicemail notifications, even though I have no new notifications.Ive seen a few different solutions for it, namely leaving yourself a voicemail, then deleting it and it should make it go away...but it doesnt. i can only get a temporary fix, which is to go and force stop the Phone application, but next time my phone restarts the same issue happens again.
2) a few times my phone will hotboot..or atleast thats what i think its called. basically the phone will freeze, then after a minute or two it will go back to the lock screen..but if i leave it alone, or if i try to run anything, it will again freeze and go to the lock screen. this even happens when i restart my phone. the way around it i found is to unlock the phone, then immediately turn off the screen. after 15-20 seconds, i can turn the screen on again and it will work fine. i read some topics on this but they seem to be random occurrences, and i didnt really see anyone saying it happens on every startup..
3) android_system/gsiff_daemon killing me battery- so over the last week ive seen that this is really killing my battery. it always takes up about 50% of my battery, no matter what i do.it also seems to cause the phone to get really hot. the topic i read below, it seems like a root cause isn't found yet, and the only way to resolve it without rooting is to restart your phone, but for me it seems so always come back at the top..
http://forum.xda-developers.com/showthread.php?t=1755180
i'm wondering if rooting and unlocking the bootloader will help at all. the last time i rooted a phone was like 2-3 years ago with my incredible, so im a little cautious about doing it and accidently bricking my phone. i was going to follow section 2 of this guide, there shouldnt be too much of a risk of it going wrong right? http://forum.xda-developers.com/showthread.php?t=1762709
y2jasper said:
So Im a little new to this, and hopefully I won't be asking things that can be easily found, since i did try looking for answers..after having my verizon s3 for over a month now (still stock), im having a few different issues/annoyances, and can't figure out how best to resolve them.
1) Whenever i restart my phone, i get voicemail notifications, even though I have no new notifications.Ive seen a few different solutions for it, namely leaving yourself a voicemail, then deleting it and it should make it go away...but it doesnt. i can only get a temporary fix, which is to go and force stop the Phone application, but next time my phone restarts the same issue happens again.
2) a few times my phone will hotboot..or atleast thats what i think its called. basically the phone will freeze, then after a minute or two it will go back to the lock screen..but if i leave it alone, or if i try to run anything, it will again freeze and go to the lock screen. this even happens when i restart my phone. the way around it i found is to unlock the phone, then immediately turn off the screen. after 15-20 seconds, i can turn the screen on again and it will work fine. i read some topics on this but they seem to be random occurrences, and i didnt really see anyone saying it happens on every startup..
3) android_system/gsiff_daemon killing me battery- so over the last week ive seen that this is really killing my battery. it always takes up about 50% of my battery, no matter what i do.it also seems to cause the phone to get really hot. the topic i read below, it seems like a root cause isn't found yet, and the only way to resolve it without rooting is to restart your phone, but for me it seems so always come back at the top..
http://forum.xda-developers.com/showthread.php?t=1755180
i'm wondering if rooting and unlocking the bootloader will help at all. the last time i rooted a phone was like 2-3 years ago with my incredible, so im a little cautious about doing it and accidently bricking my phone. i was going to follow section 2 of this guide, there shouldnt be too much of a risk of it going wrong right? http://forum.xda-developers.com/showthread.php?t=1762709
Click to expand...
Click to collapse
I would start with a factory reset and see if that solves your problems. keep in mind it will erase your apps and settings. VOL+/HOME/POWER
i was hoping to avoid factory reset since i didnt want to reset up my screens and apps, and also for the voicemail and gsif_daemon issue from what i read it keeps coming back. but if thats the best option i guess i have to suck it up and do it then
Root and unlock BL won't fix problems. That will only allow you to modify your phone more. I think you have to bite the bullet on this one. Test it out good before you install all your apps if you reset.
Sent from my SCH-I535 using xda app-developers app
You could just have some rogue apps. Many apps fail miserably just going from ICS to JB. I hated TouchWiz. Rooting and Unlocking Bootloader was the best thing that has happened to my S3. Rooting is very safe and its very easy to got back to stock. My battery was terrible on stock. 4G is going to eat your battery up quickly as opposed to just Wifi. All the alternative launchers can backup you home screen (Apex/Nova etc) and all your apps should be backed up in Googles cloud should quickly get pulled back down after a factory reset or ROM install
kanc3r said:
You could just have some rogue apps. Many apps fail miserably just going from ICS to JB. I hated TouchWiz. Rooting and Unlocking Bootloader was the best thing that has happened to my S3. Rooting is very safe and its very easy to got back to stock. My battery was terrible on stock. 4G is going to eat your battery up quickly as opposed to just Wifi. All the alternative launchers can backup you home screen (Apex/Nova etc) and all your apps should be backed up in Googles cloud should quickly get pulled back down after a factory reset or ROM install
Click to expand...
Click to collapse
hm ok. 4g isn't really the cause. in the area where my apartment is, 4g isn't even available yet, i only get a chance to use 4g on weekends when i come visit family/friends. otherwise i use the "phone info" app to turn 4g off. also my voicemail issue is resolved now, i messed around a bit more between voicemail and google voice and finally found the rogue message that was left. i'm thinking if i root and unlock, i can at the very least install a different kernal to improve battery life, to possible negate the gsiff_daemon issue.

Categories

Resources