My prime constantly reboots since I upgraded to ICS whereas it was perfect back in honeycomb. Is there anyway to downgrade back to HC whoever I wait for Asus to fix the rebooting problem?
Frooty said:
My prime constantly reboots since I upgraded to ICS whereas it was perfect back in honeycomb. Is there anyway to downgrade back to HC whoever I wait for Asus to fix the rebooting problem?
Click to expand...
Click to collapse
No known way to downgrade yet.
Wanted to bump this thread up to see if anyone has found a way to get honeycomb back in the last couple of weeks...
reboots suck but I really loved this thing when it was running honeycomb.
Related
So after updating to the 1.2BL and installing illuminate 1.5 i had noticed that my tab would not wake up after going to sleep. I had to hold down power and fully restart the device in order to get it going again.
I assumed it was because of illuminate so i wiped data/cache/dalvik and reinstalled with no luck. So i decided to wipe everything including system, repartition and then reinstall....still no luck. After updating to 1.6 and 2.0 with the same problem i figured I'd try bottle of smoke..... Well the same issue remains.
The tablet goes to sleep, and then will not wake up again with out a restart.
I had zero problems when i was on 1.1 and running other roms including stock, tnt lite, vegan tab and CM7/CM7 nightlies.
Installing a wifi lock app stops the device from sleeping and fixes the problem. However that isn't a permanent fix. I'm not sure if the problem is related to the 1.2 bootloader or Honeycomb.
Is anyone else having the same issue? Any ideas on a fix?
edit: also adjusting overclock settings doesn't make a difference
I am not sure on how to fix this, but since the Honeycomb ROMs are still in Alpha (which means they are still in development) it is most likely the ROM, or it may be just your specific G-Tablet reacting weirdly. I would suggest, if its that big of a problem, to switch to a new/different ROM and wait until they have Honeycomb stabilized. Hope this helped
(actually responding here as I got PM'd as well) I don't really know this ROM too heavily since it's not mine, but even the HC alphas have differences as far as the kernels in use are concerned. It could just be a "known issue", but you might be better off posting to the modders dev thread or PM'ing him to be sure. I haven't heard of this issue, but again I don't scan his thread heavily.
What I can tell you is that sleep of death (SOD) issues have occurred on Froyo ROMs for a long time. It's one of the things that custom kernels attempt to minimize.
Thanks for the response mate. I actually switched from illuminate over to bottle of smoke because I thought the rom may be the issue. But I'm still having the same problem
Sent from my DROIDX using Tapatalk
SOD is one thing I can't replicate on BoS, at least with my minimal testing. It was a big problem for me on the 4349 stock kernel - so much so that I started using custom kernels on TNT Lite (first) and then later on Mountain Laurel.
roebeet said:
SOD is one thing I can't replicate on BoS, at least with my minimal testing. It was a big problem for me on the 4349 stock kernel - so much so that I started using custom kernels on TNT Lite (first) and then later on Mountain Laurel.
Click to expand...
Click to collapse
yeh i haven't heard of anyone else having the same issue. At least not with honeycomb roms. I'll see if i can pull some logs to see if i can see anything from that
interesting update on this.
I nvflashed back to bootloader 1.1 with the stock tap n tap software.
Wifi turned off, and the tab wakes from sleep just fine like it should.
I flashed the latest RC1 CM7 rom for BL 1.1, and the tab will not wake from sleep like it was doing before. Unless the wifi is forced on, the tab will have to be hard reset when the screen is turned off.
I flashed Vegantab (froyo) and once again. No problems. The gtab wakes just fine.
The biggest thing is that i was using the old BL1.1 CM7 nightly builds before switching to honeycomb and i never had any problems with those.
So it seems there is something in the honeycomb and latest CM7 roms that is causing the sleep of death problem
Assuming this isn't a software bug, try boosting the min CPU frequency.
rajeevvp said:
Assuming this isn't a software bug, try boosting the min CPU frequency.
Click to expand...
Click to collapse
yeh i tried messing with all that stuff before with no luck.
I'm actually selling the tablet anyway. I've got vegantab running on it. Which isn't ideal but it's the only rom where ALL features of the device work fine, and it doesn't die when the screen is off
SOD Illuminate
Hi,
I did have the same problem over and over again whenever I replace CM7 or Vegancomb. It is just for the 2.3.4 roms with 1.2 bl. Froyo to HC, I never have them. The cure is to nvflash 4349 then reflash any Froyo rom or HC on it. For this matter, I dont like 2.3.3 or 2.3.4 versions. If you use CM7 or Vegan, it is a must to go back to 4349 first before going to diferent roms. This is one of your instructions Roebeet. By doing so, you will never have problems. I notice this first when I flashed CCv6 from Vegan and then, I got curious why. Then I repeated the same with other roms, it dd the same. Be careful with the 2.3.3 and 2.3.4. Ooops, 5274 and HC By the way yield CWM looping.
Hi.
I am about to unroot and go back to otb stock. I am wondering if anyone knows for sure when the random reboots that I, and several others encounter, first started because I need to know whether to do the OTA after I go back to stock.
From my memory....... :
Wasn't there 2 OTA's?
And the random reboots started after installing the 2nd one?
So should I just install the first one.......orrrr......does it automatically only give one OTA direct to the 2nd one released?
Or should I not install any OTA's at all and patiently wait for Gingerbread........
Thanks!
We have MR1, MR2, and MR2.5 but I think only MR1 was an official OTA (dont quote me on it tho since I have been rooted since I got the phone and have never received an OTA). I think the reboot issue has been a problem for a lot of people for the entire time and isnt a new thing. IIRC MR1 caused quite a few reboot issues but not for everyone. I personally ran w/o any reboots until I got to 2.5 and even then I have only ever had 1. Its just what works best for you.
You will be waiting patiently for quite a while for official GB from what I have heard on the boards but you can always try out some of the GB ROMs that we have already.
Beastclaw said:
We have MR1, MR2, and MR2.5 but I think only MR1 was an official OTA (dont quote me on it tho since I have been rooted since I got the phone and have never received an OTA). I think the reboot issue has been a problem for a lot of people for the entire time and isnt a new thing. IIRC MR1 caused quite a few reboot issues but not for everyone. I personally ran w/o any reboots until I got to 2.5 and even then I have only ever had 1. Its just what works best for you.
You will be waiting patiently for quite a while for official GB from what I have heard on the boards but you can always try out some of the GB ROMs that we have already.
Click to expand...
Click to collapse
You are correct Beast there has only been one official OTA. My wife is not rooted but I am
Well I went back to stock because I was gonna try to go to Verizon today and swap it out.....
I find it funny this exactly what I was going to ask today myself. I'm also running bamf remix 1.8, have tried all the radios and even installed bamf 2.0 for GB with the Mr 2.0/2.5 radios. Still got reboots. Now I want to go back to stock and unroot so I can go back to the store and swap it
Just wonder if its worth it, maybe if they let me swap SD cards
I just un-rooted my phone about two days ago. After, I did the OTA update. I hadn't seen any problems until today. I live in a 4G area and work in a (up until Monday) 3G area. Since Monday they have been testing out a 4G tower. I have had 4G until this morning, I just figured that they were still testing it out and had switched it off. Well, about an hour ago I got my first Reboot. When the phone came back up I noticed that the 4G had just came back on. I'm pretty sure that's what triggered my reboot. So in short, as long as they keep the 4G going I don't have any issues.
Just curious is the update worth doing? And if i do it do i go ahead and install the GB bamf rom and radio? or just go back to my current 1.8 remix?
im curious what you guys have your phones overclocked at? I am rooted on the RC3 bamf 3.0 and the only time I have seen reboots is when i had my phone overclocked to high. now that im at 1.42 on the bamf cpu (I disabled my setCPU) and it has been solid.
Im possibly getting the TFP tonight from a bestbuy near me. Im wondering if I should update to the OTA from yesterday or stick with 11.1
It seems although the .13 update solved alot of issues it brought others with it. I wont be missing any battery life if I update because I am not use to the past versions myself since I never had the TFP so im wondering if I should just go ahead with the update or stick with w.e. is out the box? Any advice? Thanks.
I have been waiting for the 2012/2/17 .14 firmware to arrive GTA Canada. Has anyone in Canada got their .14 OTA yet?
I am now in .11 after the last Asus OTA upgrade. However, interestingly, I just realized that mine has a IML74K.WW_epad-9.4.2.11-20120117 Build. No wonder it did not get the .13 upgrade. I bought mine at NCIX, should it be a US instead of a WW model? I am thinking to change it to the US Build using the dd method mentioned in this forum. Has anyone tried this?
Any more advice?
If you search thru the post made my Gary Key (Asus Tech manager), .14 should be released by Tuesday to WW after it passes Google Certification. WW users will not get the .13 and go straight from .11 to .14.
So wait till tuesday or do it yourself now. Your call.
How do you do it by your self...
there is no Firmware posted for WW of the .14 version on the ASUS website
I'm in no rush for this, everything is working perfect on my device.
wifesabitch said:
I'm in no rush for this, everything is working perfect on my device.
Click to expand...
Click to collapse
I've heard it forces you to update after three notifications. I did the OTA from honeycomb to ICS (.11) and everything is awesome, so I'm hesitant to update given the trouble people seem to have had.
Sent from my Transformer Prime TF201 using Tapatalk
m3t4lw01f said:
I've heard it forces you to update after three notifications. I did the OTA from honeycomb to ICS (.11) and everything is awesome, so I'm hesitant to update given the trouble people seem to have had.
Sent from my Transformer Prime TF201 using Tapatalk
Click to expand...
Click to collapse
Mine is working fine except for GPS. I'll wait until tuesday. I really wanted the GPS feature
I guess I will wait and see then...my .11 has minimal issue other then constant wait freeze issue on my ICS+ browser.
myeepad said:
I have been waiting for the 2012/2/17 .14 firmware to arrive GTA Canada. Has anyone in Canada got their .14 OTA yet?
I am now in .11 after the last Asus OTA upgrade. However, interestingly, I just realized that mine has a IML74K.WW_epad-9.4.2.11-20120117 Build. No wonder it did not get the .13 upgrade. I bought mine at NCIX, should it be a US instead of a WW model? I am thinking to change it to the US Build using the dd method mentioned in this forum. Has anyone tried this?
Any more advice?
Click to expand...
Click to collapse
To answer you specifically, yes, you could and would be fine.
I have not changed my SKU, but I've reverted to nearly every US update and have seen no ill effects, upgrading with it should be no different. You still get OTA's after, and if you go back you can freeze your DMClient (if you're rooted with Titanium Backup or something else that does similar) and not be bothered with further updates.
In my personal experience, update .11 is the holy grail of performance and battery-life, so I'd personally recommend staying there unless you're having issues.
buxtahuda said:
To answer you specifically, yes, you could and would be fine.
I have not changed my SKU, but I've reverted to nearly every US update and have seen no ill effects, upgrading with it should be no different. You still get OTA's after, and if you go back you can freeze your DMClient (if you're rooted with Titanium Backup or something else that does similar) and not be bothered with further updates.
In my personal experience, update .11 is the holy grail of performance and battery-life, so I'd personally recommend staying there unless you're having issues.
Click to expand...
Click to collapse
clockwork58 said:
If you search thru the post made my Gary Key (Asus Tech manager), .14 should be released by Tuesday to WW after it passes Google Certification. WW users will not get the .13 and go straight from .11 to .14.
So wait till tuesday or do it yourself now. Your call.
Click to expand...
Click to collapse
Thank you for these good advice. Yes, the .11 works fine for me and I can surely wait till Tuesday to screw up my Prime...if ever it does that...
Haranzo said:
I guess I will wait and see then...my .11 has minimal issue other then constant wait freeze issue on my ICS+ browser.
Click to expand...
Click to collapse
Try chrome. Works much better for me.
rony05 said:
Try chrome. Works much better for me.
Click to expand...
Click to collapse
I used chrome for a few days and i found it to be fast but unstable. I went back to stock browser. Works well enough for me, at least until chrome is out of beta status.
rmsingh said:
I used chrome for a few days and i found it to be fast but unstable ...
Click to expand...
Click to collapse
Lol, just like on the computer!
I personally use Opera Mobile, just so I have the same interface from phone to tablet and it's always been a good browser on Android (personally didn't care for it back when I tried it and Maxthon on PC's).
Dolphin HD of course.
I have the same "wait" issue with stock browser, but it doesn't really bother me. Prolly just put ICS + or whatever it's called.
Im just curious if anybody out there is running the stock version of Honeycomb and NOT having any gps lock problems?
No problems here. Don't use the GPS extensively but I've not noticed a problem when I use it with either GB or HC.
I use Sygic a ton! Like around 3 times a week and I have not had any problems on HC
Sent from my PG41200 using XDA
So your not running anything special?
Not rooted, or different kernal flashed. Stock version of HC?
jacobbones said:
Im just curious if anybody out there is running the stock version of Honeycomb and NOT having any gps lock problems?
Click to expand...
Click to collapse
there is a patch on GPS from crypted,
http://forum.xda-developers.com/showthread.php?t=1267899
used it and check your gps with gps-status.
Hope this help,
I saw that patch.
Looks like I will try and do that next day off.
Gotta root my tablet first though
When running CypherROM I had no problems with GPS lock.
I'm trying the de-sensed ROM now, and haven't tried GPS yet.
No, nothing special. Just the HC I got when i updated. No special Rom or anything.
Sent from my PG41200 using XDA
This has been hashed over and over. There must be 10 similar thread on this forum so not sure why people see the need to open yet another one, but.
Nothing actually fully fixes the GPS issue in HTC honeycomb, same for all the custom HC variants. It appears to have a problem that repeatedly resets the GPS after a period of time. For some applications, it will still work if you are in a location that allows a fast lock again or for applications that need a one time fix. There is something buried deep in the driver or kernel that is playing havoc with the GPS.
STILL NOT FIXED ON ANY VARIANT OF HC.