I updated to Jelly Bean 4.1.1 using Eftrant's method and did a complete wipe, re-installed and setup every application/game from the market but I've noticed that when I access places like Apps under Settings menu, using programs like Quick App Manager, the phone freezes or hangs. This problem was pretty bad in 4.1 but 4.1.1 seems to have improved it just a bit (not freezing/restarting as much). I thought that this was an application specific problem but doesn't look like it. Anybody having the same issue and have a solution/workaround?
Just to be clear, when I was running ICS the phone did not have a single instance of Freeze or Restart, I've been using this phone since January, so, it is not a problem with my phone either, just with the Jelly Bean update and the issue doesn't happen all the time only sometimes.
Have you tried doing a factory reset and running it without very many apps to see if it helps?
I have the same problem with Stock 4.1.1. Nothing helps (Full Wipe, No own Apps installed, Wipe cache, etc.). It randomly occurs in Settings/Apps. The Phone freezes and needs 1 Minute - Then "Settings isn't responding. Do you want to close it?"
To reproduce the problem: Slide in Settings/Apps from "DOWNLOADED" to "RUNNING" to "ALL" and back - a few times. Sometime the phone freezes.
Does it freeze at all with no apps installed? Can you pinpoint the freezes to a certain type of thing you're doing?
martonikaj said:
Does it freeze at all with no apps installed? Can you pinpoint the freezes to a certain type of thing you're doing?
Click to expand...
Click to collapse
No, unfortunately not. With absolutely no apps installed the problem occurs less times but it is not gone. I think there is a bug.
---------- Post added at 09:36 AM ---------- Previous post was at 09:28 AM ----------
Can anyone try to reproduce the issue? It seems to occur only after a full wipe and some apps installed.
Slide in Settings/Apps from "DOWNLOADED" to "RUNNING" to "ALL" and back - a few times. Sometime the phone freezes.
It also happens when you try to clear data/clear cache of a certain application like Browser, Gmail, Gallery, or any of the stock apps. A mentioned earlier the frequency of the phone freezing reduces if there are no applications installed. This definitely seems to be a bug that occurs when a lot of data about all the applications is being pulled at once. You can replicate the issue if you install an app like Quick App Manager which scans all apps when the app is started.
wessonster said:
It also happens when you try to clear data/clear cache of a certain application like Browser, Gmail, Gallery, or any of the stock apps. A mentioned earlier the frequency of the phone freezing reduces if there are no applications installed. This definitely seems to be a bug that occurs when a lot of data about all the applications is being pulled at once. You can replicate the issue if you install an app like Quick App Manager which scans all apps when the app is started.
Click to expand...
Click to collapse
Thank you for the Info!
It was happening on my GN too. But now it's fine.
I used to flash 4.0.4 factory image and OTA to 4.1.1 many times(more than 6). It was fine without any app installed from google play. After about 60 apps, freeze in setting-apps. Jump in an app detail, back, in another, freeze.
Now it' OK. But unfortunately, I don't know which setting fixed it. I try a lot.
Do you use flipboard? Or any large number of fragment files in sdcard/android/ ? Try to clean. Set flipboard to use internal storage.
If freeze again, er.....the last method. wipe cache, factory reset, flash 4.0.4, install apps and then OTA 4.1.1. Instead of OTA 4.1.1 and then install apps.
hope you can understand my English, and this can help you.
bynature said:
It was happening on my GN too. But now it's fine.
I used to flash 4.0.4 factory image and OTA to 4.1.1 many times(more than 6). It was fine without any app installed from google play. After about 60 apps, freeze in setting-apps. Jump in an app detail, back, in another, freeze.
Now it' OK. But unfortunately, I don't know which setting fixed it. I try a lot.
Do you use flipboard? Or any large number of fragment files in sdcard/android/ ? Try to clean. Set flipboard to use internal storage.
If freeze again, er.....the last method. wipe cache, factory reset, flash 4.0.4, install apps and then OTA 4.1.1. Instead of OTA 4.1.1 and then install apps.
hope you can understand my English, and this can help you.
Click to expand...
Click to collapse
"install apps and then OTA 4.1.1. Instead of OTA 4.1.1 and then install apps" fix the problem but i want to use a Custom ROM....
The Issue is listed on: code.google.com/p/android/issues/detail?id=35101
It's weird. Such an easy freeze and so few reports about it.
bynature said:
It's weird. Such an easy freeze and so few reports about it.
Click to expand...
Click to collapse
Well I have the same problem. It generally happens to me after I delete apps via settings...apps.
enough to make me quit cell phones
Happens on my nexus constantly. Verizon has sent me two replacements, which I sent back because they did the same thing, with or without any apps installed. All have had 4.1.1. This problem does not occur on 4.0.4, which I have flashed to the devices after upgrading to 4.1.1 just to run some tests. There is clearly a bug in the vzw 4.1.1 update. It is very, very frustrating and happens regardless of the apps we try to force close, clear cache, etc. They do not have to be google apps as someone has posted. I can easily duplicate the issue and it has been witnessed by two different corporate locations across four reps. I hope we can get a flashable 4.1.2 update soon, I've tried a 4.1.2 rom briefly and have not had the phone freeze at all.
Happens to me. I re flashed the rom and all went wrll
Swyped on my Galaxy Nexus running AOKP with Franco Kernel
Logcat/dmesg or it didnt happen.
Sent from my i9250
bk201doesntexist said:
Logcat/dmesg or it didnt happen.
Sent from my i9250
Click to expand...
Click to collapse
Funny.
Though it seems that logcat doesn't even log the problem, the phone is frozen solid for a couple minutes when it does freeze. I'll pull a logcat.
Sent from my Galaxy Nexus using XDA Premium via Verizon Wireless
del
And dmesg?
You people think its easy to troubleshoot these "freezes", and come in here without anything other than "i've tried a few roms and it still happens"
Sent from my i9250
del
Related
Hi, everyone; adding to the flood of questions...
I've been having some issues after a reboot lately:
- a couple of my apps will disappear. Namely Line Runner and the Merriam Webster Dictionary. I did some searching on this earlier and people who have had similar problems said it was due to the apps being installed on SD. I moved them to the phone, which seemed to solve the problem, but:
- rebooting also seems to make me lose my latest Google Search and Maps updates. The market will prompt me to update these. These apps are already on the phone, so no clue how to fix that one. But the most annoying thing is:
- after reboot, several of my game apps will force close when I try to open them. It seems like it's the more processor-intense ones: Pew Pew, Osmos, Anomaly, World of Goo. I thought maybe it was because of the undervolting/underclocking settings I have (from GideonX), but the apps work fine (running quite smoothly) after I install them, as long as I don't reboot. As soon as I reboot, if I try to open them again I get FC. If I uninstall then reinstall, they run fine again.
Any ideas? I'm running Juggernaut 4.1 with faux's 009u kernel and, as I said above, Gideon's script. I tried one reboot back to faux's stock clock/voltage settings, but I still got FCs on the apps. Granted, I didn't try it again or give it time to settle in or anything.
Any thoughts, folks? Thanks!
fix permissions? fresh wipe and install? clear cache? fiddle around
Ah, forgot to mention. Tried all of the above (fix permissions, clear cache, reflashed ROM, even recovered to my pre-custom ROM backup and reflashed from there).
I did some more testing on this, and I think I've narrowed down the problem. I flashed back to stock voltage/clock settings under faux's kernel, then reinstalled one of the apps I had issues with (Osmos). Upon reboot it still ran okay. So it seems I won't get force closes after reboot IF the app was installed under stock settings.
Does anyone know why undervolting and/or underclocking would cause apps to force close only after reboot?
EDIT:
Well, never mind. I did some more testing, and what I thought worked last time didn't work again. Must have just gotten lucky that time. Sigh.
Try wiping your phone with darksides super wipe and clean flash a rom. Check the md5 sums to make sure youre not installing a bad download
Sent from my SGH-T989 using Tapatalk
Oh, wow, didn't even know about the existence of that tool. Will definitely give that a try when I have some free time this weekend. Hopefully I can report back with positive news.
Thanks!
Don't want to count my chickens, but using super wipe seems to have done the trick so far! Using super wipe before flashing Jugg 5.0 seems to have gotten rid of my problem of FC apps.
Thanks again!
Hi
I'm frustrated - my Galaxy Nexus just keeps on crashing, randomly. At first, I thought it had to do with non stable Roms like AOKP (build 23 or 25) or Codename Android (1.4.0). So I downgraded to Stock Rom 4.0.2 on my GSM system.
But it still keeps on crashing. With this, I mean that it reboots all of a sudden and I find myself back at the SIM PIN input screen.
With Codename Android and AOKP, it was so, that it hung "deeply". Ie. when I connected it to my Linux PC, nothing at all showed up in the syslog of the Linux system - normally, it shows that "something" got connected. Not even that happened. "Solution": remove battery…
Well… I know that this is a bit slim, but how/where might I start to debug the cause of the crashes?
I don't have any special hardware connected. Most often, it crashes, while I'm typing somewhere (Browsers (different ones: chrome, browser, dolphin), Google Mail, Google Talk, Google+). But it also happens, that it crashes in the middle of the night, when I'm certainly not typing.
How to debug?
About this phone:
My installed apps: on Google Docs or or pastehtml.com — I also tried trimming the list of installed apps down, but either I didn't trim enough, or it was in vain…
Well… As you might guess… I'm totally clueless…
Thanks,
Alexander
If you have the android development tools installed on ur computer, you could try just leaving the phone plugged in while the Logcat view is opened. Logcat displays a whole bunch of debug info which may help you out when the phone suddenly reboots itself.
Also when you downgraded the firmware to stock, did you also clear the cache partition? Have you tried doing a factory reset from the UI? Did you also downgrade your radio to stock? Things to keep in mind.
- chris
Hm.logcat. Most of the time, i am not near a computer, when it cradhes. Is there a way to continually store the logcat output on the device itself?
When i downgraded, i did a cache wipe. I also did cache wipes / factory resets, when i had the custom roms installed.
I also flashed the stock radio, yes. So that is not the reason, i would say.
It is also not related to the keyboard - i thought so first. So i switched from SlideIt to SwiftKeyX. No change. And it also crashes while i am not typing.
Alexander
If I were you, I'd go to complete stock. Stock rom, kernel, and radios. No extra apps and see if it's a hardware issue or not. But that's just me.
Well, loveubuntu, i see what youre saying, i really do, but this basically would mean, that i couldnt use the phone. And what good is a phone, that cannot be used?
I am already back to stock rom, stock kernel and stock radio.
Well if you're back to 100% stock, relocked and not rooted it could be one of two things. Hardware issue or an app.
Well, thanks, but it doesnt help much...
And, actually, it just occured to me, that it is.already known, that it mist be an app. Ive got the same crashes with custom rom/kernel and stock rom/kernel. This shows, that the crash isnt.related to rom/kernel.
But how to debug this? I cannot keep the smartphone connected to the pc to have logcat ru.ning all the time. When i am travelling, i just dont have a pc around...
Any ideas?
well ffs not 24 hours a day. They mean just plug it in and run a logcat while you're using it and try to force a crash. If you can capture a log of what happened when it crashed then you will know what's crashing it.
If you go back to 100% stock (as in, flash Google images) and it still crashes with no apps installed, its a hardware problem.
Uninstall your task killer while you're at at it...
I cannot force a crash - as I said, it happens randomly
As far as crash with no apps installed… Well… I guess it won't crash, because then I won't be using it. That advice really cannot be followed.
It's been suggested to relock and remove root. What would that do? Could that really have anything to do with it? Very hard to imagine.
Oh, why uninstall the Task Killer? Yes, it's installed, but not active (in the sense, that it does not kill any tasks automatically and I also don't usually kill tasks. System also crashed, when I didn't kill any tasks).
alexs77 said:
I cannot force a crash - as I said, it happens randomly
As far as crash with no apps installed… Well… I guess it won't crash, because then I won't be using it. That advice really cannot be followed.
It's been suggested to relock and remove root. What would that do? Could that really have anything to do with it? Very hard to imagine.
Oh, why uninstall the Task Killer? Yes, it's installed, but not active (in the sense, that it does not kill any tasks automatically and I also don't usually kill tasks. System also crashed, when I didn't kill any tasks).
Click to expand...
Click to collapse
re-locking and unrooting will help diagnose the problem as app related or hardware. You may have a lemon.
Also, if you know it's app related, then the solution is easy. Uninstall all the apps and start again. That's why I suggested a factory reset. You can factory reset being rooted and unlocked. You can backup with titanium backup first anything you may need or make a nandroid.
task killers cause these kinds of problems.
Had a very simler problem to this, on stock 4.0.2, tried rooting and installing custom rom to see if it fixed and didnt also lots of factory resets nothing helped! In the end i had to send it off to sammy, got it back same problem , off again they sent it back with the same problem , off AGAIN got it back on friday with ( oddly) a new screen and havent had a problem since.
My advice send it for repair, if its happening with different roms / stock or whatever its gotta be hardware
If you want a logcat that you dont need a pc for use " alogcat" free app from the market, helped me ( mine actually had hardware error on the logcat )
Hi all,
For past few days i have been getting the strange issue. When i turn on my phone nothing would come and only black screen would show up. Then after few seconds i get message saying "launcher is not responding"...
I have tried both stock and nova launcher but same issue. I reflashed stock rom again and still same problem.
My Rom: ICS 4.0.2 Stock and stock kernel.
I want to keep stock rom so what is the solution? Why does this happen? Thanks
hp13 said:
Hi all,
For past few days i have been getting the strange issue. When i turn on my phone nothing would come and only black screen would show up. Then after few seconds i get message saying "launcher is not responding"...
I have tried both stock and nova launcher but same issue. I reflashed stock rom again and still same problem.
My Rom: ICS 4.0.2 Stock and stock kernel.
I want to keep stock rom so what is the solution? Why does this happen? Thanks
Click to expand...
Click to collapse
did you at any point between flashes, factory reseted the device?
did you try clearing app data/cache?
concerning nova launcher, you should post this under its related thread
concerning stock launcher, you should try and reach [email protected] groups
people flash all kinds of stuff but one ANR (application not responding) comes along and all hell breaks loose. get adb logcat when you're booting up/entering Android UI.
i can't wipe data or cache as i have stock recovery.I don't have CWM. i will upload the logcat soon. Thanks
hp13 said:
i can't wipe data or cache as i have stock recovery.I don't have CWM. i will upload the logcat soon. Thanks
Click to expand...
Click to collapse
if you press up (or up+power) on stock recovery, it will give you a recovery menu if i'm not mistaken (i may not recall it correctly).
and i was talking about the app data/cache that you clear in Settings > Apps as well, not just the ones in recovery.
bk201doesntexist said:
if you press up (or up+power) on stock recovery, it will give you a recovery menu if i'm not mistaken (i may not recall it correctly).
and i was talking about the app data/cache that you clear in Settings > Apps as well, not just the ones in recovery.
Click to expand...
Click to collapse
Here is the Logcat. I already wiped everything when i flashed stock rom 4.0.2 with XXKK6.
Launcher not Responding
I'm getting a similar problem with my new Galaxy Nexus. I'm running stock ICS 4.0.1, kernel 3.0.1 on the bell mobility network. I've installed a few apps, but nothing which seems too unpopular. Here is the list I had installed when the launcher was performing flawlessly:
Swype Keyboard
Draw Free
Bell Mobile TV
Volume+
Here's what I've installed recently since launcher has become unstable:
Flashlight v. 1.3.0
Skype
StumbleUpon
TED
Sudoku Free
Here's whats been installed since:
Tip n Split
Antivirus Free
RealCalc
Quite regularly I am getting the "Launcher is not responding" message with a request to wait, report, or close the launcher. The home screen will lock up temporarily and none of the buttons will become usable. I've checked the ram usage, and it is holding at around 400mb. Clearing a bunch of apps from the cache or running screen does not change the frequency of freezes. I have also tried resetting the Nexus to factory defaults without any new apps, but it only took about an hour before I got the 'Launcher is not responding' message.
Anyone have any ideas for re-stabilizing ICS?
Thanks!
There is a part in the logcat talking about a channel that is unrecoverably broken... seems 1 of the fc's, power outage or something else left a file half written in your system.
Try performing a factory reset (which will wipe all userdata and give you a clean system)
if this doesn't work and you've had your phone unlocked reflash the system, boot and recovery again (using fastboot) (how to do that is explained here: http://forum.xda-developers.com/showthread.php?t=1391881 )
If you have not tempered wit the system in any way (not rooted, no custom roms and no custom recovery) send it back to the store and get it fixed under warranty. When you can't or don't want to contact your seller proceed with reflashing your system at your own risk.
Sent from my Galaxy Nexus using XDA
I'd been using FF18 for quite a while without incident, but after upgrading to FI27 (not OTA, via the one-click method), Google Play is hanging the system immediately after successfully downloading and installing any given app. It puts me on the usual page allowing me to open the app, I press open, and wham, the system freezes until it reboots automatically about a minute later. The app that I installed then runs fine.
(In testing this several times, I should mention that one time I actually was able to open an app I just installed, but it hung about 10 seconds in, and the system rebooted as usual. It ran fine after that.)
I've searched around a bit for this and see that I'm hardly the first to encounter this issue. Sometimes it occurs when no recent update has been performed at all. Unfortunately, I haven't really found a solution yet. The best I've seen is to delete the data for Google Play and Download manager, and rebooting, which I've done to no effect. I've also tried uninstalling Google Play, but I think in this case that just leaves me with the same version that I had, the one that came with FI27 (in any case, that didn't help either).
How does one go about troubleshooting this type of problem? I suppose wiping out the phone and starting over would fix it, but I was hoping for more of a surgical rather than nuclear approach. After all, on a PC, you don't reformat when you have a problem with a program.
Have you tried wiping the data for google services framework?
sent from MY BAD A$$ ET4G
patrao_n said:
Have you tried wiping the data for google services framework?
Click to expand...
Click to collapse
I hadn't, but I did just now (there was just over 4MB there), along with a reboot following, and unfortunately it didn't help. Maybe Google Play services too, or something else?
Try deleting data for anything that says google play.
sent from MY BAD A$$ ET4G
You stated you upgraded so I'm assuming you didn't do a fresh install. Even if you did do a fresh install, restoring data & apps from an older version could cause problems. You should try a fresh load and work your way back from there.
Edit: Saw you did the one-click. Still think you should try a full wipe and try it again with a fresh load to see how it goes.
patrao_n said:
Try deleting data for anything that says google play.
Click to expand...
Click to collapse
I've now done that (though one or two had no data), along with the framework one you mentioned earlier, followed by a reboot, but it still happens. Arghh!
tdunham said:
You stated you upgraded so I'm assuming you didn't do a fresh install. Even if you did do a fresh install, restoring data & apps from an older version could cause problems. You should try a fresh load and work your way back from there.
Edit: Saw you did the one-click. Still think you should try a full wipe and try it again with a fresh load to see how it goes.
Click to expand...
Click to collapse
Yes, I chose the nodata FI27, since it said that it was good for same-version or upgrades (in this case, ICS to ICS), but I will choose the nuke-from-space one if there's no way out of this, though wouldn't just resetting to factory defaults at this point do the same thing?
It's a little bit disturbing that an issue with one app, albeit an important (though not essential) one, can require wiping the phone. If this were to come up again for some reason, maybe just one day out of the blue and not related to putting on a new ROM, it would be nice to know a way out.
Perhaps I can grab a log from somewhere with ADB?
rseiler said:
I've now done that (though one or two had no data), along with the framework one you mentioned earlier, followed by a reboot, but it still happens. Arghh!
Yes, I chose the nodata FI27, since it said that it was good for same-version or upgrades (in this case, ICS to ICS), but I will choose the nuke-from-space one if there's no way out of this, though wouldn't just resetting to factory defaults at this point do the same thing?
It's a little bit disturbing that an issue with one app, albeit an important (though not essential) one, can require wiping the phone. If this were to come up again for some reason, maybe just one day out of the blue and not related to putting on a new ROM, it would be nice to know a way out.
Perhaps I can grab a log from somewhere with ADB?
Click to expand...
Click to collapse
If you have a custom kernel with recovery make a backup. Or get one and do it and then do a full wipe and fresh load. That is the only way you'll know for sure.
Yes, I will, but I thought I'd live with it a while to see what I could learn.
I've found that opening the newly-installed app is not the issue: simply installing a new app is. If I wait on the "Open" screen right after an install, and do nothing, within a minute the system will freeze and reboot.
Interestingly, updating apps does not trigger the problem, as numerous apps have updated this week, even one that Google Play wanted me to approve manually. Go figure.
Anyway, I have a logcat of an example in case anyone is interested. In this case, I initiated an install at 15:26, which is when the log begins. It ends shortly after the reboot.
http://tny.cz/0b86937c
I flashed my Galaxy Nexus last night to rooted 4.2 rom found here: http://goo.im/devs/bigxie/maguro/bigxie_maguro_OTA_JOP40C_odexed-signed.zip
The upgrade went smoothly. Not hiccups whatsoever. In less than 15 minutes I'm on 4.2 and rooted. I installed TitanumBackup, restored my apps/settings from my previous setup. That's when things started to go wonky:
First, HD widget doesn't work. It stuck in "loading...". I removed the widget, thinking that it might require an update from the devs.
Then, things started to become sluggish. I was on Nova Prime launcher. Very often it stops responding, and after a while, it shows the "Not responding...close/report/wait" dialog. I chose 'close' and the screen would go blank. I cannot wake it up using the power button or anything. I had to pull the battery out.
I thought it was the problem with the Nova launcher. After the restart, I switched to the stock launcher. It was noticeably faster, but when I launcher apps, even the App store, it would not respond again.
Does anyone have a similar experience?
kevinjqiu said:
I flashed my Galaxy Nexus last night to rooted 4.2 rom found here: http://goo.im/devs/bigxie/maguro/bigxie_maguro_OTA_JOP40C_odexed-signed.zip
The upgrade went smoothly. Not hiccups whatsoever. In less than 15 minutes I'm on 4.2 and rooted. I installed TitanumBackup, restored my apps/settings from my previous setup. That's when things started to go wonky:
First, HD widget doesn't work. It stuck in "loading...". I removed the widget, thinking that it might require an update from the devs.
Then, things started to become sluggish. I was on Nova Prime launcher. Very often it stops responding, and after a while, it shows the "Not responding...close/report/wait" dialog. I chose 'close' and the screen would go blank. I cannot wake it up using the power button or anything. I had to pull the battery out.
I thought it was the problem with the Nova launcher. After the restart, I switched to the stock launcher. It was noticeably faster, but when I launcher apps, even the App store, it would not respond again.
Does anyone have a similar experience?
Click to expand...
Click to collapse
Ahh that sucks man. I am not really a heavy user, but i am sure you are not the only with problems :fingers-crossed:
Especially from updated OS versions, only restore apps from TiBu. No data or system stuff. That's when problems start. Just restore apps no data, re-log in and see if problems persist.
Do a full wipe and try a different ROM. Or try that same ROM before restoring your apps and data. I haven't had any freezes or force closes since I flashed 4.2
kevinjqiu said:
I flashed my Galaxy Nexus last night to rooted 4.2 rom found here: http://goo.im/devs/bigxie/maguro/bigxie_maguro_OTA_JOP40C_odexed-signed.zip
The upgrade went smoothly. Not hiccups whatsoever. In less than 15 minutes I'm on 4.2 and rooted. I installed TitanumBackup, restored my apps/settings from my previous setup. That's when things started to go wonky:
First, HD widget doesn't work. It stuck in "loading...". I removed the widget, thinking that it might require an update from the devs.
Then, things started to become sluggish. I was on Nova Prime launcher. Very often it stops responding, and after a while, it shows the "Not responding...close/report/wait" dialog. I chose 'close' and the screen would go blank. I cannot wake it up using the power button or anything. I had to pull the battery out.
I thought it was the problem with the Nova launcher. After the restart, I switched to the stock launcher. It was noticeably faster, but when I launcher apps, even the App store, it would not respond again.
Does anyone have a similar experience?
Click to expand...
Click to collapse
If you did a Titanium Backup restore with Data you're going to need to do a complete wipe and re-flash. You can restore apps between different ROMs usually, but restoring data from one ROM to another different one is almost always going to give you trouble. Just do a clean install and restore app only, you should be good to go.
Sent from my Galaxy Nexus using xda premium
Before I flashed 4.2, I did both clean dalvik cache and clean data partition. I'm going to reflash this and only restore apps. Will it restore my settings if I chose not to restore data? I guess I'll find out.
No, unfortunately it isn't going to do any settings. Not sure how complex your setup is but I can usually have everything back to the way I like it in 20-30 minutes after a clean flash.
Sent from my Galaxy Nexus using xda premium
kevinjqiu said:
I flashed my Galaxy Nexus last night to rooted 4.2 rom found here: http://goo.im/devs/bigxie/maguro/bigxie_maguro_OTA_JOP40C_odexed-signed.zip
The upgrade went smoothly. Not hiccups whatsoever. In less than 15 minutes I'm on 4.2 and rooted. I installed TitanumBackup, restored my apps/settings from my previous setup. That's when things started to go wonky:
First, HD widget doesn't work. It stuck in "loading...". I removed the widget, thinking that it might require an update from the devs.
Then, things started to become sluggish. I was on Nova Prime launcher. Very often it stops responding, and after a while, it shows the "Not responding...close/report/wait" dialog. I chose 'close' and the screen would go blank. I cannot wake it up using the power button or anything. I had to pull the battery out.
I thought it was the problem with the Nova launcher. After the restart, I switched to the stock launcher. It was noticeably faster, but when I launcher apps, even the App store, it would not respond again.
Does anyone have a similar experience?
Click to expand...
Click to collapse
You shouldn't have used Titanium Backup going from one OS release to another...
akira02rex said:
You shouldn't have used Titanium Backup going from one OS release to another...
Click to expand...
Click to collapse
I thought that's the point of Titanium Backup. Maybe from 4.1.1 to 4.2 is too big a jump?
I did notice that on 4.2, the media partition is moved from /data/media to /data/sdcard/0. There are extra /data/sdcard/legacy and /data/sdcard/obb directories now. Not sure if it's related.
kevinjqiu said:
I thought that's the point of Titanium Backup. Maybe from 4.1.1 to 4.2 is too big a jump?
I did notice that on 4.2, the media partition is moved from /data/media to /data/sdcard/0. There are extra /data/sdcard/legacy and /data/sdcard/obb directories now. Not sure if it's related.
Click to expand...
Click to collapse
You can move or copy your /android/data and /data folders from sdcard/0 to your /sdcard folder and the apps should pick up their data again.
Definitely the problem has to do with titanium backup, I used to have those kind of issues before when I had my s2, I would recommend a fresh install of jelly bean 4.2 (factory image) and reinstall all the apps from your preferred markets.
You could try to fix permissions also, just to see if the forced closes stop
Sent from my Nexus Prime JB 4.2
Well i wiped dalvik etc flashed the restored some apps and data with titanium and evthing been flawless so far, so it could be something else, did u wipe cache etc before you flashed. NB also came from 4.1
fallensoldier said:
Well i wiped dalvik etc flashed the restored some apps and data with titanium and evthing been flawless so far, so it could be something else, did u wipe cache etc before you flashed. NB also came from 4.1
Click to expand...
Click to collapse
I did wipe out the dalvik cache. I ended up reflashed the ROM and only restore the app data one by one, skipping over the ones I suspect might be a problem. It's all running smoothly now.
Sent from my Galaxy Nexus using xda app-developers app