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

Search This thread
By:
Advanced…
Woody

Woody

Retired Admin - Vacationing in Nanda Parbat
Nov 18, 2010
8,842
16,519
Immersed in Dark Matter
Hi Gary- I am not having the random reboot or battery drain and before I self-rebooted last night, I was at close to 170 hours up time. I am and will stay rooted but if you would like any input from me regarding why I am not getting the reboot, I think it would be as good info as any.

My setup and info is more or less here. If you want any input from me, feel free to shoot me a PM. I won't shoot you one bc your OP says we can't be rooted. I am willing to run the logger if it will run in a rooted device.

Thanks for your help and acknowledgment that there is a problem somewhere.
 
bsoplinger

bsoplinger

Senior Member
Jan 17, 2011
1,477
338
I'd assume that a temp unroot would be good enough for this. Is that correct? I ask because I'd assume most people using XDA are rooted.

I ask because I figure you might need more volunteers after the initial pair of group of volunteers.

Sent from my HTC Flyer P512 using Xparent Purple Tapatalk
 
T

techfan2011

Member
Jul 21, 2011
23
2
Is there an official way to get back to Honeycomb?

I just purchased my Transformer this week, and I have the reboot defect. Wifi connectivity is also unstable at times. Is there any way to downgrade to Honeycomb until the issues with ICS are resolved? This situation can not be fun for the people at ASUS. The software defect is also widespread judging by the activity on the forums. I think an OTA back to a stable release would be greatly appreciated by all of the people experiencing issues.
 
S

steve574

Member
Feb 26, 2012
12
2
Oddly enough the original ics update caused me no issues. No changes between that and 9.2.1.17. After 9.2.1.17 I have had nothing but reboot issues. I'm rooted, though otherwise stock, so I can't participate, but I am interested in a solution.
 
D

darcmasta

Member
Mar 22, 2012
7
0
Awesome that Asus is really help us out. PM-d, but could you guys take a look into native controller support in your ICS update? Not sure if this is related to the Dock or just something in general to ICS but my USB game pad (Xbox 360 controller) doesn't work anymore. Worked fine in Honeycomb but come ICS it stopped working.

Alas, I digress. Thanks for the support and lets try to get to the bottom of the big issue of the reboots.
 
sbiriguda

sbiriguda

Senior Member
Feb 3, 2011
307
155
L'Aquila
Tried to archive a log dump after a serious UI glitch in Play Store, I got back a message saying "FAILED: Archive service unavailable" and no archive was saved in /sdcard/logs.

Anyone noticing the same problem?

--EDIT--
Nevermind, the service started working after a cold reboot.
 
Last edited:
1

1234556789

Senior Member
Aug 20, 2008
372
3
Hello Gary !
my Problem- no usb connection after ics 92117 Update.- and I am not the only one.
usb debugging is on, a second device will connect fine with the same cable+ computer.
I want to downgrade, but no DE rom is avaible.
What can I do ?
Sorry for my poor englisch
gandalf

Transformer 101 no root, no custom rom.
 
Last edited:
C

Cookiekaikai

Member
Jun 22, 2010
34
0
Katy, TX
Thanks Gary. We need this issue addressed as soon as possible. I used to be very proud of my TF101 but now this is getting embarrassing to show the device to a friend only have it reboot for no reason.
 
T

trevh

Senior Member
Oct 21, 2010
65
11
Perth
I volunteered via pm yesterday.
Guess I'm one of the few who just haunts XDA without even rooting ... did all that on a few of my Android phones a year or so ago. And there is so much great stuff to do even without root that I'm having too much fun with that! :)

More concerned now that our TF-101's get secure boot key or bootloader unlock before too much longer. It's a freedombox.org thing, really imho.
 
T

Thiesen

Senior Member
Aug 8, 2009
301
18
Uhm... I was the first to reply to this thread and I also pm'ed Gary shortly thereafter... but I haven't heard a beep from him... have anyone helped Gary by sending logs yet??? Or are you under some kind of NDA???
 
Predseda3D

Predseda3D

Member
May 23, 2009
19
2
I wasnt first one, i was 6 hours later, but my PM to Gary is unread yet.

I will see tomorrow. Maybe Gary accept only peoples from US? I dont know.
 
R

rxnelson

Senior Member
Aug 30, 2011
676
76
I think I pm'ed him by the time you posted. Got the logging utility last night around 11pm EST. No NDA that I am aware of. Haven't sent anything yet. Just got installed tonight. As another user said when you do get it try a test log. Mine failed. Did a cold boot like other user and it worked after that.

Sent from my SGH-I897 using Tapatalk
 
sbiriguda

sbiriguda

Senior Member
Feb 3, 2011
307
155
L'Aquila
Thiesen said:
Uhm... I was the first to reply to this thread and I also pm'ed Gary shortly thereafter... but I haven't heard a beep from him... have anyone helped Gary by sending logs yet??? Or are you under some kind of NDA???
Click to expand...
Click to collapse
There seems to be no NDA whatsoever.

I sent in a couple of log dumps, both related to a serious front camera glitch which might be the result of a borked memory mapping in kernelspace.
"Thanks" to Murphy, no random reboot occurred since I installed the tool, only a couple of ANRs on Angry Birds Space :rolleyes:
 
aureum

aureum

Senior Member
Jul 6, 2008
226
74
42
Szczecin
www.myspace.com
sbiriguda said:
There seems to be no NDA whatsoever.

I sent in a couple of log dumps, both related to a serious front camera glitch which might be the result of a borked memory mapping in kernelspace.
"Thanks" to Murphy, no random reboot occurred since I installed the tool, only a couple of ANRs on Angry Birds Space :rolleyes:
Click to expand...
Click to collapse

Gary send me a logdog yesterday. Like You the murphy law :D after app isntalation don't have bootloops and reboots after 18 hours xD

I did't have to Cold Reboot my TF to use the logdog...
 
J

jtrosky

Senior Member
May 8, 2008
3,901
1,153
It's funny - since I've installed the logger app, I've been HOPING it rebooted and it's been up for over 16 hours now!! I think it's only like the 3rd time I've ever gotten over 16 hours uptime with ICS!

<sigh>
 
K

knoxploration

Senior Member
Apr 23, 2011
3,612
658
Folks, I would guess Gary either has enough people, or is simply busy and hasn't had time to get in touch. Quite a few of us haven't heard back from him, so I wouldn't worry.

FYI Gary, since you say you've been unable to replicate these problems, I've uploaded a video of the boot loop problem for the Eee Pad Transformer TF101 so you can see it's real. (Apologies for the poor focus.)

I would imagine a loop occurring this early in the boot process would have to very significantly narrow down potential areas where the problem could be occurring.

Holding down the power button for approximately ten seconds or so will reboot and load normally. I have *only* seen this loop problem occur after a spontaneous reboot; never after I powered the tablet down manually, or simply ran down the battery completely and restarted after charging.

 
Last edited:
Kadin

Kadin

Senior Member
Sep 23, 2007
706
98
California
Those worrying about not getting a response from Gary, notice the following which is posted at the end of the first thread...

Out of Office until 3/22/2012. Expect delays in answering questions unless email address is provided. Major ICS Update Coming in a Week for the TF201 and another announcement shortly.
Click to expand...
Click to collapse
 
  • Like
Reactions: knoxploration
oldcpu

oldcpu

Senior Member
Dec 17, 2011
173
37
Europe
I'm still waiting for a restart

jtrosky said:
It's funny - since I've installed the logger app, I've been HOPING it rebooted and it's been up for over 16 hours now!!
Click to expand...
Click to collapse

Thats been my experience also. ... Reboots are not happening since (Murphy's Law) but I have no doubt that they will.

I did not see an /sdcard/logs directory, so I created one so as to be ready.
 
You must log in or register to reply here.

Similar threads

T
[INFO] US Retail Availability (for Updates on Preorders and Purchasing)
Replies
11K
Views
1M
B
Bob Smith42
I
  • Poll
[TOOL]"1-Click Transformer Root"-Root/Unroot/cwm/stock rec-TF101(G)/201/300T(G)/SL101
Replies
801
Views
654K
M
mr_fosi
Kasimodo
[HowTo] use 3G Dongle on TF101 *UPDATED 04/13/2012*
Replies
516
Views
262K
M
marcopolo
E
Root ASUS Transformer TF101 On Android 4.0.3 ICS
Replies
14
Views
128K
RLShiftyDoggit
RLShiftyDoggit
samcaplat
How to Root the ASUS Transformer
Replies
299
Views
194K
T
tripranav

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 85
    Gary Key
    Gary Key
    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.
    View
    14
    A
    Asus_USA
    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
    View
    10
    SavCom
    SavCom
    carpe_k9 said:
    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.
    Click to expand...
    Click to collapse

    DeanONH said:
    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!
    Click to expand...
    Click to collapse

    wingzero2085 said:
    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.
    Click to expand...
    Click to collapse

    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...
    Click to expand...
    Click to collapse
    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.
    View
    10
    sbiriguda
    sbiriguda
    vicw said:
    Gary's note in post #1 says to do it after the update.. Seriously doubt it makes a whit of difference.
    Click to expand...
    Click to collapse
    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).
    View
    9
    S
    ssl123
    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.
    View

New posts