yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] Chris123NT:
It's probably ART doing it. Don't report issues with ART, switch back to dalvik and see if the issue persists, if it does then post some more details.
[Verizon Samsung Galaxy S 4] scarmon25:
FWIW I've been using ART for a few builds now and I'm having no wake lock issues. It may be an issue with an app not liking ART.
[Verizon Samsung Galaxy S 4] Chris123NT:
Yeah that's fine, the point I'm trying to make is that ART is not officially supported since it's an experimental feature.
[Verizon Samsung Galaxy S 4] scarmon25:
Oh yeah I get ya. That was more for the other guy to try and help him narrow it down. I spend enough time in the IRC to know that its a headache right now lol
[Verizon Samsung Galaxy S 4] HowardZ:
I am using VPlayer.

It is free and seems to work well.

MX Player will probably just need a one line code change in its manifest.xml file.

MX Player should probably get updated within a week.

---------- Post added at 02:52 PM ---------- Previous post was at 02:48 PM ----------

I build it unofficially - usually every night.

I also add the Intellidemand governor, and build TWRP instead of CWM recovery.

I use Kernel Tuner - but an older version from April which works better.

https://drive.google.com/folderview?id=0B88bR12MKYUKc0FOZ1M0bFd0c00&usp=sharing#list
[Verizon Samsung Galaxy S 4] RavenII:
Is anyone else having issues hanging/ending calls? I hit end and that's it...nothing happens until the other end hangs up. I'm using a T-Mobile sim in the phone. Not the VZW sim...
[Verizon Samsung Galaxy S 4] Slim1023:
How is Google Wallet? I've read in a few places that it won't work with rooted devices. Was wondering if that's just rooted stock ROMs or custom ROMs as well. Also, are any tricks needed for Google Wallet, or just download the app?
[Verizon Samsung Galaxy S 4] rajones19:
I think it just doesn't have the heart to tell you that it's almost April, but the weather still SUCKS! :laugh: Frustrating on every level.
[Verizon Samsung Galaxy S 4] radpp16:
Where is M4? or M5?
[Verizon Samsung Galaxy S 4] Erievon:
I've been on 3/25 for a couple days now, and everything seems to be running perfect. I've yet to run into any issues. I play ingress and GPS has been flawless and quick. No SMS issues either (knock on wood) though I am using Hangouts and I'm in the Cleveland, OH area.
[Verizon Samsung Galaxy S 4] FernBch:
It will be released when the dev's feel it's time and not a moment sooner. There are no ETAs or schedules to when a M build is released.
[Verizon Samsung Galaxy S 4] samoid:
Anyone know where to get the GPE rom?
[Verizon Samsung Galaxy S 4] FernBch:
Here:

http://xdaforums.com/showthread.php?t=2643031
[Verizon Samsung Galaxy S 4] jkc120:
Still having the UI lock up when using Google Now :/

Well, the 3/28 nightly is still having a UI lock up occasionally when using Google Search (Google Now is disabled).

I was able to hold the power button to get the power menu and rebooting works, so at least I don't have to battery pull.

But next time it does it, I'll have to connect and get a logcat because something is screwed up.
[Verizon Samsung Galaxy S 4] jorceshaman:
Anyone know of a way to get MHL/HDMI working on this ROM? Or is that only for TW?
[Verizon Samsung Galaxy S 4] crookedview:
I just used an MHL/HDMI adapter this weekend and it worked. This is the adapter I used : http://www.amazon.com/gp/product/B0...=B00ESM3Q7K&linkCode=as2&tag=httpwwwdrisco-20

Didn't do anything special, just plug and play.
[Verizon Samsung Galaxy S 4] jorceshaman:
I can't seem to get the one I got to work. I tried plugging it into the TV and my phone then the wall, TV, and phone. No dice.

VicTsing 2m MHL Micro USB to HDMI HDTV Adapter Cable For Samsung Galaxy S4 SIV i9500 by VicTsing http://www.amazon.com/dp/B00CO21HWW/ref=cm_sw_r_udp_awd_5yTntb0H35TYQ

Edit: I just tried again today and now it's working. Odd.
[Verizon Samsung Galaxy S 4] rpitera:
Finally took the plunge back in from 3/4 and flashed the latest nightly and while it's running ok, I'm back to not being able to switch off of dalvik and back to art. I'm really starting to wonder if it might be time to move on. It seemed like everything was great until they moved to the unified builds, but since then it's been nothing but problems.
[Verizon Samsung Galaxy S 4] onemandeep:
well it was fun playing with CM, but I miss TW. I have a backup of Hyperdrive 13 (4.3/mk2 based), how do i go back? do i need to simply factory reset and restore or do I format system etc? If someone could give me a detailed repsonse thatd be great ( someone stole my backup phone so if i brick i wont have a phone or Internet!)
[Verizon Samsung Galaxy S 4] hlxanthus:
Simply restoring your nandroid backup should be enough but you can't go wrong with a factory reset either. That is all that is needed.

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] lx1907:
Just moved from the latest snapshot to 3/25 build. Everything looks good so far.
[Verizon Samsung Galaxy S 4] bajasur:
How on earth does this OP only have 29 thanks?

:confused:
[Verizon Samsung Galaxy S 4] jorceshaman:
3+27=30 but regardless, it should have like 10 times that. After seeing your post I had to check whether I did or not (I did). Lol
[Verizon Samsung Galaxy S 4] rpitera:
I checked too. (I also did) :)
[Verizon Samsung Galaxy S 4] papstar:
When did a working LTE toggle get merged?
[Verizon Samsung Galaxy S 4] vwpiper:
"NO new update" today. What Will I Do?! ?
[Verizon Samsung Galaxy S 4] vanberge:
Better check again...
[Verizon Samsung Galaxy S 4] vanberge:
Lol. Anyone try the April 1 build yet?

Check out your ringtones if you went with it.
[Verizon Samsung Galaxy S 4] Ban-Hammer:
Ladies and gentlemen, Ban-Hammer has returned from the dead with an update regarding Bluetooth MAP, SMS and other garbage in relation the the Ford Sync and MyFordTouch systems.

I currently run the 3/29 Euroskank nightly, and after unpairing and repairing my phone to Sync, I received a text message notification! There's much more work to be done, as I had 3 new text messages on my drive, but only 1 notification. However, this is a much welcomed return of features.

Also, when using Sync to send a message, Sync states the message fails, but Hangouts shows the message as being successful, and the recipient did in fact receive the message.

Outside of that and the occasional A2DP audio disconnect, BT is pretty much flawless for me.

I've linked some stupid pictures for your viewing pleasure. Deal with it.

Imgur album here.
[Verizon Samsung Galaxy S 4] cawpin:
camera doesn't work in 3/31 build

I updated from the last snapshot to 3/31 yesterday and just noticed that the camera app won't launch. I just get a standard crash error. I've tried clearing cache and data but still get the same error.

I'm getting ready to update to 4/1.
[Verizon Samsung Galaxy S 4] FernBch:
If you're coming from the last snapshot you should seriously consider a clean flash. There are just so many changes from the M release to the unified builds.
[Verizon Samsung Galaxy S 4] cawpin:
Flagged 4/1 with a cache/Dalvik wipe and the camera still crashed. Cleared the app cache and data again and it works.
[Verizon Samsung Galaxy S 4] swordmastr54:
I'm still on a clean flash from mid last month is there anything worth updating?I've been stalking the changes but haven't seen much.
[Verizon Samsung Galaxy S 4] scarmon25:
Retracted
[Verizon Samsung Galaxy S 4] drt054:
Just Flashed CM11 4/2 nightly from SlimKat, very happy with this as is.. Everything seems to be working now.. Yay!!
[Verizon Samsung Galaxy S 4] BaronLager:
As of a couple days ago (still running 3/26), the voicemail dial pad is frozen again. This time it is COMPLETELY frozen.

A dirty flash of 4/3 didn't help the situation.

A clean flash of 4/3 didn't help the situation.

---------- Post added at 10:24 AM ---------- Previous post was at 09:48 AM ----------

For what it's worth, this doesn't seem to be ROM related, even though this problem seemed to go away when I did a clean install of 3/26... I took the phone apart and cleaned the proximity sensor (again), and this problem went away.

In the past, the proximity dirty sensor kept the screen off when I'd pull it away from my face. That's why I didn't think this could have anything to do with this issue. Screen is on, keypad should work. I guess the proximity sensor also protects from accidentally pressing keys with your cheek, so even though the screen was on, the keypad was disabled by this proximity sensor.

Clean sensor = keypad works.
[Verizon Samsung Galaxy S 4] igorneumann:
Im using CM10.2 to receive calls.

Could you use it on CM11?

What ATT build do you flashed?
[Verizon Samsung Galaxy S 4] jkc120:
4/3 FC hell

I'm using ART and the 3/28 build. I tried flashing 4/3 over top of it and I'm in FC hell. Literally, everything is FC'ing.

I tried wiping system then flashing, still no go. I am not ready to try a clean flash, but wondering if anyone else is using ART on 4/3 without issue?

*edit* Did a clean flash, no issue. Changed from Dalvik to ART and rebooted and *boom* FC hell.

So 4/3 definitely seems broken with ART.
[Verizon Samsung Galaxy S 4] jkc120:
No one else is using ART on their phone? Or am I the only one getting FC's out the arse when enabling ART? I don't see any relevant commits in 4/4 or for 4/5 that would fix ART, at least none that mention it.

I know cm11 doesn't officially support ART, hell neither does Google. But I figured enough would be using it that it would cause some buzz if it is completely fubar.
[Verizon Samsung Galaxy S 4] jorceshaman:
Not really since there's no point bug reporting something unsupported.
[Verizon Samsung Galaxy S 4] jkc120:
Last I checked this wasn't jira. ;)

And by that rationale, NO ONE should be reporting ANYTHING wrong in here unless they are on an M release, eh?
[Verizon Samsung Galaxy S 4] jorceshaman:
Not exactly, it's something they're not even actively working on at the moment whereas the other nightly features are supported and being worked on. You had reported your issue then quoted it and questioned why no one else was reporting the same issue. It's because they're not worried about fixing ART right now.
[Verizon Samsung Galaxy S 4] jkc120:
No, they're not supported. Nightlies aren't supported, period. So your argument is invalid.

Anyway, there were people on here reporting issues with ART a while back so I figured at least one other person was using it. All I wanted to know is if it were happening to others. Feel free not to reply if you're not using it.
[Verizon Samsung Galaxy S 4] jorceshaman:
10-4
[Verizon Samsung Galaxy S 4] swordmastr54:
I clean flashed this mid last month the 19th I think and got it all set up and I've been on art the entire time the only issues I've had are random ui freezes and one of my games doesn't seem to like it I have seen no reason as of yet to even update to the latest build I've not seen anything interesting if I'm wrong somebody please tell me so I can update.
[Verizon Samsung Galaxy S 4] jkc120:
Nothing wrong with trying :) I HIGHLY recommend you create a nandroid first though if you're not going to switch back to dalvik before flashing.
[Verizon Samsung Galaxy S 4] FernBch:
Tried flashing the 4/5 build today. Everything was fine until ART was enabled, then everything just FC's.
[Verizon Samsung Galaxy S 4] FernBch:
Same results with the 4/3 build.
[Verizon Samsung Galaxy S 4] ahoslc:
You guys should try the latest Vanir build ;)
[Verizon Samsung Galaxy S 4] shoutcast:
I have the same issue.. I did research on this and found out this seems to be a issue accross different roms. It doesn't happen to everybody but was found that it is a issue with people that are on mdk. apparently there are isssues with compatibility of mdk and the newer roms of 4.3 and up. Anyway this is what i read and seems to be a common issue for mdk people.. Some poeple get lock ups and some people get reboots.. So far from what i read there are no fixes but people like sbreen are looking into it.
[Verizon Samsung Galaxy S 4] FernBch:
Those of you who are successfully using ART, did you do anything special to get it to work? If so, what did you do or are you using an earlier build?

I really like CM on ART. It is more responsive and the battery life seems better than when using Davlik.
[Verizon Samsung Galaxy S 4] jamesd1085:
M5 is releasing...wonder if we will get it this time
[Verizon Samsung Galaxy S 4] scarmon25:
No. 4/5 is essentially our M5. The consensus was that CDMA isn't to the point of "stable" at this point. The 4/5 build had all the new CDMA patches and everything but since the M5 code had been frozen for a week those patches wouldn't have made it into the M5 build.
[Verizon Samsung Galaxy S 4] FernBch:
Also, the CM team feels that because there are still some issues that are affecting some individuals on various carriers they could not release a M build that wasn't working correctly for 100% of the users.

---------- Post added at 05:03 PM ---------- Previous post was at 04:18 PM ----------

Flashed 4/6 today and have two things.

First, I have noticed the "UI Freeze". It may not be the UI that is freezing. It seems like the display froze for a couple moments. The task that was active did not freeze only the display did. After a short wait I would see the display update and the task complete.

Second, ART is still a no go for me. When active the boot process does not complete as there are several FC's going on. Can't even list them cause they just pile up so fast.

Haven't noticed anything else so far.
[Verizon Samsung Galaxy S 4] jamesd1085:
Hmmm...it was pretty stable before all this unified build bs...just sayin
[Verizon Samsung Galaxy S 4] FernBch:
It's getting better again. I see the logic behind the unified builds. I have the feeling that some of the issues the devs may have expected and some they didn't.
[Verizon Samsung Galaxy S 4] swordmastr54:
I also agree that it seems to be getting better its easier on them to a degree I hope and maybe that means they can work better on bug fixes and improvements to the system overall( better optimization and make the is smaller while still being stable and feature packed)
[Verizon Samsung Galaxy S 4] jorceshaman:
Scratch that, Ktoonsez Kernel was the issue, not CM11.
[Verizon Samsung Galaxy S 4] cixelsyddyslexic:
Moved from 03/13/14 build to 04/05/14 build, and I am getting Calendar Sync stop messages. I've tried clearing Calendar and Calendar sync data and caches, and can stop the messages by disabling Calendar syncing (Exchange AND Google), but enabling sync calendar items on either account causes the messages to start popping up again. It looks like there were some changes made to Calendar made 04/02 build, but typically I haven't seen issues when only "Translation" changes are made.

Anyone have ideas?
[Verizon Samsung Galaxy S 4] kyuubi08:
Have you tried a clean flash
[Verizon Samsung Galaxy S 4] cixelsyddyslexic:
Clean flash would be my absolute last resort, so no. I'm looking for something more specifically tailored to my issue than just "blow it all away and start fresh", lol.
[Verizon Samsung Galaxy S 4] shoutcast:
NO DATA

After I left my house and left my wifi i noticed i had no data.. I can make calls just fine but no data.. no lte or 3g.. nothing.. I tried disableing and enabling the data i tried changing to different networks.. I tried clearing devaik and cache.. nothing.. I can't get data back.. Please someone Help. i am new to CM11.. So i don't know if I am missing a setting somewhere. I did a search on no data in this form and came up with nothing.. PLEASE HELP!
[Verizon Samsung Galaxy S 4] twiz0r:
There's 3 weeks of updates you flashed over....Who knows.

How long does it take to flash and re-setup? Cmon man!
[Verizon Samsung Galaxy S 4] cixelsyddyslexic:
Takes me quite a while... plus I'm not certain of a safe way to backup and restore Google Authenticator...Aside from that, though, I'd like to figure out the cause of the issue rather than just treat it like the Geek Squad (error message? Format and reinstall! Crash? Format and reinstall!) :)

E/AndroidRuntime(15845): java.lang.RuntimeException: Unable to get provider com.android.providers.calendar.CalendarProvider2: java.lang.ClassNotFoundException:Didn't find class "com.android.providers.calendar.CalendarProvider2" on path: DexPathList[[zip file "/system/framework/android.test.runner.jar", zip file "/system/priv-app/CalendarProvider.apk"],nativeLibraryDirectories=[/vendor/lib, /system/lib]]

Is the relevant error message from logcat.
[Verizon Samsung Galaxy S 4] jkc120:
Looks like you perhaps have a dup apk causing an issue. Instead of a full wipe, try just wiping system manually before flashing. You'll have to reflash gapps though.
[Verizon Samsung Galaxy S 4] mcconvict:
I've flashed tons of unified builds with no issues...
[Verizon Samsung Galaxy S 4] FernBch:
Lucky You.

I have clean flashed the last three builds and have issues with no mobile data on each one. 4/7 is completely hosed. In settings it says my network type is LTE but mobile data state says disconnected. I have also had issues with no data on WIFI. I went back to 10.2.1 for a few weeks hoping that things would get better, so I come back a couple days ago only to find that CM11 is not good enough for a daily driver yet. Back to 10.2.1 I go again. :banghead:
[Verizon Samsung Galaxy S 4] SinfulRoad:
Man, am I the only person who doesn't have problems? I've been using CM11 since December and the only problem was the GPS which I fixed by flashing stock.

Sent from my Cyanogenified S4.
[Verizon Samsung Galaxy S 4] jorceshaman:
Everything was running smoothly for me until the 2nd but even then it was a problem with Ktoonsez kernel and not CM11 (even though I mistook it for being CM). And he fixed it with his 4/7 release.
[Verizon Samsung Galaxy S 4] MustGoFast:
No, I think the majority of people aren't having major problems, but there's not much point in posting that as I feel guilty taunting those who are. You can also look at the post rate as versions have gone up and see less ad less which suggests that either there are less issues or people have given up, but I would guess the first.
[Verizon Samsung Galaxy S 4] swordmastr54:
I have had no issues but I'm on the build from mid last month.
[Verizon Samsung Galaxy S 4] lordgodgeneral:
I've had absolutely 0 problems restoring Google Authenticator using TB across different ROMs. After flashing first thing I do is install a backup apk of TB that I keep on my SD card, then restore App/Data for Authenticator. Then I can add my google account.

Another option is to create a one time use burn code for the two way authenticaiton, and use that to sign into your google account when setting up after a new flash.
[Verizon Samsung Galaxy S 4] cixelsyddyslexic:
This fixed my issue. While I was testing this out, I found that I was also still using a 2013 build of KitKat gapps, so I updated that as well, which may have been the ACTUAL fix.
[Verizon Samsung Galaxy S 4] swordmastr54:
I check for latest gapps every time I flash anything and glad your issue is fixed.
[Verizon Samsung Galaxy S 4] drt054:
No problems here.. Flashed CM11 from SlimKat at end of March and all running/working well through today's (4/9) build.
[Verizon Samsung Galaxy S 4] jkc120:
Is ART still broken? I can't report it since it's not supported nor can you file bugs on nightlies. So I guess those of us who want to use ART are SOL until M6 and the hope that someone will fix a non-supported feature?
[Verizon Samsung Galaxy S 4] drt054:
Has the CMwallpapers.apk issue been reported? (the reason why wallpaper is off centered and reason why the transparent status bar is black when using a CMwallpaper with Nova?)

I have been using an apk from a pre-unified build for CMwallpapers but have to copy it over every time I want to change wallpapers if I want to keep the transparency. Otherwise it sticks through flashing nightlies as long as I don't change wallpapers.
[Verizon Samsung Galaxy S 4] Logano520:
Is anybody else's CMUpdater doing this? Started happening to me since yesterday's build.
[Verizon Samsung Galaxy S 4] NickSaul:
Yup. I noticed that this morning. I had to go download the nightly the old-fashioned way.
[Verizon Samsung Galaxy S 4] vwpiper:
[quote name="Logano520" post=51798222]Is anybody else's CMUpdater doing this? Started happening to me since yesterday's build.[/QUOTE]<br />

<br />

Yup. I noticed that this morning. I had to go download the nightly the old-fashioned way.<br/>

Me too. Like I wasn't going to flash something before breakfast.
[Verizon Samsung Galaxy S 4] swordmastr54:
Tried the latest nightly it just keeps force closing so just restored keep up the good work I'll update someday.
[Verizon Samsung Galaxy S 4] jkc120:
I guess ART has gone from unsupported to "don't ever use it" status :) Guess I'm staying on 3/28 for the foreseeable future. No major issues for me and no new features I have to have.
[Verizon Samsung Galaxy S 4] vanberge:
I'm on 4/10 and it's running fine. Stock kernel, Dalvik, semi recent clean flash.

I have not had any problems on any unified build really with this setup.
[Verizon Samsung Galaxy S 4] dasx86:
I was getting constant FCs when I flashed 4/9, got to recovery and cleared cache, fixed it up. On 4/10 now.

I also haven't really had any issues since unification (aside from the MMS issues in early March that were cleared up weeks ago.) I don't run ART...
[Verizon Samsung Galaxy S 4] FernBch:
I've been watching the posts the last couple weeks. Tie that to my recent experiences with CM11 and, IMHO, CM11 has taken a couple steps backwards recently. ART is borked, data issues, and FC's galore is reason enough for me to "try" it briefly every few days. Once I see something that works as well as it did a few weeks back then maybe it can be a DD again. For now I'll stick with 10.2.1, it works.
[Verizon Samsung Galaxy S 4] swordmastr54:
So when 4.4.3 is open to public will this be updated to that or start a new thread how does that work with CyanogenMod?
[Verizon Samsung Galaxy S 4] FernBch:
Because it is said to be a KitKat bug fix update I would imagine that it will just be an update. That said it should still be here as CM11.
[Verizon Samsung Galaxy S 4] cawpin:
I know it's been a long time, but was this ever sorted out? I'm running the 4/7 nightly and the compass still doesn't work correctly. Even calibrating with GPS Status only works for a few minutes. Is there some special calibration I need to do to fix this?
[Verizon Samsung Galaxy S 4] swordmastr54:
I odined back yo stock just to get a mdk backup because I didn't have one and now it works fine I used it yesterday but I'm on a build from last month FYI.
[Verizon Samsung Galaxy S 4] jamesd1085:
Anyone no what kind of changes come with this theme chooser update?
[Verizon Samsung Galaxy S 4] js2shanks:
Has anyone had a problem with the front facing video camera not working? It does not work on snapchat but works in the camera app. Any help?
[Verizon Samsung Galaxy S 4] Lw00d:
i smell the next monthly coming up. :o
[Verizon Samsung Galaxy S 4] .Ejekt:
Anyone else having trouble with xposed after the latest nightly delta?
[Verizon Samsung Galaxy S 4] jkc120:
Well, since it seems ART isn't getting fixed anytime soon, I flashed 4/12 and I'm using dalvik. I had to wipe system because I was getting acore FC's though. I can definitely tell the difference in ui responsiveness on ART vs Dalvik. That, or the newest nightly has some UI lag when typing on the stock keyboard.

*edit* Well, for ****s and giggles I swapped to ART and it works! So if you're on an older build with ART enabled and want to keep using it try this:

1. change back to dalvik and reboot

2. flash new build, reboot

3. enable ART
[Verizon Samsung Galaxy S 4] jamesd1085:
Have you tried Qualcomm optimized dalvik...I used this since art was broken...may actually be smoother...since its still dalvik I get no issues with fc...there is a specific version for the cm11 branch
[Verizon Samsung Galaxy S 4] jamesd1085:
http://xdaforums.com/nexus-4/general/4-4-4-4-x-qualcomm-optimized-dalvik-t2546120

Cm11 one works with anything aosp using cm11 as a base...anything that doesn't boot try the regular one...bionic files only help on ROMs that aren't already bionic optimized...won't help on cm11