Related
My HTC Touch Pro from Sprint has always had problems. 3 times in a row the keyboard has stopped working and I've gotten it replaced. It's always been very laggy and since it's Sprint I haven't flashed any new roms or anything, just some reg edits an stuff. This most recent time though not only did the keyboard stop working but so did the audio stop working completely. I couldn't hear calls or music or anything, and when the guy tried to "fix" it, it stopped running in portrait as well. He ordered me a replacement a few days ago and it's supposed to come on Monday or Tuesday, he's gonna call me to go get it I have no clue how thats gonna work.. But the problem has gotten even worse. At first whenever I plugged in the earbuds that came with it, the audio would somehow magically return. Not through the buds mind you, they would just hang, through the phones actual speakers. I could make calls and everything again, but suddenly it started lagging like crazy and now it won't even get past the load-up "touch pro" screen. It just freezes there, I can't really go without a phone for 2 or 3 days and I need it on to receive their call. Is there anything I can do to get it running in some working manner?? And what can I do to stop these hardware issues from happening again??
EDIT: Another question, no reason for a new post. Is it possible to store my texts on my computer so I can delete em from my phone? I could never find the files!
It sounds like something is corrupted on your phone. Have you tried a hard reset? That is what returns the phone to "factory fresh". It will wipe out all of your data and any settings you may have changed which is not fun. However, it may solve more problems that it creates.
To Hard reset, turn the power off. Press and hold the volume down and Center button. Use the stylus to soft reset. Keep holding the volume down and center buttons. The screen will then give you instructions. Release and follow instructions.
Another option is to try a custom ROM. If you go this route, read the instructions carefully. Most importantly, USE A CDMA ROM!! Do not use the GSM ROM or much unhappiness will insue.
The downside to a Custom ROM would be that if you determine you need to replace your device under warranty, you have to undo everything. That takes a while and requires some reading.
Good Luck,
Doug M.
Thanks dwmackay! Appreciate the advice and I'll definitely keep all of that in mind when I get the replacement. I've always been curious about flashing ROMs and MightyRom looks very promising, is it safe to do? I'm sure atleast the keyboard will stop working again if not even more than that, would I be able to restore to stock and relock it easily? Appreciate all the advice!
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 sent my LG G2 back to LG some months ago as the top of the screen was unresponsive and the screen was starting to get unglued. It was right before my warranty ended. When I got it back, as my warranty was already expired I decided to root the phone (using stump), but I kept the stock rom. Actually the only reason I rooted my phone was to install jishnu's camera mod as I wanted better quality pics and 4k video (and that never happened as I never got to see the lg g2 version of it).
After a couple months, my phone started rebooting with no apparent reason. After a week of this shenanigans, I woke up one morning to a bootloop. I was able to get it in download mode, so I tried flashing the original stock to undo the rom using the LG flash tool method (http://forum.xda-developers.com/showthread.php?t=2663369), but It didn't go through because it said it was a different version of the phone. I even try with the alternative dll provided in the post with no luck.
Two days later, after fighting tirelessly with the phone, I was able to get into recovery (twrp). At this point, I installed a Rom (slimkat) and that seemed to fix the problem. Then, a couple days later my phone started doing the same stuff again. Most of the time, the reboots were quick and it only bootlooped every now and then, and finally going into android. It get's really hot around the camera though.
Today it's absolutely stuck in a boot loop and won't go into recovery. I was able to pull the logs a couple days ago right after a reboot.
I would really appreciate if anyone could look into them and tell me what's wrong and if it's possible to fix. My biggest fear is it is hardware related (which would suck because it basically just came back from being serviced).
Except for these last episodes, it's the best phone I ever had. I love the quality of the pics, the size, the screen and I was hoping not having to upgrade for a couple years.
Thanks in advance.
(I removed the Logs because even though I scrubbed personal data from them, I still got 16 downloads and not a single reply related to them, and just to be safe, I will minimize the chances of anything going sour)
Have the same issue. It just started going in bootlops. Sometime I can get a few hours of use if I am lucky but no matter what I do (diff roms,baseband, lg flash tool to original firmware) bootloop will not go away.
Seems like something many people are experiencing after a year.
Let me know if you figure it out
My Z3 sometimes does "stealthy" auto reboots when not in use. The system crashes and does an auto reboot but not a full one because the phone won't ask for the sim pin code, it will reboot to the lockscreen so unless you're looking at the phone while it happens you won't notice. If you're lucky enough to catch the reboot, you'll notice the screen suddenly lighting up, and the boot animation will play, then the phone will go back to the lock screen where you left it. My phone does this a couple of times a week, most of the times I don't catch it but there's a way to tell: go to Settings → About Phone → Diagnostics → SYSTEM INCIDENTS
If it shows 0 this means you haven't had a reboot in the past 10 days. Right now on mine it shows 1 which happened during the night (so I didn't catch it happening). I always have 1 or 2 in there, I'm not sure if it always happened, but I started noticing it after Lollipop, and factory reset didn't help.
Please let me know if you have any "system incidents".
MarkMRL said:
My Z3 sometimes does "stealthy" auto reboots when not in use. The system crashes and does an auto reboot but not a full one because the phone won't ask for the sim pin code, it will reboot to the lockscreen so unless you're looking at the phone while it happens you won't notice. If you're lucky enough to catch the reboot, you'll notice the screen suddenly lighting up, and the boot animation will play, then the phone will go back to the lock screen where you left it. My phone does this a couple of times a week, most of the times I don't catch it but there's a way to tell: go to Settings → About Phone → Diagnostics → SYSTEM INCIDENTS
If it shows 0 this means you haven't had a reboot in the past 10 days. Right now on mine it shows 1 which happened during the night (so I didn't catch it happening). I always have 1 or 2 in there, I'm not sure if it always happened, but I started noticing it after Lollipop, and factory reset didn't help.
Please let me know if you have any "system incidents".
Click to expand...
Click to collapse
Hi Mark
I know this phenomenon on custom Roms or when using a custom kernel.
I think this is called a hot - reboot, kinda, because it's not a full reboot.
If you're using w custom kernel this might be the reason, or the settings of the kernel.
I can't check what you requested because I'm using the concept rom atm.
But I'm quite sure I don't have this issue, as I remember from kk days that the notifications are gone afterwards and I think this would go for lp too, and I didn't notice so far (on this rom).
But I did have had random reboots many times at different set ups of course. It can also occur on certain stock kernel settings or root apps I assume.
Gesendet von meinem D6603 mit Tapatalk
Aronuser said:
Hi Mark
I know this phenomenon on custom Roms or when using a custom kernel.
I think this is called a hot - reboot, kinda, because it's not a full reboot.
If you're using w custom kernel this might be the reason, or the settings of the kernel.
I can't check what you requested because I'm using the concept rom atm.
But I'm quite sure I don't have this issue, as I remember from kk days that the notifications are gone afterwards and I think this would go for lp too, and I didn't notice so far (on this rom).
But I did have had random reboots many times at different set ups of course. It can also occur on certain stock kernel settings or root apps I assume.
Gesendet von meinem D6603 mit Tapatalk
Click to expand...
Click to collapse
My phone is completely stock and I still have these weird reboots. Before I do another factory reset I'm trying to understand if other people have them (and then not bother with a factory reset because that would mean it's a firmware issue) or if I'm the only unlucky one who keeps getting them. Anyway, I was considering getting my phone serviced, I noticed the glass is a bit misaligned and I have a dead pixel, I called the service center and they said both issues are covered by the warranty. Might as well add random reboots to the list, maybe they'll get me a refurbished phone, mine has a few marks on it.
I factory reseted my phone and then sent it in for repairs, most likely got a refurb too since this one looks brand new, and I still have those "system incidents" happening early in the morning when the phone is just resting on my table.
I don't like begging for replies but please if you stumble upon this thread just drop a line saying if you have them or not. At this point I can't be the only one.
Also I'd like to know if there is any way to consult a log or something that would tell me why it happened.
I used to have them on kk, but they stopped. Mine would only happen at work, which led me to believe it was network related somehow... As if a spotty signal was heating up the phone or something. They stopped as randomly as they started.
Sent from my SM-T700 using XDA Premium HD app
I factory reseted my phone again after messing with the concept rom, and guess what, not even one day passes and the piece of crap reboots out of nowhere like always. I'm so mad right now, I only have 3 thirdparty apps installed, poweramp, the app from my mobile data provider and waze. I will start to try and get rid of this phone now, this is absolutely ridiculous.
I have exactly the same problem. Started after installing LP. Had someone found a solution?
Sam
Wait, is this happening on the Concept ROM? Because if so, you do know that's an unfinished ROM, right? Not meant to be a daily driver?
Clean flash the latest stock LP and go from there.
robogo1982 said:
Wait, is this happening on the Concept ROM? Because if so, you do know that's an unfinished ROM, right? Not meant to be a daily driver?
Clean flash the latest stock LP and go from there.
Click to expand...
Click to collapse
Dude, read the post again. It's happening on stock lollipop with literally no mods installed. I kept the concept rom for 5 days and it was absolutely stable for those 5 days. Stock lollipop reboots at least once every 10 days, but usually twice.
Here's a recap: I had the phone for quite a while now, I don't remember if I had reboots on KitKat, but I definitely have had them for the past 2 months or so. Meanwhile I got my phone refurbished because I had a dead pixel, it was already rebooting when I sent it in, got it back factory reseted and hardware refurbished and the reboots continued once I started installing all my stuff. Now I installed the concept rom to check it out, went back to stock lollipop with a full factory reset via PCC and after a day with pretty much nothing installed I had another reboot. The only thing that was kept during all this time is my 16Gb Class 3 SanDisk SD Card and my WIND (IT) nano sim card. I've decided to buy another SD Card anticipating the Android M memory unification feature, so I bought a Class 10 uhs3 32Gb SD Card from Kingston (which by the way isn't reaching anywhere near the declared speeds of 80/90mb/s, it only reads and writes at around 35 on the phone, I made a thread about it, maybe the phone itself can't read that fast), and I've been using it for a day now. I had no reboots yet but I had some weird app incidents under diagnostics, one from photo analyzer service and one from backup and restore (I hope they happened when I was still messing with the memory card in and out, because I didn't use any of those apps).
Here's a thread I made on the official forum:
https://talk.sonymobile.com/t5/Xper...oubleshoot/m-p/1057964/highlight/false#M26160
By the way, I still don't know if these reboots are rare or if everyone has them. Too few people have commented on whether they have them or not, while this thread has 447 views. If even 10 people commented saying if they had reboots or not I'd be able to rule out glitchy firmware. A friend of mine has the Z3C and he said he has no system incidents and his phone never rebooted.
Still getting soft/stealthy reboots
After doing a complete repair via pcc, I did not put a SD card back in my phone and only installed my google account and apps... No 3rd party apps. It goes for a couple days and then starts doing a reboot usually once every charge and mostly in the morning. The battery usage graph shows a pretty significant gap as if the phone was off but not completely off. Then I find system incidents in the diagnostic app but it only gives me the date and time of when it happens. No other information. Kind of useless if you ask me. This has all started after updating the official LP build . 200 firmware. Sony needs to investigate this became it's happening more and more for people on 5.1.1
I have a locked bootloader, stock kernel, rooted, xposed, dual recovery, tricked out rxz experience ROM with 85 apps (it includes 17-19 xposed add-ons) in addition to 102 system apps, no random reboots at all. I keep an eye on phone diagnostics, system status (temperatures, etc.) like a hawk.
So guys if this happens at you at stock rom , my suggestion is ask the service for replacement maybe.
Sent from my D6603 using Tapatalk
I am currently doing a test after repairing via pcc, installing a new Google acc, only important updates to apps I use that come pre-installed. So far it's been 5 days and no soft boots or incidents in diagnostics. Although it means nothing because usually after about a week or so is when the issues come back after doing a full repair or factory reset. I guess time will tell. Otherwise everything seems to be working great, especially battery life.