Official ASUS Thread - ICS Update on TF101 (20-Mar-2012)

Search This thread

knoxploration

Senior Member
Apr 23, 2011
3,612
658
Actually, Gary has now updated the first post and he is saying that it is in fact, Google who changed the qualification requirements, hence the delay.

This is getting to the point of ridiculousness. :rolleyes:

On the plus side, we can hope that the reason Google is changing the standard is because the ludicrous situation whereby updates are being pushed with major, fundamental flaws that aren't fixed multiple months later have finally come to their attention.

I would guess that Google are the only ones with the clout to kick nVidia in line and get them to put out some decent code. Certainly, Asus don't seem able to do so by themselves, and it seems from folks in the know here that nVidia's code is likely the root cause of the worst of our problems.

So, if Google *are* actually aware, maybe they'll put the required pressure on nVidia to start doing their job. I'd imagine a thread of "or we'll start guiding our customers towards competing chipsets and reference designs" would suffice. :p
 

SavCom

Senior Member
Jan 11, 2006
204
31
vastmeridian.blogspot.com
Possibly, yes. Before one of my three reboots I had been experimenting using the TF101 as an IP camera to test out Zoneminder. Before the third reboot I had taken a short movie while surveying a cabinet in a datacentre.

Any further examples? Worth trying a movie again? I'll see and let you know.
Well well. SoD this morning after using the camera again last night (only the front camera, and only for a few minutes) Long-press of the power switch and everything up again, but reboot No. 4 after using the camera last night. I'll repeat again to be sure but maybe (hopefully?) I'll be trying .24 before too long. None the less I'll be trying the camera again afterwards.

Hmm...
 

just lou

Senior Member
Dec 8, 2010
2,086
733
New York
I thought this new. 24 firmware was some kind of joint collaboration between Asus and Google? Now ASUS says Google is holding up signing off on it?


Edit: OK, I'm wrong. It was a collaboration between ASUS and nVidia.
 
Last edited:

tpjets62

Senior Member
Mar 29, 2012
202
35
Albany, NY
www.hytechnet.com
On the plus side, we can hope that the reason Google is changing the standard is because the ludicrous situation whereby updates are being pushed with major, fundamental flaws that aren't fixed multiple months later have finally come to their attention.

I would guess that Google are the only ones with the clout to kick nVidia in line and get them to put out some decent code. Certainly, Asus don't seem able to do so by themselves, and it seems from folks in the know here that nVidia's code is likely the root cause of the worst of our problems.

So, if Google *are* actually aware, maybe they'll put the required pressure on nVidia to start doing their job. I'd imagine a thread of "or we'll start guiding our customers towards competing chipsets and reference designs" would suffice. :p

One can only hope. If they really want to have a long term domination on the market, they have got to raise the bar. Worldwide, they already have the market share, its way past time to polish the product.
 

Starlust

Senior Member
Mar 22, 2012
107
10
*BING!* It happened again. The tablet is sitting right beside me...just finished typing something in, closed the lid and a few seconds later I hear that slight "tick" or "click" sound it makes when starting up. Open the lid and the damn thing is stuck at the Asus screen. And this is the worst part...it can't even crash and reboot properly, it gets "stuck" and kills the battery. What exactly could cause it to get stuck between reboots, requiring a hard reboot to fix? Some cache not being deleted properly?

I literally never get more than 48 hours before this thing crashes or reboots. I really think it's time the tech press got wind of this. Nothing like a little bad press to get things "escalated." I wonder if The Register accepts submissions?
 

Glencairn

Senior Member
Mar 17, 2012
70
4
WiFi issues with ICS

One of the immediately noticeable side effects of ICS for many people was to affect the connection stability and re-connection time to WiFi networks, could this have some bearing?

Does anyone else have a similar experience?

Not sure if I'm welcoming you to my world or I'm joining yours but a definite yes from me for those symptoms :(
 

BigBlueEdge

Senior Member
Apr 6, 2010
69
10
Thanks Rob, I was actually talking about my pre-rooting experience, and suggesting that I was perhaps looking at original performance of HC with rose-tinted glasses. Obviously everybody's experiences are different for reasons that no-one, especially not Asus, understand.

The other thing that I should and will do is mention it on the thread with a title similar to "my TF is still rebooting after returning to HC" to see if any of the other NVflashers have had the same issue. The non-NVflashers definitely did have issues. At the time I tried this, there was general agreement that an NVflash was able, and indeed necessary, to return the TFs to their original state. From what you are saying, NVflashing is not 100% effective? Of course, I had always suspected that a number of my apps did not play nicely with HC, and that has probably muddied the waters.

I have no idea actually how to revert to HC, either with or without NVFLASH. I just know that I've heard of people who reverted to HC after ICS and continued to have problems. Ultimately it is just software (firmware) though, so that MUST be a way to fully revert to a stable HC build. It may not be 'allowed' but there is technically a way .

Rob
 

cheema

Senior Member
Sep 20, 2009
223
49
Portland, OR
> And this is the worst part...it can't even crash and reboot properly, it gets "stuck" and kills the battery.

This is the rub for me. It would be one thing if it kept rebooting like a lunatic, but to add insult to injury it does not even do that successfully. It gets stuck at the boot screen for me and that kills the battery.

Every time you completely discharge the battery, a part of it dies. A healthy battery can only take about 200 or so complete charge cycles. And that is why you are supposed to keep the battery above 30% most of the time. Something that is very difficult to do when Asus firmware is trying to deplete it as fast as possible.

This sleep of death should be renamed to "death of battery". That to me is a more serious offense.
 

rpscott02

Member
Aug 30, 2010
17
3
Cincinnati , OH
I have no idea actually how to revert to HC, either with or without NVFLASH. I just know that I've heard of people who reverted to HC after ICS and continued to have problems. Ultimately it is just software (firmware) though, so that MUST be a way to fully revert to a stable HC build. It may not be 'allowed' but there is technically a way .

Rob

Been running a stable HC for weeks now. No root.

http://xdaforums.com/showthread.php?t=1622628

Sent from my DROID BIONIC using Tapatalk
 

ssl123

Senior Member
Feb 18, 2012
185
48
It's odd. People on here complain that there is too little testing before releases. Now they are complaining about additional testing prior to a release. Please make up your minds.

If the new Google certification requirements finds or has a chance to find something that was previously missed, the delay is totally worth it.

It's not like the old way ASUS handled the firmware releases was working.
 
  • Like
Reactions: Taomyn and vicw

BigBlueEdge

Senior Member
Apr 6, 2010
69
10
I've followed this thread from day one, and tried some of the suggestions.

The ONLY thing that makes any difference for me is the above, as I've said before.

3 days ago I closed my TF without turning of the WiFi and got ready to go to bed.

About 20 minutes later, as the TF went into deep sleep, I noticed a glow from the screen as I turned off the lights.

I opened the TF a crack and found it was in a boot loop, if I had left it I would have found two totally flat batteries the next morning.

I held the power button, rebooted, turned off the WiFi manually and closed the lid.

The TF has been up since then with about 25% loss of dock battery, no reboots.

Somebody noted earlier that the network stays up even when WiFi off is selected and continues collecting emails for about 20 mins.

I'm convinced that MY problem at least is something to do with WiFi drivers or network protocols (lost IP addresses or something).

One of the immediately noticeable side effects of ICS for many people was to affect the connection stability and re-connection time to WiFi networks, could this have some bearing?

Does anyone else have a similar experience?

Since the .21 update almost the only time my TF reboots is when entering or leaving wi-fi network ranges. I was able to avoid that this morning by turning wi-fi off before leaving the house and back on once I was at work. I think there was only one or two times that it has done a RR that isn't directly related to wi-fi. Battery usage is still more intense with ICS than HC though, but not as bad as before .21.

Rob

---------- Post added at 01:41 PM ---------- Previous post was at 01:39 PM ----------


Did you use method #3? Do you have a B70 serial number?

Rob
 

rwniel

Member
Mar 1, 2011
46
11
I'm a little confused....

is 9.2.1.24 the same as 9.2.2.4 ?
9.2.2.4 is part of a separate 'fork' of firmware update versions specific to the built-in SIM slot, mobile enabled TF101G model. Whereas 9.2.1.24 relates specifically to the wi-fi only TF101. While you can imagine the firmware does share a large number of similarities, they're being developed separately (with the actual releases also on a different time-frame). So you can't draw any conclusions from those numbers themselves.

Robert
 
Last edited:

gkillerx

Senior Member
Mar 22, 2009
1,102
295
9.2.2.4 is part of a separate 'fork' of firmware update versions specific to the 3G enabled TF101G model. Whereas 9.2.1.24 relates specifically to the wi-fi only TF101. While you can imagine they share a large number of similarities, they're being developed separately. So you can't draw any conclusions from those numbers themselves.

Robert
Aha funny that 9.2.2.4 already released is then, on the ASUS site.
 
May 15, 2012
5
0
I got an update today...

Today I woke up to find my TF101 with a notification in the tray:
Asus System Firmware Update Service
New system firmware update available, press to upgrade.
I didn't feel lucky. I didn't press.

After a while I got the postpone notice in full screen. Postponed 1 day, turned off TF101 for a while, just in case.

Just wanted to make sure I got some information here first, but no-one was posting any .24 updates. So I waited 6h or so.

Turned it on again. Notification still here. Still don't feel much like pressing it.
Anyone curious?

@knoxploration, @sbiriguda, @jtrosky: comments? advice?
 

rwniel

Member
Mar 1, 2011
46
11
Aha funny that 9.2.2.4 already released is then, on the ASUS site.
I would assume at some point that Asus will release a firmware that updates the TF101G (and which incorporates some of the modifications to .24 on the TF101). But they have tended to follow a later, less frequent update schedule up to now (and as you see also have their own separate version numbers). I assume some TF101G models are also suffering stability/reboot issues (since I would assume they're based on similar hardware). But given the larger numbers of the wi-fi only models we don't end up hearing so much about them. Likewise the SL101 Slider tablet (which seems to be following the same version numbers as the TF101 (i.e. 9.2.1.21 is the latest version with presumably 9.2.1.24 to follow later at some future date).

Robert
 
Last edited:
  • Like
Reactions: gkillerx

vicw

Senior Member
Apr 3, 2011
352
43
It's odd. People on here complain that there is too little testing before releases. Now they are complaining about additional testing prior to a release. Please make up your minds.

If the new Google certification requirements finds or has a chance to find something that was previously missed, the delay is totally worth it.

It's not like the old way ASUS handled the firmware releases was working.

I don't disagree, but I think you should cut us a little slack on this, considering we have been struggling and suffering with this mess since mid February, and this it the third attempt at a promised fix for the problems.

I don't have any problem with the Google certification, except that we were given a hard target date for the release, and I'm not that optimistic that their qualification process will have anything at all to do with the issues we are and have been experiencing.

---------- Post added at 03:22 PM ---------- Previous post was at 03:20 PM ----------

Today I woke up to find my TF101 with a notification in the tray:
Asus System Firmware Update Service
New system firmware update available, press to upgrade.
I didn't feel lucky. I didn't press.

After a while I got the postpone notice in full screen. Postponed 1 day, turned off TF101 for a while, just in case.

Just wanted to make sure I got some information here first, but no-one was posting any .24 updates. So I waited 6h or so.

Turned it on again. Notification still here. Still don't feel much like pressing it.
Anyone curious?

@knoxploration, @sbiriguda, @jtrosky: comments? advice?

Press the Dang button. What could go wrong?
 

knoxploration

Senior Member
Apr 23, 2011
3,612
658
It's odd. People on here complain that there is too little testing before releases. Now they are complaining about additional testing prior to a release. Please make up your minds.

If the new Google certification requirements finds or has a chance to find something that was previously missed, the delay is totally worth it.

It's not like the old way ASUS handled the firmware releases was working.

I think, to be fair, that the reason for the contradiction there is that Asus has basically already given everybody (and indeed, forced everybody to use) a beta release at best, and an alpha release if you're realistic. They've given us no way to downgrade, and since we're already stuck with that poor-quality release, there's no reason for us to want to try the latest beta pronto and see if it's better. (It can hardly be much worse.)

I have a feeling if Asus were to provide both access to a beta, and a way to regress to a known-good Honeycomb build, most people would simply regress and let others do the testing.

And so, we have the somewhat confused response: a belief that Asus should do better testing, *and* a belief that the update should be released ASAP.

---------- Post added at 03:30 PM ---------- Previous post was at 03:29 PM ----------

Today I woke up to find my TF101 with a notification in the tray:
Asus System Firmware Update Service
New system firmware update available, press to upgrade.
I didn't feel lucky. I didn't press.

After a while I got the postpone notice in full screen. Postponed 1 day, turned off TF101 for a while, just in case.

Just wanted to make sure I got some information here first, but no-one was posting any .24 updates. So I waited 6h or so.

Turned it on again. Notification still here. Still don't feel much like pressing it.
Anyone curious?

@knoxploration, @sbiriguda, @jtrosky: comments? advice?

Save the update file before updating, and share it here. I'm sure there are some folks that would want to take a look at it.

I'll be right back; I'm off to check my own tablet.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 85
    Hi,
    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.
    14
    Hello 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.

    Tien
    10
    On the other end of things, my .27 unit is still absolutely fine @stock. Just watched the end of a movie, then played a little bit of a game, then sat and listened to music while I waiting for my laundry to be done, all while using my bluetooth stereo headset. No problems whatsoever.

    I've had it with ICS.

    I am running stock rooted on my B90. I found .24 quite stable with wifi disabled during sleep. I find .27 more unstable and now I am experiencing problems with GMail & Maps where I had none before. No ICS version is as stable as HC was. I want HC back. ICS has no advantage for me that justifies the aggravation.

    I am not interested in custom ROMS or kernals. I've got better things to do than chase that **** around.

    Asus, give me HC back, now!

    Well, that didn't take long. Not only did my husband's TF101 RR once already, but my games have begun to crash like before and yesterday evening, my WiFi cut out requiring a reboot to get it back, just as it has been doing on .24. *sigh* So much for "fixes", Asus. Oh, and the hubby's TF101 also lost sound already, too.

    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:
    ASUS Global said:
    The ASUS Transformer Pad Design Story
    2012/06/25
    Always at the forefront of technology, ASUS has proven with its Transformer Pad family of tablets that they are in tune with what consumers require from their mobile devices. Launched in March 2011, the Eee Pad Transformer showed ASUS' ingenuity and innovative thinking with the Mobile Dock design...
    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. 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
    Gary's note in post #1 says to do it after the update.. Seriously doubt it makes a whit of difference.
    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:
    1. DMClient writes the dlpkgfile and the commands for recovery in /cache
    2. DMClient updates the boot parameter partition to force a boot in recovery mode and reboots the system
    3. the boodloader cold boots the current recovery kernel image from partition SOS
    4. the recovery kernel image runs init which transfers control to recovery
    5. recovery picks up the parameter file from /cache, then unpacks and verifies the dlpkgfile
    6. 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 :rolleyes:), flashes the blob to the staging partition, wipes the Dalvik cache, clears the boot parameter partition and then reboots the system
    7. 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)
    8. the bootloader restarts itself to pick up the new partition layout and/or a new version of itself
    9. the bootloader cold boots the main kernel image from partition LNX
    10. the system boots normally up to AndroidRuntime startup, at which point dexopt is started up on all user apps to rebuild the Dalvik cache
    11. end of the update process :)
    As you can see, a cold boot before or after upgrading is absolutely pointless because both are going to happen anyway (it's the way the bootloader works when switching between recovery and main kernel - it always performs a cold boot).
    9
    This 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.