Related
Since Asus ICS update was a gigantic failure for me (Youtube HD videos broken, reboots, etc) I decided to 'downgrade' back to honeycomb. However that DID NOT fix the rebooting problem. And sometimes it doesn't even reboot, it hangs on the bootscreen and does nothing, and sometimes it bootloops or just doesn't wake up from sleep. Just to note I am using the Revolver ROM for honeycomb (fully updated) AND I did not have these problems with the rom before I tried ICS.
Has anyone had similar issues? If so how did you fix it?
Please, my transformer is becoming more and more useless
How did you downgrade to HC? Did you also downgrade the kernel and bootloader?
sent from my transformer
gee one said:
How did you downgrade to HC? Did you also downgrade the kernel and bootloader?
sent from my transformer
Click to expand...
Click to collapse
I rooted my device and used an app that installed CWM.. Kernel is downgraded when flashing revolver and I did install an overclocking kernel from revolver parts. Bootloader I don't know.
Perhaps you should try updating the bootloader? It's just a theory, but I doubt it will make you Tf any worse.
sent from my cyanogen(mod) vision
I've got the exact same issue after the downgrading to revolver rom HC. How do you update the bootloader?
Also, I noticed that no problems occur when the device is charging, kind of wierd
Sent from my Transformer TF101 using xda premium
Hope someone can tell how to update the bootloader. I was going to do the same thing with an tf101 because of all the reboots but if it dont help I rather wait to see how's it going..
The issue is that something goes wrong when the tablet goes in to "deep sleep". This is the same thing that is happening in ICS.
Now, I've found a temporary 'fix' for this issue. The fix is that you don't allow it to go in to deep sleep.
There is a program called WakeLock (It's on google play, my account is not allowed to post links :/) that lets you do just that.. Open up WakeLock and check the PARTIAL_WAKE_LOCK radio button and then tap the Aquire/Release Lock checkbox. Now you're set! The tablet should not reboot.
This has worked fine for me as a solution and my tablet has been running all day without problems. There IS a downside though, your tablet WILL consume more battery power since it doesn't go in to deep sleep.
As a countermeasure to that I used setcpu and a screen off profile that downclocks the CPU to around 200-300MHz and after a full day I'm at 50% battery life (13 hrs on battery), not amazing but acceptable (my usage consisted of having wifi on at all times and watching 3 episodes of community and light web browsing).
Hope this helps!
Flashstock said:
The issue is that something goes wrong when the tablet goes in to "deep sleep". This is the same thing that is happening in ICS.
Now, I've found a temporary 'fix' for this issue. The fix is that you don't allow it to go in to deep sleep.
There is a program called WakeLock (It's on google play, my account is not allowed to post links :/) that lets you do just that.. Open up WakeLock and check the PARTIAL_WAKE_LOCK radio button and then tap the Aquire/Release Lock checkbox. Now you're set! The tablet should not reboot.
This has worked fine for me as a solution and my tablet has been running all day without problems. There IS a downside though, your tablet WILL consume more battery power since it doesn't go in to deep sleep.
As a countermeasure to that I used setcpu and a screen off profile that downclocks the CPU to around 200-300MHz and after a full day I'm at 50% battery life (13 hrs on battery), not amazing but acceptable (my usage consisted of having wifi on at all times and watching 3 episodes of community and light web browsing).
Hope this helps!
Click to expand...
Click to collapse
The tf101 I want to downgrade don't have that deep sleep issue.. It reboots when it's in use, often repeatedly.. And often stuck on bootanimation (eee pad screen).. So maybe I should try anyway..
Sent from my LG-P990 using XDA
axepted said:
Hope someone can tell how to update the bootloader. I was going to do the same thing with an tf101 because of all the reboots but if it dont help I rather wait to see how's it going..
Click to expand...
Click to collapse
In the stock firmware on the ASUS site or in the OTA updates, there will be a blob file. The bootloader can be extracted from there with the blob tools (search in the dev section).
I'd make a flashable version, but I suspect that you have a WW TF.
Ok, now this is crazy.... I thought that I was going nuts when after a complete wipe (using SuperWipe script) and re-installation of Honeycomb from scratch, I too still had the reboots!!!
How can that be? The reboots were NOT there before I installed ICS!
Is it possible that Asus updated the firmware in a specific integerated device during the ICS update that is casuing these issues or something? I don't know how else to explain people having the same issues even after reverting back to Honeycomb!
Anyone have any thoughts on this?
I do remember hearing that the bootloader was updated with ICS - would that normally get reverted back to the "old" bootloader when doing a full wipe with SuperWipe script and re-installing Revolver (Honeycomb verison) from scratch?
Hmm, maybe the best thing to try would be to try the old bootloader with new ICS? Maybe that will stop the random reboots with ICS too!
Thanks!
No, most roms don't touch the bootloader. The stock roms and the OTAs will flash it. Although I'm not sure how much it could do once the rom was booted. I've noticed a few bad flashes lately, but they are usually resovled by flashing again with a full charge, overnight, plugged into the wall, not the USB port. Give that a try first.
gee one said:
In the stock firmware on the ASUS site or in the OTA updates, there will be a blob file. The bootloader can be extracted from there with the blob tools (search in the dev section).
I'd make a flashable version, but I suspect that you have a WW TF.
Click to expand...
Click to collapse
The one I'm going to downgrade is a US version... So if that helps, make a flashable version :thumbup:
Sent from my LG-P990 using XDA
If there is anyway someone could package the old Honeycomb bootloader, i'd be willing to try it! I have been unable to find a way to get back to stock Honeycomb (in order to re-write the bootloader). I'm assuming that I'd need an NVFLASH version of stock honeycomb firmware to get there from here?
thanks for any help offered!
Sent from my Transformer TF101 using Tapatalk
Two days ago I disabled the apps "Android keyboard" and "polaris" . Since I use Swype on the tablet and quick office, figured it couldn't hurt to try. Usually I'd been waking up to a frozen tablet or stuck on reboot screen. Two days now no freezes. Not sure if it has rebooted while asleep, but I use it every night for several hours, and since I did that I've had no problems. Maybe just lucky two days. Someone may want to investigate that further. Wifi is set to turn off when screen does. Hope this helps someone.
Sent from my Transformer TF101 using xda premium
jtrosky said:
If there is anyway someone could package the old Honeycomb bootloader, i'd be willing to try it! I have been unable to find a way to get back to stock Honeycomb (in order to re-write the bootloader). I'm assuming that I'd need an NVFLASH version of stock honeycomb firmware to get there from here?
thanks for any help offered!
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
What version tf do you have? US WW etc? Is your serial number nvflash compatible?
The other problem will be the system updates, but I think you can just delete dmclient?
sent from my transformer
i have a us transformer with the exact same problems. I went from Revolver HC to revolver ICS back to Revolver HC and the ICS reboot issue is persisting. I thought it was just me, glad to see (for my sanity's sake, not your torture) that it's not just me. I know on my old Captivate, if you used a GB bootloader with certain Froyo ROMs there was bad effects. It is possible it plays into it somehow. I never flashed an official ICS update, but since the customs are based off of ICS official it is possible something was changed. I have tried different Kernels, different Daemon settings etc, and the longest i could go was 2 days with no reboot. Mine does the same thing tho - sometimes it reboots. other times it just hangs on the ASUS screen until it kills the battery. It doesn't do it while plugged in. I have super wiped, re-flashed, restored old nandroid backs ups, you name it i have tried. Any help here is much appreciated as i have started using my kindle Fire as my primary tablet because i am becoming so frustrated with the TF. It has rebooted once while in use while playing a game. The rest is while off. Once li clicked the screen off to put it down to get a drink and it rebooted. Its quite maddening at this point,
I was eventually able to downgrade my bootloader to the version that came with 8.6.5.6 (its the version I had laying around). So, I am now running the 8.6.5.6 bootloader with Revolver ICS - we'll see what happens.
First night was encouraging - over 5 hours of deep sleep last night an no issues... I'll keep an eye on it and report back.
It just makes NO sense how the reboot problem is now present even on Honeycomb, where is wasn't as issue beofore!
I now wondering if ICS either updated some firmware on some device in the TF (wifi chip, bluetooth chip, etc) or that the bootloader might be the difference....
So I now have a Honeycomb bootloader (verify bootloader version by looking at text on sceen after holding vol down + power) and ICS OS. Time will tell....
Can anyone else explain how the reboot problem could cause the issues on honeycomb as well???
Thanks!
Sent from my Transformer TF101 using Tapatalk
jtrosky said:
I was eventually able to downgrade my bootloader to the version that came with 8.6.5.6 (its the version I had laying around). So, I am now running the 8.6.5.6 bootloader with Revolver ICS - we'll see what happens.
First night was encouraging - over 5 hours of deep sleep last night an no issues... I'll keep an eye on it and report back.
It just makes NO sense how the reboot problem is now present even on Honeycomb, where is wasn't as issue beofore!
I now wondering if ICS either updated some firmware on some device in the TF (wifi chip, bluetooth chip, etc) or that the bootloader might be the difference....
So I now have a Honeycomb bootloader (verify bootloader version by looking at text on sceen after holding vol down + power) and ICS OS. Time will tell....
Can anyone else explain how the reboot problem could cause the issues on honeycomb as well???
Thanks!
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
Give us an update on this later
FYI - Still going strong with ICS (Revolver) running old Honeycomb bootloader (8.6.5.6).... I don't know, but I have a good feeling about this (of course, I've had that "good feeling" about 20 times now without any success)!
I'll keep you posted!
Sent from my Transformer TF101 using Tapatalk
jtrosky said:
FYI - Still going strong with ICS (Revolver) running old Honeycomb bootloader (8.6.5.6).... I don't know, but I have a good feeling about this (of course, I've had that "good feeling" about 20 times now without any success)!
I'll keep you posted!
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
Nice! How long have you been running it now?
Sent from my LG-P990 using XDA
Hi there!
I recently bought an Asus Tf-101 and I'm really enjoying it... However, I've seen a lot of users complaining about random reboots and SODs. For the 10 days I've been using it I only experienced SOD and only if the tablet stays in stand-by for a long time, like 6~8 hours (during night time most of the times).
Because of this, and honestly I don't want to experience those RR, I'm considering returning it and getting a SL-101. However, I'm not sure if the slider as the same issues since they aren't very different.
I'll also take this shot to ask for any suggestion from you, like what other tablet should I get or workarounds to make this work properly (I don't want to root or flash the device, in first place I wan't a device whose brand was able to make it work without any major issue). I really would like to buy the Prime but it is out of budget and, here in Portugal, there is no TF300 yet and I actually wanted one with ICS...
So.. any feedback on SL-101 or any advice from you?
Best regards,
Miguel Ribeiro
I have an SL101 and i NEVER had any random reboot or a SOD at all, mines not rooted or flashed or anything. The only thing you MIGHT experience is some occasional lag.
Also, the ICS update is LATE AS HEEEELLL
I hope it helped
I have an tf101 b70 us with stock rooted rom. Since yesterday updated it to 9.2.1.24 and were ihad screen tears with youtube and rr/sod with the .21 firmware it still doesn`t show at the .24 firmware. But it is to early to say it is solved only have the .24 for about 27 hours now
Just a question, does the TF101 Dock has the same problem with the YouTube app as does the Slider? My AZERTY Slider can't mark a space if i dont press the up key first
I've got the SL-101 and I do have some Radom reboots. Seems to have just gone away for now. After I got the last update they stopped.
Sent from my SGH-T999 using xda app-developers app
Hey Guys just rooted my TF300 last week switched throug 3 custom roms and then went back to stock firmware....did a re root after stock install.
worked fine for a month but suddenly today screen just went black and refuses to display anythin. Ican tell that the screen is on (backlight glow visible) but it wont display anything.When i reeboot via power button screen works fine for 20 seconds till the asus logo and then degrades slowly to complete black. Warranty is void due to unlocked bootloader. plz help!!:crying:
Does the screen look ok when you boot into recovery? If it does try reflashing the rom, if not it might be a hardware issue.
what firmware on you on? if your on 30 flash back to 29 then see if it works
MegaNoob said:
Does the screen look ok when you boot into recovery? If it does try reflashing the rom, if not it might be a hardware issue.
Click to expand...
Click to collapse
screen is fine upto the asus/nvidia logo is displayed but goes bloack as soon as i get into recovery
R3Z4545 said:
what firmware on you on? if your on 30 flash back to 29 then see if it works
Click to expand...
Click to collapse
I'm on .30 but i cannot enter recovery is there any way to downgrade without recovery ?
screen has deteriorated further refuses to show the boot logo also tablet seems to be working fine tho can hear it getting emails (makes the notificatioin noise) so looks like a hardware issus sending it to the local Asus service centre any idea hw much a screen replacement will cost ?
judeabreo said:
screen has deteriorated further refuses to show the boot logo also tablet seems to be working fine tho can hear it getting emails (makes the notificatioin noise) so looks like a hardware issus sending it to the local Asus service centre any idea hw much a screen replacement will cost ?
Click to expand...
Click to collapse
Don't quote me on this, but I recall someone saying that their screen had cracked and had to get the screen replaced, and the cost would have just about as much as a new tablet, since the glass/IPS screen is all one unit.
I recall reading that, but can't find it now, so I may be thinking of something else.
Ok guys the tab came back on by itself I just left it alone for the night and it's fine today *fingers crossed* hope it does not act up again. Thank you guys for ur replies.
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
judeabreo said:
Ok guys the tab came back on by itself I just left it alone for the night and it's fine today *fingers crossed* hope it does not act up again. Thank you guys for ur replies.
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
Click to expand...
Click to collapse
Thats pretty crazy. I've never heard of anything like that. Is it still working ok?
Yep seems to be fine no issue whatsoever fingers crossed.
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
Hey guys
Sorry wrong thread.
I received the ota jelly bean update 4.2.x build 10.6.1.8. All seems well except for one issue, which for me is a major issue.
The micro hdmi out port always displays at 420p, i've tried everything I can think off to get it to change. There is nothing in settings to change resolution or any hdmi settings.
Prior to the update it worked great connect the micro hdmi cable and I could play videos with dice player or bsplayer. I would get highest possible resolution, I am using the same display device that I've used for the past year, projector with hdmi. Projector is ok as I hooked another hdmi device and works fine.
So any ideas on how to fix hdmi issue ? If no fix how can I drop the back to the previous build ?
Would the new 10.1 cm rom use hdmi out ok, or anyone have suggestion of another rom that hdmi out works ok ?
I've tried rooting but have run into another problem I'll post as separate issue.
Asus says factory reset, did not work.
I can confirm the problem, I hope it's a bug and not a "feature" because the update makes hdmi output useless.
tonyjsan said:
I received the ota jelly bean update 4.2.x build 10.6.1.8. All seems well except for one issue, which for me is a major issue.
The micro hdmi out port always displays at 420p, i've tried everything I can think off to get it to change. There is nothing in settings to change resolution or any hdmi settings.
Prior to the update it worked great connect the micro hdmi cable and I could play videos with dice player or bsplayer. I would get highest possible resolution, I am using the same display device that I've used for the past year, projector with hdmi. Projector is ok as I hooked another hdmi device and works fine.
So any ideas on how to fix hdmi issue ? If no fix how can I drop the back to the previous build ?
Would the new 10.1 cm rom use hdmi out ok, or anyone have suggestion of another rom that hdmi out works ok ?
I've tried rooting but have run into another problem I'll post as separate issue.
Asus says factory reset, did not work.
Click to expand...
Click to collapse
I can't give you a fix as I don't have 4.2 yet.
I don't know your previous built so I'll give you instructions and you use the build you wish.
I'll use 10.4.2.18 as an example. Unzip Asus firmware once and put the new zip file on your internal sdcard wait if no response power down. Repower you should get the update triangle as with an ota. Accept and wait for results. I have used this to update and downgrade as well with success.
Good Luck!
no crop /scale
hi there!
so let's try my school-english....
since the last update a few days ago to android 4.2.1 i have almost the same problems with hdmi -out!
bevore the update, for example videos from the youtube-app in 1080p came to the tv in full-screen and 1080p - AND the tab-display became black - until i tapped on it for re-activating. In the status-bar there was the hdmi-button with two options: scale or crop. in one of this two cases i only saw the video on the tv in full screen, in the other option i could see the status-bar additional on the tv. I liked to use the full-screen without status-bar.
so thats history now!
since the glourious update, nothing of this works: no more hdmi-option in the status bar, only the information. no fullscreen, but the same picture like on the display-including BOTH status-bars (on the top and -hmmm- on the "floor"), and the whole picture does not fill the tv-screen. and the display of the tab doesn't get black anymore.
that's bad. very, very bad, 'cause using the tab via hdmi in 1080p to tv is one of my main use.
can anybody help, plz?!?! i hope there is a solution without "down-date" to 4.1.x!
sry 4 my bad english
After the 4.2.1 update the tf300t has the same problem of the nexus 10:
http://code.google.com/p/android/issues/detail?id=40225
Yeah, this really sucks, can't even get the audio now! I regret that i updated to 4.2.1. Hopefully the developers will notice this and update the current version.
Well mine doesn't even work so mehh..
Sent from my Galaxy Nexus using Xparent Cyan Tapatalk 2
Only: 72 people starred this issue and may be notified of changes. And it's listed as enhancement because the Nexus 10 never had what the TF300 has lost.
Surely it's a bug and not a new feature request for TF300 users, and should be put to Asus not Google? Doers more people "starring" an issue increase its urgency?
And does it work with cm 10.1 ?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
It's a known issue on 4.2.1 that afflicts more than just the TF300T. It's why I'm still on 4.1.1 and the original JB bootloader.
So three months and no fix ? Does 4.2.2 offer anything worth updating or is it mostly fluff plus this bug?
Hello everyone,
Im newbe in tablets.
I have small problem, i helped my friend with his cracked screen in his tablet. I just replaced broken screen on my own, we had G03 and we bought the same.It works almost fine but after change we have problem with pointer its hard to point something correctly. Anyone can explain me how to fix it or how to calibrate it? Could you give me any guide what i have to do? Im not familiar with roms, changing roms etc, but if ill need it ill findout.
Best Regards.
mrpst said:
Hello everyone,
Im newbe in tablets.
I have small problem, i helped my friend with his cracked screen in his tablet. I just replaced broken screen on my own, we had G03 and we bought the same.It works almost fine but after change we have problem with pointer its hard to point something correctly. Anyone can explain me how to fix it or how to calibrate it? Could you give me any guide what i have to do? Im not familiar with roms, changing roms etc, but if ill need it ill findout.
Best Regards.
Click to expand...
Click to collapse
Best bet I know of is to reflash firmware as discussed at length in this thread. I can't guarantee the result, but if you're game, I've done it to correct erratic responsiveness. To give you an example, I replaced the touch screen only to find out I couldn't move the icons from the main screen to where I wanted them to be. They'd just slip as I dragged them. I reflashed the firmware, then tried a few roms. Paranoid solved it. From then on, no more errors no matter what. Good luck.
I had my tab rma'd and techs left a tf300 touch tool on my tab that looks like a screen calibrater. Pm me if you want to try it
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD