I've seen a post about this one in the EVO area, but not here amongst us SGS3 owners:
When I reboot my phone, it always goes through an "Android is updating, application xxx of 3xx" counting up - and takes two or three minutes every reboot.
Is this normal under ICS?
Hmm, I'd say this is Not normal. One of the big "selling points" of the gs3 and ICS is the quick boot time. For me it is very quick. Maybe u should try doing a factory reset and see if it stops this behavior??
Sent str8 from my half eaten Banilla Ice Cream Samich
ratledge said:
I've seen a post about this one in the EVO area, but not here amongst us SGS3 owners:
When I reboot my phone, it always goes through an "Android is updating, application xxx of 3xx" counting up - and takes two or three minutes every reboot.
Is this normal under ICS?
Click to expand...
Click to collapse
If you're rebooting your phone after you wipe your dalvik cache, than that is normal. Reason being is that it stores applications for optimization so that the OS can run more smoothly. When you wipe your dalvik, it clears them out, and then when you reboot, it rebuilds the cache for all applications. Just do a normal reboot without wiping anything and see if it still does it.
That is not normal if it is happening on every boot, only if you wipe your dalvik cache then yes it will update.
id_twin said:
If you're rebooting your phone after you wipe your dalvik cache, than that is normal. Reason being is that it stores applications for optimization so that the OS can run more smoothly. When you wipe your dalvik, it clears them out, and then when you reboot, it rebuilds the cache for all applications. Just do a normal reboot without wiping anything and see if it still does it.
Click to expand...
Click to collapse
Yep, just a simple reboot or even a fault / reboot does the same thing. I'm not wiping the Dalvik cache or anything. Happens every time I boot my phone, and I've noticed over the past few days that I never seem to go into 4G/LTE mode any more. Curious - I guess I've laid the hammer on it a bit too much.
Are you using a custom rom or rooted? Or are you completely stock?
Sent from my SCH-I535 using Tapatalk 2
ratledge said:
Yep, just a simple reboot or even a fault / reboot does the same thing. I'm not wiping the Dalvik cache or anything. Happens every time I boot my phone, and I've noticed over the past few days that I never seem to go into 4G/LTE mode any more. Curious - I guess I've laid the hammer on it a bit too much.
Click to expand...
Click to collapse
what rom r u using ????
with aokp there are setting to which the user can wipe cache and dalvik on every reboot
I read on another forum that a TitaniumBackup odex file may cause this on certain phones. Try uninstalling the apk and then re-install it.
krackerjac said:
what rom r u using ????
with aokp there are setting to which the user can wipe cache and dalvik on every reboot
Click to expand...
Click to collapse
Sure sounds like it. I'm using the "Route66" rooted ROM with the Invisiblek overclocking kernel in place of the recovery.
Most likely the overclock. i ran the stock rooted 66 with no issue. I also have titanium backup installed without that issue.
id_twin said:
I read on another forum that a TitaniumBackup odex file may cause this on certain phones. Try uninstalling the apk and then re-install it.
Click to expand...
Click to collapse
Worth a shot. I'll give it a rip and report back... Thanks!
hmmm... Uninstalled and replaced Titanium Backup, reflashed the stock recovery: no joy there. I'm still getting the rebuild every time I boot. I suppose when I have more time (read next weekend, I'm working 12 hours every day this weekend, then my niece is in town for a week), I'll blow it to hades and start over.
ratledge said:
hmmm... Uninstalled and replaced Titanium Backup, reflashed the stock recovery: no joy there. I'm still getting the rebuild every time I boot. I suppose when I have more time (read next weekend, I'm working 12 hours every day this weekend, then my niece is in town for a week), I'll blow it to hades and start over.
Click to expand...
Click to collapse
Oh, well - factory reset, re-route66, invisiblek's v2 overclocked kernel. I'm good, no "Android is updating..." every time, and no mo unlocked icon on the main screen.
I dunno what I did, but the Sammy din't like it!
Thanks, guys!
Related
It seems most are able to get the rom going without issue. Just curious if there is anything outside of the standard process before loading a fresh rom. I've wiped cache/data/dalvik multiple times as well as reinstalled multiple times to no avail. Will not get past the white HTC screen.
ulmerj79 said:
It seems most are able to get the rom going without issue. Just curious if there is anything outside of the standard process before loading a fresh rom. I've wiped cache/data/dalvik multiple times as well as reinstalled multiple times to no avail. Will not get past the white HTC screen.
Click to expand...
Click to collapse
I've had problems flashing to I tried various combinations. The one that worked for me was flash superwipe twice clear dalvik cache cache and data/factory reset on 4-ext recovery
Sent from my XxX Sense 4 HTC Thunderbolt
How long are you waiting? It could take a while....maybe 4-5 minutes???
jonah1234 said:
I've had problems flashing to I tried various combinations. The one that worked for me was flash superwipe twice clear dalvik cache cache and data/factory reset on 4-ext recovery
Sent from my XxX Sense 4 HTC Thunderbolt
Click to expand...
Click to collapse
Thanks, I had to go back to skyraider for the time being, but ill give that a shot later.
ulmerj79 said:
Thanks, I had to go back to skyraider for the time being, but ill give that a shot later.
Click to expand...
Click to collapse
U should do it the ROM is definitely worth it and also try redownloading u might have gotten a bad Download
Sent from my XxX Sense 4 HTC Thunderbolt
Lineside said:
How long are you waiting? It could take a while....maybe 4-5 minutes???
Click to expand...
Click to collapse
It sat for at least 10 minutes. I always let a fresh rom sit for awhile. It just never got to the splash screen.
format system, that is one thing that most people miss.
I always backup my stuff then format /cache, /system, /data, & /sdcard so the phone is completely fresh. Then I re-install my backup app and restore my backups to the sdcard. I realize that formatting the sdcard is not necessary, but I just prefer having my the phone completely fresh. Most of my data is in the "cloud" anyways, so very little needs to be restored.
Personally I never really wipe the /system, as it is done automatically before the ROM installs. I do wipe /cache, /data, and /dalvick 3 times, just to make sure it works. The ROMS install without a hiccup, now if I could just get the Wi-Fi to stop causing my phone to lock up.
My recommendation would be format system manually just in case cause I have always done that and never had issues with a rom install. Liquid Ics jmod is running o so smooth for me.
liquid thunderbolt ics
I've had my NT for quite a while now. Once I got it, I'm pretty sure I used the nook & zergy tool to root, and that's been it.
I've been on 1.4 forever, with CWM 5.5.04 as my recovery (on the emmc maybe? I don't need an sd to boot into it).
I've noticed that my stability has been declining, with random reboots here and there and rapid battery drain, so I decided it was time to get back to some flashing. I started with this http://forum.xda-developers.com/showthread.php?t=1494367, using the first 1.42 version as the others are dead. Everything loaded and booted fine, but it reboots with little provocation...you know, like, touching it, and may or may not go into a reboot cycle 3-4 times before chilling out. I still can't do much without triggering a reboot though. Search in the market? Reboot.
I attempted to restore using this http://forum.xda-developers.com/showthread.php?t=1402190, but it just boots right up normally. If I manually flash it it fails.
So, here I am with a non-bricked NT that doesn't do me much good, and I'm wondering how to get it back in order.
Are you wiping cache and dalvik cache from recovery?
Also, are the reboots occurring on battery power, or on charging as well?
Sent from my ST27i
I've done a data wipe and wiped the dalvik from cwm. I've not wiped the cache partition if that's what you're asking. Reboots are when it's unplugged or plugged.
n8w said:
I've done a data wipe and wiped the dalvik from cwm. I've not wiped the cache partition if that's what you're asking. Reboots are when it's unplugged or plugged.
Click to expand...
Click to collapse
Ok. Data wipe does wipe cache as well.
You could try a cm Rom to see if the problem persists, but if you are looking for warranty, better to stay on stock.
Also, if you pull last kernel message ( from /proc/kmsg) , some dev may be able to determine cause for reboot.
I think it's possible this is a hardware issue.
Sent from my ST27i
Thanks for jumping on this. I went ahead and wiped the cache partition, because "why not?" and I'll be damned, but I haven't had a reboot yet. Hitting search in the market was a sure trigger, and it's behaving well so far.
satan89 said:
Ok. Data wipe does wipe cache as well.
...
Click to expand...
Click to collapse
/Cache and /Data are two separate partitions on emmc, and unless something change in recent CWM/TWRP Recovery, there are separate menu options to wipe each of them.
/Data is typically used to hold user downloaded/installed apps, and should not need to be wiped except when upgrading to a different ROM or a different ROM version.
I really don't know much about how all that works, but for whatever reason, wiping the cache fixed my issue.
Sent from my DROID RAZR using Tapatalk 2
Hello,
Newbie here. Followed all instructions on the SuperNexus ROM and did the flash, hit reboot and now I have been waitong on a loading screen with a nice colourful X for around 20 mins...
How long do I wait?
Maybe try to reflash the rom. Don't know about Supernexus specificaly, but 20 minutes is in general too long for a reboot after flashing a rom.
Sent from the Matrix
BlandyDoes said:
Hello,
Newbie here. Followed all instructions on the SuperNexus ROM and did the flash, hit reboot and now I have been waitong on a loading screen with a nice colourful X for around 20 mins...
How long do I wait?
Click to expand...
Click to collapse
Reboot into recovery and wipe data/factory reset and then reboot and should boot to rom. As mentioned above 20 mins is generally too long, 5 mins usually max I would wait.
Whenever you flash a new rom you should wipe data/factory reset before flashing. Only times you shouldnt is if you're simply installing a rom update like a CM nightly etc. Rom/kernel cleaning scripts that you flash via cwm are also good for cleaning old crap and avoid issues. You can backup/restore all your apps/appdata with Titanium Backup Pro.
Even 5 minutes is a long time, the average bootscreen I get after flashing a new ROM is 2-3 minutes. 20 minutes is definately a boot loop. Just go back into CWM wipe data and reflash.
If you have information you don't want to wipe though then try and reflash the ROM you were previously on and boot up, or use a cleaning script to try and get past the bootloop. However, you're going to need to wipe at some point or it will be very unstable.
postfatal said:
Even 5 minutes is a long time, the average bootscreen I get after flashing a new ROM is 2-3 minutes.
Click to expand...
Click to collapse
I didnt say 5 mins is average, I said 5 mins would be the max I would wait before wiping/reflashing etc.
postfatal said:
20 minutes is definately a boot loop.
Click to expand...
Click to collapse
lol, no it isnt. A "bootloop" is when your device just keeps rebooting in a loop, ie goes to a logo/kernel screen reboots and goes back and does same, hence "loop". If its stuck on a screen for 20 mins its just stuck, not in a "loop".
postfatal said:
Just go back into CWM wipe data and reflash.
Click to expand...
Click to collapse
No real need to re-flash just yet as 9/10 you can simply wipe data, although flashing aswel wouldnt hurt.
postfatal said:
If you have information you don't want to wipe though then try and reflash the ROM you were previously on and boot up,
Click to expand...
Click to collapse
Or restore from backup user made. (If he had enough sense to make one).
Well then it's stuck, if I slipped up and said bootloop does it really matter, the effects are the same in that his device isn't working. If I wipe data I always reflash afterwards, and a backup would be a great suggestion, but given he is "newbie" and this is his first post, and he's obviously got about as much clue about these things as Inspector Clouseau in a coma, restore a backup probably isn't going to happen. If he does have a backup though (meaning he has some clue), why on earth has this thread ever been made?
I'm not really sure why you addressed me directly over some totally unimportant points but thanks, I like to write stuff.
postfatal said:
Well then it's stuck, if I slipped up and said bootloop does it really matter, the effects are the same in that his device isn't working. If I wipe data I always reflash afterwards, and a backup would be a great suggestion, but given he is "newbie" and this is his first post, and he's obviously got about as much clue about these things as Inspector Clouseau in a coma, restore a backup probably isn't going to happen. If he does have a backup though (meaning he has some clue), why on earth has this thread ever been made?
I'm not really sure why you addressed me directly over some totally unimportant points but thanks, I like to write stuff.
Click to expand...
Click to collapse
Nothing personal dude, was just that I was addressing the 5 minute thing so thought I would split it up a bit
I personally use cleaning scripts for rom/kernel before every flash now except for cm nightly updates.
Thanks to everyone who replied. Not sure why people end up arguing in these threads though. lol
In a nutshell I left it for over an hour just in case, then I turned it off and on, powered into recovery with CWM did the data wipe and then rebooted again into recovery to flash in the SuperNexus file and the Google Apps file. I did one at a time with a reboot after each file flash, that speeds up the process a lot. Took about 2 mins per flash to work.
This is awesome!
I tried CM a while back (WAY back, actually - pre-ICS) for the i717. It wasn't bad but after a while I went back to stock because for me it just 'felt' better. Hard to explain it other than that. In any case, I've been on full stock ever since and was happy with it.
Then Official JB comes out from the carrier and my phone is laggy as all hell and it's gotten to the point of royally pissing me off to the point that I'm considering my options.
My question is this: Do we know the cause of the lag? If so, is it fixable via custom kernel or something similar, or do I need to go to a whole separate ROM to get away from the problem (and are there any in particular that are recommended if that is the case)?
tigerknight said:
I tried CM a while back (WAY back, actually - pre-ICS) for the i717. It wasn't bad but after a while I went back to stock because for me it just 'felt' better. Hard to explain it other than that. In any case, I've been on full stock ever since and was happy with it.
Then Official JB comes out from the carrier and my phone is laggy as all hell and it's gotten to the point of royally pissing me off to the point that I'm considering my options.
My question is this: Do we know the cause of the lag? If so, is it fixable via custom kernel or something similar, or do I need to go to a whole separate ROM to get away from the problem (and are there any in particular that are recommended if that is the case)?
Click to expand...
Click to collapse
Check this thread out. It's titled slow 4.1.2
http://forum.xda-developers.com/showthread.php?t=2314464
440bro said:
Check this thread out. It's titled slow 4.1.2
http://forum.xda-developers.com/showthread.php?t=2314464
Click to expand...
Click to collapse
I've disabled a lot of apps, but I will go back and compare to that list and see about disabling some more that I may have missed. Thanks
tigerknight said:
I've disabled a lot of apps, but I will go back and compare to that list and see about disabling some more that I may have missed. Thanks
Click to expand...
Click to collapse
Have you done a factory data reset since the upgrade? That seems to clear up a lot of issues too.
440bro said:
Have you done a factory data reset since the upgrade? That seems to clear up a lot of issues too.
Click to expand...
Click to collapse
I don't recall, but if I had to venture a guess I'd say probably not. I followed the above thread to the 'slow 4.1.2' and disabled everything I could on that list and did a restart, not sure which one did the trick but now it's nice and speedy.Hoping it stays this quick and isn't just a factor of not a lot built up in memory yet. I'll try a factory reset if it bogs down again.
there could also be some existing apps that continue to run in the background.
you might either go into app manager and force close them and clear their cache individually
OR
maybe reboot phone every day or two. clearing any cache build up. kind of a preventative maintinence thing.
if you ventured new ROM, may I suggest Padawawn.
every phone is a bit different, but I have had the best results ever
4.2.2 ROMs perform better IMO. Good luck
™
i prefer stock as well and was also experiencing lag until i found the right setup for myphone. started out by debloating. then flashed phasekernel_jb.3 and use setcpu or whatever tuner app you prefer and set governor = fantasy/scheduler = sio/min = 384/max = 1728. all phones are different so you may need to try different settings to find what works for yours. i have not had any lag since.
Here is what worked for me. I had the same issue as you and posted it a while back. This also greatly increased my battery life. I suggest that if you are rooted go ahead and wipe the device - in fact do it twice! You will have to reinstall of you your apps but it got rid of all the lag and almost doubled my battery life.
geebee1932 said:
Here is what worked for me. I had the same issue as you and posted it a while back. This also greatly increased my battery life. I suggest that if you are rooted go ahead and wipe the device - in fact do it twice! You will have to reinstall of you your apps but it got rid of all the lag and almost doubled my battery life.
Click to expand...
Click to collapse
When you said "wipe", did you mean factory reset or TWRP wipe?
If TWRP, which one you wipe? I tried checking all selection and it wiped even the OS!
lanwarrior said:
When you said "wipe", did you mean factory reset or TWRP wipe?
If TWRP, which one you wipe? I tried checking all selection and it wiped even the OS!
Click to expand...
Click to collapse
You wipe the caches. If you wipe system, it will delete the OS and the data wipe will wipe your data of course.
Sent from my SAMSUNG-SGH-I717 using xda premium
briand.mooreg said:
You wipe the caches. If you wipe system, it will delete the OS and the data wipe will wipe your data of course.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
OK.
I am ready to do the factory reset twice. My Note is rooted and have SuperSU. If I factory reset, wouldn't it remove SuperSU also but NOT TWRP?
If yes, can I just install the SuperSU zip from TWRP? No need to re-root?
lanwarrior said:
OK.
I am ready to do the factory reset twice. My Note is rooted and have SuperSU. If I factory reset, wouldn't it remove SuperSU also but NOT TWRP?
If yes, can I just install the SuperSU zip from TWRP? No need to re-root?
Click to expand...
Click to collapse
You will have full root. I always wipe both caches, system and data when flashing a new ROM, its actually the preferred way.
Sent from my SAMSUNG-SGH-I717 using xda premium
briand.mooreg said:
You will have full root. I always wipe both caches, system and data when flashing a new ROM, its actually the preferred way.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Wait, I already have stock AT&T JB and rooted. I just want to fix the lag and not installing a new ROM. Do I really need to wipe system and data? Wouldn't that wipe the whole OS?
I did the factory reset and want to wipe both caches... errr.. what's the button combination to boot to TWRP? I use "Quick Boot" before..
lanwarrior said:
Wait, I already have stock AT&T JB and rooted. I just want to fix the lag and not installing a new ROM. Do I really need to wipe system and data? Wouldn't that wipe the whole OS?
I did the factory reset and want to wipe both caches... errr.. what's the button combination to boot to TWRP? I use "Quick Boot" before..
Click to expand...
Click to collapse
It can be done by pressing at the same time Volume up and Power buttons until the display lights up, which is when you have to release Power button, while at the same time you should keep pressing the Volume Up button.
If you wish to keep your current ROM DON'T wipe system.
Sent from my SAMSUNG-SGH-I717 using xda premium
lanwarrior said:
When you said "wipe", did you mean factory reset or TWRP wipe?
If TWRP, which one you wipe? I tried checking all selection and it wiped even the OS!
Click to expand...
Click to collapse
Just the normal wipe -the first one on the selection menu.
lanwarrior said:
Wait, I already have stock AT&T JB and rooted. I just want to fix the lag and not installing a new ROM. Do I really need to wipe system and data? Wouldn't that wipe the whole OS?
I did the factory reset and want to wipe both caches... errr.. what's the button combination to boot to TWRP? I use "Quick Boot" before..[/QUOTE
many people just disable the lock screen to fix lag
Click to expand...
Click to collapse
Whenever I use ANY rom that isn't based on stock I get random reboots. I'm currently on stock ics and really want to be able to run later versions of android. I can run padawan rom and blackstar perfectly fine without any random reboots but for other roms I somehow get random reboots. Am I flashing roms the wrong way or is something wrong with my phone?
Any help is appreciated!
shaftgobbler said:
Whenever I use ANY rom that isn't based on stock I get random reboots. I'm currently on stock ics and really want to be able to run later versions of android. I can run padawan rom and blackstar perfectly fine without any random reboots but for other roms I somehow get random reboots. Am I flashing roms the wrong way or is something wrong with my phone?
Any help is appreciated!
Click to expand...
Click to collapse
After flashing new ROM, did you wiped cache+dalvic cache and factory resetted your phone?
If not then do so, it'll be helpful for you.
Also try to clean flash your ROM, after wiping system and data.
PS: Also check the ROM your flashing is stable enough and don't have major bugs.
Regards,
hitman-xda
hitman-xda said:
After flashing new ROM, did you wiped cache+dalvic cache and factory resetted your phone?
If not then do so, it'll be helpful for you.
Also try to clean flash your ROM, after wiping system and data.
PS: Also check the ROM your flashing is stable enough and don't have major bugs.
Regards,
hitman-xda
Click to expand...
Click to collapse
I tried that many times lol but it still didn't help though. Might try again though.
shaftgobbler said:
I tried that many times lol but it still didn't help though. Might try again though.
Click to expand...
Click to collapse
Clean flash ROM > wipe cache+dalvic cache > reboot > flash gapps > wipe cache+dalvic cache > reboot > factory reset > reboot
Hope the above thing works
Regards,
hitman-xda
hitman-xda said:
Clean flash ROM > wipe cache+dalvic cache > reboot > flash gapps > wipe cache+dalvic cache > reboot > factory reset > reboot
Hope the above thing works
Regards,
hitman-xda
Click to expand...
Click to collapse
k will try when I have the chance I appreciate the help:good:
hitman-xda said:
Clean flash ROM > wipe cache+dalvic cache > reboot > flash gapps > wipe cache+dalvic cache > reboot > factory reset > reboot
Hope the above thing works
Regards,
hitman-xda
Click to expand...
Click to collapse
Order is incorrect. Factory reset, wipe cache and dalvic cache, flash ROM, flash a compatible gapps package, wipe cache and dalvic cache again, reboot system. Let rom fully boot. Only enter your wi-fi and google account info at this time (If asked) .Let settle for at least 10 minutes after boot before playing with your newly installed ROM. Best to use gimmeitorilltell's TWRP version 2.8.0.0 or possibly newer or most recent CWM. Use of incorrect gapps, or fiddling with a roms settings before letting it settle in will result in problems. Follow instructions/tips in the OP of the forum thread dedicated to your your chosen ROM.
Sent from my SAMSUNG-SGH-I717
developweb said:
Order is incorrect. Factory reset, wipe cache and dalvic cache, flash ROM, flash a compatible gapps package, wipe cache and dalvic cache again, reboot system. Let rom fully boot. Only enter your wi-fi and google account info at this time (If asked) .Let settle for at least 10 minutes after boot before playing with your newly installed ROM. Best to use gimmeitorilltell's TWRP version 2.8.0.0 or possibly newer or most recent CWM. Use of incorrect gapps, or fiddling with a roms settings before letting it settle in will result in problems. Follow instructions/tips in the OP of the forum thread dedicated to your your chosen ROM.
Sent from my SAMSUNG-SGH-I717
Click to expand...
Click to collapse
k will try that thanks guys for the help
Well I followed the steps exactly as told and I'm still getting random reboots. What shud I do next? I'm using beanstalk 4.3 since some of the kitkat Roma I use seem buggy and I can't get gaps to work on lollipop
shaftgobbler said:
Well I followed the steps exactly as told and I'm still getting random reboots. What shud I do next? I'm using beanstalk 4.3 since some of the kitkat Roma I use seem buggy and I can't get gaps to work on lollipop
Click to expand...
Click to collapse
Ok, I'll bite again....
Many who have had ongoing, unexplainable things going on with their phone recommend 1)a new or different battery (a fresh battery does wonders) or 2)wiping everything and going back to full stock....whatever shipped with your phone. Like a reset. Start over.
Edit: and lollipop gapps come in 5.0 and 5.1 and like I said earlier make sure you've got the right ones.
Sent from my SAMSUNG-SGH-I717
developweb said:
Ok, I'll bite again....
Many who have had ongoing, unexplainable things going on with their phone recommend 1)a new or different battery (a fresh battery does wonders) or 2)wiping everything and going back to full stock....whatever shipped with your phone. Like a reset. Start over.
Sent from my SAMSUNG-SGH-I717
Click to expand...
Click to collapse
I did both of those already. I'm currently using a new battery and went back to stock multiple times then returning to a rom. Nothing seemed to work.
developweb said:
Ok, I'll bite again....
Many who have had ongoing, unexplainable things going on with their phone recommend 1)a new or different battery (a fresh battery does wonders) or 2)wiping everything and going back to full stock....whatever shipped with your phone. Like a reset. Start over.
Edit: and lollipop gapps come in 5.0 and 5.1 and like I said earlier make sure you've got the right ones.
Sent from my SAMSUNG-SGH-I717
Click to expand...
Click to collapse
Well im not having random reboots now thanks for the help though I hope it stays this way. But I get reboots when changing cup speed and governor or stay in camera app for too long. Probably just the rom itself. Thanks all for the help! I'll tell if anything goes wrong:good: