yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] jkc120:
Not using exposed here, though I just remembered one other non-stock thing I have setup, software nav bar.
[Verizon Samsung Galaxy S 4] MustGoFast:
Where is the new gapps I see mentioned here? The initial post link is still the same CM11 Gapps file that they started with months ago.
[Verizon Samsung Galaxy S 4] jkc120:
Are there any parts of gapps that are NOT updated by the play store?
[Verizon Samsung Galaxy S 4] macravin:
The dialer.

Sent from my Galaxy S4 Google Edition
[Verizon Samsung Galaxy S 4] jkc120:
Ok, but nothing that should cause Google search to lock up the UI I wouldn't think?
[Verizon Samsung Galaxy S 4] gonzlobo:
I had lockups on 6/5 and 6/7 running stock kernel with the cm-recommended gapps. No xposed running on this ROM. My lockups occurred while running plume and pocketcast.
[Verizon Samsung Galaxy S 4] jkc120:
Out of curiosity, is there any specific action you're doing when the lockups occur? I can open Google search without issue and even use voice search but about 1/2 or maybe 1/3 of the time if I start typing by the 3rd or 4th character *poof* lockup
[Verizon Samsung Galaxy S 4] FernBch:
The Gapps link in the op are dated 01052015, I think. Anything newer is a Gapps package put together by someone else. Regardless of the Gapps you use they are all Google applications and unless they have been themed they should be no different than any other besides which apps are in the package. That said I went to the PA Gapps

because the ones linked here FC'd for me.

The dialer is not a Google App, it is part of the ROM and changes with the version changes.

All of the Google apps are updated through Google Play, if it doesn't update there it isn't an app.

Theoretically, as long as you have the APK's for Play and Google Services you do not need to install a Gapps package. You could just go to Google Play and pick the ones you want from there. That is why in the OP the Gapps are listed as an optional item. They are not required to use CM or any other ROM.
[Verizon Samsung Galaxy S 4] gt5oh:
Noticed Snapshot M7 releases came out today for a lot of other phones, is this one in the works or a ways off?
[Verizon Samsung Galaxy S 4] FernBch:
There's no tellin as there are no ETA's on when something gets released. One wasn't put out last month because the development team thought it was too soon and it wasn't ready. The idea is to release an "M" build (Milestone not the same as Stable or RC) about once a month. A milestone can be thought of being a "snapshot" of where the build stands.
[Verizon Samsung Galaxy S 4] gt5oh:
Thanks

I was just going by this post -- http://www.androidpolice.com/2014/0...-rolling-out-for-supported-devices-right-now/
[Verizon Samsung Galaxy S 4] FernBch:
I would guess there's one comin for the VZW S4, too. If you go by the CM "game plan" were about due for one.

Edit:

Looks like M7 for jflte is up!!!!!

http://download.cyanogenmod.org/

---------- Post added at 01:30 AM ---------- Previous post was at 12:51 AM ----------

Just flashed M7.

First impression is on the initial boot after flashing it hung at optimizing app 24. Pulled the battery, booted into recovery, wiped cache and Davlik, and rebooted. I'm using ART so that may have been why it hung. Everything seems fine now. I'll work the crap out of it tomorrow and see how it is. I did notice that I went from 100% battery to 77% just flashing and getting it to boot. It does take a few minutes for the first boot after flashing so I'm not too concerned about it right now.

---------- Post added at 01:34 AM ---------- Previous post was at 01:30 AM ----------

Just noticed something else. I thought CM updated to 4.4.3 r1.1 a couple days ago but about phone says 4.4.2. Typo or M7 is still 4.4.2??
[Verizon Samsung Galaxy S 4] hlxanthus:
M7 is 4.4.2.
[Verizon Samsung Galaxy S 4] FernBch:
Thought so, guess I'll be going to a nightly real fast. 4.4.3 was doing great fr me.
[Verizon Samsung Galaxy S 4] 760hacker:
Don't see a jfltevzw M7 is it generic jflte?
[Verizon Samsung Galaxy S 4] hlxanthus:
Yes, look under jflte

Sent from my Galaxy S 4
[Verizon Samsung Galaxy S 4] Lw00d:
do you clean flash or dirty flash?? you should try clean flash. if you havent already.
[Verizon Samsung Galaxy S 4] jkc120:
Yes, I have. It made no difference.
[Verizon Samsung Galaxy S 4] DipRip:
FYI for anyone flashing today's build (snapshot), corporate email just force closes each time you open the app. I had to revert back to 6/7.
[Verizon Samsung Galaxy S 4] lolminraise:
Does m7 still have the same problem as m6, where I unplug my headphones while music is playing and the sound for ringtones and notifications will stop working? I have to reset the phone to fix this.
[Verizon Samsung Galaxy S 4] macravin:
Does anyone know what nonhlos I can use with this? I know they added support for mk2 while back, but I haven't been following since. Can I use the nc5 nonhlos?

Sent from my Galaxy S4 Google Edition
[Verizon Samsung Galaxy S 4] rajones19:
On latest (6/11) nightly. Experiencing FC in 'People' app the instant I select an individual from the list. The good news, at least for me, is it looks like the Compass may at long last be fixed. More testing required to verify that.
[Verizon Samsung Galaxy S 4] dmarden:
Confirmed.
[Verizon Samsung Galaxy S 4] Lw00d:
i flash the NC5 nonhlos awhile back, test them for about a month, i kept getting lost calls at work. so i flash back to MK2 nonhlos.
[Verizon Samsung Galaxy S 4] musicfreak190:
Hey guys is 6/11 4.4.3 yet?
[Verizon Samsung Galaxy S 4] swordmastr54:
Yes I just flashed it with 4.4.3 gapps and its fine I've had no issues at all.
[Verizon Samsung Galaxy S 4] FernBch:
I keep getting "PowerManagerService.Display" waleloks that are keeping the phone from going to sleep. Thoughts?

I'm on the 6/6 build and have a logcat.

https://www.dropbox.com/s/tl95jhkf4wwbzk5/Log_2014-06-11_11-25-14.txt
[Verizon Samsung Galaxy S 4] JaeKay:
Anyone know of a way to get the camera button to slide up from the bottom of the lockscreen like AOSP? right now, our only options are the camera widgets or the slider short cuts.
[Verizon Samsung Galaxy S 4] bsimpson1:
That logcat is pretty big so i couldnt read through it all. From what i did read through, i couldnt find anything relevant. It looks like you're using betterbatterystats, but have you ever tried wakelock detector? Maybe it will give some insight that BBS overlooks. I think the wakelock is normal as long as the screen is on. You could try checking how long the wakelock has been used and confirming that it's still increasing while the screen is on, then turning off the phone and checking to see if the time has increased while the display is off.

To manually release the wakelock regardless of the cause, you can open terminal emulator and do:

su -c "echo PowerManagerService.Display > /sys/power/wake_unlock"

The wakelock might be reacquired every time the screen turns on or off though. In that case, the above might not be very useful
[Verizon Samsung Galaxy S 4] FernBch:
After reading your reply I guess a little more detail is needed. When I made the logcat I noticed my screen was dimmed but my device never entered sleep/ deep sleep (whichever is the correct term). That particular wakelock was active for 1 hour and 29 minutes. I saw no partial wakelock or running service that would explain it. It's like it missed or never got the call to release it.
[Verizon Samsung Galaxy S 4] saul1991:
Does cm have the lock screen notifications???
[Verizon Samsung Galaxy S 4] hlxanthus:
Nope
[Verizon Samsung Galaxy S 4] Agrajag27:
I'm on the stock 4.4.2 (mistakenly flashed it from Odin 3.10) after having a bad run with another ROM.

Obviously now I've lost root.

Is there a straight-forward path for trying out CM11 on my S4 as is at this point?

Any input greatly appreciated. Thanks!
[Verizon Samsung Galaxy S 4] JaeKay:
Losing root isn't your biggest problem. Now you don't have custom recovery because you can't loki. That means you can only run tw roms using safestrap
[Verizon Samsung Galaxy S 4] Agrajag27:
Sorry but some of that is a bit Greek to me. "loki"?

I assume TW is TouchWiz and that CM isn't a TW ROM?

Right now what I'd really like is nothing more than a rooted, fairly stock ROM that's as reliable as stock. Just want to de-bloat, get my old TB data back and that's about it.
[Verizon Samsung Galaxy S 4] macravin:
This is how you root:

http://xdaforums.com/showthread.php?t=2720163

If all you really want is bebloat and stability then I wouldn't recommend even using safestrap to flash roms. Just use TB to delete stuff you don't want.

Sent from my Galaxy S4 Google Edition
[Verizon Samsung Galaxy S 4] bsimpson1:
Are those who were experiencing slow WiFi speeds on this rom still having problems? I didn't notice it before because my wifi subscription was slow. Now that I have a new, faster one, I'm noticing that my speed is usually around 400 kb/s whereas on my pc the speeds are around 3 mb/s .
[Verizon Samsung Galaxy S 4] bsimpson1:
I solved my WiFi issues by logging into my gateway and changing security from wpawpa2 psk (tkip/aes) to wpa/wpa2 psk (tkip)
[Verizon Samsung Galaxy S 4] jkc120:
No WiFi slowness here. My slowness ended up being my phone preferring to stay connected to the WAP that was further away when I was 10 feet from the one downstairs!
[Verizon Samsung Galaxy S 4] Agrajag27:
Thanks. This is the perfect answer for me. The only issue is the link given for rooting. I did that BEFORE using Odin with the stock 4.4.2 image. Just couldn't get any image to work with it and gave up. Had 4.3 working, but of course it was that broken build with no sound and such meant only as a stopgap until you load another image. If I do that, I can then load the same unrooted 4.4.2 and keep root?
[Verizon Samsung Galaxy S 4] ItsAaronR:
Seems like with the new camera wrapper I can't record in 1080, 720 seems to work fine, anyone else?

Also weird in apps like Snapchat recording using the FFC doesn't work, but in the camera app it does.
[Verizon Samsung Galaxy S 4] scarmon25:
Yeah 1080 recording seems borked
[Verizon Samsung Galaxy S 4] drmark50:
I have not seen any reports of proximity sensor malfunction with calling.

When I put phone up to my face screen shuts off but won't come back on when I remove. I can hold down the home button and the app manager opens up. I can then select the call and hangup. Is this a setting issue?
[Verizon Samsung Galaxy S 4] swordmastr54:
It lasts for 10 seconds then phone reboots.
[Verizon Samsung Galaxy S 4] scarmon25:
Yup. Same exact thing. I'm sure its a known issue. If not then it is now LOL
[Verizon Samsung Galaxy S 4] drmark50:
I am running the 12/12 nightly and pa gapps. I have also noticed that the clock FC. I was running Gummy ROM 4.4 prior. This one is more stable and the battery life is much better. Nice work!
[Verizon Samsung Galaxy S 4] SonicJoe:
It should be noted that this issue only affects the AOSP camera. Focal takes 1080p videos just fine.
[Verizon Samsung Galaxy S 4] reinaldistic:
My Bluetooth audio is unusable since 12/13, anyone else experiencing this?
[Verizon Samsung Galaxy S 4] drmark50:
update on my clock FC. I dirty flashed to 12/14. no change. I then factory wiped, cleared cache, flashed 12/14 rom and installed CM gapps (non ART). And now clock works.

I still have persistent problem with proximity sensor (screen staying off) during phone calls. I also have Ti backup getting stuck during restore. I had that before with gummy rom, but didn't have it when I switched to CM 12/12 nightly.
[Verizon Samsung Galaxy S 4] Chris123NT:
I'm actually looking into it now, I'm seeing the same thing, seems to be due to some CAF merges into the bluetooth stack that happened on the 13th.

And it only seems to be crapping out on head units that display track info, can you confirm?
[Verizon Samsung Galaxy S 4] Dusty Rhodes:
My Ford Sync Touchscreen in my 2012 GT won't BT audio stream but will operate fine during phone calls. BT streaming disconnects and reconnects over and over.
[Verizon Samsung Galaxy S 4] brizey:
If I get a chance today I will try to stream BT in my car.
[Verizon Samsung Galaxy S 4] Chris123NT:
Yeah bluetooth audio is totally screwed, steve merged a bunch of ****, and 12 hours ago merged something new that makes it not even connect. Running a test build now with all of this **** reverted to see if that brings it back.
[Verizon Samsung Galaxy S 4] ITGuy11:
Bluetooth goes into a connect/disconnect loop for me as well on 12/14 build. 2010 Fusion Ford Sync, no track info is displayed on my head unit.
[Verizon Samsung Galaxy S 4] cybereclipse:
Does Caller ID by Google work on any CM 4.4 based roms for anyone.

EDIT: nvm...finally read that CM uses the AOSP dialer and not the google dialer.
[Verizon Samsung Galaxy S 4] daventodd123:
I'm on the MDK radios on this ROM. Can I flash just the MK2 modem zip or do I need to wait for the NON-HLOS version?
[Verizon Samsung Galaxy S 4] TMYINC:
Just flash the modem zip.
[Verizon Samsung Galaxy S 4] reinaldistic:
Exact same thing is my problem
[Verizon Samsung Galaxy S 4] FernBch:
Ok, I've been running the 12/12 nightly and have an issue/question. Any app that uses text to speech or a Google sound service has issues. I am getting "unfortunately Google text-to-speech" or "Google sound search" has stopped on a regular basis, even when I'm not using an app requesting the services. Is this a Google issue, a CM issue, or both? Of all the issues I have run into using CM nightlies I must say that this one could make me go back to 10.2.0 until things become more stable. I haven't seen a workaround or fix for this.
[Verizon Samsung Galaxy S 4] Chris123NT:
BT issues should be fixed in the next build.
[Verizon Samsung Galaxy S 4] bsimpson1:
Sorry for the successive complaints, but does anyone else have problems with the mic being too quiet (besides when you're talking directly into it) in audio recording apps?
[Verizon Samsung Galaxy S 4] JaeKay:
Yup, but idk if it's hardware or software related. Anyone test it on a tw ROM?
[Verizon Samsung Galaxy S 4] saul1991:
nobody else having the proximity sensor issue??? is there an app i can at least use to keep the phone wake during calls?? i have already cleaned the sensors and im still having this issue...
[Verizon Samsung Galaxy S 4] JaeKay:
You have to take apart the phone and use compressed air. Only way it'll work I found.
[Verizon Samsung Galaxy S 4] bsimpson1:
Well it definitely seems to be possible to use the mics to create a decent recording. Running this script in android terminal emulator will begin recording and output a wav on /sdcard called testfile.wav, and as you will see (or hear) it's very audible when played back:

#!/system/bin/sh

#Enable DSP AFE for Audio Recording over Slimbus TX
amix 'MultiMedia1 Mixer SLIM_0_TX' 1
# Set the Slimbus TX Channels
amix 'SLIM_0_TX Channels' One
# Enable Codec TX Path
amix 'SLIM TX7 MUX' 'DEC4'
amix 'DEC4 MUX' 'ADC3'
amix 'DEC4 Volume' 100%

arec -D hw:0,0 -C 1 -R 48000 /sdcard/testfile.wav

I got the above from this page after hours of searching for a solution.

My best guess is that the low volume is due to noise reduction filters. There's a build.prop entry that can be used to disable noise correction and use the mic as analog I believe.
[Verizon Samsung Galaxy S 4] albert001:
11-20140611-Nightly-jflte has a weird visual bug. All other versions had other critical issues like during calls I couldnt hang up or dial a number because the sensor wasnt working that detects when the phone is to your ear. This version runs everything well but I the screen flickers a lot on the homescreen. Not on any of apps but only on the homescreen when using widgets or adding icons or widgets the screen flickers as your touching the screen. FYI.

It seems to be the Trebuchet launcher is the cause of the problem. Using Nova Launcher or any other fixes the issue.
[Verizon Samsung Galaxy S 4] bsimpson1:
Can anyone check to see if they're able to play youtube videos in the browser (the browser that comes preinstalled with the rom)? I know it used to work, but i cant get mine to play anymore.
[Verizon Samsung Galaxy S 4] indolent:
I was able to fix mine following this post:

http://xdaforums.com/showpost.php?p=48365578&postcount=33
[Verizon Samsung Galaxy S 4] hlxanthus:
method 1 did nothing for me but method 2 completely fixed it for me.

Sent from my Galaxy S 4
[Verizon Samsung Galaxy S 4] jaybird779:
I feel really lame, I cannot find those radios. Can someone point me to them? Many thanks!
[Verizon Samsung Galaxy S 4] djdmbrwsk:
http://xdaforums.com/showthread.php?t=2487298
[Verizon Samsung Galaxy S 4] jaybird779:
Thank you for that!! I found that page, but didn't think that was it for some reason.
[Verizon Samsung Galaxy S 4] gonzlobo:
Well this is odd, wifi didn't work on 620. Flashed back to 618 and it's good.
[Verizon Samsung Galaxy S 4] vwpiper:
Not being argumentative. Just informing.

I've been on 6-20 for over 3 hours. So far everything that I have tested has been working (including WiFi). In fact I have one more bar than I usually do. Don't know if it's just a bar or if I'm getting better reception.
[Verizon Samsung Galaxy S 4] jackburnt:
I had the same issue. Installed (clean), connected to Wifi fine. Installed apps via TiBu, rebooted, wouldn't work. I then "forgot" the network and reconnected. Working fine now.

I would say try that. Forget it and connect again.

Looking forward to using this build as I was still on a build from April. Heading to Seattle for a conference next week and I definitely want a working compass.

Update: Blah, compass is still off.
[Verizon Samsung Galaxy S 4] jkc120:
Are you saying 6/20 is supposed to fix the compass?
[Verizon Samsung Galaxy S 4] Crossoverdoc:
Is there another way to fix the 'can only send one text message' issue other than flashing a GPE ROM first? If that's still the only way could someone link me to specific instructions on this?
[Verizon Samsung Galaxy S 4] isaacfinnegan:
Anyone having issues with IR on the latest nightlies? I'm on 6/17 and the IR appears to have stopped working. Wanted to ask around before I embark on the wipe/restore/debug process
[Verizon Samsung Galaxy S 4] rajones19:
Compass definitely not fixed for me.
[Verizon Samsung Galaxy S 4] darklavalizard:
There is absolutely no way to get this installed on a phone that has a stock 4.4.2 ROM correct? I know the bootloader is locked down on it and you can't install a custom recovery. Just bought the phone from a friend discounted because of what stock ROM it has on it. Don't know why he installed the stock 4.4.2 but he did....
[Verizon Samsung Galaxy S 4] crossen0:
Correct. Sorry mate.
[Verizon Samsung Galaxy S 4] heath2805:
Are you sure it's official stock? Check your settings, about phone to see what kernel and baseband its on.
[Verizon Samsung Galaxy S 4] darklavalizard:
Baseband: I545VRUFNC5

Kernel: 3.4.0

dpi@SWDD5015 #1

Fr Mar 28 13:38:41 KST 2014

Any hope?
[Verizon Samsung Galaxy S 4] heath2805:
Yep that's pure stock. I figured I'd ask in case a rooted 4.4.2 stock build was installed.
[Verizon Samsung Galaxy S 4] jackburnt:
I thought there were changes, but nope. I just assumed (my own fault) that after 2 months, the compass would be fixed.
[Verizon Samsung Galaxy S 4] gonzlobo:
Unfortunately, I can't even get wifi to turn on. When I move the slider to ON, it remains there dimmed out and wifi refuses to turn on. That said, I can't even make the phone forget the network it's used to connecting to. Tried 6/20 again & still didn't work.
[Verizon Samsung Galaxy S 4] heath2805:
No problems with WiFi on 6-15 or 6-18. I don't use compass or IR so no issues for me lol
[Verizon Samsung Galaxy S 4] radpp16:
Any RC yet?
[Verizon Samsung Galaxy S 4] crookedview:
Compass has been working for me for a long time. Both in Maps and GPS Status.
[Verizon Samsung Galaxy S 4] jkc120:
I *thought* it was working for me, until I did walking nav in a city and it screwed me hahaha
[Verizon Samsung Galaxy S 4] Lw00d:
i use google maps all the time, i never had a issue with compass. unless compass only works when one is walking. i really doubt that.
[Verizon Samsung Galaxy S 4] jackburnt:
Yea, I had that happen to me too. My cat got loose so I tracked it into the woods. Used my phone's torch and compass to get around and got loss FURTHER into the woods. Oh well. Navigation works so it's not too bad.

No other issues so far *knocks on wood*
[Verizon Samsung Galaxy S 4] bsimpson1:
Actually that's exactly how it works. It samples your position at a regular interval and based on the changes it decides which direction you're moving relative to the map. BUT, it normally wouldnt work that way if we had a working compass; It only uses that method as a fallback. The problem with the compass is because the proper firmware for our magnetometer isnt available i believe.

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

I noticed a speedup since i decided not to flash the cm11 version of the qualcomm-optimized dalvik on the latest nightly.
[Verizon Samsung Galaxy S 4] Lw00d:
i see.
[Verizon Samsung Galaxy S 4] FernBch:
That is correct. It's not a fault of CM, Sammy has to release drivers or something for the firmware. Then the compass will work properly.
[Verizon Samsung Galaxy S 4] jfu:
IR still broken on the latest nightly!
[Verizon Samsung Galaxy S 4] gonzlobo:
Ok, 622 fixed my wifi. Heh, I'll shut up now (yes, I know it's my phone only).
[Verizon Samsung Galaxy S 4] stvn2569:
I was wondering if I've got safestrap, supersu 2.0 from the market and I'm on a Verizon gs4 NC5 can I flash the newest CM rom (I belive it's CM 11) correct me if I'm wrong. If I can would I flash it on the stock part of the original Verizon OS?

SiVisPacemParaBellum

OderintDumMetuant
[Verizon Samsung Galaxy S 4] saul1991:
you can't sorry, you have to be on the mdk version
[Verizon Samsung Galaxy S 4] stvn2569:
Ok thanks, that sucks.

SiVisPacemParaBellum

OderintDumMetuant
[Verizon Samsung Galaxy S 4] indolent:
There used to be a setting in maps to tell it to orient you based on the direction you're traveling. That seems to have disappeared. Mine definitely does not currently work that way. Whether I'm moving or standing still, my compass is way off.

I don't know if it's just a firmware thing with CM. My compass never worked with stock touchwiz either.
[Verizon Samsung Galaxy S 4] musicfreak190:
6/23 running real nice. Android 4.4.4.
[Verizon Samsung Galaxy S 4] jkc120:
Only issue I have in 6/23 is that the button backlight setting doesn't stick. I set it to off (unchecked) and after a reboot it goes back to enabled. Though it has been like this since the 6/14 nightly.
[Verizon Samsung Galaxy S 4] JaeKay:
Can confirm. Ever since the option for on screen nav bar was enabled
[Verizon Samsung Galaxy S 4] 0reo:
Does the IR blaster work? For some reason that's my only hang-up with this ROM.
[Verizon Samsung Galaxy S 4] FernBch:
The 6/22 build is not reporting signal strength correcfly, either.
[Verizon Samsung Galaxy S 4] jkc120:
Working ok on 6/23 for me.
[Verizon Samsung Galaxy S 4] stvn2569:
I'm appoligized if what I'm about to ask has already been answered but I was just wondering if Cyanogen will ever be available for Verizon's gs4 on the nc5 OS?
[Verizon Samsung Galaxy S 4] Slim1023:
Not unless you can unlock the bootloader. And after a year of trying, there hasn't been a method of doing so.
[Verizon Samsung Galaxy S 4] carlbettag:
dirty flashing M7

Anyone have a problem dirty flashing M7 over M6? I did this & got stuck in a CM endless boot...

Haven't yet starting debug yet, just curious if this is a shared problem or not.
[Verizon Samsung Galaxy S 4] IMMORTALKING69:
As much as I love this ROM, I am currently running GPE BC the camera ( HDR ) and BT work flawlessly. There are several things I miss about cm but can't go back until these are fixed. To me, a ROM builder should be required to first get the main functions down right? Not required but just want to! Please CM get this working for me what is the hold up????
[Verizon Samsung Galaxy S 4] DreamFX:
Everything works in this rom. What are you talking about?
[Verizon Samsung Galaxy S 4] thestinkinggenius:
Totally agree - I keep checking back every week or two to check on the status and it doesn't seem to be getting much better.