Related
Hi all. For some reason, my phone shuts down only when its screen is off. If I keep the display on or if it's plugged in, it'll stay on... Any ideas anyone? Help much appreciated.
pokedoke said:
Hi all. For some reason, my phone shuts down only when its screen is off. If I keep the display on or if it's plugged in, it'll stay on... Any ideas anyone? Help much appreciated.
Click to expand...
Click to collapse
Im hearing this alot from my gf who says this happens or that it just powers down altogether...
1-4 times a day. I have no answers yet...
Sent from my PC36100 using XDA App
well, thanks for replying. I just asked for warranty exchange. Seems other people had the problem too. Just didn't have time to hunt then.
My first captivate had that same problem. It seemed to be random and occur after the phone goes into standby mode, I would try and bring up the lock screen and it wouldn't appear and I would have to power the phone back on. Didn't happen for the first month or so that I had it, then it started happening as much as 10-15 times a day. May have occurred more often in areas with bad reception. Tried several different ROM's including stock with no apps or addons and still happened. I ended up swapping it out for a new one, and my new one has yet to do it, seems like there's no other option.
As far as I'm concerned, I notice JPM/JPK Roms (I have applied tayutama 1.0.0 and voodoo kernel pre6) has this VIBRATE issue when the phone goes into sleep.
In details:
When the screen goes off (black), in a few seconds, the phone will have a slight vibrate.
If you turn on the screen and play around with it and let it sleep again (screen goes off), in few seconds it will still vibrate again!!
Not only a few seconds after phone sleep it will vibrate, I notice the phone will vibrate on its own (phone is sleep) once in awhile in no specific duration
Anybody experiencing this can let me know what causes it? I do not know whether stock ROMs have this problem coz I always flash another ROM (mostly to deodex) over my stock ROM with either lagfix or voodoo kernel applied right after
I would appreciate if we investigate it in details if this issue is confirmed
have same problem with jp6 firmware ,have posted in jp6 firmware topic about it
Oh, I think this issue is serious enough to have a thread on its own
Anyway do we have a solution/workaround for it so far? Would love to solve this 'bug' as it's kinda annoying at times...
Yep, I get that too, on JP6 .. and all in all.. I am really pissed right now, Voodoo pre6 F***ed up my radio connection .. it detects networks in 3 4 minutes, it connects and then it disconnects in a matter of seconds,...,,, mothaxxxxx
Same problem here with JPM. Im using sztupy 0.1 experimenatal rom, but after reading your posts it seems clear that its not a problem of his room
It's dreaming leave it alone.
Wifes phone refused to send text early this evening, turned phone off, phone has failed to restart since, gets stuck at start up logo and just keeps randomly vibrating.
The phone is running froyo jp6 on voda network
Usually a random vibrate means a process is crashing or has a serious error. Use the alogcat or adb logcat to look at the log immediately after this happens, or if there's nothing there look in the kernel log with "adb shell dmesg".
Got phone to boot but everything is gone, with out a factory reset even external sd card has been blanked out . Missus is well pi#$ed off
Time to go buy her that Iphone 4 shes always wanted Or get used to sleeping in dog house. Your call
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...
Heya all,
So my Galaxy Mini started rebooting itself today.. Anybody knows what to do? I can't give much details only that I thought the problem could be the custom rom (CM7, New Experience). I flashed it back to stock, but it's still doing the same thing, sometimes it'll hold out for 30 minutes but sometimes it restarts and I can't even open Whatsapp before it reboots again.
All I can tell the on/off button for locking isn't always working as fast as it should. Could this button be stuck or something like that?
Also warranty is gone, got water damage from like 1.5 year ago.. Maybe that could still have something to do with it.
Thanks in advance,
Sanderth.
Update: I was just viewing a WhatsApp message and it rebooted itself again, please does somebody have any advice on how to fix this?
Bump: Please does anybody know what the problem could be? Today at school I wasn't even able to send a message via WhatsApp
Edit: I'm pretty sure it always happens a few seconds after I pressed the on/off button to lock. I just tried to lock it, got the prompt where you can enable airplane mode and turn the phone off and I clicked the back arrow, after ~5 secs it rebooted, could something be stuck behind this button or could my ROM be bugged?
Edit2: Well I disassembled my phone, probably something was stuck behind my button and fell out or something else was wrong with it.. But the most important thing is: It works like it should again, locking is going smooth now and it really feels as if my phone was better than before XD
Next time I'll open it first before opening a topic on xda, but well.. Hopefully somebody who will ever have the same problem will find this thread and fix it the same way I did
:thumbup:
Sent from my GT-I9300 using xda premium
Well to be honest, it'll stick to randomly rebooting itself once in a while, less than it was before disassembling and putting it back together again though (From 5 times in one hour to max. 3 on a day). But trying this could never mess something up (as long as you know what you are doing.) At least it's possible to use my phone normally again.
For the people that don't know how to disassemble, use this: http://www.formymobile.co.uk/s5570disassembly.php
Disassemble until you've got the battery compartment of, then just assemble again.
Hi Guys,
I have a serious problem with my Inc S. Lately, after using a few apps (mainly on the bus) the phone will go to the lock screen. A this point when the power button to wake the phone, it will just hang. The backlights will still be on but the phone is unresponsive. I have pull the battery out for 10-15 mins before it will restart. This issue happens at least 2-3 times a day. I can see no reason why this would happen. I have tried a factory reset but nothing works. Any help to resolve would be greatly appreciated.
GiantP2 said:
Hi Guys,
I have a serious problem with my Inc S. Lately, after using a few apps (mainly on the bus) the phone will go to the lock screen. A this point when the power button to wake the phone, it will just hang. The backlights will still be on but the phone is unresponsive. I have pull the battery out for 10-15 mins before it will restart. This issue happens at least 2-3 times a day. I can see no reason why this would happen. I have tried a factory reset but nothing works. Any help to resolve would be greatly appreciated.
Click to expand...
Click to collapse
Telling us your issue is fine. However, we need more information such as your bootloader status as well as what ROM you are currently on (if you are of course)
I have unlocked the bootloader, cwm recovery, but still running stock Rom. Haven't flashed a new Rom as yet. The phone seems to get quite hot, too. I think overheating may be the problem as it won't turn on for 15 - 30 mins after battery has been pulled out, which suggests the phone would need that time to cool? Dunno, just a thought.
Sent from my HTC Incredible S using Tapatalk 2
GiantP2 said:
I have unlocked the bootloader, cwm recovery, but still running stock Rom. Haven't flashed a new Rom as yet. The phone seems to get quite hot, too. I think overheating may be the problem as it won't turn on for 15 - 30 mins after battery has been pulled out, which suggests the phone would need that time to cool? Dunno, just a thought.
Sent from my HTC Incredible S using Tapatalk 2
Click to expand...
Click to collapse
Overheating is most likely your culprit. But its pretty difficult to pull the phone to about 50 degrees you really should watch whats running in your background and what applications you are running. Overheating may damage your phone and I assume you probably won't want that.
Would flashing a new Rom help? Never done it before.
Sent from my HTC Incredible S using Tapatalk 2
Ok, so when the screen blacks out, I can still receive sms. I have turned the screen time out to "never" (as it seems to only lock up when it goes to sleep mode), but it still blacks out after say 1/2 hour and screen becomes unresponsive. Have to pull battery out for a while. Is this a hardware issue rather than a software issue?
This still an ongoing issue, and driving me nuts. When ever the phone goes to the lock screen or after a phonecall, it wont come back on. The touch still works (can play music, etc by touching screen from memory) but the screen wont show anything. Have flashed cm7.2, done wipes, etc with no luck. Any help?
GiantP2 said:
This still an ongoing issue, and driving me nuts. When ever the phone goes to the lock screen or after a phonecall, it wont come back on. The touch still works (can play music, etc by touching screen from memory) but the screen wont show anything. Have flashed cm7.2, done wipes, etc with no luck. Any help?
Click to expand...
Click to collapse
Ok now that is not an overheating issue. That's probably a ROM issue or a kernel issue. I would suggest switching ROMs, maybe CyanVivoX or CyanVivo10.1 if AOSP is your thing. If not then maybe SVHD, Nik Project X Rebirth, or ViperVivo for Sense 4.1 (or Blackout or ARHD if you want Sense 3.6). Happy flashing
After a month of stuffing around and flashing my phone with different tons, I am still having the same problem. The only solution I have found is to install a wakelock app from the playstore, which isn't ideal as the screen stays on, drains battery and everything gets activated when the phone is in my pocket (mates are sick of getting phantom calls from me). The phone is no longer in warranty so I don't wanna take it to a tech.... There has to be a solution. Any further help woyl be greatly appreciated.
Sent from my HTC Incredible S using Tapatalk 4