Related
Well, what the title says. It's becoming extremely annoying. Any suggestions?
what rom are you on?
I was on stock UCLA3, but when this problem occured I completely went back to stock. Still exists.
have you tried to do a 3e recovery factory restore?
I don't know what to do, honestly. I'm open to any suggestions! I'll look that up, thanks in advance.
Flash a custom rom with good kernel!
Well, I returned the phone to its original state. Exactly how I bought it.. The problem still exists. I don't think this is a kernel/rom issue.
What does ATT look at when they do exchanges? My counter says 2, is that a bad thing? Or can I just say I was trying to restore it because it kept shutting off and I didn't exactly know what I was doing? It has to be something with the hardware.
MAGiK9 said:
Well, I returned the phone to its original state. Exactly how I bought it.. The problem still exists. I don't think this is a kernel/rom issue.
What does ATT look at when they do exchanges? My counter says 2, is that a bad thing? Or can I just say I was trying to restore it because it kept shutting off and I didn't exactly know what I was doing? It has to be something with the hardware.
Click to expand...
Click to collapse
Yeah thats a bad thing, but they probably wont say anything. Don't mention anything about the counter
I started having the exact same issue this last weekend, took my phone into At&t warranty center, they replaced the battery and did a reflash back to factory rom. Still had the issue after that. The problem didn't start till after I took it out of my otter box and started taking the back off to pull the battery for rooting and flashing roms. Since i have put the phone back in the otter box case I have not had it restart on my yet. I am thinking it is a loose back cover and the battery is being knocked loose and then back in place hence the restarts. Just some of my observations from my own experiances with this same problem.
Ironically, mine has never happened until I took it out of the Otterbox Commuter case.
luckily i haven't had this issue, and i have removed it like 8-10 times before learning I didn't have to...
I took my phone to the att store so they could look at it.. I explained what was going on and the guy told me he was going to check the counter.. BUT he never did. He ordered me a new battery, and if that does not work they will send me a new phone. However, i'm going to get the new phone anyway.
Reboot issues and battery
Ok, same problem here, ICS leaked 4.0.3, Samsung Galaxy S2 skyrocket. Thought it was setcpu and/or busy box, not.. I notice that when I moved my phone in an odd manner it would reboot. Removed the battery cover and noted that there was play in where the battery sat, so much so that I was able to stick my finger nail into the separation, I don't know call it a half a cm. Any way, I took some note book paper, made a wedge so the battery was nice and tight... so far so good. Will let you know.
I'm not sure if this will be any help or not. My phone has done the same thing a couple of times and at least twice I've noticed that it was because I had the phone in my pocket and I was accidentally holding down the power button when I was bending over/squatting/etc. As for the other times it has restart on its own, I have no idea. It's been at least a month since those happened though.
So Im a little new to this, and hopefully I won't be asking things that can be easily found, since i did try looking for answers..after having my verizon s3 for over a month now (still stock), im having a few different issues/annoyances, and can't figure out how best to resolve them.
1) Whenever i restart my phone, i get voicemail notifications, even though I have no new notifications.Ive seen a few different solutions for it, namely leaving yourself a voicemail, then deleting it and it should make it go away...but it doesnt. i can only get a temporary fix, which is to go and force stop the Phone application, but next time my phone restarts the same issue happens again.
2) a few times my phone will hotboot..or atleast thats what i think its called. basically the phone will freeze, then after a minute or two it will go back to the lock screen..but if i leave it alone, or if i try to run anything, it will again freeze and go to the lock screen. this even happens when i restart my phone. the way around it i found is to unlock the phone, then immediately turn off the screen. after 15-20 seconds, i can turn the screen on again and it will work fine. i read some topics on this but they seem to be random occurrences, and i didnt really see anyone saying it happens on every startup..
3) android_system/gsiff_daemon killing me battery- so over the last week ive seen that this is really killing my battery. it always takes up about 50% of my battery, no matter what i do.it also seems to cause the phone to get really hot. the topic i read below, it seems like a root cause isn't found yet, and the only way to resolve it without rooting is to restart your phone, but for me it seems so always come back at the top..
http://forum.xda-developers.com/showthread.php?t=1755180
i'm wondering if rooting and unlocking the bootloader will help at all. the last time i rooted a phone was like 2-3 years ago with my incredible, so im a little cautious about doing it and accidently bricking my phone. i was going to follow section 2 of this guide, there shouldnt be too much of a risk of it going wrong right? http://forum.xda-developers.com/showthread.php?t=1762709
y2jasper said:
So Im a little new to this, and hopefully I won't be asking things that can be easily found, since i did try looking for answers..after having my verizon s3 for over a month now (still stock), im having a few different issues/annoyances, and can't figure out how best to resolve them.
1) Whenever i restart my phone, i get voicemail notifications, even though I have no new notifications.Ive seen a few different solutions for it, namely leaving yourself a voicemail, then deleting it and it should make it go away...but it doesnt. i can only get a temporary fix, which is to go and force stop the Phone application, but next time my phone restarts the same issue happens again.
2) a few times my phone will hotboot..or atleast thats what i think its called. basically the phone will freeze, then after a minute or two it will go back to the lock screen..but if i leave it alone, or if i try to run anything, it will again freeze and go to the lock screen. this even happens when i restart my phone. the way around it i found is to unlock the phone, then immediately turn off the screen. after 15-20 seconds, i can turn the screen on again and it will work fine. i read some topics on this but they seem to be random occurrences, and i didnt really see anyone saying it happens on every startup..
3) android_system/gsiff_daemon killing me battery- so over the last week ive seen that this is really killing my battery. it always takes up about 50% of my battery, no matter what i do.it also seems to cause the phone to get really hot. the topic i read below, it seems like a root cause isn't found yet, and the only way to resolve it without rooting is to restart your phone, but for me it seems so always come back at the top..
http://forum.xda-developers.com/showthread.php?t=1755180
i'm wondering if rooting and unlocking the bootloader will help at all. the last time i rooted a phone was like 2-3 years ago with my incredible, so im a little cautious about doing it and accidently bricking my phone. i was going to follow section 2 of this guide, there shouldnt be too much of a risk of it going wrong right? http://forum.xda-developers.com/showthread.php?t=1762709
Click to expand...
Click to collapse
I would start with a factory reset and see if that solves your problems. keep in mind it will erase your apps and settings. VOL+/HOME/POWER
i was hoping to avoid factory reset since i didnt want to reset up my screens and apps, and also for the voicemail and gsif_daemon issue from what i read it keeps coming back. but if thats the best option i guess i have to suck it up and do it then
Root and unlock BL won't fix problems. That will only allow you to modify your phone more. I think you have to bite the bullet on this one. Test it out good before you install all your apps if you reset.
Sent from my SCH-I535 using xda app-developers app
You could just have some rogue apps. Many apps fail miserably just going from ICS to JB. I hated TouchWiz. Rooting and Unlocking Bootloader was the best thing that has happened to my S3. Rooting is very safe and its very easy to got back to stock. My battery was terrible on stock. 4G is going to eat your battery up quickly as opposed to just Wifi. All the alternative launchers can backup you home screen (Apex/Nova etc) and all your apps should be backed up in Googles cloud should quickly get pulled back down after a factory reset or ROM install
kanc3r said:
You could just have some rogue apps. Many apps fail miserably just going from ICS to JB. I hated TouchWiz. Rooting and Unlocking Bootloader was the best thing that has happened to my S3. Rooting is very safe and its very easy to got back to stock. My battery was terrible on stock. 4G is going to eat your battery up quickly as opposed to just Wifi. All the alternative launchers can backup you home screen (Apex/Nova etc) and all your apps should be backed up in Googles cloud should quickly get pulled back down after a factory reset or ROM install
Click to expand...
Click to collapse
hm ok. 4g isn't really the cause. in the area where my apartment is, 4g isn't even available yet, i only get a chance to use 4g on weekends when i come visit family/friends. otherwise i use the "phone info" app to turn 4g off. also my voicemail issue is resolved now, i messed around a bit more between voicemail and google voice and finally found the rogue message that was left. i'm thinking if i root and unlock, i can at the very least install a different kernal to improve battery life, to possible negate the gsiff_daemon issue.
s3 turning off randomly requiring battery pull to restart. here is the breakdown to date problem occured,verizon tech sent replacement phone, that phone did it so sent it back and kept original phone, replaced sims card, problem still there, replaced battery, problem still there replaced phone again, still there, replaced sims card and battery again,guess what phone is still shutting off randomly, stock rom,factory mode (no apps)nothing not even email linked all software ota up to date. all is documented by verizon and and sumsung but everytime i talk to them all i get is the same old we can send you a like new phone after all the resets and ect., i dont want another s3 that is reman wich i know does they same thing and i didnt really want to exchange what i thought was the best for a droid wich verizon wants to do and sammy wants to send reman. i have already had two other reman phones that do the same thing. now here is the kicker i own 3 total s3's and now guess what one of the other is doing it now too. is there anybody else having this problem? is there a way to track what is running when it shuts down?would a different kerrnel help? would a different rom help? could this be my account with verizon? any help at all i dont know what to do?
more info
i am starting to think this is a problem with the screen not waking up and staying dark and not necessarly shutting down. any ideas on ways to check this?
coop245 said:
i am starting to think this is a problem with the screen not waking up and staying dark and not necessarly shutting down. any ideas on ways to check this?
Click to expand...
Click to collapse
Try another rom although it sounds like an app. Can't be the phone on that many of them. You only one reporting this problem so has to be something you are putting on phone.
prdog1 said:
Try another rom although it sounds like an app. Can't be the phone on that many of them. You only one reporting this problem so has to be something you are putting on phone.
Click to expand...
Click to collapse
both phones are doing this on stock. no apps installed
My friend had 8 replacements through verizon before he got a good one. So try a couple more times maybe. I know it is really inconvenient but honestly the GS3 is the best Android on Verizon right now (arguably atleast) and they probably won't let you trade up to a Razr HD Maxx which is the only one I would recommend.
I'm having the same problem apparently. I just bought this phone used and activated it monday night. That night, i plugged the phone into the charger while i slept and the phone shut off overnight. Phone wouldnt turn on with the power button - required a battery pull to restart.
Going through tuesday, the phone worked fine. However, in the evening, the phone was idle for a few hours, and when I went to check it before going to bed I found it had powered off again! Required another battery pull to restart...plugged it into the charger, and went to sleep. When I woke up, I again found (for the third time) that the phone had powered down, and required another battery pull to restart.
Going into wednesday, phone is working fine. Then I leave it idle in the afternoon for a few hours during work, and when I get ready to drive home, I find it is again powered down, requiring a battery pull to restart (fourth time in less than 2 days).
Now I go to visit verizon, and the rep tells me (after I think he was looking through some company forums for answers) that I should try clearing the cache from every app, since maybe the data was corrupted during my OTA update to JB (which i installed monday night), and some app was causing this problem. So I do that, and the same thing happens again overnight...battery pull etc...
I'm figuring next I'm going to do a factory data reset, possibly tonight. This is supposed to be my sister's christmas gift! Hah...trying to work the bugs out before tuesday. Any thoughts?
Starting a post with I'm not crazy sound like something a crazy person would say.... just saying.... But I agree with the earlier post that it could be app or rom based and only effecting the screen. These are the options I see you having:
1. Try freezing any apps you've installed one at a time and see if it stops
2. Make nandriod and try another rom and then come back if that doesnt fix it
3. Try this thread to clear everything and upgrade http://forum.xda-developers.com/showthread.php?t=1984436
-This method formats internal and external sd card AND bumps you up to rooted JB in the process. Use VRBLK3.
4. Get a replacement phone
KjK89 said:
Starting a post with I'm not crazy sound like something a crazy person would say.... just saying.... But I agree with the earlier post that it could be app or rom based and only effecting the screen. These are the options I see you having:
1. Try freezing any apps you've installed one at a time and see if it stops
2. Make nandriod and try another rom and then come back if that doesnt fix it
3. Try this thread to clear everything and upgrade http://forum.xda-developers.com/showthread.php?t=1984436
-This method formats internal and external sd card AND bumps you up to rooted JB in the process. Use VRBLK3.
4. Get a replacement phone
Click to expand...
Click to collapse
These options might work for the OP, but only #4 could work for me since i'm not rooting this phone (its for my sister). If I find a fix for my issue, i'll post here.
Are you guys using an sd card? If so it might be a corrupt file that the system goes over and gets stuck on, messing the cell up. Did you try making a backup on pc, formating your card (fat32) and putting you stuff back on it? Or take the card out and see if you get the same problem without it. If you're going thru all the replacements then its gotta be something that you use in common with all of em. GL!
I rarely start a thread and i typically search first and i did that already but couldn't find an answer or someone else with the issue...
So my problem is simple but annoying... When i snap a picture with the stock camera app and flash turned on, randomly my phone shuts off and will NOT turn on again until i do a battery pull... I say randomly because it doesn't always happen... But it happens quite often...
I haven't tried with a 3rd party camera app because I prefer to use stock apps mostly... So I'm not sure if its app related or hardware related... I'm leaning towards hardware because I've had this issue since running 4.1.2 ROMs and I've tried multiple stock/modified camera apps to no avail... Currently on 4.2.1 ROM with of course the 4.2 camera...
Torch toggle works fine, as well as turning on the flash while recording video... This ONLY happens when the flash comes on for taking a photo... And again it only happens randomly...
Anyone else experience this or know how to fix it?
Sent from my Nexus S 4G using Tapatalk 2
the1dynasty said:
I rarely start a thread and i typically search first and i did that already but couldn't find an answer or someone else with the issue...
So my problem is simple but annoying... When i snap a picture with the stock camera app and flash turned on, randomly my phone shuts off and will NOT turn on again until i do a battery pull... I say randomly because it doesn't always happen... But it happens quite often...
I haven't tried with a 3rd party camera app because I prefer to use stock apps mostly... So I'm not sure if its app related or hardware related... I'm leaning towards hardware because I've had this issue since running 4.1.2 ROMs and I've tried multiple stock/modified camera apps to no avail... Currently on 4.2.1 ROM with of course the 4.2 camera...
Torch toggle works fine, as well as turning on the flash while recording video... This ONLY happens when the flash comes on for taking a photo... And again it only happens randomly...
Anyone else experience this or know how to fix it?
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
The first thing I would do is flash factory Google. This will rule out it being a ROM issue. If the problem is so there then yes it is a hardware issue.
Sent from my Nexus S using xda premium
Great suggestion... I'll try that when i have a computer to back everything up and make sure i can root again!!
Sent from my Nexus S 4G using Tapatalk 2
I've seen that happen with a bad battery once. Would occur more often at low charge percentage too, but was relatively fine at 100%. Took a while to figure out what the heck was going on
polobunny said:
I've seen that happen with a bad battery once. Would occur more often at low charge percentage too, but was relatively fine at 100%. Took a while to figure out what the heck was going on
Click to expand...
Click to collapse
Strangely, it was doing it before i got a new battery a couple months ago... I sorta felt my battery was bad so i went to get a new one from the sprint store... The guy said because "It was rooted and the phone had so much awesomeness.." it was draining the battery faster... I told him a quick reason why i thought it had to be the battery and he just gave me a battery from the drawer without doing any paperwork or anything... My battery wasn't feeling any better after the change and i still had issues with flash...
I think I'll just take some photosphere pics and well lit shots... Who needs flash anyways? Lol
Sent from my Nexus S 4G using Tapatalk 2
I have the EXACT same issue however long pressing the power button turns on the phone instead of pulling the battery. It also started happening to me only on jelly bean. My GF has the same problem.
I can also tell you it happens with camera zoom FX as well but this cannot be a hardware issue since it only happened in jelly bean. It cant be that "suddenly" our phones developed a problem.
Is nobody using a nexus S to take photos or what? Or is it just a few unfortunate users affected by this?
Thanks for that post... Now I know I'm not alone here lol... I too noticed it with JB... Its %~°^¶©£ annoying... I wish a dev would look into it... I think it may have something to do with the flash having that instant jolt of high voltage... Idk because I'm no expert... I found a 50/50 chance of making it work correctly... If you hold the shutter button to let it focus, then let it snap, there's a chance it won't shut off... Just something to try and see if it helps!!
Sent from my Nexus S 4G using Tapatalk 2
just did a complete factory restore back to 4.1.1 unrooted and everything... forgot to test the camera... i rooted again and installed custom recovery... tested camera out several times... no issue at all... tested some more... no issues... decided it WORKS!! so i flashed cm10.1 and updated everything again... tested camera and OFF!!! FU%$&*&@&#&^$%$^@&$^&$^^%$#^%@*@*@&&#^*&@^#*&^@#*^ i'm at a loss for what to do here... i'm glad one other person reported this... but there HAS to be more people out there with this issue...
test it... make sure flash is ON and snap a few pics... maybe a close pic out of focus, etc... idk what else to do... it worked fine unrooted...
I've had this issue happen randomly to me too...but usually only when my battery is low. And it is VERY annoying when it happens.
Sent from my Nexus S 4G using xda app-developers app
PartimusPrime said:
I've had this issue happen randomly to me too...but usually only when my battery is low. And it is VERY annoying when it happens.
Sent from my Nexus S 4G using xda app-developers app
Click to expand...
Click to collapse
doesn't matter my battery level... it happens on my charger too lol...
I didnt have this problem last night on a wedding thankfully as that would have been embarrassing, lots of pics were taken with flash. Its the sheer randomness of this that it makes it so hard to diagnose. :S
I've been having exactly the same problem. I cannot relate it to Battery Levels, as the battery drains sooo fast since I got the ICS upgrade.
I am now on the Factory ROM 4.1.2 and it is all problems. I am thinking of going back to Ginger Bread... them were the days!!!
J.
if you read above, it worked fine for me when i flashed 4.1.1 factory image... something to do with 4.2 i guess... idk... i'm not stressing it so much... i've learned not to use my camera when its dark or low light lol...
have the same problem
Do you have a link to the stock 4.1 ROM?
ejohn3288 said:
Do you have a link to the stock 4.1 ROM?
Click to expand...
Click to collapse
it wasn't a ROM, it was the factory image from returning the phone to stock with the program i used to root it... i've given up on pictures with this phone haha
Its a Battery Problem
I'm suffering from this same issue and after downloading several camera app to no avail, the issue is finally resolved. From my experience, I can safely conclude that my was a hardware battery issue. At first I didn't believe it was a battery problem. I decided to go to different stores and tried several batteries but all shut down the phone when the flash on/flash auto + taking a snap is executed. Then, I pulled out the battery from my friend's brand new S3 and inserted it in my phone's battery compartment, fire on the phone and voila the camera flash worked like a charm without shutting down the phone. I used the same old battery on the new S3 low and behold, the new S3 inherited the flash+camera=shutdown issue instantly.
Same Issue on SGS2 Hercules
Having this issue after flashing a ROM on my GS2 Hercules, good thing I only experience it when my battery level is below 25%. But it would really be a pain if I would want to take a picture with a flash while my battery is low.
Have anybody tried other solution or troubleshooting aside from trying a different/new battery.
similar problem here...
the same thing happens to me, but with the difference that i run stock 4.1.2 rooted, and when the phone die after the led flashes, i just press pwr button and the phone turn on like never was happened.
i think it's a problem of corruption of something in the system, if i do a factory reset, for some limited shot the camera+led works, after that the phone die instantly.
similar problem with front camera, if i switch from back to front the camera service crashes and i can't do anything for make it working (manually stop the gallery process, reboot, cleaning data of gallery process), just wait some days and the process came back working (just for the rear camera).
sometimes i notice that while the stock camera app doesn't work, the Whats app camera keep working also with flash!
Rookie91 said:
similar problem here...
the same thing happens to me, but with the difference that i run stock 4.1.2 rooted, and when the phone die after the led flashes, i just press pwr button and the phone turn on like never was happened.
i think it's a problem of corruption of something in the system, if i do a factory reset, for some limited shot the camera+led works, after that the phone die instantly.
similar problem with front camera, if i switch from back to front the camera service crashes and i can't do anything for make it working (manually stop the gallery process, reboot, cleaning data of gallery process), just wait some days and the process came back working (just for the rear camera).
sometimes i notice that while the stock camera app doesn't work, the Whats app camera keep working also with flash!
Click to expand...
Click to collapse
same issue with the nexus 5.. taking pictures works and then suddenly shuts down the phone, the power button can't wake the phone and the only way to get it to turn on is to plug it into an outlet.. very annoying.
that said I looked around the forums and it seems like a hardware battery issue, when the voltage supplied is too low or high or something
flash has caused my phone to shut off.
got GS3 SCH-i535 I've noticed the flash causing the screen to black out completely and shut off phone. I usually have to pull battery. its done it on 4.2 and 4.3 probably even 4.1 i dont remember I'm currently running 4.4.2. it just did it again which has prompted me to look online. as glad as i am to know im not the only one. is there any ****ing solution???
Everything was fine on the phone until I tried out AOKP 4.2.2 alpha 2 a week ago, When I had the rom installed the phone would randomly shut down. I thought it was because the rom was not stable enough so I flashed CM9. On CM9 the phone would shut off every five minutes it was that bad. I then installed Miktouch 0.7 and the shutdowns for the most part stopped. The phone will shut down now and again and it always shuts down after I use youtube for 10+ minutes or use the camera for several minutes.
I tried to revert to stock and see if that fixed anything but when I boot into the bootloader it looks for PG59IMG and says no image found and nothing happens. I got the PG59IMG from this thread: http://forum.xda-developers.com/showthread.php?t=1878329
Any help is appreciated.
I swear it sounds mechanical...maybe battery related. Just starting out of the blue like that and it being cross ROM and all. It should just flash that file automatically from hboot though. Are you sure you copied the file to the root of your SD card? Did you relock your bootloader with *fastboot oem lock* before running it? Sometimes it doesn't like it if the usb cable is still plugged in. (for some weird reason) If you're still S-On, did you flast the boot.img file thru adb with *fastboot flash boot boot.img* after flashing your ROM?
Oh yeah, you won't be able to flash that PG59IMG if it is newer than the hboot version listed in your bootloader right now. That is until you get S-Off with the wire trick.
Check some of that stuff out & get back to us.
I agree it sounds mechanical, most likely a bad battery.
I confronted similar behavior over the weekend and a testing with a new battery allowed me to point a finger at an older, aftermarket battery as causing the shutdowns.
Sorry for the delay in the reply - real life got in the way.
I thought it was also mechanical but the shut downs are MUCH less frequent in Miktouch than on ICS roms so I thought it may have to do partially with the software.
I'm S-off, used the revolutionary method years ago. Never issued the "fastboot oem lock" command and I've never done anything related to fastboot. The stock image was in the root of the sd card.
When the phone does shut down it doesn't matter if take out the battery or do anything else, I can't get the phone to start back up until 20 mins later or so. The phone will certainly shut down if I use the camera or use youtube so if there is a way I can grab a log or something that could help let me know
I've had very similar issues, since installing a CM 10 alpha, and now on 10.1. The first couple weeks when I first rooted/flashed CM 10 were fine, but then it started rebooting one day, and never has stopped. Stock battery, no reboots prior to that, S-On, flashed the boot.img for each rom, and it's doing this with both CM 10 and CM 10.1. Does that also sound like battery, since it's the stock battery which has always worked fine? Also, it seems heat/intensity related - if I'm playing a game, using GPS, or talking a long time, that's when it tends to happen, and then it tends to happen right at/near the lock screen for a while after that until it's cooled down (perhaps that screams battery, but since it always restarts fine/has power I would have guessed it had to do with the processor or kernel). Thanks in advance for any advice!
Could be the battery...
I agree with the other posters. I had the experience of lots of random reboots a while back when I was working my way through sverhagen's 9.1r3+ ROMs. But, it just turned out that my stock battery had given up the ghost. Swapping to one of the gold batteries fixed the problem. I tried the stock battery in the interim for a brief stint and switched back to the gold, as the stock battery still caused random reboots. So maybe its time for a battery refresher
Faizt20 said:
Everything was fine on the phone until I tried out AOKP 4.2.2 alpha 2 a week ago, When I had the rom installed the phone would randomly shut down....
Click to expand...
Click to collapse
Thanks, guys, I just ordered a battery, when it gets here I'll confirm whether that fixed it or not. Much appreciated, didn't realize batteries could go wonky in that way!
presin16 said:
Thanks, guys, I just ordered a battery, when it gets here I'll confirm whether that fixed it or not. Much appreciated, didn't realize batteries could go wonky in that way!
Click to expand...
Click to collapse
Yeah....the little suckers are on a power trip I think.
i've been having some shut down issues for a while, on different ROMs so I don't think it's that. whenever i'm using it i don't have any issues (unless it's a known ROM thing, that's separate). even during the day when i'm not using it, it hasn't shut down or anything. the issue is that a lot of times when i wake up, i find that the phone has been shut down. i charge it overnight. so, my best guess is that i should stop doing that, maybe the battery is bad, it can't handle that for that long?
idk any ideas would be helpful. i'm considering buying a gold battery anyway
Did you try the new Battery ?
I was have random shutdown and lockup problems. The phone would lock with a blank screen and I'd have to pull the battery to get it back.
Am running SilverL's CM 10.1. I might be a coincidence, but I backed off on the aggressiveness of the CPU settings (in the performance menu) and the problem went away.
I'm currently running a min/max = 128/1242.
I'm trying not to post a new thread so I'll post my very similar problem.
I got this phone about a year ago. I put Miktouch on it and was experiencing random shut downs all the time. I believe I posted on here and I can't remember the responses. As the mytouch q kinda sucks and I want a solid phone. I gave it another attempt this time with CM 9.1.0. When I used the camera once it shut down and restarted I think. Then I got a solid few days before it started going wanky again. Today alone I've had like 5 restarts. From what I've searched around it seems the problem here is the battery? This is stock battery and I got the phone used off ebay. I think I used stock rom like a week before rooting and putting Miktouch on it.
edit: For some odd reason my background also changed. Charged the phone backup. It turned off again.
If you've flashed any ROMs here to the MyTouch Q then that's your problem. It isn't this phone. These forums are for the HTC MyTouch 4G Slide. A much more powerful phone with a different manufacturer & motherboard. If you have S-Off go to their forums, wipe...wipe...wipe & reflash one of their ROMs. You're lucky you're not bricked.
WeekendsR2Short said:
If you've flashed any ROMs here to the MyTouch Q then that's your problem. It isn't this phone. These forums are for the HTC MyTouch 4G Slide. A much more powerful phone with a different manufacturer & motherboard. If you have S-Off go to their forums, wipe...wipe...wipe & reflash one of their ROMs. You're lucky you're not bricked.
Click to expand...
Click to collapse
I know. I'm talking about two different phones in the same post. I bought this phone (Mytouch 4g Slide) last summer but shortly started having problems. As I didn't want to deal with it I went back to my slowly dying touchscreen on my G2. When that finally died (touchscreen) I just bought a mytouch q as I wanted a phone that worked. This was my first new phone in a long time.
I am NOT trying to install any roms for the MyTouch Q on the MT4GS or the other way around.
S-OFF should be off on the 4G slide. Pretty sure my mytouch Q is still rooted though. It sucked at running CM 9
Sorry. Somehow I got confused. That being the case, it sure does sound like some type of a hardware issue instead of a software one.
WeekendsR2Short said:
Sorry. Somehow I got confused. That being the case, it sure does sound like some type of a hardware issue instead of a software one.
Click to expand...
Click to collapse
Yeah, from what I read it could be a battery problem. Going to go with this Anker battery as its the only reliable battery I can find that doesn't cost an arm and a leg.
Anker Battery
Yeah I'd start with a new battery myself, either a new OEM or an anker, both are cheap on eBay. Also look for a post where me and weekends were discussing the emmc of this phone, bear in mind I have zero proof, but I got a suspicion there may be multiples they put in here and some worse than others.
If the battery won't work then I would repartition the whole dang thing, either by returning to stock and the rerooting and resoff, or by at least flashing the same bootloader on top of the one you currently have.
Just some ideas, but if you want a better idea of what's causing your issue, pull a logcat
Sent from my Nexus 7 using xda premium
demkantor said:
Yeah I'd start with a new battery myself, either a new OEM or an anker, both are cheap on eBay. Also look for a post where me and weekends were discussing the emmc of this phone, bear in mind I have zero proof, but I got a suspicion there may be multiples they put in here and some worse than others.
If the battery won't work then I would repartition the whole dang thing, either by returning to stock and the rerooting and resoff, or by at least flashing the same bootloader on top of the one you currently have.
Just some ideas, but if you want a better idea of what's causing your issue, pull a logcat
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I have a theory of whats causing it. If I extensively use the phone the battery warms up which gets to the point it shuts down. Thus if the battery is still too warm and I turn the phone on then it will just keep shutting down. Of course I can't do this until I'm home for the day as I'm out and about this weekend.
edit:
I used the Revolutionary way to turn s-off which is permanent.
I get random shut downs constantly. Usually atleast 3-4 times a day. It's pretty nerve racking. I honestly don't think it's the battery, I've experienced this issue on three different batteries and it happened on all of them. It's not ROM related either as I've tried probably 15 different ROMs (stock based, ICS, JB) and they all have this issue.
My buddy who has a Sensation also has this issue on his phone. Maybe it's a problem for that phone too since they are pretty similar?