I'm running CM11 4.4.4 and light gapps which are compatible with ART, but I can't enable Art as my runtime. I select Art as my runtime, it reboots but nothing happens, it goes back to dalvik once again. Have you ever faced this issue? What should I do? Thanks in advance.
Related
Hi everyone,
My touchpad(16GB) reboot almost evertytime when I play a video or song and pluging earpod.
The situation is: when I play the video first, and then plug the earpod, my touchpad would stop, and then reboot.
If I plug in earpod first, then play video, it would not reboot.
Some times even when I run a app, it would just stop to response, and then reboot.
I am using cm9 the 20121217 nightly version. But the touchpad also would reboot when I was using previous nightly.
I do try wipe cache, wipe dalvik cache, fix permissions. But it would just reboot.
I installl the cm 9 using ACME installer 3. And I do try wipe data, cache and dalvik everytime I installed new cm9 nightly. But the reboot issue just happen to my touchpad all the time.
Webos runs ok and never have any issue.
If you have experience dealing with this issue, could you show me your method or any clue about what should I do?
Thank you.
Merry Christmas~~~~
The audio driver isn't the most stable. My device was constantly rebooting when going into sleep unless I left the audio unmuted and played the lock/unlock sound. But I've never had an issue with heaphones. You may just want to backup anything important and do a clean android flash (factory reset, wipe data, system, etc)
laofan said:
Hi everyone,
My touchpad(16GB) reboot almost evertytime when I play a video or song and pluging earpod.
The situation is: when I play the video first, and then plug the earpod, my touchpad would stop, and then reboot.
If I plug in earpod first, then play video, it would not reboot.
Some times even when I run a app, it would just stop to response, and then reboot.
I am using cm9 the 20121217 nightly version. But the touchpad also would reboot when I was using previous nightly.
I do try wipe cache, wipe dalvik cache, fix permissions. But it would just reboot.
I installl the cm 9 using ACME installer 3. And I do try wipe data, cache and dalvik everytime I installed new cm9 nightly. But the reboot issue just happen to my touchpad all the time.
Webos runs ok and never have any issue.
If you have experience dealing with this issue, could you show me your method or any clue about what should I do?
Thank you.
Merry Christmas~~~~
Click to expand...
Click to collapse
The only thing I can think to do is to run acmeuninstaller, then install android again, using ACMEInstaller3.
Good luck.
Merry Christmas to you!
I run webos doctor and reinstall cm again. As long as I don't use any Chinese music player, my touchpad Is ok.
Thank you.
Sent from my cm_tenderloin using xda app-developers app
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.
hi, im having a problem, is it normal for a custom rom to heat up my phone after about 5 minutes of using it? i mean while texting?
when it's in sleepmode evything coolsdown, but then after waking it up for about 5-10minutes it heats up, im using the governor
abbysplug and i/o sio. im not connected to the wifi or mobile data(never used data though). i turn off sync for all my accounts and
location is turned off, im currently using Carbon 4.4.2(06022014). and my battery drain is like 3-5minutes for every 1% of its juice. is it
normal? because when im in stock rom my battery last a lot longer. im using set-cpu and greenify as for my battery saving. oh and here's one
more problem, everytime a set a setting for example changing dalvik to ART, after i set it, and rebooted, i check in the setting it's back to dalvik.
also the read-ahead option for extsd everytime i set it up for 4000KB and thick the start on boot, after reboot it goes back to the default, same for my prefered network 2g/3g i always use 2g only but then after several minutes back to 3g again. please if someone can help me.
i did a fullwipe (System, Data, Cache, Dalvik Cache)
im using Aroma GAPPS
and Recovery is TWRP by Android-Andi
and the Rom is by New-Maclaw
For the heating up & battery consumption : It's 1GHz bug. Hung the WiFi and reboot. :good:
For changing from dalvik to ART : update your recovery with NovaFusion's last update and try again. Btw ART is working. :good:
As for the other problems are bugs of the rom : Update the rom and wait for repairs.
jstath1972 said:
For the heating up & battery consumption : It's 1GHz bug. Hung the WiFi and reboot. :good:
For changing from dalvik to ART : update your recovery with NovaFusion's last update and try again. Btw ART is working. :good:
As for the other problems are bugs of the rom : Update the rom and wait for repairs.
Click to expand...
Click to collapse
thanks for the response sir, i don't have a 1ghz bug, mine is playing around 200-1000, just updated my TWRP to 2.7.1 will try again to change the runtime.
Samsung Galaxy S III Mini battery drain problem
This has only happened twice. It could be my phone overheating and that causes my phone to reboot and go from around 60%-70% to exactly 4%.
But maybe its something else, i'm not sure. My phone isnt rooted or anything. But i will root it once i get this fixed.
I have the SIII Mini, Model Number- GT-i8190, android version- 4.1.2. PLEASE HELP
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.
Hey guys,
So I've tried using xposed framework on a variety or ROMs for my XT1033 Moto G
All of them install fine, but give me random bootloops when I reboot/power off my phone
I can fix it by wiping cache and dalvik cache, but it's ridiculously annoying to do so every time
Does any one else seem to have this problem?