this is not good@gary i hope you reading this. i hope asus will send out a QUICK fix for this
Official ASUS Thread - ICS Update on TF101 (20-Mar-2012)
- Thread starter Gary Key
- Start date
-
- Tags
- tf101 transformer
this is not good@gary i hope you reading this. i hope asus will send out a QUICK fix for this
Ok - since you asked so nicely...
<... time passes ...>
I've run the IP Webcam program for 30 minutes, which was what I was doing before. It's now off, and I'll let the tablet go back to sleep and watch with interest.
I'll report back tomorrow morning if it's still clear and earlier if I get any issues.
Little update on the "defective hardware revision" thing: surprisingly the tech support service didn't answer my questions either (sarcasm self test completed), instead they asked I RMA the damn TF101.
Well, at this point I'll give a shot at it just to make them run out of options for covering up this mess.
Well, at this point I'll give a shot at it just to make them run out of options for covering up this mess.
Well... I went to the store where I bought it and talked to them about this issues we're all having and they insisted in performing a factory reset... Oh what the heck... I told them too anyway. So I kept it without installing anything and in the next day .24 was released.Really?!?!
All that was suggested by Gary was a cold reboot after the firmware update from .21 to .24. See http://www.transformerforums.com/forum/showthread.php?t=21834
Which I did. So far, so good.
>>> Sent from my TF101 (powered with sometimes crappy ICS) using Tapatalk 2
---------- Post added at 10:45 AM ---------- Previous post was at 10:44 AM ----------
Well, yes... But since my TF101 is about 1 month old I want it working out-of-the box without any workaround...
Just a suggestion, if more of us can start logging the kernel reboots maybe we could start posting videos of the logs on Youtube.
That should get some attention in the right places.
Plus, if we all know what to look for, we may find that there are more triggers than you've already seen.
More information is what may be needed to pin this thing down.
Thanks are due to you, jtrotsky, knoxploration and many others for sticking with this.
I was thinking something along the lines of a kernel dump upload service on App Engine, so that each user can upload its own panic/watchdog/reboot dump and choose if they want to make them publicly available.
Again, it's not even in "pre-planning" phase, just an idea floating around in my brain
Definitely, the only reasonable thing for Asus to do here is giving us the option to revert to HC (for those who need a stable system) and at the same time giving logdog to all users who want to run the "extended beta test" for ICS.
You're welcome
---EDIT---
Houston, we have a problem!
I'm running the CTS suite and it reported 3 failures in the general app API area (tests are still running, I'll have more details when the whole suite has finished running). On top of that, the home screen went totally berserk as soon as the tests started and after those 3 failures the screen went completely black even though I explicitly disabled sleep mode.
Keep it classy, Asus...
Last edited:
So, if any of us were to find and install the LogDog tool
How should we configure it to give consistent useful results, it's presumably much better if we're all reporting with the same settings to avoid confusion?
I notice that there's the ability to add a note to the archive, what should be the standard entry here, just machine type (e.g. B60....) or more detail required?
If it looks like we're going to do this, let's do it properly folks
@sbiriguda, your suggestion of a centralised db sounds like a good idea, if you give us instructions based on what you've discovered so far we can get started as soon as we're ready.
I've just had 2 browser crashes trying to view this thread directly from my TF (stock and Stock+ browsers, just dumped me back to the home screen)
How should we configure it to give consistent useful results, it's presumably much better if we're all reporting with the same settings to avoid confusion?
I notice that there's the ability to add a note to the archive, what should be the standard entry here, just machine type (e.g. B60....) or more detail required?
If it looks like we're going to do this, let's do it properly folks
@sbiriguda, your suggestion of a centralised db sounds like a good idea, if you give us instructions based on what you've discovered so far we can get started as soon as we're ready.
I've just had 2 browser crashes trying to view this thread directly from my TF (stock and Stock+ browsers, just dumped me back to the home screen)
FYI - Another app that seems to cause issues is Pinball Arcade. It causes all sorts of issues (display issues when installing tables, the app itself crashes often and it has even initiated a "pseudo-reboot" (where the uptime doesn't get reset) more than once - might be a good app to use to try and break something and check out the logs...
Again, it may not be the apps fault, but it is, at the very least, highlighting some issue within the OS (for me at least)! I have purchased all of the tables and I see lots of issues while the tables are downloading....
Sent from my Transformer TF101 using Tapatalk 2
Would appreciate that
+1
I'd be willing to install logdog and use it since I'm back to mostly stock, just rooted now. Figured I'd see how the .24 fix works out for me. Of course with over 500 apps I'm sure I can find a problem maker or two.
Sent from my Transformer TF101 using Xparent Purple Tapatalk 2
I had the same thing twice yesterday. This us a new issue for me. It's quite maddening, in that the wifi controls were unresponsive for at least 5 minutes, then it suddenly started flashing through changes that looked like it was playing catch up with every button press I had done. After that, it was back to normal.
This is just about all I can take with this update. I'm going to step up my efforts to try to find a way completely back to HC.
Sent from my Galaxy Nexus using Tapatalk 2
Last edited:
I've just had 2 browser crashes trying to view this thread directly from my TF (stock and Stock+ browsers, just dumped me back to the home screen)
Hmm. I have had two similar crashes on .21 and I'm completing this post on .24. If this works, then things are better for me at least.
PS - tablet still OK from using camera this morning..... (/crosses fingers)
I am digging the System Bar Lock on this and I have noticed the Browser compiling excessive amounts of /data also. So much so that I cleared it out and restored my bookmarks via TB. I hate excessive /data.
I'll do the Logdog if anyone wants to shoot it to me. I aready have Catlog running but for consistency I'll switch species. As of this morning, I haven't had any RR or SODs but I know the check is in the mail in that one.
Some background:
Rooted
I have frozen ALL Asus bloat including the Tegra Games app (correlation to the tegra_pm_suspend?)
I have GMail but not the stock Email or Email Exchange (I don't use or need it),
SetCPU running and changed governer to interactive (VICW- I used to have the lowest frequency set to 312 but as of last night, I lowered it back to 216 to see what happens. I remember you and I working on this when ICS first came out)
Use stock browser, Dolphin and Onskreen
Also running Cache Cleanrer NG, Reboot Logger, CPUspy, Catlog
I watched and have been watching entire baseball games on MLB At-Bat since the season began and have not had one time where it froze or locked up or rebooted on me (although I will now probably bc I typed this out).
On .17 and .21 I have only had a handful of RR (maybe 10-15 the whole time according to Reboot Logger) and 2 SODs (which really sucked btw). I have about 70-80 user apps installed and have frozen the bloat since the beginning <--this is making me think one of the Asus apps is triggering the panic but not sure. If anyone wants any more info, just let me know.
My B70 has been stable since .24, except for a couple cases where I had to wait for a few seconds for mysterious pauses (only 2 times) and the 'this app is not responding, do you want to close' message showed up. I did the complicated cold boot/update/multi-wipe process mentioned above. Since I had wiped a few weeks back and didn't have much other than e-mail and wi-fi to set up from scratch I had nothing to lose by being extra cautious. I'm near 48 hours uptime. I wasn't able to check the wi-fi network change problem from .21 because the TF didn't know about the work wi-fi until I got there and set it up. Next week.
One thing to comment on is that battery life doesn't seem that much improved. In 12 hours of sleeping last night the dock battery drained about 20%. That seems higher than HC used to do. I suppose I should install one of those sleep monitoring apps to see how much it is sleeping.
Rob
One thing to comment on is that battery life doesn't seem that much improved. In 12 hours of sleeping last night the dock battery drained about 20%. That seems higher than HC used to do. I suppose I should install one of those sleep monitoring apps to see how much it is sleeping.
Rob
I just thought I would throw in another data point. I flashed .24 and am about to hit 24 hours of uptime, with 14 hours of sleep. I'm running a rooted, deodexed, mostly stock rom, stock kernel. I only had a few reboots in .21, so at best, I am mildly affected by the RR/SOD issue. I'm not trying to rub it in, but just wanted people with RR/SOD issues to know that something better is possible. Good luck and I hope it gets sorted out for all of us.
sent from my transformer
sent from my transformer
Last edited:
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.
