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
Hi I am not sure what happened but I found someone locally selling a Galaxy Gear for $200.00. I thought that was a pretty good deal so I met up with the person today and got the watch. He showed me it working on his Note 3. He breezed through the screens with his finger. I called him...he took the call on the watch...I mean everything looked fine. Now I must mention I already bought a Galaxy Gear and love it. Been side loading apps and really having fun with it. I thought for this price I could play around with rooting and try some things that I did not want to on my existing gear because I am happy with the way it is working. Figured if I sold it on Ebay eventually I would still make possibly $50.00 when it was all said and done. So the first thing I did was charge up the new Gear ..it was at 87% already but thought it could not hurt. I was trying to figure out how to link TWO gears to my Note 3 and you pretty much just add a new gear and unpair or disconnect the other. So far so good...so I get the option to restore my data....I'm like sweet! Goes through the entire process including with even watch styler. I push a recently configured watch face to the gear. And that's as far as I got. I tried to swipe left and right with no luck. no up or down either. Ok, I figure maybe the buggy watch styler hung up the gear. Hold the power button down on the side and I get the reboot or shutdown...go to hit shutdown and the screen does not sense I am touching it. I tried it over and over and still nothing. Finally my only option was to hold the side power button in....says rebooting...actually comes up shows the time but I still cannot swipe in any direction. I even went as far as to go into the system menu by pushing the side button over and over after the reboot and I did a reset in there but still no touch response. Now If I had not actually seen it working I would have thought the dude pulled a fast one on me and who knows maybe he still did but it WAS working. Out of desperation I called Samsung and gave them my serial number and they told me it is eligible for warranty return...but watch them find it was previously wet or dropped somehow. I do not know if it has been but that would just suck. So much for my good deal. Do any of you extremely smart folks know what I can try or do you think it and I are hosed? I did try USB to see if that made a difference and if I go into the download mode I could launch ODIN and it shows it is detected. I am trying not to totally reset my other gear by uninstalling anything on the phone but I trust you guys so what do think I should do?
Hello guys, I've acquired my New Moto X last monday and I've been using since then. It a fantastic phone and everything else but I have a problem with the moto voice. I use it like, 5 times a day, works perfect, but after a time, and I have a theory that it's conflicting with other apps installed in the phone, it became too slow. Like, i say my activation phrase, it beeps but nothing shows up, only 10 seconds later a very slow and laggy version of the interface. It also happens when I open it directly from the Moto app. After this, I've done a factory reset on the phone, and the Moto Voice came back to life... BUT, after 3 days it started again... Then I done it again... And guess what in 24 hours the same error. The worst part is that I dont' know if they are going to solve this error, I have already reported it but I don't know... And if I send it back to the store to get a new one I'll probably saty almost a month without a phone... Anyone else have this problem? Any solutions
Did you try clearing cache?
Also, are you on the latest version 6.1.10.1?
Yes to both!
I found the OK google feature responds faster and better. Just as long as you don't want to command other apps.
I'm having the exact same issue. It's very slow. Same issues after factory reset. Also - when it does work, works with Google Now, but none of the MOTOX apps like 'find my phone' etc.
any resolution?
Same thing here
I have had the same issue. I tried uninstalling and reinstalling several times with no luck. The few times I've managed to get through the entire voice set up it ends up un-checking my launch phrase with in a few uses and moto voice stops working. I keep providing feedback when the voice app fails and hopefully they will figureboit why this is happening. Happy to hear its most likely not my device and an issue with the app.
I have the same problem and i may have located the problem. Try turning off bluetooth completely and see if the problem still exists?
Does anyone else have this issue? I have a stock Moto X on 4.4.4. I use it at work with a bluetooth LG headset and up until a few weeks ago never, ever had a problem with it. I cant pinpoint when it became to happen, if I had to guess Id say a month or 2 ago, it got to the point where I literally have to keep the phone in my pocket to get a clear bluetooth connection. Now, its to the point I cant even do that. I have to have the phone right in front of me, unobstructed, to get a clear stream. If I walk away from it 2-3 feet it gets terribly scratchy and the audio cuts in and out.
I began to think maybe the headset was going bad. I got out my old Bionic and found I have no issues with the headset. I can walk 30+ feet away with it connected with clear stream. I just bought a car with bluetooth connectivity and also have problems with the bluetooth crashing on the phone, yet my kids phones connect with no problem.
Ive googled the issue and only found a few people that seem to have the same problems. They said it seemed to have happened with the latest update to 4.4.4. My phone shows the last update was August 1. Thats coming up on 3 months ago, that seems a little long ago when the issue first started, but I know Ive been dealing with this for at least 6 weeks. Its possible it has been 3 months.
I have cleared the cache in recovery mode, no help. Short of doing a factory reset I dont know what else to try. One person that had this issue did a factory reset and said it didnt help. So I dont necessarily want to wipe my phone to find out it didnt fix it.
Was hoping the update to 5.0 might fix this, but who knows when thats coming, especially on Verizon.
Any suggestions to this issue?
Quick back story, bought ZW3 and turns out it never made any sounds. Purchased a second one while the first went back to Asus for repair. When I got it back, I confirmed that it was working fine and then I shut it down, out it back in it's original box and put in closet.
After spending the normal time getting the watch and the phone to work as I wanted, I believe everything was working as it should. Then AW 2.0 finally came, and a little more learning, no problem. But then the phone goes to Android 8.0.0 and and I'm back to frustrations, such as no longer when you select your watch in the BT list of paired devices, does it say "connecting" or does the BT icon ever show it's connected, battery life now sucks, blah blah blah.
About 4 weeks ago, ZW3 #2 half the time the sound is low in volume and distorted like a severely blown speaker. So I shut shut it down and pull out ZW #1 and it doesn't want to connect to AW. Eventually I end up defaulting it but holy shizzle sticks! It takes forever to load ll apps and finally update to AW 2.0.... like more than half a day!
Now I bring you to yesterday and ZW #1 stops making sounds altogether AGAIN and on top of all that, I can't get either watch to be seen or therefore connected to AW on the phone. I have repeatedly uninstalled and reinstalled the app on the phone and 90% of the time it opens and sits on a white screen with the logo. Other times it goes to the "Set Up" screen and the first time I set the permissions and such, and after that it goes to the "Select your device" screen but never sees either one.
Now, if I "forget" the devices on the BT setting screen, it pops up with the request to pair and the code, but that makes no difference in AW functioning.
So, What little hidden step am I missing? I should be able to switch back and forth between to identically set up devices, or at least connect to one. So frustrated, plus now I have to figure out how to get Asus to realize that they didn't fix sh!t.
send all three in and tell them to give one good one.
You know you have to have both watches paired to phone, You cant just take second zw3 out and try to use it like it was the first one, do you? Yes? Ok.
Now if there is still problem:
1.Factory reset watch (unpair from phone from within the watch settings)
2.reset wireless connections on phone (will loose all wifi networks and BT paired devices)-but this helped me get rid of wear app misbehaving (like you wrote-forever sitting on splash screen,etc.),
3.clear data and cache of Wear app and then uninstall it
4.Restart phone.
5.Pair the watch.