Related
Hey guys, so I just finished up changing my infuse over to Legend 2 ICS edition and I've been playing with it for about a week and I'm having a rather large issue. Whenever I leave the gps ability enabled so that my apps can find where I am the phone has a tendency to dump battery life like there is no tomorrow but worse than that it stops sending and accepting text messages randomly while the rest of the phone continues to operate. There are no warning signs so that I know this is happening and I have to reboot the phone to get it to work again. If I leave the gps feature off this is not an issue however, this is rather useful to have running so that my apps all work. Any idea how to fix this problem?? Thanks for your time.
I've been running legend 2 for almost a couple weeks and legend before that, my gps was buggy at first-it wouldn't lock on to my location. I did a complete wipe and reinstall, then let the phone boot up and let it settle for a while before I did anything else. Haven't had any problems since
---------- Post added at 03:13 AM ---------- Previous post was at 03:07 AM ----------
http://forum.xda-developers.com/showthread.php?t=1318160
http://forum.xda-developers.com/showthread.php?t=1561463
use clean wipe, I run that a few times just before I flash a rom now, haven't had any problems since I started using that.
Thanks a bunch I'll try that out and get back to you on if it works or not in the next couple of days.
Thanks
Sorry it took me so long to get back to you, work had me pretty tied up for a while. Thanks for the help everything seems to be working fine for the most part now. I need to reboot every once and a while due to overheating but I think thats just the fact that the phone is adjusting to the new ROM. Thanks again for the help.
Klevin2011 said:
Sorry it took me so long to get back to you, work had me pretty tied up for a while. Thanks for the help everything seems to be working fine for the most part now. I need to reboot every once and a while due to overheating but I think thats just the fact that the phone is adjusting to the new ROM. Thanks again for the help.
Click to expand...
Click to collapse
Hmmm, the phone shouldn't be overheating at all, do you do any tibu system restores? I've had an app cause an overheating problem before. One thing I've learned is when you do allot of flashing, checking out different roms or themes, its good to just do an odin or hemdall flash back to stock that has repartitioning.
It gives you a fresh start.
TiBu
I have done TiBu on the phone however I did have to flash it back to stock with odin partway through flashing this rom the second time because I bricked the phone, I'm still at a loss because I need to restart the phone usually once a day because it stops accepting and sending text messages without warning while everything else still works. It's kinda weird, I've been chalking it up to the fact that its a new rom and the phone needed to get used to it but it doesn't seem that way anymore.
Klevin2011 said:
I have done TiBu on the phone however I did have to flash it back to stock with odin partway through flashing this rom the second time because I bricked the phone, I'm still at a loss because I need to restart the phone usually once a day because it stops accepting and sending text messages without warning while everything else still works. It's kinda weird, I've been chalking it up to the fact that its a new rom and the phone needed to get used to it but it doesn't seem that way anymore.
Click to expand...
Click to collapse
Have you tried the new version 3 to see if maybe that helps? This is first Ive heard anything like this. I guess it works fine using another rom?
Sent from my SAMSUNG-SGH-I897 using xda premium
I didn't even know there was a version 3. I'll have to go take a look at that and see what happens. Thanks for the help.
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
Still having issues
Ok so I'm still having an over heating issue and my phone refuses to send or recieve texts for periods of time. I'm going to delete a couple of apps to see if they're causing the problem. If that doesn't work any chance that I'm having a hardware issue with the phone, it wouldn't be the first time I've had issues this would be my 5th replacement due to hardware issues in the phone.
I never had a random reboot on ICS now on JB I'm having it at least once a week...not a lot, I know but still something is not right. The last time this happened I tried looking further into it and the only thing I see that may be causing the issue is signal loss. I am 100% stock and have maybe 25 downloaded apps, if that. Is there an app for STOCK that will backup some of my data? I really don't think a factory reset will help but I'll give it a shot. Any other ideas? I freaking love this phone and this is my only complaint....would love to fix the problem. Thanks.
Here's a shot of the signal before the reboot.
Is it worth trying a factory reset? I feel the chances of it doing any good are very slim. Switch to a different modem?
Sent from my SCH-I535 using xda premium
I'm having the same issue, and a reset did not help.
Sent from my SCH-I535 using xda app-developers app
Thanks for the reply. As long as it does not get worse it's not a huge deal. Maybe the next update will fix it?
Sent from my SCH-I535 using xda premium
Not sure what the right word is (hotboot?) but today my phone rebooted (not fully) while I was using it. No fc's or freeze ups, just the reboot. I'm currently on the no wipe leak which ended up being the official ota.... Since the no wipe was modified would it make any sense to install the full wipe version to see if the problem is resolved?
Sent from my SCH-I535 using xda premium
Flashed full wipe via Odin. In case anyone else has this problem I will post back with results in a week or so.
Sent from my SCH-I535 using xda premium
I'm having the same issue. It seems that something is causing JellyBean-enabled SGS3's to just jump into "interrupt heaven". It's always a quick boot, never resets the "Up time" counter, and only takes a few seconds to get back to normal, but it's a real pain in the arse!
Any ideas what the culprit is, guys? I'm running a newly replaced (ordered it on January 2nd and the first thing it does was download and upgrade to JellyBean "VRBLK3" before I could even start get it loaded, basically as soon as I activated the phone, it started to download the OTA before I could even get to anything else). I know in my case I have a couple of mods installed - maybe one or more of these is common amongst those of us having issues? I have the "4x5 scrolling" mod and the "BLK3 Logo fix" mod that removes the stupid VZW drum-beating and pulsating display on boot-up. Other than that, my phone is rooted (using method involving loading the older ICS bootchain so you can install the latest CWM recovery), has CWM Touch 6.0.2.3 and that's about it, other than your usual rooted toolkit programs. Anything common to the rest of you?
Oh, by the way - I've already tried reformatting the cache, blowing away the dalvik cache and even a complete factory reset, which seems to make it less jumpy, but it always comes back within a day or two if not just a few hours.
I had the same problem with mine rebooting when I had very bad signal. Last Friday I did a factory reset then Odin to 4.0.4 and let the phone update to 4.1.1 and the problem seems to have gone away. I am not willing to call it cured yet, but it hasn't rebooted since. This went from where I was rebooting constantly all day long at work and when on the road in bad signal areas.
So far so good.
By the way, I looked EVERYWHERE and couldn't find anyone complaining of this earlier so I figured it had to be a bad download of the update.
It's something in Jelly Bean update itself. I tried booting my phone in "Safe Mode" - which only loads factory programs, and it still happens. I sure wish I could put a finger on anything in the way of a pattern, but - so far there's nothing I can single out that seems to make any difference. I'll do the system/factory reset and re-install everything one more time just to see if it helps.
Weird...
Factory reset (and everything else) - it still reboots
ratledge said:
It's something in Jelly Bean update itself. I tried booting my phone in "Safe Mode" - which only loads factory programs, and it still happens. I sure wish I could put a finger on anything in the way of a pattern, but - so far there's nothing I can single out that seems to make any difference. I'll do the system/factory reset and re-install everything one more time just to see if it helps.
Weird...
Click to expand...
Click to collapse
Well, something in a factory reset helps, but it doesn't last. First, just to be thorough, I used "ROM Manager" to 'fix permissions', then I did a complete flush of the system, removed the micro-SDXC card, did a format of the cache partition, flushed the Dalvik cache, then did a factory reset and reinstalled everything. I seemed to help for a while, but eventually it started to reboot randomly - sometimes when it was just sitting idle not even being used at all.
That indicates to me there's something funky in the JB (VRBLK3) firmware, especially since I was seeing reboots even while I was booted in safe mode, where nothing loads except factory-installed programs.
Fortunately, it never reboots while it's in recovery or download mode... :silly:
Ah, I forgot to note: this is the second phone that acts exactly the same way with the VRBLK3 (Jelly Bean) ROM update. Symptoms of the problem are identical, down to the spontaneous combustion that started this thread. Mine's not "in pocket" as per the OP, but - I don't think that has anything to do with it.
ratledge said:
Well, something in a factory reset helps, but it doesn't last. First, just to be thorough, I used "ROM Manager" to 'fix permissions', then I did a complete flush of the system, removed the micro-SDXC card, did a format of the cache partition, flushed the Dalvik cache, then did a factory reset and reinstalled everything. I seemed to help for a while, but eventually it started to reboot randomly - sometimes when it was just sitting idle not even being used at all.
That indicates to me there's something funky in the JB (VRBLK3) firmware, especially since I was seeing reboots even while I was booted in safe mode, where nothing loads except factory-installed programs.
Fortunately, it never reboots while it's in recovery or download mode... :silly:
Ah, I forgot to note: this is the second phone that acts exactly the same way with the VRBLK3 (Jelly Bean) ROM update. Symptoms of the problem are identical, down to the spontaneous combustion that started this thread. Mine's not "in pocket" as per the OP, but - I don't think that has anything to do with it.
Click to expand...
Click to collapse
Thanks for thoroughly trying different things to try and figure out the issue. Your problem seems worse than mine... I was getting reboots every few days. All day today was fine after installing full wipe but that's not a thorough test for what I was experiencing.
Sent from my SCH-I535 using xda premium
Ryno77 said:
Thanks for thoroughly trying different things to try and figure out the issue. Your problem seems worse than mine... I was getting reboots every few days. All day today was fine after installing full wipe but that's not a thorough test for what I was experiencing.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
You could also try getting a new sim from Verizon to see if that helps with connectivity to towers. You've already Odin flashed stock images and wiped pretty much everything significant at that.
New SIM?
SlimSnoopOS said:
You could also try getting a new sim from Verizon to see if that helps with connectivity to towers. You've already Odin flashed stock images and wiped pretty much everything significant at that.
Click to expand...
Click to collapse
Well, unfortunately I've done that - twice in the past ten days, the latest one came Tuesday afternoon. No change, still just reboots while I'm not even using the phone, and it's not the phone, it's the software. I can't say for absolute certain that it is in the VRBLK3 / JB code, but I can say for sure it _is_ something I am running, but the fact that it does reboot in safe mode indicates it's not anything downloaded or added to the base system as shipped.
ratledge said:
It's something in Jelly Bean update itself. I tried booting my phone in "Safe Mode" - which only loads factory programs, and it still happens. I sure wish I could put a finger on anything in the way of a pattern, but - so far there's nothing I can single out that seems to make any difference. I'll do the system/factory reset and re-install everything one more time just to see if it helps.
Weird...
Click to expand...
Click to collapse
Irrelevant question -- can't help my curiosity. How is it that you're on your 6th GS3? You get a new one every month?
6 Pebble Blue 32MB phones in about 8 months
jaymattt said:
Irrelevant question -- can't help my curiosity. How is it that you're on your 6th GS3? You get a new one every month?
Click to expand...
Click to collapse
Heheh... Well, I got one on "day 1" by pre-ordering it from Verizon, after two months the power button fell off. They sent me a "CLN" one, it lasted ten days and started randomly rebooting (even if reloaded with 'virgin' unrooted OS), the third (another "CLN") was delivered with no power button and the volume rocker fell off while I was taking it out of the box. At that point, I got kind of pizzed and did the 'good customer for 10 years' and elevated it through three levels until I finally got them to ship me a brand new one. That one lasted two months until my wife left it on top of my car and I backed over it in my driveway. I used my Asurion (insurance) to get #5, which arrived rebooting from the moment I started it up. Within a few days after monkeying around with their tech support (they ain't the brightest bulbs - instructions include "remove the battery and dial yourself and hit the 'Send' key three times" - not kidding) I managed to get #6 shipped out, and it's first act of life was to suck down the VRBL3 (Jellybean) software update and I've mucked around with it for two weeks, tried loading it with various combinations of "No Wipe" and "Factory Reset" versions of VRBLK3, removed a bunch of programs I've had installed but never really used and it still just vibrates about once an hour (and it's totally random, sometimes lasts 6 hours, sometimes 6 minutes before rebooting), jumps to the "warm/quick start" and recycles without resetting the "time up" counter. I'm thinking it's something I fed it (i.e. a nasty program or interaction between programs) - but I've come up empty-handed so far as running it to ground.
Does anyone have any knowledge of known interactions or "bad programs" that just don't play well together under JB?
Sadly my friend, you need CLN #7. Nothing here is going to resolve that.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Sadly my friend, you need CLN #7. Nothing here is going to resolve that.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Well, normally - I would agree. But this makes three phones that act exactly the same in a row. The first of which was my 2nd "New" GS3, updated OTA to Jellybean - which immediately started the rolling reboots. The problem with the "CLN" phones are that they were all defective in one way or another, or they wouldn't be recertified. I don't really think VZW does a good job recertifying these phones, there are just too many of them coming out every single day, and - lord knows Asurion probably is behind that curve. :silly:
All three phones have been identical in their behavior - "down to the letter" since VRBLK3 was released. :fingers-crossed:
Question: now that I've used my insurance, do I _have_ to go back to Asurion for replacement, or since I'm still in my first year, will VerizonWireless entertain sending me another? It seems like reading the information that comes with the Asurion phones, they are the ones that are now guaranteeing my phone for a full year from the time it was sent (that would be this past Monday).
The phone has an Asurion sticker inside it, not a VZW one...
And the winner is: battery replacement. Every single VZW marked battery causes it to reboot, but a plain old Samsung battery (made in Korea - I've noticed almost all the VZW branded SKUs are made in China) works 100% and gives me an average of 12 hours moderate usage. The batteries I had from previous phones, VZW and Asurion all have the Verizon markings on them, and every single one of them causes it to reboot. This new one I got today straight from Samsung does not.
Curious, huh? I have one out of five batteries with VZW markings, and it does the same as the other four "made in China" ones. You've gotta wonder...
Glad you found a fix. Is it possible the new battery is slightly larger? Wondering if the old batteries were maybe a bit loose.
Sent from my SCH-I535 using xda premium
Hey guys!
I have posted before but since then the issue has exacerbated to the point where I'm at my wit's end.
I have the SM-P907A AT&T version of this tablet. I bought it second hand and started experiencing issues almost immediately, although nothing as bad as what I'm going through now.
It began with the odd blue-screen and very rare restart. It quickly escalated when I created multiple profiles (user ids). The restarts would happen entirely randomly but without fail within 10 minutes of operation no matter what I did. Oddly enough, it would NEVER restart when connected to a power supply, though I have drawn very little from that.
Thusly, I factory reset my tablet and hoped that would fix the issue; to no avail. Then I decided to Odin flash the stock ROM. Again no joy. Restarts were persistent and regular when the tablet wasn't connected to a power supply. I then rooted the tablet, installed Titanium Backup Pro and proceeded to freeze all apps/odex-es related to Samsung Knox. As some have posted, doing this helped them out. Not lucky enough, I guess.
My questions:
Did my setting up multiple users somehow mess with the tablet in such a deep and integrated way that even factory resetting, re-flashing stock would not help? Is that even possible? My firmware version is P907AUCU1AND7. I'm going to manually update to Lollipop but if my meddling with the multiple users "broke" something essential, will that help?
No, proppably not
kalaris said:
Hey guys!
My questions:
Did my setting up multiple users somehow mess with the tablet in such a deep and integrated way that even factory resetting, re-flashing stock would not help? Is that even possible? My firmware version is P907AUCU1AND7. I'm going to manually update to Lollipop but if my meddling with the multiple users "broke" something essential, will that help?
Click to expand...
Click to collapse
I don't think that using the multi user functionality has anything to do with the issues you are experiencing. I have 3 user on my tablet and using it for a year now. Both on KitKat and Lollipop that I am using now. Both rooted, KitKat with Xposed also. Never had issues with blue screens and reboots.
Issues with US devices have been posted regularly and explanations have been posted. Don't focus on multiuser for the issues you experience.
I' am using the SM-P905 International version (EUR)
PDA: P905XXUABOG1
CSC: P905EURABOG1
Ridiculous
Okay guys. Seriously ridiculous. I downloaded the lollipop ROM but got an error when adb sideloading it because it requires the previous firmware P907AUCU1ANK2 for it to update properly whereas I have the one older than that: P907AUCU1AND7.
Can someone help a brotha out? Post a link from where I can download it?! Maybe share their stock rom file?! Pretty please? I've managed to find only TWO results on google. One is a mobilefileserver result requiring that I Pay $60. The other is a Chinese site requiring that I pay significantly less but in a way which is baffling me at the moment.
Any good guy out there who can help??????
A member posted links to it in 5.1.1 upgrade posts...
Sent from my SPH-L300 using XDA Free mobile app
zomg! thank you! how'd i miss this?!
kalaris said:
The restarts would happen entirely randomly but without fail within 10 minutes of operation no matter what I did. Oddly enough, it would NEVER restart when connected to a power supply, though I have drawn very little from that.
Click to expand...
Click to collapse
Random restart is the problem of cracked battery connector. Re solder the battery connector will fix it permanently.
Read the thread " Flickering Screen " in Galaxy Note or Tab Pro, you will see they all have similar problem like yours and the fix is simple.
No software or upgrade will fix the hardware problem, regardless Kitkat or Lollipop.
Hi everyone!
I have a international version of the s7 that I bought in France.
Since 1 week, my phones crash randomly and also every time I try to update or download an app on the store. It happens with two different roms (superman and galaxy project).
But not happy to only crashing, it also bootloop after it, sometimes during 20 minutes before booting correctly. And it makes the phone's temperature going up a lot. With all the issues with the note 7 heating and blowing, I fear for my s7.
Also, I can't just return it, because I'm not in France anymore, and it costs a lot to pay the taxes if I want to send it for a check (especially if they do nothing on it)
I was wondering if the cpu clocks on the roms has something to do with it.
If you have any suggestions, I'll wait for it.
Thanks
Sacher_Masoch said:
Hi everyone!
I have a international version of the s7 that I bought in France.
Since 1 week, my phones crash randomly and also every time I try to update or download an app on the store. It happens with two different roms (superman and galaxy project).
But not happy to only crashing, it also bootloop after it, sometimes during 20 minutes before booting correctly. And it makes the phone's temperature going up a lot. With all the issues with the note 7 heating and blowing, I fear for my s7.
Also, I can't just return it, because I'm not in France anymore, and it costs a lot to pay the taxes if I want to send it for a check (especially if they do nothing on it)
I was wondering if the cpu clocks on the roms has something to do with it.
If you have any suggestions, I'll wait for it.
Thanks
Click to expand...
Click to collapse
Hi
Do a factory reset , do not restore anything see if it works ok , if so then it maybe an app causing the problem
or you could flash a stock rom to test the phone and make sure there is no hardware issues
Thank you for your answer.
I'll take a try this weekend with a stock rom as I have the issue with 2 custom roms so far.
If anybody has other ideas until that, please let me know
Little feedback. I flashed the stock Samsung rom two days ago and it seems to work fine for now. But it was also quite fine with the custom rom at the beginning, so I will do another feedback after one or two weeks.
Well... The phone froze and rebooted 5 times in 10 minutes after trying to update some apps itself...
I had the same problem. At the end I was not able to boot Android. I had to claim my cell phone to seller. After one month it was repaired. The final verdict was SOFTWARE problem. They said that EFS was corrupted. One of Samsung firmware has bug which cause problem with EFS.
I also had that problem. I also had to send my phone to the repair center. In my case they replaced the mainboard.
I bought one early september and after two weeks it started doing just that. I tried everything, then sent it to the seller (ebay seller...) and the repair shop couldn't anything about it. I only got my money back yesterday. Back when I invesitgated the issue, nobody was talking about it. So since I liked the phone, I bought a new one from another place (less shady) yesterday... I now think I shouldn't have. Anybody knows more about this ?
Edit: I'm thinking that if I root the phone and backup the EFS and all sensitive partitions before starting using it (or even getting updates) I should be safe...
Yeah, that would be great, but your KNOX will be 0x1. So you will have problem to return this phone back with status 0x1.
Odoslané z SM-G930F pomocou Tapatalku
Hello everybody,
Sorry for the very late reply. I actually sent my phone to another shop here in Japan. But this week, they send me a mail to say that they were not able to fix the issue. But still they taker me 50$ for the time...
I was thinking about buying a new one, but now that some of you are talking about an EFS issue, I'll try to fix again. I will look for some tutorial for that, but if you know how to procede, just reply here
Merry Christmas guys !
hello, i've been having a similar issue.
My phone would be fine for 2 weeks, maybe a month then Suddenly it would reboot to no end, it even reboots from TWRP.
It doesn't reboot while in Download mode. Then what i do to fix it is flash a stock rom from ODIN, sometimes the first couple or 5 times it will reboot during initial first boot up of this stock Rom. I would leave it alone for a while like half day then try it again in the evening or the next day.
Today for example, it started boot looping late last night and I installed Stock ROM with PIT FILE and Nand ERASE and Repartition ticked, boot loop, again, boot loop, tried it again, also rebooted before it started up to stock recovery and factory reset. Then it started up fine and has not rebooted so far.
But this has happened many times and it'll happen after 2 weeks or 1 month. When it does, i first go and delete cache and delvic cache to see if that would fix it, but it doesn't.
Right now it works, but for how long i don't know, when it works, everything is fine with the phone, no imei or calling or heating issues.
I can't guess whats wrong, is it really EFS that got corrupted but not fully but eventually its finding a problem and causing boot loops or something if that makes sense??
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