Related
OK have had my phone for a week, no issues until today. Only thing I have done is unlocked the phone, no root and still on stock 4.0.2
I went to make a call, and it rang, but went right to speakerphone, and the whole screen went grey, could not choose anthing like end call, or get off speakerphone, then phone rebooted.
Happened 3 times in a row, everytime phone rebooted, and went to make a call, it reboots.
Do you think unlocking the phone would cause this? Should i relock it and exchange or any other ideas?
Thanks
tannor said:
OK have had my phone for a week, no issues until today. Only thing I have done is unlocked the phone, no root and still on stock 4.0.2
I went to make a call, and it rang, but went right to speakerphone, and the whole screen went grey, could not choose anthing like end call, or get off speakerphone, then phone rebooted.
Happened 3 times in a row, everytime phone rebooted, and went to make a call, it reboots.
Do you think unlocking the phone would cause this? Should i relock it and exchange or any other ideas?
Thanks
Click to expand...
Click to collapse
I would go from any of the home screens to Settings/Apps/All/Phone/Clear Data. Then reboot the phone and try making calls again.
If that doesn't fix the issue, I would 1) backup all the stuff on my sdcard that I wanted to keep (pictures, music, etc.) to my computer, 2) from a home screen go Settings/Backup & Reset and select Factory Data Reset.
Additional Notes: Make sure Backup and Restore are checked in the Privacy setting. When going through the setup after the reset, turn on wifi as soon as you can (assuming it is available). After you have entered your Gmail account info, you will be presented with a screen that has two check boxes. Basically they are "Do you want Google to backup and restore this phone”. Make sure you check both of those. Your apps will then automatically reinstall (paid and free). Set the phone aside for a minute or two and let the apps download and install.
If none of that fixes the issue, contact Verizon.
Good luck.
Thanks...well does this make sense.
Before I read your reply i assumed this would have to be exchanged. So first thing I did was hook it up to my PC, use adb to restart it in bootloader.
Then locked it again. and hit start.
Now when I open phone, i can make calls no issues.
So relocking fixed it? But why? This is also bothers me, becuase I bought the phone to be able to customize and now not sure if unlocking will cuases these problems in the future.
Does anyone know what changes relocking does? trying to figure out why that fixed it.
tannor said:
Thanks...well does this make sense.
Before I read your reply i assumed this would have to be exchanged. So first thing I did was hook it up to my PC, use adb to restart it in bootloader.
Then locked it again. and hit start.
Now when I open phone, i can make calls no issues.
So relocking fixed it? But why? This is also bothers me, becuase I bought the phone to be able to customize and now not sure if unlocking will cuases these problems in the future.
Does anyone know what changes relocking does? trying to figure out why that fixed it.
Click to expand...
Click to collapse
My guess is that the reboot fixed it, not the re-lock.
Good luck.
Geezer Squid said:
My guess is that the reboot fixed it, not the re-lock.
Good luck.
Click to expand...
Click to collapse
Yeah but it rebooted everytime i tried to make a call?
I saw the google logo and the lock, and then flashy animation and had to wait a minute or so before phone booted up.
it locked up like that 5-6 times in a row until I decided to relock it.
Oh yeah. Let's count that as my brain fart for today.
Sent from my Galaxy Nexus using Xparent Cyan Tapatalk
Not sure if i should try and relocking..or just exchange it.
it could have been coincidence that it worked after relock. because after relock i don't really think it does much?
I only have 5 days left before I can return and exchange. Also now i cant replicate it.
Has anyone experienced any spontaneous reboots on their ZL yet?
Mine has done it twice, both times while doing things related to Google apps or accounts. The first time my phone rebooted, I was actually adding my Google account after a reset to fix the notification LED issue. When I unchecked the option to backup and restore my Google account, my phone blinked the xperia logo, then rebooted (Sony logo, xperia logo, boot animation then done). It was a very quick reboot.
The next time, I was installing apps from the Play Store. A bunch of apps were queued up, downloading and installing over Wi-Fi. I hit the home button, then was about to open up a folder to check my Gmail app settings when again, the phone blinked the xperia logo and proceeded to reboot. When it was done, it continued to install my apps as queued from the Play Store, as if nothing happened. It hasn't done it since (of course, this was only a few hours ago).
My phone is not rooted & I have not messed with the bootloader unlocking or anything. It's 100% stock while I'm evaluating it against my SGS3 for a potential permanent switch. I've got the US C6506 model (black, on AT&T -- LTE is working fine).
I really, really like this phone so far, and I'm just hoping that these two reboots were a random oddity, not to be repeated.
Interestingly, I actually fully set up the phone yesterday evening, but when I discovered I had the notification issue, I reset it this morning and re-did all of it. The phone did NOT reboot at all yesterday in the 4 or 5 hours I spent playing with it, either. It sat in standby overnight without incident as well -- all prior to the reset today & the 2 subsequent reboots.
I guess from here it'll be a waiting game to see if it does it again, but in the meantime, I was curious if anyone else had seen anything like this with their ZL.
Yup, seen it twice myself. First time, I noticed that it had rebooted when I couldn't find any previously running apps. The second time I was in the Settings screen when it randomly rebooted. I was just about to click the Display setting when this happened.
I'm just running the stock ROM on the C6506 model. I'm keeping an eye out on it and will see if there is a pattern.
rajeshr said:
Yup, seen it twice myself. First time, I noticed that it had rebooted when I couldn't find any previously running apps. The second time I was in the Settings screen when it randomly rebooted. I was just about to click the Display setting when this happened.
I'm just running the stock ROM on the C6506 model. I'm keeping an eye out on it and will see if there is a pattern.
Click to expand...
Click to collapse
Thanks ... in some ways it's good to know, and in others, it worries me. I hope it isn't a pattern, though. Thus far, I've used the phone since the two reboots without incident (music playing, bluetooth connections, and phone calls).
EDIT: A third reboot. This time I had just updated a few apps in the Play Store, returned to my home screen and was about to turn my Wi-Fi off when it rebooted. One common thread thus far is that my Wi-Fi has been on each time. I have no idea if that's related or not, though.
I have been using mine for 1 week and have not had any reboots. I am using the hspa version (c6502) and I am a heavy user
Seems to me that the random reboots are isolated to 6506 models. I haven't had one single reboot in the past week I have been extensively using mine (6502). However, while I was on CM10, my phone hung and rebooted like hell.
Yeah I'm c6502 aswell no random reboots.
Sent from my Nexus 4 using xda premium
No reboots on C6502
Same here, have been using my ZL (C6502) for the past 22 days without a single reboot or freeze. Heavy usage for last week or so (wifi on all the time). I too think this and the low call volume issue might be specific to C6506 (LTE) version.
6502 here as well, no reboots so far and I'm rooted. Been about 2 weeks.
I'm starting to think this issue is unique to me and/or my phone -- at least my specific case. Actually, I'm glad for that, because I love this phone.
I realized I may in fact have memory card corruption. I'm going to explore that further, because I had some serious issues with my SGS3 corrupting microSD cards. I thought it hadn't done it on my current card, but I have discovered some corrupted sound files on it, so I think I'm going to do a format of my microSD and see what happens.
Thanks for all the input, folks!
I had some reboots in past one week
using since March 10th
today itself had 2-3 reboots
one more thing is had blank screen during a phone call also
we need Roms for this device I never understood
why there is so much delay in release of custom Roms
Once,
but not sure it was rebooting. Cuz the screen went blank. Then i had to press a tiny yellow button that says off near the sim slot. Then it came back to life. Plus my wake up button is kinda hard to press. Do you guys hv that problem?
Sent from my C6502 using xda app-developers app
safuan7822 said:
Once,
but not sure it was rebooting. Cuz the screen went blank. Then i had to press a tiny yellow button that says off near the sim slot. Then it came back to life. Plus my wake up button is kinda hard to press. Do you guys hv that problem?
Sent from my C6502 using xda app-developers app
Click to expand...
Click to collapse
I wouldn't call that a reboot, at least not in the sense that I was seeing them. That's more like a freeze that would require a battery pull on a phone with a removable battery (I used to have this all the time on the Samsung Captivate).
My ZL was rebooting fully right in front of me (screen goes black, then the xperia logo, followed by the full normal boot sequence, just very rapid -- the boot animation is shorter than a cold boot).
Note -- I have not actually fixed my memory card yet, and I have not seen any more reboots. I'm nearly a full day on my current battery charge, too.
I have the C6506 also, and I get numerous random reboots also. I did get few logcats, but I have not seen any revelant info that causes the random reboots. I replaced my micro-sim, thinking it may caused modem panic reboots, but that wasn't root of the problem. However, I did notice that the reboots occurred less without micro SD card, but I haven't completely made that conclusion yet (I want to listent to my music!).
I also have a 6506 and have been experiencing some kind of reboot. Not a full reboot that the OP has been talking about, but one where my screen just turns off. At first I thought better battery stats was just having issues as my stats would end up all out of whack for no reason. Then today the screen shut off while in use. I only had to push the power button to get back to my lock screen. But again my stays were all out of whack. I'll have to pull the log later but I hope this is is just a software issue.
Qmann05 said:
I also have a 6506 and have been experiencing some kind of reboot. Not a full reboot that the OP has been talking about, but one where my screen just turns off. At first I thought better battery stats was just having issues as my stats would end up all out of whack for no reason. Then today the screen shut off while in use. I only had to push the power button to get back to my lock screen. But again my stays were all out of whack. I'll have to pull the log later but I hope this is is just a software issue.
Click to expand...
Click to collapse
Interesting. I've replaced all my corrupted files on my microSD card as of now, and so far, aside from that first day, I have not had a single reboot of the kind I saw before. Actually, no reboots at all, and my current uptime shows it (111 hours).
What happened to me was I had had a bad microSD card in my SGS3 -- files would become corrupted with time on it. I finally replaced it with a new one, but apparently when I copied my data back to it, I inadvertently copied a few of the corrupted audio files (notification sounds, actually) but never noticed it. I realized this when I was resetting my notification sound for text messages and heard the signs of corruption in the file, and so I began to think my phone had been responsible for the corruption. I know now that that can't be true -- otherwise I'd have some corrupt photos as well, and I don't. Only a few select sound files were bad, and because I keep regular backups of the contents of my microSD cards, I just copied the wrong ones (d'oh!).
Of course, I've had random reboots on android devices before (Asus TF101), so I'm quite wary of them -- if I see anything further, I'll post about it.
I looked at the log and saw nothing conclusive that would be making my screen turn off. I also checked my up time and it hasn't reset, so I know it's not a true reboot. When I put my SD card in I just wiped it from the phone. The only thing I put back was music files. Thinking about that now it wasn't the clean start I usually give my phones. So I just wiped the card again and we will see today if anything happens
C6503 here and I've been getting a couple reboots a day since I bought it. 2 days ago I used PC Companion to solve another issue (random loss of network signal) by reinstalling the phone software and that seems to have fixed it. Unfortunately the random reboots are still present.
I don't use any SD card at the moment.
I've now been using my ZL for a month or so, and since that first day when I made this post, no spontaneous reboots at all. I have no idea how or why, they just stopped on their own.
Last night I tried turning on my Pixel C only to see a screen saying enter android password ive never seen this screen before so i figured i would try my Google password and i got a second message saying "the password you entered is correct but unfortunately your hard drive is corrupted and you will have to factory reset your device" or something along those lines so i hit factory reset where the open android appears and it had text in the bottom saying something like erasing hard drive i left it like that since i had somewhere to go and when i came back the pixel c was completely dead so i connected it to the charger and tried turning it on and it would boot to the google logo then the four dots and just reboot all the time i was not able to even leave it turned off i did try factory resetting the pixel through android manager but still had the same problem. has anyone else experienced this problem? i have contacted google and they are sending me a replacement just wondering if anyone knows whats wrong with it and why it messed up like this
yes, i am aware of the screen and the factory reset erase sequence. but the reset sequence occured while full charge and plugged into a pc . if the battery on yours was near discharged during the erase sequence it might have completely discharged before completing the factory reset which usually results in somewhat unknown issue. best to plug it in to charger before erase sequence if this happens again. good to hear that another unit is on its way.
xm0is3sx said:
Last night I tried turning on my Pixel C only to see a screen saying enter android password ive never seen this screen before so i figured i would try my Google password and i got a second message saying "the password you entered is correct but unfortunately your hard drive is corrupted and you will have to factory reset your device" or something along those lines so i hit factory reset where the open android appears and it had text in the bottom saying something like erasing hard drive i left it like that since i had somewhere to go and when i came back the pixel c was completely dead so i connected it to the charger and tried turning it on and it would boot to the google logo then the four dots and just reboot all the time i was not able to even leave it turned off i did try factory resetting the pixel through android manager but still had the same problem. has anyone else experienced this problem? i have contacted google and they are sending me a replacement just wondering if anyone knows whats wrong with it and why it messed up like this
Click to expand...
Click to collapse
Exactly the same thing happened to me, it was fully charged back then and after I reset the tablet it went in to boot loop. I got the new replacement now and it is working better now
damjan006 said:
Exactly the same thing happened to me, it was fully charged back then and after I reset the tablet it went in to boot loop. I got the new replacement now and it is working better now
Click to expand...
Click to collapse
Tell us please, how the replacement device. Because I am from Russia and I detail it is important to find out how things are going.
dkryder said:
yes, i am aware of the screen and the factory reset erase sequence. but the reset sequence occured while full charge and plugged into a pc . if the battery on yours was near discharged during the erase sequence it might have completely discharged before completing the factory reset which usually results in somewhat unknown issue. best to plug it in to charger before erase sequence if this happens again. good to hear that another unit is on its way.
Click to expand...
Click to collapse
im guessing the battery was around 80% when it decided to mess up so i think it got stuck formatting the hard drive and just died from there
damjan006 said:
Exactly the same thing happened to me, it was fully charged back then and after I reset the tablet it went in to boot loop. I got the new replacement now and it is working better now
Click to expand...
Click to collapse
any guess why this happened to yours? im thinking it might have to do with the magnets inside the pixel C i did stick it on the fridge to see if it was pretty strong (dumb yeah i know) lol it did work fine while stuck to fridge but messed up a few hours after that
This just happened to me. Here is the sequence of events that led up to it.
1. Fully charged and unplugged it. ( I did pull the unit off the keyboard as it was propped up but this shouldn't affect the storage right? )
2. It did a random reboot after taking it off the charger.
3. It asked for my password in a "pre-boot" screen
4. The message I get is : "Decryption unsuccessful" "The password you entered is correct but unfortunately your data is corrupt.
"To resume using your tablet you need to perform a factory reset. When you set up your tablet after this reset you'll have an opportunity to restore any data that was backed up to your google account."
jlcutler said:
This just happened to me. Here is the sequence of events that led up to it.
1. Fully charged and unplugged it. ( I did pull the unit off the keyboard as it was propped up but this shouldn't affect the storage right? )
2. It did a random reboot after taking it off the charger.
3. It asked for my password in a "pre-boot" screen
4. The message I get is : "Decryption unsuccessful" "The password you entered is correct but unfortunately your data is corrupt.
"To resume using your tablet you need to perform a factory reset. When you set up your tablet after this reset you'll have an opportunity to restore any data that was backed up to your google account."
Click to expand...
Click to collapse
thats the same message i got also after turning on the display I also have a keyboard and took it off to put the tablet on the fridge and put it back on the keyboard afterwards and it still worked fine until i turned the screen off and tried to turn it on later
jlcutler said:
This just happened to me. Here is the sequence of events that led up to it.
1. Fully charged and unplugged it. ( I did pull the unit off the keyboard as it was propped up but this shouldn't affect the storage right? )
2. It did a random reboot after taking it off the charger.
3. It asked for my password in a "pre-boot" screen
4. The message I get is : "Decryption unsuccessful" "The password you entered is correct but unfortunately your data is corrupt.
"To resume using your tablet you need to perform a factory reset. When you set up your tablet after this reset you'll have an opportunity to restore any data that was backed up to your google account."
Click to expand...
Click to collapse
yup, this has happened to mine several times but except for one time, i just pressed vol dn & power to get to the options screen and rebooted. so i did not have to reset but one time. but mine has not died yet. i also think the magnets might be causing this and some other issues
I've just had the same thing this morning and I'm in the process of a truly awful conversation with Google support during which I had to explain to them what "stuck in a bootloop" meant...
I've had this one since a week after launch, working fine - I assume there weren't any recent updates that changed any of the memory partitions?
You guys could always try to unlock your bootloader from fastboot and reflash the stock images.
PriyanPhoenix said:
I've just had the same thing this morning and I'm in the process of a truly awful conversation with Google support during which I had to explain to them what "stuck in a bootloop" meant...
I've had this one since a week after launch, working fine - I assume there weren't any recent updates that changed any of the memory partitions?
Click to expand...
Click to collapse
God I hate dealing with non-technical customer service reps, the devs from Dolphin Browser didn't understand portrait vs landscape, I ended up stopping the conversation because I'd rather beat my head against the wall. Same thing goes for Wizards of the Coast and Magic 2015, I asked then why all my data on my tablet didn't sync to the cloud since it was using Google Play games so I could continue the game on my phone and they just kept on saying "It's not meant for phones so that's why it doesn't work" even though it actually worked perfectly on my phone, they also kept calling me by the wrong name, even after multiple corrections.
Sent from my Pixel C using Tapatalk
I have the EXACT same problem on my 32GB píxel c, i am returning it.
Enviado desde mi XT1039 mediante Tapatalk
Same here
Okay, same boat here. Just received my Pixel C two days ago. Pretty neat to use, put always fully charged. Several unresponsive(freeze) occurs to me, especially when I tried Lens Blur feature in Google Camera. But overall I'm pretty satisifed with the experience and design.
Today I got onboard of a airplane. I guess it's after X ray security check machine... then I opened the tablet it prompted me with password. And the following with sort of "your drive is corrupt but we can restore it from Google backup" things. I clicked next (it's fully charged by now) and the looping restart begins. I can't even turn it off until I find the vol down + power trick to enter the recovery menu. But right now it's completely unusable. I think I'll request a order returning when I'm back...
I've just had the same experience on a third Pixel C, this time after about a week. I think this time I'm just going to demand a refund. They've failed to send me a single working device and don't seem to have any fix for this. I can't go through a continual process of RMA-ing and losing any data not yet backed up indefinitely.
What country are you guys from for those of you having issues? I'm in the USA and bought mine as soon as it launched and haven't had a single issue with it, meanwhile I see a bunch of people are having random QA issues which seems to be pretty odd.
Sent from my Nexus 6 using Tapatalk
I'm in the UK. I bought at launch so I'm well outside the 30-day window, but I've gone through three different units. On the plus side, they agreed to a refund with no hassle at all so I assume this isn't an isolated issue. Thanks to Amazon Prime I'm already setting up a Sony Xperia Z4 and, whilst I'd still prefer stock Android and the Pixel C 's aspect ratio, I'm actually pretty impressed with it so far...
Same thing here.
Did your replacement function?
Some premium tablet
Screw Google for not sending a USB C to USB A 3.0 cable so I could at least attempt a ADB factory flash.
God I hate dealing with non-technical customer service reps,
Click to expand...
Click to collapse
You know "boot loop" isn't a technical term right??
Anyone else having issues with the Pixel not waking up from sleep. This happens to me seemingly randomly, at least I have not been able to pinpoint what is causing it. I have to use the power button and volume rocker to hard reboot it. This is my second unit that has done this, and Google just wants to replace it again.
I made a quick video of it:
https://www.youtube.com/watch?v=97iho4sHAlc
I have exactly the same problem ...
to boot, I press 10 seconds repeatedly on the power button.
I already had the problem of keyboard update ...
I thought this was solved but sadly it's still around. Suffered from it a few days ago after doing a factory reset about a week ago.
Ves said:
I thought this was solved but sadly it's still around. Suffered from it a few days ago after doing a factory reset about a week ago.
Click to expand...
Click to collapse
Same here, I finally received the Feb update on my replacement Pixel and thought it was solved... nope.
I bought the Pixel for quick work trips so I did not have to bring my laptop. I take allot of flights in the morning and return that afternoon/evening. The Pixel was going to be used for Presentations, and notes. It is super frustrating when I have the tablet all setup to present and I have to mess with it to get it to turn back on. This thing has way to many problems for a premium tab, and seems like Google has not dedicated the appropriate resources to supporting it (support/dev).
Ah the old "Sleep of Death" it seems to have plagued (mostly) tablets for years. I've had it happen on my Asus Transformer T101 years ago and it also happened on my Samsung Galaxy Tab S 10.5". I haven't had it happen yet in the months I've owned the Pixel, but I have had some odd issues where I press the power button to turn it on and it shows the unlocked boot warning for literally a second and then turns off/reboots, when it does that I have to hold the power button for like 10 seconds to force a reboot and then it boots up fine.
Sent from my Pixel C using Tapatalk
I use the pattern to unlock my device. For years on my Asus TF201 (which had occasional severe performance problems), I would occasionally turn it on, get nothing for several seconds, and then get the pattern unlock screen for a fraction of a second, and then it would sleep. Sometimes if I drew the pattern really fast it would unlock it. Othertimes, I think I just rebooted it.
With the Google Pixel C, I (perhaps foolishly) continued the pattern unlock approach. It usually works fine. But occasionally, I will get the pattern unlock screen soon enough, enter the pattern, and it will do nothing for several seconds (just frozen on the pattern screen with my drawn pattern) and then go to sleep. If I try this repeatedly, sometimes once it will actually let me in. Otherwise I reboot and try again.
buurmas said:
I use the pattern to unlock my device. For years on my Asus TF201 (which had occasional severe performance problems), I would occasionally turn it on, get nothing for several seconds, and then get the pattern unlock screen for a fraction of a second, and then it would sleep. Sometimes if I drew the pattern really fast it would unlock it. Othertimes, I think I just rebooted it.
With the Google Pixel C, I (perhaps foolishly) continued the pattern unlock approach. It usually works fine. But occasionally, I will get the pattern unlock screen soon enough, enter the pattern, and it will do nothing for several seconds (just frozen on the pattern screen with my drawn pattern) and then go to sleep. If I try this repeatedly, sometimes once it will actually let me in. Otherwise I reboot and try again.
Click to expand...
Click to collapse
I do not use the pattern lock, I do secure it with a passcode though. My issue does not seem to be related to the security though as it does it at random times and never display the login prompt.
still having both random reboots and screen blackouts. This is a shame google will not acknowledge the problem and say they're fixing it. It only makes me believe that they know about it yet CANT fix it. Like its a hardware issue more than a software one. At least if they would say "we are aware of the issue and working on a fix" or "we were working on a fix but now working just a big OS update instead" Id feel like I wasnt ripped off by them. I mean I have EVERY nexus device box still displayed in my hobby room at my house. Im a huge fan but this is really bad.
Joined beta N program, hopefully this issue is resolved on the Pixel C.
I was just wondering if anyone else has an issue with their Note 4 rebooting randomly with no external input. This started happening with the Android 6.0 update both on the download from here and the AT&T official release, Any Ideas? I've already purchased a new battery due to a separate issue, any idea?
I had the same problem. The phone would freeze and randomly reboot. Sometimes the system crashes and asked me for the typed-in password (not fingerprint). Sometimes when I charge the phone, and unplug the power cable, the charging led stays lit and the battery has to be pulled. I decided to switch the battery with my wife's Note 4 and see if the effects remained. So far I haven't had any problems after switching the battery, so I believe the battery may be the cause of all these issues. I'll keep you updated on the issues.
I'm back. The battery replacement didn't fix the reboots. I think my phone's hardware is permanently damaged. :crying:
have you downgraded?
and can you help me with my problem?[
AlexanderDAB said:
have you downgraded?
and can you help me with my problem?[
Click to expand...
Click to collapse
I'm downgrading to stock 5.1.1 right now. I'll keep you updated. I placed an order for a Galaxy S7 Edge International Version (G935F) yesterday.
ajumatt said:
I'm downgrading to stock 5.1.1 right now. I'll keep you updated. I placed an order for a Galaxy S7 Edge International Version (G935F) yesterday.
Click to expand...
Click to collapse
can you downgrade to Android 5.0.1 and help me with my problem?
its something completely different to this topic
I've been having the same issue, started about 2 weeks ago. phone would start being sluggish then if I continue tapping on screen, it'll reboot. At least once I saw it go into recovery & reinstall firmware(?). Another time it just sat at the bootloader screen waiting for software download or something till I took out the battery. Most likely it's a software issue related to 6.0 update or updates afterwards. taking out the SD card helped a bit.
but basically got annoyed & upgraded to LG V20 today. Coincidentally, there was another person at the AT&T store with a Note 4 having the same issue.
Mine just rebooted twice on me a while ago, first is emergency calls only now the reboots then what. And yes the slow charging is a problem too. MM got serious issue dam att
Sent from my SAMSUNG-SM-N910A using XDA-Developers mobile app
adavis1201 said:
I was just wondering if anyone else has an issue with their Note 4 rebooting randomly with no external input. This started happening with the Android 6.0 update both on the download from here and the AT&T official release, Any Ideas? I've already purchased a new battery due to a separate issue, any idea?
Click to expand...
Click to collapse
use wakelock its an app u get it from play store.it makes ur cpu always running.some how it fixes the problem of random reboots. dl it and set it to partial lock (the 5th option)
Same problem. Just started a few weeks ago. REALLY frustrating having to enter my password every 3-4 minutes. NEVER buying another Samsung, too many damn issues with this phone.
My reboots tend to happen once the phone goes below 60% battery. It's fine above 60%. Once it goes below 50%, the reboots tend to happen with any intense network activity. The phone will often go from 50% to 22%. I forgot what the 30's and 40's look like. I will try the Wakelock app.
Ugh. I posted about this a few weeks ago. It's started happening more frequently and will occasionally go into a boot loop or show 0% battery even though there's a charge.
Has anyone found any solution? I haven't tried wiping / resetting but I'm getting close to trying it.
Here is a cautionary tale for you. My completely stock, unroooted phone started acting the same exact way. On the 4th or 5th battery pull (to fix a frozen screen) it just crapped out. It's totally unresponsive. Deader than a door nail. Tried everything. The download mode, discharging by power button depression/battery removal, etc. Adb shell command does not detect it. Nor Odin. Computer throws up a qhsusb_bulk error when I plug it into pc. I have NO CLUE how to fix it & I am desperately seeking a solution. Please proceed wisely with your oddly acting phones & don't let this happen to you.
k.babymamma said:
Here is a cautionary tale for you. My completely stock, unroooted phone started acting the same exact way. On the 4th or 5th battery pull (to fix a frozen screen) it just crapped out. It's totally unresponsive. Deader than a door nail. Tried everything. The download mode, discharging by power button depression/battery removal, etc. Adb shell command does not detect it. Nor Odin. Computer throws up a qhsusb_bulk error when I plug it into pc. I have NO CLUE how to fix it & I am desperately seeking a solution. Please proceed wisely with your oddly acting phones & don't let this happen to you.
Click to expand...
Click to collapse
Same issue. Just got off the phone with Samsung support, all possibility of having this particular phone with this particular issue sent in for evaluation has been suspended. Translation, they know it is an issue and will not stand by the changes they push to their products (latest OS). I am researching the prospect of legal action since THEY pushed the new OS against my request. Shouldn't that affect the warranty or coverage? Consulting my attorney friends as we speak. Will let you know. I am not sure how WakeLock will help, it is not going to sleep, it is repeatedly power cycling through a kernel process until the battery overheats or it reboots.
Same issue
Since Marshmallow, my 910A will get sluggish or freeze, shut down, sometimes reboot and sometimes just brick (temporarily). Sometimes--more often in recent days, I get a "dll_mmc read fail" message and the target that says do not stop downloading. No matter what I've tried--factory and soft resets, cache clearing, battery pull, replacement, and SD card switch, contacting AT&T and Samsung rep--it doesn't seem to change. This is a daily issue and becoming more frequent. Any suggestions or do I just need a new phone? Thank you.