I have a tilt and for some reason the last couple of days it will just turn its self off. It has done it twice while I was in the middle of a call. Any know what could be causing this. ATT stock ROM... Second one already exchanged one with same problem, No Software installed....
Me too! I have the same issue. I tried to reset Tilt (from Setting options) and it did not solve the problem. I am seeking ways to solve this issue before I have to call ATT.
Please Help!!!
this started happening to me about 1 month ago, it's progressively gotten worse (phone turns off after 2min call even with full battery). At first I thought maybe the phone was overheating because immediately turning the phone back on after it shut-off during a call the phone would get half way through booting and then turn off again.
Luckily my phone is under warranty for another couple weeks (cutting it pretty close!) I called att and they think it's a battery problem. they sent me a new one... I just got it today. Going to do some heavy use and see if I can get it to turn off.
keep ya posted.
charged the new battery completely and then ran it all the way down testing it with phone calls / internet surfing / downloads... no crash or power off. looks like the battery was the problem.
Hi Guys,
Could someone tell me why my 2 weeks old Galaxy S (Service Provider: Bell) turns it self off out of the blue?
It happend twice already, the phone was on my pocket, I pushed the on/off side botton and nothing happens, the screen is pitch black!!
This is an irritating issue as I'm forced to physically take out the phone from the case and remove the battery and put it back on to turn on the phone.
Does anybody whats causing this issue? and how to fix it ?
Your help is much appreciated!
Cheers
Also, I was wondering if I do a factory reset to try solving the random shutting down problem, will I have to re-purchase all the apps I bought from the Market?
Send for warranty is needed I think
Sent from my GT-I9000 using XDA App
Essayli said:
Also, I was wondering if I do a factory reset to try solving the random shutting down problem, will I have to re-purchase all the apps I bought from the Market?
Click to expand...
Click to collapse
No, the info that you purchased the apps is stored in your Google account. So if you use the same Google account as you're using now as your primary account after reset, you can download all those apps for free. (Primary account is the Google account you first associated with the device.)
i had the same problem with 3 different bell vibrants. About 6 days ago, i bought a new sim card from bell for $5, and it has not happened since. I bought my phone from Bestbuy, but bought my new sim card from Bell store because perhaps the bestbuy sim cards are outdated. Hopefully it stays ok.
One thing i did notice was that when my phone would turn off by itself, it was always in an area where there was bad reception. Maybe a link.
I found that it happened when I installed a different launcher other than Touchwiz. I was using LauncherPro, uninstalled it and everything worked fine. I installed ADW and everything is fine so far.
I saw this thread yesterday and was thankful mine hadn't developed this issue. And then last night after about two hours idle time, my SGS switched itself off and the power button wouldn't respond at all. The only way to revive my beloved phone was to do a hard reset (i.e. removing the battery).
For what it's worth, the only "mods" I've made are installing a handful of apps. No new launcher, no custom ROMs etc.
I'm tempted to give Voda a ring and ask for a new SIM. But this really smells more like a hardware fault to me. A faulty SIM shouldn't result in a handset switching itself off, I'd think...
i'v encountered smailar problem , first i thought my phone turned itself off, later i suspected some apps i'v installed ( setCPU, autokiller etc), after while and digging, i found that i'v installed "Android Tweak" , it has an option to disable screen dim, and i'v used that option, so i changed it back and the problem is gone.
in Spain we have the same problem and no solution by now
http://www.htcmania.com/showthread.php?t=126937
Same thing happened to me last night. Maybe a bug with the date?
Rc-Blob said:
Same thing happened to me last night. Maybe a bug with the date?
Click to expand...
Click to collapse
Mine just died again ten minutes ago. I guess it's a possibility, but considering the number of bugs that we're all discovering with the hardware and software, I'm suspecting it's yet another dodgy batch of phones from Samsung.
I just bought two Galaxy S and I am having same problems with both. I called Belll and they said they never had this kind of problem before. I had installed few apps and thought may be those apps were causing the problem, but even after deleting the apps..phones are powering off itself...
Did any one find the solution yet??
Same problem here, and from what i am hearing is becoming frecuent among galaxy owners. Im amazed something this important hasnt made the news , i mean, its a huge malfunction issue .
I had the same issue.
I called up Samsung support and they asked me to do a phone reset. I didn't try that, but I upgraded the firmware and it's gone now. I suspect resetting the phone will also solve the issue.
This happened to me for the first time today as I woke up and it wasn't dark outside. When I looked to see what time it was my phone (that I use as an alarm) was off!!
This is the first blemish on an otherwise outstanding experience. But it is a major one. I will assume that it is somehow related to something I've installed. But I'm not looking forward to figuring it out, since I've got a lot of apps
lockpick said:
This happened to me for the first time today as I woke up and it wasn't dark outside. When I looked to see what time it was my phone (that I use as an alarm) was off!!
This is the first blemish on an otherwise outstanding experience. But it is a major one. I will assume that it is somehow related to something I've installed. But I'm not looking forward to figuring it out, since I've got a lot of apps
Click to expand...
Click to collapse
Good luck. I did a factory restore the other day to see if that would help. It didn't. Like you I use my SGS as an alarm... I woke up two hours late this morning because my phone had switched itself off in the middle of the night.
I'm currently waiting for a replacement handset. I'm not holding my breath that the new hardware won't have exactly the same bug though...
Mine started doing this yesterday...same with a bunch of coworkers that have the same phone. We think it may be related to bad reception.
Sigh
My phone just started doing this in the last couple of days.
I've also noticed sometimes it gets into a state of continuously saying "usb debugging connected" and then "usb connected" and just continuously keeps displaying those even though it has no usb cable anywhere near it..
Havent flashed the phone for about a week now and it was fine for 3-4 days after the flash so no idea what is going on..
Anyone else seen those usb messages? They come and go.. but it seems when they come its usually when my phone turns off..
Kilack said:
Sigh
My phone just started doing this in the last couple of days.
I've also noticed sometimes it gets into a state of continuously saying "usb debugging connected" and then "usb connected" and just continuously keeps displaying those even though it has no usb cable anywhere near it..
Havent flashed the phone for about a week now and it was fine for 3-4 days after the flash so no idea what is going on..
Anyone else seen those usb messages? They come and go.. but it seems when they come its usually when my phone turns off..
Click to expand...
Click to collapse
I've not seen anything like that myself but then I have stuck with stock firmware.
robbiev80 said:
Mine started doing this yesterday...same with a bunch of coworkers that have the same phone. We think it may be related to bad reception.
Click to expand...
Click to collapse
Thats funny...because the only time it has happened to me is at work, where the phone is struggling for reception. It has turned off a total of about 8 times over 1 month. It has never turned off anywhere else (except one other time i was getting bad reception in the forest, and a few minutes later it was off)...strange
I complained about this issue originally in the MavRom thread but was advised this isn’t a known issue with the ROM, so after more troubleshooting, here I am. This is the chain of events:
- Bought the Droid 3 unlocked so I could use it on Rogers
- Instantly flashed CM9, lived with the various issues hoping they’d be resolved soon
- They weren’t, so I started looking for a permanent GB rom. Tried MavRom
- Noticed a day or two later the following issue:
Wifi will just randomly encounter an error and turn off. It typically happens without me noticing, and then I’ll be at home and notice I’m on data when I should be on wi-fi. If I try to turn it on using the power widget it will briefly light up as though it’s trying to turn on, but eventually give up. If I try to turn it on through settings, where it normally would say “wifi is on” or “wifi is off”, it just says error. I used to reboot the phone to fix it, but just realized a few weeks ago that I just need to turn airplane mode on and off, then turn wifi back on.
This isn’t the worst thing in the world but it should not happen. There is also no pattern to it, or any apparent triggering event. It can happen half an hour after the last time, or it can go a whole day without happening. My phone is in essentially the same state all night while I am sleeping, so the same thing should happen every time. But sometimes I wake up and the error has occurred, other times it hasn’t.
So as I said, I complained in the MavRom thread, they insisted it wasn’t related to Maverick. So I flashed Eclipse to try it out. Right away I realized that this error was happening in Eclipse too. So, somewhere in all the clearing data and cache and flashing of ROMs, etc, I managed to wreck the wifi in a way that reflashing doesn’t appear to fix.
Realizing this, I tried to go all the way back to stock to see if that would work. I used the .906 to .890 patch (since it’s the only way to go back to .890 or at least mostly), then had to use quick unbrick to fix it when it wouldn’t start up. Everything was fine; it was a stock motobloat Droid 3 again. After a few hours of usage I was pretty convinced that the wifi error was gone.
So I installed Eclipse again. For most of the day everything seemed fine but the same problem reared its ugly head last night just like it used to. It sounds like I need to somehow update the part of the Gingerbread OS specifically related to wifi but I have no idea where to go from here. Has anyone else seen a problem like this before? Any troubleshooting advice?
seventieslord said:
I complained about this issue originally in the MavRom thread but was advised this isn’t a known issue with the ROM, so after more troubleshooting, here I am. This is the chain of events:
- Bought the Droid 3 unlocked so I could use it on Rogers
- Instantly flashed CM9, lived with the various issues hoping they’d be resolved soon
- They weren’t, so I started looking for a permanent GB rom. Tried MavRom
- Noticed a day or two later the following issue:
Wifi will just randomly encounter an error and turn off. It typically happens without me noticing, and then I’ll be at home and notice I’m on data when I should be on wi-fi. If I try to turn it on using the power widget it will briefly light up as though it’s trying to turn on, but eventually give up. If I try to turn it on through settings, where it normally would say “wifi is on” or “wifi is off”, it just says error. I used to reboot the phone to fix it, but just realized a few weeks ago that I just need to turn airplane mode on and off, then turn wifi back on.
This isn’t the worst thing in the world but it should not happen. There is also no pattern to it, or any apparent triggering event. It can happen half an hour after the last time, or it can go a whole day without happening. My phone is in essentially the same state all night while I am sleeping, so the same thing should happen every time. But sometimes I wake up and the error has occurred, other times it hasn’t.
So as I said, I complained in the MavRom thread, they insisted it wasn’t related to Maverick. So I flashed Eclipse to try it out. Right away I realized that this error was happening in Eclipse too. So, somewhere in all the clearing data and cache and flashing of ROMs, etc, I managed to wreck the wifi in a way that reflashing doesn’t appear to fix.
Realizing this, I tried to go all the way back to stock to see if that would work. I used the .906 to .890 patch (since it’s the only way to go back to .890 or at least mostly), then had to use quick unbrick to fix it when it wouldn’t start up. Everything was fine; it was a stock motobloat Droid 3 again. After a few hours of usage I was pretty convinced that the wifi error was gone.
So I installed Eclipse again. For most of the day everything seemed fine but the same problem reared its ugly head last night just like it used to. It sounds like I need to somehow update the part of the Gingerbread OS specifically related to wifi but I have no idea where to go from here. Has anyone else seen a problem like this before? Any troubleshooting advice?
Click to expand...
Click to collapse
I would sbf and stay on stock, if it reappears, bring it to verizon. Im afraid I've never heard of this problem before. Since it happened with 2 separate roms, it seems more like hardware. Otherwise the sbf should have fixed it.
Sent from my XT860 using xda premium
Odd. I know that this was a problem on most ICS roms. Haven't heard of it happening on a GB rom. This happens to me on Gummy 1.2. Same symptopms: wifi kills with no cause and no pattern. I toggle airplane and keep browsing as I only turn on wifi when I am actively using it.
Sent from my DROID3 using xda premium
Just bought a xperia TX few weeks ago
But I feel that there are some problems during I use.
Sometimes when I want to wake it up from standby mode
It doesn't wake up and the screen keeps nothing appears
But the notification light still works, so that the phone should still working and not ran out of battery
The solution I use is pull the battery off and place it again....
This happened about 4 times in a week...
My phone is 7.0.A.3.197
even it is rooted or not, the situation still here.
Is there any idea to solve it?
Had exactly the same problem with my T and tried every posible documented solution but nothing worked. So I just dropped my T to service yesterday and expecting to collect it tonight, after that we'll see what the problem really is. The guy from sony said they have had this issue in the U and Sola but nothing reported so far on the T. He claimmed however that for this issue is to be settle in first quarter 2013 via update of course, in those devices. But did not mention something about this in the T.
In anyway I don't feel like is software related, my bet goes to a hardware issue in some unlucky devices.
I started a post here called Xperia T SOD so keep an eye on it as later on I'll report my findings after the Sony Service job.
Sent from my MB860 using xda app-developers app
Sorry for push back the post.
I noticed that this situation happened when I connected to my home's wifi for a long time.
Because during the holidays, the times of my phone suddenly dead from sleeping mode is increased.
I am using mobile data at outside and Wifi at home, and the situation always happen at home, so that I think that the phone maybe dead from sleeping mode in a significant condition, that means the Wifi connection.
I tried to set the wifi keep on during sleep only when plugged in, then the the situation haven't happen again in previous two weeks!:laugh:
I received the latest update to 4.4.4 this past Wednesday. This is the update that included the HTC Eye Experience. The update went smooth and everything was all good until I was driving home from work. The phone randomly rebooted itself and ever since, I cannot get Wi-Fi to turn off. It stays off for approximately one minute and then turns right back on. I have searched this forum and others all day with no solution seeming to help. I also hard reset the phone earlier today but the problem persists. Anyone had this issue or have any solutions? Thank you in advance!
schakab said:
I received the latest update to 4.4.4 this past Wednesday. This is the update that included the HTC Eye Experience. The update went smooth and everything was all good until I was driving home from work. The phone randomly rebooted itself and ever since, I cannot get Wi-Fi to turn off. It stays off for approximately one minute and then turns right back on. I have searched this forum and others all day with no solution seeming to help. I also hard reset the phone earlier today but the problem persists. Anyone had this issue or have any solutions? Thank you in advance!
Click to expand...
Click to collapse
Do you Sprint Connection Optimizer running? That'll keep Wi-Fi on. See this http://support.sprint.com/support/t..._Optimizer_on_or_off_HTC_Onereg_M8/51761-1469
henderjr said:
Do you Sprint Connection Optimizer running? That'll keep Wi-Fi on.
Click to expand...
Click to collapse
Thanks for responding! Its not Connections Optimizer. It has been turned off from day 1 but I did recheck and it is still off. My M8 is not rooted and completely stock. It worked great up until this update. I tried soft reset and hard reset to no avail. There is a message that pops up in the notification bar sometimes (Wi-Fi notification with a red triangle) that says setup has not been complete but nothing happens when I click on it and it goes away. Sprint is, of coarse, no help at all. They want to send me a new phone but I really don't think this is a hardware issue. Maybe a bad download?