yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] saul1991:
Dude I can't find it lol but yeah I doubt the sensor since the home button doesn't wake the phone
[Verizon Samsung Galaxy S 4] FernBch:
Who's CM11 are you running. Is the Cyanogenmod or one of the others?
[Verizon Samsung Galaxy S 4] saul1991:
Cm from this post that links to their new website
[Verizon Samsung Galaxy S 4] FernBch:
Sorry, had to ask. Go here:

System Settings>Performance>Processor>CPU Governor

There you will find choices for the governor type. A different choice may help. Early on (In CM10) I had issues with screen delay in general, changing my Governor setting helped a lot. So, when I went to CM11 I automatically set it to Ondemand as well.
[Verizon Samsung Galaxy S 4] saul1991:
OK I think I found it. This it??
[Verizon Samsung Galaxy S 4] FernBch:
Nope, that's About Phone. When you go into System Settings, Performance is the second listing from the bottom (right above About Phone).
[Verizon Samsung Galaxy S 4] saul1991:
Its not there. Thanks though I'll keep looking :(
[Verizon Samsung Galaxy S 4] FernBch:
Ok, I see the issue.

Go into about phone and go to the bottom. Second from the bottom Says "Build Number". Tap on that until you unlock Developer Options, it's something Like 6 or so taps. Once the message says they are enabled go up one menu level and you will see something like this:

Go into Performance>Processor>CPU Governor and try OnDemand and see if it helps.
[Verizon Samsung Galaxy S 4] saul1991:
Thanks man i got the CPU settings but I still have the issue with the Ondemand option. I'll keep trying the other ones.
[Verizon Samsung Galaxy S 4] FernBch:
Glad you got it. It may not help, but it's worth a shot. Make sure you reboot after each settings change.

---------- Post added at 11:10 PM ---------- Previous post was at 11:06 PM ----------

Oh, one other question. When you came to CM11 did you clean flash the first time or dirty flash? If you clean flashed did you just wipe system, data, and cache or did you also do a factory reset? I have found in the past when changing ROMs, even from CM10 to CM11 including a factory reset worked better for me. That way there were no traces of a previous ROM leftover.
[Verizon Samsung Galaxy S 4] saul1991:
I did a full wipe data, cache and dalvik cache. But I found a way to hang up with out waking the phone up in accessibility there's am option to hang up with the wake button button. Ill use that in the mean time.
[Verizon Samsung Galaxy S 4] FernBch:
At least you found a workaround. Wish the governor settings would have helped.

As for other's that were experiencing that, I honestly don't know if they found a fix or if it fixed itself.
[Verizon Samsung Galaxy S 4] invisiblek:
Its in review. I fixed it up for us last night: http://review.cyanogenmod.org/#/c/58164/

EDIT: err...two nights ago... xD

Its in review. I finished it up a couple hours ago: http://review.cyanogenmod.org/#/c/59936/

Did this just start happening today or recently? I had an issue with this on my HTC earlier today so I doubt its device-specific. Probably something got derped in framework, I haven't looked into it.
[Verizon Samsung Galaxy S 4] FernBch:
Invisiblek to the rescue!

You da man!!

:thumbup:
[Verizon Samsung Galaxy S 4] saul1991:
Its always happen when ever I use cm. that's why I stay away but after running it for a day, its the only issue I have.
[Verizon Samsung Galaxy S 4] jorceshaman:
Awesome! I'll keep an eye out for it to be merged and then back to nightly flashing! You're awesome, thank you!
[Verizon Samsung Galaxy S 4] jkc120:
I'm still on the 02/13 nightly. I haven't had any issues so I've been hesitant to update. :)
[Verizon Samsung Galaxy S 4] ahpatel:
Tried a dirty flash of the 2/20 build and still couldn't get a GPS lock. Will try a full wipe this weekend.
[Verizon Samsung Galaxy S 4] onemandeep:
Precautions

I have been in the dark for a while in terms of the S4 updates (mdk, mj7, etc). If i were to flash this rom could i simply restore my nandroid of Hyperdrive 13 (a 4.3 tw based rom).
[Verizon Samsung Galaxy S 4] macravin:
Yes, you would have no problem doing this.
[Verizon Samsung Galaxy S 4] Cilraaz:
Are TxdoHawk and I the only two seeing this problem? I initially had the issue while using Euroskank's CM11. I had been using their 1/24 build until the problem happened on 2/19. I updated to their 2/19 build at that point. Flashing back to stock eliminated the problem. Today, I tried the official 2/21 nightly and had the same problem. I don't understand why it happened, considering that nothing on my phone changed prior to the issue occurring.
[Verizon Samsung Galaxy S 4] papstar:
What theme are you running?:eek:
[Verizon Samsung Galaxy S 4] saul1991:
http://xdaforums.com/showthread.php?t=2631573 here's a link to it
[Verizon Samsung Galaxy S 4] Kidd_Funkadelic:
Just tried my first upgrade to the latest unified nightly. I reflashed the PA Art-friendly KK gapps that I had kicking around for awhile on top of it and got stuck at the CM logo. The MD5 was correct, so the file was good. Ideas? Dirty migration to unified has been done before. I'm running ART. Wonder if I should try reverting to dalvik first or skipping the gapps flash. Restoring nandroid now.
[Verizon Samsung Galaxy S 4] FernBch:
I just dirty flash each nightly. Nothing else.
[Verizon Samsung Galaxy S 4] justda:
Are you using a GSM sim from a GSM provider? I use my I545 with T-mobile and had this issue. There is a flashable fix.

http://xdaforums.com/showthread.php?t=2635758
[Verizon Samsung Galaxy S 4] djdmbrwsk:
I am having the exact same issue as described in the other post...

...I literally woke up this morning with the issue. I've been runnin the 2/12 nightly with no issues at all and then suddenly this happened! I do remember seeing that Twitter and Chrome Beta updated overnight, but I doubt they're the issue. If I flash back to TW I experience no problems. Different modems and a clean flash of M3 didn't seem to help either. What the heck?!
[Verizon Samsung Galaxy S 4] invisiblek:
This won't work anymore because all variant-specific stuff is set based on the bootloader on your device (something you can't change). You *may* be able to kang0r props from here: https://github.com/CyanogenMod/android_device_samsung_jflte/blob/cm-11.0/init/init_jflte.c from the att section and/or use the gsm blobs (more likely fix) in /system/blobs/gsm/ inside the jflte rom zip.
[Verizon Samsung Galaxy S 4] saul1991:
I have the same issue with gummy. Ahhhhhhhhh no one else have this bug???
[Verizon Samsung Galaxy S 4] djdmbrwsk:
Update on the text/sms issue...

I just clean flashed the 10.2 stable and this issue still exists for me. I'm thinking it has to be a modem/radio thing. Have you other two guys with the problem flashed new modems? ...or new kernels for that matter?

Specifically I was on CM11 2/12 nightly with the ktoonsez kernel and the mk2 modem/radio. I hadn't just installed any of the things above either...texting just randomly broke this morning. Man this sucks...
[Verizon Samsung Galaxy S 4] bsimpson1:
Have you tried disabling/uninstalling voice plus? It's been known to cause issues with texting.
[Verizon Samsung Galaxy S 4] djdmbrwsk:
Yep...no luck. And the issue is there right after a flash even before restoring old apps/settings.
[Verizon Samsung Galaxy S 4] dwitmer1989:
You can add me to the weird SMS issue ranks. Tried the voice+ thing tried different modem/radio tried different kernel. I'm seeing it pop up on all kinds of ROM threads. Really weird
[Verizon Samsung Galaxy S 4] sherdog16:
Hey guys I'm noticing with videos I'm only recording at 16 fps. There a setting somewhere to give me 30?
[Verizon Samsung Galaxy S 4] Kidd_Funkadelic:
Looks like it was due to this. See the link to the other fix indicating it will be resolved in an upcoming nightly.

http://review.cyanogenmod.org/#/c/59953/
[Verizon Samsung Galaxy S 4] FernBch:
So I guess the only way to get LTE working again is to flash stock then come back to CM? Can anyone confirm or know of another way to fix? LTE quit 2 builds ago as best as I can tell.
[Verizon Samsung Galaxy S 4] djdmbrwsk:
I just changed my network to "CDMA only" instead of "LTE/CDMA/EvDo" and after a restart my texts send reliably. Not sure what's going on with LTE but this seems to work for now...
[Verizon Samsung Galaxy S 4] tjk639:
Are you using stock CM kernel or another? One of KTs builds caused me not to have LTE. updating it fixed it.
[Verizon Samsung Galaxy S 4] phonedawg:
GSM SIM in Verizon GS4 running CM 11 unified build

Is anyone using a GSM SIM now able to receive incoming calls? I am hoping that the unified build should fix the issue.
[Verizon Samsung Galaxy S 4] FernBch:
Stock CM kernel.
[Verizon Samsung Galaxy S 4] thcaddict:
Sorry to clog this thread if this has been discussed before, but there is just sooo much to look through it makes it quirte difficult.

I am running my stock rooted S4 on MJ7, with SafeStrap 3.71, and I am looking to flash CM11. Everytime I try to flash CM, and then I flash the corresponding modules that go with MJ7, upon reboot all I can get is a black screen. Has anyone else had this problem, and know how to fix it? If I am not able to run CM11 on MJ7, are there any other AOSP based ROMs that will work with my phone running MJ7? I really need to get away from this TouchWiz interface, I really prefer AOSP. Much thanks to anyone that is willing to chime in and help out.
[Verizon Samsung Galaxy S 4] jkc120:
With SafeStrap you are limited to TW ROMs, sorry :(
[Verizon Samsung Galaxy S 4] FernBch:
Had to revert to a previous build today. I started having problems with phone calls. The main issue was when I dialed I could not hear anything in the earpiece. First call I would make after a reboot or sending a message was fine. Second call was not until reboot. Also began having an issue with the screen staying off when I pulled the phone away from my ear. My nandroid was for the 2/14 build, so that's where I am for the moment. Here's a logcat for anyone who would like to dissect it:

https://drive.google.com/file/d/0BzP9_0-z4Cyhdi1DakR2SXB2X3M/edit?usp=sharing

---------- Post added at 10:54 PM ---------- Previous post was at 10:50 PM ----------

Edit:

That was the 2/21 build that gave me trouble.
[Verizon Samsung Galaxy S 4] scarmon25:
Latest build only had one commit different than the previous build. It was for copyright stuff for the calendar. Nothing system or kernel wise I could see.
[Verizon Samsung Galaxy S 4] scarmon25:
Looks like there isn't any changes in tonight's build either. Unless something changes within the next hour there won't really be any reason to flash tonight's build unless your new to CM and flashing for the first time.
[Verizon Samsung Galaxy S 4] FernBch:
I have noticed something that may be a little peculiar. It may be more a CWM issue than a CM issue. Yesterday I restored a nandroid of the 2/14 build. I went through my device and noticed that things are not in exactly the state they were when I created the backup. Most were minor things, android debugging was off, and a few other minor settings. One thing was my runtime setting. I have used ART since day one, but after restoring I was set to Davlik.

Maybe I have misunderstood CWM and nandroids all this time, but I thought a nandroid backup was supposed to be a "snapshot"" of your current system that when restored from would return your device and settings to a previous state exactly as it was when the backup was created.

This is the second time I have seen this and I have never experienced it on any ROM other than CM.
[Verizon Samsung Galaxy S 4] rpitera:
I don't think it was your restore, I just checked and I'm on Dalvik now too and I know I've been on art since I started. I don't know when this happened since this is the first time I bothered to check, but I am currently on the 2-22 nightly.

Switching brought up a disclaimer that art is not supported under cm, which I don't remember seeing before. The phone just reboots, but doesn't change over. It just stays on dalvik.
[Verizon Samsung Galaxy S 4] FernBch:
Ya know, that makes me think. There have also been a couple times after flashing a nightly that settings have changed (I've always dirty flashed to preserve settings and such). There has been a few instances of Ymail settings being different after a dirty flash, too. But I never thought much about it until today.

How's the 2/22 nightly? I just finished downloading it but haven't flashed yet.
[Verizon Samsung Galaxy S 4] rpitera:
It seems ok, besides refusing to switch to art. But I haven't really made any calls yet. I activated my buddy's phone last night and called and texted him, but since he was sitting right there I never put the phone up to my ear so I can't confirm or refute your issue right now.

---------- Post added at 11:30 AM ---------- Previous post was at 11:26 AM ----------

Weird behavior now. After the second attempt to switch to art, the home screen (using GEL) keeps refreshing itself. I think I'm going to try falling back to 2-21
[Verizon Samsung Galaxy S 4] FernBch:
Hmmm. I really like using ART, my S4 seems to be more responsive and has better battery life than when on Davlik. If it will not switch I may stay put for a while (flashed the 2/17 build today).

My troubles were on the 2/20 build. I'm Leary right now of going back to the unified builds. I know 2/17 was issue free for me.

---------- Post added at 12:44 PM ---------- Previous post was at 12:35 PM ----------

Being how the USC and VZW GS4's are so close, I wonder if we can get any benefit from this:

http://www.androidpolice.com/2014/0...-updates-for-the-galaxy-s4-and-galaxy-note-3/
[Verizon Samsung Galaxy S 4] rpitera:
Well, I went back to the 2-20 build and still cannot switch to art. As far as nandroid backing up the state, I can confirm this because when I went back to 2-20 I was at work and not only did it restore with my old email password (I had changed it on the network while I was backing up), but it even was in vibrate mode when it came back up, which is how I had it at work.

I'm suspicious of the unified builds too now, but my only option would be a clean install of the 2-17....assuming it's still available somewhere. Did they remove it when they moved to the unified build branch?
[Verizon Samsung Galaxy S 4] brandonair95:
Try here: http://download.cyanogenmod.org/?device=jfltevzw&type=nightly
[Verizon Samsung Galaxy S 4] rpitera:
Thanks, I was just about to edit my post as I found out but ya beat me to it. Looks like the last available vzw specific build its 2-16.

I'm wondering if I should try dirty flashing it....any opinions?
[Verizon Samsung Galaxy S 4] FernBch:
I can upload 2/17 to G-Drive and link it. Give me a few.
[Verizon Samsung Galaxy S 4] rpitera:
Do you ever get tired of coming to my rescue? Lol. Thanks much.
[Verizon Samsung Galaxy S 4] FernBch:
No. We're supposed to bail each other out in a jam. Lol

You're Welcome
[Verizon Samsung Galaxy S 4] rpitera:
Just a quick update before I hit the shower, I made and received calls with no issues, and no problem with texts.
[Verizon Samsung Galaxy S 4] brandonair95:
Is there no nightly for today?
[Verizon Samsung Galaxy S 4] FernBch:
Here it is, jfltevzw-2/17-nightly

https://drive.google.com/file/d/0BzP9_0-z4CyhY0V3UGJic05BWlE/edit?usp=sharing

MD5 should be

935eb2c3a536d282a77a29d91a56a30d

---------- Post added at 02:02 PM ---------- Previous post was at 01:59 PM ----------

Doesn't look like it, checking it looks like 90% of the builds failed today.
[Verizon Samsung Galaxy S 4] scarmon25:
This may have already been mentioned but I found a weird little bug on my device. If I open the downloads app and then hit the back button nothing happen. The back button works fine in every other app. Just not the downloads app. Anyone else have this.
[Verizon Samsung Galaxy S 4] FernBch:
I only have seen it the first time after a reboot when opening it. Every other time it works properly.
[Verizon Samsung Galaxy S 4] scarmon25:
A reboot fixed it
[Verizon Samsung Galaxy S 4] FernBch:
Looks like there about 10 commits that are being reverted in the next build. I think the team is onto something.
[Verizon Samsung Galaxy S 4] rpitera:
Thanks very much. Phone has been otherwise behaving under the 2-20 build but I'd rather have this.
[Verizon Samsung Galaxy S 4] scarmon25:
2/24 build I noticed something. When I first flashed it the WiFi toggle wouldn't work. Rebooted and it worked fine. Not sure if it was just me or will be the same for everyone.
[Verizon Samsung Galaxy S 4] igacek:
Sorry if this is too late of a reply, but I found that the camera force closes if you have Developer Options enabled. Try turning it off.
[Verizon Samsung Galaxy S 4] LilRico:
I think it was the 22 nightly, but after I updated it, it stopped force closing and started working again! :)

Thanks for trying to help me out! :good:
[Verizon Samsung Galaxy S 4] FernBch:
So, does anyone know of a different fix to get LTE working again other than going back to stock and re-flashing CM. 4G quit working for me sometime over the last week or so.

I'm currently on the 2/17 build and running the stock kernel.
[Verizon Samsung Galaxy S 4] scarmon25:
FWIW I'm on the 2/24 and LTE is working. Now I am running a jflteusc so that may have something to do with it.

---------- Post added at 09:37 PM ---------- Previous post was at 09:27 PM ----------

I do notice even though I get LTE it always says roaming indicator off.
[Verizon Samsung Galaxy S 4] jorceshaman:
http://review.cyanogenmod.org/#/c/59936/
[Verizon Samsung Galaxy S 4] scarmon25:
Yeah. I'm in USC. I hit up invisblek and let him know hopefully it follows over for us too. ')
[Verizon Samsung Galaxy S 4] papstar:
Tried flashing 2/24 nightly. Bootloops after recreating the dalvik cache. Anyone else?
[Verizon Samsung Galaxy S 4] radpp16:
Will there be a M4 or next is RC1?
[Verizon Samsung Galaxy S 4] FernBch:
My guess would be M4. Only my humble opinion, but there are a few minor issues and they just went to "unified" builds, so I would not expect a release candidate yet.
[Verizon Samsung Galaxy S 4] FernBch:
Well, guess I gotta do something I haven't had to do in a long time. Downloaded 2/24 and dirty flashed like I always do, and, behold!! I'm stuck in a bootloop. Checked the md5 and it's good, so when I get home later, I'll make a fresh TiBu, wipe, wipe, wipe, factory reset, and flash and see what happens.
[Verizon Samsung Galaxy S 4] RedBullet:
was just about to move to the unified build (since the OTA is no longer telling me about updates!)

Can I do a dirty flash?
[Verizon Samsung Galaxy S 4] FernBch:
Should be able to. Make a nandroid first just in case.
[Verizon Samsung Galaxy S 4] FernBch:
Same here (running ART). (See 3 posts up)
[Verizon Samsung Galaxy S 4] Kidd_Funkadelic:
Look back a few pages. I posted about the same thing. ART is currently broken in the unified builds. From what I found it will be fixed in tomorrow's nightly.
[Verizon Samsung Galaxy S 4] FernBch:
Aahhh, 'splains everything! Guess I'll wait a day.

---------- Post added at 11:11 PM ---------- Previous post was at 11:06 PM ----------

Anyone have any news on getting LTE working again without having to go back to stock first?
[Verizon Samsung Galaxy S 4] shawner47:
Not sure if anyone else is noticing this and not sure if this matters... I was looking at my network settings today and APN is grayed out for me so I can't change or even verify that it is right. Could this be the problem? If so, does anyone know how to get into the APN settings other than in Mobile Networks? I tried a trick that someone had used for the Note 3 but it wouldn't work on the S4, at least not on mine. I really don't want to go back to TW...

Also I am on the 2/04 nightly with stock kernel.
[Verizon Samsung Galaxy S 4] FernBch:
CM hasn't implemented VZW APN's into the build, yet. If you know the APN's you can open "voice dialer" and say "open APN's" and see if you can manually create them. For now the info is in the buildprop, IIRC.
[Verizon Samsung Galaxy S 4] shawner47:
Ah, that makes sense. Like I said, wasn't sure if it made a difference with what we were seeing. Guess that puts us no further in our hunt for the cause/fix. Thanks for that info though! The search continues...
[Verizon Samsung Galaxy S 4] kjettern:
Battery :(

Anyone have a solution for my huge battery drain? I've tried switching to efficient kernel but still my phone drains 40% in 2 hours! I'm not using it either.. My battery stats suggests it's my screen that drains 50% but it hasn't been much on.. I did not have this problem with an early buggy omega rom..

Thanx!
[Verizon Samsung Galaxy S 4] BaronLager:
Big Oopsie

I read this article this morning, it may shed some light on some issues users have experienced in the past few days:

http://www.cyanogenmod.org/blog/cm-installer-ota-issue-identified-with-d2-and-jf
[Verizon Samsung Galaxy S 4] FernBch:
They do not mention jfltevzw, does that mean our devices issue has been fixed?
[Verizon Samsung Galaxy S 4] Kidd_Funkadelic:
I can confirm like I suspected that the 2/25 build now works with ART. I just moved up to the unified builds finally. As I mentioned yesterday the issue was referenced in my earlier post a few pages back:

http://xdaforums.com/showpost.php?p=50540964&postcount=1925

There was a fix that went in that broke ART that I linked to, and a comment in there pointed to a follow up fix that would resolve it and was present in the 2/25 build. So flash away ART lovers.
[Verizon Samsung Galaxy S 4] BaronLager:
It included the d2 and jf device trees. I'd assume that included jfltevzw.
[Verizon Samsung Galaxy S 4] FernBch:
I thought so, just wanted to be sure. Haven't had much luck with the last 3 or 4 bills.

Now I just have to figure out how to get LTE working again.

---------- Post added at 10:14 AM ---------- Previous post was at 09:45 AM ----------

Success! Now on the 2/25 build, although it didn't go off without a hitch. When I chose update from the menu in the CM updater it rebooted but hung loading CWM. This may not be a CM issue, though. Yesterday I got a notice for a update to CWM (I use RomManager). My current version was 6.0.4.4 and the new was 6.0.4.7. After updating it still shows the version as being 6.0.4.4. After a battery pull it loaded CWM and applied the 2/25 nightly.
[Verizon Samsung Galaxy S 4] swordmastr54:
Running 25 build on KT kernel its smooth and very good art is running fine and now it shows Verizon instead of empty and had no issues flashing or anything just make a backup as normal. Good luk everybody.