Related
Getting tried of watching my phone reboot. If going back to stock would resolve the issue I would do it. I called big red today and the pinhead I spoke to acted like it was the first time anyone had called about the TB rebooting on it's own. I'm looking at going to a different phone. I really think at this point it is a software issue that they need to correct. Just like with most businesses things are not addressed until they become a problem. So my thought is we should set a date when every one calls in to report their rebooting phones. We do this every week until we get a resolution. Anyone with me?
Wait... You are rooted and getting reboots? Are you on gb? Did you root or install your rom properly? What kernel?
Stock I had no issues. Non-Gb I've had mostly no issues... Some kernels less reliable than others, of course. But to be honest it sounds more like a user issue than a tb issue
Sent from my ADR6400L using XDA App
Sent from my ADR6400L using XDA App
Are you near a Verizon store? Verizon is usually very easy to convince that you need your phone replaced. (Although I think they will only replace it with the same model. But I'm not sure.) My Thunderbolt never reboots on its own but I know it is a problem that many Thunderbolts are experiencing, so maybe yours (and many others) is/are defective. I'm 99% sure if you go into a Verizon store and tell them that it randomly reboots all the time, they'll replace it for you.
I reverted back to stock and haven't had a single reboot or loss of data on three days. Just sayin'.
Sent from my ADR6400L using XDA App
I have read posts where people who are not rooted are getting reboots after they took the update. Have never had an issue with my phone until I took the update. Am going back to stock for a week or so to see if that clears things up.
Funny how VZW is changing their stance on it, almost as if it never has happened. About a month ago I went into a store and they told me that Im not the only one experiencing problems and that there will be a fix within 2 months.
I called VZW tech support and they told me that no one else is having reboots.. . . . I dont get it.
Try flashing your radios, I put both of mine to .6 and the reboots stopped.
(there is a thread in teh development forum, with the packages)
Can you specify what you mean when you say "both"? I have been getting reboots too - approximately 1 per day - but is there a process to flash each radio independently?
Sent from my ADR6400L using XDA App
sethschmautz said:
Can you specify what you mean when you say "both"? I have been getting reboots too - approximately 1 per day - but is there a process to flash each radio independently?
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
No, but each flash has two radios
Sent from my ThunderBolt using XDA Premium App
Silvus said:
Try flashing your radios, I put both of mine to .6 and the reboots stopped.
(there is a thread in teh development forum, with the packages)
Click to expand...
Click to collapse
Any issues with tethering or gps using the old radios?
Sent from my ADR6400L using XDA App
Silvus said:
Try flashing your radios, I put both of mine to .6 and the reboots stopped.
(there is a thread in teh development forum, with the packages)
Click to expand...
Click to collapse
I still had reboots with both at .6, currently trying cdma.7/LTE.6.
Sent from my ADR6400L using Tapatalk
It is a hardware issue,that's where the few pricked phone came from,my original bolt had the reboot loop on stock but no one seems to want to hear that,it is a series of phones having the trouble and they are or have replaced most of them,as far as most of the other reboot go that is self made misery by not following directions or not reading to find the fix, this bolt I have now has no reboot issues and it has a mat finish to it,the other one and a few I have seen that had issues had a smooth glossy finish.
Sent from my ADR6400L using XDA Premium App
satseaker said:
It is a hardware issue,that's where the few pricked phone came from,my original bolt had the reboot loop on stock but no one seems to want to hear that,it is a series of phones having the trouble and they are or have replaced most of them,as far as most of the other reboot go that is self made misery by not following directions or not reading to find the fix, this bolt I have now has no reboot issues and it has a mat finish to it,the other one and a few I have seen that had issues had a smooth glossy finish.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I would love to think its a hardware issue, but my phone was solid from day one. Then I took the update and get these random reboot.
Sent from my ADR6400L using XDA App
It is not a hardware issue. It is a problem with the update and how certain phones installed it. Verizon is in the process of making a new update and has been working on it with HTC for a little while now & expect to have it going out this month. For some reason the software does not talk to the towers properly with some models & the hardware does not get the proper info which causes the reboots. Exactly how to tell which phones are affected, I don't know. My friend is trying to find out for me.
I can say that I ran my phone with rooted stock & moved up to the rooted update when it was available which I am still on and I have not had any issues at all besides the low recorded video audio which the update seems to have fixed for me.
My phone is:
Rooted stock & radios w/update
Adrynelynes 4.47 Kernal
I am telling you what HTC said they admit that a certain series is defective hence the snappy replacement. Just cause one Rom works and another doesn't isn't always the Roms fault,ever had a CPU that would run one OS and not another or RAM that worked fine on xp but not win 7 once the defective hard hits its limit it will fail. I have seen hardware work fine overclocked and the exact same hardware crash with half the settings,or a motherboard run suse fine but put Windows on it and it dies a week later. I didn't say they all were defective just one series of them and when they did the update a lot of the phones started to fail and some didn't,so does that tell you hardware or software,if one can run fine and the other fails its either a bad flash or bad hardware. Take your pick
Sent from my ADR6400L using XDA Premium App
I didn't do the update over the air on my other bolt, I downloaded it from HTC and it killed the phone,but the same download is on this phone and it works just fine,not one reboot, and its still stock and not rooted. The other one was dated Dec
10 and this one is dated Feb 11, I would just about guess they tweaked the update to weed out the bad phones faster,makes sense to me.
Sent from my ADR6400L using XDA Premium App
satseaker said:
I am telling you what HTC said they admit that a certain series is defective hence the snappy replacement. Just cause one Rom works and another doesn't isn't always the Roms fault,ever had a CPU that would run one OS and not another or RAM that worked fine on xp but not win 7 once the defective hard hits its limit it will fail. I have seen hardware work fine overclocked and the exact same hardware crash with half the settings,or a motherboard run suse fine but put Windows on it and it dies a week later. I didn't say they all were defective just one series of them and when they did the update a lot of the phones started to fail and some didn't,so does that tell you hardware or software,if one can run fine and the other fails its either a bad flash or bad hardware. Take your pick
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I wasn't aware of HTC stating there was some defective hardware. Never saw any references to it. If thats the case then glad they acknowledged it.
It's definitely not a hardware issue. Its a radio/ signal issue. Verizon does know about it, and is working on getting a new update out there. I know this, for a fact.
Sent from my ADR6400L using XDA App
jett2314 said:
I have read posts where people who are not rooted are getting reboots after they took the update. Have never had an issue with my phone until I took the update. Am going back to stock for a week or so to see if that clears things up.
Click to expand...
Click to collapse
My TBolt is not rooted and before the update I had no problems at all but after the update the random reboots started. Battery life is acceptable but could be allot better.
Called Verizon yesterday and they acknowledge the problem and actually said HTC is aware of the problem and are working on it but have no expected date as to when it will be fixed. I believe it is definitely is a software issue and will be fixed when the official Gingerbread is released. Just my 2 cents.
So I was listening to Pandora and texting when suddenly my phone turned off the screen. It was still playing music so I tried to hit the lock button so it would unlock but it wouldn't I tried it a couple times and still nothing. I then waited and while and nothing..Then I took off the battery and it was still playing music as if it still had the battery...for like 15 seconds. Then it tried turning on over and over without the battery on. Now it wont turn on at all. I've tried connecting it to charger, taking out battery, nothing. What happened?
So no recovery mode no DL mode no response from the phone at all now correct?
Sent from my SGH-I727 using Tapatalk 2
The_Blue_Waffle said:
So no recovery mode no DL mode no response from the phone at all now correct?
Sent from my SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I haven't tried either of those. If I connect it to the charger sometimes it will show the Samsung Boot Logo but then it won't move from there. I'll try recovery mode.
EDIT: Recovery Mode works
Was the phone hot at all when this happened
Sent from my SGH-I727 using Tapatalk 2
The_Blue_Waffle said:
Was the phone hot at all when this happened
Sent from my SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
No it was not. Normal Temperature.
Try to force it into recovery or download first. Had you flashed a new ROM (doesn't matter which one) recently?
Almost sounds like just a freak thing man if you can get her into DL or recovery I would consider stock for a few days in case it was hw failure just to monitor it otherwise restore a backup or flash something and drive on
Sent from my SGH-I727 using Tapatalk 2
The ROM I'm running right now is CyanogenMod the latest stable one. And is there anything else I could do instead of restoring? Because I'm going to lose a ton of stuff..
Well you can hope it will reboot . But that seems unlikely
Sent from my SGH-I727 using Tapatalk 2
If you flash a new rom you won't lose your data. You'll only lose apps and settings and stuff. Which you can backup with recovery (unless you meant download) if you can't get to recovery there's not much you can do for your settings. But reflashing won't touch any pictures or anything on the internal sd card.
Rehab4Life said:
So I was listening to Pandora and texting when suddenly my phone turned off the screen. It was still playing music so I tried to hit the lock button so it would unlock but it wouldn't I tried it a couple times and still nothing. I then waited and while and nothing..Then I took off the battery and it was still playing music as if it still had the battery...for like 15 seconds. Then it tried turning on over and over without the battery on. Now it wont turn on at all. I've tried connecting it to charger, taking out battery, nothing. What happened?
Click to expand...
Click to collapse
I'm not sure exactly what happened, perhaps a hard ware fault, but I am starting to believe there is more to this. I have seen the same thing happening quite frequently lately, and each device yes even my wife's iphone 4 did the same thing while she was listening to Pandora, as well as my niece with her Galaxy S II. Same as you experienced, she was listening to Pandora and was texting a friend, then the phone went dead.
So it is not localized to either iPhone or Android devices from the information I have been gathering. When I took my wife's iPhone to the apple store here in Anchorage, the rep I was dealing with informed me that they have had several in the last week that had the same issue, while doing the same thing as your device did. Of course all he could say was if it is under warranty they will give my wife a new one. So she did, just like many others.
I also spoke with Daniel @ Pandora and informed him of the same issue that was with my wife & nieces iPhones, as well as android devices. His reply was that Our app is not 100% designed for use with the latest iOS release, and not for android devices running Jelly Bean. We have had several complaints about this happening to both types of devices, you have to remove the battery and reboot the system. I asked him how to do that with an iPhone, and he informed me to "remove the back panel and the battery will pop out." After I laughed at him I reminded him that it is not possible for the AVERAGE user to remove the iPhone battery, but it is quite easily done on most Android devices.
Once I was able to get him to realize that the iPhone battery does not come out, he "remembered" that and informed me to uninstall the Pandora app, clear caches and reinstall the app. I then asked him how to do that since the screen would not come on? His reply was "well it looks like your phone is dead, you might want to go get a new iPhone. I informed him that I had already done so with my wife's iPhone but was working off of my nieces S II now. Ok, back through the script we go. Battery out, yadda yadda. Informed me that Pandora does not offer support for rooted devices or devices on UN OFFICIAL ROM'S, and JAILBROKEN iPhones.
I informed him I was working off of a bone stock Samsung Galaxy S II and that while my niece was listening to Pandora and sent a text message that is when the device was rendered useless. The S II was still dead screened at the time, and I had left the phone plugged into the wall charger for over 24 hours, so the battery should not be dead. Continued through the script with him, and finally I asked him, "Ok why is it that 2 different devices, running 2 different operating systems running the same Pandora app would both be rendered useless from listening to Pandora & sending a text?" His reply was We do not offer support for rooted devices.
Now I am not 100% blaming Pandora nor am I saying that their app is 100% at fault, but it is apparently an issue with the app itself possibly using too much system resources, and when another app wants some of those resources the Pandora app causes a force close that is not easily recovered from.
If your Skyrocket is still under warranty, or you bought extended warranty, I would highly recommend as above to return the phone to bone stock if at all possible, get all you need off of it that you do not want to lose, and run Pandora again, and see if it does the same thing, if so then return the device.
Interesting, so Pandora's app is not compatible with JB or iOS6. I'll have to take it off both my phones; TuneIn and iHeartRadio are better anyway lol
Interesting. I was listening to Pandora and running GPS. Mine froze up for a very long time, then rebooted itself.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Custom ROM flash failures
Hello,
I have Flashed ROMS with CWM recovery before with success, but recently have been getting failures. I can however, Flash with Odin still. The log I get with CWM REcovery is attached.
Search "adb" for backing up your current info before flashing anything.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
xcrazydx said:
Interesting. I was listening to Pandora and running GPS. Mine froze up for a very long time, then rebooted itself.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
That is what I was informed, but with hundreds of thousands of devices running JB I don't fully understand the issue there. It's good that your's rebooted itself. My nieces never rebooted, neither did my wife's. Again I am not sure of the issue, and would love to have a log of some one running it on their device, so that I could further investigate.
MasterDecker said:
That is what I was informed, but with hundreds of thousands of devices running JB I don't fully understand the issue there. It's good that your's rebooted itself. My nieces never rebooted, neither did my wife's. Again I am not sure of the issue, and would love to have a log of some one running it on their device, so that I could further investigate.
Click to expand...
Click to collapse
Well, I removed Pandora after that. I won't be using it anymore. Sorry man
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
xcrazydx said:
Well, I removed Pandora after that. I won't be using it anymore. Sorry man
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
No worries, but now I get to go and buy my wife a NEW iphone 5. Again she was listening to Pandora, and received a text message (this was on her 4S). screen went out, sounds stopped, and the life of her 4S was extinguished. I think it was on purpose, so that she could get the i5. But never the less I was actually there this time when it happened.
POOF, dead. *sigh* now if only ALL iphones would do this I would be happy.
MasterDecker said:
No worries, but now I get to go and buy my wife a NEW iphone 5. Again she was listening to Pandora, and received a text message (this was on her 4S). screen went out, sounds stopped, and the life of her 4S was extinguished. I think it was on purpose, so that she could get the i5. But never the less I was actually there this time when it happened.
POOF, dead. *sigh* now if only ALL iphones would do this I would be happy.
Click to expand...
Click to collapse
Damn. I think she did it on purpose too. I would've immediately uninstalled Pandora if I was her. She killed it on purpose!
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Nope my boss gave her an i phone 4s. Which she in turn took took to at&t and traded it in for a note 2.
Sent from my Transformer TF101 using xda app-developers app
Is anyone else running Cyanogenmod 11 M-releases on their Nexus 5?
I just got mine a week or two ago, and the first thing I did was unlock it and flash it to CyanogenMod 11. (M8 at the time)
I'm using the device encryption, because I'm a paranoid bastard (And I love the fact this phone is actually usable while encrypted, unlike my Nexus S), and I find it very crashy. Several times per day, seemingly totally random, often while entering into the keyboard, though sometimes while it's just in my pocket. I've been able to determine no rhyme or reason.
No error messages, no apps crashing, no force closes, just several times a day it'll just freeze and reboot. Data loss is a common occurrence. I've lost my WhatsApp! database several times now, and a few others as well.
Is this just me, or is CyanogenMod 11 this crappy for other people too? I can't find a way to prove to myself that this is a hardware problem, the Android Stability Test app just keeps going and going. I've been watching adb logcat during a crash, and nothing interesting is output. Any suggestions on how to troubleshoot this?
starslab said:
Is anyone else running Cyanogenmod 11 M-releases on their Nexus 5?
I just got mine a week or two ago, and the first thing I did was unlock it and flash it to CyanogenMod 11. (M8 at the time)
I'm using the device encryption, because I'm a paranoid bastard (And I love the fact this phone is actually usable while encrypted, unlike my Nexus S), and I find it very crashy. Several times per day, seemingly totally random, often while entering into the keyboard, though sometimes while it's just in my pocket. I've been able to determine no rhyme or reason.
No error messages, no apps crashing, no force closes, just several times a day it'll just freeze and reboot. Data loss is a common occurrence. I've lost my WhatsApp! database several times now, and a few others as well.
Is this just me, or is CyanogenMod 11 this crappy for other people too? I can't find a way to prove to myself that this is a hardware problem, the Android Stability Test app just keeps going and going. I've been watching adb logcat during a crash, and nothing interesting is output. Any suggestions on how to troubleshoot this?
Click to expand...
Click to collapse
Try without encryption. It's hardly useful and only causes issues on Android.
Lethargy said:
Try without encryption. It's hardly useful and only causes issues on Android.
Click to expand...
Click to collapse
We'll have to disagree about the usefulness of encryption, (I like that if my phone is powered off, my data is PRIVATE until and unless my passphrase is entered) but I'll wipe the phone this eve, TRIM it, and get setup on it again without encryption.
starslab said:
We'll have to disagree about the usefulness of encryption, (I like that if my phone is powered off, my data is PRIVATE until and unless my passphrase is entered) but I'll wipe the phone this eve, TRIM it, and get setup on it again without encryption.
Click to expand...
Click to collapse
Maybe it's useful if you have something important on your device, but really, if you do, it shouldn't be kept on your phone anyways.
On Android, encryption is nothing but trouble, maybe it doesn't cause issues right away, but eventually it'll cause many. If you really wanted to keep things secured then I don't see why you would unlock the bootloader, flash a custom recovery and install a custom ROM.
Lethargy said:
Maybe it's useful if you have something important on your device, but really, if you do, it shouldn't be kept on your phone anyways.
On Android, encryption is nothing but trouble, maybe it doesn't cause issues right away, but eventually it'll cause many. If you really wanted to keep things secured then I don't see why you would unlock the bootloader, flash a custom recovery and install a custom ROM.
Click to expand...
Click to collapse
CyanogenMod has Privacy Guard, which is another feature I'm using, mostly with the aforementioned WhatsApp!, which has a list of permissions longer than my arm. I don't like it, but I need it for work.
I'll grant that the custom Recovery and ROM may slightly weaken the encryption (specifically an attacker could alter the ROM from Recovery), but even so having the encryption makes the phone a million times more resistant to data theft and tampering than not having it. It's worth noting that tweaking the ROM is the _worst_ an attacker could do. If I suspected such a thing had happened I could re-unlock the bootloader (which would wipe my data), and re-flash a known good Recovery and ROM. I'd lose my data, but even if the attacker had dumped the partition they still wouldn't have my key, and my data would still be private.
And the phone has crashed twice today. I'm going to repeat my original question - is anyone running Cyanogenmod 11-M on their Nexus 5, and if so is it stable? Should I be RMAing this phone, or should I try reverting it to stock first?
starslab said:
And the phone has crashed twice today. I'm going to repeat my original question - is anyone running Cyanogenmod 11-M on their Nexus 5, and if so is it stable? Should I be RMAing this phone, or should I try reverting it to stock first?
Click to expand...
Click to collapse
its more then likely the encryption. Disable it, re-flash and see what happens
No encryption. Wiped and trimmed the phone yesterday, now 4 crashes.
Try another ROM, see if it crashes. If it still does, flash factory images and see if it still does.
If so, RMA.
Nothing but trouble for me since upgrading to m9. I have been using the various M builds since March with no problems. M8 was fine. No device encryption for me. I tried turning it on and instead got stuck redoing the whole phone.
Now I get frequent crashing. I switched to the most recent nightly yesterday. Apps stopped crashing. However the os itself still crashes. Several times the screen wouldn't turn on after removing it from my pocket. The light was blinking so it definitely didn't just turn off. It also has stayed black after a few (but not all) phone calls. I've had to hard reset every time to recover.
Thinking about reverting to m8 backup. Willing to give it a few more nightie and see if it works out.
Where did you get it? I'm using the stable M9 snapshot off the CM site for hammerhead and it works pretty good.
Sent from my Nexus 5 using XDA Free mobile app
MrObvious said:
Where did you get it? I'm using the stable M9 snapshot off the CM site for hammerhead and it works pretty good.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Got it from the OTA update. Unfortunately I'm not experienced enough to know how to debug it or use proper logs. It could be that its an app I'm using combined with the most recent update...
Im using M9 snapshot too and i have not had 1 problem its been excellent
No problems for me on the M9 snapshot either. I'm coming up on 100 hours of uptime. Have you tried another kernel? I've always found that the stock CM kernel isn't the best. I'm using ElementalX 1..04 and it works pretty great.
C0dy said:
No problems for me on the M9 snapshot either. I'm coming up on 100 hours of uptime. Have you tried another kernel? I've always found that the stock CM kernel isn't the best. I'm using ElementalX 1..04 and it works pretty great.
Click to expand...
Click to collapse
+1. I installed another kernel (Chaos) for that reason and it's way faster.
OP: Maybe a bad flash? I would download M8 latest stable snapshot, and do OTA upgrade to M9. That's how I got mine.
C0dy said:
No problems for me on the M9 snapshot either. I'm coming up on 100 hours of uptime. Have you tried another kernel? I've always found that the stock CM kernel isn't the best. I'm using ElementalX 1..04 and it works pretty great.
Click to expand...
Click to collapse
Thanks for the suggestion. I actually have been using elemental and forgot to install it after the OTA. Will put that on now and see if it helps.
starslab said:
And the phone has crashed twice today. I'm going to repeat my original question - is anyone running Cyanogenmod 11-M on their Nexus 5, and if so is it stable? Should I be RMAing this phone, or should I try reverting it to stock first?
Click to expand...
Click to collapse
cyanogenmod is not what it used to be. it ALWAYS has one type of issue or another.
simms22 said:
cyanogenmod is not what it used to be. it ALWAYS has one type of issue or another.
Click to expand...
Click to collapse
Yeah it'll never be like the GB days. There's either audio problems, crashes, or other random problems. It's sad because people are expecting it to be like it was in old days. CM is not for stability, you can quote me on that.
Sent from Tapatalk on Nexus 5
last four hours have been fine since adding elemental. Hopefully works in the long run. 8/18 nightly.
Yeah it'll never be like the GB days. There's either audio problems, crashes, or other random problems. It's sad because people are expecting it to be like it was in old days. CM is not for stability, you can quote me on that.
Click to expand...
Click to collapse
What roms do you think are more stable than CM at this time?
trobbs said:
What roms do you think are more stable than CM at this time?
Click to expand...
Click to collapse
Just about any
My pixel had decided it's going to randomly freeze and reboot itself
It does it a few times a day and doesn't seem to matter what apps are running
Is there anyway of logging the reboots without root to find the cause?
Sent from my Pixel using Tapatalk
rosswaa said:
My pixel had decided it's going to randomly freeze and reboot itself
It does it a few times a day and doesn't seem to matter what apps are running
Is there anyway of logging the reboots without root to find the cause?
Click to expand...
Click to collapse
Same thing happening to me here too.
What I would do is start from scratch, install factory image, don't install any apps, use for a day to test, then install your apps one by one to find the culprit.
If still rebooting without any apps installed, it might be time for a rma
Sent from my Pixel using XDA-Developers mobile app
I used that Google support and came down to putting the phone I to safe mode for 24 hours to see but some days it does it a few times and other days it's fine
Sent from my Pixel using Tapatalk
Has there been any resolution to this? My Pixel has been randomly rebooting, too. Already tried troubleshooting with Google tech support, tried Safe Mode (did it there, too), and factory reset and cache wipe.
It still happens. And when I say random, I mean random. Sometimes it reboots overnight, sometimes in my pocket, sometimes as I'm using the phone (it'll freeze in some cases too before it reboots). There's no obvious indication of what's causing it.
Has there been any light shed on this problem? Any clue as to whether it's software or hardware related?
Some days it doesn't, others it'll do it 5times. I've not had any luck fixing it which is annoying because it awesome except for that
Google aren't very helpful either, they refused to help because I got my phone through carphonewarehouse lol
Sent from my Pixel using Tapatalk
rosswaa said:
Some days it doesn't, others it'll do it 5times. I've not had any luck fixing it which is annoying because it awesome except for that
Google aren't very helpful either, they refused to help because I got my phone through carphonewarehouse lol
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Yeah, there really is no rhyme or reason to the way it reboots, making it even harder to diagnose.
Rebooted again while it was just sitting on my table. No rhyme or reason to this bug.
I've had my 5" Pixel since launch. Google Store device, 32GB, never unlocked the boot loader.
I had a few random reboots, but never actually saw it happen. I'd go to use my phone and see the pattern unlock screen you get on first use after restart.
I have not had it occur since the January OTA.
UnusualSuspect said:
I've had my 5" Pixel since launch. Google Store device, 32GB, never unlocked the boot loader.
I had a few random reboots, but never actually saw it happen. I'd go to use my phone and see the pattern unlock screen you get on first use after restart.
I have not had it occur since the January OTA.
Click to expand...
Click to collapse
Same here. Sometimes I'll go to my phone wanting to use it, try my finger to unlock, and it'll prompt me to input my pattern because it's required after a reboot. Clearly, rebooting by itself.
It's frustrating because there's no rhyme or reason to it. Sometimes it'll happen multiple times a day, sometimes it won't happen for a couple of days.
At first, I thought the Jan update fixed it too because it didn't occur for a while after the update, but then it reared its ugly head again. I've already tested it in Safe Mode, did a factory reset, and the rebooting still persisted.
If you simply research this on the web, many others are having this issue. And it's even been reported a few times by Android sites/blogs. Google needs to get on top of this. At the very least, they should confirm it's a software issue and not a hardware issue.
---------- Post added at 10:08 PM ---------- Previous post was at 09:09 PM ----------
Just a few links of people online reporting this problem:
https://productforums.google.com/forum/#!topic/phone-by-google/QHp96fk4Ygw
https://productforums.google.com/fo...vS_XxvBh8;context-place=forum/phone-by-google
https://www.reddit.com/r/GooglePixel/comments/59i9e5/pixel_xl_random_restarts/#bottom-comments
Happens at random but only when I'm using Chrome or when my Pixel has been sitting on my nightstand charging.
I've had the phone since launch with no issues. My random reboots just started yesterday and it's happened 5 times in the past 12 hours. Glad I'm not the only one with the problem.
Sent from my Pixel XL using Tapatalk
im thinking this is a hardware issue, im pretty annoyed if it is! i get it like 6 times a day or nothing for a while, makes no difference what im doing or apps being used
Going to try and get a replacement this is a joke, fully wiped and flashed and still does it
Sent from my Pixel using Tapatalk
Mine hasn't really been "rebooting"... It's actually just been suddenly shutting completely off for no reason. It will be fine for a few days, then the next fee days it will simply abruptly shut off for no reason... Battery levels don't seem to make a difference.. Weird.
Sent from my Pixel XL using Tapatalk
For me it seems that the reason lies in Bluetooth or just in the BT stack. If I deactivate bluetooth it works fine through the day. But I need bluetooth so I started BT again and the Pixel XL 128GB crashes sometimes 10 Times a day, but as I checked BT was automaticly deactivated after these first reboots. I seemed. The Pixel stopped rebooting as I activated BT and deactivated it myself.
And now? How long do we have to wait. I don´t think it´s a hardware issue.
So, I have this issue but it became (very) apparent only after the OTA Oreo. First two weeks were fine (and subsequently first two weeks after a factory reset I've done), but then it slowly starts doing this after those 2 weeks. Freezes then reboots. At first it's 1-2 a day, now it's like 12-20. Ridiculous. There's a buganiser thread for this issue and Google is aware of it. Most of the bug reports have this in them:
Code:
Sense Key : Hardware Error [current]
which Google rep says is a hardware issue. I also have an access to a Google's internal buganiser thread on this issue (i'm a vendor) and they refer to this being a Toshiba's memory issue. Not sure though why this started happening only after the Oreo update. Also people who flash Nougat report no issues as well. Another funny thing is that there's at least two users with Pixel (XL) 2 who suffer from it. Anyway, I'll be giving it back to my carrier over the weekend (glad we have 2 year warrant here in UK) even though I'm pretty sure I'll get a refurb with a similar problem after two wasted weeks of wait.
Flash nougat rom and see does this problem occur or not? If not then us nougat for a while then again update to oreo
I sideload a lot of apps, and an annoying kwirk that I've found is that unknown sources does not stay enabled permanently. Everytime I attempt to install an app from unknown sources, I have to hop into settings and recheck unknown sources.
Yes, I do uncheck "this install only"
me too. I've turned it back on about a dozen times. This last time seems to be holding, for a day so far.
yeah, it's been driving me nuts, I kept having to do this with all my Amazon underground apps. I did notice in the settings though in my case, it showed checked, but once amazon tried to install an app, it would magically uncheck.
did the software update this morning and it did not fix this for me still.
A good example why root and tasker is needed; this has been my experiance with touch wiz on S7 as well, simple setti gs dont stick ore reset sometimes. With root andbtasker though you can wright tasks that will auto re-apply seetings when touch wiz drops the ball.
This is different, my unknown source settings stuck on my S7E and Note 7 I had.
Root isn't needed for this. If it only happened after a reset it'd be no big deal. It happens literally every time you try and install and app. Even if its 2 mins apart no reboot.
Have same issue. Never had this issue before with S7 Edge and was not rooted. The permission just doesn't stay like it should.
Man, I thought I was going nuts lol. Same issue, but at least it didn't break the feature.
I thought this was just me.
Sent from my SM-G955U using Tapatalk
Same issue here
Sent from my SM-G955U using Tapatalk
Same here
Sent from my SM-G955U using Tapatalk
Can confirm I'm having the same problem. I'll see if talking to Samsung will get them to patch it soon hopefully.
Ditto
Sent from my SM-G955U using Tapatalk
nosympathy said:
This is different, my unknown source settings stuck on my S7E and Note 7 I had.
Root isn't needed for this. If it only happened after a reset it'd be no big deal. It happens literally every time you try and install and app. Even if its 2 mins apart no reboot.
Click to expand...
Click to collapse
You misunderstand my post, often despite samsung best efforts, touch wiz is buggy, this is a bug!
Options;
1) You live with it
2) wait for samsung to fix, which in my experiance doesnt happen often
3) fix it yourself (but root and tasker required)
Same issue here, kind of a ridiculous bug
Same issue. At first, I thought Verizon struck again. I never know ifnitnis a bug or Verizon intentionally screwing with the OS.
VinylJStar said:
Same issue. At first, I thought Verizon struck again. I never know ifnitnis a bug or Verizon intentionally screwing with the OS.
Click to expand...
Click to collapse
Well I've got AT&T, and it's like this. Not tooooooo bad but still and annoyance, and definitely not intentional because there is a option to uncheck "for this install only". It should get fixed.
lol, i thought i was going crazy.
Same problem here thought it was weird.
I'm having the same issue. At least I know now that I'm not the only one
Mine does. I went into settings and turned it on. I installed 3 apps and it's still on.
Sent from my SM-G955U using Tapatalk