Database Develop

[SOLVED] Cyanogen shutting down by itself.

I was wondering if I was missing a post. I still get random Cyanogen Shut downs. I am using 4.2.13 after a wipe and still experience random shutdowns.
The phone just goes dark and I have to power it up again.
I have read some people attribute it to locked home screen and some people while using locale.
It is quite frustrating and I was wanting to know... if there isn't a fix, what Rom should I port back to. I need to clear this up because it gets aggravating missing calls.

Give superD 1.2 a try or even dwangs ROM they both are very speedy and well stable

Try re-flashing the rom, or you can try another rom as you said...i recommend Super D or WG Build....i myself use WG Build

You might be running out of system space.
Go to console:
$ su
# df
Check the Available next to /system. 28mb should be normal, but you could always apply the 10mb ramhack. Go with CFS for stability.

Can you recreate the scenario by which the phone will reboot on it's own and get a logcat?

No I cannot recreate it, it is very random. Afterwards I cannot logcat. I have tried wipe and reinstall of alot of his roms, all of them do the same thing.
I was hoping there was a fix because it is his rom I prefer.
I guess I will try another rom and maybe the problem will resolve itself.

Brutal-Force said:
No I cannot recreate it, it is very random. Afterwards I cannot logcat. I have tried wipe and reinstall of alot of his roms, all of them do the same thing.
I was hoping there was a fix because it is his rom I prefer.
I guess I will try another rom and maybe the problem will resolve itself.
Click to expand...
Click to collapse
Try Enoms rom if you tried Super D and WG-Build Y-2.6 with no success.
The problem you have is definitely weird.
I also suggest updating your Radio, Spl and RA Dream to the latest versions.
If possible try another microSD card preferably Class 6 to see if that fixes your problem.

I've been experiencing this same thing with random shut downs. I am running 4.2.13 also.
I have tried a wipe and re-install but the problem still exists.
There doesn't seem to be any rhyme or reason to it. The only thing I can say is that it always happens after the phone has been idle and when I go to pick it up it's powered down and I then need to power it back up.
It is very frustrating becuase you're never fully aware that the phone is off until you go to use it. I don't know if it's the ROM or some program that I've installed. I've been uninstalling all recent programs but so far the problem still exists. Perhaps I'll try one of the other recommended roms.

I have tried the stock rom and Dwangs rom, so I doubt its the ROM. Also I installed minimal applications and it still happens.
Its a toss-up between battery and phone. Although my battery is an extended battery, it can happen even when the battery is at 80%+ charge.
I called T-mo and they are going to swap out my phone. When I get it I will run the stock rom for a couple days with my Extended Battery. If it continues, I will put the stock battery back in it. Then I will go back and root it. If the problem comes back, then it has to be the rom.

Brutal-Force,
I'll eagerly wait your results. Unfortunately I purchased my G1 off of ebay a year ago so if it is the phone I'm out of luck.
Out of curiosity do you use Nitrodesk Touch down for Exchange? I've had some reboots right in the middle of synchronizing my email with this program.
Thanks

No I do not. As a matter of fact, I had uninstalled almost everything in an attempt to track down the culprit.
I really do think its gonna end up being the battery. Since the phone is not an option for you, I would recommend trying out a cheap 10 dollar battery off the internet. While I can't imagine why a charged battery would do this, I have noticed by looking at a friends G1 that the phone interprets batteries in different ways. In his phone his battery never showed below 90% even though after 10 hours it would run out of battery. As soon as he put in on the charger it showed 90%.

I to had purchased one of the extended batteries shortly after purchasing the phone. It has worked fine for just about a year but perhaps it is beginning to have problems. I'll dig out the original stock battery later today and try that for a day or so and see what happens.
Thanks

I have the same problem. My phone randomly restarts. It's more of an annoyance rather than a big problem, especially since it's almost always a restart and not a shutdown. If you guys do indeed find out it's the battery do post your findings here!
Thanks

I have exactly the same symptoms. Though before I saw this post I was attributing it to the fact that I have recently dropped my phone.
I also have a spare battery (I'm using Andida instead of original now), so I'll test to see if that happens with the original too.

Hmmm..
OK so i take out my extended battery and put in the original battery and plug it in to charge since it's on the low side. The phone immediately reboots and continues to do so indefinitely.
As soon as the home screen comes up it reboots.
So I put my extended battery back in and same thing. Now I'm not sure what to think so I've backed up my SD card and performed a complete wipe and am installing a completely different ROM.
I'm hoping it was the ROM or some program and not the phone.
I'll get back later.

rckeystone said:
Hmmm..
OK so i take out my extended battery and put in the original battery and plug it in to charge since it's on the low side. The phone immediately reboots and continues to do so indefinitely.
As soon as the home screen comes up it reboots.
So I put my extended battery back in and same thing. Now I'm not sure what to think so I've backed up my SD card and performed a complete wipe and am installing a completely different ROM.
I'm hoping it was the ROM or some program and not the phone.
I'll get back later.
Click to expand...
Click to collapse
Its good that you guys are investigating the cause of this issue. I too admitingly started using CM when I first rooted my phone. I too had issues and FCs so changing the Rom was the first thing that came to my mind.
You never know maybe its the battery (see the 1700 battery thread on the many problems Andidas has had with their G1 extended batteries)
In the end I am hopeful that you find a solution and have found out sometimes its as easy as changing Roms to fix many complaints/issues you might have.

This is what I've experienced so far.
I did a full wipe of my phone yesterday and installed the AOSP ROM (went away from cyanogen) and I have installed most of my programs. So far all is great. I've had no reboots or any other issues. Since yesterday I have been using my extended battery so I know the battery is OK.
I can't say for sure what was causing my issue. I had been using cyanogen's ROM for quite some time so I don't have a reason to think it was the ROM unless it was one of the current updates.
Perhaps I just had a collection of issues that came to a head and it was time to clean the phone and start over.

Same Problem
Hi, First post here. Great site by the way.
I am having the same problem as you are. Cyanogen, manup's 2.1 (1.5) and the "official tmobile 1.6" rom would frequently reboot or shut off on me. I tried three different sd cards and completely wiped my phone everytime i went between these roms. After much frustration I unrooted my phone last week and went to stock 1.6. It was working perfectly fine but the terrible battery life convinced me to try rooting my g1 again. After going through all the steps the same symptoms came back. So in order to be able to use my phone I went back to the stock unrooted rom. I also would like to mention that before these symptoms came up I had my phone rooted since may 2009. I also tried various SPL's and recoverys while trying to resolve my problem. Thanks

Random reboots are the reason why I don't run CM roms for any length of time anymore. I do load them from time to time to check it out and what not, but more often than not, I always find myself back on a Dwang rom.

My new G1 should be arriving tomorrow, but it has been 2-3 days now with the original battery. No shut downs. While it will be nice to have a new phone (although my phone is unblemished) it will suck to have to re-root it. I am pretty certain its the battery.
I will recheck when I get my new phone set up, I will put the extended battery back in it. I am still pretty certain it is the battery though.

Random Restart and Boot Loop when Plugged In (STOCK)

So I was hoping that anyone here could shed some light on an issue that one of my friends who just bought a Nexus is having. His N1 is bone stock, and is an AT&T model. Every once in a while, completely out of the blue, the screen will turn black and restart, but then enter an infinite boot loop, where the only solution is to remove the power adapter and battery.
In trying to pinpoint the problem, we have noticed:
-It really only tends to happen when the device is plugged in.
-It's not related to the battery, charger, or microSD (since we tried mine to no avail)
-It's probably not kernel, ROM, or radio related (we let it do the OTA 2.2 update, and the crashes were still present)
I don't understand why it only happens when the phone is plugged in. The phone isn't hot to the touch, so I doubt that the battery is over heating.
Any help will be greatly appreciated. Thanks!
PS. I tried searching, but the only mention of boot loops I could find were on custom ROMs and Kernels...

Exact Same problem and Phone here!!!
Just got it today too! Please any suggestions would be nice! Want to root this phone but to afraid there is a hardware issue!

My friend ended up calling HTC and they asked him to return it, which he did, for a full refund. Ironically, he ended up getting a Samsung Galaxy S (ATT Captivate variety). Nexus one, although less powerful, is more sleek in my book...

I've got almost the exact same problem on an AT&T N1 running Froyo FRF91, the two differences I have are that the phone does feel hot to the touch, and that it never happened on 2.1. If anybody has some info on this it would be greatly appreciated, but I will be calling HTC/Google in the next few days to see if we can resolve this problem.

Hey guys,
I had a very similar problem with my phone rebooting while charging especially on the Car Dock. I ended up doing an exchange with Google/HTC and received another unit. This one now has no problems with rebooting. I suggest calling and getting your units replaced. My guess is there was a bad batch that have hardware issues.
Jay

jpav80 said:
Hey guys,
I had a very similar problem with my phone rebooting while charging especially on the Car Dock. I ended up doing an exchange with Google/HTC and received another unit. This one now has no problems with rebooting. I suggest calling and getting your units replaced. My guess is there was a bad batch that have hardware issues.
Jay
Click to expand...
Click to collapse
What can I do if it is unlocked? Any chance they still help you out? Or just forget it?

I don't think it would hurt to just give them a call. I have read some forums where people have sent unlocked phones in for repair and then got them back fixed and re-locked. It is worth a shot instead of having a faulty phone. I did the exchange option and it did take me a while to get my replacement phone, but that was due to HTC moving their repair facility according to the tech. The techs that I have talked to have been helpful. If I thought a tech was no good I just hang up and try again with a different person.
Jay

I have been having pretty much the exact same issues.
I have an AT&T unlocked/rooted N1.
Random reboots frequently when the phone is charging via plug or USB for seemingly no reason. I thought it may have been an app, or combination of apps, so I tried a combination of different steps to try and find a solution.
Wiped data/cache
Wiped data/cache & fix apk permissions (Amon Ra 1.7.0.1)
Wiped data/cache and flashed the current ROM I was using again
Wiped data/cache and flashed different ROMs (both 2.1 and 2.2 w/proper radio) including MCR r16-21, PhoenRom, LeoFroYo, Cyanogen 5/6 RC1 and even tried intersectRaven's Kernel's
Reformated the SDCard both via gparted from Ubuntu live cd and Amon Ra's recovery 1.7.0.1
Swapped out the SDCard thinking possibly a bad block
And finally re-flashed back to shipping stock 2.1 and stock recovery w/successful OTA 2.2 install
All steps I was able to get my N1 to randomly reboot plugged in or not. I even had it sitting on my desk at work unused for 30-40 min (running CM RC1) and it rebooted with no user input what-so-ever. It happens more often while plugged in but was not limited to charging state.
All that said, I finally called support, took about 30 min total to arrange a replacement. This included a factory reset while on the phone with the tech and I was able to get the phone to reboot within a few minutes of first boot.
Take it for what it is worth, but I am positive that this is a hardware issue in my case. Just hope my replacement goes without penalty (unlocked and all) and that my new N1 doesn't have the same issues.

[Q] Random shutdowns with Cognition 2.2b5.5, 6, 7

Experiencing random shutdowns ever since moving to Congnition. This morning, just to clean everything out, I did an Odin Master Clear and used Odin to flash Cognition 2.2b6. About an hour later, I had my first random shutdown.
This doesn't appear to be totally random. It only occurs when the phone is in screenlock mode, such as when it's in my pocket or sitting unused on my desk. I will go grab the phone to turn on the screen, and realize that it is shut off. So, I have to long hold it to boot it back up again.
Is anyone else experiencing this issue with Cognition? It seems to occur about once an hour for me, and sometimes it will go hours without shutting down. Also, it never appears to shutdown when I'm using it, but maybe that's just by chance.
Any other ideas how I could fix this? I've already Master Cleared. Could it be an app that doesn't play well? The only apps I've installed so far is Launcher Pro, Beautiful Widget and Titanium Backup, of course.

Are you serious??????? You open a thread just to ask this question?? Why not ask in the Cognition thread?!!!!

daraj said:
Are you serious??????? You open a thread just to ask this question?? Why not ask in the Cognition thread?!!!!
Click to expand...
Click to collapse
Because it has a trillion posts and my question would be swallowed up in about three minutes.

Same here but i dont think its cognition its the froyo leak. It was happening to me with the stock leak too so i know its not cog. If u think it is try the stock leak. But id wait to see if it still happens after offical build.
Sent from my SAMSUNG-SGH-I897 using XDA App

I had them on Stock ROM but havent had any since installing Beta 6 or 7.

ryanjg11 said:
Experiencing random shutdowns ever since moving to Congnition. This morning, just to clean everything out, I did an Odin Master Clear and used Odin to flash Cognition 2.2b6. About an hour later, I had my first random shutdown.
This doesn't appear to be totally random. It only occurs when the phone is in screenlock mode, such as when it's in my pocket or sitting unused on my desk. I will go grab the phone to turn on the screen, and realize that it is shut off. So, I have to long hold it to boot it back up again.
Is anyone else experiencing this issue with Cognition? It seems to occur about once an hour for me, and sometimes it will go hours without shutting down. Also, it never appears to shutdown when I'm using it, but maybe that's just by chance.
Any other ideas how I could fix this? I've already Master Cleared. Could it be an app that doesn't play well? The only apps I've installed so far is Launcher Pro, Beautiful Widget and Titanium Backup, of course.
Click to expand...
Click to collapse
I would use Odin One Click and go back to stock for a few days and see what happens.
If your restoring with Titanium Backup, don't restore settings.

bet you don't get a solution before they lock this thread

No random shut downs here on either cog 2.2 beta 5 or beta 6

formgen said:
I had them on Stock ROM but havent had any since installing Beta 6 or 7.
Click to expand...
Click to collapse
+1 b5.5,b6,b7 No shutdowns. Had them all the time on 2.1 JF6.

my random shutdown issue STOPPED as soon as I started running Cognition ROMS. DG was a lifesaver for my phone.
If your having them.. keep it on stock - if it repeats - you have a dud and need to get it replaced.
And when you flash it to stock.. don't load anything on it to see if it stops the random shutdown.
**edt... and um wth is this in the dev forum and not the Q&A?

Try this if you havent
No problems here either. I have been with Cog since the beginning and have never had this problem. I had it on another ROM from another Dev and immediately came back to Cog. I am now running Cog 2.2 Beta 7 and Love it! Fastest phone I have ever owned, very stable and GPS finally works!!! I would recommend flashing back to stock with Odin, doing a master clear and then installing Cog beta 7 via Rom Manager. I dont deal with Odin when flashing ROM's, only when going stock.
Hope this helps!

hey... i thought i was the only one getting the random shutdowns. i think i've been getting it since the first month of owning my phone. i get it 2-3 times a day. 1 if i'm lucky. i don't blame it on cognition's rom, tho... dunno what to do or who to ask about this problem.
but as for flashing back to stock and then the latest COG rom, i have tried that, but it didn't work...

I haven't run Cog beta7 for very long, but I can tell you I've never had a random shutdown for the entire time I've owned my phone (bought 3 days after release).
I'm tempted to tell you to try a different battery or something of that nature...

gflare said:
I haven't run Cog beta7 for very long, but I can tell you I've never had a random shutdown for the entire time I've owned my phone (bought 3 days after release).
I'm tempted to tell you to try a different battery or something of that nature...
Click to expand...
Click to collapse
i would agree swapping the phones battery or the whole thing would be the way to go...

This is not an unusual issue. Seems even Moto apologized for it in their Froyo OTA for the Droid. Moto says a fix is coming. I would suspect it is a Froyo bug and something that will be worked out in a future update for all Froyo handsets.

No random shutdowns for me on stock leaked of any of the 2.2 cognitions

I've been having random shutdowns on Stock 2.1 Eclair for a while, there was another thread poster about this in the Q&A.
Even after I flashed to cognition b5.5, I get them, and with the same frequency. Sometimes I get 2 or 3 a day if I'm extremely unlucky, usually I'll only get one like once a week. I don't really find it to be too big of an annoyance.
I think it has something to do with an app, and not the phone itself. If you're getting them consistently 2-3 times a day then I guess you should just master clear, go back to plain stock, and then reflash cognition if you want to.

PEBCAC problem
ryanjg11 said:
Experiencing random shutdowns ever since moving to Congnition. This morning, just to clean everything out, I did an Odin Master Clear and used Odin to flash Cognition 2.2b6. About an hour later, I had my first random shutdown.
This doesn't appear to be totally random. It only occurs when the phone is in screenlock mode, such as when it's in my pocket or sitting unused on my desk. I will go grab the phone to turn on the screen, and realize that it is shut off. So, I have to long hold it to boot it back up again.
Is anyone else experiencing this issue with Cognition? It seems to occur about once an hour for me, and sometimes it will go hours without shutting down. Also, it never appears to shutdown when I'm using it, but maybe that's just by chance.
Any other ideas how I could fix this? I've already Master Cleared. Could it be an app that doesn't play well? The only apps I've installed so far is Launcher Pro, Beautiful Widget and Titanium Backup, of course.
Click to expand...
Click to collapse
PEBCAC problem "me thinks".

Its device specific, I had one that did it, they gave me a new one.

designgears said:
Its device specific, I had one that did it, they gave me a new one.
Click to expand...
Click to collapse
That definitely seems to be the case. I had a Captivate that was running JF6 that was completely stock other than being rooted. It started randomly shutting down within a couple of days. I thought it could be an issue with rooting it, so I flashed back to stock and used it like that for a few days. The random shutdown issue didn't go away, so I took my phone back and told them it was defective. They gave me another one and I haven't had the shutdown issue even once, through JF6, JH7, JI6, and Cognition 2.2 Beta 6 and now Beta 7.

[Q] Stock Dialer Gone Bad, Used Odin and Kies, Still bad! Help!

Ok, so Friday morning I woke up and my phone was stuck in exhibition (desk) mode. I had to remove the battery twice to get it to boot into android and stay there.
This is a NON ROOTED Captivate. Using stock Froyo from Kies.
After I get it into Froyo, I went to make a phone call, and then the dialer sends the call, and vanishes. The phone freezes. The call goes through, but I now have no access to the rest of the phone. No ability to use the dial pad, or even to shut off the phone. I have to manually remove the battery.
After 48 hours I was pissed off. I'm out of warranty with AT&T by a month because I bought it on launch day last year.
So I used Odin to reset it to stock Eclair, and tested it, worse than in Froyo! The phone actually froze and the call didn't even go through! So I re-updated via Kies.
I'm back to square one. I have no idea where to go from here. HELP! I don't want to suffer this until the Galaxy S 2's come out here in the states, and I don't want to flash it to a custom rom if at all possible. Resetting it to stock should have fixed the issue if it was software, right? So it has to be hardware, right? But how does that make sense that only the phone function would be affected?
HELP!
Thanks in advance,
Tiberius Reign

^ Any recently downloaded app, widget, etc. that could be suspect ?? Anything come to mind that u may have done right before this started ??
I see u went to stock eclair, but i ask the above just in case u might have reinstalled everything after u went stock.

I tested the phone without installing any apps. I had a worse problem. The damn phone rebooted. I upgraded back to Froyo, and it became manageable. I saw someone else who was having similar issues with com.android.phone freezing and locking up all the time. Mine does it some of the time, and it's getting worse. I tried the delvik clear etc that was listed, and it still didn't help.
I'm kind of at my wits end here.

A lot of us i think are starting to have this problem. I had started a thread a while back about it but was never able to solve the problem. here is my original thread http://forum.xda-developers.com/showthread.php?t=1168128
here are threads of other people having a similar problem that i have also replied in
http://forum.xda-developers.com/showthread.php?t=1204823
http://forum.xda-developers.com/showthread.php?t=1226807
i think would should all stick to replying back to one thread maybe this one because its newer, this way it can be easier for us to help each other find a solution to this problem.

Do any ROMs fix the shutdown problem?

I tried to search but alas Tapatalk isn't very good at that.
I bought a Captivate via eBay. Before I press to return it, is there a fix or ROM that fixes the dreaded random shutoffs? I tried resets and the GB Serenity ROM but alas I'm still encountering it...rather frequently. Every hour or less it'll shut off. So, other than the battery draining Captivate Keep Alive app...is there a real solution?

barring anything physical with your phone .. I have not had any sleep deaths or random reboots since switching to Fusion-CM-ICS-beta. It used to be a chronic issue with my phone.

Thanks for the fast reply Garyth. I'll give it a go.

I've heard the aosp roms seem to help the problem (this includes the ICS roms). They use different drivers than Samsung roms.

So far, so good. Data is consistently faster as well. Thanks again!

Hmm. Still getting random yet pervasive shut downs.

I believe this was a known hardware issue as well. There is a thread around somewhere will effected build numbers.

I saw that thread and don't believe mine is in the range. I'll be calling the seller tomorrow anyway.

Not sure if you are in the same boat as me, since the IMEI of my phone does fall into that catergory of the "recalled" phones, but since it was out of warranty by the time I saw that post, they wouldn't exchange it at the store.
At any rate, here's what I've gone thru:
Back in the Froyo times, I "think" CM7 fixed the issue, but I was too fidgety at the time so I was always trying new roms so I don't remember 100% if that was true or not.
I read somewhere that this could be caused by the battery shifting around due to temp changes as it charge/discharges, and that you should put some electrical tape or whatever to make sure your batt. made good contact. Didn't work for me at all.
So finally what fixed the problem was Captivate Keep Alive app, it's in the market.
First I tried it with two ICS roms: ICSSGS and Fusion, with Platypus and IcyGlitch kernels. The app work fine with a setting of 85%, but I was getting "charge death" as well, which I've never had before.
So now I've rolled back to KK4 (Serenity ROM) with the latest Corn kernel, and for some reason I have to set the app to 80% charge but works.
There'll be definitely an increase in battery drain, but for me it hasn't been that bad.

I used to have that problem when I first got my cappy, had froyo KB1 on it, and it would randomly shut down. Eventually when I got into hacking the android, when I finally updated to newer bootloaders, the problem went away. Though I can't recommend flashing bootloaders, since you can hard brick your phone if unsuccessful. Just saying that's what seemed to solve the problem for me.

mrhaley30705 said:
I've heard the aosp roms seem to help the problem (this includes the ICS roms). They use different drivers than Samsung roms.
Click to expand...
Click to collapse
Can anyone confirm this?
crt60 said:
I used to have that problem when I first got my cappy, had froyo KB1 on it, and it would randomly shut down. Eventually when I got into hacking the android, when I finally updated to newer bootloaders, the problem went away. Though I can't recommend flashing bootloaders, since you can hard brick your phone if unsuccessful. Just saying that's what seemed to solve the problem for me.
Click to expand...
Click to collapse
But what bootloader fix that to you?

Mine only rebooted randomly once when on eclair. Haven't had a problem in gb or ics.
Posted from my ICS'd Captivate

That would help if eclair wasn't completely useless.
Sent from my Samsung Captivate running Team ICSSGS 4.0.3

I tried Captivate Keep Alive. Even it didn't work. A replacement phone is on its way. The IMEI was actually affected, but I didn't realize at first because I only looked at the last digits. Apparently was a really early build. The seller photographed the new IMEI before shipping it out so I could verify.

I have Dark Knight's 4.0.4 ROM since 2 weeks ago.
At the moment, and I hope it remains 0 reboots.
Just wanna share with you, is up to you to try it....
http://forum.xda-developers.com/showthread.php?t=1501615
By the way, with this ROM also I got the best Quandrant Benchamark score (2400) without overcloking...

I'll keep that in mind but I got a replacement that works really well. I ended up getting it from another seller though.