Related
I was lucky enough to receive a GT 10.1 from Google I/O, however when I do not use it for some amount of time, it behaves as if it shut down. Pressing the power button for about 10s will cause it to boot normally. The time needed for this to happen is the range of a few hours, I mainly notice it overnight. Has anyone else had this problem?
It's happened once on mine. There's a thread about it on the forum. I think most users are having to hard cycle the power by holding down the power button for about 10+ seconds. Hopefilly its another pre release oddity that gets solved with a software update.
I haven't experienced that in mine. Hopefully it somehow gets fixed.
Sent from my GT-P7510 using XDA Premium App
I think it has happened two or three times on mine. I did root it and froze some of the samsung apps with titanium backup. I restored them thinking that might help. At any rate, I'm hoping that the 3.1 update will fix these issues.
Mine isn' t rooted, so i don't think that's the issue.
tau_ said:
At any rate, I'm hoping that the 3.1 update will fix these issues.
Click to expand...
Click to collapse
There seems to be a laundry list of stuff I'm finding, this problem included. I hope that 3.1 update is indeed in "a few weeks" like they said in the keynote and doesnt turn into months. If the I/O GT-P7510 was a consumer facing product we'd all be reading stories about high return rates by now.
aygriffith said:
Mine isn' t rooted, so i don't think that's the issue.
There seems to be a laundry list of stuff I'm finding, this problem included. I hope that 3.1 update is indeed in "a few weeks" like they said in the keynote and doesnt turn into months. If the I/O GT-P7510 was a consumer facing product we'd all be reading stories about high return rates by now.
Click to expand...
Click to collapse
Yeah, this has happened to me many times. The "sleep" mode apparently turns the device off completely. Ugh.
aygriffith said:
Mine isn' t rooted, so i don't think that's the issue.
There seems to be a laundry list of stuff I'm finding, this problem included. I hope that 3.1 update is indeed in "a few weeks" like they said in the keynote and doesnt turn into months. If the I/O GT-P7510 was a consumer facing product we'd all be reading stories about high return rates by now.
Click to expand...
Click to collapse
Yeah, this has happened to me many times. The "sleep" mode apparently turns the device off completely. Ugh.
I have tried looking at the logcat but it doesn't seem to have any entries from before I powered it on from sleep (at least none that show up in DDMS in Eclipse). Perhaps someone more knowledgeable can try to get some info about the device during a long idle period.
tau_ said:
I have tried looking at the logcat but it doesn't seem to have any entries from before I powered it on from sleep (at least none that show up in DDMS in Eclipse). Perhaps someone more knowledgeable can try to get some info about the device during a long idle period.
Click to expand...
Click to collapse
Try leaving it plugged in to your computer with DDMS running overnight. That should preserve the log even after it freezes. Be sure to unplug it from the computer before rebooting the tablet or it might clear the log upon boot.
aygriffith said:
Mine isn' t rooted, so i don't think that's the issue.
There seems to be a laundry list of stuff I'm finding, this problem included. I hope that 3.1 update is indeed in "a few weeks" like they said in the keynote and doesnt turn into months. If the I/O GT-P7510 was a consumer facing product we'd all be reading stories about high return rates by now.
Click to expand...
Click to collapse
It has to be. Didn't google say they were forcing OEMs and carriers to update?
I've noticed the same issue as well, probably 4 or 5 times. I'm going to leave it plugged into my computer to night to see the logcat file.
The power issues are becoming more frequent. In the past two days I have heard two spontaneous reboots from my GT 10.1, with perhaps others that have gone unnoticed.
So i left it plugged in to logcat last night, and there was no shutdown. It looks like mine only turns off when charging via power outlet.
Just adding that I'm not having any issues with crashing or reboots at all with my IO 10.1. Maybe I'm in the minority but my Sammy has been flawless since the first boot. My only complaint is that it think I'm in the U.K so my clock is always off (heard there's an app to fix that but too lazy to deal with it at the moment).
I will watch for the charging bug and see if I can replicate it.
I Had this issue a lot with my Xoom and my transformer. That was o of the biggest reasons that I returned them. It's looking like it's a honeycomb issue.
Well when they went over that whole "forcing" of carries to update in the press only event after the keynote it came out that its a goal more of a requirement. So don't hold your breath. It surely does not mean that when the Nexus devices get a new build of Android that your average skinned carrier phone will the next day.
Sent from my GT-P1000 using XDA App
Mines powering off 4-5 times a day and I have seen a few reboots. I must say its not impressing me at the moment seeing I was ready to launch my Xperia x10 out the window for rebooting for no reason.
SO my tab shut down again last night. So I just left it didn't need it on Saturday just too busy. I turn it on tonight and to my amazement the battery is at 24% from nearly full. It sorta confirmed my suspicions the GT isnt shutting down its locking up with the screen off. Has anyone else noticed this or suspected it.
Viperoz said:
SO my tab shut down again last night. So I just left it didn't need it on Saturday just too busy. I turn it on tonight and to my amazement the battery is at 24% from nearly full. It sorta confirmed my suspicions the GT isnt shutting down its locking up with the screen off. Has anyone else noticed this or suspected it.
Click to expand...
Click to collapse
I always suspected it was locked up with the screen off because if it was shut down, it wouldn't need a super long press to power on again.
I have the Vodafone 10.1v and it has the same issue. I have only ever seen it when connected to my PC though.
Running fine for a day, then suddenly when i looked at the screen it was at the "Asus" screen (with the logo and spinny thing below) - i touched the screen and it froze.
And now its frozen.
And I had just charged it...grrr - do i really have to wait 12 hours or however much it takes before the battery is depleted.
I wonder if there is a way to reset it.
Kermode said:
Running fine for a day, then suddenly when i looked at the screen it was at the "Asus" screen (with the logo and spinny thing below) - i touched the screen and it froze.
And now its frozen.
And I had just charged it...grrr - do i really have to wait 12 hours or however much it takes before the battery is depleted.
I wonder if there is a way to reset it.
Click to expand...
Click to collapse
Hold the power button down.
Sent from my Galaxy Nexus using XDA App
Happened to several guys.
Did you try to press and hold power for ten or more seconds? It should power off and you should be able to power it on again.
this is happened to me 3 times so far.
Hold the power button to power off and reboot.
For mine after it boots it'll run ok for a minute or so, then run horribly slow until the launcher crashes. after the launcher starts back up it'd be ok.
Did you hard reset before the OTA? Where you stock, stock rooted, cwm flashed? Just trying to get more info.
fone_fanatic said:
this is happened to me 3 times so far.
Hold the power button to power off and reboot.
For mine after it boots it'll run ok for a minute or so, then run horribly slow until the launcher crashes. after the launcher starts back up it'd be ok.
Did you hard reset before the OTA? Where you stock, stock rooted, cwm flashed? Just trying to get more info.
Click to expand...
Click to collapse
We are having way too many threads for the same issue...
Mine still experiences the problem after a factory reset.
As everyone mentioned, holding down the power button fix it temporarily.
Someone else reported that you can avoid the random reboot problem by disabling deep sleep using no sleep widget, although it's a crude walkaround.
Sent from my HTC Sensation 4G using XDA App
Just an idea but what if you use something like SetCPU and up the lower frequency. Had this issue on a kanged ICS rom for my phone. It wasn't the deep sleep that was the problem but the lowest frequency was too low to re-initialize the apps that were cached once you woke it up.
I did a full complete wipe and updated from .13 to ICS and am not going to jinx myself by saying what I am implying. If you know what I mean.
Interesting, and I do agree that there are too many threads, since I am trying to get some idea of how common this is. I think I was the original poster on this, but in any case in my particular situation I tried holding the power button down, resetting it through the reset hole, and holding the power button in while pressing the volume button down (this did give me the option of reformatting which I tried) but in every case it simply flashed the eedpad screen. The battery finally appears to have died and I'm trying to recharge it now, but so far it is now completely dead. All of this happened after it went into deep sleep. This tablet is 100% original, never been rooted or tampered with in any way so, unless this is a coincidence or a combo of ICS and one of the apps I have in it, I expect this to become a very common occurence. Anyway, I'll let it charge for a bit and see what happens. I already have an RMA (the service person didn't seem too surprised and didn't really try much trouble shooting - when I asked if he had heard of this before he kind of said I wasn't the first) so I'm sending it back to Asus on Monday so that when I get it back I can sell it, but I'm just wondering what percentage of people are having this problem. Heck, if it's even just 5% Asus is going to have a major expense on its hand.
I had the dreaded Asus logo freeze twice now, since the ics update. Both times when I wasn't using the tablet.
Sent from my Galaxy Nexus using Tapatalk
Mine has frozen 2x already since the ics update. I performed a factory reset before and after the update.
Screen just goes black/blank and would have to hold the power button for 10secs.
Sent from my Transformer TF101 using Tapatalk
Hey thanks, I thought I had pressed power down for long enough - but apparently not.
I was on normal HC and just accepted the update when it prompted me for it.
But if a lot of people are seeing this i guess Asus made a little blunder in this version.
I just came in after leaving my Transformer asleep for about three to four hours, and found the asus logo flashing on for a few seconds and then off, repeating over and over. Had to do a reset with power and vol down to get it to reboot. Seems OK for now except it really drained the battery.
I guess there will be a few ICS bugs to work out.
jparity said:
We are having way too many threads for the same issue...
Mine still experiences the problem after a factory reset.
As everyone mentioned, holding down the power button fix it temporarily.
Someone else reported that you can avoid the random reboot problem by disabling deep sleep using no sleep widget, although it's a crude walkaround.
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
About the "No Sleep" widget, that was me. Well, this seems to be a widespread issue. Asus should take the update back and stop offering OTA...this is a pretty big issue.
Sent from my GT-I9100 using XDA App
msaraiva said:
About the "No Sleep" widget, that was me. Well, this seems to be a widespread issue. Asus should take the update back and stop offering OTA...this is a pretty big issue.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Well asus is good about providing prompt follow up updates so I wouldn't be surprised if we start getting bugfix updates in the coming weeks.
Yea seems like the TF only goes crazy when it's in sleep/not being used.
Mine is not rooted so I don't really want to go through the trouble changing processor frequency.
Where is the reset hole btw?...
Sent from my HTC Sensation 4G using XDA App
It's next to the hdmi port.
jparity said:
Yea seems like the TF only goes crazy when it's in sleep/not being used.
Mine is not rooted so I don't really want to go through the trouble changing processor frequency.
Where is the reset hole btw?...
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
r_nt said:
It's next to the hdmi port.
Click to expand...
Click to collapse
Isn't that the mic? I don't believe that's a reset button. I could be wrong though
Sent from my Transformer TF101 using xda premium
eminembdg said:
Isn't that the mic? I don't believe that's a reset button. I could be wrong though
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
There isn't holding the power button for 15 seconds resets it.
Sent from my Transformer TF101 using Tapatalk
r_nt said:
It's next to the hdmi port.
Click to expand...
Click to collapse
I thought it's the mic too... Does your voice record still work after you "reset" your TF?...
Edit: Saw the dreaded Asus loading screen again when I came back from dinner... 3rd time today... It's getting on my nerves a bit now. Such a pity that the TF is perfect besides this issue... I don't care if it reboots every hour or so, as long as it doesn't hang and depletes the battery.
Just to clarify, and so others don't break their microphone,THERE IS NO RESET HOLE! if your device is frozen, hold the power button to reset.
Are we certain its the deep sleep causing this?
Didn't happen to me this morning. I stopped using it around midnight and woke up fine the next day.
fone_fanatic said:
Just to clarify, and so others don't break their microphone,THERE IS NO RESET HOLE! if your device is frozen, hold the power button to reset.
Are we certain its the deep sleep causing this?
Didn't happen to me this morning. I stopped using it around midnight and woke up fine the next day.
Click to expand...
Click to collapse
How do you it didn't happen? It doesn't get stuck at the ASUS logo for me, it simply reboots. Try leaving something open, like a browser window, turn off the screen and come back sometime later. If it's back to the homescreen and there are no recent apps, then it rebooted.
I don't know if it is the deep sleep that is causing it. All i know is that the bug is only triggered while sleeping. Every logcat i get stops at an AlarmManager event, before the reboot.
Sent from my Transformer TF101 using XDA Premium HD app
Ok, random reboots are gone...now it's just sleep of death.
Every. Damn. Morning.
No kidding...every single day, the thing has shut itself off and drained it's battery completely..TABLET AND DOCK mind you, for about a week now. I can't set it down and close the lid..I feel like I'm using paul burton's Spark ROM. I am actually about to RMA this thing myself because of this......
It's getting very hot on recharge from completely dead, and it's done it so many times now I fear it's very likely to have damaged the life of my battery as an end-user..
Add to this..dust INSIDE my camera lens, dead pixels, and half-working microSD slot (the card has to be inserted JUST SO..in order to be recognized).
I want a new device..I'm done playing around with this defective toy, I want a real workhorse that I can depend on, I need it for my projects. Sadly, I have a SBK1 too...
Had only a few reboots a week on all ICS stock, Revolver, Revolution and CM9 roms. No battery drain. I do not have a dock.
Since I flashed CM9 Megatron a few weeks ago, I experienced no reboots at all, except a few lockups on Home Screen. Since Megatron 1.0.3 based on ICS 4.0.4 and the latest guevor kernel test13, it's running smooth as butter with great battery life and overclocked to 1.4GHz.
Does the battery drain like that when it is not docked?
With all those issues, you should RMA. Although when you get the device back it will probably still have sleep of death (and maybe random reboots).
Sent from my DROIDX using Tapatalk 2 Beta-5
In another thread, it was mentioned that the ICS update defaults the TF101 to have the setting "stay awake - screen will never sleep while charging" enabled, no matter whether it looks like there's a checkmark on that setting or not. When the tablet is docked, it is considered as "charging" and therefore it will stay awake and drain the tablet battery and the dock battery. The fix is to manually toggle the checkmark on and off on that setting, whether there looks like there is a checkmark there or not. That's why I asked whether or not the battery drains when undocked.
Strangely I didn't get a second update yet
ssl123 said:
In another thread, it was mentioned that the ICS update defaults the TF101 to have the setting "stay awake - screen will never sleep while charging" enabled, no matter whether it looks like there's a checkmark on that setting or not. When the tablet is docked, it is considered as "charging" and therefore it will stay awake and drain the tablet battery and the dock battery. The fix is to manually toggle the checkmark on and off on that setting, whether there looks like there is a checkmark there or not. That's why I asked whether or not the battery drains when undocked.
Click to expand...
Click to collapse
The 'fix' was reported to be simply unchecking and checking the box (it's toggle is set to on, but the actual feature is disabled until you do this). I had previously done this, and forgotten about it..but I will go check again, though I am pretty sure that my CWM backup was made well after my settings were adjusted like this, and the backup I restored and am using now did not previously crash like this.
EDIT: Also, once the dock is drained to 3% it is supposed to stop 'charging' so it *should* not result in draining the tablet's battery completely (from full charge on both units however, with screen off, awake or asleep, I would think I could get more than 8-10 hours battery life without draining both batteries to 0%..yes, 0%. This is what scares me that the batteries have been damaged..after 5-8 times that it has overdischarged now..)
Experiencing the exact same issues here
SODs and complete battery drain when supposedly off. My tab is also permanently connected to keyboard.
Getting very frustrated now.
I've using Revolver ROMs for a long time now and these issues only occured after flashing the ICS betas. It had gotten so bad that I went back to Honeycomb but the SODs and battery drain persisted even then.
Tonight I flashed the newly released Revolver RC1 rom in hope that the issues would be fixed but unfortunately I've had a random reboot already
Not sure where to go now as the stock Asus rom has these issues as well I believe. iPad anyone?
Rant over and many thanks to all the devs for their unselfish work.
Jake
Well, my screen keeps coming on. That seems to be the problem. At random while docked, it just comes on. I look at the dock when it's closed and see it's on..so I open it and manually turn it off (the screen not the device) and leave it open..a few minutes later, there it is again, on..for no reason.
This is my likely culprit, and it's really pissing me off. I am on a stock ROM, so unless this is guevor's kernel's fault, it's Asus', I'm leaning towards Asus.
However judging from some of the responses, it would seem users are having this without using guevor's kernel..so there goes that option.
Can anyone confirm they are getting this issue with the stock kernel?
You are part of this group then: http://forum.xda-developers.com/showthread.php?t=1559544
Not just you all....
Funny...
Came here to consider rooting my tablet to fix similar issues, and you all are having the same issues. I am NOT rooted, tablet keeps going into some sort of "deep sleep" (that's what a developer friend called it). Sometimes the battery is draining to nothing, sometimes not. Although, once it goes into this sleep mode, it's near impossible to get back out and always requires a reboot.
PLUS the constant rebooting for no reason, right in the middle of work. This thing's been super buggy since the ICS update, ASUS is absolutely no help (worst service I've experienced in years)...wish I had never installed it. NOTHING about the update is worth all this headache...
According to my research, it's a known issue...meaning ASUS knows it's a problem and are supposedly working on it. I kept reading about another OTA update that was supposed to fix some of these issues last week, but haven't seen anything yet.
Yet another notch in the "dump android" column
sigh.
(Wish I could be more help, thought you'd want to know it's a product-wide issue)
hi therr
please install the wakelock app until asus fix the problem
works for me, but i dont have a dock
Sent from my Transformer TF101 using XDA Premium HD app
Since going to aokp nightlies and guevor kernel test 13. I have had zero reboots batt drain etc... works like it's supposed to, oc to 1400 as well been three days now on two different tf's i have one at home and one at work.I am officially a happy camper again.
glange65 said:
Funny...
Came here to consider rooting my tablet to fix similar issues, and you all are having the same issues. I am NOT rooted, tablet keeps going into some sort of "deep sleep" (that's what a developer friend called it). Sometimes the battery is draining to nothing, sometimes not. Although, once it goes into this sleep mode, it's near impossible to get back out and always requires a reboot.
PLUS the constant rebooting for no reason, right in the middle of work. This thing's been super buggy since the ICS update, ASUS is absolutely no help (worst service I've experienced in years)...wish I had never installed it. NOTHING about the update is worth all this headache...
According to my research, it's a known issue...meaning ASUS knows it's a problem and are supposedly working on it. I kept reading about another OTA update that was supposed to fix some of these issues last week, but haven't seen anything yet.
Yet another notch in the "dump android" column
sigh.
(Wish I could be more help, thought you'd want to know it's a product-wide issue)
Click to expand...
Click to collapse
Not exactly a product-wide issue. For whatever reason, some Transformers, like mine, do not have the same problems or not nearly to the same extent. I have had 300+ hour uptimes (2 weeks) with this iteration of ICS, though, when it does go down, I suspect it might be when I choose to use Flash in a browser. I haven't really looked into it. You are also mixing up issues. This particular issue is with dock owners. Toggling the "stay awake" setting may or may not help in this case. I don't have a dock, so I don't know. Some say it did help.
The issue you are describing is separate and has a workaround and a possible fix posted.
Workaround: http://forum.xda-developers.com/showthread.php?t=1567795
Possible fix: http://forum.xda-developers.com/showthread.php?t=1518552
ASUS might have already resolved the problem in their TF101G firmware, but I don't know why they haven't released a patch yet for TF101.
As many have pointed out in other threads, it's not possible to extrapolate how many are affected by your issue because this is a support forum that pops up high in the Google rankings. Many people end up here when looking for support for problems. Therefore the population here is naturally going to be disproportionately high in people having problems. I myself ended up on XDA because of an issue with the Lenovo K1 tablet.
I am at the point where I want to throw my Transformer out the window it happens so much.
spotdog14 said:
I am at the point where I want to throw my Transformer out the window it happens so much.
Click to expand...
Click to collapse
I sometimes feel the same way but it sucks bc when the tablet works fine its awesome. Did the update they release for the TF101G work without problems? Damn, I wish it get fixed soon.
spotdog14 said:
I am at the point where I want to throw my Transformer out the window it happens so much.
Click to expand...
Click to collapse
So why not just install the wake lock app and stop the aggravation? It is a 100% rock solid fix, or workaround for now. Battery life hardly suffers also.
fldude99 said:
So why not just install the wake lock app and stop the aggravation? It is a 100% rock solid fix, or workaround for now. Battery life hardly suffers also.
Click to expand...
Click to collapse
In my tests I lose 0.3%/hour without wakelock and 1.5%/hour with wakelock. So over a few hours not much impact. But over 12+ hours it starts to add up.
Sent from my Transformer TF101
I started getting a random reboot here and there after the last update, but only when low on battery and when its plugged in. It will have less then 20% batt, plug in and then it'll reboot instantly after a few minutes.
Its a pos and i am getting rid of mine. I shouldn't have to root or install an app for this **** to work. Complete and utter fail.
I have been using a new ICS build and wanted to warn everyone about the shutdown problems. It seems that by choosing to shut down by pushing the button and choosing "shut down" leaves the backlight running (you can see it if you look).
This has drained my battery down to nothing preventing my Kindle from booting. The stock charger did nothing, no charge, no light, no boot. Plugging in to the PC made the Kindle come on, but reboot after a couple seconds, not long enough for me to even get into recovery mode.
On a hunch I used my phone charger. Not only did the Kindle kick on and boot, but it seems to be slowly charging. I restored back to the stock ROM and now it seems like the stock charger has no effect at all.
Just be careful and be aware that the back light will stay on for now until the kernel is updated.
Thanks!
Sent from my Kindle Fire using xda premium
It happened to me already, but it woke up with the original charger.
Thanks!
yeah two known bugs for the 3.0 kernal are usb wall charging and the device not shutting all the way off (backlight stays on). if you need to you can always go into recovery to charge up. also turning lockscreen and touch sounds off in settings>sound will help save battery
It's 2 different bugs that can combine in a bad way: quick battery drain and loss of wall charger.
Anyways there is hope, people have been grabbing a USB charger form other devices or for most the USB-PC route still charges.
The ROMs are getting very good, the banding is fixed and it seems the AC charger issues have been patched up, even the small menu buttons are fixed in one of the ROMs. Now all I need is a volume bar and I will have my daily driver for a while.
This just happened to me...
My kindle died after shutting down for one day. No battery at all...
Did you even read the first post of the kernel thread?
ryanhuong said:
It's 2 different bugs that can combine in a bad way: quick battery drain and loss of wall charger.
Anyways there is hope, people have been grabbing a USB charger form other devices or for most the USB-PC route still charges.
The ROMs are getting very good, the banding is fixed and it seems the AC charger issues have been patched up, even the small menu buttons are fixed in one of the ROMs. Now all I need is a volume bar and I will have my daily driver for a while.
Click to expand...
Click to collapse
Something for the volume control:
https://play.google.com/store/apps/details?id=rubberbigpepper.VolumeControl
Back to OP, I used to hold power until the backlight would turn off (about 15sec) but one day it just so happened that my kindle did not turn off completely even then. After that I have been holding it down for a straight 20sec.
Sent from my Amazon Kindle Fire using XDA
StaticMatt said:
Did you even read the first post of the kernel thread?
Click to expand...
Click to collapse
No, and that's why it's a surprise to them. Hashcode has been saying, repeatedly, he doesn't recommend it as a daily kernel. In big red letters, at the top of two threads, it says wall charging doesn't work. Throughout those threads it has other people posting who say they don't know why their kindle died overnight.
It's just a neverending...I wanna call it a cycle, but there's no cycle to it. It's more like a neverending stream of people who refuse to read.
Guaranteed, if I made a thread offering a kernel and in big red letters at the top it said "THIS KERNEL WILL BRICK YOUR KINDLE" and then proceeded to post a changelog and other information about how to install, etc... There would be no less than 100 posts the following day asking why their kindle doesn't work.
If the devs were offered a dime every time somebody failed to follow directions...
Felnarion said:
No, and that's why it's a surprise to them. Hashcode has been saying, repeatedly, he doesn't recommend it as a daily kernel. In big red letters, at the top of two threads, it says wall charging doesn't work. Throughout those threads it has other people posting who say they don't know why their kindle died overnight.
It's just a neverending...I wanna call it a cycle, but there's no cycle to it. It's more like a neverending stream of people who refuse to read.
Guaranteed, if I made a thread offering a kernel and in big red letters at the top it said "THIS KERNEL WILL BRICK YOUR KINDLE" and then proceeded to post a changelog and other information about how to install, etc... There would be no less than 100 posts the following day asking why their kindle doesn't work.
Click to expand...
Click to collapse
This is a discussion forum right? We are discussing.
If I can help even 1 person avoid that problem then I will. Maybe you guys should stick to the dev threads with all the smart people. This thread is for dummies who can't read.
Not going to argue with you on that one.
ryanhuong said:
This is a discussion forum right? We are discussing.
If I can help even 1 person avoid that problem then I will. Maybe you guys should stick to the dev threads with all the smart people. This thread is for dummies who can't read.
Click to expand...
Click to collapse
You do see the irony in all that, right?
@ryanhuong - just wanted you to confirm once that the wall charger is not indeed working for you.
I too had the same impression for some time as it _looks_ that way, but then realized it is working when I hit the top-left Refresh button in Settings -> Battery. The % kept going up.
umash4 said:
@ryanhuong - just wanted you to confirm once that the wall charger is not indeed working for you.
I too had the same impression for some time as it _looks_ that way, but then realized it is working when I hit the top-left Refresh button in Settings -> Battery. The % kept going up.
Click to expand...
Click to collapse
With the newest kernel yes it seems to charge fine. The Pure AOKP build seemed to have more issues. Now I am using the newer AOKP and not does the charger work again, but the LED now shows orange or green (but the battery icon s still wrong).
Huge improvements so far.
This happened a few times with my Optimus V. This was because there was no offline charging support for AOSP ROMs at the time. The only way I could get the phone to stay on was to force the battery into a LG Rumor Touch and recharge it with that until the battery could boot the Optimus. Thinking how the Kindle Fire has no offline charging support and a non-removable battery strikes fear into my soul.
I know the AOKP ROMs fully power off the device. So at least I'm okay with that.
Also, is it bad that my Kindle Fire charges extremely slow with any other cable than the stock charger?
Sent from my Amazon Kindle Fire using Tapatalk 2
It will always work best with the stock charger, but until the bugs are fixed, who knows.
KemikalElite said:
Thinking how the Kindle Fire has no offline charging support and a non-removable battery strikes fear into my soul.
Click to expand...
Click to collapse
It does charge offline, the problem lies in the LED not reporting this properly (it doesn't turn on to reflect the charge status).
KemikalElite said:
Also, is it bad that my Kindle Fire charges extremely slow with any other cable than the stock charger?
Click to expand...
Click to collapse
This is normal, as they usually provide less amps than the stock charger (1.8).
For what it's worth, I am on #33 AOKP KF Edition and the LED works perfectly. It's the icons that don't work right.
EDIT: I take that back. If the KF is asleep and you plug it in the LED stays dark. If the tablet is awake and you connect the charger, the orange comes on, putting the tablet to sleep the LED stays orange till it turns green when full.
Felnarion said:
No, and that's why it's a surprise to them. Hashcode has been saying, repeatedly, he doesn't recommend it as a daily kernel. In big red letters, at the top of two threads, it says wall charging doesn't work. Throughout those threads it has other people posting who say they don't know why their kindle died overnight.
It's just a neverending...I wanna call it a cycle, but there's no cycle to it. It's more like a neverending stream of people who refuse to read.
Guaranteed, if I made a thread offering a kernel and in big red letters at the top it said "THIS KERNEL WILL BRICK YOUR KINDLE" and then proceeded to post a changelog and other information about how to install, etc... There would be no less than 100 posts the following day asking why their kindle doesn't work.
Click to expand...
Click to collapse
Actually as one of the guys that's working on the kernel I would have to say you're incorrect. Wall charging does in fact work. The issue with the led is that the kernel doesn't correctly update it, as well as it doesn't update the from in a manner for the icon to change. If you download a battery widget in the market you will see that it does in fact charge with a wall charger. This is also a better route to go since the OEM charger puts out about 1000mv as opposed to 100mv w/USB 1.0 or 500mv w/USB 2.0. Only other steady charging scenario would be USB 3.0 because its output is 900mv.
Sent from my MB860 using XDA
Hi All,
I was browsing the web a couple of hours ago and my N10's screen started flashing on/off and after around 10secs the thing crashed/turned itself off. Being an N10 this was not an unusual event! However when I try to turn it back on nothing happens. I can hold the power button / power button with volume buttons pressed and nothing happens. If I plug it in to charge I do not get even get a charging icon.
If it makes any difference I was running the latest Rasaber with Franco's r11 kernel and I know I had at least 40% battery left when it died. I have left it plugged in to the stock charger for around an hour hoping that something might happen but still nothing.
Has anyone ever experienced anything like this?
There was not a sad enough looking Emoticon to convey my sadness over the possibility my lovely Manta is dead......
no man ... it s impossible . nexus 10 its the best device ever . acording to some gurus here
your device its dead . now you have to stay on your knees to google replace it . good luck
Sent from my Nexus 10 using xda app-developers app
Something similar happened to me but I'm totally stock. I Googled and the solution was to recharge the unit via my PC USB instead of plugging it into an outlet. I have no idea what happened but after a few hours of being connected to my PC it was back and working. Hope that helps.
I'm running the same rom and kernel combo. No problems or anything weird happened. It must be hardware related.
Did you try the holding-the-power-button-for-a-minute routine?
I would try to leave it plugged in on the charger for a while and see if it gets fixed. That usually solves all sorts of "wont turn on" problems
samwheat said:
no man ... it s impossible . nexus 10 its the best device ever . acording to some gurus here
your device its dead . now you have to stay on your knees to google replace it . good luck
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
You seem upset
i seem realistic
another nexus 10 with problems
Sent from my Nexus 10 using xda app-developers app
is it possible for the tablet to get overheated?
I have had that happen on stock.
My theory: it is linked to the 'battery status not updating'-bug. Your Nexus thinks the tank is still half full, while in fact you are running on fumes. It does not realize this, so no dimming of screen, no low power warning, it just goes full steam ahead, until the battery is totally and utterly and completely depleted.
Then, obviously, it won't start but it will also have trouble charging. You need to charge it for quite some time, sometimes try a different charger, and sometimes keep the power button depressed for a full minute for it to come back to life.
Now when I use my Nexus, I keep an eye on the battery status. If it does not go down, I know I need to reboot for the battery status to be read properly again. It is a bit of a bother, but not too much. The bug only kicks in after the tab has been lying around for a while sleeping. So if I want to watch a movie, I first reboot. As long as I keep using the tab (i.e.watching the movie), the bug won't 'activate' and the tab will shut off properly when it senses the battery is low, in stead of continuing and deep depleting the battery.
Sent from my Nexus 10 using XDA Premium HD app