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?

G1 Device screen not wake up, a short message to all DEVs,

Dear all DEV,
I dont know if you all facing same problem as me, I have tried many kind of Hero for G1 from tradition hero by Drizzy till now the rom was upgrade to use RAM hack, but now I found one issue with my G1 when I try new rom that build on new JAC kenel ( I can't remember all BFS xxx) and it was my phone will not wake up and alert me anything after he sleep for quite a long time, for example, some one call me, they still can ring me, but for me I know nothing from me phone and even I press to unlock the phone, nothing happen. The screen just stay back or sometime I can see some picture from the screen without backlight, but nothing work for me, unless I pulled out battery and reboot phone back. After new reboot, it will go back to same situation again after a long sleep.
This text is not a panic to any DEV, but I want to show it out to you guy all in the new thread just want you all hear about this issue, cause sometime I reply in other thread, it was obmitted.
MOD, you can say I start new thread for nothing important and you can close it anytime you want, cause My main purpose just need some DEV to see my issue and keep it in consideration.
As this issue happen to me currenly I can not use SenseHero or M-LING... cause it's all give me this bad experience, and now I just stay with a very tradition Hero from Drizzy.
Regards,

I did have the same problems when using BFS 300 and 302. But 202 was fine, but didn't have WIFI. Pretty much what you need to do is use one that doesn't use any BFS (MLIGN, myHero) and you'll be fine.

Not sure if this is the same problem or not?
I replaced the MB in my G1 and now it fails to wake the screen up - SOMETIMES. No real rhyme or reason to it that I have found. I suspect that it's related to the MB and not any specific ROM. On reboot, sometimes I get the G1 logo for a few seconds, and then it goes black until reaching the boot screen. Other times it will go white on reboot, or white with black stripes. Sometimes, I can get it to wake up by pressing power then home several times, but that hasn't worked in a few days.
I'm preventing it from going to sleep, seems to work but it killer on my battery. Posting here to see if anyone else has run into this, and if there are any known fixes.

This only happens to me when I had stericsons LS. This may be a thing of the past because now I just stick with cyans rom. Last night I tried the 10 mb hack and had the issue again. Developer was already aware and working on the kernels though.

[Q] charging problem

i finally get my SGS back to JM1, install the voodoo lagfix + colour fix (which im now looking to remove as it does wierd things to my screen, the colour fix not the lagfix). anyway i thought i had it set-up perfectly, then i put it on charge last night at some point it hit the 100% charge and then 5-10 mins later it turned off (as in completly turned off), as i use this phone for daily alarm/diary etc this is obviously quite a shock that the alarm no longer functions if the phone is off, i know sony and nokia and htc's will all still work in these circumstances, due to this i missed a very important meeting.
so how can i fix this, firstly i want it to stop turning off on full charge (it used to just stay on), if this is not an option i want to make it so the alarm goes off, even if the phone is off,

I just tested it and the alarm of my gt-i9000 doesn't work either, when the phone is turned off. Pretty lame.
I have Froyo JPM with Chainfire's root

you would think it would as some things are important, im more worried that its turning itself off 5-10 mins after being fully charged, there is no setting for it either, so its a problem with the way the rom flashed.
i did a full clear and wipe of both sd, and cache from the recovery menu, and then i also formatted the int sd, when android booted to get rid of that annoying process error. so it cant be that. the only things i have installed are the apps i have paid for, and the lagfix, i never had this issue b4 when i did not use the lag fix, could it be that thats causing it.

how to fix turning off issue for samsung i9000 ?

I just have updated my mobile from 2.2.1 to 2.3.4, i used this forum tutorial - http://forum.xda-developers.com/showthread.php?t=1139050
I have issue - my phone is turning off for no reason, you know i don't have lots of apps only fb,twitter,skype and 'advanced task killer'
actually when I am doing Skype video calls, writing SMS or anything else my phone just changed to 'black screen' every couple hours and afterwards my Samsung turning off with sound. To turn on I need take battery off and then into back then he allow to turn on...
before I updated I had little bit similar situation, my phone had 2.2.1 version and i didn't have black screen, but my phone just had 'freezing' for 10 sec or more...
what's problem for? what's your suggestions ? thank you a lot.
Ed

I have this issue as well, although it doesn't happen as much since I upgraded to gingerbread. I did have it happen once the other day. I was listening to music and I needed to make a call and when exiting the music app, it froze. It then went black and I had to take battery out and put it back in. It's annoying if you got a otterbox case on it with two layers. I had heard updating to gingerbread stops this but so far I don't think it's 100%. I use my phone as my alarm and one time it went dead with a full charge and I was almost late for work.
Let me know if you figure something out.

what can say experts about our issue ?
I will take some day my mobile to repair centre.. it's sad if couple of people have same issue and nobody can tell us the problem reason.

Try to flash a custom kernel and see if it the problem is still there

can you tell me or give information what's is 'flash custom kernel' ?

I have also encountered this problem, very frequently if i may add.
the problem actually first occured a few months ago, after i updated my firmware to gingerbread.
In my case the phone does not freeze, the screen wont turn on or respond to any gestures (hardware/capacitive button won't too), however any running process still runs, in specific i can still recieve phone calls, or at least hear the ringer.
I know of many other people that encountered this problem, all came from different ROMs (MIUI, SH 3.5 and up, Stock, PilotX etc..) and i, for one, can say that in the past two-three weeks it atarted appearing a few times a day.
So - does anyone have any ideas for the nature of this BUG??
BTW I use the i9000t which i own for over 7 months now.

Same problem
Hi, I have the same problem here.
and have seen this myself on stock roms too.
It doesn't happen very often (only once on my phone for now) but it is getting me pissed off as no one knows the nature of this BUG.
could it be a problem with the latest 2.3.4 version ? or an update of one of the applications?
I don't have too many apps on my phone only skype and 2-3 games.
the only thing I can think of right now is that all people who had this bug had skype on the phone but I don't really think it's from that.

Hi, And-roid if u ll update to 2.3.4 your mobile will working deffo better, i suggest you update your mobile to 2.3.4

Hey eddys, i have 2.3.4 for over two months now, and the problem just go worst...

Hi eddys,
I have the 2.3.4 (and my brother and sister in law have it too with a stock rom).
this is happening on all roms and all kernels...maybe a problem with the 2.3.4?
I don't know but it is very weird, no one has an answer for this....
edit:
just checked this with my phone supplier and of course they have no idea what so ever about this bug.
come to think of it they didn't even know how to fix my brother in laws "problem" when the 3G internet didn't work (settings-->wireless and network-->mobile network--> check the V on Use packet data ) so no surprise there.

Anyone???
Maybe theres another forum that this problem should be posted at??

I have this bug too, but only while tethering. I've found a solution to the tethering related crashes - after you start tethering, go to the SuperUser settings, and disable root permissions for android wifi tether. Your phone shouldn't crash anymore.

hey zyczu,
unfortunately, I do not use tethering at all, do you suggest i should disable ALL root permissions?
This bug is really getting on my nerves!!!
Everything else, but this, is working great...

Since upgrading my i9000m to 2.3.3 through Kies, my phone has exhibited similar symptoms 3 times: freezing, not responding to touch etc.
The first time I had pulled the battery when it did this, but the 2nd time I had just put the phone down a minute or 2 earlier so display was off so didn't notice it(about 2 weeks ago). And the 3rd time(today), I was using it at the time, and so started taking off my rubberized case, only to have it restart before I got the chance to pull the phone back off.
Startup took much much longer than normal, which I recall the startup was similar during the 2nd "freeze & reboot". For some reason today, I randomly though maybe its an OTA update so I checked "Settings..About Phone" and found my kernel version listed as:
Code:
2.6.35.7-I9000UGKG3
[email protected]#2
I have no idea what it was before, but September 8th was 2 days ago... It is possible it said that before today's restart but no idea. I have a PIN on my SIM so when starting up have to enter PIN for it to work, but on these auto restarts I never got asked for my PIN so it could have restarted other times too without me noticing(ie. middle of night).

Hmm, mine used to something similar when I would leave Bluetooth on but would move out of range of a paired device. After a few minutes it would just shut down or stop responding. Haven't had that issue since moving to Milkys rom.

hi guys, i just used this tutorial http://androidadvices.com/how-to-up...0-to-stable-gingerbread-xwjvh-2-3-3-firmware/
first I installed 2.3.3 XWJVB then 2.3.3 XWJVH
just doing step by step...
my phone was working fine 2days then i had same issue and then I changed to original SAMSUNG battery and it's working perfect.
try this..
p.s. what kind of batteries you have 'original' or 'non-original' ? thank you

madmigs:
I did not notice the kernel version ive had before, however i took my phone to a service center today, and for what i can see i have the same version as you do, take aside the i9000t instead of i9000m...
eddys:
Ive been using different batteries orig/non-orig on and off, although since ive noticed it hurts performance i stopped doing that, do you suggest that this might be the cause of the problem?
If so, the factory wipe i just did (formatted the internal SD card) should do the trick.

try reading this it helped me since i turn the wi fi off when i go out
http://androidforums.com/samsung-galaxy-ace/312084-randomly-turning-off.html

Are you guys experiencing turn-off issue while phone is in the locked state. I mean you locked the screen and then after a while when you picked it up for unlocking it was powered off. If anyone has this issue, then I found a solution. Just let me know

my turning off issue went back and it's getting every time more annoying, I don't know what to do...

[Q] I9000M 2.3.3 stock constant reboot and screen turned off

Hi I have a strange problem with my Samsung Galaxy S Vibrant (I9000M) running 2.3.3 stock.
Description:
a) Booting the phone would show the big S animation and bong sound however after that the animation repeats in a loop with no more sound. The phone never reaches the home screen. I notice this mostly in the morning when I wake up.
b) Usually during the morning when I wake up to check the time the screen doesn't turn on but it seems as if the phone is still working; the chime for plugging in the charger sounds. (I thought the battery was dead but it was actually at 60%)
What I've done so far:
a) I brought it back to the vendor and got a new phone.
b) Holding the power button would turn off the phone, then I would turn it back on. Sometimes it requires that I pull out the battery which results in losing all my data on the internal memory like a factory reset.
Question:
I'm highly concerned. I've gone through two of these phones and problem "b" is always a prelude to problem "a". I'd like to know if there is a possible solution and/or what the problem might be?
Note:
a) The problem started happening a day or so after I started using Samsung IM. (Skype was installed but never used)
b) The problem started the morning right after I installed Skype. (I have since uninstalled Skype, it's still happening )

You should not be losing data on your SD card by pulling the battery.
Did they give you a new phone or a refurb?
What's the build number of your phone? Should be a number under the battery in YY.MM format.

Hi Black Rose
I was talking about the internal memory not the sd card.
It's a new phone.
The build is 11.11.

If you are running stock 2.3.3 and having those issues, I think the phone is faulty.
My wife is running 2.3.3 on an 11.03 build and has no problems.
The fact that you are losing data when you pull the battery sounds like the internal memory is failing.

Alright, thanks. Do you have an idea what causes the screen to not turn on for the second phone? (This new one doesn't loose internal memory on battery pull)

I had that happen to my own phone (also an 11.03) once with Froyo 2.2 and once with 2.3.3.
With Froyo I was able to plug in the charger and the phone "woke up".
The only time it happened on 2.3.3 I received a couple of notifications at the same time and had to power it off to get the phone to work again. It never happened again in the several months I was running 2.3.3.

Okay!
Thank you Black Rose for giving me some useful information. I was just worried that this would lead to something a lot worse.
Much appreciated!

This is my 3rd phone had the exact same problem as you I heard it was something with the mother board there is a board in here dedicated to the problems with the gt-i9000m
Sent from my GT-I9000 using Tapatalk

Thanks for letting me know bambam1978; I hadn't realized there was a whole topic for all the problems. I've been searching for the specific problem where most have customs roms which is why I started this one.