yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Q&A, Help & Troubleshooting] seeding11:
Perhaps it is just me, but my TF did reboot every now and then (say, once a week?) when I was using HC Revolver. I can't say for sure that it never rebooted while stock because it used to reboot successfully every time, and I kept it in a drawer back then when not in use, so I wouldn't have been able to see it happen.

The difference for me now (ICS Revolver) is that I have a combination of successful reboots, unsuccessful reboots and SOD, though I have only one of these each week. Stock ICS was just awful for me so it went as soon as Revolver 4.0 appeared! In case someone asks, I always wipe/reformat between each ROM.

So not as bad as some are reporting, but not as reliable as I hope that it will become.
[Eee Pad Transformer Q&A, Help & Troubleshooting] jtrosky:
It certianly is nice to be back on rock solid Revolver 3.11.1 (Honeycomb)! Thanks to whoever said that the NVFlash method worked for them. I originally tried to get back to Honeycomb (Revolver 3.11.1) via CWM (after upgrading to ICS), but the reboot issues persisted, even on Honeycomb, when "downgrading" that way.

However, whatever NVFlash does differently, made the difference. I would also think that this would provide very valuable clues as to what may be causing the issues is ICS as well. If I provided the exact files I used (for both CWM and NVFLash "downgrade"), could someone compare the two methods to see what exactly the NVFlash method does that the CWM doesn't? Again, I would think that this would provide some good troubleshooting information....

Thoughts?

In my opinion, if Asus had provided a way for folks to easily get back to Honeycomb, then this wouldn't be such a "hot topic"!
[Eee Pad Transformer Q&A, Help & Troubleshooting] gee one:
After all that, I flashed back to ICS and the ICS bootloader, and now I just crossed over 4 days of uptime. This is the exact same rom I flashed to go to ICS in the first place. I think the reboots are due to a bad flash/low battery.

sent from my transformer
[Eee Pad Transformer Q&A, Help & Troubleshooting] SiNJiN76:
Has there been any word from Asus about an update?
[Eee Pad Transformer Q&A, Help & Troubleshooting] harshbedi:
Did you wipe the cache and dalvik cache before installing new ROM (No need of using superWipe script..It didn't work for me) I was having the same issue of random clicking/reboots.. I did the factory reset,wiped the cache and wiped the dalvik cache and pheww my transformer was back. After that I flashed the Revolution 3.2.0 ICS Rom and it is working perfectly fine. May be you can try these steps and let us know if it works for you
[Eee Pad Transformer Q&A, Help & Troubleshooting] fear_factory84:
My experience..

I have a tf101 + dock (ww version b60), I was on revolver 3.11.1 with 8.6.6.17 bootloader or something similar (the one that comes with revolver 3g enabler pack, maybe someone can confirm which particular version is) and my tf was running 100% stable over months, with and without dock.

I did a full nandroid backup from cwm (roach 3.2.0.1).

Then I tried some ics roms, like paul's one, and then 9.2.11 ww version. It ran without reboots but for example google maps crashed every time (gl error, segmentation fault).

So after 9.2.1.17 was out I upgraded it using the cwm flashable ww zip (incremental).

I still don't know which bootloader I have since my tf is at home.. I'll update my post, but it will be surely 9.2.1.11 or 9.2.1.17..

Reboots for me appeared mostly using dock but also without (more rare).

So I decided to restore my revolver 3.11.1 backup. Since I know that cwm doesn't backup kernel, I flashed from cwm first revolver 3.11 (full) and then 3.11.1. Then I restored my 3.11.1 backup.

Yesterday I leaved my tf charging with dock, when I came back home I found it bootlooping on asus screen (first asus message), tablet's battery was 4%, and dock battery full.

So reboot happen also for me on honeycomb.

Now I can try several things, but I need some advice:

- flash a full stock 8.6.5.21 ww rom with bootloader, then flash with nvflash cwm recovery, and then reflash revolver 3.11, then 3.11.1 update then restore my 3.11.1 nandroid

- flash a full 9.2.1.17 stock ww rom with 9.2.1.17 bootloader wiping all

- throw my tf away

Regards

update: my bootloader now is 9.2.1.17. today my tf was in sleeping mode, under revolver 3.11.1 in airplane mode. no reboots 3% battery drain for all day. So definitely this is an issue that involves also wifi/gps/bluetooth chip..

update2: I did a full wipe, nvflashed 8.6.5.13 ww, upgraded via official methods to 8.6.5.21, rebooted, upgraded to 9.2.1.17. Now it's running on that, unrooted and fully stock, I reinstalled my apps from market without restoring anything.

Now I want to see how it works, then I'll probably root it if it works without reboots.
[Eee Pad Transformer Q&A, Help & Troubleshooting] xd.bx:
I think the first ICS updated caused overheating issues that led to irreversible damage. I don't think ASUS will ever come with an honest answer though. "Persistent Perfection" => a bit overreaching, maybe ;)
[Eee Pad Transformer Q&A, Help & Troubleshooting] jtrosky:
No, I eventually got back to a stable version of Honeycomb - the key was to use NVFlash to flash a stock HOneycomb image first, then root it, install CWM and install Honeycomb version of Revolver. Back to stable again....

So, it's not irreversible damage to any hardware...
[Eee Pad Transformer Q&A, Help & Troubleshooting] fear_factory84:
After some days running stock 9.2.1.17 non-rooted, I had no reboots until I used my dock.

Now I'm trying to use guevor's test 15 kernel...
[Eee Pad Transformer Q&A, Help & Troubleshooting] warlord234:
I cannot use NVflash due to my B80 TF.

It seem that NVflash can fix the SOD by replacing something.

So I just downgrade my TF to the first HC 3.0.1 stock via CWM which I notice that it even replace the bootloader to the very old one and maybe it replace other problem things.

Then I update it back via OTA to latest ICS 4.0.3. stock with fully charge all time to prevent any bad flash as some people claim it would cause issues.

Let's pray this would fix the SOD!!

EDIT: Still get RR and hang on boot :-(
[Eee Pad Transformer Q&A, Help & Troubleshooting] jtrosky:
Yep - even if you would have stayed on Honeycomb, the reboots would still continue. Like I said, the only way I have found to revert to Honeycomb and also stop the reboots, etc is via NVFlash (which obviously, you can't use). This leads me to believe that the problem has something to do with one of the partitions that doesn't get re-written with CWM... For example, maybe ICS rewrites the swap partition and it's doing it incorrectly so that after you swap so much, boom, the problem happens. I completely made that example up - I have no idea if there even is a swap partition or if ICS would even uses it anyway, but you get the point...
[Eee Pad Transformer Q&A, Help & Troubleshooting] EricBuist:
Starting to loose hope

Hi,

The more I read on forums, the more discouraged I am about this issue. It seems solving this will require a substantial amount of time for me. I can't even get passed the first step consisting of rooting the bulky device. I am just hitting broken links and non-working procedures. Asus is of no help, advising me to call technical support over the phone for more assistance.

My goal is to either get a stable ICS device, or revert this to a stable HC device to be sold back on eBay. I don't want a table stuck to an old version of Android; I will buy an iPad if that is the Android way, sorry, but I cannot sell a faulty device crashing and rebooting randomly. Rooting is not a requirement, since I already have Linux computers on which I can hack as much as I want without being blocked by Android limitations.

Is anyone aware of some people or place in Montreal that could be of any help with that? Without further clue, I will be forced to restore that device to factory default and sell it half the price I bought it as an Internet-only tablet. It will probably work somewhat well if one never installs anything on it I guess.

Thanks for any help.
[Eee Pad Transformer Q&A, Help & Troubleshooting] oldcpu:
Problem is upstream - ICS is still not stable

The problem with that view, IMHO, is there currently is no stable version of the new ICS. If you read every forum of a Tablet with ICS (and indeed the phones with ICS) you will find ICS is not yet stable. Even 4.0.4 after some initial enthusiasm, has not been proven to provide the stability that many of those complaining on this thread, want to see.

IMHO the problem is mostly upstream, and it will take time to fix. Jumping to another Tablet, will IMHO show similar instability, where some with the other Tablets (and phones) have the problem, and some do not.
[Eee Pad Transformer Q&A, Help & Troubleshooting] EricBuist:
Ok, if the problem is upstream, then I guess I just did the wrong choice with Android. This is a bit frustrating, because nowadays, I always do the wrong choice when purchasing an item. There are so many variables to consider that there are just too many possibilities for a mistake, and no one in my neighberhood is interested in such items, so I am alone trying on the bleeding edge and stuck with problems only few people can understand fully.

By the way, I found a wonderful overview of TF101 rooting+unlocking+troubleshooting on http://xdaforums.com/showthread.php?t=1494230.

---------- Post added at 05:00 PM ---------- Previous post was at 04:54 PM ----------

I myself tried NVFlash, since I have a B60, but I just cannot get a compatible ROM for it. Download sites for these ROMs are VERY slow unless I subscribe to Premium membership and I would like to avoid starting paying 20$ per month just to get a single file. I know unsubscription after the download is likely to be a hard task.

I thus fell back to CWM that I got working yesterday, and found I can wipe data and cache separately. I thus tried to wipe cache and davlik cache, then rebooted. I'll see if it helps. The bootloop is less frequent since I disabled animated background, removed all widgets from my homescreens, toggled the checkbox to disable networking while in sleep mode and finally disabled notifications altogether. If no bootloop happens anymore, I will try progressively reactivating some functionalities. Otherwise, I will try a reflash after a full wipe, then the downgrade (with another full wipe).
[Eee Pad Transformer Q&A, Help & Troubleshooting] xbs:
Don't blame ICS my nexus s works flawless with 4.0.4
[Eee Pad Transformer Q&A, Help & Troubleshooting] oldcpu:
Users with ICS and the Nexus are experiencing random reboots

Glad to read you have no problems with ICS on your Nexus.

Unfortunately, others can NOT claim the same: http://greenpower.pouzerate.com/index.php/forum/4-troubles-a-bugs/444-galaxy-nexus-random-reboot ... which has posts by users, with the Nexus and ICS, experiencing random reboots
[Eee Pad Transformer Q&A, Help & Troubleshooting] cspiby:
The thread you link to is about a 3rd party app causing instability, how does that prove anything?

ICS is not inherently unstable, ASUS implementation of it however, is.
[Eee Pad Transformer Q&A, Help & Troubleshooting] oldcpu:
IMHO the problem is MOSTLY upstream ....

The internet is full of reports of Samsung users with ICS which is unstable. Some are seeing reboots. Some are not. Another example http://greenpower.pouzerate.com/ind...4-galaxy-nexus-random-reboot?limit=6&start=12

I could surf and post on and on and on and on and on and on and on .... ad infinitum.

But whats the point ? You and others refuse to believe.

The point is there is a core of dissatisfied Asus Transformer users, who are experiencing a high frequency of reboots, and they are blind to the fact that this is an ICS wide problem ...

Believe it or not , some of us with the Asus Transformer do not have the reboot issue. I can ONLY reproduce it with great difficulty. That suggests to me that the same is true for many non-Asus ICS users. They either do not have the reboot problem or they can only reproduce it with great difficulty (like myself with the Transformer). But I believe the ICS problem is there.

Don't believe me on this. Surf a LOT on this issue and come to your own conclusion.

---------- Post added at 01:11 PM ---------- Previous post was at 12:34 PM ----------

The number of threads on Samsung, and Nexus, and Xoom reboot problems is massive, far too many for me to repost them all. There are threads such as this with the headline: " Rumour: Android 4.0.5 coming in April, bringing reboot fixes to Galaxy Nexus and ICS to Nexus S " and it contains speculation that Android-4.0.5 will fix their reboot problems.

http://mobilesyrup.com/2012/03/28/r...oot-fixes-to-galaxy-nexus-and-ics-to-nexus-s/

Why speculate on 4.0.5 being necessary if 4.0.4 does not have reboot problems? IMHO the reason is 4.0.4 does have reboot problems for an assortment of ICS hardware devices.

I'm not anti-ICS. I like my Transformer. I like ICS. I am happy I updated my TF101 to ICS. I do NOT have the reboot problems most users have. But I do recognize the reboot problems exist, I recognize it is incredibly annoying for a number of Asus Transformer users, and I also recognize that the reboot problems are NOT confined to the Asus Transformer, but they impact a number of ICS users with different hardware.
[Eee Pad Transformer Q&A, Help & Troubleshooting] EricBuist:
Unfortunately, resettting Dalvik cache did not do the trick: my tablet was persisting in rebooting. I finally got pissed off, near the point of banging the thing over a wall of brick, and then gave up on ICS. However, I could simply not get my hands over a stock HC ROM!!! I looked from Asus site: nada. Other Google sites gave me broken links, often to ROMs of incorrect SKU. The trick that finally worked was a NVFlash ROM I found at here (I hope it won't be broken for someone who click on it...). Lesson learned: I will archive the ROMs of my mobile devices. :)

I will enjoy my "new" HC device some time, and possibly try something else. I was not convinced by the bootloader theory until I thought about microcode updating. The ICS bootloader may well upload some microcode to soft-update the firmware of some chips on the tablet. So I will eventually try to root my HC tablet, reinstall CWM and flash a Revolver ICS on top of that. Now that I know I have a safe return path to HC, I can try pretty much anything! I will also run CWM and Titanium backups to avoid the need for reconfiguring my device upon returns to HC.

By the way, is anyone aware of a procedure to make a dual boot configuration? It would be very nice to be able to try out some ICS-based ROM while keeping at any time the possibility to reboot into HC. If ICS becomes stable for my device, then it would be the reference ROM, and I could dual boot into custom ROMs as I see fit.

I admit that this is very problematic for users of >B70 tablets for which NVFlash is not an option. I hope Asus or Google will come up with a definitive fix for this or at least an official downgrade path. I just hope Asus does not assume that RMA is the official "downgrade" path... That would be quite bad.
[Eee Pad Transformer Q&A, Help & Troubleshooting] seeding11:
Sorry if I am repeating myself but I've just said the same thing on the Official Asus thread and thought it would be more appropriate to mention it here. I was saying that an NVflash had restored my TF to the exact state that it used to be... not as perfect as I had thought I remembered that it was. I did a clean install of all apps from the market and I had no TB data to restore.

On HC (prior to being rooted), I had the odd RR, woke up to a flat battery several times prior to discovering the autoairplane workaround, but the most annoying of all, it would was freeze completely while I was using it requiring me to reboot it manually (although I always suspected that it was app related). It was exactly the same after going back via NVflash. I am back using ICS because I prefer to deal with a RR during sleep every couple of days than a freeze while I am in the middle of something.

I'm wondering if everyone else who went down this road did actually end up with a much more stable TF, or whether there is/was a degree of stability and performance in HC, just as there is with ICS?
[Eee Pad Transformer Q&A, Help & Troubleshooting] septijo:
after update to 9.2.2.3, experience SOD and RR, i revert it back to HC with no luck.

already tried everything : nvFlash to HC (i try all version i can found : 8.6.5.13, 8.6.5.21, then 8.4.4.11), try Revolver 4rc2, Prime 2.11, Prime 1.4 and Prime 1.6r2 .. all with no luck !!! people said nvFlash will do the trick.. none on mine !!

I even try Team EOS Nightly build 33 (it is ICS 4.0.4) .. still no luck.. once every some minutes, logo "Team OS" trembling and waving in my TF101's creen .. (reboot)

Then.. i try Revolver 3.11.1 ... still no luck...

before give up TF101 (i was think that it is related to permanent hardware damage !!!)... i installed

WAKELOCK .... !!! HORAAAAAYYYYYYYYY.... i use option no 1 : Screen off, cpu on

TF101 is healthy. standby for 3 hours with only 1% less battery.

Stop waste your time, back to HC (nvFlash is preffered), download WakeLock from market / playstore, sit back and relax.

n.b. mine is B60 (SBK1) it is practically unbrickable by nvFlash, so i can try lots of version. if you dont have SBK1, DO NOT do as i did, just back to HC very cautiously and install WakeLock. mission accomplished.
[Eee Pad Transformer Q&A, Help & Troubleshooting] jtrosky:
I'm sorry, but I REFUSE to accept "wakelock" as a "solution". Personally, when I NVFlash'd back to Honeycomb, my RR/SOD issues went away (as it has for others) - maybe there truly is a hardware issue at work here? Not sure, but I do know that disabling deep sleep is certainly not the "solution" that I am looking for!
[Galaxy Y GT-S5360 General] CharlieBros:
I read a lot of threads but IDK how to do it with the Yphone, so please:

Somebody can tell me or make a tutorial to know how do it?

Thanks and sorry for my bad english, I'm 14 years old and our english teachers don't know a **** :D

Charlie
[Galaxy Y GT-S5360 General] jakarta.indonesian:
Hahaha:-D . My english more bad than you ...
[Galaxy Y GT-S5360 General] CharlieBros:
LoL!, And how old are you?
[Galaxy Y GT-S5360 General] wildsoul09:
here is a thread of a tutorial for making a rom for Y:)

http://xdaforums.com/showthread.php?t=1493319
[Galaxy Y GT-S5360 General] CharlieBros:
Oh! I didn't see that!, sadly the thread it's still in development but thanks anyway :D
[Galaxy Y GT-S5360 General] mrdoods:
go find in internet
[T-Mobile Samsung Galaxy S II SGH-T989] luarken:
hello friends, I need to know, how much energy can be spent, the proximity sensor

using Tap Tap app.

I'm looking for the best option to unlock the screen without touching the power button

T989
[T-Mobile Samsung Galaxy S II SGH-T989] iLeopard:
Im not quite following. Whats the Tap Tap app have to do with the proximity sensor and are you wanting to keep the screen live with the app open?
[T-Mobile Samsung Galaxy S II SGH-T989] ingenious247:
I think he's referring to the "always on" feature, keeping the proximity sensor always working so that the phone can be unlocked by waving your hand over the phone a set number of times (without even touching the phone physically)

However, battery life would only be a small concern IMO.. I would be more worried about the durability of the sensor being constantly on.. as in, would it cease to function eventually from over usage?
[T-Mobile Samsung Galaxy S II SGH-T989] ingenious247:
Update: it seems the "always on" setting is being reported as shutting off on it's own despite settings after an extended period of time. Reports vary from ten minutes to several hours/overnight, so the amount of time before it fails to stay active is unclear.

Personally I'm not sure of that's a bug or intentional. There are a couple of logical reasons to force the auto shut off after some time

1. Security - If you're not using your phone for an extended period of time, then it should lock back up, because frankly some people are idiots. Also who would want their phone easily accessed because they took a nap or ran to the store and forgot their phone? If you're not near it, you don't need to show off the feature (which let's be honest, that's the coolest thing about it. Who wants to constantly wave their hand over their phone like a weirdo with no one watching? You're not a wizard bro no matter how many RPG's you play)

2. Sensor Durability - the app won't last long if there's people in the play store leaving ratings like "proximity sensor doesn't work anymore, even after uninstalling. Factory reset didn't fix, I'm suing you ****er!". Plus if the Dev's worth supporting he's already tested and knows that's an issue, then he or she's protecting their customers

All of this information comes from user reports in the Google Play store and various threads. I have not installed the app and do not plan to until I see consistent commenting that issues have been addressed or resolved by the Dev (and yes I will be watching)

Seems like a "show off" app and I'd like to give it a shot when I'm sure it's functional. Typically in this case I'd just install, see what happens then email the Dev. However when it comes to hardware (proximity sensor) I'm a little more cautious since my phone is running like a champ with a flawless screen..I can't risk an exchange.

Sent from my T989 hunting for Siri Connor
[T-Mobile Samsung Galaxy S II SGH-T989] fuse1820:
Just thought I would point out that, when using an AT&T Skyrocket UCLA3-based ROM, the proximity sensor turns itself off if you leave the Phone app so that the screen doesn't keep turning off if you try to pull down the notification tray
[HTC One X] Slaytanic:
Hi,

does any of you know if the device can work in USB Mass Storage mode, i.e. can it be seen as an external drive from Windows/OSX/Linux

without

additional software? I own a MacBook Pro and HTC support told me that they are going to release soon a piece of software that works under OSX, but it would be wonderful to have access to the device storage without additional software..
[HTC One X] HTC-Gunge:
Question already asked and answered here:

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

They dont use USB Mass Storage they use Media Transfer Protocol to deal with USB connection. This change was introduced in Honeycomb and has continued into Ice Cream Sandwich.

You can still transfer files to and from the devices its just a diffrent way of doing it.

Source: http://glasskeys.com/2011/02/28/why-google-uses-mtp-instead-of-usb-file-transfer-on-android-3/

Source: http://en.wikipedia.org/wiki/Media_Transfer_Protocol

No idea how this works with OSX though I'm a Windows guy :)
[HTC One X] Slaytanic:
Very nice reply, thank you very much!
[HTC One X] Slaytanic:
I've found Android File Transfer Google utility for OSX: http://www.android.com/filetransfer/
[HTC One X] MinecraftZombi.es:
Actually, the One X still uses mass storage mode. Plug it in and you get the same old prompt for charge only, disk drive etc. and it still shows up as a removable disk.

Yes, vanilla android handsets like the GN use MTP mode, but HTCs don't. They have a separate partition still.
[HTC One X] HTC-Gunge:
Hmm that's interesting if its true, it means HTC have implemented it independently of the OS. Could even be a selling point as I know quite a few people didn't really like the change from USB Mass Storage to MTP.

Thanks for the info!
[HTC One X] lukesky:
I'm one of those who hates MTP because it is not as reliable as USB Mass Storage. MTP just doesn't want to play nice with my Win7 machine on my Nexus so I'm really looking forward to the One X and getting proper USB Mass Storage on it.