Database Info

ART runtime in VZW 4.4 update

Has anyone had any luck moving from Dalvik to ART with the latest VZW 4.4 update?
When I switch over to ART, the device asks to be rebooted. It will reboot, but when it comes back up, it's set back to Dalvik again.
WP=0 and rooted if that's worth anything.

digitaloutsider said:
Has anyone had any luck moving from Dalvik to ART with the latest VZW 4.4 update?
When I switch over to ART, the device asks to be rebooted. It will reboot, but when it comes back up, it's set back to Dalvik again.
WP=0 and rooted if that's worth anything.
Click to expand...
Click to collapse
This was actually the first thing I switched once I got the 4.4 update. I have rebooted since and mine is sticking to ART. I have noticed no problems or compatibility issues as of yet.
EDIT: I forgot to mention that I am not or have ever rooted my Maxx.

Mine has successfully switched to ART and have no problems. I am wp off but am not rooted.

Interesting. Wonder if it's related to root. It works fine on my Nexus but my Nexus isn't rooted either.

digitaloutsider said:
Has anyone had any luck moving from Dalvik to ART with the latest VZW 4.4 update?
When I switch over to ART, the device asks to be rebooted. It will reboot, but when it comes back up, it's set back to Dalvik again.
WP=0 and rooted if that's worth anything.
Click to expand...
Click to collapse
I am WP=0 and rooted as well and encounter the same exact problem you do. Probably an incompatibility with root.

I switched to art first thing after update and root. No problems to report and no noticeable difference either. My only issues is that a video I took was choppy. Doubt it was an art issue.
Sent from my XT1080 using Tapatalk

Just switched to test...the initial boot took FOREVER on the "Android is upgrading" screen...but it seems to be working fine...
WP off and rooted 4.4
Sent from my XT1080 using Tapatalk

In another thread a few people mentioned that if you are using Xposed that the setting won't stick. This is intentional as it could possibly brick your phone if Xposed is compiled with ART at the moment.
http://forum.xda-developers.com/showthread.php?t=2582646
If it's not Xposed, then there may be other apps out there that have similar safety mechanisms.

[Q] Hardware issue?

Does anyone have a problem with random "pauses" while using apps? It's totally not noticeable for applications that aren't continually running animations (ie: kindle, text scrolling) but becomes evident when doing thins such as:
- recording video (the "pause" will cause the recording to stop randomly for both continuous and time lapse)
- playing games (will cause the game to go to the pause screen)
- tasker programming (I think this is affected because tasker will randomly close itself without a FC dialog, profiles and tasks seem okay)
I turned on debugging to see if it was a dirty screen or anything, but the touch coordinates don't change at all when the "pause" happens. Anyone have an idea how I can fix this? It is rather crippling to the N5.
I am rooted and I have seen this problem on all roms (and I believe I noticed it on stock too...)
I use a ballistic case, if anyone else has had problems with it...
Thanks in advance!
Using N5 on Carbon + Franco kernel

I guess no one's ever had this problem before? =[

Have you tried factory reset? Fixes most problems. Could be Franco's kernel has a bug in the latest release.
Sent from The Deathstar

Have you tried going back to complete stock to see if that fixes the problem?
Sent from my Nexus 5 using XDA Premium 4 mobile app

mistahseller said:
Have you tried factory reset? Fixes most problems. Could be Franco's kernel has a bug in the latest release.
Sent from The Deathstar
Click to expand...
Click to collapse
I've tried out a few roms (factory reseting and cache clearing between each one) to see if it was any one problem, but whether AOSP or CM based, I still have the problem =/
Bruce Lee said:
Have you tried going back to complete stock to see if that fixes the problem?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Do you mean stock + unrooting? I think I remember having the problem back then, but I don't quite remember before I rooted...I'll try going back to stock w/ root first and see if it's still happening. Thanks!

Do you mean stock + unrooting? I think I remember having the problem back then, but I don't quite remember before I rooted...I'll try going back to stock w/ root first and see if it's still happening. Thanks!
Click to expand...
Click to collapse
Yes follow the link in the general to go back to complete stock and that will eliminate anything and everything that could be an issue related to software.
For what it is worth, what method did you use to root?

mistahseller said:
Yes follow the link in the general to go back to complete stock and that will eliminate anything and everything that could be an issue related to software.
For what it is worth, what method did you use to root?
Click to expand...
Click to collapse
I used the Chainfire's autoroot (http://forum.xda-developers.com/showthread.php?t=2507211) on Windows.

mistahseller said:
Have you tried factory reset? Fixes most problems. Could be Franco's kernel has a bug in the latest release.
Sent from The Deathstar
Click to expand...
Click to collapse
Bruce Lee said:
Have you tried going back to complete stock to see if that fixes the problem?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hmm, I think it worked. I haven't tested it out for lengthy periods of time but I haven't noticed any pausing anymore! =]
I followed the unroot instructions to return to stock. Although I didn't relock the bootloader.
Then I booted up stock and it seemed like it works fine.
I reinstalled CWM recovery through adb (same as I did the first time) and proceeded to reflash
It seems like the problem is gone now on custom ROM as well. Interestingly enough, if I nandroid restore my old backup, I do get the problem again.
Is there something different between reflashing stock part and wiping from factory/data reset + system partition format + wipe cache + wipe davalik?
Thanks for your help guys! I was sure before that it was hardware since I had the problem on stock w/ root, but thankfully it's not a hardware problem! =]

CyanogenMod 11

Bout damn time I made a thread
Sent from my SGH-T699 using Tapatalk

It IS about time.

ok so the cm wiki page says to use cwm. any reason i can't use twrp?

Gibson99 said:
ok so the cm wiki page says to use cwm. any reason i can't use twrp?
Click to expand...
Click to collapse
Shouldn't be any reason you couldn't use TWRP. I'm pretty sure nard himself uses it. The CWM was a CM project for a long time, and still the recovery built within it. Everyone pushes their stuff.

been running M7 for about a day now. had one fc with touchdown, my work email client, but otherwise looks good. surprised i had to manually change build.prop to set the dpi. i'm not blind, so i hate the trend towards gigantic fonts even on smallish screens like this one.
i also wasn't able to use tibu to restore securid from my old phone (vzw droid4) but i suspect that app uses some system properties like imei to create its security, so it can't be moved... not a problem. just have to do clean in stall and reimport the token.
one thing i noticed even in cm11m2 on my d4 as well as on this phone in cm11m7 is that the included sms app doesn't actually have a dark theme, and that sticks out like a sore thumb. even when you check the box for dark theme in the sms app itself, it's still white. not a huge deal obviously but doesn't match the rest of cm's normal polish.

Gibson99 said:
been running M7 for about a day now. had one fc with touchdown, my work email client, but otherwise looks good. surprised i had to manually change build.prop to set the dpi. i'm not blind, so i hate the trend towards gigantic fonts even on smallish screens like this one.
i also wasn't able to use tibu to restore securid from my old phone (vzw droid4) but i suspect that app uses some system properties like imei to create its security, so it can't be moved... not a problem. just have to do clean in stall and reimport the token.
one thing i noticed even in cm11m2 on my d4 as well as on this phone in cm11m7 is that the included sms app doesn't actually have a dark theme, and that sticks out like a sore thumb. even when you check the box for dark theme in the sms app itself, it's still white. not a huge deal obviously but doesn't match the rest of cm's normal polish.
Click to expand...
Click to collapse
The "use dark theme" option only applies to the quick reply pop up windows. The option is conveniently listed in the "quick reply" section.

orange808 said:
The "use dark theme" option only applies to the quick reply pop up windows. The option is conveniently listed in the "quick reply" section.
Click to expand...
Click to collapse
doh, you're right. my point still stands about messaging not matching the rest of cm's theming. i guess they expect people to just use chomp, go, handcent or whatever other app... i like the standard one in cm tho. except for how light it is.

What did change from the blobs for the builds after 14 /06 ?
Running 14/06 now, really good, battery charging issues are gone (i think), because a new kernel/other blobs.
Where can you find more info about blobs changes (propetary) ?

I've been having data and sms issues lately since I switched to cm11 or any of the latest 4.3.3 builds. Was there a recent radio firmware released?

Gh0sTly said:
I've been having data and sms issues lately since I switched to cm11 or any of the latest 4.3.3 builds. Was there a recent radio firmware released?
Click to expand...
Click to collapse
Which nightly?
Are you on T-Mo? Are you using a third party messenging app?
Did you wipe your data and cache before you flashed?

Gh0sTly said:
I've been having data and sms issues lately since I switched to cm11 or any of the latest 4.3.3 builds. Was there a recent radio firmware released?
Click to expand...
Click to collapse
which build are you on? i'm running cm11-20140608-Snapshot-M7 (which is 4.4.2, not 4.3.3) and have no issues to report so far. i haven't given it a full shakedown yet - still haven't tried BT or GPS but so far so good. watched netflix on the bus this morning and never had an issue. my wife and i text a lot and haven't had issues w/ that either. this evening i'm going to try out BT with my elm327 obd-ii adapter and if i have time, test audio over an avantree cara adapter. i started google maps a couple times and it found me quickly and accurately but i haven't run gps for more than a minute or so at a time so i don't know how it'll do. maybe i'll turn it on while on the bus this afternoon and see if it works well for the whole ride home.

robuser007 said:
What did change from the blobs for the builds after 14 /06 ?
Running 14/06 now, really good, battery charging issues are gone (i think), because a new kernel/other blobs.
Where can you find more info about blobs changes (propetary) ?
Click to expand...
Click to collapse
I updated ****. we're benefiting vicariously from the d2 kit-kat release
Sent from my Nexus 7 using Tapatalk

After a few minutes of playing with the CM M5 smartphone burned and became slow. Now the smartphone with the stock firmware does not burn more but it is slow. It works well this M7? You recommended me?
For a few months I used CM kitkat but I had to do a wipe. Now I do not know how to install the CM. I'm using the stock firmware.
To install:
1 rooted smartphone.
2 I copy "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip" in memory of the smartphone.
3 CWM 6.0.1.2 "install zip from sdcard -> choose zip from sdcard" I select "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip"
4 updates fail
What I'm wrong?
thanks for the help

Balthasar85 said:
After a few minutes of playing with the CM M5 smartphone burned and became slow. Now the smartphone with the stock firmware does not burn more but it is slow. It works well this M7? You recommended me?
For a few months I used CM kitkat but I had to do a wipe. Now I do not know how to install the CM. I'm using the stock firmware.
To install:
1 rooted smartphone.
2 I copy "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip" in memory of the smartphone.
3 CWM 6.0.1.2 "install zip from sdcard -> choose zip from sdcard" I select "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip"
4 updates fail
What I'm wrong?
thanks for the help
Click to expand...
Click to collapse
First, use the most up-to-date recovery; I'm pretty sure that cwm 6.0.1.2 isn't it if I see 6.0.4.7 on other devices. I like using TWRP personally, and there's a thread in this forum for that. The outdated recovery is probably the main problem right there for the failed flash.
Second, it doesn't look like you wiped anything in your steps. No factory reset, not even wiping cache and dalvik. Most people do a clean flash (that's a factory reset in recovery) when troubleshooting a failure to install a custom ROM.
Try using the latest recovery, wiping at least cache and dalvik, and see if it helps.
Good luck
Sent from my Nexus 5 using Tapatalk

reaper000 said:
First, use the most up-to-date recovery; I'm pretty sure that cwm 6.0.1.2 isn't it if I see 6.0.4.7 on other devices. I like using TWRP personally, and there's a thread in this forum for that. The outdated recovery is probably the main problem right there for the failed flash.
Second, it doesn't look like you wiped anything in your steps. No factory reset, not even wiping cache and dalvik. Most people do a clean flash (that's a factory reset in recovery) when troubleshooting a failure to install a custom ROM.
Try using the latest recovery, wiping at least cache and dalvik, and see if it helps.
Good luck
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i second this. my steps were:
1- boot to download mode, install twrp
2- boot to recovery, flash CM
3- while still in recovery, flash gapps if you want them (make sure you have the correct version of gapps from the CM site)
4- still in recovery, wipe cache and dalvik
5- still in recovery, do factory reset
6- reboot normally (it's called 'system' in twrp) and start using phone
note that there is no need to copy/flash SU at any time because CM is already rooted.

using nightly 22/06 my phone slowed down to unusable slow, flashed 24/06 yesterday.
Never had this before on cm nightly's for the relay.
And the charging (usb) problems aren't over yet (sometimes it works fine for a few hours, sometimes a few minutes).
Did a clean install a week ago (didn't solve anything).

robuser007 said:
using nightly 22/06 my phone slowed down to unusable slow, flashed 24/06 yesterday.
Never had this before on cm nightly's for the relay.
And the charging (usb) problems aren't over yet (sometimes it works fine for a few hours, sometimes a few minutes).
Did a clean install a week ago (didn't solve anything).
Click to expand...
Click to collapse
Ok. Now, find out what version of cpu you have and get some logs to help them track down your problems.
There's a search box in the corner.
I don't have any of the problems you are describing and I am betting the developers do not, either.

orange808 said:
Which nightly?
Are you on T-Mo? Are you using a third party messenging app?
Did you wipe your data and cache before you flashed?
Click to expand...
Click to collapse
I am on T-Mo, I get this via the default android messaging app as well as hangouts, but I also have times where mobile data refuses to work as well.
Right now, I'm having this issue on 11-20140608-Snapshot-M7-apexqtmo. I did wipe data and cache before I flashed. I'm not sure what is causing my issue.
I am tempted to reflash it back to factory, and take it back under my total care and get it replaced for a S5, but I really like my keyboard. :crying:

did you wipe cache and dalvik after flashing the rom? the only quirk i've noticed on m7 is that if i don't reboot every couple of days, my work email program (touchdown) likes to get slow and crashy while composing emails. going to the recent apps drawer and closing everything there usually fixes that. gps and bluetooth work fine even at the same time and battery life is great. after having tried multiple roms on my droid4 and having gps and camera issues, i am pleasently susprised how stable cm is on this relay (which i've only had a couple weeks now).

Gibson99 said:
did you wipe cache and dalvik after flashing the rom? the only quirk i've noticed on m7 is that if i don't reboot every couple of days, my work email program (touchdown) likes to get slow and crashy while composing emails. going to the recent apps drawer and closing everything there usually fixes that. gps and bluetooth work fine even at the same time and battery life is great. after having tried multiple roms on my droid4 and having gps and camera issues, i am pleasently susprised how stable cm is on this relay (which i've only had a couple weeks now).
Click to expand...
Click to collapse
I even tried that too. My phone's about a year and a half old now. I've noticed recently if the keyboard is out, or i'm holding the phone sideways, and I get a call, the phone app crashes over and over till i rotate it upward so the display is vertical, then it stops crashing(all while the phone is still ringing so I can still answer it.)

Reboots after changing wallpaper

Hi, I am running Franco kernel #53, Carbon rom 4.4.3, Xposed framework and Greenify. After I install the kernel, it immediately breaks 5 of my apps, and I have to reboot and reinstall them, but that is a tiny problem. The more annoying one is every time I change my wallpaper the device soft reboots.I have tested and found that it hasn't anything to do with the undervolting. This wasnt happening with the stock kernel.
Suggestions?

I've heard wallpapers getting changed after a reboot, but it's the first time I'm seeing a device getting rebooted after changing the wallpaper
Backup Xposed and remove it, restart your phone and then try changing the wallpaper?? May be one of the modules is conflicting with it??

vin4yak said:
I've heard wallpapers getting changed after a reboot, but it's the first time I'm seeing a device getting rebooted after changing the wallpaper
Backup Xposed and remove it, restart your phone and then try changing the wallpaper?? May be one of the modules is conflicting with it??
Click to expand...
Click to collapse
Nope, Xposed isn't the problem either. As soon as I install franco's kernel the reboots occur. Maybe the rom has changed something and became incompatible..... maybe I should just wait for the next kernel version.

Alright, did a clean install and everything is fine.
Sent from my Nexus 5 using Tapatalk

Dawnut said:
Alright, did a clean install and everything is fine.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Good to hear that!

Rom/Kernel independent Reboots

Hey guys,
ive tried different roms (stock cm11s, mahdi, droidkang) with different kernels (stock, franco, ak).
I have completely wiped my device and set up everything new.
Still im getting reboots every now and then.
Mostly it happens to me while im surfing with chrome, but it also happened in the gallery, while watching movies and so on. Never had a problem while gaming.
Last_ksmg always says "kernel panic", followed by "failed to stop secondary cpus".
Please see the linked last_ksmg files.
https://dl.dropboxusercontent.com/u/16054199/last_kmsg6
https://dl.dropboxusercontent.com/u/16054199/last_kmsg7
Any help is highly appriciated, im getting really frustrated...

Are you using any kernel apps? What other apps are you using? Are you running Xposed?

The only app worth mentioning is lightflow, and i have changed dpi to 380 with texdroider.
thanks fir your reply

soulcrash said:
The only app worth mentioning is lightflow, and i have changed dpi to 380 with texdroider.
thanks fir your reply
Click to expand...
Click to collapse
Try reflashing everything through fastboot. Each individual partition, just to make sure everything is clear and wiped.

soulcrash said:
The only app worth mentioning is lightflow, and i have changed dpi to 380 with texdroider.
thanks fir your reply
Click to expand...
Click to collapse
I was having reboot issues will using both DPI changer and textdroider from the playstore. I would suggest getting rid of textdroider DPI and instead manually change it. Go into your file manger then system/build prop and look for LCD.density. It fixed my rebooting issues running Jedi Open Source rom.
Sent from my Oneplus one using XDA Free mobile app

Hey guys,
i have fastboot flashed the stock images of 25r, 33r and 38r, and even without installing one single app or changing any system settings, i get reboots.
Any ideas left, or is my hardware defect?

soulcrash said:
Hey guys,
i have fastboot flashed the stock images of 25r, 33r and 38r, and even without installing one single app or changing any system settings, i get reboots.
Any ideas left, or is my hardware defect?
Click to expand...
Click to collapse
Reboots are usually on the software level, but 38R actually had reboot problems. Best if you installed a custom kernel and tweaked it yourself, say AK.

Well, i have tried almost every possible rom-kernel-modem combination, including stock images with fastboot. I dont know where this could be a software problem...

soulcrash said:
Well, i have tried almost every possible rom-kernel-modem combination, including stock images with fastboot. I dont know where this could be a software problem...
Click to expand...
Click to collapse
Yes, but I and a couple of friends get those reboots too. It's a common problem, not easily diagnosed. If your last_kmsg gets written to, it's saying that a configuration has crashed and the software itself is requesting a forced reboot.
If the last_kmsg has nothing inside then it's obviously a hardware issue.
Sent from my OnePlus One using Tapatalk VIP

Hmmmm...
You say i should set up the ak kernel until it works on my device ... I have no clue what all these detailed settings, apart from mhz and voltage mean - can u recommend some "safe" settings for me?

soulcrash said:
Hmmmm...
You say i should set up the ak kernel until it works on my device ... I have no clue what all these detailed settings, apart from mhz and voltage mean - can u recommend some "safe" settings for me?
Click to expand...
Click to collapse
After you install ak, install UKM (flashable zip in recovery) and then install Synapse from the Play Store. Then go into Synapse and swipe the drawers to see these options.
CPU:
Set a safe non overclocking frequency
Governor: slim
Hotplug: CPU Boost by CyanogenMod
GPU Governor: msm-adreno-tz
Memory: Drop Caches Enabled
USB Fast Charge Disabled
Log Creation disabled.

Thanks for your help man, i still get reboots, im back at my nexus5 and wait if someone from the opo support answers me ... Frustrating.

have you the problem on all ROms after updating to R38? Some ppl are reporting that after R38 Update even other ROm Versions does the Random Reboot Bug....