Got the update, turned off WakeLock, and at some point in the middle of the night it rebooted. Not locked so I waited. Got stuck in a later reboot. Sigh. I'm glad that ASUS is trying to fix this. So at this point I've just re-enabled WakeLock, and will wait for the next update with the hope that it will have a better result.
Official ASUS Thread - ICS Update on TF101 (20-Mar-2012)
- Thread starter Gary Key
- Start date
-
- Tags
- tf101 transformer
I'm pretty confident you'll still have the problem even after a wipe (I do with my tablet, although I didn't go quite as far as creating a completely separate testing Google account), but it'd be good to be able to make that clear to Asus with a brand new device that they just themselves shipped to you.
Environmental... hmm, it *would* explain why some of us can replicate it with multiple tablets, but not why the patterns can be radically different with two identical tablets at the same location (mine seems to have noticeably worse problems than my wife's, but we both have problems).
Even if it's environmental in some manner, though, it still has to hail from a software problem at the end of the day, because it didn't happen with Honeycomb. (I'd heard people complaining of Sleep of Death with HC, but I'd never personally seen it happen at all for most of the last year; now it's about the most common state to find my tablet in when I pick it up.
I'm wondering if instead of environmental, it's to do with usage patterns. Maybe some people are using their tablets so lightly that they don't see problems, and others are using them enough to pass some threshold on memory or CPU utilization that kicks the problem off in the first place. Then once the instability has been started, you get a boot loop or whatever the next time the tablet tries to sleep after the instability.
Actually, there is an explanation as to why the patterns can be radically different - most wifi routers come with their channel set to "auto" by default, which means that they can change which channel they are using from time to time, based on what other wifi routers in the area are using. Maybe it's only when other routers are using the same channel as your router/Transformer...
Again, it's a longshot, but I can probably test this, although, probably not with stock ROM (can stock USA ROM do channels 12-14?)
Sent from my Transformer TF101 using Tapatalk 2
Sorry, but I have a background as a trained network engineer for a major multinational, so I'm not your typical home user. My router is set on the channel that is quietest and has best coverage throughout my property. I have both of my tablets on static IPs because HC had a problem with wifi connections locking up when the DHCP lease expired. My suburb is low-enough density that I can only see 2-3 neighboring networks, and they would appear to have fixed channel allocations, too. They're also very weakly received inside my house, and I don't suffer interference from any other 2.4 GHz devices, either. And for most of the day I don't even have devices joining or leaving the network.
Hence, my network simply doesn't change significantly.
Sent from my Transformer TF101 using XDA
Hence, my network simply doesn't change significantly.
Sent from my Transformer TF101 using XDA
Oh, sorry, missed your question re: stock rom channels for US devices. It's been a while since last I read, and I don't honestly remember the answer to the question, sorry.
Sent from my Transformer TF101 using XDA
Sent from my Transformer TF101 using XDA
Actually, I wasn't talking about your home router, but about other routers that your router can see. It's possible that other users routers are changing channels and interfering with your channel, right? I too, have mine set to the cleanest channel possible, but even then I have other networks around my house that use that same channel at times.
I used to have it set to channel 12, but I now have devices that don't support that channel, so I have to move back down into the "normal" channels...
It should be easy enough to test this theory as long as a stock TF will connect on channel 12.... I'll test that later too (too many household members streaming TV programming over the wireless right now)....
EDIT: Nevermind - you already explained in your post that your neighboring networks don't change their channels at all... I misread it the first time...
Oh well, it was a theory...
Sent from my Transformer TF101 using Tapatalk 2
Last edited:
EDIT: Nevermind - you already explained in your post that your neighboring networks don't change their channels at all... I misread it the first time...
Oh well, it was a theory...
Hey, nothing wrong with theories, I'm all for them. Somebody's gotta fix this thing, and so far it isn't looking like Asus are a cert to manage it... ;-)
FYI - while the new loaner tablet stayed up overight while sleeping, abot 15-20 minutes later I opened it again and nothing happened. Waited a few seconds and bam - it rebooted (not stuck in boot loop this time). Uptime was a little over 7 hours.
This loaner unit actually seems WORSE than mine! I'm going to reset to factory defaults now and see if the same thing happens with stock apps and a fresh google account. I will however be installing a *few* apps, to at least help me determine if it rebooted and is deep sleeping (cpu spy and uptime widget)....
EDIT: Whoa, my original TF is now all messd up - half of the appps force close immediately, if I tap the tapatalk widget, it puts me in gmail app with some error on the screen!
Should I be able to use the same google account on two exact tablets without issue (never had two of the same devices before)...
Looks like inhave to factory reset my original tf now.... ugh...
Sent from my Transformer TF101 using Tapatalk 2
This loaner unit actually seems WORSE than mine! I'm going to reset to factory defaults now and see if the same thing happens with stock apps and a fresh google account. I will however be installing a *few* apps, to at least help me determine if it rebooted and is deep sleeping (cpu spy and uptime widget)....
EDIT: Whoa, my original TF is now all messd up - half of the appps force close immediately, if I tap the tapatalk widget, it puts me in gmail app with some error on the screen!
Should I be able to use the same google account on two exact tablets without issue (never had two of the same devices before)...
Looks like inhave to factory reset my original tf now.... ugh...
Sent from my Transformer TF101 using Tapatalk 2
Last edited:
If we *believe* in Asus, and that the loaner didn't have problems, then i agree it should be enviromental. If it was caused by some kind of interference, then disabling wifi should fix the problem (I know, why would someone want a TF without connection... I just want to know WHAT is the cause of the RR and SoDs).
I have zero background in engineering, so correct me if Im saying something stupid.
From now on, I'll disable all the wireless connections on my TF and check how long can i go without RR or SoDs.
I'll report back from my PC as soon as anything worth reporting happens.
Sent from my Transformer TF101 using Tapatalk 2
Its an important test to report to ASUS if your loaner has the same issues with rebooting so that they know that their "reference" tablet is also broken.
Regarding multiple units with the same account, I havent tried two ICS devices but I certainly have both my phone and tablet wired to the same account with no problems. The phone is running gingerbread. That scenario had better work!
One thing I find curious about this issue is why there seems to be a sort of honeymoon period immediately following an update where it seems stable for a bit and then the problems appear to progressively get worse. Cache build up is a theory but even after a cold boot the problem stays...
Regarding multiple units with the same account, I havent tried two ICS devices but I certainly have both my phone and tablet wired to the same account with no problems. The phone is running gingerbread. That scenario had better work!
One thing I find curious about this issue is why there seems to be a sort of honeymoon period immediately following an update where it seems stable for a bit and then the problems appear to progressively get worse. Cache build up is a theory but even after a cold boot the problem stays...
Well, I have disabled Wifi / Bluetooth, Wakelock, and have cold booted.
So now I have a really nice and expensive sudoku machine.
I never got over 18hr without RR, so thats my goal for today.
I let it Deep Sleep a lot, then I play a little, and back to sleep.
It's docked, has a mini SD mounted and not charging.
Update #1: TF has an uptime of 6h22m with over 5h of Deep Sleep. Apps used: CPU Spy / UpTime Widget / Andoku 2 / Settings. Dock Battery has gone from 86% to 75%.
Update #2: TF has an uptime of 13.5hr with 12hr of deep sleep. Same apps used as before. Battery has gone to 58%.
So now I have a really nice and expensive sudoku machine.
I never got over 18hr without RR, so thats my goal for today.
I let it Deep Sleep a lot, then I play a little, and back to sleep.
It's docked, has a mini SD mounted and not charging.
Update #1: TF has an uptime of 6h22m with over 5h of Deep Sleep. Apps used: CPU Spy / UpTime Widget / Andoku 2 / Settings. Dock Battery has gone from 86% to 75%.
Update #2: TF has an uptime of 13.5hr with 12hr of deep sleep. Same apps used as before. Battery has gone to 58%.
Last edited:
If it is wifi interference then my neighborhood is the perfect testing ground. From my living room I see 33 wifi networks in the 2.4 ghz range. There are no stable channels and all are congested. I have my tablet turn off wifi when I close it, and the WakeLock app prevented the reboot, and boot loop for over10 days. Installed the update, and rebooted in 10 hours and got stuck in a boot loop soon afterwards. To me it's clearly a deep sleep issue but what is the trigger during deep sleep is the real question.
Oh yeah, I am most certainly in contact with Asus through all of this - and Gary is even replying on the weekends! Like I said, the guy is dong everything he can to help us, trust me!
So, I'm now back to pretty much stock apps on both TF's. Let's see what happens now... I have them connecting to two different wireless routers at this point (yes, I have more than one in my house - I actually use a total of 5 wireless routers - most of which are in client-bridge mode in order to network cabled-only devices into my wireless network).
I'll report back soon....
Sent from my Transformer TF101 using Tapatalk 2
Screenshots of infinite power bug and update
Screenshots
http://xdaforums.com/album.php?albumid=6825
ICS .11&.17 - battery drain from 100% to 0% in about 7 mins and charges up in about the same amount of time. Had this bug for over a month from march onwards. I first got the infinite power bug after upgrading to ICS, it's where the battery meter stays at 100% for hours on end without being plugged in for charging.
ICS .21 - Since the 9.2.1.21 update I had it 4 times total, it's been alternating with another bug where it goes from charged to zero battery and shuts down the second I unplug the charger. The infinite power bug must only be triggered by OTA update because I tried reinstalling the .21 firmware.
Mine is from the B30 batch.
I do not have the dock.
I do not have the random reboot issue.
Battery life after shutting down and reboot is completely random. Sometimes it the same. Most of the time it's less. And on the rare occasion it actually says that the battery is higher than when it was shut down, all without the charger plugged in.
Things I have tried
Reboots, resets, coldboot, changing various settings, etc. I sent it in for repair which was a waste of shipping costs. Emailed ASUS twice, response time is longer than 1 week. The response from the second email said to call repair center. Calling is much faster but same results no one knew if it was hardware or software problem. Dragging around a 12FT extension cord is still currently the best solution I've come up with.
Update: My battery now fluctuates between 4-35 mins. I thought is was stuck on a half hour charge up and discharge cycle for a while but it's still fluctuating. I had the no audio bug once, yes I did check to see if the silent mode was off. It was fine after reboot.
Screenshots
http://xdaforums.com/album.php?albumid=6825
ICS .11&.17 - battery drain from 100% to 0% in about 7 mins and charges up in about the same amount of time. Had this bug for over a month from march onwards. I first got the infinite power bug after upgrading to ICS, it's where the battery meter stays at 100% for hours on end without being plugged in for charging.
ICS .21 - Since the 9.2.1.21 update I had it 4 times total, it's been alternating with another bug where it goes from charged to zero battery and shuts down the second I unplug the charger. The infinite power bug must only be triggered by OTA update because I tried reinstalling the .21 firmware.
Mine is from the B30 batch.
I do not have the dock.
I do not have the random reboot issue.
Battery life after shutting down and reboot is completely random. Sometimes it the same. Most of the time it's less. And on the rare occasion it actually says that the battery is higher than when it was shut down, all without the charger plugged in.
Things I have tried
Reboots, resets, coldboot, changing various settings, etc. I sent it in for repair which was a waste of shipping costs. Emailed ASUS twice, response time is longer than 1 week. The response from the second email said to call repair center. Calling is much faster but same results no one knew if it was hardware or software problem. Dragging around a 12FT extension cord is still currently the best solution I've come up with.
Update: My battery now fluctuates between 4-35 mins. I thought is was stuck on a half hour charge up and discharge cycle for a while but it's still fluctuating. I had the no audio bug once, yes I did check to see if the silent mode was off. It was fine after reboot.
Last edited:
Well, that's great to hear at least. No idea if he has the clout to, but if he does then his next step needs to be to provide an officially sanctioned path back to Honeycomb, until the problem is fixed.
Honestly, your problem is utterly different to everybody else's, and sounds to me more like a hardware issue. Have you rolled back to Honeycomb, and managed to restore normal behavior? If not most likely your battery is simply dying, and it coincidentally happened alongside the ICS update availability. Either way, you should probably start a separate thread as your problem isn't what's being discussed here, and by shoehorning your problem into this thread, anybody who *does* share the same problem as you won't find the thread.
It started hours after the first ICS update. If the battery were dying how does it explain how I got 2 hours out of it right after the .21 update. And it's been over a month and no one seems to have my exact problem. If I start a thread it only be me posting to it.
A little birdie told me that they ARE working on it (the downgrade path)...
Sent from my Transformer TF101 using Tapatalk 2
Well, suffice to say, posting in a thread that's completely unrelated to your problem isn't going to help either. If you continue I'll be putting you on ignore, and I doubt I'm alone in that. If you post in a thread that's got a topic actually related to your problem, there's every chance you'll find that a) somebody knows how to help you, and b) somebody else does have your problem, and you just didn't know that because both of you were posting in utterly unrelated threads.
---------- Post added at 01:42 PM ---------- Previous post was at 01:39 PM ----------
A little birdie told me that they ARE working on it (the downgrade path)...
Sent from my Transformer TF101 using Tapatalk 2
A.W.E.S.O.M.E.
I'm at the point where I don't even care if I have to wipe all my apps to do it; my own tablet has gotten unhappy from all the reboots to the point where quite a few apps instantly close again when opened and even kill the "report error" dialog that pops up. Hence I'm going to have to wipe anyway. And I'll be downgrading my wife's tablet too, because even though hers seems pretty stable still, I can tell from her tone of voice whenever I mention Asus that she's sick of all the reboots too. ;-)
This does make perfect sense but I was hoping with the shear number of people on this thread that someone might also have these bugs. I started a new thread. I don't think anyone will respond on it.
Well..haven't had a single rr or SOD since the recent patch. Previously couldn't make it through the night without a SOD in the AM without wake lock app enabled. It still could happen, but something was improved with this patch-no question about it. However, I have to reboot manually because after a period of time the gmail app acts up with freezing and force closing. Just my experience so far. Stock unrooted btw
Similar threads
- Poll
Top Liked Posts
-
There are no posts matching your filters.
-
85Hi,
We have not been able to replicate the battery drain and random reboot issue that several users have reported after the ICS update and subsequent firmware updates.
As such we are looking for a few volunteers here to run a custom logging problem and report back their results. The system needs to have either the random reboot or battery drain issue and cannot be rooted.
If you are willing to run this logging problem (very much appreciated) then please PM with the following information.
Name
Email Contact Information
Serial Number
Problem Description
Sincerely,
Gary
Update -
I will start sending out the logging file and instructions to the test group tomorrow.
The logging tool simply captures low level OS routines that might lead us to the source problem.
3/21/2012 Update -
The logging tool was delivered to the first control group tonight. I will send the tool to the second control group tomorrow. Thank you for your assistance and replies.
3/26/2012 Update -
Thank you for your assistance and log reports. R&D is working on them feverishly right now. I will send out the tool to a third control group shortly.
4/2/2012 Update -
First off, thank you for your assistance and log reports. We are still investigating root causes for some of the problems. As such, personnel from the three control groups might be contacted directly for a system replacement so we can further investigate the lockup problem. I will have an update later this week.
4/9/2012 Update -
Thank you for the continued log reports. We are working through all the data now within R&D and at NVIDIA/Google. As soon as I have word on a Firmware update I will post it here.
4/18/2012 Update -
We sent out a beta Firmware release to a few users for testing. So far, it has solved the problems these users have experienced but I am still waiting on a couple of test updates. We also received back a unit that had the random lockup and screen corruption problem and so far after 22 hours of testing no problems. If the balance of the test updates are positive, we will get this build qualified and releases ASAP.
4/24/2012 Update -
9.2.1.21 will roll out today in North America. This release addresses several of the random reboot and lock problems reported by a few users after upgrading to ICS. It also provides new functionality with WiFi-Direct, Unzip in File Manager, Restore Tab function in the Browser, and general performance/stability tweaks. Although we had a high success rate in the beta testing phase in solving the random reboots, there were a couple of users who still experienced it during deep sleep mode. We are having those systems returned to us for further analysis and regression testing with their particular setups.
5/3/2012 Update -
We will release 9.2.1.24 into beta testing shortly. This firmware contains new NV code based upon the beta test group who still had issues with .21. I will provide updates once the firmware goes out to the beta group but it did fix returned units that experienced random lockups after .21.
5/9/2012 Update -
I have been out with pneumonia but will have messages forwarded to the Customer Care Team. The .24 release is in final qualification testing and will be released shortly.
5/10/2012 Update -
The .24 release is approved and will be released in the near future.
5/14/2012 Update -
The .24 release should go to FOTA later today or early tomorrow. Please shutdown and perform a cold boot after updating.
5/15/2012 Update -
Bad news, Google has changed their CTS qualification requirements on firmware so the .24 release is delayed for a couple of days. We have asked for an exception to release earlier, especially since it already passed qualification testing.
5/16/2012 Update -
The .24 release should go to FOTA very shortly.
5/22/2012 Update -
Sorry for the delay, tried not to die from pneumonia last week after a relapse. I will start answering general questions again today and forwarding CSR events to the Service Team. Good news is that we have hired a full time employee to assist our Tablet owners in the Android centric forums. His name is Tien Phan and he is available here under the user name Asus_USA. He is part of our new Customer Loyalty Group and will be taking over forum coverage and assisting our valued customers. I will still be around, especially to handle technical problems and coordinate with Engineering until Tien is completely up to speed. However, as always, if you run into a problem that is not solved by our Service Group please feel free to contact me.
5/31/2012 Update -
We are working on another release with updated code from NV/Google. I will be in Taiwan next week to discuss this version and once a beta is available we will release it to a small group of testers. So far, this updated code based has worked extremely well on the TF201/TF300 in beta testing. As soon as I have an update it will be posted.
6/11/2012 Update -
We received additional code enhancements from NV/Google while I was in Taiwan last week. We will create a beta update shortly for testing and hopefully the next firmware update will occur in the next two weeks. I/O and Thread priority changes are the top two items and will address ANR and Sleep issues, however, still testing various application loads as some applications do not want to play nice with thread overrides.
7/4/2012 Update -
New .27 Firmware is released and addresses browser and ANR problems among other items. As always, after the update is complete, clear browser and system caches, shutdown and then power up.14Hello TF101 users
If you are still experiencing SOD or RR after updating to .24, please send me a PM. When sending a PM, please provide some brief details along with the following information:
- SOD, random reboots, or both.
- Observed uptime before issues or how often they happen.
- If you are stock, rooted, flashed ect.
- best contact e-mail
Also, if you have a bug report you'd like to submit, I am working on gathering them up to send to HQ for analysis. Please PM me also.
Tien10
well that's nice and consistent....
For my part, when the tablet is alive and working, .27 seems good and stable and better than .21 and .24. No crashes, just one case where Dolphin stopped responding - and that was a failure on the wireless signal where I was using the tablet.
I do, however, have an issue regarding the device sleeping. I can only wake the device by a long-press of the power switch and it does seem to drain the battery excessively too.
Asus & Gary: I'm sorry about your impressions about people's responses here but you are largely the cause of this harsh language by your lack of communication. There are two activities that are crucial to the management of any problem - be it IT related or not. One activity is obviously the activity needed to fix the problem and you clearly have people working on this, albeit without apparently considering a roll back to Honeycomb.
And then there is the communication. This in many ways is the more crucial activity and it is here that you have been weaker than you should have been. You may disagree, but let me put this in perspective:
Ask yourselves
- How much communication has there been about your new products?
- How much communication has there been about this issue?
- What channels do you use to communicate to your NEW customers
- What channels have you used to communicate to your TF101 users?
I follow you on Twitter, Facebook and here. I look at your Asus web site, I am a 'VIP' on your system. The communication about this issue has been woeful. This is why you now have angry users, not because you've not fixed it, but because you seem to be ignoring it - and therefore us.
Let's look at the news on your Global site today:
Really? In tune? Come on. Prove to me, prove to us all that this is true. Give us HC back. Come up with a communication strategy that lets us know what is happening, regularly. Until you do, until you realise that the world is not just made up of 'new sales' but also of 'existing users' who you have already won to your cause. Remember, a bird in the hand is worth two in the bush.ASUS Global said:
Asus. We are all part of the same team here. The ball has been passed back to you, you have an open goal in front of you, do you score? Do you miss? Or do you pass it back to us and give up?
Your call.10
It doesn't, it just shows that they don't have a fscking clue on how their own product works.
This is what happens during an OTA update:
- DMClient writes the dlpkgfile and the commands for recovery in /cache
- DMClient updates the boot parameter partition to force a boot in recovery mode and reboots the system
- the boodloader cold boots the current recovery kernel image from partition SOS
- the recovery kernel image runs init which transfers control to recovery
- recovery picks up the parameter file from /cache, then unpacks and verifies the dlpkgfile
- recovery runs the updater-script which in turns verifies the integrity of the target system (if you modified some key files it will bail out and show the red exclamation mark), applies patches, extracts new files, resets all permissions (that's where you lose root access ), flashes the blob to the staging partition, wipes the Dalvik cache, clears the boot parameter partition and then reboots the system
- the bootloader picks up the blob from the staging partition, verifies its layout and rewrites the partitions specified in its header (for a .21->.24 OTA this means EBT, SOS and LNX - bootloader, recovery and main kernel image)
- the bootloader restarts itself to pick up the new partition layout and/or a new version of itself
- the bootloader cold boots the main kernel image from partition LNX
- the system boots normally up to AndroidRuntime startup, at which point dexopt is started up on all user apps to rebuild the Dalvik cache
- end of the update process
9This thread started under a spirit of cooperation. It had since devolved into one of confrontation. Now we are trying to lift the discourse back to cooperation once again. Change is often hard fought, and the natural tendency of things is to fall and degrade. And, let's face it, the levels of people skills here can vary widely. Let's not give into temptation and regress again now into personal arguments. We need to look forwards and ever upwards, together.
It is, of course, ASUS's responsibility to provide a solution to this problem, and I still expect no less from ASUS. Let that be clear. None of us on XDA caused it, and none of us on XDA can fix it [Nvidia closed source drivers]. Some "solutions" on XDA help mask it, but masking it is not a fix nor does that help the greater non-XDA TF101 ownership at large. It would be morally and ethically reprehensible for ASUS to leave the TF101 ownership in this state - but I still have faith that they will do the right thing. I have faith that their people, Gary Key and Tien Phan, are good men, honorable men, trying to do the right thing to the best of their capabilities and positions. Gary has proven to me, by the speed and content of his last in-thread response, that he does read this thread, and I commend him for that. He has not abandoned this issue, despite the various levels of discourse, and I do trust he will persevere until he ultimately brings us the solution we need.
The major culprit in front of us has been identified: it is the "out of memory" issues being kicked up by Nvidia OpenGL. We need someone within ASUS championing our cause, and that person can only be Gary. However, Gary does not go about this alone. Many of us in this thread are still very willing to cooperate. Gary only needs to tell us what he needs from us, what he needs us to do, who he needs us to call and harass, etc. Please, by all means, use us if we can help at all. All I ask is that we please try our best to reach the solution soon and to pursue it with renewed vigor. We are all getting a little bit restless over this, and the tide can't be held back forever.
