Related
Random shut down solution! At least for me.
My phone shuts down pretty much 2-5 times a day since i got it. No matter what I do to it. But I tried the app, load monitor and enabled WAKE LOCK and my phone hasnt rebooted in 4 days!
Anyone else had similar experience.
Sent from my SAMSUNG-SGH-I897 using XDA App
Umm, not meant in an asshat way at all man, but your real solution is to take that sucker back. I wouldn't put up with that at all. Bad phone. Just my opinion.
From a phone on an app
I have to agree with the post above mine. I believe it's a hardware issue and that you should return it for another one. I have two captivates and neither I've of them have ever had the random shutdown issue.
Truth is, the phone is bad. Ask for a warranty replacement. I went through 2 phones until I got a good one with no issues. A perfectly good working phone should never randomly shut off as mine were doing before (4-10 times a day) Even setting Set-CPU to 1000mhz 100% of the time didn't fix the other phones I had. Hell, even leaving the screen on the entire time one of them still shut off once.
Others have found that the "wake lock fix" has not worked (although it initially seemed promising). If your shutdowns recur, exchange the unit. That's been the only remedy to date.
Did you have set cpu installed? That's what happened to me after installing set cpu. Sometimes it would lock up after the screen went off & sometimes it would just reboot randomly. I got around this by setting the min clock speed to 200mhz. I think set cpu sometimes undervolts the cpu when scaling especially at 100mhz & at 1000mhz when the screen is off. If it did that stock then I would definitely return that pos! Wake lock will kill your battery life.
Sent from my SAMSUNG-SGH-I897 using XDA App
Well we will see. I was in the process of a rma and just got the phone last night.
I see if the new one has any issues. By the way this will be my 4 th phone(3 through the first month, this one through rma). So the get another phone idea kind of sucks.
Just a curser glance at the back of the rma phone and I can see its different. So maybe I'll get lucky on it.
Sent from my SAMSUNG-SGH-I897 using XDA App
. .
Same here, I'm in Australia, I bought the phone from the US, It used to shutdown 3 - 5 times a day, especially when it's fully charged. Wiped the phone (Internal and external) and now it's solid stable. no special apps or settings or whatsoever. It's a little bit weird though.
I think the problem may be from the phones overcharging. Mine was brand new and I left it on the charger overnight then took it off the charger in the morning and when I came home from work it was powered off. It may be a safety feature built into the phone and not a defect. I had it happen to me twice when I didn't take it to work with me after charging it all night the night before.
Sent from my SAMSUNG-SGH-I897 using XDA App
I leave mine plugged in all the time overnight and it has Never booted off
Sent from my SAMSUNG-SGH-I897 using Tapatalk
galaxyjeff said:
I think the problem may be from the phones overcharging. Mine was brand new and I left it on the charger overnight then took it off the charger in the morning and when I came home from work it was powered off. It may be a safety feature built into the phone and not a defect. I had it happen to me twice when I didn't take it to work with me after charging it all night the night before.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I thought the same, but last night I forgot it on the charger with no problems at all, No shutdowns... Strange...
It happens to my Samsung S Vibrant and I *think* I can reliably reproduce the issue, at least on my phone.
Steps:
1. Go to a spot where you know it has failed, for me this is my office because it has bad reception and it seems to only shutdown for me when there is bad reception.
2. Make sure 3G is turned on and open an application that uses data.
3. Wait for the phone to sleep, do not hit the power button or anything to make it sleep (not sure if this step matters)
4. Wait ~30 mins without touching the phone (You can play music with it while this is happening if you want, the music will stop to let you know it's failed)
5. Try to wake up your phone, it is now dead.
I'm not sure this will work for everyone but last night I could reproduce 3 shutdowns in an hour and a half. And reproduced about 7 shutdowns yesterday when my phone only usually shuts down ~2 times a day.
I'm testing out all kinds of software permutations (disabling stuff, installing things like Captivate Keep Alive). Nothing has worked so far, my guess right now is that the problem lies in the Pattern Unlock feature so I have disabled it, I read that on a forum somewhere.
My guess is that if you have too much running in the background it might take up too much cpu or ram so that when the phone tries to come out of sleep it can't get enough CPU power to come out of sleep and therefore gets stuck in a kind of limbo. This theory could then be releated to the SetCPU problem when you set the CPU too low when it sleeps the issue occurs.
Moral of the storey is I have no idea what's going on, but please post if this works or doesn't work. Maybe it will shed some light on the issue, or you can tell me I'm wrong so I can give up. Let me know if you have Pattern Unlock enabled...
Luckily I'm not past the 30 day mark and I'm exchanging for a new Vibrant tonight. Wish me luck!
UPDATE: It's not the fault of Pattern Unlock, just reproduced the issue with it turned off.
UPDATE #2: Got my second Vibrant, just reproduced the issue within 30 mins of getting into work in the morning.
My Captivate used to shut off once every 2 weeks. Now it's doing it 4 times a day. However, I just found this app:
http://uk.androlib.com/android.application.org-bluesteel-cka-qxnim.aspx
Looks promising. I hope this works.
My wife's stock Captivate has been doing this for a week or two (our phones are about 6 weeks old). My rooted Captivate has -not- been doing it. We both have the same "plug it in all night" charging pattern. Hers will be going back shortly.
Jack45 said:
Others have found that the "wake lock fix" has not worked (although it initially seemed promising). If your shutdowns recur, exchange the unit. That's been the only remedy to date.
Click to expand...
Click to collapse
Tha'ts not true.
My phone was working fine. Then I rooted it. Then I started sideloading bunch of apps. Randon shutdown started to happen. I started tracing back and deleted apps one by one. Didn't work. Replacing the phone was out of the question because I live in Canada and bought the AT&T phone cash off a seller.
SOLUTION:
if you have had SetCPU (or overclock app) and had it to anything to your phone, this is what you got to do.
Run the SetCPu again, and make sure that you do Max 200mhz and Min 200mhz.
Reboot the phone.
Then go into SetCPU, disable autodetect. Then uninstall app.
No more random shutdowns.
It is NOT a hardware issue.
I can confirm that the App stops my phone from shutting down.. unfortunately I have to set it to 65% charge for it to work (whereas others can leave it on default 80%).
Found my issue, it was happening when my phone was jumping between the 850 mhz band and the 1900 mhz band. It would freeze and only happen in areas of bad signal. Locked it on to the 850 mhz band and havent had a freeze since.
100 hours of uptime and counting
http://forum.xda-developers.com/showpost.php?p=8612667&postcount=386
I have also heard that some phones experience the issue when fully charged and that putting a wake lock on your phone with captivate keep alive will solve the problem. These are two independant issues.
i'm not really that knowledgeable about how the phone interacts with different bands, but i'm trying to fix this problem as well and i'll try anything. are there any side/adverse affects to locking it onto a single band?
Has anyone tried removing the sim? to see if it still turns off?
The problem im having is when its near full and goes to sleep i need to turn it back on (like it shuts off) but i tried removing the sim and has not had this problem
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.
Hey everyone!
My problem with random shut-downs on the captivate became unbearable, and I kept searching through threads for a solution, and I finally found this:
http://uk.androlib.com/android.application.org-bluesteel-cka-qxnim.aspx
This app doesn't let your CPU completely turn off when on standby.
I used it for a whole day and no shut-downs.
Usually, I'd get at LEAST 3 shutdowns a day.
I hope this helped you all.
What have you done to be getting random shutdowns? I've flashed multiple roms and used modded framework files and still I never get a random shutdown.
NeoXerO said:
Hey everyone!
My problem with random shut-downs on the captivate became unbearable, and I kept searching through threads for a solution, and I finally found this:
http://uk.androlib.com/android.application.org-bluesteel-cka-qxnim.aspx
This app doesn't let your CPU completely turn off when on standby.
I used it for a whole day and no shut-downs.
Usually, I'd get at LEAST 3 shutdowns a day.
I hope this helped you all.
Click to expand...
Click to collapse
Not bad. Wouldn't you want to have the convenience of NOT worrying about random shut downs (with or without) the app tho? I guess its just me, but those things would really irk me. lol
cappysw10 said:
What have you done to be getting random shutdowns? I've flashed multiple roms and used modded framework files and still I never get a random shutdown.
Click to expand...
Click to collapse
It's just pure luck. Some phones will randomly shutdown regardless what ROM you use. Some don't.
The only true solution so far is get a warranty replacement, or maybe couple replacements (the refurbs you get back may still suffer the same problem). Samsung itself has no clue what's the cause of it yet last time I checked.
NeoXerO said:
Hey everyone!
My problem with random shut-downs on the captivate became unbearable, and I kept searching through threads for a solution, and I finally found this:
http://uk.androlib.com/android.application.org-bluesteel-cka-qxnim.aspx
This app doesn't let your CPU completely turn off when on standby.
I used it for a whole day and no shut-downs.
Usually, I'd get at LEAST 3 shutdowns a day.
I hope this helped you all.
Click to expand...
Click to collapse
CKA is a possible solution for one of the anomalies that causes shutdowns. For additional information, use the forum's "Search" function and look for "Captivate Keep Alive."
i just starting to get shutdown once a day started 4 days ago. i trying to uninstall 1 app at a time to see what happen. just uninstall dolphin browser v4.0.
Jack45 said:
CKA is a possible solution for one of the anomalies that causes shutdowns. For additional information, use the forum's "Search" function and look for "Captivate Keep Alive."
Click to expand...
Click to collapse
Really? Well, this worked for me, and I had it pretty bad with those random shutdowns (even happened to me on stock 2.1 before flashing).
I think some people might be getting random shutdowns due to certain apps.
I 2nd that. I installed Keep Alive because my would shut down once a day after full charge but only if GPS is on. Mine doesn't shut down if GPS is off. Now it's been 3 days without any shut down and I leave GPS on continuously.
my phone shut down (1 time) daily, and i'm unable to reproduce the shutdown. maybe it' a memory leaks, it shuts down when it runs out of ram. going to reboot my phone (1 time) daily to see what happens...
NeoXerO said:
Really? Well, this worked for me, and I had it pretty bad with those random shutdowns (even happened to me on stock 2.1 before flashing).
I think some people might be getting random shutdowns due to certain apps.
Click to expand...
Click to collapse
I concur, I never had any shutdowns until I went to cog 7... And for the first week I didn't have any shutdowns, only after installing apps did this problem start. So I think you are correct that out has something to do with certain apps. Probably an app that is not fully compatable with android 2.2... I just wish I could figure out which app is causing this issue.
Sent from my SAMSUNG-SGH-I897 using XDA App
My phone keeps shutting off also. At first thought it was software, but even with a clean install of 2.1 with Odin and nothing added to it, it still did it. Then I thought it was the SD card, but still not it. I started noticing a pattern with it doing fine for 11-16 hours with a full charge depending on how much I used it, but it eventually shuts off. Every time I turned it back on, the battery is at <65%. I completely drained the battery last night and charged it back up and now it's doing it at 70%.
Anyone in this thread that has had at least 1 random shut down, or more, should look into a warranty replacement. A perfectly good working phone shouldn't shut down for the hell of it or because it "runs out of memory"
I went through this before and messed with the phone for a few days taking off apps, re-flashing etc... ultimately the problem went away when I simply just asked for a replacement unit.
I understand that there are a couple of topics opened for this but I wanted to have a new one with the title showing that a solution has been found as I want to help other who are experiencing the problem.
I'm not sure if this would resolve the issue for you but it did for me so please don't blame me if it didn't work for you, I say this because the solution requires an install of a paid app.
So I've had my transformer for 2 weeks and the SOD has been happening since day 1, it would happen every time I left my transformer asleep for more than 2-10 minutes (WIFI on or off). I've tried everything but could not resolve the issue. The only time the SOD didn't happen is when I had it plugged into the charger.
Solution: WidgetLocker, it's an SOD killer
All I did was install it and left everything as is, I also made sure that the stock lock screen is disabled.
I dont think it's widget locker that fixed the problem its disabling the stock lock screen. I had the sleep issue the first few days I had the xformer but after disblong the lock screen it went away.
Sent from my Transformer TF101 using XDA Premium App
I had SOD issues when I had Juice Defender installed. I knew it was causing the problem because it started happening right after it was installed. Haven't had one SOD occurrence since I removed it.
I had te stock lock screen disabled for days but the problem never went away until I installed widgetlocker.
I don't want to be a Debbie Downer, but I think you'll find the SOD will reappear when you least expect it. Mine didn't do it for well over a week after I fiddled with all the suggestions offered on this forum, and now it's just as random as ever. I hope 3.1 fixes this, but it sounds a lot like a Transformer issue rather than a HC issue, since you don't hear the Xoom or Iconia owners complaining about the same thing.
Anyone else tried this?
Thanks
the SoD is probably caused by the big frequency/voltage jump when you wake the system up. This is probably what's freezing the system. Someone with a rooted transformer that's having the issues should get the netformer kernel and sit minimum frequency to something higher (400~600 MHz) and see if they still get the problem.
FYI: We had the same problem with the HTC hero when some hero's would lock up when asleep when you set the minimum frequency too low which meant they made a big frequency jump when the screen got turned on.
I've got the acer and this happens all the time with it. I notice it also will randomly turn the screen on just sitting there. Wonder if it's just a 3.0 issue and not something just the asus has.
L0$t$0ul said:
I've got the acer and this happens all the time with it. I notice it also will randomly turn the screen on just sitting there. Wonder if it's just a 3.0 issue and not something just the asus has.
Click to expand...
Click to collapse
I don't think we've had the screen waking up issue.
It's been over 24 hours and not a single SOD since installing WL. I used to get it SOD every time I left my ASUS unused for few minutes.
If I use dock I never have that problem only without dock.
Glad to hear the wake issue isn't happening here. It's really annoying. Just had my acer not wake up again though. Happens at least once a day.
seshmaru said:
I don't think we've had the screen waking up issue.
Click to expand...
Click to collapse
Sorry bit I've only just found this thread. I too am suffering with the SOD after 5-10 mins of standby. But I also have the random "waking up" when in standby -sometimes after a couple of seconds, sometimes after a couple of minutes. Seems you can't rely on it doing what it is supposed to do i.e. sleep until woken !
steftymo said:
Sorry bit I've only just found this thread. I too am suffering with the SOD after 5-10 mins of standby. But I also have the random "waking up" when in standby -sometimes after a couple of seconds, sometimes after a couple of minutes. Seems you can't rely on it doing what it is supposed to do i.e. sleep until woken !
Click to expand...
Click to collapse
3.1 update fixed this for me and no Widgetlocker is needed.
MODS : Please move to GENERAL SECTION. Thanks.
Hi, starting this thread to roll up on bugs reporting. Will compile all your reports, verify them and inform Samsung about it and hopeful for a fix.
Sent from my GT-P6200 using XDA App
1) Sleep of Death (two users)
2) Floating Dialer popped up without being asked for... (two user + myself)
sleep of death. Its rare for me but still annoying when it happens. Plus, sometimes when I have the browser set to quick menu when you drag from off screen for the toolbar. The right side will bring up the dial for a second and disappear. Other than that awesome tab!
I get randon reboots and shutdowns, at least one of each everyday, usually right after I first turn it on for the day. It also sometimes is a bugger to wake up, sleep of death? I thought it might be powersaver mode causing me problems but they persist after I turned it off.
kzoodroid said:
I get randon reboots and shutdowns, at least one of each everyday, usually right after I first turn it on for the day. It also sometimes is a bugger to wake up, sleep of death? I thought it might be powersaver mode causing me problems but they persist after I turned it off.
Click to expand...
Click to collapse
I do not have this issue at all.
Try to flash the original firmware and hard reset. Do not root or install apps. Run it for a couple of days and see the result.
But I do believe it can be related to the motherboard.
Example, my original P1000 tablet was superb, no hangs or SODs... but I bricked it (excessive tinkering) and Samsung changed the motherboard. Since then, I started to experience hangs and a few SODs... sold it off...
PandaHandz said:
sleep of death. Its rare for me but still annoying when it happens. Plus, sometimes when I have the browser set to quick menu when you drag from off screen for the toolbar. The right side will bring up the dial for a second and disappear. Other than that awesome tab!
Click to expand...
Click to collapse
happens a couple times a day to me.. I am getting tired of it for sure..
Not trying to be mean, but not development related. Should be just Q&A
Sent from my Insanity powered SGS2
I've been fortunate so far also but if I start to get SOD then I would root grab set cpu and raise your minimum to 400
Sent from my Nexus S using xda premium
sorry for not posting sooner, removed the Micro SD card and reinstalled everything, that was a week ago, not one single SOD or reboot.
Not sure what it means, but it could be looking for the SD to index or update files and not reading the card causing the reboot?
What do I know, it just could be luck, but worth a try.
Let me know how it works for you.