hi everyone!
ok so last night I flashed franco kernel on my phone and I went to bed setting an alarm for 8. in the morning I woke up but not at 8, because my alarm didn't go off. why? because my phone was off. it got so unbelievably hot that you literally couldn't hold it for more than 3 seconds without seriously burning yourself. there's also the Google bumper case on it, that's how got it got. I have no idea how, or why it got so hot, but it did. the only thing I can think of is franco kernel, and how the vibrator frequency is set so high. but when I checked my battery graph app it showed no results from 3 to 8:40, or about 2 hours after I plugged my phone in and went to bed. by the time the phone finally turned on, the battery was at 40 percent, and I noticed that all my Wi-Fi access points got deleted, as well as my wallpapers on the launcher (the ones I set, not the built in ones). I didn't really think anything of this, until now when I went to use Google maps, and the location was off by a lot and there's a huge 5km wide blue circle around my location. I thought it was a maps problem and cleared data with no luck. I tried other location apps like transit with the exact same problem, so now I'm thinking... did the insane temperatures melt something? did it destroy my Wi-Fi location thing? why did it get so hot? like I've never had this problem before until I flashed franco kernel so I'm assuming it's a problem with that. anything I could do to fix my phone? thanks!
It's possible but I'm pretty sure the phone would shut off before damage happened (and that feature is in an area where the kernel can't touch).
This may or may not help but disable the Google Plus app.
For some reason it started glitching out and was continuously using 100% CPU even though I never used the app. Disabling it let my battery last more than an hour and stopped the heat issues.
Mine gets randomly hot.Try to restore a backup and see what happens. IF that doesn't work you might need to restore a factory Image. Can you use adb/fastboot?
mgear2 said:
It's possible but I'm pretty sure the phone would shut off before damage happened (and that feature is in an area where the kernel can't touch).
This may or may not help but disable the Google Plus app.
For some reason it started glitching out and was continuously using 100% CPU even though I never used the app. Disabling it let my battery last more than an hour and stopped the heat issues.
Click to expand...
Click to collapse
if it did then why was it blazing hot in the morning after 5 hours when it turned off? :/ and i was thinking of that, google plus shows up in the battery graph even though i never used it, but i use auto backup so wouldnt it stop working if i disable it?
habitformer said:
Mine gets randomly hot.Try to restore a backup and see what happens. IF that doesn't work you might need to restore a factory Image. Can you use adb/fastboot?
Click to expand...
Click to collapse
i dont have any backups and i restored a factory image, i restored the system, boot, radio, and cache, but its still broken... could it be possible that something bad happened to the hardware? because its looking more and more likely :/
NuckFuggets said:
i dont have any backups and i restored a factory image, i restored the system, boot, radio, and cache, but its still broken... could it be possible that something bad happened to the hardware? because its looking more and more likely :/
Click to expand...
Click to collapse
If you did all of that then it is possible there was some damage to parts inside the phone and RMA would be necessary. Although I imagine Google or LG would wonder how this happened
mistahseller said:
If you did all of that then it is possible there was some damage to parts inside the phone and RMA would be necessary. Although I imagine Google or LG would wonder how this happened
Click to expand...
Click to collapse
damn this will be my second rma.. but I'll just say that I plugged my phone in before i went to bed, set an alarm, and woke up to a blazing hot phone. that's not too far away from the truth
NuckFuggets said:
damn this will be my second rma.. but I'll just say that I plugged my phone in before i went to bed, set an alarm, and woke up to a blazing hot phone. that's not too far away from the truth
Click to expand...
Click to collapse
Do you use the original cable and charger to charge? Have you checked BetterBatteryStatts to see if an app is active when its not supposed to, i personaly think is unusal app activity that keeps the phone busy. Just flash the stock rom in fastboot and see if it improves or happens again.
gee2012 said:
Do you use the original cable and charger to charge? Have you checked BetterBatteryStatts to see if an app is active when its not supposed to, i personaly think is unusal app activity that keeps the phone busy. Just flash the stock rom in fastboot and see if it improves or happens again.
Click to expand...
Click to collapse
yeah I did, but no I haven't, it would be pointless because the phone turned off so the app wouldn't be to say what app went crazy. but yeah I flashed stock system and boot image with no luck, although the phone didn't overheat this morning lol
NuckFuggets said:
yeah I did, but no I haven't, it would be pointless because the phone turned off so the app wouldn't be to say what app went crazy. but yeah I flashed stock system and boot image with no luck, although the phone didn't overheat this morning lol
Click to expand...
Click to collapse
If it we`re me i`d factory reset and after that reflash the stock rom, there is an app/widget or setting that is borking you device.
gee2012 said:
If it we`re me i`d factory reset and after that reflash the stock rom, there is an app/widget or setting that is borking you device.
Click to expand...
Click to collapse
I was thinking of doing a reset, but I don't think it will work, I wiped dalvik and cache a number of times, and nothing worked. like nothing location related works anymore, so i don't think that a reset will do anything :/
NuckFuggets said:
I was thinking of doing a reset, but I don't think it will work, I wiped dalvik and cache a number of times, and nothing worked. like nothing location related works anymore, so i don't think that a reset will do anything :/
Click to expand...
Click to collapse
What went wrong when flashing the stock rom, i hope not a flash failure for remote device (or somethig like that)! Cause that would mean the internal memory got corrupted and is no longer available, repair or RMA.
gee2012 said:
What went wrong when flashing the stock rom, i hope not a flash failure for remote device (or somethig like that)!
Click to expand...
Click to collapse
I don't think anything went wrong with flashing the rom, I think that a component in the phone is just messed up cuz anything I did didn't help with the location thing :/
NuckFuggets said:
I don't think anything went wrong with flashing the rom, I think that a component in the phone is just messed up cuz anything I did didn't help with the location thing :/
Click to expand...
Click to collapse
That does have no effect on flashing a stock rom, look here for how to flash a stock rom (real easy) http://forum.xda-developers.com/showthread.php?t=2513701.
gee2012 said:
That does have no effect on flashing a stock rom, look here for how to flash a stock rom (real easy) http://forum.xda-developers.com/showthread.php?t=2513701.
Click to expand...
Click to collapse
I did all that though, but minus the factory reset. still nothing :/
NuckFuggets said:
I did all that though, but minus the factory reset. still nothing :/
Click to expand...
Click to collapse
Then you have to send it in for repair. Maybe its hardware related.
Leaving your phone plugged in the power outlet overnight might be the cause, and I don't know how well franco kernel is optimized for such scenarios too. The auto shutdown prevented further damage to your phone.
ej8989 said:
Leaving your phone plugged in the power outlet overnight might be the cause, and I don't know how well franco kernel is optimized for such scenarios too. The auto shutdown prevented further damage to your phone.
Click to expand...
Click to collapse
I always do that, and never had a problem before :/ so Idk what happened
gee2012 said:
Then you have to send it in for repair. Maybe its hardware related.
Click to expand...
Click to collapse
yeah I guess. I'll call Google today and see what happens
If the phone shut down in the middle of the night and was still blazing hot in the morning even though the phone was off then that points at a charging issue that has overheated the battery. No custom kernel should be able to override the charging circuitry so I'd definitely say it's a hardware fault.
The overheated battery has probably damaged some of the antennae in your phone.
If I were you I would flash full stock and RMA your phone.
Sent from my Nexus 5 using xda app-developers app
I've read that overheating can damage battery or hardware..So Google will know better what's wrong with your phone.
Alex240188 said:
If the phone shut down in the middle of the night and was still blazing hot in the morning even though the phone was off then that points at a charging issue that has overheated the battery. No custom kernel should be able to override the charging circuitry so I'd definitely say it's a hardware fault.
The overheated battery has probably damaged some of the antennae in your phone.
If I were you I would flash full stock and RMA your phone.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I guess so. but then how come this all happened the night I flashed franco kernel? I've always used the same charger with no problems, it's only that night that everything went wrong.
I guess I'll have to rma it then, since this will be my second time I should be pretty good at it haha
Related
Hi all
Sometimes, my Atrix 2 will just freeze when the screen is off, and obviously won't come back on until the battery is pulled and reinserted. (draining it at the same time). It seems to have happened the most when airplane mode was turned on.
I'm afraid all this battery pulling will make the cover loose.
Does it happen with anyone of you?
thanks
EDIT: I'm on 2.3.6 stock, non root.
thenext1 said:
Hi all
Sometimes, my Atrix 2 will just freeze when the screen is off, and obviously won't come back on until the battery is pulled and reinserted. (draining it at the same time). It seems to have happened the most when airplane mode was turned on.
I'm afraid all this battery pulling will make the cover loose.
Does it happen with anyone of you?
thanks
EDIT: I'm on 2.3.6 stock, non root.
Click to expand...
Click to collapse
I have never experienced such a problem... So it just freezes while it sleeping? I have one idea but it's kind of stupid, there is an option under display, that says lock in pocket. Try unchecking that, I've had other people tell me that their phone freezes up afterwards...
You might have to do a warranty exchange.
Sent from my MB865 using xda premium
tmease1 said:
You might have to do a warranty exchange.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
I've written "drain" but it's not much of a drain - from 100 to 60% in a whole night. A true drain would be with the phone going from full to empty in a couple hours and getting very hot in the process.
I think the phone locks up for some reason during sleep and the cpu never goes into low power mode. As far as I can remember, this has happened only when it was bedtime, with the phone already put in airplane mode, and never in the long standby hours of the day while I work.
I hope this has something to do with software, and not hardware.
(A warranty replacement is out of question, as I'm not from the US...)
I'll try posting in the motorola forum, too.
100-60 overnight is a bit on the high side for drain if you are not using the phone. I would do a warranty swap.
thenext1 said:
I've written "drain" but it's not much of a drain - from 100 to 60% in a whole night. A true drain would be with the phone going from full to empty in a couple hours and getting very hot in the process.
I think the phone locks up for some reason during sleep and the cpu never goes into low power mode. As far as I can remember, this has happened only when it was bedtime, with the phone already put in airplane mode, and never in the long standby hours of the day while I work.
I hope this has something to do with software, and not hardware.
(A warranty replacement is out of question, as I'm not from the US...)
I'll try posting in the motorola forum, too.
Click to expand...
Click to collapse
It's probably something to do with the CPU govener. Try rooting, install bootstrap, then flashing the deodexed version of 2.3.6 found here. Just be sure to flash as a backup by placing it in \sdcard\clockworkmod\backup\. Select restore in clockwork and it should be there.
See if that gets rid of the problem You don't mid rooting right
Yes I mind rooting! Sorry!
I was just seeking for your experience, to know if you did by chance notice this behaviour/glitch... you keep telling me to do an exchange but it's obvious it's not an option for me, as you can see from the flag under my user name. Otherwise I would have got me a new atrix already. (Because of other minor annoyances)
I once had an acer liquid that started getting nuclear-fusion-hot and discharged in 2 hours each time, without the software taking a hit. Now that was hardware related.
As to my atrix2, I am sure it's not hardware related, because it happens only sometimes and in certain circumstances. One time, I turned it off and back on 5 secs after and it was already frozen. No way, we're not talking of hardware fault here.
Thats major drain overnight! I leave my phone on overnight and generally get about 1% drain per hour.
Sent from my MB865 using XDA App
WTF, either I can't speak my mind, or you don't read my posts!
It's not that I get a 40% drain every night. In fact I got it only once, last night, when I decided to leave the phone in deep coma after I found it unresponsive after just a few minutes it was turned off and in airplane mode (the time of brushing teeth and coming back to bed, FYI). In that circumstance I got the 40% drain, but otherwise i get a normal 5% drain like yours.
This thread is not on the battery drain, but on finding what causes the phone freezing while screen-off.
Thank you.
I have never heard of this happening on the A2.
When the phone freezes up, does it get hot at all? It's possible that your problem is hardware-related, but the only way to be sure of that is to make sure that it's not software-related...
It may possibly be one of the apps that you're using. If you're OK with it, then I highly recommend to begin with a hard reset. I write down all of the apps that I know I will need and then I reinstall them after the reset, then if I realize I need to use an app I don't have I install it.
Another thing to try is flashing the fxz. This will clear every single bit of data on your phone and reinstall stock 2.3.4. Then you can update to 2.3.6 and gradually regain your (necessary) apps as with the hard reset.
Sounds kinda like these reported bugs below:
http://forum.xda-developers.com/showpost.php?p=21817704&postcount=36
and
http://forum.xda-developers.com/showpost.php?p=21819590&postcount=37
thenext1 said:
WTF, either I can't speak my mind, or you don't read my posts!
Click to expand...
Click to collapse
You must not be able to communicate your thoughts very well then cause the post I responded to didn't make any mention of the fact it only happened once. And your first post said it happens "sometimes", meaning more than once. Sorry guy, i'm not a mind reader.
thenext1 said:
I've written "drain" but it's not much of a drain - from 100 to 60% in a whole night.
Click to expand...
Click to collapse
thenext1 said:
This thread is not on the battery drain, but on finding what causes the phone freezing while screen-off.
Click to expand...
Click to collapse
I know what the thread is about, but you chose to share your experience with the battery draining issue not only in the first post but also in the once I quoted above which led me to believe this thread was about that as well so that's what I chose to respond to.
Thanks
kirkgbr said:
Sounds kinda like these reported bugs below:
http://forum.xda-developers.com/showpost.php?p=21817704&postcount=36
and
http://forum.xda-developers.com/showpost.php?p=21819590&postcount=37
Click to expand...
Click to collapse
Yeah, sounds like that. What did you do to overcome it?
Do you use airplane mode at all?
916x10 said:
You must not be able to communicate your thoughts very well then cause the post I responded to didn't make any mention of the fact it only happened once. And your first post said it happens "sometimes", meaning more than once. Sorry guy, i'm not a mind reader.
I know what the thread is about, but you chose to share your experience with the battery draining issue not only in the first post but also in the once I quoted above which led me to believe this thread was about that as well so that's what I chose to respond to.
Thanks
Click to expand...
Click to collapse
I think I made sufficiently clear that the draining was secondary to the freezing issue, and, in turn, that the freezing issue happened only sometimes... which, in my (surely flawed) understanding, is more often not the case than it is.
Anyways no problem man!
thenext1 said:
Yeah, sounds like that. What did you do to overcome it?
Do you use airplane mode at all?
Click to expand...
Click to collapse
Not sure what fixed it. I have done a couple things since then.
1.) Rooted <- not sure how this could fix a problem like this.
2.) Froze several apps with Titanium Backup. <- This one makes the most sense.
I never use airplane mode.
The other user (dk-v1) says that his softkey lights come on while the screen stays black.
I don't remember about the lights, probably one time they turned on, but don't remember right now.
About the black screen, I'm not sure what he means, but mine stays black and with backlight off.
From reading the OP...I would suspect that it could be an app that is trying to sync while in airplane mode. I would try troubleshooting (uninstalling one by one to see if the problem goes away) apps that sync, preferably the ones you installed. But if it still persists do a factory reset and start over. Good luck man!!!
my wife actually started having this problem with her inspire recently. I tracked it down to the no led app she was using. deleted it and everything has been fine since. so your issues could most definitely be app related.
thenext1 said:
I think I made sufficiently clear that the draining was secondary to the freezing issue, and, in turn, that the freezing issue happened only sometimes... which, in my (surely flawed) understanding, is more often not the case than it is.
Anyways no problem man!
Click to expand...
Click to collapse
I never said it was the primary issue......u said this thread wasnt about the draining issue, but since u brought it up in your op and subsequent posts its clear it was an issue so when somebody responds to one of the issues you're having, don't be a douchebag about it by saying "thats not what this thread is about". Trying to insult me by insenuating I don't read before I respond is no way to show appreciation for my attempt at helping you. It seemed you were under the impression that a 40% discharge overnight wasnt a major drain so I shared with you my experience thinking it would put yours into perspective.
But apparently explaining my thought process and posting your own quotes for you to see how/why I'd think what I thought isnt enough to knock you off your high horse so I'm over it, carry on. If you feel the need to respond any further you can pm me, no sense cluttering the thread any further.
Sent from my MB865 using XDA App
this morning (and maybe 2 other times before) my screen blacked out and refused to turn back on. i am not rooted. any ideas why this would happen? i ended up having to pull the battery twice and then it's been working fine since.
thanks
then that was probably it...if it continues, do a factory reset
xmc wildchild22 said:
then that was probably it...if it continues, do a factory reset
Click to expand...
Click to collapse
ok. i'll keep an eye on it. hopefully it wont happen again.
polarbearmc said:
this morning (and maybe 2 other times before) my screen blacked out and refused to turn back on. i am not rooted. any ideas why this would happen? i ended up having to pull the battery twice and then it's been working fine since.
thanks
Click to expand...
Click to collapse
What ROM are you using? I've had that happen to me twice now. The buttons light up, I can hear screen noises, but a black screen. I pull the battery and reboot, everything is fine. I'm using DS_MOD.1.55.531.3, rooted and S-OFF.
Fuzi0719 said:
What ROM are you using? I've had that happen to me twice now. The buttons light up, I can hear screen noises, but a black screen. I pull the battery and reboot, everything is fine. I'm using DS_MOD.1.55.531.3, rooted and S-OFF.
Click to expand...
Click to collapse
not rooted, just stock. but the way you described it is exactly what happens. buttons light up, things can happen (you can hear it) but totally black screen.
polarbearmc said:
not rooted, just stock. but the way you described it is exactly what happens. buttons light up, things can happen (you can hear it) but totally black screen.
Click to expand...
Click to collapse
Are you on the 1.55.531.3 Stock ROM? That's what I'm running, just rooted.
Fuzi0719 said:
Are you on the 1.55.531.3 Stock ROM? That's what I'm running, just rooted.
Click to expand...
Click to collapse
yep. i figured i'd wait as long as i can before i decide to root (really don't have any reason to... i've always rooted my devices, my G1 and G2... just don't really have a need to yet with this phone)
I'm running Rubix v5.3 ICS Splashed, and the same exact thing happened to me tonight, weird...
Pulled the phone out of my pocket and screen was black. You could hear lock sounds and keys light up but the screen stayed black.
Pulled the battery and all is well again. This can't be a coincidence, can it?
This has happened to me periodically both on stock and on bulletproof, I never really gave it much thought though, because it was easily fixed by a reboot.
yellowjacket1981 said:
This has happened to me periodically both on stock and on bulletproof, I never really gave it much thought though, because it was easily fixed by a reboot.
Click to expand...
Click to collapse
i'll probably just end up forgetting about it soon enough, but it's just annoying that our phone should have an issue like that. if i had money to switch phones whenever i want i'd already have left it because of this issue, you know what i mean?
polarbearmc said:
i'll probably just end up forgetting about it soon enough, but it's just annoying that our phone should have an issue like that. if i had money to switch phones whenever i want i'd already have left it because of this issue, you know what i mean?
Click to expand...
Click to collapse
Happening twice in the six months I've had it is not a big enough issue for me to want to switch phones.
Fuzi0719 said:
Happening twice in the six months I've had it is not a big enough issue for me to want to switch phones.
Click to expand...
Click to collapse
It's been progressively getting worse, now I get just a black screen nothing coming up after multiple charges and battery pulls... praying it's not the screen and just a battery problem!
If it's fixed by a battery pull at first then it's most likely just a battery issue.
Indirect said:
If it's fixed by a battery pull at first then it's most likely just a battery issue.
Click to expand...
Click to collapse
No luck after battery pull, you think it's screen then or flex cable? The screen worked like 8 hours ago with minor black-outs one or twice a day to more frequently and random reboots like 6-8 just today!
Flex cable could cause flickering. You're really quite SOL with it then.
Sent from my Nexus S 4G using xda premium
Indirect said:
Flex cable could cause flickering. You're really quite SOL with it then.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Would you suggest I get it repaired or something similar?
Yeah, you may need to get it repaired. :|
My N5 shuts down at random times when i record a video or take a picture, both in non HDR and HDR, with or without flash.
It's annoying because most of the times the recent pictures and the whole video doesnt get saved..
Does it happen to anyone else? I've rooted, but I've also restored it back to factory and done the whole process again in case i did something wrong the first time. I also tried franco kernel in case there was something wrong with the kernel.. Anyone? Kinda desperate.. its really annoying.
I didnt notice it happening after my very first root, without any additional software. Now im running stock + xposed.
maybe its the "exposed" interfering with something? have you tried without exposed?
simms22 said:
maybe its the "exposed" interfering with something? have you tried without exposed?
Click to expand...
Click to collapse
Yes, it also happened after i rooted for the first time, at that time i didnt have xposed. I just recently installed xposed, maybe 5 days ago.
Inkness said:
Yes, it also happened after i rooted for the first time, at that time i didnt have xposed. I just recently installed xposed, maybe 5 days ago.
Click to expand...
Click to collapse
hows your battery life in general? i ask because it may be that you need to recalibrate your battery. also, how much storage do you have left?
simms22 said:
hows your battery life in general? i ask because it may be that you need to recalibrate your battery. also, how much storage do you have left?
Click to expand...
Click to collapse
My battery is great! 6hr SoT with franco. And space is also good, maybe 16GB free, give or take. Just ask more questions if you need to! I don't mind!
try this. go to the phones main settings, apps, all, camera.. now press the clear data button then reboot. see if it will still shut down after.
did this happen before installing the latest franco kernel?
simms22 said:
try this. go to the phones main settings, apps, all, camera.. now press the clear data button then reboot. see if it will still shut down after.
Click to expand...
Click to collapse
I already tried that and it didn't work wiped camera and even force stopped it etc, with restart.
mistahseller said:
did this happen before installing the latest franco kernel?
Click to expand...
Click to collapse
Yes, it did. Even on stock kernel, after root though. I'm not sure if it happened before root, but i tried to bring it back to factory image and it still had the same problem..
Hello, did you resolve this problem? I'm having the same after changing screen & battery :/
RMA matey, on my Sensation when that happened it just meant the phone battery couldn't supply the voltage so I ended up buying another battery. As you can't replace the battery, the only option you have left is RMA. Before you RMA, flash factory images and see if the same happens. If it does then it's a battery issue.
topgeardave said:
it just meant the phone battery couldn't supply the voltage so I ended up buying another battery. As you can't replace the battery, the only option you have left is RMA.
Click to expand...
Click to collapse
That's what I thought.
I installed a new battery following screen replacement because the original one was glued like crazy to the old screen. So RMA isn't an option but I can try to find a better quality battery, I know how to install it.
Tito1337 said:
That's what I thought.
I installed a new battery following screen replacement because the original one was glued like crazy to the old screen. So RMA isn't an option but I can try to find a better quality battery, I know how to install it.
Click to expand...
Click to collapse
You'll need the part "*Google Nexus 5 BL-T9 2300mAh EAC62078701" Try and find an original LG one
topgeardave said:
Try and find an original LG one
Click to expand...
Click to collapse
Yeah they all say it's "Original" or "Genuine" but I'm pretty sure the one I got is physically smaller than the true original one...
Right now I have charged it and the camera + flash works. I will update if it fails again (most likely on low battery)
Tito1337 said:
Yeah they all say it's "Original" or "Genuine" but I'm pretty sure the one I got is physically smaller than the true original one...
Right now I have charged it and the camera + flash works. I will update if it fails again (most likely on low battery)
Click to expand...
Click to collapse
Yeah, once it goes below 25% it'll start to go screwy. Eventually it'll get to a point where even at 80% the battery won't be able to supply the voltage for the camera. The problem with aftermarket batteries is that cell degradation is much worse than oem batteries as the quality is not the same. In an ideal scenario, you're best off buying a nexus 5 that someone is selling for parts and use that battery.
Hey guys I've had my N5 for almost a year now but it seems to have gone kaput on me recently...
On Monday I was on a skype call, (just audio) when my phone suddenly restarted, I didn't pay much mind to it as that happened before and it would usually just cut back on, but this time, it restarted, and restarted and just didn't stop. That lead me to think its the power button being stuck so i checked it out and made sure its not being depressed and well yeah it wasn't. And soon after that the phones screen was sometimes on during the reboots and sometimes off. I knew it was rebooting because the N5 vibrates a bit when Google pops up on the loading screen in a certain way, but yeah now the screen doesn't light up at all, there's still vibrations and sounds like when I call or when I say Okay Google a few times, the LED will even light up during a call. I know the phone is "on and working" in the background but the screen doesn't light up and as such I can't touch it, any ideas and or advice friends?
bump de bump?
Possibly your backlight burnt out? Water damage?
if you are running cyanogenmod, you could be experiencing sod "sleep of death". thats when you know the phone is on and working, but the screen doesnt turn on. ive been reading lots of complaints about cm and the sod.
TheROMGuy said:
Possibly your backlight burnt out? Water damage?
Click to expand...
Click to collapse
As the phone kept rebooting it went from seeing everything, to seeing nothing but the back light to dark, so maybe? It was just by me on my desk too so I was doubtful about the water damage but I put it in the sealed rice bag for about 24 hours just in case but still no luck.
I actually am running cyanogenmod and whenever I do have a problem I always feel that its related to CM as the phone doesn't have any physical damage...maybe I should look into that, any other ideas friends?
P.S I am using the ElementalX Kernel and UNFORTUNATELY I turned on the FAST CHARGE USB option and that makes the phone play funny with the computer, if you guys have any advice as to how I could turn off that option please do let me know
http://forum.xda-developers.com/goo...l-06-03-14-one-click-factory-restore-t2513937
I used this tool to try and remove anything that could be bothering my phone, software wise, and I'm not sure if it wiped away Kernels and Roms but thought you guys should know, my computer now recognizes the phone and I can see folders and such, which are now empty.
dynamo147 said:
http://forum.xda-developers.com/goo...l-06-03-14-one-click-factory-restore-t2513937
I used this tool to try and remove anything that could be bothering my phone, software wise, and I'm not sure if it wiped away Kernels and Roms but thought you guys should know, my computer now recognizes the phone and I can see folders and such, which are now empty.
Click to expand...
Click to collapse
all it does is completely wipe your phone and install an older android version. flashing the factory img will do the same, except youll get the newest android version. don't use these tools, doing things the right way will be more beneficial to you. anyways, since cm is having issues, try a different rom, or just go stock.
simms22 said:
all it does is completely wipe your phone and install an older android version. flashing the factory img will do the same, except youll get the newest android version. don't use these tools, doing things the right way will be more beneficial to you. anyways, since cm is having issues, try a different rom, or just go stock.
Click to expand...
Click to collapse
Thats my problem though my screen is still untouchable or see able and it makes it hard to flash stuff since I can't properly use TWRP, and having the fast charge hack on my computer doesnt really sense im in USB Debug but I guesssss its off now though, but still no screen loving
dynamo147 said:
Thats my problem though my screen is still untouchable or see able and it makes it hard to flash stuff since I can't properly use TWRP, and having the fast charge hack on my computer doesnt really sense im in USB Debug but I guesssss its off now though, but still no screen loving
Click to expand...
Click to collapse
if still no screen, its probably physically damaged(hit or factory damage). is an exchange possible?
simms22 said:
if still no screen, its probably physically damaged(hit or factory damage). is an exchange possible?
Click to expand...
Click to collapse
Well i got mine through the Play Store and I did think about an RMA, I know there was that free screen replacement thing going on but the customer rep sounded like he had no idea what I was talking about. and I'm thinking its a flex cable issue as my phone hasn't incurred any damage from drops or bumps or anything since i make it a point to be stationary while using phone, but....where the sim card tray is, that "bridge" or thin piece on the bottom side toward the phone has split as a result of my bad sim card ejecting, but that was when i first obtained the phone, also there is another split, inside the phone there is a canopy above the charging port that is split but i still know that occurred long before this, and its not even an electrical piece along with the sim card bridge thing.
BUTTT yeah im afraid if I RMA they will use that as an excuse to charge me $400, even though I know it's not playing any sort of factor in my screen acting up....Is there a policy on that?
dynamo147 said:
Well i got mine through the Play Store and I did think about an RMA, I know there was that free screen replacement thing going on but the customer rep sounded like he had no idea what I was talking about. and I'm thinking its a flex cable issue as my phone hasn't incurred any damage from drops or bumps or anything since i make it a point to be stationary while using phone, but....where the sim card tray is, that "bridge" or thin piece on the bottom side toward the phone has split as a result of my bad sim card ejecting, but that was when i first obtained the phone, also there is another split, inside the phone there is a canopy above the charging port that is split but i still know that occurred long before this, and its not even an electrical piece along with the sim card bridge thing.
BUTTT yeah im afraid if I RMA they will use that as an excuse to charge me $400, even though I know it's not playing any sort of factor in my screen acting up....Is there a policy on that?
Click to expand...
Click to collapse
ive rma'ed before, google is really good about it. i sent my nexus 7 back with a custom recovery, rom, kernel.. and the thing going on with google and exchanging the n5 once without question, isnt about the screen, its for anything.
simms22 said:
ive rma'ed before, google is really good about it. i sent my nexus 7 back with a custom recovery, rom, kernel.. and the thing going on with google and exchanging the n5 once without question, isnt about the screen, its for anything.
Click to expand...
Click to collapse
I suppose I might as well shoot for it? Is there a way to decline paying for the device if they decide that I should pay?
dynamo147 said:
I suppose I might as well shoot for it? Is there a way to decline paying for the device if they decide that I should pay?
Click to expand...
Click to collapse
send back the rma? honestly, i dont know. i dont know anyone thats ever had to pay. unless its obvious that you did something, youll be fine.
So when you hold down the power button and the vol - for about 15 seconds the bootloader screen doesn't show up? If so, yeah try to RMA.
I will chat it up with one of the customer service peeps and see what they think then, and maybe even hopefully one will know about the replace anything deal
anactoraaron said:
So when you hold down the power button and the vol - for about 15 seconds the bootloader screen doesn't show up? If so, yeah try to RMA.
Click to expand...
Click to collapse
and yup Ik its in bootloader mode though because the computer beeps and tries installing drivers and what not and also because it does that single vibrate, but yeah the screen is still dark so I can't see my selections, I believe I can still actually make a selection though, just unable to see them
dynamo147 said:
and yup Ik its in bootloader mode though because the computer beeps and tries installing drivers and what not and also because it does that single vibrate, but yeah the screen is still dark so I can't see my selections, I believe I can still actually make a selection though, just unable to see them
Click to expand...
Click to collapse
Check to make sure you have the newest drivers (there's a sticky in the general section with all the useful info). If you bought it from the play store see if you can get an RMA - Google seems to have a good rep with this. It wouldn't hurt to flash a factory image to erase everything either before sending it off (privacy and whatnot). If you have the newest TWRP (2.8.0.1) if you boot into recovery and you should be able to access the internal storage without having to select anything (in case there's anything there not backed up). Boot to recovery is volume down twice and power I think.
anactoraaron said:
Check to make sure you have the newest drivers (there's a sticky in the general section with all the useful info). If you bought it from the play store see if you can get an RMA - Google seems to have a good rep with this. It wouldn't hurt to flash a factory image to erase everything either before sending it off (privacy and whatnot). If you have the newest TWRP (2.8.0.1) if you boot into recovery and you should be able to access the internal storage without having to select anything (in case there's anything there not backed up). Boot to recovery is volume down twice and power I think.
Click to expand...
Click to collapse
Well now that I used that tool I'm not sure if my recovery is still TWRP or if it's stock, it flashed a stock factory image I'm told, but that doesn't remove the Kernel and Recovery too does it? I wanna get it as stock as possible before I sent it out. At this point I believe it has a factory image but I can't say for sure about anything else
dynamo147 said:
Well now that I used that tool I'm not sure if my recovery is still TWRP or if it's stock, it flashed a stock factory image I'm told, but that doesn't remove the Kernel and Recovery too does it? I wanna get it as stock as possible before I sent it out. At this point I believe it has a factory image but I can't say for sure about anything else
Click to expand...
Click to collapse
See here http://forum.xda-developers.com/showthread.php?t=2513701.
My Pixel 3 randomly restarts and gets stuck in long bootloops. The frequency is completely random, ranging from three times a day (rarely) to once a week or two (more common). There is no trigger, sometimes I have it in my hand, doing stuff, and it does that, sometimes it does it when it's sleeping.
The bootloop is always the same.
I see the bootloader message, then th Google logo, and the phone restars after about one second. I never counted to loops but sometimes it must be tens of them. There doesn't seem to be a way to stop them, or at least I am not awaer of any key combinations.
I presume the phone eventually boots into safe mode or something.
I've had it for several months, bought it used in good condition off Ebay, and other than this I never noticed anything off.
This is extremely frustrating and I have no idea what to do.
Does anyone have any idea?
I really hope it never been inside water. Try updating your OS, or change to Custom ROM. If it still occurs, then that's a big problem.
It's most probably an app that's causing this, try disabling/uninstalling some apps that you don't need.
Booting into safe mode is also an option, that way you can make sure if an app is actually causing this.
I factory reset and later on completely reflashed the phone at one point in not too distant past and it didn't help one bit.
It's also completely untroubleshootable given how randomly the problem occurs, which also makes me sceptical about an app doing this
I'm inclined to think it could be a hardware problem.
WalrusInAnus said:
I factory reset and later on completely reflashed the phone at one point in not too distant past and it didn't help one bit.
It's also completely untroubleshootable given how randomly the problem occurs, which also makes me sceptical about an app doing this
I'm inclined to think it could be a hardware problem.
Click to expand...
Click to collapse
It's highly unlikely for it to be hardware problem, unless you have water/dust/humid damage.
Or maybe your phone heats really fast and therefore some pin inside the motherboard gets shortened due to the heat. But what are the chances of this happening?
But just to be sure, what happens when you connect your device to a charger with output more than 2 amp?
Did you modify your device in anyway whatsoever? Anything the previous owner noted about the device?
I didn't nodify it at all.
This is the charger I use https://www.alzashop.com/vention-dual-quick-30-usb-a-wall-charger-18w-18w-white-d6323711.htm
WalrusInAnus said:
I didn't nodify it at all.
This is the charger I use https://www.alzashop.com/vention-dual-quick-30-usb-a-wall-charger-18w-18w-white-d6323711.htm
Click to expand...
Click to collapse
Yeah, just flash some different ROM on your device and we're good.
Make sure you backup everything through TWRP and that you're flashing your device specific ROM.
As a test you mean? I am used to the stock ROM and last time I checked, there was no stable Android 11 (I think) ROM I would use.
WalrusInAnus said:
As a test you mean? I am used to the stock ROM and last time I checked, there was no stable Android 11 (I think) ROM I would use.
Click to expand...
Click to collapse
Was the last time you checked a year ago?? A11 has been out for a good while now. Here: Stock A11 ROM (Blueline).
And not as a test, no, flash it and keep using it. You can also flash custom ROM if that's your thing.
XDHx86 said:
Was the last time you checked a year ago?? A11 has been out for a good while now. Here: Stock A11 ROM (Blueline).
And not as a test, no, flash it and keep using it. You can also flash custom ROM if that's your thing.
Click to expand...
Click to collapse
But I said I flashed the stock ROM before with no luck. You're suggesting I do the same again. That makes very little sense.
What about the Google camera and LOS btw?