I've had this for a couple days now, and I've noticed that when I turned on the display after it's been off for a while there are a bunch of vertical lines corrupting the picture. This has happened twice and they go away after using it for a while. Anyone else having this problem? I'm thinking I'll need to get it replaced, but with no stock available that'll be a problem.
I concur that I have the same issue. I usually notice this first thing in the morning when I turn it on for the first time after its overnight charge.
At first I thought it was the live wallpaper but no, it does instantly disappear if you launch the browser though. Otherwise it usually goes off after 20-30 seconds of use.
Either way, it certainly seems to come into effect after a prolonged screen off/standby period.
Of course since I posted this it hasn't happened again, hopefully it's just part of the break in process.
I suspect it's a software problem since it goes away and doesn't occur when the tablet it switched off and then on as it only occurs after wakeup from standby.
I've also noticed if you wake it up and see the corruption lines, send it to standby then wait 2secs then waking it up again seem to make the lines disappear.
Anyway this has happened from day 1.
i also have this issue
I've raised a support ticket with ASUS regarding this in the hope of them fixing it via a software update if it is indeed software problem. So I suggest you guys do the same if you haven't so they realise it's not an isolated problem with a couple of transformers.
I doubt it's a software issue, but I'll try setting it to standby for a few seconds like you said the next time it happens.
ASUS support got back to me and asked me to try and do a factory reset, did it with no improvements.
They also said if it doesn't work, then I should send it to my local ASUS service centre. Since there are still stock shortages I'll put up with it for now and send it in for repairs/replacement in a month's time.
My Transformer has the same issues as everyone else; it's extremely laggy, apps crash, etc. But I also have this thing where every once in a while, if I click on something, my screen will go white with a line at the bottom and freeze. I have to restart the tablet to get it working again. I read through a lot of different threads and couldn't find anything. Is anyone else experiencing this?
I can't find any causes/solutions online. Any ideas?
Kimusubi said:
My Transformer has the same issues as everyone else; it's extremely laggy, apps crash, etc. But I also have this thing where every once in a while, if I click on something, my screen will go white with a line at the bottom and freeze. I have to restart the tablet to get it working again. I read through a lot of different threads and couldn't find anything. Is anyone else experiencing this?
Click to expand...
Click to collapse
I've had the same issue but haven't seen it in a couple days. I was told to cold boot it to solve the problem. After doing that, I haven't seen it again, but I haven't used it as much.
I am having the same issue. Started last night. Froze up first then a bit later went to white screen then rebooted. Today it froze up again...no white screen this time but could not access settings...the icon for settings was there but nothing else. Happen after reboot again...shut it down after that till now. Had been working fine. UPDATE is needed badly...I also have the Acer a700, that has been great so far...much better than this one.
Happened once to me too, i rebooted, and it has not happened since.
Sent from my ASUS Transformer Pad TF700T using xda premium
Haven't had the white screen return yet but I have had a recurring issue with freezing. Tablet was working last night when I put it down...this morning there was no internet connection. Went to settings to turn on wifi and it froze, just like before, only the settings logo and the word settings were visible. Received a message about the program not responding, my options were to close down or wait for program. When I got the white screen before it happened just as described above.
Here is the thing, installed the 9.4.5.26 20120720 firmware update earlier last night...I was hoping that was the fix for this issue but no such luck.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
I had a freezing issue only once.
I installed and used an app that ran in compatibility mode.
It started portrait and I think there was no landscape mode at all.
But I tried to turn the tab for that mode and that was that...
Crashed.
So maybe check for running apps that are not compatible ?
My unit had a burning smell come out of the speaker. Memory has been running consistently high 560 - 690 ram. Now I just got the "white screen of death".
Unit is going back for a replacement.
I have been having the same problem. The past couple of freezes occurred whil using google chrome. I have decided to send it back for a refund (thank you Amazon!)
Too bad, I had anticipated the arrival of this tablet for so long.
I returned my first one for tv snow but i did notice that you can wait it out 15seconds or so. Its almost like it is coming out of a deep sleep coma
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Decided to send mine back today (froze again)... who knows how long before I get a replacement...I hope it has no issues or it will go back again and I will get another a700... which has been working great. Sucks because I have to suck up the cost of the screen protector...and buy another.
~zealouz
Asus tf700
Acer a700
HTC Thunderbolt
Samsung Galaxy S3
Worst purchase ever!
I really like Andoid, I currently have a Galaxy S3 phone and I don't have any problems. I really wanted an Android tablet and with the higher resolution the Infinity seemed like the one to get. I have had it for a month and I think this purchase is one of the worst I ever made. With the keyboard and accessories I have around $1000 invested in a tablet that only works part time. It crashes at least once a day while doing different tasks. Just now it was just sitting there on the locked screen and the screen went to all white. Holding the power button didn't do any good and I had to use the reset button. I feel like I wasted my money and I don't know if I should avoid Asus products or if Android tablets suck, the problem might even be with Jelly Bean. I don't like Apple at all but I really wish I had bought an iPad.
this has happened to me three times in the last day, and each time while i tried to play an MP3 and read a Kobo book at the same time. (don't get me started on why a $500 tablet can't play music and display text AT THE SAME TIME. what the hell).
i'd start the track, load up kobo, and BOOM: white screen. i think i know why: all my music was in internal storage. for the hell of it, i moved all my tunes to the microSD card. and no more white screen, i can read and listen to tunes at the same time.
go figure.
AM Radio said:
this has happened to me three times in the last day, and each time while i tried to play an MP3 and read a Kobo book at the same time. (don't get me started on why a $500 tablet can't play music and display text AT THE SAME TIME. what the hell).
i'd start the track, load up kobo, and BOOM: white screen. i think i know why: all my music was in internal storage. for the hell of it, i moved all my tunes to the microSD card. and no more white screen, i can read and listen to tunes at the same time.
go figure.
Click to expand...
Click to collapse
I've been having this happen a lot. Essentially, I have two things happen:
1. In some app (Firefox, Redfin (we're house hunting), etc) and click something. Tablet freezes. Click something again, and it resets. The next thing you see is the black screen w/ Asus logo.
2. Same as above, but first you get a full white screen for ~10 seconds. THEN it reboots and you see the black screen w/ Asus logo.
It happens at least once an hour under heavy use of the tablet (lots of app switching, browsing the web, etc).
I have:
1. Cold booted.
2. Upgraded to JB.
3. After upgrading to JB, I reset cache and everything *multiple* times before installing all new apps.
Is this a known issue, or are the few people complaining about it just F'd?
I am seeing this too. Not sure what else to do with this issue?, Exchange? I want to believe this is software, but where does that leave me?
jordanmw said:
I am seeing this too. Not sure what else to do with this issue?, Exchange? I want to believe this is software, but where does that leave me?
Click to expand...
Click to collapse
I have this issue under Jelly Bean, but never had it happen under ICS. If you are in the same boat, an exchange will likely not help. Your best bet is either to put on a different firmware, or get a different unit all together (ie, not Asus).
Bandacoo said:
I feel like I wasted my money and I don't know if I should avoid Asus products or if Android tablets suck, the problem might even be with Jelly Bean. I don't like Apple at all but I really wish I had bought an iPad.
Click to expand...
Click to collapse
The problem is that Asus decided to use a cheap nand chip that has slow i/o speeds which causes the lag. It's not a problem with android. Have a look at a note 10.1 if you want to see a lag free tablet.
Still, I flashed a new rom, and its much improved. And no white screens so far with a few hours of use.
White screen is a known issue with JB, it's not hardware issue. We just have to wait for another update from Asus. They promised to release a new one soon to address, keyboard, wifi and camera issues, but did not mention about white screen issue. We just have to wait and see. If white screen issue is bothering you too much, just down grade back to .30.
buhohitr said:
White screen is a known issue with JB, it's not hardware issue. We just have to wait for another update from Asus. They promised to release a new one soon to address, keyboard, wifi and camera issues, but did not mention about white screen issue. We just have to wait and see. If white screen issue is bothering you too much, just down grade back to .30.
Click to expand...
Click to collapse
i'm getting this white screen with heavy use - sometimes a couple times a day. never had the problem with ICS. definitely a post-JB thing. it's gotta be a software issue not a hardware problem. a fix will come. in the meantime.....
doody.
I should start by saying I'm not that new to android, but I am by no means an expert and have not been able to figure out how to get out of a very confusing situation.
My tf700 is currently running 4.1.1 Jelly Bean and the newest firmware version 10.4.4.23. Before the firmwarm update, I had unlocked my device thinking that I would try out some of the newer roms based on many recomendations from the facebook Infinity group. I never got around to rooting and installing TWRP, and a few days later I updated to the current stock firmware version manualy (downloading zip from website, flashing from stock recovery). Everything worked great for the first 2 days, and I had compeltely forgoten about rooting/romming thinking that the risks far outway the reward as my device was already near perfect. This morning my infinity began to act funny. Touch responseiveness was awfull (about 1/3 times I pressed, it would react) and it would sporadically stop charging while connected to a power supply. Some time later, while I was watching a flash video my screen turned completely blue and I force restarted it by holding the power button. From then on, I could not turn on my infinity and I tried EVERYTHING (pushing the reset button with a pin, trying a cold boot, holding power for 30 sec etc.). When i tried any of these combinations, the device would start vibrating and the vibrations would not stop. Also, the screen remained black the whole time and nothing I did would even get me a faint glimmer of any sort of screen response.
Has anyone had this sort of issue? I do not think this is a firmware problem seing as it worked fine for 2 days with this firmware and I am at a complete dead end as to what to do. Because I am unlocked, I can not send in my infinity for repair as my warranty is gone. Any help with this issue would be greatly apreciated!
~ Rock
rock1324 said:
I should start by saying I'm not that new to android, but I am by no means an expert and have not been able to figure out how to get out of a very confusing situation.
My tf700 is currently running 4.1.1 Jelly Bean and the newest firmware version 10.4.4.23. Before the firmwarm update, I had unlocked my device thinking that I would try out some of the newer roms based on many recomendations from the facebook Infinity group. I never got around to rooting and installing TWRP, and a few days later I updated to the current stock firmware version manualy (downloading zip from website, flashing from stock recovery). Everything worked great for the first 2 days, and I had compeltely forgoten about rooting/romming thinking that the risks far outway the reward as my device was already near perfect. This morning my infinity began to act funny. Touch responseiveness was awfull (about 1/3 times I pressed, it would react) and it would sporadically stop charging while connected to a power supply. Some time later, while I was watching a flash video my screen turned completely blue and I force restarted it by holding the power button. From then on, I could not turn on my infinity and I tried EVERYTHING (pushing the reset button with a pin, trying a cold boot, holding power for 30 sec etc.). When i tried any of these combinations, the device would start vibrating and the vibrations would not stop. Also, the screen remained black the whole time and nothing I did would even get me a faint glimmer of any sort of screen response.
Has anyone had this sort of issue? I do not think this is a firmware problem seing as it worked fine for 2 days with this firmware and I am at a complete dead end as to what to do. Because I am unlocked, I can not send in my infinity for repair as my warranty is gone. Any help with this issue would be greatly apreciated!
~ Rock
Click to expand...
Click to collapse
Update:
I can now rarely get it to vibrate for even a second holding the power for a long long time. Screen does not come on at all. Looks completely dead.
By your description sounds like a dead or dying LCD.
Sadly RMAing to Asus may cost you out of pocket.
Where did you get the tablet and how long ago?
Thats OK said:
By your description sounds like a dead or dying LCD.
Sadly RMAing to Asus may cost you out of pocket.
Where did you get the tablet and how long ago?
Click to expand...
Click to collapse
I was hoping it wouldn't lead to something like this. I got my tablet from Amazon around the first week of september. I have treated it very well.
I'm not quite sure how it could have burned out, my brightness is usualy <50% and I have used the super IPS+ more less time than I can count
on one hand. If this is the case, Is it possible that a technical problem like this would still be repaired on warranty seeing as it has nothing to do
with the bootloader?
Also I'm not sure how this explain the constant vibrating that does not turn off untill the battery runs out. The way I see it is you could be right, the tablet is trying to tell me it's not going to work, or there is really some kind of software glitch.
Have you ever had LCD problems with a tablet? any idea how much this could cost?
rock1324 said:
Have you ever had LCD problems with a tablet? any idea how much this could cost?
Click to expand...
Click to collapse
I've not had any manufacturing problems with my tab.
I don't see anything you may have done that caused the screen to go bad.
Sounds odd yet a few folks have had their tablet just start working again after seeing similar dead LCD's.
The vibrate thing is weird...almost like a bootloop with no screen.
There's a chance Asus may co-operate if you contact them for an RMA.
It's worth a shot...not sure if Asus has any standard repair rate for this sort of thing.
Curious do you see the back-lights in a darkened room?
Thats OK said:
I've not had any manufacturing problems with my tab.
I don't see anything you may have done that caused the screen to go bad.
Sounds odd yet a few folks have had their tablet just start working again after seeing similar dead LCD's.
The vibrate thing is weird...almost like a bootloop with no screen.
There's a chance Asus may co-operate if you contact them for an RMA.
It's worth a shot...not sure if Asus has any standard repair rate for this sort of thing.
Curious do you see the back-lights in a darkened room?
Click to expand...
Click to collapse
Thanks for the advice, I have heard some terrifying stories of Asus customer support (never had a problem with them myself) and of devices just being completely lost in their care.
To answer your question, no the back lights are not visible at all. The only way I know the Infinity is somewhat alive is by the led coming on while charging and the somewhat random vibrating patterns that happen when trying to boot up.
First of all, I'm happy to be a part of the site now. I'm not new to Android in any way, but have only decided to join a forum because Motorola tech is no help at all, and I can't figure it out on my own.
So here's the story. When I plug my Maxx HD in at night, it functions perfectly, and seems normal. Normal temperature and charge rate. Let's say for example it was at 50% when I plugged it in just before I went to bed at midnight or so. But when I wake up in the morning, the phone is powered off and doesn't register as charging. I unplug it, and it won't power up regularly, so most of the time I have to soft reset just to get the screen on. When it boots up, it runs smoothly like nothing happened. The battery is usually 5% or 10% higher than it was when I plugged it in many hours ago, so it's safe to assume it locks up and shuts down fairly quickly after I fall asleep. I have yet to be able to recreate this problem while I am awake. I have tried disabling, reenabling, and uninstalling just about everything, and the problem doesn't seem to relate to anything in the software. The curious thing is that this problem does not occur regularly. Sometimes, it will happen 3 nights in a row. Other times, it won't happen for a week.
A side effect of this, it seems, is that when it does decide to hold a charge, it will run from 100% to 90% and hold there for an hour or so, no matter how lightly or heavily I use it. Then, out of the blue, it will drop to around 60% or 70%, and the rest of the day will drop at a regular rate.
I've been searching for a solution for this problem for weeks and haven't found a valid answer other than "use a Motorola charger" "get a new phone" the always relevant "Have you tried an FDR?", and the typical answers from a bored Motorola employee about whether I've turned the phone off and on again.
To reply to those answers, yes, I've used a regular Motorola charger, Verizon's most powerful and expensive speed charger, and even the cheapest charger I can find and it still shuts off and won't charge no matter the charger. I currently use the Verizon charger because it is the most convenient and fastest charging.
No, I can't return it because the RMHD was a trade. I don't have the receipt of any documentation of the purchase. I had an S3 that I disliked because, let's be honest, Touchwiz is intrusive and irritating at times, and I was too lazy to try and find a working rom for it. I cold traded some guy that lived near me for his RMHD, phone for phone. No chargers, no receipts. just straight up trade. His still had the plastic on the screen, and he claimed he changed his mind about it as soon as he took it out of the box and thought it was too thick, and wanted an S3.
As for the FDR, yes I've done that 4 or 5 times now with no change.
So my question is, is this a hardware problem or a problem with the battery sensor? I'm tempted to say that the battery sensor is defective and protects the phone from overheat by shutting it down even when it's at normal temperature and won't take any more charge. But if that was the case, why doesn't it happen every night? Any help is appreciated, and I'm prepared to hear someone say "suck it up until the S4 or the Motorola X is released". Thanks for your help, and if I need to root my precious HD to fix it, I'm prepared to do so.
Sounds like there is an issue with your phone man, If you have already done FDR n whatnot and it still behaves the same, then not sure what else you could do to rectify that. If you have insurance on it you could put in a claim, it would cost money, but not as much as getting another phone.
Id say at this point though, why not unlock, root, try other roms, whatever. If for some reason it clears up running something else, then great! If not then you haven't lost anything but the time spent doing it. Id go for the 4.1.2 roms If you do, since they will have everything functioning, 4.2 roms are nice but not everything works yet (camcorder, HDR photos, voice search/transcribing, GPS issues, etc.)
I agree on the moto employees being lazy, they have 3 solutions to everything, FDR, reboot, FDR a ton of times in a row, its kind of insulting when they do that even after you say you already did it. "Hey I got a problem, I FDR, cleared this, rebooted, etc" - me "Did you FDR, clear that, reboot, etc??? Mine runs fine, must be something you did!" - Moto guy
Either way, let us know how it goes, and good luck, hope your issue gets resolved.
hollovoid said:
Sounds like there is an issue with your phone man, If you have already done FDR n whatnot and it still behaves the same, then not sure what else you could do to rectify that. If you have insurance on it you could put in a claim, it would cost money, but not as much as getting another phone.
Id say at this point though, why not unlock, root, try other roms, whatever. If for some reason it clears up running something else, then great! If not then you haven't lost anything but the time spent doing it. Id go for the 4.1.2 roms If you do, since they will have everything functioning, 4.2 roms are nice but not everything works yet (camcorder, HDR photos, voice search/transcribing, GPS issues, etc.)
I agree on the moto employees being lazy, they have 3 solutions to everything, FDR, reboot, FDR a ton of times in a row, its kind of insulting when they do that even after you say you already did it. "Hey I got a problem, I FDR, cleared this, rebooted, etc" - me "Did you FDR, clear that, reboot, etc??? Mine runs fine, must be something you did!" - Moto guy
Either way, let us know how it goes, and good luck, hope your issue gets resolved.
Click to expand...
Click to collapse
To put it simply, if there's ANY way I can determine if it's a software issue, I'd like to try it. A phone this expensive really has no excuse to have a hardware issue. I've heard the SIM reader can sometimes cause system problems, so I'll try blowing in the slot like an old N64 cartridge and seeing if maybe it misreads while charging and shuts off because of a speck of dust, or something ridiculous like that..
greydelta38 said:
Would it be worth reflashing the stock Motoblur 4.1.2? I used to run CM10 on the old GNexus, I'd love to use that again on my HD, if it's available.
As for a new phone, if need be, my upgrade happens to be right after the GS4 is released on Verizon so I might as well get that and then not have to worry about F-ing up my primary phone. I'm a little wary of rooting whatever my primary device is, because I've bricked a Bionic with a stupid mistake I made when I was new to Android.
Click to expand...
Click to collapse
You could try reflashing the stock rom, and there is a couple CM10 unofficial builds floating around in the roms section. Of course there is always risk in doing anything, but they have a pretty good method for rooting/unlocking, so id say if you feel up to it, go for it.
hollovoid said:
You could try reflashing the stock rom, and there is a couple CM10 unofficial builds floating around in the roms section. Of course there is always risk in doing anything, but they have a pretty good method for rooting/unlocking, so id say if you feel up to it, go for it.
Click to expand...
Click to collapse
I changed that post after I found a little more info, btw.
I usually don't go for unofficial. The only 10.1 I could find was a 4.2 but call audio, camera, nfc, and wifi weren't working. I wish they had a timeframe on an official release. Moto phones never have enough support.
greydelta38 said:
I changed that post after I found a little more info, btw.
I usually don't go for unofficial. The only 10.1 I could find was a 4.2 but call audio, camera, nfc, and wifi weren't working. I wish they had a timeframe on an official release. Moto phones never have enough support.
Click to expand...
Click to collapse
At this point, all CM builds are unofficial. All 10.1 builds are 4.2, 10.0 is 4.1. We are only going to get official when a proper kernel is ready and we have full functionality. 10.0 should have most everything working though, as the official moto builds are on 4.1.2. It does suck, Imagine if moto had never developed that ridiculous bootloader of theirs, we would be in great shape! But it is getting better, just everybody is starting from scratch now that its unlocked, so the pace seems slow.
If you don't mind the camcorder not working, the AOKP and Xenon HD builds are pretty awesome for 4.2. Best way to try them out is to put TWRP on and backup your stock, then you can switch between roms very easily and see if anything improves. The other recoveries should work the same as well, but ive only had experience with TWRP on this phone, and it works very well.
greydelta38 said:
First of all, I'm happy to be a part of the site now. I'm not new to Android in any way, but have only decided to join a forum because Motorola tech is no help at all, and I can't figure it out on my own.
So here's the story. When I plug my Maxx HD in at night, it functions perfectly, and seems normal. Normal temperature and charge rate. Let's say for example it was at 50% when I plugged it in just before I went to bed at midnight or so. But when I wake up in the morning, the phone is powered off and doesn't register as charging. I unplug it, and it won't power up regularly, so most of the time I have to soft reset just to get the screen on. When it boots up, it runs smoothly like nothing happened. The battery is usually 5% or 10% higher than it was when I plugged it in many hours ago, so it's safe to assume it locks up and shuts down fairly quickly after I fall asleep. I have yet to be able to recreate this problem while I am awake. I have tried disabling, reenabling, and uninstalling just about everything, and the problem doesn't seem to relate to anything in the software. The curious thing is that this problem does not occur regularly. Sometimes, it will happen 3 nights in a row. Other times, it won't happen for a week.
A side effect of this, it seems, is that when it does decide to hold a charge, it will run from 100% to 90% and hold there for an hour or so, no matter how lightly or heavily I use it. Then, out of the blue, it will drop to around 60% or 70%, and the rest of the day will drop at a regular rate.
I've been searching for a solution for this problem for weeks and haven't found a valid answer other than "use a Motorola charger" "get a new phone" the always relevant "Have you tried an FDR?", and the typical answers from a bored Motorola employee about whether I've turned the phone off and on again.
To reply to those answers, yes, I've used a regular Motorola charger, Verizon's most powerful and expensive speed charger, and even the cheapest charger I can find and it still shuts off and won't charge no matter the charger. I currently use the Verizon charger because it is the most convenient and fastest charging.
No, I can't return it because the RMHD was a trade. I don't have the receipt of any documentation of the purchase. I had an S3 that I disliked because, let's be honest, Touchwiz is intrusive and irritating at times, and I was too lazy to try and find a working rom for it. I cold traded some guy that lived near me for his RMHD, phone for phone. No chargers, no receipts. just straight up trade. His still had the plastic on the screen, and he claimed he changed his mind about it as soon as he took it out of the box and thought it was too thick, and wanted an S3.
As for the FDR, yes I've done that 4 or 5 times now with no change.
So my question is, is this a hardware problem or a problem with the battery sensor? I'm tempted to say that the battery sensor is defective and protects the phone from overheat by shutting it down even when it's at normal temperature and won't take any more charge. But if that was the case, why doesn't it happen every night? Any help is appreciated, and I'm prepared to hear someone say "suck it up until the S4 or the Motorola X is released". Thanks for your help, and if I need to root my precious HD to fix it, I'm prepared to do so.
Click to expand...
Click to collapse
You could always ask Verizon and see if it's under warranty. These phones aren't a year old yet if I am correct. Rooting your device is not the best idea because it technically can void your warranty.
Keep calling. Email Motorola support. Contact your carriers Cs. Or just sell the thing on ebay.
Sent from my DROID RAZR MAXX HD
jfriend33 said:
You could always ask Verizon and see if it's under warranty. These phones aren't a year old yet if I am correct. Rooting your device is not the best idea because it technically can void your warranty.
Keep calling. Email Motorola support. Contact your carriers Cs. Or just sell the thing on ebay.
Sent from my DROID RAZR MAXX HD
Click to expand...
Click to collapse
As I said in my post, I don't have a warranty, and I don't particularly care about a warranty. Motorola CS is pretty awful, they're all bored and don't really give a crap about your problems, unlike the friendly and caring service I've gotten from Samsung before. I don't want to sell it, seeing as how the RMHD is arguably the best phone on the market for the time being.
UPDATE: I uninstalled a RAM booster called Memory Booster - RAM Optimizer a few days ago, and have yet to have a charging problem. I had the booster set to auto clean the system garbage when the screen was off. I'm making an educated guess here, but I'd be tempted to say that it was killing one of the Android processes that keeps the phone awake while charging, and it would bug out and crash.
Long story short, if you're having a problem with an HD shutting down overnight, UNINSTALL ANY APP KILLERS, TASKERS, OR RAM BOOSTERS.
Hope this works.
Okay, so I thought I was in the clear. I was wrong. It definitely is less frequent, but my RMHD still continues to totally die every night. I've determined that it's definitely NOT a hardware problem. I'm convinced that it may be overheating at night and Android shuts it down for safety, and somehow locks it up in the process. Last night, I went to sleep with 20% battery, and plugged in. This morning it was totally dead and would only respond to a soft reset, booting into recovery, where I prompted a reboot. It started fine, showing 44% battery.
What the hell is going on? I went so far as to reflash Motoblur, and I tried Eclipse 4.1.2 and still had the same problem. Is it maybe an app that is hostile? Someone has to know how to fix this huge annoyance.
Sent from my DROID RAZR HD using xda app-developers app
greydelta38 said:
Okay, so I thought I was in the clear. I was wrong. It definitely is less frequent, but my RMHD still continues to totally die every night. I've determined that it's definitely NOT a hardware problem. I'm convinced that it may be overheating at night and Android shuts it down for safety, and somehow locks it up in the process. Last night, I went to sleep with 20% battery, and plugged in. This morning it was totally dead and would only respond to a soft reset, booting into recovery, where I prompted a reboot. It started fine, showing 44% battery.
What the hell is going on? I went so far as to reflash Motoblur, and I tried Eclipse 4.1.2 and still had the same problem. Is it maybe an app that is hostile? Someone has to know how to fix this huge annoyance.
Sent from my DROID RAZR HD using xda app-developers app
Click to expand...
Click to collapse
Not hardware but it gets hot and shuts down? Sounds like hardware to me.
Sent from my DROID RAZR HD using Tapatalk 2
Yeah sounds like hardware.
Sent from my XT926 using xda app-developers app
scoobaspeaz said:
Not hardware but it gets hot and shuts down? Sounds like hardware to me.
Sent from my DROID RAZR HD using Tapatalk 2
Click to expand...
Click to collapse
It's not hardware. I reflashed stock 4.1 AGAIN, and have yet to have it screw up. It's been about a week and a half since. Motorola sent me a new charger just in case. I know you guys think it's hardware but for some reason I'm totally convinced that it was an app screwing with Android. I guess I'll find out sooner or later. Thanks for the feedback.
Sent from my Galaxy S4 using xda app-developers app