Develop Bugs

[Q] Why doesn't SetupWizard.apk fire up for me anymore?

I've apparently done something to my Epic and I can't figure out how to reverse it. Probably because I don't know what I did and/or when.
Since I got my Epic, every time I first boot it up after installing a ROM (whether it is custom or going back to a stock image), the Setup Wizard fires up, asks the usual questions, gets my google account info, and then automatically syncs my contacts and apps I've downloaded for the market. I've read plenty of posts where folks don't like this and will cancel the process so they can do it manually. Personally, I like that feature but it no longer works no matter what ROM I flash.
I first noticed it when I was on ViperRom 4.0.4. I wanted to upgrade to ViperRom 5, the newest release, and since I was on DK28 based rom, I wanted to first flash the stock EB13. It all went smooth as silk but when EB13 started for the first time, the Wizard didn't start asking me setup the phone for the first time. It just went straight to the stock launcher (TouchWiz I assume). And yes, I did all the custommary wiping of the 3 finger salute before I started. Bottom line, I just took mental note of it but moved on because EB13 was just a stepping stone for what I wanted to do. So, 3-finger salute, lotsa wiping, then flashed Synergy (ViperRom 5.0). Again, absolutely no problems. But again, the Setup Wizard didn't fire up. Hmmm...
So, I re-wipe, re-flash, and still no wizard. Grrrr... Since then, every rom I've installed/flashed has not once had the Setup Wizard fire up! WTH??? LOL. At the moment, I've Odined back to DI18 (just for the hell of it mainly). So I'm on DI18, RFS, not rooted, just like it came out of the box....no wizard?
What did I do? How do I re-enable the SetupWizard.apk (assuming that's what it is). I know the file is there in system/app because with every rom, I could use astro or root explorer and see that it is where it belongs. Of, course if I try to run it from one of the explorer apps, I get an error message, but doing a full wipe/restore to DI18 should have let the apk run, right? Have the permissions been altered to not let it run? Is this something I can correct with ADB?
Any help would be most appreciated and welcome.

The rom dev needs to enable it. It has been disabled by them
Sent from my SPH-D700 using Tapatalk

Yep the ROM devs have to enable it. Otherwise whenever you go to Market or GMail for the first time it will ask you to enter your Google information, (the Android Setup Wizard kicks in...)

I had thought that might be the case, but if they disable it, is it disabled forever?
When I installed ViperRom 4.0.4 (Trinity I believe, the last of their DK28 based roms), it was there and working. The wizard fired up after the first bootup of Trinity and everything went as normal as can be. I used Trinity, and only Trinity, until version 5 (Synergy) was released. I didn't flash/odin a single rom the entire time I was on 4.0.4 as it met all my needs. EB13 was released during this period but I resisted the temptation to try it figuring I'd wait until TPhillips released his next ROM (excellent job btw). So, the next thing I finally flashed (actually it was Odin) was EB13 since the dev's instructions said to be on EB13 before flashing Synergy (ViperRom 5.0). THAT is when it happened. When EB13 fired up for the very first time, no SetupWizard! But it was there for the previous ROM (ViperRom's Trinity 4.0.4) and gone when I went to EB13 a month or so later. So, by that reasoning, it was disabled in EB13 because that is the first time it didn't fire up. And, it hasn't fired up since. I've flashed 3 or 4 times since then, as recently as this morning when I Odined back to DI18, but the last time I saw the SetupWizard was when I installed Trinity (a month and a half ago I guess). I could understand custom rom dev's disabling it, but this happened when I Odined a stock EB13. I can't see Samsung and/or Sprint disabling it. And I know it was there on DI18, but it didn't fire off this morning.
Somewhere, I must have goofed something up, and I do believe I need to change a permission setting somewhere (the file is where it belongs), I'm just not sure what to do or even why it happened. When I odined the stock DI18, i would have thought that would reset every setting/permission/flag there was...but it didn't! So, I have to wonder is there anything else not properly "permissioned" since whatever this is has "stuck" through maybe half a dozen flashes & odin's...plus it started when I flashed a stock recovery.
To me atleast, this is really weird!?!
Thanks for the replies, I thanked you both. But, any other ideas?
Paul627g said:
Yep the ROM devs have to enable it. Otherwise whenever you go to Market or GMail for the first time it will ask you to enter your Google information, (the Android Setup Wizard kicks in...)
Click to expand...
Click to collapse
And for the record, I do know that when I go to the Market or Gmail the first time, I get to enter all my info and everything is fine. But, the ONLY time (that I know of anyway) that all of my previous apps (like 75 of them give or take) will automatically download and install is if I get that setup wizard to fire the very first time the phone starts up after a fresh install. If one cancels (or in my case doesn't get to do it), then I have to go to the market and install the stuff myself. Of course, I have both TitaniumBackup (pro version, I lbelieve in supporting the devs) and MyBackupRoot, so it's not like I'm screwed or anything, I just "LIKE" for it to be all automated...it just feels fresh that way! LOL.
This isn't like a huge problem, I'm just more curious as to what happened than anything else and wondering why odining back to stock (either DI18, DK28, or EB13) doesn't reset things to make this work like it should...

Samsung has it disabled. its been disabled since the phones release. Some devs enabled it for there custom roms for some time.
Sent from my SPH-D700 using Tapatalk

Well, that makes a lot more sense then. Because it was EB13 that was the first time I didn't see it. Just out of curiousity, what would I need to modify to make it work in a rom, or am I just pissing in the wind. For example, can I modify something in a rom (lets say Synergy from Team Viper since thats what I'm using at the moment), perhaps in ADB, before I flash it so that the apk fires up to start. Or, can I take the .apk's of my favorite apps and "drop" them in the rom (I know not to extract a rom from the zip file then re-zip it after making changes) so that they install with the rom when I flash it, like a ViperRom or Syndicate. They would go in the data/app folder, right? Or, just quit my *****ing and deal with it? LOL.
Really, mystery, thanks for your time...

Your just pissing in the wind so why don't you just stfu .
I'm not sure how to enable. I think its something in the build.prop. Your gonna have to ask a rom dev to get a def awnser.
As far as adding your own apps you can just add them to the data/app and they will automatically install when you flash the rom.
If your worried about your apps you can always try syndicate or bonsia. There script backs up the user apps then wipes everything. Once the rom installs it automatically restores your apps and phone to where it was before flashing.
Your welcome
Sent from my SPH-D700 using Tapatalk

SetupWizard was only one part of the process. They removed GoogleBackupTransport (the other part) in EB13. Even if you enable the SetUp Wizard in the build.prop, it won't restore any apps other than the ones you purchased. The googlebackuptransport.apk from DK28 is not compatible with EB13/EC05.

MysteryEmotionz said:
Your just pissing in the wind so why don't you just stfu .
Click to expand...
Click to collapse
LOL! Damn, I can't remember the last time I was b^tch slapped like that! Damn, that's what u get for thanking a guy (or gal) twice in one day!
OK, so I hit the brakes on the SetupWizard and dropped a pile of APK's that I like in the data/app folder. I had read before that one could do that with zip's flashed in CWM. Actually what I read talked about taking stuff out if you didn't want it (like when all the Sprint and/or Samsung apps were rolled into one big zip to flash, the OP had said just take out anything you didn't want), so I had figured the reverse was true and I could drop apk's in. I just wasn't sure about a ROM. Anyway, it worked perfect...
Oh, and Mystery...bite me!

Glad it worked for you and I have been some assistance.
I gladly will
Sent from my SPH-D700 using Tapatalk

mattallica76 said:
SetupWizard was only one part of the process. They removed GoogleBackupTransport (the other part) in EB13. Even if you enable the SetUp Wizard in the build.prop, it won't restore any apps other than the ones you purchased. The googlebackuptransport.apk from DK28 is not compatible with EB13/EC05.
Click to expand...
Click to collapse
You know I asked this question many of times to a few devs and everyone just said change the build.prop from DISABLED to OPTIONAL for SetupWizard. Which I did and I went as far as to decompile the setupwizard.apk to see that the coding was still there for the backup and restore but for the life of me I couldn't get it to function.
You are the first to come up with a different response saying the googlebackuptransport.apk, which makes perfect sense. Why nobody has ever taken the second to explain that further than the build.prop response I have no idea.
Thanks, at least my endless wondering of what happened between DK28 and EB13 now has a answer.

Paul627g said:
You know I asked this question many of times to a few devs and everyone just said change the build.prop from DISABLED to OPTIONAL for SetupWizard. Which I did and I went as far as to decompile the setupwizard.apk to see that the coding was still there for the backup and restore but for the life of me I couldn't get it to function.
You are the first to come up with a different response saying the googlebackuptransport.apk, which makes perfect sense. Why nobody has ever taken the second to explain that further than the build.prop response I have no idea.
Thanks, at least my endless wondering of what happened between DK28 and EB13 now has a answer.
Click to expand...
Click to collapse
No problem.

[Q] After flashing latest CM9, Nitro runs super slow. Even after reflashes.

After flashing the latest CM9 nightly, I turned on my phone and found that it is running incredibly slow. Like, it takes over 15 seconds to launch any app. I have reflashed different nightlys and HO!NO!'s rom but the problem persists. I have also checked to make sure that I don't have any CPU settings that are keeping the processor slow. I even restored a nandroid backup, it didn't help.
I have now done the following:
-Wiped Data/factory reset
-Wiped Cache
-Wiped Dalvik Cache
-Install from zip
It is still slow.
Is there something I am overlooking? Any idea what is going on?
EDIT:
This is a logcat(whittled down to ~400 lines) of the issue happening in kernalpanics rom. I had the dialer open, put phone to sleep, woke up phone, and immediately started dialing a number. The phone hangs for about 5-15 seconds, and "catches up" later. The log starts right after I woke the phone, so it should pop up at the beginning.
http://dl.dropbox.com/u/16882142/logcat-copy.txt
Here are two videos of the problem(sorry for the wmv):
CM9
GB Rom
Recap:
-I have formatted SD card and tried without SD
-I have tried with and without the SIM card
-I have flashed many different nandroid backups
-I have formatted everything and installed new Roms (I couldn't get HO!NO!s Rom working though)
-I am trying to follow the "unbrick methods" to flash stock firmware. I cannot get the flash to start though(Post)
-I am running out of ideas!

Sounds to me like you got a lemon. Look into this http://forum.xda-developers.com/showpost.php?p=24179363&postcount=4
Out of curiosity is it a phone from bell?

No, its from AT&T. It is actually a refurbished replacement to a new phone I got in December. I want to return it to factory settings but ADB will not recognize the LGP930. This is incredibly frustrating, when I try to install the drivers through LG software I manually put in my IMEI and it says "File not found"
Thank you for the reply, I really need to try to restore this thing.
EDIT: To reiterate, something is seriously messed up with this phone. It takes ~30 second to launch any app. IT will say the program is not responsding and I have to "wait" instead of close to get it to load.

Try formatting system partition then install CM9 again.

Thank you for taking the time Drumist. I have actually already reformatted /system then reinstalled a nightly. I just did it again and still, it is messed up. My main issue right now is that I can't even connect this damn phone to ADB, I can't try to replace this with CM9, rooted, and CWM.
Can anyone help with the driver issue. HO!NO! won't even install anymore, it just sticks on the LG logo. So I am stuck with CM9, but the drivers don't work. Everytime I hook it up to either of my computers, it will detect it as LGP930 for a split second, then try to find drivers, then it recognizes the device as 4 different devices! LGE Modem, LG USB Composite device, LG GPS, and unidentified device. Please, does anyone know how to get into ADB, I am desperate here.
I essentially have an unusable phone. Just to make a call I have to click on phone, then it hangs for about 30 seconds until it says the app is not responding and asks if I want to force close it. I have to select wait, then eventually the app will load. All list-views work fine so I can scroll the contact list. But when i select a contact I have to wait another 30 seconds.
I have searched and read this forum for hours on what to do about the drivers, but no luck.
Is it possible that this is the fesult of a corrupted file system?

My very limited troubleshooting skills with Android says you've either got a/some app(s) running that's soaking up all the CPU/System resources, or there's some major I/O issues going on with your phone (whether because of messing with the ROM or with Hardware is unknown).
Unfortunately you've also stated that you can't get ADB to work, which throws a big wrench in the works to get some debug logs.
If you haven't already tried, there's a very helpful thread on getting ADB working on the Nitro (via stock Google USB driver, not LG). I highly recommend doing those steps and get ADB working for further troubleshooting: http://forum.xda-developers.com/showthread.php?t=1601159
Another thing to try, for giggles, pull the SDCard out and see if there's any performance gain...Maybe you've got a hosed SDCard, or bent/bad pins in the SDCard slot (worth a shot anyway).
Good luck!

Namuna! Thanks for your reply.
I figured out it is somehow related to the SD card, THANK YOU! I actually tried removing the SD card yesterday when the problem first started, but the trick is I have to boot my phone up with no card in it. Once I put a card in, even if I take it out, the problem starts up again.
Since my phone ran out of battery hours ago, I am at work, and I left my cable at home; I cannot try the google drivers. I won't be geting home until late so I'm going to have to do some more experimenting tomorrow.

You don't need the Google drivers now. LG drivers are working again.

I remember that that is the case Malnilion, but I need to try something.
Bad news, apparently I jumped the gun because my phone is super slow again, with or without an SD card.
I just really need ADB access, a log would be a godsend.

I have found I can get to ADB when in CWM, but I can't get the drivers to work when in CM9 so I can't get a logcat.

Try to adb in recovery. Did you format that SD card?
Sent from my LG-P930 using XDA

I now have a version of kernalpan1cs rom running on my nitro. Almost everything runs fine, but the slowness happens when I try to make any phone call and with other random apps.
I have ADB now, and I am going to post a logcat of what happens when I try to dial a number using the phone app, then when I try to make a phone call.
I just need some help, I can look at the logcat when I do ADB logcat, but I have a hard time keeping track of when the problems happen. There are so many things that happen immediately after it that I cannot keep track of where the previous information was in the console window.
BTW, I notice that when the slowness happens when I dial a number in the phone app that the log reports a bunch of stuff about going into wakelocks and coming out of wakelocks. I thought this was kind of weird.

2 things.
1. I salute you for sticking with this phone through all the issues you've had (and still continue to have). I would've got the thing back as close to stock as possible and then exchanged it for another Nitro a long time ago. You've already done it once, it seems the refurb you got is also suffering some hardware issues...Might be time to do it again!
2. If you are dead set on chasing this rabbit down its' rabbit hole though, then I suggest getting acquainted with another debug tool called ddms (http://developer.android.com/guide/developing/debugging/ddms.html). It's a GUI based debugger that utilizes logcat, but is much more robust with tools for filtering and viewing associated processes.
Good luck!

Have you tried replacing the sim? Sounds like a shot sim to me.

beaups said:
Have you tried replacing the sim? Sounds like a shot sim to me.
Click to expand...
Click to collapse
This is a good point, especially if it's the same SIM that you used on your previous Nitro...Thereby bringing the issues with it!

Thanks guys! First off, I have exams going on so this has definitely taken the backburner, otherwise I would be on top of this.
@beaups: I'm pretty sure it isn't the SIM, when the SIM is out the slowness continues in either ROM.
@Namuna: I think I will give ddms a try once I have some time(hopefully this weekend). Thanks for the tip, I usually like getting my hands dirty
This is a logcat(whittled down to ~400 lines) of the issue happening in kernalpanics rom. I had the dialer open, put phone to sleep, woke up phone, and immediately started dialing a number. The phone hangs for about 5-15 seconds, and "catches up" later. The log starts right after I woke the phone, so it should pop up at the beginning.
http://dl.dropbox.com/u/16882142/logcat-copy.txt
Lastly, if I try to exchange this phone for another, what should I do in order to make it more factory-like? Install a stock ROM? Uninstall CWM?
EDIT:
Here are two videos of the problem(sorry for the wmv):
CM9
GB Rom

I also got the same thing here after updating the cm9 followed by a wipe data.. Tried all the things listed.. format system, gb roms.. Have you had any luck with the unbricking method?

I have same situation about the super slow after cm9. However, i fixed the problem after using the unbricking method. everything back to normal now. You can take a try. It seems like cm9 mess up some I/O address, cause it only slow down whenever you need to input or output from system.(Example: phone call, music ..etc)

did it
had the same problem, [Guide] Unbricking Solution for LG Nitro HD (P930) did it for me, back to usual speed

Yes, the unbricking solution worked for me, I just had to use the method in the original post once I worked out some driver issues.
I still am wondering what caused this though.

Problem with touch of blue 2.2

Sorry for putting this here, but do not have enough posts to reply to the official thread over in development forum.
I did a clean install of TOB after rerooting, getting S-off and downgrading to froyo then upgrading it back to gingerbread while retaining S-off. Seems I had to get S-off for custom roms to work correctly when verizon sent me a new phone due to the 2am loop boot happening every night for a week even doing a full wipe/factory reset.(they know it is a known issue and sent me a new phone as mine wouldnt stop looping. I installed the last RUU available to take it back to stock and it still did it.
Walked in the bedroom this morning and the softkeys lights were on, figured I had gotten a notification or update or something. Watched it for a few, when it went to the TOB boot animation. would get loaded to home screen, then the loading animation would start again, happened continuously over a 30 minute time frame before I finally pulled the battery to get it to stop. tried to use the phone as it loaded and it started to do it again. Going to attempt to get into recovery and fix permissions, format data/cache, and see if that fixes it.
Anyone else having that problem?
Also are there any mods like the older stock+ that wont show the darned nag screen about there being an update available?
Thank you in advance for any advice/help.
devnulled

Also wanted to ask if the verizaon backup assistant is/can be fixed? it FC's whenever I try to load it. When I try to sync contacts on the VZW website I get a few texts with junk characters but no more contacts. Already did a fix permissions in CWM recovery, and through CWM itself. Thanks again for your help. Will update if anything Ive done fixes the problems.
Devnulled

devnulled said:
Sorry for putting this here, but do not have enough posts to reply to the official thread over in development forum.
I did a clean install of TOB after rerooting, getting S-off and downgrading to froyo then upgrading it back to gingerbread while retaining S-off. Seems I had to get S-off for custom roms to work correctly when verizon sent me a new phone due to the 2am loop boot happening every night for a week even doing a full wipe/factory reset.(they know it is a known issue and sent me a new phone as mine wouldnt stop looping. I installed the last RUU available to take it back to stock and it still did it.
Walked in the bedroom this morning and the softkeys lights were on, figured I had gotten a notification or update or something. Watched it for a few, when it went to the TOB boot animation. would get loaded to home screen, then the loading animation would start again, happened continuously over a 30 minute time frame before I finally pulled the battery to get it to stop. tried to use the phone as it loaded and it started to do it again. Going to attempt to get into recovery and fix permissions, format data/cache, and see if that fixes it.
Anyone else having that problem?
Also are there any mods like the older stock+ that wont show the darned nag screen about there being an update available?
Thank you in advance for any advice/help.
devnulled
Click to expand...
Click to collapse
The 2am reboots are not a phone issue, it is a known issue with the latest ota. I cant believe they would rather give you a new phone than to admit they sent out a messed up ota.
Try fixing permissions and wiping data as you said.
If 2.2 is installed you should not get a nag to update, as its based on the latest ota.

devnulled said:
Also wanted to ask if the verizaon backup assistant is/can be fixed? it FC's whenever I try to load it. When I try to sync contacts on the VZW website I get a few texts with junk characters but no more contacts. Already did a fix permissions in CWM recovery, and through CWM itself. Thanks again for your help. Will update if anything Ive done fixes the problems.
Devnulled
Click to expand...
Click to collapse
Vzw backup was removed from the rom as most people dont use it. If you want it back, flash this http://dinc.does-it.net/APKs/VZW_Backup.zip, thru recovery.

Thank you cmlusco,
clearing cache and fixing permissions has fixed it, sorry for saying there was a problem. Verizon almost got back 3 phones (an eris that i was given, my old palm pre plus, and my incredible) at the same time with a certified letter having me cancel my contract 6 months early when the phone started rebooting back around the 4th of july. They replaced it last summer/fall when they rolled out gingerbread and my phone got half of it installed when it locked up and would not finish the update but was enough there to lock it from being fixed by ruu even.
I agree that it was not the phone, I told tech support I had it rooted for different skins and roms and to fix buggy software and they suddenly wanted to send out a new phone under warranty. I think they just wanted to get out a phone that was a little harder to root and get s-off rather than fix what was obviously a software bug issue. the new phone was supposed to be fully updated, but it wasnt installed, was still on the prior OTA and had a helluva time getting it to accept a custom recovery to begin with. Would goto the white HTC screen, then flash once or twice and go black with white bars down each side. took 3x to get it to accept it and ended up having to flash an older version first .92 i think (was 3 weeks ago now).
I will flash the backup software this time as my contacts were all edited on the website. Thank you again for the best rom Ive played with in a long time.
(forgot to add when I asked about the mods, I meant in a stock rooted rom that was similar to the old stock+ in use/appearance, but didnt get a nag screen, not that touch of blue did not have it. sorry for the confusion)
devnulled

Apologies for resurrecting an old thread, but I'm experiencing this issue too.
Getting overnight boot loops on Touch Of Blue 2.2.
I can temporarily fix it by booting to recovery, then wiping cache and dalvik cache.
Unfortunately, this is a daily ritual since updating from Stock+
I wiped our phones per rom install instructions ("Wipe dalvik-cache and format everything in the mounts and storage menu except emmc and sdcard before flashing."), so I'm not sure what's going on.
Seems to correlate with any 'pushed' updates from the Google Play store, but that's just my personal observation...
Any new developments (or permanent resolutions) on this issue since it was reported before?

dibmem said:
Apologies for resurrecting an old thread, but I'm experiencing this issue too.
Getting overnight boot loops on Touch Of Blue 2.2.
I can temporarily fix it by booting to recovery, then wiping cache and dalvik cache.
Unfortunately, this is a daily ritual since updating from Stock+
I wiped our phones per rom install instructions ("Wipe dalvik-cache and format everything in the mounts and storage menu except emmc and sdcard before flashing."), so I'm not sure what's going on.
Seems to correlate with any 'pushed' updates from the Google Play store, but that's just my personal observation...
Any new developments (or permanent resolutions) on this issue since it was reported before?
Click to expand...
Click to collapse
No i looked into it, but couldnt figure out what was causing it. Tob is my daily driver and for some reason i have never gotten these reboots. It must have to do with a stock app that i have removed or something. Mabey gmail, i always remove that as i use maildroid. Wish i could be more help, i will install fresh and not remove anythimg and see if i get the reboots. Then it will be easier for me to trouble shoot.

cmlusco said:
No i looked into it, but couldnt figure out what was causing it. Tob is my daily driver and for some reason i have never gotten these reboots. It must have to do with a stock app that i have removed or something. Mabey gmail, i always remove that as i use maildroid. Wish i could be more help, i will install fresh and not remove anythimg and see if i get the reboots. Then it will be easier for me to trouble shoot.
Click to expand...
Click to collapse
Thanks for the reply... I wonder what's doing the damage - The dedicated Gmail isn't on my phone. My wife is running TOB as well with the same symptoms. She runs a lot more apps than I do and we were looking for the ext4 fix when I found TOB.
Maybe it's another app? Let me know if you want a list...
Planning to load your rooted stock this weekend and see how things go.
If, in the meantime, you need a guinea pig for any possible fixes, let me know - I don't mind installing stuff via recovery. I'm a little rusty on adb, but I could do that as well.

dibmem said:
Thanks for the reply! I saw your rooted stock build - Most likely will go with that.
I wonder what's doing the damage - I could pull Gmail off for the evening and see if mine is stable. My wife is running TOB as well with the same symptoms. We were looking for the ext4 fix when I found TOB.
If pulling Gmail doesn't work - I'll load your rooted stock and see how things go.
If you need a guinea pig for any possible fixes, let me know - I don't mind installing stuff via recovery. I'm a little rusty on adb, but I could do that as well.
Click to expand...
Click to collapse
You can just flash back to tob 1.3. Same thing just not based on 4.08.605.15. Still has all the same features and look.

cmlusco said:
You can just flash back to tob 1.3. Same thing just not based on 4.08.605.15. Still has all the same features and look.
Click to expand...
Click to collapse
Can I flash that build directly over 2.2 or do I need to do a full wipe beforehand?

dibmem said:
Can I flash that build directly over 2.2 or do I need to do a full wipe beforehand?
Click to expand...
Click to collapse
Just wipe dalvik-cache and the cache partition and flash over. I have done it before and had no issues. That being said, if stuff starts acting goofy you may need to wipe and flash from scratch.

cmlusco said:
Just wipe dalvik-cache and the cache partition and flash over. I have done it before and had no issues. That being said, if stuff starts acting goofy you may need to wipe and flash from scratch.
Click to expand...
Click to collapse
Loaded 1.3 per your instructions. Also flashed the stop OTA and stock unlock patches. All is well this morning. No symptoms of a reboot present.
Observations: I noticed when I updated my phone, upon reboot, it wanted to immediately update various software in Google Play.
Perhaps the whole lockup / reboot issue is directly related to how the market pulls down updates(?)... On 2.2, I was doing a morning ritual: I would install market app updates, boot to recovery and do the following: Wipe cache, then dalvik cache. (Last couple of days, I ran 'fix permissions' as well). The process, albeit slightly tedious, worked with varying success - yesterday, it took a few TOB boot screen boots before the phones were stable (wife and mine).
Today, all seems to be fine. After installing 1.3, I did all my updates last night - nothing new pulled down in the market for me.
My wife's phone had one pending update that I left to see if the phone was stable overnight - Still there this morning. So, no 2 am reboot.
Hope this helps with development in some way.
Thanks much for your help and input - I'll keep an eye out for a future build of TOB for problem child phones.
---------- Post added at 05:03 AM ---------- Previous post was at 04:48 AM ----------
cmlusco said:
Just wipe dalvik-cache and the cache partition and flash over. I have done it before and had no issues. That being said, if stuff starts acting goofy you may need to wipe and flash from scratch.
Click to expand...
Click to collapse
Any pointers on upgrading the radio? Currently on 2.15.00.07.28
(Not in a rush - I see there's a few warnings on bricking your phone - unfounded or true?)

dibmem said:
Loaded 1.3 per your instructions. Also flashed the stop OTA and stock unlock patches. All is well this morning. No symptoms of a reboot present.
Observations: I noticed when I updated my phone, upon reboot, it wanted to immediately update various software in Google Play.
Perhaps the whole lockup / reboot issue is directly related to how the market pulls down updates(?)... On 2.2, I was doing a morning ritual: I would install market app updates, boot to recovery and do the following: Wipe cache, then dalvik cache. (Last couple of days, I ran 'fix permissions' as well). The process, albeit slightly tedious, worked with varying success - yesterday, it took a few TOB boot screen boots before the phones were stable (wife and mine).
Today, all seems to be fine. After installing 1.3, I did all my updates last night - nothing new pulled down in the market for me.
My wife's phone had one pending update that I left to see if the phone was stable overnight - Still there this morning. So, no 2 am reboot.
Hope this helps with development in some way.
Thanks much for your help and input - I'll keep an eye out for a future build of TOB for problem child phones.
---------- Post added at 05:03 AM ---------- Previous post was at 04:48 AM ----------
Any pointers on upgrading the radio? Currently on 2.15.00.07.28
(Not in a rush - I see there's a few warnings on bricking your phone - unfounded or true?)
Click to expand...
Click to collapse
If your s-off you can flash just the radio thru hboot. If s-on you would have to do a whole ruu in order to upgrade it. A bad radio flash can brick a phone. That being said, i have done it many many times with no issues. Just make sure to verrify the md5 sum, and never interrupt or run out of juice while flashing.

cmlusco said:
If your s-off you can flash just the radio thru hboot. If s-on you would have to do a whole ruu in order to upgrade it. A bad radio flash can brick a phone. That being said, i have done it many many times with no issues. Just make sure to verrify the md5 sum, and never interrupt or run out of juice while flashing.
Click to expand...
Click to collapse
Results post: Ended up flashing TOB 1.3, radio 2.15.10.12.20, and CMW 5.0.2.0. Updating the radio via hboot ended up being very easy (as long as I verified md5 beforehand.) Our phones are stable overnight - no reboots. Signal sucks here at home, but seems to be slightly better - hopefully will be better around town. If not, there's plenty of other radio versions to try out.

[Q] Phone unusable after being plugged in overnight

This happens about once every two nights. I hit the power button and the lock screen comes up fine, i unlock it with the slider and then home screen starts flickering slowly and is completely unusable. Is this the dreaded redraw issue I've heard mentioned? A forum search doesn't bring up any solutions for this. Any idea what to look for in logcat?
This is on 28i running ICS 2.29, rooted/deodexed+ "bloatware removal script" from deodex forum. Phone works great throughout the entire day.

twent4 said:
This happens about once every two nights. I hit the power button and the lock screen comes up fine, i unlock it with the slider and then home screen starts flickering slowly and is completely unusable. Is this the dreaded redraw issue I've heard mentioned? A forum search doesn't bring up any solutions for this. Any idea what to look for in logcat?
This is on 28i running ICS 2.29, rooted/deodexed+ "bloatware removal script" from deodex forum. Phone works great throughout the entire day.
Click to expand...
Click to collapse
I've never heard of this dreaded redraw issue, nor have I had it happen to me. Maybe doing a fresh fw flash, and add customizations one by one, making a CWM back up as you add each mod. Then see where and why the issue starts. Here is my process:
1. Flash Firmware > Root > CWM
2. Make a CWM backup called something like: 29fw_clean_base--
3. install busybox and deodex
4. Make a CWM backup called: 29fw_clean_BB_DO--
5. Install init.d
6. Make a CWM backup
7. Then start adding my mods one by one maing backups as I go called 29fw_running"1,2,3, etc."--
8. Then I can go back and delete or archive CWM backups as to what I need. Always keeping the "clean_base" ready for use if need be.

jeriku said:
I've never heard of this dreaded redraw issue, nor have I had it happen to me. Maybe doing a fresh fw flash, and add customizations one by one, making a CWM back up as you add each mod. Then see where and why the issue starts. Here is my process:
1. Flash Firmware > Root > CWM
2. Make a CWM backup called something like: 29fw_clean_base--
3. install busybox and deodex
4. Make a CWM backup called: 29fw_clean_BB_DO--
5. Install init.d
6. Make a CWM backup
7. Then start adding my mods one by one maing backups as I go called 29fw_running"1,2,3, etc."--
8. Then I can go back and delete or archive CWM backups as to what I need. Always keeping the "clean_base" ready for use if need be.
Click to expand...
Click to collapse
Heh you're everywhere today man! I never even installed init.d, guessing this is for startup scripts or something? I will have to give reflashing a shot, odd thing is it was a fresh install from last week and i pretty much did the first 3 steps in that order.
Do you (or anyone who replies) have a good method for analyzing logcats? tools for proper syntax highlighting maybe? some app must do something in the middle of the night to cause this crap.
thanks

twent4 said:
Heh you're everywhere today man! I never even installed init.d, guessing this is for startup scripts or something? I will have to give reflashing a shot, odd thing is it was a fresh install from last week and i pretty much did the first 3 steps in that order.
Do you (or anyone who replies) have a good method for analyzing logcats? tools for proper syntax highlighting maybe? some app must do something in the middle of the night to cause this crap.
thanks
Click to expand...
Click to collapse
I know, since getting my LT28 I'm always checking the forum, lol.
Yes, init.d for start up / optimization scripts. It's most important to me for my led brightness script. I might suggest going back to the start and doing the bloat removal thing last. See what that gets you. I have not used that script and don't plan to. I'll remove manually what I know I want removed.
I have no knowledge on how to analyaze logcats, sorry.

twent4 said:
This happens about once every two nights. I hit the power button and the lock screen comes up fine, i unlock it with the slider and then home screen starts flickering slowly and is completely unusable. Is this the dreaded redraw issue I've heard mentioned? A forum search doesn't bring up any solutions for this. Any idea what to look for in logcat?
This is on 28i running ICS 2.29, rooted/deodexed+ "bloatware removal script" from deodex forum. Phone works great throughout the entire day.
Click to expand...
Click to collapse
I have two suggestions for you. 1}.Try going into settings>Security>Screenlock and choosing "None". This will reduce the memory usage and prolong battery life. 2).The second is to upgrade to the latest Calendar app if you use the calendar widget.
https://play.google.com/store/apps/...yLDEsImNvbS5nb29nbGUuYW5kcm9pZC5jYWxlbmRhciJd
I was having re-draw issues even on stock firmware with the old calendar / widget installed. I'm guessing this is software / memory management related issues with ICS. Could be wrong but my phone works better with the above settings / app.

Also, try the PIN lock. The slider lock screen is a hog.

I'm having the same problem. I changed to PIN screenlock but even there, I have to press each button slowly and wait for the phone to respond .. It's almost like the CPU is hung while charging .. any other idea's why this is happening? This is only happening to me while charging the phone.

I'd re flash the ftf so you'll lose root deodex and the scripts then give it a week see what happens if it works fine try rooting wait a week see what happens then deodex and see what happens
My guess is when you deodexed something got misplaced or formatted improperly and it screws up the phone while trying to unlock you may also want to boot into cwm mode clear cache dalvik and fix permissions. You never really want to install a bunch of changes at once because if one breaks the phone you cannot pinpoint the issue that's why I waited a few days before I deodexed after rooting
Sent from my LT28at using xda premium

Maybe this is a bug on ICS 2.29, that's what I'm on. Anyone seeing this on 1.19 ?

enrique71 said:
Maybe this is a bug on ICS 2.29, that's what I'm on. Anyone seeing this on 1.19 ?
Click to expand...
Click to collapse
Never had this problem. Never.
Sent from my Xperia ION on Cm9 using XDA Premium app.

Browser constantly crashing across multiple roms

My browser constantly crashes and I can't for the life of me figure out why, so I am turning to you guys for help with my first post. Here's what's up:
Within one minute of opening my browser, but often within a few seconds of browsing, the browser will crash. No dialog or anything, it just suddenly closes. Sometimes it will restore itself when I reopen it, sometimes not.
This has happened across multiple roms, including cm10(which I am on now) AOKP, Frostyjb etc. I've used all the wiping options in CWR including formating /sdcard but nothing has helped. I can't find anybody with a similar problem. Any ideas?

You didn't tell us which browser. Use a different one.

kaixo24 said:
My browser constantly crashes and I can't for the life of me figure out why, so I am turning to you guys for help with my first post. Here's what's up:
Within one minute of opening my browser, but often within a few seconds of browsing, the browser will crash. No dialog or anything, it just suddenly closes. Sometimes it will restore itself when I reopen it, sometimes not.
This has happened across multiple roms, including cm10(which I am on now) AOKP, Frostyjb etc. I've used all the wiping options in CWR including formating /sdcard but nothing has helped. I can't find anybody with a similar problem. Any ideas?
Click to expand...
Click to collapse
Goto: settings / apps / browser /
Clear the cache and data and if it says: un-install update try that too
boot in to recovery and wipe davik and cache and fix permissions
Worth a shot :/

WarlockW said:
Goto: settings / apps / browser /
Clear the cache and data and if it says: un-install update try that too
boot in to recovery and wipe davik and cache and fix permissions
Worth a shot :/
Click to expand...
Click to collapse
Tried all that before and tried it again just now. Seems to be a bit better for a minutes (no crashes) but within 5 minutes it starts crashing upon loading my homepage etc. It's strange because crashes of this nature never happened to me even when running highly experimental ROMs on my old Atrix 4g. Is it possible that there are some configuration files (say host files or something) that are not wiped by the factory reset in CWM and are tripping things up? I think I will try flashing a stock image using Odin (which should wipe everything on the phone, correct?) and see if that fixes things.
And I am talking about the stock browser. It's the best (usually) for me and I'm sure it shouldn't be acting like this. Chrome and firefox crash even on stable stock builds so I can't really tell from them, lol.

Flashing stock with odin would be my next suggestion.
But also, after your next flash, don't install anything. Go straight to the browser after boot and see how it acts.
Can you verify it happens on any network? 3G/4G or any wifi?
Sent from my SGH-T999 using xda app-developers app

DocHoliday77 said:
Flashing stock with odin would be my next suggestion.
But also, after your next flash, don't install anything. Go straight to the browser after boot and see how it acts.
Can you verify it happens on any network? 3G/4G or any wifi?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your help and sorry to bring this topic back up, but my phone is really driving me crazy. For the past week I have experimented with Odin flashing the stock firmware on to my phone (both ICS and the recent JB) as well as constant factory resetting, but nothing changes the behavior. Using an alternative browser like Firefox (it sure has improved) results in a more stable experience, but things that use the default browser like gmail and (I think) Facebook still crash all the time. Also, the unlock screen often is unresponsive upon waking the phone, which is shortly followed by a reboot.
This behavior happens even if I do a factory reset, flash the stock firmware and boot up straight to the browser without signing in to my Google account or doing anything else. It happens irrespective of the network I am using.
I know we aren't supposed to use the repartition feature in Odin, but is there a safe way to do it or otherwise wipe everything off the internal memory leaving only the download mode so I can really start from a clean slate? I really want to rule out any software problem. The thing is, I'm getting a Nexus 4 and want to sell my sIII (it's still in mint condition) but I can't ethically do it knowing that my phone is somewhat borked. please help!!

I bought my phone new in box off of Ebay because I wanted the blue color. What a mistake. Samsung and T-Mobile are rebuffing any warranty requests I make (I didn't trip the flash counter) because I don't have a receipt. It would seem strange that this is a hardware problem as everything else works fine, but could I be wrong?. Only the default browser and apps that use it exhibit this behavior. Anybody have any ideas on what is going on??
kaixo24 said:
Thanks for your help and sorry to bring this topic back up, but my phone is really driving me crazy. For the past week I have experimented with Odin flashing the stock firmware on to my phone (both ICS and the recent JB) as well as constant factory resetting, but nothing changes the behavior. Using an alternative browser like Firefox (it sure has improved) results in a more stable experience, but things that use the default browser like gmail and (I think) Facebook still crash all the time. Also, the unlock screen often is unresponsive upon waking the phone, which is shortly followed by a reboot.
This behavior happens even if I do a factory reset, flash the stock firmware and boot up straight to the browser without signing in to my Google account or doing anything else. It happens irrespective of the network I am using.
I know we aren't supposed to use the repartition feature in Odin, but is there a safe way to do it or otherwise wipe everything off the internal memory leaving only the download mode so I can really start from a clean slate? I really want to rule out any software problem. The thing is, I'm getting a Nexus 4 and want to sell my sIII (it's still in mint condition) but I can't ethically do it knowing that my phone is somewhat borked. please help!!
Click to expand...
Click to collapse