Related
hey, i have had my Galaxy S3 sence black friday of 2012, and it is not rooted or anything. but just recently within the last few weeks, it has randomly restarted, like im texting or playing on FB and then screen goes black then i see samsung logo. any sugestions on how i can fix this?
Mine recently started doing the same thing. After being rooted about a year ago, and being stable on the same ROM for the last 6 months or so, it randomly started rebooting itself 10-20 times a day.
I tired installing a stock ROM, stock kernal, etc. but nothing helped. I eventually unrooted it using QBKing77's video (on this site) and used Odin to install the stock tar image. This was in preparation to take it back for what I could only assume was a hardware issue. After a *lot* of automatic OTA updates (maybe 8 -10 or more!) it seems to have solved the issue. The phone has been stable without a restart for the last 48 hours.
In addition to that, I also pulled my sd card and ran it through the windows disk tools which said it found a few errors and corrected them. So at this point I don't know if it was ROM/kernal related, card related, or a perfect storm of a combination of each. I'd suggest you pull your sd card and use windows to check it 1st since that'd faster and easier. If that doesn't work, unroot.
I plan on waiting another day or two before I unroot again, just to be sure it's still stable. Hope this helps.
** Just saw that you're unrooted. If you're still in warranty, take it back. If not, try rooting it, and installing a new kernal or ROM and see if that helps.
i am not in warrenty, i wish but im not. i dont want to root it,
Check if your battery is swollen, the spin test works pretty well if you're unsure just by looking at it. A swollen battery is one of the most common reasons for frequent reboots if you're running stock.
Power button failure known defect with S3. They replace them at Sprint. It's referred as Sudden death syndrome.
Sent from the future via Tapatalk 4
Ok here is my question - Two times i have installed CM11 roms, the newest nightlies, after wiping data / cache, using CWM for recovery, and rumrunner to achieve s-off / unlock. The first time my phone functioned fine for a few days, then began over heating and the top speaker quit working, started issuing static after certain apps turned on, or when the phone booted up. Also - battery was draining faster than i could charge it. Would jump multiple % points at a time.
I "BELIEVE" that my charger has gone bad, and that is the culprit for destroying the phone. Even after flashing back to stock, removing s-off and relocking the bootloader, it drained the battery(even when powered off battery continued to drain and phone was hot to touch).
After this happened to my first htc one, i returned it to stock, and got a replacement under warranty. Then i proceeded to root / s-off / unlock my new htc one, and drop CM11 m7vzw onto it. It functioned fine.......until i plugged it into the charger that i think is the culprit. After hitting 100% power, the phone started to heat up and the top speaker quit functioning. I instantly upon noticing this, used CWM to restore a backup of the stock software. Which did nothing to fix the problem, phone continued to over heat and drain the battery, only one speaker worked. I managed to flash it back to the stock oem RUU software and relock the bootloader, attain s-on before it died completely(so i could turn it in for warranty with no issues AGAIN).
My question - is this a bad charger you think, that is killing my phones? Or could it possibly be something inside of CM11 and PA gapps(4.4) killing my phones? I do not have a meter on hand to test my charger, so i am going on logic that it must be the charger. Since i can't imagine that cm11 is killing every m7vzw it is installed one, and it seemed to function fine until i plugged into that charger.
I love custom roms, and seriously hate all the bloatware that comes attached to verizon phones, so looking for some advice from people mor familiar with this subject then i am. I have only recently started customizing my phone. My back ground is in computers not phones, but seeing as how i am not tweaking the cpu or gpu at all, i am thinking it MUST be this charger. Please let me know what you think, if you have experience with this on a m7vzw. I get another phone tomorrow, and do not plan on using the same charger again, but i am somewhat wary as to upgrading the rom after all this crap ive been through. ANY advice is appreciated. Much thanks!
ccarr313 said:
Ok here is my question - Two times i have installed CM11 roms, the newest nightlies, after wiping data / cache, using CWM for recovery, and rumrunner to achieve s-off / unlock. The first time my phone functioned fine for a few days, then began over heating and the top speaker quit working, started issuing static after certain apps turned on, or when the phone booted up. Also - battery was draining faster than i could charge it. Would jump multiple % points at a time.
I "BELIEVE" that my charger has gone bad, and that is the culprit for destroying the phone. Even after flashing back to stock, removing s-off and relocking the bootloader, it drained the battery(even when powered off battery continued to drain and phone was hot to touch).
After this happened to my first htc one, i returned it to stock, and got a replacement under warranty. Then i proceeded to root / s-off / unlock my new htc one, and drop CM11 m7vzw onto it. It functioned fine.......until i plugged it into the charger that i think is the culprit. After hitting 100% power, the phone started to heat up and the top speaker quit functioning. I instantly upon noticing this, used CWM to restore a backup of the stock software. Which did nothing to fix the problem, phone continued to over heat and drain the battery, only one speaker worked. I managed to flash it back to the stock oem RUU software and relock the bootloader, attain s-on before it died completely(so i could turn it in for warranty with no issues AGAIN).
My question - is this a bad charger you think, that is killing my phones? Or could it possibly be something inside of CM11 and PA gapps(4.4) killing my phones? I do not have a meter on hand to test my charger, so i am going on logic that it must be the charger. Since i can't imagine that cm11 is killing every m7vzw it is installed one, and it seemed to function fine until i plugged into that charger.
I love custom roms, and seriously hate all the bloatware that comes attached to verizon phones, so looking for some advice from people mor familiar with this subject then i am. I have only recently started customizing my phone. My back ground is in computers not phones, but seeing as how i am not tweaking the cpu or gpu at all, i am thinking it MUST be this charger. Please let me know what you think, if you have experience with this on a m7vzw. I get another phone tomorrow, and do not plan on using the same charger again, but i am somewhat wary as to upgrading the rom after all this crap ive been through. ANY advice is appreciated. Much thanks!
Click to expand...
Click to collapse
Are you using the stock charger?
Try a different charger on the next phone. Many people have flashed CM11 and don't have those issues so it appears to be your charger that's killing the phones.
Don't think it's the charger. I am seeing more and more threads of people running cm11 a d getting this overheat issues then phone dying. I think it's best that people leaves cm11 alone until it can be fixed. As I have never seen any other Rom act like this.
Sent from my HTC6500LVW using Tapatalk
The only thing i can think of, after resting on it, is that i turned on the DSP manager EQ shortly before it happened each time. Not going to customize the one I am getting today. Just thankful I know enough that I managed to get them both back to s-on / locked / stock RUU before sending them back.....so my warranty will cover them.
And yes, i was using the stock HTC charger that came with the device. Wish i had a meter.
This is odd. I have been using CM 11 for close to a week now, and haven't experienced any issues like this yet, and hopefully won't. The battery life isn't great (and I will probably return to using BoneStock from @andybones ), but no overheating or speaker issues. I don't normally listen to a lot of music, and I have not messed with DSP manager much, but I have used it, and music/videos seem to work fine. I would recommend trying a different charger to rule that out. Also, if you are getting a warranty replacement, try leaving the phone s-on and stock for a few days and see how it acts with your charger - that will help narrow down the real cause.
peteschlabar said:
This is odd. I have been using CM 11 for close to a week now, and haven't experienced any issues like this yet, and hopefully won't. The battery life isn't great (and I will probably return to using BoneStock from @andybones ), but no overheating or speaker issues. I don't normally listen to a lot of music, and I have not messed with DSP manager much, but I have used it, and music/videos seem to work fine. I would recommend trying a different charger to rule that out. Also, if you are getting a warranty replacement, try leaving the phone s-on and stock for a few days and see how it acts with your charger - that will help narrow down the real cause.
Click to expand...
Click to collapse
Both phones are dead. Will not charge, will not turn on. They only worked for a few hours after the over heating issue started. Battery continued to drain even after being turned off, and after it was drained it would not charge at all. It was lucky i could even get them back to s-on / locked / stock. And the issue continued after going back to stock. Hardware damaged for sure. So no more testing on those. lol
On the next one, wait a week before installing a ROM, and see if the phone functions fine. If not, then its the charger or something else you've been doing with it. If it is fine, try installing cm11 again and see if it returns. If it returns at THAT point, then it might be the ROM, though I doubt that's the issue. You'll never know if its cm11 or something else causing the issue if you immediately flash it after getting it.
Fu5ion said:
On the next one, wait a week before installing a ROM, and see if the phone functions fine. If not, then its the charger or something else you've been doing with it. If it is fine, try installing cm11 again and see if it returns. If it returns at THAT point, then it might be the ROM, though I doubt that's the issue. You'll never know if its cm11 or something else causing the issue if you immediately flash it after getting it.
Click to expand...
Click to collapse
That is my plan, and i have other chargers. I don't plan on using the HTC one. Going to use a stock samsung charger until i get my replacement charger in the mail. I am hoping it was the charger. It just seemed odd that the issue happened both times after turning on DSP, then using the phone to either watch netflix, or listen to music on the speakers. Also, I figure if no one on these forums has the same issue.....then it must be the charger. In the meantime - I am just going to root / s-off and use stock software till next week or so.
I'm just getting paranoid as to how many times verizon will let me get a warranty replacement, even though i am sending them back in full stock format. lmao
ccarr313 said:
That is my plan, and i have other chargers. I don't plan on using the HTC one. Going to use a stock samsung charger until i get my replacement charger in the mail. I am hoping it was the charger. It just seemed odd that the issue happened both times after turning on DSP, then using the phone to either watch netflix, or listen to music on the speakers. Also, I figure if no one on these forums has the same issue.....then it must be the charger. In the meantime - I am just going to root / s-off and use stock software till next week or so.
I'm just getting paranoid as to how many times verizon will let me get a warranty replacement, even though i am sending them back in full stock format. lmao
Click to expand...
Click to collapse
They'll let you send as many as you want as long as its under warranty haha. I remember I had to send in the droid bionic 4 times and the droid RAZR twice, both times without any hassle from them. I just had awful luck with those phones, mostly screen-lifting.
Haha. Good to hear. Because I have 10 months of warranty left, and I am a computer modder at heart.....and that has turned me into a custom rom loving phone crazy person. :laugh:
Yeah you've got nothing to worry about there. Just make sure its back to stock. They honestly probably wouldn't say anything if it weren't, but we don't want to give them even more reasons to lock us down more.
I'm having the same issues. I'm on my 4th phone now.
This happened to me on several ROMs. SlimBean 4.3, SlimKat 4.4 now.. and I flashed back to stock while I had a phone that wasn't dead yet.. but it's still happening.
I'm not sure what the deal is. Just happens without rhyme or reason out of the blue one day.
Can anyone recommend flashing anything that might help?
What's responsible for the battery management even if there's no ROM installed? HBoot? Should I re-flash an HBoot to attempt to fix? It's not the ROM, I don't think. If it is, it's something that permanently screws up the phone. I've completely wiped my phone and went to stock. Same issue.
I got my new phone, and s-off'ed / unlocked / flashed cwm recovery, then updated it to 4.3 ota, no issues so far. Scared to put any custom rom after what happened to the last two. But having no issues yet with it, with only a custom recovery and s-off. Have rom manager loaded also, and made a back up since it seems to be running fine now. If anyone isolates this problem and can get a fix going, would make me very happy.
I've noticed that trickster and some of the other CPU performance apps are locking the min CPU speed at the max speed so the phone always stays at top speed. If it stays like that for an extended period of time it will damage the phone. The heat can cause the battery to drain really fast and damage the CPU. If you are on any ROM with a custom kernel I would be on the lookout for this.
Sent from my HTC6500LVW using Tapatalk
I was running CM11 on my nexus Galaxy and I thought my battery was bad. My phone would die after a few hours. I got a new battery and it did the same. I installed slim ROM and now I am getting 10+ hours no problem. Also my phone does not feel like it is going to melt.
Phone was sold as is, it turned on but the battery was drained completely and died soon after reaching home screen. I took a plunge since price was $50 tempting Washingtons :laugh: I was 100% sure something is wrong with this device but **** it i did it. Bought a charger and USB cable on the way home and so far it's charging just fine.
Phone is mostly erased at least manually I think, because somebody left his google account as I can see email in the plays store menu and some apps, or maybe this is all the carrier pre-installed junk I'm looking at ? LOL
I don't have much experience with Samsung devices but it's a SM-N900T model with N900TUVUCNB4 4.4.2. from February 2014 according to this site http://www.galaxynote3update.com/galaxy-note-3-odin-factory-stock-firmware-usa-canada/
My question is do I stay on this Android or do I jump to Lolipop ? Wasn't there some memory issues with 5.0 ? Or maybe Custom builds ?
Your first move is to sell it to me for $5
If I was OP, I would fully charge the phone, do full factory reset and run it few days as is to test if everything works,. Once you start updating, especially custom ROM, things can break and you'll never know if it's software or hardware. If everything works fine, then you could decide for yourself what to do next. My biggest worry would be the phone is blacklisted, since Note 3 in good shape sells for $200-$300.
OK
Phone charged fully I booted it up and after short amount of time it would freeze constantly when bringing up the keyboard (Samsung or google), can't recall which one was first now because I was changing them in settings and nothing helped. Either way it was freezing after typing couple of letters or appear then crash/disappear. All this combined with some crashes from app called Lookout. Google told me to do Volume UP+HOME+POWER and do a factory reset, after that everything works fine now. Changed my sim card and I can place calls with no issues also data works fine but damn there is tons of f***ing poopy preloaded apps in here from Samsung and other garbagio . I think whoever was using this device had no idea what to do with those errors and just stopped using it somewhere around Feb. 2014 because since then basically nothing was updated on it. I'm gonna let it sit for couple of days then probably will upgrade to 5.0 via KIES and maybe replace the battery either way with OEM or maybe something like this ? http://www.amazon.com/Anker-T-Mobile-Compatibility-18-Month-Warranty/dp/B00FF54C8Q/
4xxxxL said:
OK
Phone charged fully I booted it up and after short amount of time it would freeze constantly when bringing up the keyboard (Samsung or google), can't recall which one was first now because I was changing them in settings and nothing helped. Either way it was freezing after typing couple of letters or appear then crash/disappear. All this combined with some crashes from app called Lookout. Google told me to do Volume UP+HOME+POWER and do a factory reset, after that everything works fine now. Changed my sim card and I can place calls with no issues also data works fine but damn there is tons of f***ing poopy preloaded apps in here from Samsung and other garbagio . I think whoever was using this device had no idea what to do with those errors and just stopped using it somewhere around Feb. 2014 because since then basically nothing was updated on it. I'm gonna let it sit for couple of days then probably will upgrade to 5.0 via KIES and maybe replace the battery either way with OEM or maybe something like this ? http://www.amazon.com/Anker-T-Mobile-Compatibility-18-Month-Warranty/dp/B00FF54C8Q/
Click to expand...
Click to collapse
If you're planning on keeping it, you'd be better spending the extra $ on one of these mate: http://www.amazon.com/Zerolemon-Zer...d=1453047493&sr=1-1&keywords=ZeroLemon+Note+3
I'm getting 6 days on a full charge outta mine, compared to 1 day with stock battery (course I'm running a custom rom, but when I was back on stock with my ZeroLemon, I was getting 3 days outta it)
4xxxxL said:
OK
Phone charged fully I booted it up and after short amount of time it would freeze constantly when bringing up the keyboard (Samsung or google), can't recall which one was first now because I was changing them in settings and nothing helped. Either way it was freezing after typing couple of letters or appear then crash/disappear. All this combined with some crashes from app called Lookout. Google told me to do Volume UP+HOME+POWER and do a factory reset, after that everything works fine now. Changed my sim card and I can place calls with no issues also data works fine but damn there is tons of f***ing poopy preloaded apps in here from Samsung and other garbagio . I think whoever was using this device had no idea what to do with those errors and just stopped using it somewhere around Feb. 2014 because since then basically nothing was updated on it. I'm gonna let it sit for couple of days then probably will upgrade to 5.0 via KIES and maybe replace the battery either way with OEM or maybe something like this ? http://www.amazon.com/Anker-T-Mobile-Compatibility-18-Month-Warranty/dp/B00FF54C8Q/
Click to expand...
Click to collapse
Actually you can root the phone easily, even without tripping knox on kitkat, once rooted you could freeze or kill on start up most apps that bother you, that's what I do and problem solved, phone runs like a dream.
pete4k said:
If I was OP, I would fully charge the phone, do full factory reset and run it few days as is to test if everything works,. Once you start updating, especially custom ROM, things can break and you'll never know if it's software or hardware. If everything works fine, then you could decide for yourself what to do next. My biggest worry would be the phone is blacklisted, since Note 3 in good shape sells for $200-$300.
Click to expand...
Click to collapse
There is actually an easy way to not worry about the blacklisted issue before you ever buy a phone from someone. You can go to www.swappa.com/esn and check the status of the phone by entering it's IMEI. We buy and resell phones a lot and this is how we check them. You can check up to 10 phones free every 24 hours on the site.
4xxxxL said:
OK
Phone charged fully I booted it up and after short amount of time it would freeze constantly when bringing up the keyboard (Samsung or google), can't recall which one was first now because I was changing them in settings and nothing helped. Either way it was freezing after typing couple of letters or appear then crash/disappear. All this combined with some crashes from app called Lookout. Google told me to do Volume UP+HOME+POWER and do a factory reset, after that everything works fine now. Changed my sim card and I can place calls with no issues also data works fine but damn there is tons of f***ing poopy preloaded apps in here from Samsung and other garbagio . I think whoever was using this device had no idea what to do with those errors and just stopped using it somewhere around Feb. 2014 because since then basically nothing was updated on it. I'm gonna let it sit for couple of days then probably will upgrade to 5.0 via KIES and maybe replace the battery either way with OEM or maybe something like this ? http://www.amazon.com/Anker-T-Mobile-Compatibility-18-Month-Warranty/dp/B00FF54C8Q/
Click to expand...
Click to collapse
Sounds like you did get lucky and come across someone who wasn't tech savvy at all, and had no idea how simple it was to fix. But hey... that's their lose and your gain.
If you do decide to root it at some point and want to run a custom ROM, click on the top banner in my signature and check it out. I think you might just like it.
kevp75 said:
If you're planning on keeping it, you'd be better spending the extra $ on one of these mate: http://www.amazon.com/Zerolemon-Zer...d=1453047493&sr=1-1&keywords=ZeroLemon+Note+3
I'm getting 6 days on a full charge outta mine, compared to 1 day with stock battery (course I'm running a custom rom, but when I was back on stock with my ZeroLemon, I was getting 3 days outta it)
Click to expand...
Click to collapse
Yeah man, there is an awesome custom ROM out for this phone. I can't remember the name right off hand, but I'm sure you've heard of it. Haha
pete4k said:
Actually you can root the phone easily, even without tripping knox on kitkat, once rooted you could freeze or kill on start up most apps that bother you, that's what I do and problem solved, phone runs like a dream.
Click to expand...
Click to collapse
You can freeze them, but in my opinion if you've gone to the trouble of rooting it, you might as well completely remove the bloatware. If all you do is freeze the apps, they are still there needlessly taking up the internal storage. There are a few lists on here that tells what is safe to remove without fear of messing the phone up.
problem with deleting "bloatware" is two fold: some programs are interdependent and deleting one you don't want may break another you need. Also, I don't know about others, but I changed my mind in the past and reactivated some applications I never thought I'll be using before.
As far as space goes, the whole system uses 4 GB maybe, so you could save 1 GB, if you're aggressive deleting files, probably couple min of 4k video worth. I got 128 GB sd card, problem solved. Maybe different story with Note 5, but that's one of main reasons I never upgraded.
Either way I strongly suggest at least freezing apps and testing before deleting it.
TimboMachimbo said:
Your first move is to sell it to me for $5
Click to expand...
Click to collapse
Lmao
Still been using the device to watch stuff on wifi @ home and **** Can't use it as my daily driver it's just to big :0 anyway the other hidden issue that I found out about it is that the charging port is kinda beaten up especially on the left side. Sometimes you can plug the cable in and it won't charge until you apply little pressure on the connectors left side it's time to do this http://www.amazon.com/Charging-Ribbon-Connector-Samsung-T-Mobile/dp/B00H3DZRXC/
Alliance Rom
4xxxxL said:
Phone was sold as is, it turned on but the battery was drained completely and died soon after reaching home screen. I took a plunge since price was $50 tempting Washingtons :laugh: I was 100% sure something is wrong with this device but **** it i did it. Bought a charger and USB cable on the way home and so far it's charging just fine.
Phone is mostly erased at least manually I think, because somebody left his google account as I can see email in the plays store menu and some apps, or maybe this is all the carrier pre-installed junk I'm looking at ? LOL
I don't have much experience with Samsung devices but it's a SM-N900T model with N900TUVUCNB4 4.4.2. from February 2014 according to this site http://www.galaxynote3update.com/galaxy-note-3-odin-factory-stock-firmware-usa-canada/
My question is do I stay on this Android or do I jump to Lolipop ? Wasn't there some memory issues with 5.0 ? Or maybe Custom builds ?
Click to expand...
Click to collapse
Flash Alliance 5.0 Lollipop ...best rom for note 3
http://forum.xda-developers.com/not...-alliancerom-n900t-uvufob6-v1-online-t3055309
Replaced the charging port with the $5 one I bought via Amazon... charging worked great but the voice recording and mic in general sounded garbled had to put the broken one back lol :S
I've noticed recently (~3 times in last couple weeks), my Pixel XL will not start charging unless I re-boot, from 25%-35% charge. I've swapped chargers (Nexus 5X vs Pixel XL) and USB-C cables without success.
A simple reboot fixes the issue, but is a bit of a pain.
Pixel XL 128
7.1.1, Jan Update
Rooted
TWRP
Verizon SIM
Anyone else seeing this oddity? Any suggestions to correct??
Edit: 1/15 Replacement Device received, unlocked & rooted. The issue returns after just one day! Reboot needed to re-charge.
I have this same problem! I have had it since getting the pixel with root, custom kernel. Thought it was the kernel but the device swears it has nothing to do with it.
I haven't had TWRP very long but it happens still. It's random, and a reboot always fixes.
I wish I knew the cause, but too annoying to run full stock unrooted to test lol.
I've had this issue as well even with stock. Completely random. I've since flashed Pure Nexus since it's release and haven't had the issue anymore.
Happened again this morning. Gah, no overnight charge.
Chatting with Brian at Google.
He jumped to "Sending a Replacement Phone" after about 2 mins of very basic discussion. Seems odd, but whatever. Seemed a pretty quick surrender...
I did inquire if this was a known issue. He said, No, probably just a rare scenario.
I'll probably run stock for a while on the new phone to see if this recurs. Then I'll return to root and monitor.
markp99 said:
Chatting with Brian at Google.
He jumped to "Sending a Replacement Phone" after about 2 mins of very basic discussion. Seems odd, but whatever. Seemed a pretty quick surrender...
I did inquire if this was a known issue. He said, No, probably just a rare scenario.
I'll probably run stock for a while on the new phone to see if this recurs. Then I'll return to root and monitor.
Click to expand...
Click to collapse
Interesting. I don't feel like getting it replaced, because I have a dbrand skin on it that would not transfer.
JagXK8 said:
I've had this issue as well even with stock. Completely random. I've since flashed Pure Nexus since it's release and haven't had the issue anymore.
Click to expand...
Click to collapse
Hmm, how long have you been running on PureNexus? Sounds promising.
xocomaox said:
Interesting. I don't feel like getting it replaced, because I have a dbrand skin on it that would not transfer.
Hmm, how long have you been running on PureNexus? Sounds promising.
Click to expand...
Click to collapse
Since 1/6. I've actually had 3 problems with my pixel. Randomly not charging, volume buttons not working and times call quality. But so far haven't had any issues after flashing pure nexus. I did chat with support but wasn't a quick surrender.
Sent from my Pixel XL using Tapatalk
JagXK8 said:
Since 1/6. I've actually had 3 problems with my pixel. Randomly not charging, volume buttons not working and times call quality. But so far haven't had any issues after flashing pure nexus. I did chat with support but wasn't a quick surrender.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I am almost certain it is a software issue. I am going to flash Dirty Unicorns soon I think which will hopefully fix the problem.
xocomaox said:
I am almost certain it is a software issue. I am going to flash Dirty Unicorns soon I think which will hopefully fix the problem.
Click to expand...
Click to collapse
I am inclined to agree its a software issue, which is why I was surprised "Brian" offered a hardware replacement so quickly. I did very recently do a Factory Reset to address my "Double-Tap-To-Wake" issue (reset fixed it), so maybe this was his queue to not try yet another reset...
markp99 said:
I am inclined to agree its a software issue, which is why I was surprised "Brian" offered a hardware replacement so quickly. I did very recently do a Factory Reset to address my "Double-Tap-To-Wake" issue (reset fixed it), so maybe this was his queue to not try yet another reset...
Click to expand...
Click to collapse
I think Google offering to replace units quickly isn't terribly surprising.
The cost for them to replace a unit is very low. They are probably shipping out a refurb, and are only paying for shipping costs. The unit that will be returned is surely fixable with ease and can be re-deployed to another user. This is a super low cost way of providing what appears to be excellent customer service to the end-user. Apple and other companies have done this for years and have been very successful.
EDIT: I am now on DU so I will let this thread know if I have any more charging issues.
Woke up this morning to charge my phone, didn't start charging. Rebooted to fix. Made a call and the call quality was like I was in a poor reception area. Oh well still happens at random. Think I'm ready for a replacement.
Sent from my Pixel XL using Tapatalk
JagXK8 said:
Woke up this morning to charge my phone, didn't start charging. Rebooted to fix. Made a call and the call quality was like I was in a poor reception area. Oh well still happens at random. Think I'm ready for a replacement.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Well it happened to me last night on DU. I think I might be able to use this as a free replacement card down the road to get a refreshed unit. It's crazy that without touching the phone I can reboot it and it will work.
My replacement devices arrived last night - Pixel XL, 128GB, Black.
They are probably shipping out a refurb...
Click to expand...
Click to collapse
Especially with all the shipping delays, I fully expected this replacement would have been a refurb. By all appearances this replacement is new or at least a pristine refurb. Packaging and accessories were clearly new (that part is easy), but the phone's back, corners, edges and glass are all 100% flawless.
The phone appears to be playing well. Ran it on Daydream for 2:27 last night to watch a NextVR basketball game - no overheating, possibly sightly less drift than my old device.
Edit: My plan to hold-off rooting failed - I am unlocked & rooted, but kept the stock recovery vs TWRP (in anticipation of FlashFire).
Replacement Device received, unlocked & rooted. The issue returns after just one day! Reboot needed to re-charge. Blargh!
I should have used a little more discipline and not rooted right away - for science.
I am doubtful I'll revert to stock to test some more, but who knows.
Odd. Given that not everyone who is rooted has this issue perhaps sharing a list of mods/root apps and other apps that you installed on the new device could help to shed some light on where things to sour.
I seem to have had this issue ever since I rooted and installed ElementalX kernel. So it would appear that either I have a bad device, it's root, it's the elex kernel, or both root+kernel causes this.
I've modded emoji's but only once or twice, definitely had the issue on a fresh DU and PureNexus install with only root and kernel.
I am still questioning the charger, but not much because I also use the USB-a to USB-c cable connected to a cheap 1a chsrger at work with the same problem. So very unlikely it is the cable.
xocomaox said:
I seem to have had this issue ever since I rooted and installed ElementalX kernel. So it would appear that either I have a bad device, it's root, it's the elex kernel, or both root+kernel causes this.
I've modded emoji's but only once or twice, definitely had the issue on a fresh DU and PureNexus install with only root and kernel.
I am still questioning the charger, but not much because I also use the USB-a to USB-c cable connected to a cheap 1a chsrger at work with the same problem. So very unlikely it is the cable.
Click to expand...
Click to collapse
For me, still a most basic configuration:
- rooted (supersu 2.79-sr2)
- stock recovery
- stock kernel
- stock launcher
- no roms
At the moment, the only root-apps that possibly raise a flag as not fully stock. Nothing odd in this list as far as I can see:
- adaway (modified hosts file)
- titanium
- flashfire (not in use)
- rootchecker
- quickreboot
- tasker & autolocation
Next instance of no-charge, I'll try the brand new charger & cable from the replacement packaging.
markp99 said:
For me, still a most basic configuration:
- rooted (supersu 2.79-sr2)
- stock recovery
- stock kernel
- stock launcher
- no roms
At the moment, the only root-apps that possibly raise a flag as not fully stock. Nothing odd in this list as far as I can see:
- adaway (modified hosts file)
- titanium
- flashfire (not in use)
- rootchecker
- quickreboot
- tasker & autolocation
Next instance of no-charge, I'll try the brand new charger & cable from the replacement packaging.
Click to expand...
Click to collapse
It's strange if it is root causing it, why has nobody else mentioned anything? I'm glad you get it on the stock kernel, so that rules that out.
xocomaox said:
It's strange if it is root causing it, why has nobody else mentioned anything? I'm glad you get it on the stock kernel, so that rules that out.
Click to expand...
Click to collapse
I'm not rooted and my bootloader is not unlocked and still have this issue from time to time. So pretty sure it has nothing to do with root. Trying to use some usb-c headphones once (they didn't work) did trigger it immediately. It's likely going to be related to the usb-c port in some way, possibly a firmware issue?
I also randomly encounter this problem. I already returned 1 pixel xl that quit charging, completely stock, a reboot did not fix it. On my second device and still occurs occasionally seems like it takes a week or so and a reboot fixes, so not sure what the problem is. Still completely stock.
I've read 10 pages on this subforum, random talks about updates, LTE fixes, etc...I've yet to find a single thread giving an official fix for random rebooting? I get this at least 4x a day...regardless of charging or not, SD card installed or not, all the latest updates are installed. I can't be the only one and if so, why isn't this a Sticky issue at the beginning?
I and few have others have the unpleasant experience with rebooting. But it was a little relief that this issue is not just with my Note4.
Laughter is the key to happiness
I had this problem with the early 6.01 stock roms, but it eventually calmed down. Now I get a reboot about once a week. I just assumed the first couple 6.01 stock roms were buggy.
I suppose lots of hardware issues could also cause it.
I bought this phone used for $140, I don't know how long it's been running 6.01, but I'm guessing he knew it had this issue. It happens 3-4 a day for the past two weeks. It'll do it while at rest on or off a charger, middle of use, etc. Aren't they're apps that can log what's going on when it fails so this can be resolved, like acatlog? These phones aren't new anymore, it seems there should be a fix out by now...root and overclock while undervolt, remove bloatware from Sprint Normal Apps or whatever it's called, etc
m5james said:
I bought this phone used for $140, I don't know how long it's been running 6.01, but I'm guessing he knew it had this issue. It happens 3-4 a day for the past two weeks. It'll do it while at rest on or off a charger, middle of use, etc. Aren't they're apps that can log what's going on when it fails so this can be resolved, like acatlog? These phones aren't new anymore, it seems there should be a fix out by now...root and overclock while undervolt, remove bloatware from Sprint Normal Apps or whatever it's called, etc
Click to expand...
Click to collapse
So, what rom is the phone running?
Bone stock at the moment. I'm going to let a Sprint store give it a looking over, but I'm not hopeful as they're usually useless vs what I can find here myself. At minimum I'm going to root it and remove bloatware, but I haven't reviewed roms yet. Unless this thing stored it in memory, but I was doing a copy and paste last time it froze and rebooted, yet I was still able to paste when it came back on...safe to assume that means it's only a soft reboot?
m5james said:
Bone stock at the moment. I'm going to let a Sprint store give it a looking over, but I'm not hopeful as they're usually useless vs what I can find here myself. At minimum I'm going to root it and remove bloatware, but I haven't reviewed roms yet. Unless this thing stored it in memory, but I was doing a copy and paste last time it froze and rebooted, yet I was still able to paste when it came back on...safe to assume that means it's only a soft reboot?
Click to expand...
Click to collapse
What version of stock? If it's old, some of the early 6.01 roms were pretty buggy. The current stock rom is QC1, which just began to roll out this week. Make sure you are on the most current rom.
Last update I received was this week which turned out to only be a security patch.
So, you're on most recent rom. Only suggestion I have is full reset. If that doesn't do it you've got a hardware problem.
So I hope I don't jinx myself, but I think a new battery has solved my issue...with some extra steps Let me explain.
Bought the phone used, it'd reset about 3-4x a day...being charged, being used, whatever. It'd reboot anywhere from 80% down to 40%, no rhyme or reason. Sometimes it simply wouldn't allow me to turn it back on, the light would flash blue while dimming in and out, but wouldn't power up the screen. Plugging it back in and it'd be at 30%-45% no matter what. I downloaded an app called Battery Calibration from Meza (sp?) that had a little Android logo with a % on his chest. Resetting may or may not have completely solved the problem had it not soft reset when trying to get battery stats to refresh themselves. It's my understanding that if it reset, it rewrote a battery stat upon reboot, making this step useless.
I got two new batteries from eBay (http://www.ebay.com/itm/112344168032?_trksid=p2057872.m2749.l2649&ssPageName=STRK:MEBIDX:IT), I charged one in the phone and one on an external charger. Even after running with the new battery, it still reboot once and shutoff around 43% reported on the phone itself. Once plugged in and phone still off, it said it was at 15%. I swapped in the other new and charged battery, powered on the phone, plugged it in until it read 100%. I fired up the Battery Calibration app, unplugged the phone as directed and then to force the battery to drain faster, I let YouTube play uninterrupted for about 4hrs. NOT A SINGLE REBOOT!! For the first time with this phone, it actually stayed on and dipped below the 30%'s and gave me a warning when the battery was getting low (yellow icon) and getting critically low (red icon) before it finally powered itself off at 1%. The phone is now charged on the factory fast charger, this time playing Pandora with the screen off and uninterrupted as well...it's currently sitting at around 57% last I checked.
Once it's fully charged, I'll run it like any normal user (texting, music, etc) without being plugged in and if all works well, it won't reboot.
Hopefully this helps someone with the same issue and is a $8 fix since I bought two batteries.
poit said:
So, you're on most recent rom. Only suggestion I have is full reset. If that doesn't do it you've got a hardware problem.
Click to expand...
Click to collapse
I reset the phone the day I got it.
if your phone often reboot many times in a day, make sure that you don't use Ram kernel V6 or v7 for your Rom, V5 is only version that not make your phone randomly reboot. I try Ram kernel v6 and v7 in Note 7 port rom, note 5 port rom and stock either, and this kernel version always make my phone reboot many many times, unless i flashed v5 or stock kernel, the problem had gone.
I had this problem. I replaced the battery with an official Samsung battery I ordered from Sprint, and the problem went away. Simple as that. No reboots ever since.
Purchased a new battery from Amazon, Samsung OEM, problem solved. Put back old battery guess what it started again but only when battery reached 70% of the original charge. So it must be the battery memory problem.
Sent from my SM-N910P using Tapatalk
Four batteries later and this still happens. Can this be addressed via rooting and then undervolting? I remember phones of the past where people would overclock for speed and undervolt for battery life, but one way too high or too low and you'd either get random rebooting or freezing. This is so god damn annoying!!!!!!