Database Users

[Q] Lockscreen Reboot Issues

I've been having lockscreen reboot issues with the last few Fission roms, and a couple of Matt's. Has anyone else had this problem and resolved it?
I followed the installation instructions and even formatted my SD card. I'm going to try to SBF before I install the next Fission, is there anything else I can do to completely clean out my phone? Such as wiping some system files in recovery or something.
The only data I have left over from other ROMs is backups I made of a few games like Angry Birds.
Any suggestions are appreciated, I've been trying to fix this issue for awhile!

Are you doing a hard reset after flashing roms? Resetting the phone in applications>privacy, at the bottom of privacy?

mikeyinid said:
Are you doing a hard reset after flashing roms? Resetting the phone in applications>privacy, at the bottom of privacy?
Click to expand...
Click to collapse
Yup, after installing the ROM and rebooting I do a hard reset through the privacy menu. Would it make a difference if I sign into my google account on first reboot before doing the hard reset?

kdog349 said:
Yup, after installing the ROM and rebooting I do a hard reset through the privacy menu. Would it make a difference if I sign into my google account on first reboot before doing the hard reset?
Click to expand...
Click to collapse
I never sign into google until after the hard reset. But I dont know if that matters. Next time you flash a rom, try wiping data and cache in recovery, after flashing, but before you reboot. And, are you overclocking or undervolting?

I'll try wiping data and cache before my first reboot. I know I used to do this but not sure if I've done it recently.
I haven't messed with overclocking or underclocking. Do you know if any widgets are known to cause problems? I run Launcher Pro, but I went a day or two with the stock launcher and still had some reboot issue.

kdog349 said:
I'll try wiping data and cache before my first reboot. I know I used to do this but not sure if I've done it recently.
I haven't messed with overclocking or underclocking. Do you know if any widgets are known to cause problems? I run Launcher Pro, but I went a day or two with the stock launcher and still had some reboot issue.
Click to expand...
Click to collapse
Launcherpro wouldnt cause it. I would sbf if i were you, and just keep doing what your doing. After so many flashes there is bound to be some residual bs left behind.
*Fission 2.2.1 will be hitting the forum soon so an sbf is in your best interest Im running it now and its VERY good...

mikeyinid said:
Launcherpro wouldnt cause it. I would sbf if i were you, and just keep doing what your doing. After so many flashes there is bound to be some residual bs left behind.
*Fission 2.2.1 will be hitting the forum soon so an sbf is in your best interest Im running it now and its VERY good...
Click to expand...
Click to collapse
I'll give SBF a try. I've been loving everything about the fission ROMs, can't wait to get 2.2.1
Thanks so much for the help!

mikeyinid said:
Launcherpro wouldnt cause it. I would sbf if i were you, and just keep doing what your doing. After so many flashes there is bound to be some residual bs left behind.
*Fission 2.2.1 will be hitting the forum soon so an sbf is in your best interest Im running it now and its VERY good...
Click to expand...
Click to collapse
I'll give SBF a try. I've been loving everything about the fission ROMs, can't wait to get 2.2.1
Thanks so much for the help!

Lock Screen Reboots are something that seem to be present in all these Moto Droid phones. I always always always get them on both D1 and Dx and D2, with any ROM, theme, etc. Just seems to be a common problem Motorola has, along with their insane fascination with their Motoblur UI which is also a complete mystery.

mjones1052 said:
Lock Screen Reboots are something that seem to be present in all these Moto Droid phones. I always always always get them on both D1 and Dx and D2, with any ROM, theme, etc. Just seems to be a common problem Motorola has, along with their insane fascination with their Motoblur UI which is also a complete mystery.
Click to expand...
Click to collapse
Personally I had a Droid 1 for 6 months and don't remember having any lockscreen reboots, at least not at the frequency of 2-3 a day that I'm having now. Could run the phone for a week without rebooting.
There were a couple of D2 roms that didn't have the reboot issue for me, but most do so maybe it is an issue with the phone like you say. I Don't understand their persistance with motoblur either At least take out eFuse if you're going to throw on motoblur

I've been trying lockbot free to solve my reboot issues. You can basically set it to be exactly the same the normal lockscreen, and so far it seems to be working for me.

I had this problem. Random, intermitten soft reboots during slide to unlock. Ran multiple roms, always had the problem. But I was always removing the same things after sbf. I had found one Dev to seem to find this to follow the music.apk file. So this time I left it on. On my last sbf, I left that in there. Havent had a problem since. Before that I had tried what I thought to be everything, multiple sbfs, multiple roms, completely formatted sd card, and re-sbf'd again. But I always deleted music.apk. Because it always seems to start running, using memory that I thought was unnecessary. Since I dont play music from my phone, other then streaming music. Hope that helps someone. Saved a ton of frustration for me!

But I always deleted music.apk. Because it always seems to start running, using memory that I thought was unnecessary. Since I dont play music from my phone, other then streaming music. Hope that helps someone. Saved a ton of frustration for me!
Click to expand...
Click to collapse
Which music.apk is this? Is it the D2's original application or the google music app? Because I've never taken the music app that's been on the phone or came with any ROM and I've had a few not a big number but a few.
Sent from my DROID2 using XDA App

Not sure what the google music one is, but the file is named music.apk

Please clarify this lol. Mine was working great until I installed that damn black theme for fission rom.

I've had a droid1 and I have never had reboot issues with roms before. I think it may just be a d2/x problem
Sent from my DROID2 using XDA App

Yeah the same thing happens to me. I'm pretty sure the dev's for Fission know about it, so hopefully 2.2.1 from them fixes it.
Sent from my DROID2 using XDA App

I had this same problem until yesterday. I installed the Music.zip that came with fission. Now I haven't had a single problem. (I also installed the 10 percent framework and the Camera.zip) I can't remember who posted it but once I installed the Music.zip everything works great.

Im just curious, are you guys only experiencing these reboots with the non-blur roms, or have you experienced them with other roms also? I have only had one reboot, and that was running fission 2.2.1.

tonorice said:
I had this same problem until yesterday. I installed the Music.zip that came with fission. Now I haven't had a single problem. (I also installed the 10 percent framework and the Camera.zip) I can't remember who posted it but once I installed the Music.zip everything works great.
Click to expand...
Click to collapse
Was it the "Android_Music.zip" or "D2_Music.zip"?

some apps will hang and use more than 80% cpu!

guys i have this issue, after flashing to darkly v9 some apps hang for one min or more. Example.
1- advance task killer will hang if I go see running services and back to task killer menu.
2- flickir wallpaper hd will hang if I preview any wallpaper and go back to the list of wallpapers.
At task manager, I can see these apps using 80% cpu for the hanged time.
I reinstalled apps, didnt help
i flashed the phone back to factory (using download), flashed to darkly v8, didn't help.
What to do
Edit- Ok, i found that it only happens when wifi is on.

night_wolf_in said:
some apps hang for one min or more
Click to expand...
Click to collapse
Dont use those apps? (Ever occurred to you that it might be the apps and not the roms? or some other app that makes the other apps hang? Perhaps your very own task manager?)

umm, if everyone using those apps. and it runs fine. i think asking me to not to run the app is kinda not the right approach.
if things were working, then they are not working. then it means something wrong went. and i agree could be either. but before blaming the apps that are useful. lets try to fix it.

this issue, after flashing to darkly v9
Normally if you have a problem after doing X then its usually the fault of X
jje

agreed, but then after flashing back to v8. the issue was still there. hence the weird thing.
i asked around in another forum. and i think it fixed it. here was his solution
Got the same problem. Got a bit sick and tired of it thats why i tried Doc's ROM, and i became a happy man.
but before that, have you tried using SGS Tools and run the clear_thumb_db.txt script?
Click to expand...
Click to collapse
so i ran what he suggested. and it worked. i spend 4 hrs yesterday cracking my head was the phone was doing like that. on top of that. i flashed it at least thrice!!

agreed, but then after flashing back to v8. the issue was still there. hence the weird thing.
Yes but you may have needed a complete wipe of system and data to clear the problem .
jje

I did wipe. Even did factory resest in recovry mode. Al yet didnt make it work. Now flickie wall paper stil hangs. Me out of ideas. Some suggested different rom!

Rom Kitchen far less reported bugs .
http://forum.xda-developers.com/showthread.php?t=817703
jje

oks. well give it a try later on. at least after two weeks. cant waste my time as i wasted my weekend!

Odd Problems with HTC Hero CDMA

I have this weird problem, and I can't figure out the cause.
Whenever I use my phone lately, it will randomly freeze/force close certain apps. It's super laggy. If I drag my hand/palm across the touch screen, it will stop lagging and perform all the touch commands that I had "queued" up. This seems to persist even though I just wiped+flashed my phone again.
I've got nandroid backups for my stock hero, CM6.1.0, and now I just wiped and flashed to CM7.0.2. Sitting in the CM7.0.2 setup wizard as I type this, and it's lagging like crazy. Is it possible my Hero is internally damaged somehow and that's causing the problems, or does it sound like software? My Hero has been through a LOT of bumps, some harder than any phone should have to endure.
Still, I'm strapped for cash and making the best of what I've got. Anyone got any ideas? Is it possible that I screwed something up using the adb shell when I was a little nooblet? And that said, is there anyway to wipe everything and start with a completely clean slate?

rjhall said:
I have this weird problem, and I can't figure out the cause.
And that said, is there anyway to wipe everything and start with a completely clean slate?
Click to expand...
Click to collapse
I'm new here but I've had a lot of different problems also. What I do is RUU and start over. It fixes a lot of screwups on my part... if you have the problems after RUU with stock s/w then I'd have to say its your phone. Good Luck.

rjhall said:
I have this weird problem, and I can't figure out the cause.
Whenever I use my phone lately, it will randomly freeze/force close certain apps. It's super laggy. If I drag my hand/palm across the touch screen, it will stop lagging and perform all the touch commands that I had "queued" up. This seems to persist even though I just wiped+flashed my phone again.
I've got nandroid backups for my stock hero, CM6.1.0, and now I just wiped and flashed to CM7.0.2. Sitting in the CM7.0.2 setup wizard as I type this, and it's lagging like crazy. Is it possible my Hero is internally damaged somehow and that's causing the problems, or does it sound like software? My Hero has been through a LOT of bumps, some harder than any phone should have to endure.
Still, I'm strapped for cash and making the best of what I've got. Anyone got any ideas? Is it possible that I screwed something up using the adb shell when I was a little nooblet? And that said, is there anyway to wipe everything and start with a completely clean slate?
Click to expand...
Click to collapse
First when a rom is starting up, it's likely to be SLOW, for 2 reasons, kernels need to "warm up" and the market is probably downloading a crapload of apps (this is a new feature). Second, it sounds like maybe you're device is running low on RAM, I would suggest you get an app from the market called "autokiller" and set the preset called "optimum". Third, go into settings/cm settings/performance and then set your governor to interactive 352-691 or ondemand 264-691. Fourth, go read a LOT of the threads in here and learn some stuff that will help you. Fifth, what recovery are you using and what exactly did you "wipe". Sixth, what do you mean could you have messed something up with adb shell?

il Duce said:
First when a rom is starting up, it's likely to be SLOW, for 2 reasons, kernels need to "warm up" and the market is probably downloading a crapload of apps (this is a new feature). Second, it sounds like maybe you're device is running low on RAM, I would suggest you get an app from the market called "autokiller" and set the preset called "optimum". Third, go into settings/cm settings/performance and then set your governor to interactive 352-691 or ondemand 264-691. Fourth, go read a LOT of the threads in here and learn some stuff that will help you. Fifth, what recovery are you using and what exactly did you "wipe". Sixth, what do you mean could you have messed something up with adb shell?
Click to expand...
Click to collapse
1. Yeah I know that. I hadn't had this problem until the last couple months. Until then, it was more or less okay. The problem is, it really is a completely fresh rom.
2. The Hero is kind of a low memory phone to begin with, so that's certainly a possibility. 2.2 and 2.3 aren't exactly kind on old hardware.
3. I don't have those settings in 6.1.0. I was using SetCPU for awhile with it at 480-7XX (Can't remember, I think 791, as that was max) and OnDemand. I had some screen off, temperature, and battery profiles too.
4. Any specific threads I should read you can suggest? I was lurking on the forums for awhile before I did anything to my phone (didn't want to brick it).
5. I'm currently using Amon RA 1.6.2. I considered clockwork, but some people said it has more problems. I've heard complaints that Amon RA requires signed packages, but frankly it hasn't been a problem thus far. It actually saved me from bricking my phone when I was new to this whole thing. As for what I wiped, I simply went through Amon RA and wiped data, dalvik, battery stats and rotation. Don't know what battery stats/rotation are, but I am familiar with the Dalvik cache.
6. As for saying I could have messed something up, when I was flashing my phone, it was something I'd never done before. It's certainly possible I mistyped something or screwed something up.
I was hoping someone could help me to completely wipe it and start fresh, since I'm sure it's had its share of problems.

I would suggest flashing clockwork. You can wipe more areas of the system then the one you have. And it has more features. I personally made the switch.
As for your lag, it might be your hardware. If you did a clean install and wiped boot, system, cache, data, and dalvik, and installed the latest stable release and it's still laggy? Then things are not looking good brother.
You experience the same thing on a sense base ROM?

also it could be cpu govenors because usually by default most roms have it set to ondemand witch has always caused problems for me and as soon as i set it to performance its fine.

Bierce22 said:
also it could be cpu govenors because usually by default most roms have it set to ondemand witch has always caused problems for me and as soon as i set it to performance its fine.
Click to expand...
Click to collapse
Are you aware that the performance governor runs at the MAX CPU speed all the time? Seriously. Your battery life must suck.
sent from a series of tubes.

yea but otherwise my performance sucks lol.
most of the time on aosp and cm7 i cant even stream music without it freezing unless i set it to performance.

Houndog101 said:
I'm new here but I've had a lot of different problems also. What I do is RUU and start over. It fixes a lot of screwups on my part... if you have the problems after RUU with stock s/w then I'd have to say its your phone. Good Luck.
Click to expand...
Click to collapse
What is RUU? How do I do this? I tried to search the forums but it said search was unavailable. Would this return the phone to 100% stock, no recovery software or anything? That's really what I'd like to do now, to make sure there's not a trace of rooting or flashing left, that way I can start from scratch.
oohaylima said:
I would suggest flashing clockwork. You can wipe more areas of the system then the one you have. And it has more features. I personally made the switch.
As for your lag, it might be your hardware. If you did a clean install and wiped boot, system, cache, data, and dalvik, and installed the latest stable release and it's still laggy? Then things are not looking good brother.
You experience the same thing on a sense base ROM?
Click to expand...
Click to collapse
I tried using RomManager to flash Clockwork, and it still booted to Amon RA recovery. I'm going to try to use ADB to do it, but I don't know that I'll be able to.
EDIT: Manually pushed ClockworkMod Recovery v2.5.0.7 onto my Hero.
Before I touch any of these settings, what will format boot, format system, formata data, and format cache do? Can it brick my phone, or will it let me flash a ROM onto a completely clean phone?

hmm thats very weird thats just about the only thing rom manager is good for now adays is installing cmr

rjhall said:
Before I touch any of these settings, what will format boot, format system, formata data, and format cache do? Can it brick my phone, or will it let me flash a ROM onto a completely clean phone?
Click to expand...
Click to collapse
You will not brick, that is how you wipe. You should also wipe dalvik cache. Go to this site for really good instructions :
www.romrepo.info/wiki

But please note when u wipe u "wipe" lol you will loose all your market apps and anything else installed just make sure you dont wipe sd card then youll loose all your photos and music backups exc...

rjhall said:
What is RUU? How do I do this? I tried to search the forums but it said search was unavailable. Would this return the phone to 100% stock, no recovery software or anything? That's really what I'd like to do now, to make sure there's not a trace of rooting or flashing left, that way I can start from scratch.
Click to expand...
Click to collapse
So I downloaded the 2.1 update from the HTC website, ran it, and it completed with no problems. Phone booted up, and now I'm trying to go through the tutorial, lagging all the while. It's almost impossible to type.
Does this mean it's hardware related?

sorry for not posting sooner but lagg isnt usually caused by hardware the kernal probably has to worm up also is it the 2.27 software update or 2.3 because 2.27 lagged pretty bad anyway and if your typing with vibrate on keypress try turning that of it always helped me.

Bierce22 said:
sorry for not posting sooner but lagg isnt usually caused by hardware the kernal probably has to worm up also is it the 2.27 software update or 2.3 because 2.27 lagged pretty bad anyway and if your typing with vibrate on keypress try turning that of it always helped me.
Click to expand...
Click to collapse
I had to start from scratch several times and my phone was pretty snappy when I first started it up after RUU. Also you stated your phone was fine and then just started running slow for no reason, was this after it took a bump?

are you talking to me or rjhall lol

Bierce22 said:
are you talking to me or rjhall lol
Click to expand...
Click to collapse
sorry, RJhall..

I don't recall it taking any bumps before it just stopped working like it has.
However, I have found how to "fix" the problem. If I squeeze the sides of the phone in, it stops lagging and works. Any touch motions of queued up will then immediately execute. Any idea what in the phone is physically broken?

rjhall said:
I don't recall it taking any bumps before it just stopped working like it has.
However, I have found how to "fix" the problem. If I squeeze the sides of the phone in, it stops lagging and works. Any touch motions of queued up will then immediately execute. Any idea what in the phone is physically broken?
Click to expand...
Click to collapse
Never had mine apart, maybe someone has and can help..

Okay so things have gotten increasingly weird. It used to be that squeezing the sides of the phone allowed the touch screen to work. Yesterday that stopped working altogether. Today, the screen stopped turning on at all. The LCD simply doesn't turn on. Pressing the red button turns on the phone (it vibrates when turning it on) and when the phone is on, pressing the red button lights up the keys (so I know it's waking the phone up). I took the phone apart (much simpler than I thought it would be) but I was unable to find anything that seemed out of place or broken. Does anyone have any ideas?

Annoying "Major" Startup FC Errors - Loking for Some Feedback

Alright I've searched through XDA, and I'm sure this has been covered before but I couldn't find it.
Problem:
Booted up my phone (i9000T) up this morning and it started vibrating (the FC vibrating type feedback), and I was getting all these .com.Android errors (from the keyboard, to internal Android errors, to Pandora, to the keyboard again ETC). Eventually it kicked me back to the initial setup screen and all those errors kept popping up. (The last apps that I installed were 2 days ago, Shazam and Soundhound from the market)
Finally I said "Screw it", reflashed my phone in Odin, repartitioned, and reinstalled everything (since I decided to format my SD in the Recovery Menu too which I forgot that my TiBu backup was on)
Is my phone/SD Card dying, or WTF is going on? & How common does this BS happen to you guys?
A little background:
I had 2 different i9000m (bell) phones that died from the internal SD errors. When they were dying they went through this same startup BS as what happened to my i9000T. Eventually on the next reboot they would go through the "boot loop of death".
So I decided to go the "i9000T" route because I got really tired of my i9000m phones dying. So of course I'm very concerned about WTF is going on with my i9000T (since that phone isn't supposed to have the SD issues like the Bell)
My current Setup:
i9000T
Running one of the stock Froyo Euro Roms (I9000XXJPU) for a couple of weeks now
Added the I9000B_JPA_JP3_JPA_JPA_modem_850.zip modem to get 3G
Rooted with CF
Apps I have apx 60 or so (all from the Android Market) mainly general BS stuff like Launcher Pro, Smart Keyboard Pro, TV Guide ETC...
I mean I really LOVE the Galaxy S phones, but none of this stuff crapping out ever happened when I owned a Milestone, Desire, or even my Atrix.
My first 2 i9000M phones lasted a month, and now this goofy error happened right around the month mark for my i9000T too, but haven't received the "boot loop of death yet?"
Right now things "appear" to be fine after I reinstalled all my apps and settings again from scratch.
So as my bold question above states:
Any ideas what could be going on with my phone, and is this that common of an issue for the Galaxy S users?...

So how often does a stock ROM crap out for no reason for you guys?...
Sent from my GT-I9000 using xda premium

I once had an error like that, which I thought was probably due to me messing up flashing in Odin. However, it hasn't recurred in a couple of months now, although I'm using the international I9000 and not the I9000T. Also, I've stopped formatting the internal SD during flash to increase its longevity, given I don't flash too often.

do you have a lot of apps installed ?
if yes check if datadata is full or not..

Chief_Death said:
do you have a lot of apps installed ?
if yes check if datadata is full or not..
Click to expand...
Click to collapse
I have exactly 60, with plenty of space available.
None of these errors are making any sense to me...
Sent from my GT-I9000 using xda premium

Clicking repartition doesn't do a factory reset and doesn't clean the cache data.. You need to do that in the 3 button recovery mode (Factory reset / Wipe cache data) in the On-Sound "-" and Home menu.

Did you do a factory reset before upgrading to ICS?

When I see all these posts about problems, I honestly can not relate at all because my TF101 with ICS literally has no problems at all. I've downloaded about 30 apps so far.
Other people who say they have no problems also usually mention that they did a factory reset before upgrading to ICS.
Just a coincidence?

I did and haven't had as many issues as others....some tho - tearing when expanding the recent app list, some random app crashes that I'm blaming on the apps....I did have a reboot cycle yesterday after waking up on battery from the dock...a cold boot remedied that.....other than that it's been a good update....

mines running smooooth as well, I did a full wipe so doing a factory rest didnt make sense to me. I'm running AR HD..
No factory reset for me and I'm good so far.. well I just got it back from Asus, I think they might have done one lol

sonspot said:
mines running smooooth as well, I did a full wipe so doing a factory rest didnt make sense to me. I'm running AR HD..
No factory reset for me and I'm good so far.. well I just got it back from Asus, I think they might have done one lol
Click to expand...
Click to collapse
full wipe does what factory reset does plus more.... so you did do factory reset. Can't believe you are taking it that literally.

horndroid said:
Did you do a factory reset before upgrading to ICS?
Click to expand...
Click to collapse
Nope. And I upgraded directly from a custom ROM.
100+ apps installed before the upgrade and running great afterwards: no random reboots, battery draining or app crashing. The only issue I have is with Chrome occasionally locking up. However I attribute that to its BETA status.
horndroid said:
Just a coincidence?
Click to expand...
Click to collapse
Perhaps ... perhaps not. A problem-free ICS upgrade, however, is not the sole provenance of those who factory reset/full wipe.
--L.

I did a full wipe when updating to ICS. Was fine for the first few days and now I have reboots/shutdowns maybe once a day. I had battery drain once as well. Its actually been pretty good other than that but I have kept it pretty standard with only a few apps as I am waiting for some better ROMS to come out with fixes.
Sent from my Transformer TF101 using Tapatalk

I did not wipe or factory reset. Have had one LOD 3 hours into sleep mode, one boot loop when I pulled out the SD card and one spontaneous reboot soon after coming out of sleep mode and rotating from landscape to portrait. Have had various Google app issues that are working themselves out.

I was prepared to wipe after I took the OTA, but haven't because I have had zero issues. I use my tf101 everyday, and it hasn't locked up or randomly rebooted once. I have about 60 apps installed.

Nope. I just hit update.
I've had the weird shutdown during sleep only once since first day update was available for USA.
Sent from my SGH-T959 using xda premium

I only had an error that Android media closed out something like that for the first few days after update.
Clearing caches in my music apps seemed to work at first. Now that is back and my tf had been shutting down while in sleep. Just put it down to sleep for about 20 mins came back to Android logo on the screen with the circle froze.
It seems like this is getting worse for mine. tried everything but a wipe. Stock has not been rooted.
have always been on stock since the beginning. Never had any major issues. Was considering rooting to get cornerstone when it is stable.
Until than what other options can fix the reboots.

For some reason on honeycomb downloading something or the honeycomb status bar would always flash and mess up. I downloaded lots of stuff and tweaked it so that might be why. I wiped after coming from revolver and went to stock ICS. When it updated it was crazy slow and laggy. After every app was restored from the market I reset it and it FLEW. It just flies in terms of speed.
When I did my titanium restore I restored EVERYTHING. Not just apps but system data as well. When I did that I noticed it was slower and laggy and that notifications and download gitch was present.
I did factory reset again and only restored the app data this time and it's perfect now. No more lag or anything. Titanium back ups are fine and everything but if you were currently having lag or weird problems restoring the system settings doesn't help. I did not need them anyways. I love ICS. I really love how we get the status/notification bar that the prime has. Also the sony tablet and other tablets now have the little box markers at the top which let you know what page you are on. I'm glad we get that now as part of ICS too.
Factory reset definitely helps. Also I got to see that cool droid restoration image when it was resetting everything. I have never seen that before and it looked awesome.

no factory reset, Everything working good

This thread is complete nonsense, and to prove it, I have two TF101 tablets here. One was wiped before *and* after the ICS update, and had almost nothing reinstalled on it. The other was not wiped before *or* after. There are pretty-much no programs installed in common on both. Both are experiencing random, spontaneous reboots. Both are experiencing lockups. I've yet to see a boot loop on the one that wasn't wiped, but that's just chance -- I'm quite certain if I left it long enough, it would boot loop too, just like the one that was wiped.
horndroid loves to try and suggest this is somehow a user problem, but it's not. It's a fundamental problem of the stock Asus ICS ROM.

My result;
Normal upgrade from HC to ICS = strange behauvor and reboots.
Factory reset and upgrade to ICS = works like a dream, no big complains...
After ICS I have notice that some times ( one or maybe two times a day) screen is flash /flickering - but only for a micro second. Statusbar sometimes flickering when open, but not a big deal...
I have about 200 apps installede, many from 2 parts Market ( read Aptoide)
---------- Post added at 08:21 AM ---------- Previous post was at 08:09 AM ----------
My result;
Normal upgrade from HC to ICS = strange behauvor and reboot.
Factory reset and upgrade to ICS = works like a dream!
After ICS I have notice that some times ( one or maybe two times a day) screen is flash /flickering for a micro second. Have you observed this?

knoxploration said:
This thread is complete nonsense, and to prove it, I have two TF101 tablets here. One was wiped before *and* after the ICS update, and had almost nothing reinstalled on it. The other was not wiped before *or* after. There are pretty-much no programs installed in common on both. Both are experiencing random, spontaneous reboots. Both are experiencing lockups. I've yet to see a boot loop on the one that wasn't wiped, but that's just chance -- I'm quite certain if I left it long enough, it would boot loop too, just like the one that was wiped.
horndroid loves to try and suggest this is somehow a user problem, but it's not. It's a fundamental problem of the stock Asus ICS ROM.
Click to expand...
Click to collapse
Yea it's definitely something that will be patched by Asus. I have the random reboots and the flickering screen.
Sent from my SAMSUNG-SGH-I997 using Tapatalk

I had a small problem when I updated my asus tf. Sometimes. when I pressed the home button, all the icons disappeard and I couldn´t do almost nothing with the launcher.
Then I decided to do a factory reset and now all is going well on my transformer

knoxploration said:
horndroid loves to try and suggest this is somehow a user problem, but it's not.
Click to expand...
Click to collapse
Yeah. It is hard not to notice this in about everyone of his replies. I am glad his works, but a growing majority of people it does not.
So i hope this anticipated fix which ASUS is rolling out NW fixes the probs-- Hum!! I seem to recall being called out as spreading rumors in another thread about the ASUS fix. - Well like i said the fix is on its way.

No wipe from rooted stock ... the odd second of screen flicker when running onskreen but nothing to cry about. All good really

My EEE Pad was running like **** (i.e. sleep of death, rapid drain, huge lag, random reboot) I have upgraded from stock 3.2 without performing factory reset.
I tried cold boot and that did not help anything.
So I took the plunge and did full wipe + cold boot. So far have not had a single issue. Just FYI.

Mine actually appears to be getting worse and worse, quickly. The stock apps are going o pieces. Google Maps repeatably crashes if I zoom in beyond a certain level, or if I enable the satellite view layer. Gmail is near-unusable -- email counts are frequently incorrect, or are correct but new emails that are visible through a web browser don't show up when you reload in the app, the app repeatably crashes when I click on certain email threads to view them, and randomly crashes at other times, sometimes within seconds of opening the app in the first place. Google Reader likewise often locks up, doesn't mark posts as read when you click on them, doesn't reload posts correctly, etc.
It's *only* the Google apps that are misbehaving; well, other than the OS itself regularly, randomly rebooting, freezing, or getting stuck in boot loops, this is.
And this is all on a stock, unrooted TF101 that has relatively few apps installed, and was wiped both before and after the ICS update.
Looks like when this new patch arrives, I'll be wiping and starting from scratch yet again, in the hopes of resolving this mess.