yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer General] knoxploration:
I guess this post was tempting fate, really. Just came upstairs to find my tablet had locked up (sleep of death), had to hold the power button in for ten seconds or so to restart.

Interesting. I was only going by what I'd read elsewhere, which suggested us unrooted folks couldn't get anything worthwhile logged.

I'm still of the verdict that there's little point in providing logs, since my understanding is that no third party can fix this until Asus releases their source (which they're unlikely to do while their build is so embarrassingly unstable.) However, I'll look into CatLog when I have a minute.
[Eee Pad Transformer General] oldcpu:
More thoughts on log files

I don't share that view. My view is the more detail Asus are provided as to the problem, the higher the probability they will come up with an immediate fix. Plus there likely will be alternative 3rd party packages that one can risk installing (not what I nominally would recommend nor do, but I do note there are already kernel updates ...). But IMHO the bottom line is the more technical detail that Asus are provided the higher the probability of a quick fix.

I have also discovered Acer Icona Tablet and a Toshiba Tablet with ICS are experiencing reboot/power management problems. I do not know if this is more often, as as often, or less often, than that of the Transformer.

Thanks. I am also saying that there are other programs for non-rooted user other than CatLog that capture log files. A quick search in the app store will confirm that comment of mine. At this stage of my learning process I do not know which is the best, nor do I know (yet) the optimal settings.
[Eee Pad Transformer General] knoxploration:
If Asus aren't able to replicate a problem this common themselves and determine the cause without end-user assistance, then frankly, they shouldn't be in the Android business.

As far as I'm aware, the third-party ROMs are all either based on existing ROMs with pieces pulled out of other ROMs and tacked on, or based on the stock ICS source with pieces pulled out of other ROMs and tacked on. Either way, neither can "fix" the problem; they either have it, or they don't. Nobody's actually fixing them, because they don't have the source from Asus to troubleshoot, fix, and recompile.

I could be wrong on that, but I don't believe I am.
[Eee Pad Transformer General] oldcpu:
I could not disagree more

I do not agree with that statement.

They are using Android which is an implementation of the free open source GNU/Linux operating system, which has been modified by Google for Tablets.

Creating an operating system is not a trivial matter and without a doubt, the capability to create an operating system is WELL beyond the capability of Asus. Very very far beyond.

In fact, NO Tablet supplier has the capability to create, maintain, and debug an operating system for a computer by themselves. No Tablet supplier. Even Google need to rely on the open source GNU/Linux community in order to help them with Android. YES this IS that large and it IS that complex.

Frankly, IMHO if an organization like Asus wish to solve this, IMHO they need to (1) ask Google for assistance, and (2) reach out to the user community for help.

IMHO that is the ONLY way this will be solved

Clearly we are polarized on completely different view points. Mine is based on being a GNU/Linux user for 12 years, and having seen hundreds of major problems that could only be solved by an all-team effort, and not by one GNU/Linux distribution.
[Eee Pad Transformer General] Vintage76:
D Flashed ICS a day or so ago and it has been fantastic. Much quicker and slicker....The thing that has pleased me the most is the fact that typing is no longer an issue...the whole spelling suggestion part of it is so much better. The scroll bit is better, a lot more accurate and the magnifier helps.

The only problem I had was the usb issue that is common place and maxthon browser playing up abit. I installed the update which has fixed usb woes. However the maxthon browser persists...(The browser stays blank and you need to touch the screen to make it respond and load properly).

Very happy with ICS so far.
[Eee Pad Transformer General] DaveBG:
I just want to see if i have it. I can make a backup of my data and will decide but unfortunately I have no choice... No update found for my device every day same story...
[Eee Pad Transformer General] knoxploration:
And how does that all-team effort work, when Asus aren't releasing the source, and are shutting out the team? It doesn't.

Also, you seem to be giving Asus credit for a vast project, but in actual fact what they've done is take an existing operating system, plug in a few off-the-shelf drivers and rebranded apps, and code a few very small (compared to the size of the OS) pieces themselves. And yet despite telling us Google were approving the code (remember that two month delay?), we have a nightmare that can barely manage to go a day without crashing.

They have the tablets on hand. They designed them. They know them better than anybody else. They will have no problems replicating the problem, and can log it in as much detail as they like.

If they can't fix it with all that info on hand, god help us.

EDIT: Belay that. Asus have finally pulled their fingers out, and released the source.

http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#download

Now perhaps the community can do what Asus clearly can't, and fix this problem...
[Eee Pad Transformer General] oldcpu:
As you noted later Asus DID release the source.

Still, the issue of the source code is not necessary if we give Asus details on the crash. You do not need the source code for that.

I have helped developers in many GNU/Linux problems where I did not look at the source code. YES, that IS possible. I provided log information with symptoms. I provided hardware and configuration information. And ARMED with that information from me and others, they were able to implement a fix that was not otherwise easy.

No, you give them credit for a vast project. I do not.

Just the contrary. I stated GNU/Linux is a project too vast for Asus to be the producer of an OS.

You are assuming the problem exists with an Asus implementation. What if the problem is upstream ? (I assume you know what that means). If it is upstream, then Asus may not be able to solve this without community help.

And EVEN if the problem is not upstream, but is at Asus level, the simple fact is many users do NOT have this problem. One user notes they have 15 TF-101 Tablets and not one has the problem. Not one. How can that be ? What that tells me if one adopts a certain systemic approach the problem is not there. What if Asus do not see the problem.

It makes infinitely more sense to provide logs as opposed to grumble (which some users are doing).

What is the hangup about providing technical support (via log files) so to help YOUR tablet work better ? To help MY Tablet work better ? To help OTHERS Tablet work better ? What is the hangup about us providing log files to make this more likely to happen ?

Listen - I don't want to debate this. I am sure you feel the same. We both have better things to do. I won't reply to further posts on this sort of debate. I will continue to ask for log files until mods ask me to stop.
[Eee Pad Transformer General] Thiesen:
Here is one log done with CatLog. This is the only log I have so far of any RR/SoD. I am in the process of recording new logs though (it could take a while and be really big one). It's an recording of everything in verbose mode.
[Eee Pad Transformer General] oldcpu:
Thanks for log file

Thanks for the log file. I note just before a reboot ( ? ) ...

03-19 13:55:58.910 D/TaskWidgetDataUtils( 1080): getWidgetData()
03-19 13:56:07.320 D/PowerManagerService( 170): @PowerManagement: Auto-dim timeout
03-19 13:56:07.320 D/PowerManagerService( 170): @PowerManagement: Screen Bright {true -> false}
03-19 13:56:14.329 D/PowerManagerService( 170): @PowerManagement: Auto-sleep timeout
03-19 13:56:14.350 I/power ( 170): *** set_screen_state 0
03-19 13:56:14.350 D/PowerManagerService( 170): @PowerManagement: Screen turned off mScreenOnTime=415608ms Battery<C,V>: <100,8>
03-19 13:56:14.350 D/PowerManagerService( 170): @PowerManagement: Acquire UWL 'sleep_broadcast' flags [partial] refcount=1
03-19 13:56:14.350 D/AlarmManager( 170): Added alarm Alarm{41890a00 type 2 android} type:ELAPSED_REALTIME_WAKEUP when: After 0h:0m:4.0s
03-19 13:56:14.390 D/PowerManagerService( 170): @PowerManagement: sending ordered bcast for ACTION_SCREEN_OFF
03-19 13:56:14.400 D/EthernetService( 170): stopPolling
03-19 13:56:14.400 D/Ethernet( 170): Screen Off
03-19 13:56:14.410 D/AlarmManager( 170): Added alarm Alarm{41894ea8 type 0 android} type:RTC_WAKEUP when: At 2012-03-19 14:09
03-19 13:56:14.430 D/SurfaceFlinger( 89): About to give-up screen, flinger = 0x28a958
03-19 13:56:14.430 D/AlarmManager( 170): Added alarm Alarm{418f3158 type 2 com.google.android.gsf} type:ELAPSED_REALTIME_WAKEUP when: After 0h:0m:29.0s
03-19 13:56:14.440 D/AlarmManager( 170): Added alarm Alarm{418f4140 type 2 com.google.android.apps.maps} type:ELAPSED_REALTIME_WAKEUP when: After 2h:54m:35.0s
03-19 13:56:14.540 D/PowerManagerService( 170): @PowerManagement: Release UWL 'sleep_broadcast' flags [partial] refcount=0
03-19 13:56:14.550 D/FlexLabs( 1124): Widget count: 2
03-19 13:56:19.769 D/AlarmManager( 170): Triggered Alarm 41890a00 ELAPSED_REALTIME_WAKEUP IntentSender{412357d0: PendingIntentRecord{41890960 android broadcastIntent}}
03-19 13:56:44.810 D/AlarmManager( 170): Triggered Alarm 418f3158 ELAPSED_REALTIME_WAKEUP IntentSender{41907090: PendingIntentRecord{418f30b8 com.google.android.gsf broadcastIntent}}
03-19 13:56:44.920 D/dalvikvm( 170): GC_EXPLICIT freed 1329K, 10% free 13810K/15239K, paused 15ms+7ms
03-19 13:56:44.940 D/dalvikvm( 1080): GC_CONCURRENT freed 521K, 9% free 6723K/7367K, paused 2ms+2ms
03-19 13:56:45.370 D/TaskWidgetDataUtils( 1080): In trigger refresh list utils
03-19 13:56:45.370 D/TaskWidgetDataUtils( 1080): getWidgetData()
03-19 13:57:01.310 D/FlexLabs( 1124): Widget count: 2
03-19 13:57:01.410 V/AddonsDetectorAccessibilityService( 539): Cached event
03-19 13:57:01.410 V/AddonsDetectorAccessibilityService( 539): Storing notification info... (android)

and looking at that I don't see anything obvious to me. Was your Transformer was 'sleeping' at the time? Each of the 4 reboots I have seen (since installing ICS ~6 days ago) my Transformer was 'sleeping'. I have yet to have one while I am actively doing something on it.

But 4 reboots (on my part) is a very small sample.
[Eee Pad Transformer General] Thiesen:
Yes it was deep sleeping set to turn wifi off. It was my first Sleep of Death (it didn't get stuck in any bootloop, I had to press the powerbutton for atleast 10 sec to get it to boot up again)
[Eee Pad Transformer General] knoxploration:
You assume Asus are listening. Fairly clearly, they aren't. They've publicly stated in the media that there is no reboot problem. They've not admitted since that there is one. They've completely ignored requests for help from users. There is nothing at all to suggest that Asus will take one word anybody says, and do anything with that.

I'm not a child, I'm well versed in technology, thanks very much. The problem is not upstream, or it wouldn't be restricted solely to Asus' products.

No, the fact is that other users claim not to have the problem (and thus far, I've not seen anybody claim to have multiple tablets and not see the problem, certainly not 15. I can't begin to imagine how much time you'd have to invest to confirm 15 tablets not to have the problem.)

Occam's Razor: Simplest explanation is probably right. Simplest explanation is that these users probably *do* experience random reboots, they just haven't noticed.

I didn't say we shouldn't do it. I said (and I was most likely right, although we'll never know now) that while the source was unavailable, there was very little chance that providing logs would result in a fix.

Now that the source is available, that's different, something I immediately acknowledged on finding they'd finally released it. End users will likely be the source of the fix, not Asus. If Asus was capable of fixing it on any kind of reasonable schedule, frankly, they'd never have released the firmware this fundamentally flawed in the first place.

I agree. I won't be replying from this point onwards either.
[Eee Pad Transformer General] oldcpu:
Please post log files - not only Asus may be impacted

just a note asking users to post their log files.

Already surfing on the error messages I have stumbled across two ICS users: an Acer Iconia Tablet user with a similar problem and a Toshiba Tablet user with a similar problem.
[Eee Pad Transformer General] ishida:
Updated on 19MAR, it has been work well since then, no restart itself, not stuck at the booting, no sleep to death, the battery problem solve, the sound is fine now it is as loud as before.. good good! but somehow the software doesnt work well with the hardware and also the wifi not as strong as before... beside that everything is fine.... and I am from Vietnam!
[Eee Pad Transformer General] horndroid:
Nope. You are wrong. Here's proof

A lot of people don't experience random reboots.
[Eee Pad Transformer General] randomjoy:
I just looked at mine, its claiming an up time of 11 hours right now but I have had these problems twice this afternoon, once it rebooted, and once it got stuck looking like a brick..... This might not make sense but that's what I'm seeing...

Maybe a reboot doesn't count as the device ever being off, also one thing I have noticed is that when it goes into that hard to turn on state, it is not actually off, the screen is just black. I think this because a) I can still charge my cellphone with the tablet when it appears to stuck off and b) when I hook it up to my tv with the hdmi port, the tv receives a signal, and the tv screen shows a black screen.
[Eee Pad Transformer General] oldcpu:
Asus involvment

For those who may have not noticed, an Asus rep has started a thread here, and is offering to provide a logging application to assist in the investigation: http://xdaforums.com/showthread.php?t=1556914 ... one first sends a PM to the Asus rep to volunteer, and then after one obtains the log with the Asus provided app, one then is to email them the logs (where email address is provided).
[Eee Pad Transformer General] nickola:
Hello,

I've not encountered any problem yet with ICS, but I have something to blame about it.

This morning, I connected my TF101 to my Wifi network and immediately appeared a Download icon is the notification area, stating a new firmware was downloading.

I have not searched for firmware updates through Parameters, my TF101 was a HC 3.2.1. I've had no opportunity to refuse the upgrade to ICS, which I would have, considering the number of people having issues, it seems the system is just not stable enough at the moment to my liking, I would have waited for some time...

Now, I have ICS, and just pray not to encounter issues.

Is it an habit to force upgrades ? Am I the only one is this case ?

Thanks

Nickola
[Eee Pad Transformer General] knoxploration:
All Transformers check for updates occasionally, and all allow you to postpone the update three times before installation is forced (unless, that is, you know how to prevent it altogether.)
[Eee Pad Transformer General] nickola:
Yes, I found it too late ...

Damn why are they forcing the update.

I've had some app crashes (Angry birds space seem pretty unstable on TFs), but I'll only blame the system for the 2 random reboots I encountered in the last 2 days.

Anyway, how can I prevent the TF from "auto updating", as I'm going to buy a second (for myself, the other one's the wife's one) ?

Thanks

Nickola
[Eee Pad Transformer General] Adonis4g:
Same reboot issue plus not able to cold boot

[QUOTE

I have this same boot problem while the tablet is sleeping. Sometimes i will go to the tablet and the battery will be totally drained .Not from use but from rebooting over and over. Sometimes the onky thing to do is to hold the power button in for a long time to restart it. Another issue is that i can no longer do a cold reboot by holding in the power and volume up keys at the same time. Asus informed me in the past that a cold reboot sometimes fixes some bugs but i cant even do that anymore. I have contacted Asus about these issues but have yet to hear a response.

=knoxploration;23816370]You assume Asus are listening. Fairly clearly, they aren't. They've publicly stated in the media that there is no reboot problem. They've not admitted since that there is one. They've completely ignored requests for help from users. There is nothing at all to suggest that Asus will take one word anybody says, and do anything with that.

I'm not a child, I'm well versed in technology, thanks very much. The problem is not upstream, or it wouldn't be restricted solely to Asus' products.

No, the fact is that other users claim not to have the problem (and thus far, I've not seen anybody claim to have multiple tablets and not see the problem, certainly not 15. I can't begin to imagine how much time you'd have to invest to confirm 15 tablets not to have the problem.)

Occam's Razor: Simplest explanation is probably right. Simplest explanation is that these users probably *do* experience random reboots, they just haven't noticed.

I didn't say we shouldn't do it. I said (and I was most likely right, although we'll never know now) that while the source was unavailable, there was very little chance that providing logs would result in a fix.

Now that the source is available, that's different, something I immediately acknowledged on finding they'd finally released it. End users will likely be the source of the fix, not Asus. If Asus was capable of fixing it on any kind of reasonable schedule, frankly, they'd never have released the firmware this fundamentally flawed in the first place.

I agree. I won't be replying from this point onwards either.[/QUOTE]
[Eee Pad Transformer General] knoxploration:
For anybody trying to read the previous post, which accidentally mangled the quoting and placed the new post inside a quote of my post, above is what Adonis4g actually meant to post.
[Eee Pad Transformer General] tnw513:
Asus Italia cit: Today we updated the Prime and April 6 will update TF101G. We count the first to release a new update for TF101.

You can view this on Asus Italia Official page on facebook...

Silvio
[Eee Pad Transformer General] oldcpu:
Those stating the problem is restricted to Asus appear to me have not checked much, as I have noted cases of two other tablets with ICS with symptoms that could be similiar. Ergo this could indeed be upstream and we have users who prefer to rant and declare credible possibilities (and indeed what could be likelihoods) as the fault of Asus when indeed there is a reasonable probability that Asus have an upstream problem on their hands., are in my view graduating from being understandably frustrated users to being no no more than anti-Asus trolls whoshould be labelled as such (trolls) as they continue to spread disinformation to deliberately make it more difficult to sort the problem.
[Eee Pad Transformer General] ishida:
I think at some point Asus needs to release another update again! my tablet somewhat not stable now! it restarted automatically, or sleep to death or stuck while booting! hmmmm what is so wrong with ICS on this tablet!
[Eee Pad Transformer General] oldcpu:
Try some of the work arounds

Some users are claiming that the WAIT_LOCK work around (documented in this thread http://xdaforums.com/showthread.php?t=1567795 ) works for some. Others claim doing a factory restore (do I have that worded right ? ) coupled with a very cautions fresh install of selected apps helps and works for them/some.

Some users who have rolled back to Honeycomb note they still have the problem, suggesting to me that either (1) problem was present but not noticed with Honeycomb (possibly because less severe) , or (2) applications (including stock ones) that were updated for ICS when completely re-installed are causing some problems for Honeycomb. Obviously there could also be other reasons.

In my case I don't want to apply these sort of 'work arounds' as I am trying to cause the problem to appear (so I can document it) and I am finding it not so easy to reproduce. I find if I leave my B7O TF101 powered 24/7, then I can obtain occurrences of about one/day.

I find if I switch my Transformer OFF for a short time a few times/day, I can not see the problems. Before I started trying to reproduce the problem, I would switch my transformer OFF for 20 minutes (when walking to work) and then about 10 hours later for 20 minutes (when walking home from work) and then for about 5 minutes just before going to bed at night and prior to plug the Transformer 'in' for an all night charge. That is how I operated my transformer with Honeycomb 3.2.1 and when I initially adopted that with ICS (4.0.3) I could not see the problems. I had no ICS problems with my nominal switch OFF 3x per-day strategy. I had to switch to a 24/7 strategy to reproduce the problems. And I am still trying to reproduce/document the problem with ICS.

... so if you are not trying to reproduce the problem (like myself) you could try some of the work arounds.

Edit - and yes, I too am hoping that Asus can work with their upstream suppliers to apply a fix either upstream, or at the Asus ICS packaging level.
[Eee Pad Transformer General] tomassan:
Spontaneous restart, log messages

My TF101 rebooted this morning, and I had logcat running. While I have minor knowledge about the workings of android, I find the following entries interesting:

D/AlarmManager( 165): Added alarm Alarm{416dfdd0 type 2 com.google.android.apps.maps} type:ELAPSED_REALTIME_WAKEUP when: After 0h:14m:59.0s repeatInterval: 0h:15m:0.0s

Now, there are MANY of these added alarms, but no corresponding

'Removed alarm' entries. Now if the process com.google.android.apps.maps adds a lot of repeated alarms, wouldn't that fill up some queue somewhere?

The log ends with:

D/AlarmManager( 165): Triggered Alarm 416dfdd0 ELAPSED_REALTIME_WAKEUP IntentSender{416cc6d0: PendingIntentRecord{4164cfd8 com.google.android.apps.maps startService}}

W/ThrottleService( 165): unable to find stats for iface rmnet0

I have set up logcat to save every 10 messages for better resolution, perhaps I should set it even lower to catch the last events prior to the reboot?
[Eee Pad Transformer General] Bloodimirgr:
Installed any app recently before the reboots or just happened?
[Eee Pad Transformer General] DaveBG:
Still no update for me.

Yet i still do not have the ICS update. I know some users have problems but I at least would like to see it available... :mad:
[Eee Pad Transformer General] bgl:
oh wow i didn't know this :(

I wasn't planning on upgrading to ICS cuz of the issues reported here but i have no choice? I'm supposed to get my TF101 today. No workaround to stop this or tool?
[Eee Pad Transformer General] jab0321:
Just got a notification to update the Tegra Zone app on my tf101. Said it included bug fixes and the default update notification is turned off. I updated it and did a cold boot and so far the screen on my tf does not turn on and off on its own anymore. Might be too soon to see if this is the reason but I will keep everyone posted.

I have had good luck with the Auto Airplane app from DON, but I turned it off to see if this update fixes anything.
[Eee Pad Transformer General] knoxploration:
There's a workaround; I haven't done it but I believe it involves occasionally locating and deleting the update package before it is installed. Forum search will tell you for sure.

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

Probably unrelated, since TegraZone is just an app, not a part of the OS. They most likely just mean fixing bugs in the TegraZone app itself.
[Eee Pad Transformer General] anarox:
Holy smokes, just uppgrade to ics, its not as bad as we make it out to be.Honeycomb is a worse os than ics. ICS is an amazing update, they remade android to something that is faster, better and more beautiful.