Database Develop

phone shuts off!!! help..

Can someone please help me..
I installed Cyanogen 3.4 when it got released a few days ago and it was running smoothly.. I think he is a genious. Just today my phone shut off on its own and I had to take the battery out and put it back in to get it to come back on. I don't know if it is Cyanogen or some sort of app, as I download apps quiet frequently. I am going to go through my apps now and also reinstall Cyanogen 3.4 tonight and leave my phone on all night. I guess I will have to see in the morning..
Anyways, can someone help

I ve fot sometimes the same issue with dudes cupcake which use th cygnonen kernel...
I ll be glad to have a fix

Are you overclocking the processor? That might contribute to it shutting down.

I do overclock but why do i have to 'battery pull' to make it reboot?

Yes, same issue here.
Uhh, again...
Powered up, set to standby, waited 1 min, shut down.
EDIT: I'm on Rogers Cyanigenized.

Same issue here. Complete lockup with screen off, have to pull battery to boot again. Seems to happen every 6-12 hours for me.
My Phone:
Cyanogen 3.4
radio 2.22.19.26I
Haykuro's SPL
Kernel 2.6.27.24-cm by [email protected] )
NOT overclocked, and no clocking tools even installed. Persists after several clean wipe and reflash also.
This thread's timing is great... I was just about to reset back to rc29 and build back up. Thought I was going to have to replace my phone

Rastasia said:
I do overclock but why do i have to 'battery pull' to make it reboot?
Click to expand...
Click to collapse
This question should probably be in the Dream section and will probably get locked/moved but Pulling the battery reset the "overclock" until it boots back up. This would be why pulling the battery helps.

hey you don't havbe to pull battery just push end call start call and menu all at once it will reboot you phone

Ok, thanks to Jakob, we know, that android freezes, is doesn't shut down.
I now tested with and without overclock, it made no matter to me not to overclock, there's no difference.
But I experienced it didn't happen when it's connected to a charger..
mysterious..

This keeps hapening to me, first it was happening in Cyanogized Rogers rom, then in The Dudes 1.3 b 12, I'm flashing JAC1.62 right now, this never happened to me before I got my class 6 16gb and started using apps2sd
Just curious, does this happen to anyone without a2sd

i'm having the same problem

seems to happen in the builds using the Cyanogen kernel. I'm sure this issue will iron itself out in future releases so just sit tight.

I too am having the problem on the Cyanogen 3.4 build. Its definately a change in 3.4 as I didn't have this problem in any of the 3.3 betas. I'm doing Apps2SD as well.
One thing I have noticed as well is that networking has been acting flakier than normal.
I had this issue on the pre-cupcake radio but not as frequent, so maybe it's just an amplified version of the same problem? There was a thread about it before but I'm too lazy to search for it.

The hangs was the only reason I moved to virtududes rogers rom v3

I'm going to try and get this sorted out tomorrow. For some reason the OOM killer kicks in sometimes and kills a critical process like zygote.

atleast you don't have this problem!
I've reflashed,wiped,formatted and apps2sd2 or sdpsplit, so many times already... trying different ways for each. But same thing always happens... my memory card gets damaged then wiped all by itself.

Uninstall toggle Setting and use Reparing Ext partition with Cyonagen recovery seems to fix this issue

So happy I found this thread! I'm using Google Ion and having this issue since yesterday. So annoying. Anyone got a fix?

I`m having the same problem, the phone freeze, looks like is a hardware problem, i`m on CRC1

I have started to have this issue as well. I am currently running Cyan4.1.999. It happened yesterday while on a call, after a call, and also while the phone was on charge.
Solutions?

Phone restarts by its self after flashing fresh 2.1.1

ok first off i love the fresh roms so im not bashing.
does anyone else have an issue that seams to be directly related to flashing the new fresh 2.1.1 rom.
when im in a call and end it with the power button it restarts the phone.
is this because of what i think it is or something else.
i wiped everything when i flashed so i dont know what else it could be, in the mean time i guess i have to go back to fresh 1.1 sense i cant find a fresh 2.0d download link anymore and i deleted my nandroid and the 2.0d rom off my computer like an idiot. uneless someone could point me to a 2.0d link

shawnwojcik said:
ok first off i love the fresh roms so im not bashing.
does anyone else have an issue that seams to be directly related to flashing the new fresh 2.1.1 rom.
when im in a call and end it with the power button it restarts the phone.
is this because of what i think it is or something else.
i wiped everything when i flashed so i dont know what else it could be, in the mean time i guess i have to go back to fresh 1.1 sense i cant find a fresh 2.0d download link anymore and i deleted my nandroid and the 2.0d rom off my computer like an idiot. uneless someone could point me to a 2.0d link
Click to expand...
Click to collapse
probably should be in q&a or fresh's thread but here is a link all fresh's downloads are on geekfor.me should be at the bottom
http://geekfor.me/category/android21/page/2/

I found that the restarting issue on my end was linked to the battery stats and roation stats. After i wiped those, for some reason, i stopped restarting.

sdotcarlisle said:
probably should be in q&a or fresh's thread but here is a link all fresh's downloads are on geekfor.me should be at the bottom
http://geekfor.me/category/android21/page/2/
Click to expand...
Click to collapse
sorry i wasnt sure where to put it. sould i start a new thread in there or can a mod move this one?

Powers16 said:
I found that the restarting issue on my end was linked to the battery stats and roation stats. After i wiped those, for some reason, i stopped restarting.
Click to expand...
Click to collapse
Can you elaborate on this? How do you wipe these stats?

i had the same problem but it was on fresh and damage control, i figured out it was the app i was using to call people with...called quick connect...
it didn't happen if i dailed with the stock dialer or through people...

jasonevil said:
i had the same problem but it was on fresh and damage control, i figured out it was the app i was using to call people with...called quick connect...
it didn't happen if i dialed with the stock dialer or through people...
Click to expand...
Click to collapse
Alright I did everything mentioned, above. i wiped the battery and rotation stats in ra recovery i even re partitioned my sd card and did a wipe data/factory reset plus the ext and dalvik-cache. then re flashed fresh 2.1.1.
also i am not using any other dialer that i know of. just the one that comes backed in the rom.
so why am i still resetting randomly!!! it even did it when i was doing nothing at all not just in a call like before.
this is on two seperate sprint htc heros that this is happening to.
anyone please help!

shawnwojcik said:
Alright I did everything mentioned, above. i wiped the battery and rotation stats in ra recovery i even re partitioned my sd card and did a wipe data/factory reset plus the ext and dalvik-cache. then re flashed fresh 2.1.1.
also i am not using any other dialer that i know of. just the one that comes backed in the rom.
so why am i still resetting randomly!!! it even did it when i was doing nothing at all not just in a call like before.
this is on two seperate sprint htc heros that this is happening to.
anyone please help!
Click to expand...
Click to collapse
couple questions.
1. are you using any aggressive process killers, like the one found in spare parts?
2. what, exactly, do you mean by resetting? do you mean a quick 10 second restart of rosie, or a full on 1.5 minute reboot?

Nextelian said:
couple questions.
1. are you using any aggressive process killers, like the one found in spare parts?
2. what, exactly, do you mean by resetting? do you mean a quick 10 second restart of rosie, or a full on 1.5 minute reboot?
Click to expand...
Click to collapse
sorry i took so long to reply.
no process killers.
Im now able to replicate it restarting (not randomly) if i let the phone go to sleep by its self and sit for a minute when i hit the end button to wake it up nothing lights up like it should instead it does a full on 1.5 minute reboot every time.
on a separate thread someone suggested i try a different battery because whenever they put a different battery in it stopped resetting. (I was not able to try this yet because i don't have any spare batteries laying around)
I just find this hard to believe only a few people are having these problems and why no one seems to have a definitive answer.

This is kind of one of those bugs where I have to say it's something going on with your phone. Fresh Rom 2.1.1 has been downloaded over 4000 times. I restart mine constantly while testing things which means I am constantly duplicating your situation of restarting the phone, letting it sleep, and then turning it on via the power button, and I have never had this happen.
Please post a debug log of it happening and we'll see if we can figure out why your phone is doing it.

My sister had this issue even on stock 1.5. Rooted, added recovery still had it. Flashed 2.0d, still had it, went to recovery and wiped battery stats.
Haven't had it happen since. Now on 2.1.1 and all is well...go figure.

flipzmode said:
This is kind of one of those bugs where I have to say it's something going on with your phone. Fresh Rom 2.1.1 has been downloaded over 4000 times. I restart mine constantly while testing things which means I am constantly duplicating your situation of restarting the phone, letting it sleep, and then turning it on via the power button, and I have never had this happen.
Please post a debug log of it happening and we'll see if we can figure out why your phone is doing it.
Click to expand...
Click to collapse
thank you for helping flipz, sorry for thinking it was something to do with your rom (foot in mouth). I now believe it a hardware issue related to any 2.1 fw.
This has happened to me on 2 different phones. Mine and my friends. Mine restarted "randomly" once i wiped the battery and rotation stats and it fixed mine. My friends on the other hand i could not get to stop restarting for the life of me. So i was forced to switch back to a 1.5 fw rom.
Point being it will take me a few days to get back over there and put a 2.1 fw back on it and get a debug log off of it. for now i can try using his battery in my phone and see if i have any issues. im crossing my fingers in hope i will so we can buy a new battery and see if it goes away for him.
in the mean time i can post a debug log for my phone but it probably wont do any good
i will try to post the results of the battery swap later today.
again thanx flipz i am confident with your help we can resolve this.

ok i thought i attached a error log but i guess its too big, so ill try zipping it and attaching it.

hero
I noticed reinserting the root file helped me also make sure your not using otwidhet or super pc unless u have a rom for it i use fresh toast 2.1 no problems quickquickquick

REDSCARFACE said:
I noticed reinserting the root file helped me also make sure your not using otwidhet or super pc unless u have a rom for it i use fresh toast 2.1 no problems quickquickquick
Click to expand...
Click to collapse
I kind of a noob, what do you mean reinserting the root file? i thought the root was the main directory not a file.
Also i dont know what "otwidhet" or "super pc" are, im assuming im not using them if they didnt come with the rom. right?

whoops, i forgot to post the results of swapping my battery with my fiends to see if i could single out a bad bad battery.
i didnt have any luck making my phone reset itself with his battery. One of these days im going to buy a couple new batteries put on in my friends hero and flash fresh 2.1.2 on it. Im also going to try using different radios on a hunch from a different thread i read.
i dont mean to waste anyones time im just busy and messing with phone is something i cant devote alot of time to especially sense i put a 1.5 fw rom on my friends phone and he no longer has any issues.
thanks for the patients in helping me guys.

ok im at a loss. i really need your guys help.
I put a 2.1fw on my buddies phone. put my battery in his phone let it go to sleep by itself and hit the end button to wake it up and it still does a reset. now i guess im not sure if it s a full on reset but it takes about a minute to reset.
so i put his battery in my phone and let it go to sleep and het the end button to wake it up and it also reset, now i did not clear the battery stats either and now after one time i can not get my phone with his battery to self reset for the life of me...???
no matter what bettery i try his phone will not stop resetting.
im posting an error log from his phone i got off adb using
adb bugreport > errorlog.txt
is that what im suppose to do? please help i would have been just fine with the 1.5fw on his phone but there was an audio issue that on some calls the person on the other end could not hear him.
does anyone know if the flipz audio fix will work for that or is that not a good ides?

Here is his error log, i hope this is what im suppose to post.
if anyone has any ideas about the audio fix for the 1.5fw that would be awesome cause now i gotta go back to that becasue i cant leave his phone with porblems.

Could it be that it is just Sense restarting and not the whole phone. Try using Fresh 2.1.2 with LauncherPro and see if you still have the problems. Make sure that you are not using the vanilla launcher in 2.1.1 as I had several instances where it caused instability.

lineman78 said:
Could it be that it is just Sense restarting and not the whole phone. Try using Fresh 2.1.2 with LauncherPro and see if you still have the problems. Make sure that you are not using the vanilla launcher in 2.1.1 as I had several instances where it caused instability.
Click to expand...
Click to collapse
I dont think thats the issue, my phone now restarts itself abuot once a day and i am using launcher pro. i also have my friends battey in my phone. so i guess is could still be the battery.
Im still confused on what i have to do to get some help from the devs. i posted a error log like asked if i was suppse tp post something else could someone please tell me? this is getting extremely frustrating. am i the only one here???
please someone help.

Home and search button's not working

Hi, I have an AT&T Nexus One, running FRF85B currently. As of lately, even before update I noticed my home and search button stopped working. The haptic feedback responds when I touch them but they don't do anything. I searched the forums so please don't flame me if I missed a thread. Much thanks to anyone that can help!
P.S. I soft reset the phone a few times and also have reflashed

can you post a logcat of what happens when you press the buttons? and also try wiping cache and dalvik cache

Try to wipe and reflash and post logcat

Gfs stock phone just started doing this. Will try to get some kind of logs... A reset wouldn't make her very happy, fffuuuu

http://www.google.com/support/forum/p/android/thread?tid=3c3ae39887a83bbc&hl=en
&
http://code.google.com/p/android/issues/detail?id=8503
according to this we arent the only ones. it looks like a factory reset can fix the problem, but some on the link above re-encountered the problem weeks later.
surprised XDA hasnt run into this before...
in addition to home/search buttons haptic'in but not doing anything, slide lock screen goes away and the phones cannot receive calls.

Those buttons are programmable, maybe some app took control and does nothing ?A launcher perhaps?

'Programmable'? How can I set Search to ixquick?

Quantumstate said:
'Programmable'? How can I set Search to ixquick?
Click to expand...
Click to collapse
The app's manifest needs to mention that it can handle that event

britoso said:
Those buttons are programmable, maybe some app took control and does nothing ?A launcher perhaps?
Click to expand...
Click to collapse
doesnt make sense though, everyone that has had this issue had all 3 completely unrelated issues:
1. buttons vibrate, do nothing
2. phone cannot receive calls
3. lock screen disappears
a wipe fixed it last night but man it was a ***** to reinstall everything for her.

turbosix said:
doesnt make sense though, everyone that has had this issue had all 3 completely unrelated issues:
1. buttons vibrate, do nothing
2. phone cannot receive calls
3. lock screen disappears
a wipe fixed it last night but man it was a ***** to reinstall everything for her.
Click to expand...
Click to collapse
This is exactly what is happening to me. I'm going to wipe now.

god damn it. this **** just started happening again... n1 has been running the OTA stock GB 2.3.3...
we ended up getting HTC to warranty the phone and everything was fine until this morning..
any help?

same
So i started having this problem about 3 weeks ago as well right after i flashed CM7's newest experimental build. first thing I witnessed was not being able to receive calls. I figured that this was a problem with CM7 and flashed modaco's r26, after a full wipe, when it just came out a few days ago. After a day, i got the problem with the lock screen and the home and search buttons not working. I again thought this was a problem with gingerbread for some reason and flashed MIUI Mod Rodriguez style rom, again full wipe. I had restored everything through titanium backup and other forms of recovery and within about 60 minutes my home button and search keys stopped working.
So I finally figured that it was some settings that I must have adjusted and carried through numerous different ROMs that caused the problems. So next time around I didn't restore anything, running on MIUI mod, and didn't restore anything for the remainder of the day to see what happened. Low and behold, after a reset the problem came back. One other complication is that the phone will always forget my google account and i'll have to re-connect it. Then I realize that the home key doesn't work. So even not importing anything from my old Rom's with a clean wipe didn't get rid of it.
I still get haptic feedback, but the buttons just don't do anything. I changed the setting for how home and search respond in both scenarios and can't get any response either. I flashed back to an old version now and so far i'm alright. But if someone can figure out why this is happening that would be awesome.
For the other people who are having this problem, when you're doing a clean wipe are you then restoring things back via titanium back up or otherwise? and when did you first start to experience these problems?

Istarted having this same problem today. I recently flashed over to cm7 rc2 and then the same thing happened. It seems like after I do a titanium backup and then change a setting it will reset to the cm boot screen and when it comes back there's no home screen or search buttons. All the same issues. Haptic feedback works but nothing happens. I'm on an evo btw.

Same thing occuring for me after flashing CM7. Reverted back to Miui, but so far no luck in fixing this. Numerous factory resets have yet to resolve as well. This is pretty frustrating...

Having this issue as well on CM7. DEFINITELY Titanium related.

I had this problem too. I just had to shut down the phone then leave it for about 10-15 minutes then turn it on again. Everything should be fine again. ^^

screen freezes when i wake my phone

Ever since i manually updated to frf91 sometimes when i try to wake my phone my screen freezes an i can't unlock it also when i try to power my phone back on it will vibrate 7 times an it wont come on. I guts take the battery out an put it back it to get my phone to turn back on. I've never had this problem until i manually updated my phone. I did a factory reset an it helped for a while but the problems come back. Has anyone had this problem an does anyone know how i can fix this? I'd really appreciate any help i can get

Help please

Is the bootloader unlocked?

this seems to be a common issue with FRF91, although most people's phones will unfreeze after a minute or two, does your backlight turn on and off when you press the power button?

Jep4444 said:
this seems to be a common issue with FRF91, although most people's phones will unfreeze after a minute or two, does your backlight turn on and off when you press the power button?
Click to expand...
Click to collapse
whether it unfreezes after a minute or two depends on what it's doing..there have been many times where i have to pull battery...........

rensky said:
whether it unfreezes after a minute or two depends on what it's doing..there have been many times where i have to pull battery...........
Click to expand...
Click to collapse
ya i have had to as well but most of the time it wakes just fine

No my bootloader is not unlocked an yea the backlight will come on but it won't unlock. Ive never tried waitin a min to see if it fixes itself i just usually pull the battery when it happens an sometimes when i try to turn my phone back on it does the 7 vibrating thing. Like i said before it never happened until frf91

I have an app called AutoKiller installed. It tweaks the Android system's inner memory management routines. it was set to something other than default. I changed it back to default, and haven't had a problem since. if you have this installed, maybe try and switch it to default settings.

Sounds like a data issue. A factory reset only wipes user data, You must wipe in recovery to wipe rom data. Also make sure you have the correct radio for the build especially coming from lower build. If that's the issue flash radio first to support the build. Then flash the rom.
Sent from my Nexus One using XDA App

How do u wipe in recovery? Yea im a newb lol

Also if i wipe in recovery will i still be on 2.2 or will i have to update to it again?

What's causing Cappy to reset frequently after factory wiping and NO oc/uv?

I have frequently been flashing/testing different rom's on my Cappy's but recently ran into a problem which I originally thought had to be the rom(s) or oc/uv but apparently is not.
The issue is resetting after the phone has been screen off or asleep for a half hour or more.. and recently been rebooting during calls....never while using the phone for anything else.. but most often when i'm not using the phone and i go to wake it up, I notice it is off and have to turn it on only to notice i missed some calls,etc..
This started about a week ago. I have since wiped the phone at least TEN times. Different ROM's almost every time. I have gone with STOCK voltages and clocks.. i even changed the min voltage to 200 or higher in case that was causing the sleep issue but i never had the issue before.. but it's still turning off a lot.. and this is my second cappy, the one that I dont do much oc or uv..like the other that I have OC'd to 1.785 Ghz stable... this one is usually run at 1.1 or 1.2 with little or no uv...
I've tried different modems to see if that was causing the restarts during calls...and have wiped the phone with different rom's so many times...
what on earth can cause this? is the phone's hardware in some way damaged? Could previous tweaking have caused damage or could the phone just be toast? or am I missing something?
The phone still boots fine and if i'm using it i can do anything and everyting (including oc and uv) for hours...but if i make or receive a call, about 50% of the time it will restart..and if the phone goes to sleep..for the night or just for some time during the day..usually it will be off when i go to turn it back on..
any help? thanks

pchemerys said:
I have frequently been flashing/testing different rom's on my Cappy's but recently ran into a problem which I originally thought had to be the rom(s) or oc/uv but apparently is not.
The issue is resetting after the phone has been screen off or asleep for a half hour or more.. and recently been rebooting during calls....never while using the phone for anything else.. but most often when i'm not using the phone and i go to wake it up, I notice it is off and have to turn it on only to notice i missed some calls,etc..
This started about a week ago. I have since wiped the phone at least TEN times. Different ROM's almost every time. I have gone with STOCK voltages and clocks.. i even changed the min voltage to 200 or higher in case that was causing the sleep issue but i never had the issue before.. but it's still turning off a lot.. and this is my second cappy, the one that I dont do much oc or uv..like the other that I have OC'd to 1.785 Ghz stable... this one is usually run at 1.1 or 1.2 with little or no uv...
I've tried different modems to see if that was causing the restarts during calls...and have wiped the phone with different rom's so many times...
what on earth can cause this? is the phone's hardware in some way damaged? Could previous tweaking have caused damage or could the phone just be toast? or am I missing something?
The phone still boots fine and if i'm using it i can do anything and everyting (including oc and uv) for hours...but if i make or receive a call, about 50% of the time it will restart..and if the phone goes to sleep..for the night or just for some time during the day..usually it will be off when i go to turn it back on..
any help? thanks
Click to expand...
Click to collapse
If you have tried many different modems and ROMs then i think your best bet is to flash back to stock and see if the problem persists, if yes, well then it's hardware, if not, then you may have had a buggy kernel or perhaps your phone just didn't like the ROM you ran (this has happened to me with several versions of DarkyROM, and yet other DarkyROMS work perfectly) Good luck!