I know it is experimental, but I'm running CM11 20140714-UNOFFICIAL and posts in the developers forum says that ART works well on it, so I thought I'd give it a try. I went to settings, developer options, select runtime and chose ART. The phone rebooted, did a phone is upgrading / reoptimizing 122 apps and when it finished, I got that:
"unfortunately com.android.phone has crashed"
When I checked "ok" the same message pops. Repeat. I rebooted and phone and it did re-optimization on 22 appls. But still the loop of crashes, maybe 80% are the com.android.phone, but I also get com.android.gapps and com.android.acore and other apps (youtube, etc). I tried booting into recovery mode and wiping the cache davlik cache and cache, but same problem. I was able to switch back to davlik (when you press ok after a crash, 20% of the time you get a half-second window to do something and I was eventually able to get to settings, etc). That caused the phone to crash on startup, but wiping the cache cleared that. So now I'm back where I started.
But it seems like other people having gotten ART working on the 20140714 CM11 build. Did I do something wrong when switching to ART? Anything else to try?
Thanks,
Ben
exhibit679 said:
I know it is experimental, but I'm running CM11 20140714-UNOFFICIAL and posts in the developers forum says that ART works well on it, so I thought I'd give it a try. I went to settings, developer options, select runtime and chose ART. The phone rebooted, did a phone is upgrading / reoptimizing 122 apps and when it finished, I got that:
"unfortunately com.android.phone has crashed"
When I checked "ok" the same message pops. Repeat. I rebooted and phone and it did re-optimization on 22 appls. But still the loop of crashes, maybe 80% are the com.android.phone, but I also get com.android.gapps and com.android.acore and other apps (youtube, etc). I tried booting into recovery mode and wiping the cache davlik cache and cache, but same problem. I was able to switch back to davlik (when you press ok after a crash, 20% of the time you get a half-second window to do something and I was eventually able to get to settings, etc). That caused the phone to crash on startup, but wiping the cache cleared that. So now I'm back where I started.
But it seems like other people having gotten ART working on the 20140714 CM11 build. Did I do something wrong when switching to ART? Anything else to try?
Thanks,
Ben
Click to expand...
Click to collapse
depends on which gapps you use. Banks mini so far works the best for art aside 1 issue. you have to use different camera app or at least i have to. experiment your self and see which gapps works best for you other then cm gapps as it fails with art.
TripFX said:
depends on which gapps you use. Banks mini so far works the best for art aside 1 issue. you have to use different camera app or at least i have to. experiment your self and see which gapps works best for you other then cm gapps as it fails with art.
Click to expand...
Click to collapse
Can I dirty flash different gapps over my working install, or I do I need to do a full wipe to remove my current (non-ART compatible) gapps first?
Thanks,
exhibit679 said:
Can I dirty flash different gapps over my working install, or I do I need to do a full wipe to remove my current (non-ART compatible) gapps first?
Thanks,
Click to expand...
Click to collapse
you can try dirty if you want but personally I would do a full wipe.
Related
I just installed CM9 via the Novacom2 method. The tablet seems to reboot itself after a few minutes of being booted up for no apparent reason. I can start up the device, and not even touch one thing, and after a bit it will self reboot.
Anyone experiencing this? Should I do a reinstall? Novacom2 method, or a complete factory reset with CWM?
CM9 runs extremely smooth otherwise, but I can't have it up for more than 5 minutes with a self reboot. It's bizarre.
Thanks in advance people...
I meant ACMEInstaller2 where I wrote Novacom2 ....
The only time I got random reboot is if I try to overclock. I went to replace CWM with TWRP today, and checked in CPUspy something quick. I had 36 hours of up time (remember this only dropped 4 days ago). Initially I tried to OC, even only going one step up I got freezes, and reboots. But leaving it at stock frequencies I have zero stability issues.
I would say to start fresh. With a fresh downloaded copy. Go into CWM and wipe data / factory reset, wipe cache, advanced > wipe dalvik, mounts > format system, data, cache, then reinstall, and install the charge fix. Then don't restore anything, and see if that fixes it.
Sent from my Galaxy S II (i777)
that may be the route I go. After about 15 reboots it is currently holding steady I have not made any interventions.
As a side issue, I get email notifications but the email app crashes upon opening. Gmail works fine though....
quarlow said:
The only time I got random reboot is if I try to overclock. I went to replace CWM with TWRP today, and checked in CPUspy something quick. I had 36 hours of up time (remember this only dropped 4 days ago). Initially I tried to OC, even only going one step up I got freezes, and reboots. But leaving it at stock frequencies I have zero stability issues.
I would say to start fresh. With a fresh downloaded copy. Go into CWM and wipe data / factory reset, wipe cache, advanced > wipe dalvik, mounts > format system, data, cache, then reinstall, and install the charge fix. Then don't restore anything, and see if that fixes it.
Sent from my Galaxy S II (i777)
Click to expand...
Click to collapse
I did a fresh start as above and the CM9 from is running problem free and 10x better than before when I had done the acmeinstaller2 method. Thanks button hit.
gizmo2431 said:
I just installed CM9 via the Novacom2 method. The tablet seems to reboot itself after a few minutes of being booted up for no apparent reason. I can start up the device, and not even touch one thing, and after a bit it will self reboot.
Anyone experiencing this? Should I do a reinstall? Novacom2 method, or a complete factory reset with CWM?
CM9 runs extremely smooth otherwise, but I can't have it up for more than 5 minutes with a self reboot. It's bizarre.
Thanks in advance people...
Click to expand...
Click to collapse
Try fixing permissions and wiping up cache from CWM, that fixes the reboots after power-on for me.
It used to do it if I left the screen to go off, but is fine now
I too am having reboot issues, but it only happens when I'm doing something. So far trying to open the Photoshop PS Touch app will cause a reboot, clicking settings in boat browser, etc. It's strange as hell.
I as well get the stock android mail client crashing when opened but its notifacations and gmail all work. I just installed maildroid and disabled stock email and seems to work OK
gizmo2431 said:
I just installed CM9 via the Novacom2 method. The tablet seems to reboot itself after a few minutes of being booted up for no apparent reason. I can start up the device, and not even touch one thing, and after a bit it will self reboot.
Anyone experiencing this? Should I do a reinstall? Novacom2 method, or a complete factory reset with CWM?
CM9 runs extremely smooth otherwise, but I can't have it up for more than 5 minutes with a self reboot. It's bizarre.
Thanks in advance people...
Click to expand...
Click to collapse
I have the same issue, but normally when the screen is on, it always reboots when I try to connect to usb storage, I have a galaxy s2 running on stable(nightly had too many bugs). anyone has the same problem?
I usually get reboots when I let the screen turn off due to inactivity. I tried installing TWRP and doing a clean install from there but it rebooted at the setup screen for CM9. I've had reboot issues since I first installed CM9, but its improved a little bit. I did try uninstalling android completely then reinstalling, but still got reboots. Does anyone have any other suggestions?
I think the best thing to do is use ACMEUninstaller to complete remove Android from your TP, then reinstall from scratch. I had reboot issues after upgrading from CM7a2 until I did a complete wipe.
[SOLVED]
Sorry I keep posting things to myself and solving it on my own after hours -__-.. I already struggled hours beforehand and was frustrated..
Anyways, I went to CMW recovery mod, deleted the back up that I backed earlier. And then format/reset to factory mod / wipe partition / cache / Dalv. Then I went to boot my device but after 10 minutes, it'd still be loading cyanogen.... so I reinstalled the CyanogenMod9. Wiped all the things I mentioned above again and when it loaded to OS, it worked..
I have no idea what was causing it.. probably the back up file interfering somehow? Because that's the only thing I got rid of and everything went back to normal.
_________________
Hey guys, I successfully installed CyanogenMod 9 on my Gingerbread 2.3.5.
Everything is great and slick. I used to use CyanogenMod 7.
Funny thing is, I enabled the lock screen (pattern) and it seems to be not working? I don't know if I'm missing something but after leaving my phone for good 20 minutes, I came back to turn on (from sleep) and it wasn't asking for lock screen pattern. I tried slide too, same.
Also, from my previous versions, whenever I was in setting or any app, if I were to press on Home Button it would bring my back to main screen. My Home button no longer does this. I have no idea what it does now, I press it and the phone vibrates (indicates that its been pressed) but no effect. I have to literately press Back like 5 times just to return to Main menu.
Is there something I'm suppose to enable or something?
Let me know, thank you
-Dan
danroh said:
[SOLVED]
Sorry I keep posting things to myself and solving it on my own after hours -__-..
Click to expand...
Click to collapse
lol, hate when that happens
Hey danroh,
I had same issue with home button and lockscreen and this steps fixed problem:
1) I accidentally downloaded Jelly Bean gapps instead of ICS version
2) Reinstalled CM9
3) Downloaded experimental build and flashed that over stable one
4) Flashed with proper ICS gapps
5) Factory reset/Data wipe, Clear Dalvik cache
6) Reboot
-----
Hit thanks if that worked for you
HElp ME
hard2play said:
Hey danroh,
I had same issue with home button and lockscreen and this steps fixed problem:
1) I accidentally downloaded Jelly Bean gapps instead of ICS version
2) Reinstalled CM9
3) Downloaded experimental build and flashed that over stable one
4) Flashed with proper ICS gapps
5) Factory reset/Data wipe, Clear Dalvik cache
6) Reboot
-----
Hit thanks if that worked for you
Click to expand...
Click to collapse
IT didnt wok, maybe because i dont have the needed gapps. Do you have a link?
danroh said:
[SOLVED]
Sorry I keep posting things to myself and solving it on my own after hours -__-.. I already struggled hours beforehand and was frustrated..
Anyways, I went to CMW recovery mod, deleted the back up that I backed earlier. And then format/reset to factory mod / wipe partition / cache / Dalv. Then I went to boot my device but after 10 minutes, it'd still be loading cyanogen.... so I reinstalled the CyanogenMod9. Wiped all the things I mentioned above again and when it loaded to OS, it worked..
I have no idea what was causing it.. probably the back up file interfering somehow? Because that's the only thing I got rid of and everything went back to normal.
Click to expand...
Click to collapse
Weirdly, my brother's Galaxy S had the same thing. Home button just would not work after installing CM9. Tried a few things, failed.
Then, I found this thread and I remembered that I'd backed up his old CM7 a while before. Deleted that backup in CWM Recovery, factory wiped/cache wipe, reinstalled CM9 and Gapps for 9 and boom, everything was fine.
EDIT:
Another thing to note is that when the home button wouldn't work, there was no Lockscreen either, just like you had. On first boot it didn't prompt me for a google account either, which it did do after I deleted the backup.
hard2play said:
Hey danroh,
I had same issue with home button and lockscreen and this steps fixed problem:
1) I accidentally downloaded Jelly Bean gapps instead of ICS version
2) Reinstalled CM9
3) Downloaded experimental build and flashed that over stable one
4) Flashed with proper ICS gapps
5) Factory reset/Data wipe, Clear Dalvik cache
6) Reboot
-----
Hit thanks if that worked for you
Click to expand...
Click to collapse
hey man!!..thnx for your guide...i w as actually in great trouble coz of this error..nd now its fixed!!...thnx a lot!!...
hello,
i had a problem with cwm builds that sometimes it woke up without pushing any buttons...i had tried resetting and re installing the rom and it didnt worked,but as it happens few times a month i just left it
but now that i flashed cwm 10 nightly,it happens more and more,it wont sleep at all:crying:
anyone had this problem?
what i can do?
i've already tested rebooting,and killing process and force closing apps...
renux said:
hello,
i had a problem with cwm builds that sometimes it woke up without pushing any buttons...i had tried resetting and re installing the rom and it didnt worked,but as it happens few times a month i just left it
but now that i flashed cwm 10 nightly,it happens more and more,it wont sleep at all:crying:
anyone had this problem?
what i can do?
i've already tested rebooting,and killing process and force closing apps...
Click to expand...
Click to collapse
Sudden wake up seems like a broken app issue. If you reflashed ROM and the issue persist, that problably means you didn't make "clean install" i.e. didn't wipe all system partition, factory reset, wipe cache/dalvik.
If you indeed made clean install but still have the problem, try fixing permissions at recovery. Also try installing app that tells you which app keeps waking device (GSam Battery Monitor or Better Battery Stats), and uninstall that app. I had similar issue, caused by CPU Control app - which crashed during one reboot. It was waking devide while trying to adjust governor/clocks.
If that don't help try to reflash ROM again (ensuring you make clean install) but don't install any apps. Try most minimalistic ROM you can find - without any stock apps.
divibyzero said:
Sudden wake up seems like a broken app issue. If you reflashed ROM and the issue persist, that problably means you didn't make "clean install" i.e. didn't wipe all system partition, factory reset, wipe cache/dalvik.
If you indeed made clean install but still have the problem, try fixing permissions at recovery. Also try installing app that tells you which app keeps waking device (GSam Battery Monitor or Better Battery Stats), and uninstall that app. I had similar issue, caused by CPU Control app - which crashed during one reboot. It was waking devide while trying to adjust governor/clocks.
If that don't help try to reflash ROM again (ensuring you make clean install) but don't install any apps. Try most minimalistic ROM you can find - without any stock apps.
Click to expand...
Click to collapse
thanks for ur reply divibyzero
actually like when i used cwm ICS builds it got disappeared by itself for unknown reasons!,and of course im glad of it
and yes,i had a clean install with every thing wiped and i have checked permissions and logcat myself,but there wasn't anything strange!
by the way those apps u suggested was really useful for me,and i've found many interesting thing inside the phone
I had CM 10.2 installed on EMMC and I updated to verygreen's CM 11 from the development forum. I performed an update vice a clean install, but I did clean davlik, but other than that I didn't reset anything.
I activated developer options the normal way with no issues once in CM 11, but when I click on developer options in settings, the settings app crashes. I performed a factory reset, cleared all cache, and it worked fine. Then I did a full restore from backup and now when I try to access developer options it crashes again.
I have since updated to the nightlies a couple of times, but there's no change after each update.
Has anyone else had this issue? I searched and couldn't find anyone else that had this issue. Any ideas?
Do a fresh install, those are still nightlys and sometimes **** like this happens.
I had a time where Trebuchet crashed everytime I opened the drawer.
Jann F said:
Do a fresh install, those are still nightlys and sometimes **** like this happens.
I had a time where Trebuchet crashed everytime I opened the drawer.
Click to expand...
Click to collapse
Yea, that's what I ended up doing. Did a fresh install after wiping everything and now it works great.
hello there,
i recently installed cyanogen mod 11 (4.4 kitkat) on my phone via CWM. i used following guide to restore my data:
http://androidforums.com/threads/guide-to-retaining-data-after-flashing-a-new-rom.682090/ (basically just restoring my data through a cwm option).
however, the system keeps optimizing 78 apps on every boot. on the first boot it were around 170 apps. i tried some of the solutions on the internet, e.g wiping my dalvik cache (which leads to oprimizing the 170 apps again) or not charging while booting, needless to say none of them worked.
one solution i havent tried yet is to reinstall the apps. i would like to know if you have suggestions which may work. also please tell me if i you need any further information.
Doflaminhgo said:
hello there,
i recently installed cyanogen mod 11 (4.4 kitkat) on my phone via CWM. i used following guide to restore my data:
http://androidforums.com/threads/guide-to-retaining-data-after-flashing-a-new-rom.682090/ (basically just restoring my data through a cwm option).
however, the system keeps optimizing 78 apps on every boot. on the first boot it were around 170 apps. i tried some of the solutions on the internet, e.g wiping my dalvik cache (which leads to oprimizing the 170 apps again) or not charging while booting, needless to say none of them worked.
one solution i havent tried yet is to reinstall the apps. i would like to know if you have suggestions which may work. also please tell me if i you need any further information.
Click to expand...
Click to collapse
Have you tried:
Boot (and update), software shutdown, reboot? (i.e. select Power Off on the screen)
Boot (and update), hardware shutdown, reboot? (i.e. hold down the power button until it dies)
Boot (and update), remove and replace battery, reboot? (i.e. don't let the operating system shutdown properly at all)
Taking a backup after it's updated, then restoring from that backup?
Wiping regular cache as well as dalvik?
That's just "this might work" things I might try.
As for actually diagnosing the issue and prescribing a targeted response - that's beyond my expertise.
assuming with "update" you mean the optimization process: yeah, tried most of them except your fourth suggestion. going to try that one soon. even if it should not work, your answer is appreciated