yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] jkc120:
Yeah, it's a bummer to lose the screen real estate, but back on the right for me (since I hold my phone in my left hand) is no good and I'm too OCD to change the button mapping to swap menu and back haha :)

---------- Post added at 10:05 AM ---------- Previous post was at 09:43 AM ----------

Some additional info:

- same issue occurs on m7 (HTC One)

- does NOT occur on Manta (Nexus 10)

It seems to be an issue where if the PREVIOUS tap was NOT on the sw nav, the next sw nav tap often misses. If I tap home repeatedly, I don't see any misses.

So somehow there's a period of time after touching the normal screen that the software nav button taps won't register. If I wait a full second or so, it works fine.
[Verizon Samsung Galaxy S 4] jkc120:
I cleared my logcat buffers then was able to catch this during a logcat by tapping an empty spot on my launcher home screen then the software nav home button:
[Verizon Samsung Galaxy S 4] linuxthinker:
Nope, incoming calls aren't ringing through, either :( It seems like GSM was better-supported on stock :(

Any plans to fix GSM support or is this pretty much a CDMA-only phone under CM?
[Verizon Samsung Galaxy S 4] 32BitWhore:
Running like a dream for me on 12/9 and Ktoonsez 12/4 kernel. So happy to have CyanDelta functionality again! No issues yet to speak of.

Sent from my CM11/KT Powered Galaxy S4
[Verizon Samsung Galaxy S 4] scarmon25:
Its googles new runtime environment. It is supposed to be faster than the dalvik runtime environment they've used since android fame to fruition on mobile devices.

---------- Post added at 07:17 PM ---------- Previous post was at 07:15 PM ----------

Something I've noticed. If you turn location off then back on it goes back to high accuracy. Doesn't matter what you had it on prior it always goes back to high accuracy. Need to have something they makes the setting stick through off and on toggle.
[Verizon Samsung Galaxy S 4] NickSaul:
Looks like the action overflow buttons will always be enabled in Kitkat. I hope CM makes a way to remove them for us, since we already have a hardware menu button.

Here's the story on Android Police.
[Verizon Samsung Galaxy S 4] scarmon25:
I've notice it in some apps. Hitting g the hard menu key triggers a drop down from that button. To me it doesn't seem like a huge deal. But that's just me.
[Verizon Samsung Galaxy S 4] Lw00d:
is ART enable automatically or do i have enable it? if so where is it?
[Verizon Samsung Galaxy S 4] scarmon25:
You have to enable it. Its in developer options. Little advice. When it reboots it coverts all the odex files within apps and such to oat files. This takes a minute and can cause some excessive heat. You may wanna throw the phone in a freezer or kick on the AC and hope it in front of a vent. Freezer works much better. Once that first boot is done you won't have to worry about that anymore.
[Verizon Samsung Galaxy S 4] Zmnypit:
Looks like 12/9 had a camera update. Anyone flash it yet?
[Verizon Samsung Galaxy S 4] scarmon25:
Yeah I'm on it now. Nothing major. No visual or up front changes. Those changes to the HAL which is back end.
[Verizon Samsung Galaxy S 4] Lw00d:
danm!!! i will wait until i get home from work then, throw that bad boy in the freezer.
[Verizon Samsung Galaxy S 4] crossen0:
I just installed the optimized dalvik stuff on top of euroskanks cm build. Going to test it against ART. ART worked well enough when I enabled it. But I know its not ready from prime time, yet.
[Verizon Samsung Galaxy S 4] scarmon25:
So are the touch sounds supposed to be quieter that the lock and unlock sounds.
[Verizon Samsung Galaxy S 4] gunnermike:
Actually it is ready. It infact is a dramatic improvment. The issues come from apps that depend on Dalvik run time to work properly. Those are few and far between and I havent run into one myself. Just make sure you enable ART as soon after the first boot as possible, this way all the apps you download from the market install under ART.
[Verizon Samsung Galaxy S 4] scarmon25:
I can say that so far using ART has shown some real improvements in certain apps. They open quicker and seem too respond better. So because of that I will continue to use it.
[Verizon Samsung Galaxy S 4] rexdog1888:
Just step outside or something(assuming it's cold).

Mine did get extremely hot but not to the point I was worried about damage to the hardware or anything.

YMMV though and I would definitely suggest letting it sit till it cools down a bit

Edit: Somehow managed to quote the wrong person..
[Verizon Samsung Galaxy S 4] scarmon25:
Is it just me or is Google rolling out updates like majory fast. 4.4.2 now

http://xdaforums.com/showthread.php?t=2562534
[Verizon Samsung Galaxy S 4] NickSaul:
Every time I try switching to ART, I get prompted to reboot, I reboot, go into Settings, and Dalvik is still enabled.

Any ideas?
[Verizon Samsung Galaxy S 4] gunnermike:
Sounds like you have Xposed Framework installed.
[Verizon Samsung Galaxy S 4] NickSaul:
That would be correct! I didn't know that they were not compatible.

Thank you for bringing this to my attention. I'll probably just perform a clean install and not install Xposed.
[Verizon Samsung Galaxy S 4] ups2525:
Wallet works for me on 12/8 build

Wallet works for me on 12/8 build...just bought a book. :good:
[Verizon Samsung Galaxy S 4] mattyb65:
No matter what I do, I can't get calls to work anymore since flashing the 2/2 (I think) build. I've flashed other roms, went back to old backups but nothing is working. Basically it looks like the call is going through (whether incoming or outgoing) but I can't hear anything nor can anyone hear me. At this point the phone becomes very laggy. When I'm on a TW rom, sometimes I get an error message saying something about "the process com.android.phone has stopped"

Any suggestions?

Thanks,

Matt

---------- Post added at 07:29 PM ---------- Previous post was at 06:58 PM ----------

After finally going back and trying 1/31 build of CM11 and wiping everything, it seems to be working again. I'll leave this up just in case others are having the same problem.
[Verizon Samsung Galaxy S 4] jkc120:
Please +1 the sw nav issue if you've experienced it, thanks :)

For anyone using software nav who has experienced the issue where the nav buttons don't register, I've narrowed it down a bit. If you don't mind, please +1 this post on the CM community page, although it doesn't seem specific to CM (can reproduce on AOKP as well) nor to jf* as I've had confirmation that m7 and mako also see it and I was able to reproduce it (albeit not as reproducibly) on hammerhead.

https://plus.google.com/110825127270933703288/posts/14k9zoEBQuF

Thanks!

---------- Post added at 05:07 PM ---------- Previous post was at 04:44 PM ----------

Is this only on GSM? I tried a test call both inbound and outbound on Verizon and it worked fine. I'm on the MJ7 MDM if it matters.
[Verizon Samsung Galaxy S 4] phonedawg:
You can file a bug report and follow up. Thats your best bet. No one else cares about it.

http://forum.cyanogenmod.com/topic/...-properly-in-verizon-s4-jfltevzw/#entry414142
[Verizon Samsung Galaxy S 4] radpp16:
20140301 build is gonna rock!
[Verizon Samsung Galaxy S 4] FernBch:
20130301? That's a month away.....
[Verizon Samsung Galaxy S 4] JaeKay:
Which is why it's gonna rock ;)
[Verizon Samsung Galaxy S 4] FernBch:
I like your logic.....
[Verizon Samsung Galaxy S 4] scarmon25:
Actually that's about a year behind

Got a Ninja edit there lol
[Verizon Samsung Galaxy S 4] linuxthinker:
Thanks for the tip. I found this JIRA eventually linked off that topic: https://jira.cyanogenmod.org/browse/CYAN-2362

It turns out the fix is even easier than that. No build.prop or recovery changes; just replace the ril shared libraries from the AT&T build and I'm off to the races ^

I've started a thread with a flashable package with GSM rils: http://xdaforums.com/showthread.php?p=50030386
[Verizon Samsung Galaxy S 4] scarmon25:
Just noticed camera storage location is back. Able to set it to save to SD card.
[Verizon Samsung Galaxy S 4] noobnl:
on cdma ril you should try this:

ro.telephony.ril.v3=newDriverCallU,newDialCode
[Verizon Samsung Galaxy S 4] FernBch:
Stupid typo, lol. shoulda been 2014.
[Verizon Samsung Galaxy S 4] linuxthinker:
Ugh, I've accidentally soft-bricked my device by writing to the wrong partition. :( Would someone mind dumping their fota partition?

dd if=/dev/block/mmcblk0p22 of=/sdcard/fota.img

or

dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota.img

It should only be 10MB. If someone could zip and post it (plus an md5 to be sure), I would really appreciate it. Thank you!
[Verizon Samsung Galaxy S 4] jkc120:
Here you go. Good luck!

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

It's gzip'd, here is the md5:

f1c9645dbc14efddc7d8a322685f26eb *fota.img
[Verizon Samsung Galaxy S 4] suoirotoN:
Is this on the latest nightly(2014/2/4)? I have been waiting to flash because of all the problems so im still on 1/31 nightly. I really want this feature back!
[Verizon Samsung Galaxy S 4] spliffstar1904:
Black screen after fresh install

Hi guys. ive been flash for some time now on motorola devices and i finally got an s4 a lil while ago. its on the MK2 build, rooted and safestrap 3.71 installed. i downloaded the newest nightly and gapps and after installing and doing my wipes, i get a black screen with no boot animation at all. I waited almost ten minutes to see if anything would pop up and nothing. everything installed successfully and its on rom slot 1. am i missing anything?

Rod
[Verizon Samsung Galaxy S 4] swordmastr54:
Can't put aosp on anything past mdk sorry only two based ROMs.
[Verizon Samsung Galaxy S 4] brandonair95:
Its on 1/31 too
[Verizon Samsung Galaxy S 4] jkc120:
NP! Glad you got it sorted!
[Verizon Samsung Galaxy S 4] dstreng:
Has anyone successfully flashed the 2/4 nightly?
[Verizon Samsung Galaxy S 4] scarmon25:
I flashed the jflteusc 2/4 build just fine. Very similar to VZW builds. FWIW
[Verizon Samsung Galaxy S 4] vanberge:
I had to clean flash to get the option to show up. I'm on 1/30
[Verizon Samsung Galaxy S 4] blulite:
I figured out the problem with the screen not turning on during/after a call. It's not a CM11 software problem. It is a hardware problem (dirty glass in front of the proximity sensor). I've seen two methods mentioned on the web as potential fixes.

You can try compressed air into the ear piece (see if it blows the dust away).

OR

If that doesn't work you will need to take off the back-plate and clean the glass (mine had a black haze on it, came off with alcohol and q-tip).

Click here to remove the back-plate (your done with this video at the 2 minute mark).

Then here to see where/how to clean the proximity sensor.

Jeff
[Verizon Samsung Galaxy S 4] jkc120:
So I think the soft nav "issue" I was reporting is not a problem, but rather some behavior that wasn't working before but now is.

I have confirmation that it does this on m7 as well as mako, and my buddy at work let me borrow his hammerhead (Nexus 5) and I can reproduce it on stock 4.4.2 and also with cm11 M2 on his phone, though it doesn't seem to be quite as repeatable.

I'm guessing the software nav "dead zone" never quite worked properly or wasn't fully enabled/implemented, but is in kitkat. It's probably a good thing as it should help reduce accidental hitting of back/home/etc when typing or doing other things near the sw keys. It's just different and is going to take a little getting used to.

For me, that leaves the only issues (unless it's fixed on 2/4) for me being:

- battery life is slightly worse than on AOKP mr2 is for me

- wifi is slow (able to pull 55 down / 11 up on my cable modem on AOKP mr2 but only 11 down / 11 up on cm11 2/3 nightly)

As I leave wifi off most of the time anyway due to the annoying battery drain due to wakelocks (unless that's fixed in kitkat), the 2nd one doesn't bother me too much, and the first one is probably due more to my being able to use faux's kernel on jb and tweak some things. Or, it's just placebo *shrug*

I think I'll flash 2/4 and use it for a couple of days and see if there's anything else that's a showstopper.

One HUGE plus is that video recording works on cm11, whereas it does not on AOKP mr2 nor on their kitkat build. Huge thing w/a 2 month old :)

Oh, and the other major plus is, of course, the fixed boot hangs :D
[Verizon Samsung Galaxy S 4] brandonair95:
Speak for yourself my sensor works just fine on Touch Wiz
[Verizon Samsung Galaxy S 4] tjk639:
What kernel is everyone using for CM11?
[Verizon Samsung Galaxy S 4] brandonair95:
Stock normally but Chronic sometimes as well.
[Verizon Samsung Galaxy S 4] suoirotoN:
Yeah just changed it now, thanks for the heads up I've been waiting for this.
[Verizon Samsung Galaxy S 4] blulite:
Of course, I always speak for myself. I agree, TouchWiz is seams to deal with the dirty proximity sensor better, as it worked sometimes for me. But I can ABSOLUTELY state that with a newly cleaned sensor and CM11 (2/4 build) the phone goes dark when I put it to my ear, and lights up automatically when I pull it away from my ear.

Jeff
[Verizon Samsung Galaxy S 4] brandonair95:
Makes sense. I'm gonna try the compressed air trick first. Where do I blow it into? The hole where the headphone jack goes into or the metal grill at the top of the phone where your ear goes onto?
[Verizon Samsung Galaxy S 4] blulite:
I'm not exactly sure, I tried the mesh and it didn't work. Once I disassembled the frame I could see why, there was a good amount of black soot covering the glass where the sensor goes.
[Verizon Samsung Galaxy S 4] jfu:
Can confirm that dust is underneath the glass of the sensor. I just shined a flashlight over the sensors and see a layer of haze. Going to get a can of air sometime this week.
[Verizon Samsung Galaxy S 4] scarmon25:
Sounds to me like TouchWiz may be more sensitive with the prod sensor than cm. Well. Won't the be the first and certainly not the last time I take an S4 apart.
[Verizon Samsung Galaxy S 4] brandonair95:
I just opened it up and cleaned the lens. Was kinda hard since it's my first time doing it but thanks to all that helped especially scarmon25 and blulite :) :good:
[Verizon Samsung Galaxy S 4] BaronLager:
I had to do this exact thing, as this scenario was extremely frustrating. I also thought it was an AOSP issue, cause I didn't experience it with any TW based ROMs, or so I thought. After switching back and forth, the issue stuck, forcing me to clean the sensor.

I tried the compressed air trick, and it didn't work. I did find it very easy to disassemble the phone, and clean the sensor off from the inside.
[Verizon Samsung Galaxy S 4] jkc120:
Group messaging causes data drop?

So my wife's family included me on a massive group messaging thread, and I've noticed the "LTE" indicator goes away when I'm receiving the messages. I see bars but no LTE indicator, and I confirmed that the data connection is gone.

Is this normal? I don't remember if I saw this on jb or not.
[Verizon Samsung Galaxy S 4] brandonair95:
I don't belIeve it is normal. But I could be wrong of course.
[Verizon Samsung Galaxy S 4] jkc120:
hmm I think the group message was a coincidence. I think the phone just dropped data for some reason. In fact, I just saw the signal bars go empty (which is giving me flashbacks of my bad galaxy nexus whose radio would just crap itself randomly like 200 times a day). Wonder if it's just the network around here? Any way to find out why it's dropping?
[Verizon Samsung Galaxy S 4] scarmon25:
Wonder what we have here. http://review.cyanogenmod.org/#/c/59114/
[Verizon Samsung Galaxy S 4] brandonair95:
Not sure but personally LTE is spotty for me on AOSP. Most times I get 3g over LTE but on TW I mostly always get LTE. Make sure sure your data settings are LTE/CDMA/EvDo and I'd try a clean flash of tomorrow's build. It has a revolutionary new feature
[Verizon Samsung Galaxy S 4] jkc120:
Interesting, it was set to "LTE/CDMA/EvDo/GSM/WCDMA", so I set it to "LTE/CDMA/EvDo". Not sure that should make a difference since VZW doesn't use the other GSM frequencies do they?

Anyway, thanks! I'll see if it continues to do it.

FWIW, at home I am < 1 mile from a tower, and it was still doing this. So maybe it was as simple as changing that. *fingers crossed*
[Verizon Samsung Galaxy S 4] JCBiznatch:
I really like this Rom. Pretty stable from what I've noticed. Only problem I have is how hot the phone gets while tethering. This is a must for me to use so I have to find a way to keep heat down like on other roms I've flashed.
[Verizon Samsung Galaxy S 4] jkc120:
There's another complimentary commit w/that:

http://review.cyanogenmod.org/#/c/59120/1/msm8960.mk

Looks like it was basically just moved.
[Verizon Samsung Galaxy S 4] scarmon25:
I hate it when they do that stuff. Comment on stuff like that.
[Verizon Samsung Galaxy S 4] Recon0212:
1. Does anyone have random lockups that stop after about 10 seconds?

2. Does anyones BT drop randomly?

3. For those who use snapchat, does your front face recording work? Mine doesn't.

Thanks!
[Verizon Samsung Galaxy S 4] scarmon25:
The random lockups happen occasionally. Haven't had any of the other two.
[Verizon Samsung Galaxy S 4] .Ejekt:
I think I'm done updating for a while. Ever since that mess up with the bootloop a couple days back I've had some kind of device crippling issue on each update. The most recent, I can't open a single app once the phone has finished booting. I select the app from my drawer but nothing happens. Eventually, the phone just locks up and I have to pull the battery. Another NAND, another day.
[Verizon Samsung Galaxy S 4] FernBch:
Looks interesting............

This is listed under "depends on"

Multi-carrier overlays: Fix Mms
[Verizon Samsung Galaxy S 4] brandonair95:
It was set like that on mine too and my data wasn't stable but I changed it and rebooted and my data problem was fixed. Report back if it doesn't help :good:
[Verizon Samsung Galaxy S 4] thesoldier:
I experience the same snapchat issue as well.
[Verizon Samsung Galaxy S 4] Ironclad Lou:
http://xdaforums.com/showthread.php?p=50066037
[Verizon Samsung Galaxy S 4] brandonair95:
Wi-Fi Tethering doesn't seem so revolutionary

Good find tho
[Verizon Samsung Galaxy S 4] jkc120:
Thanks, so far so good! wonder why this isn't the default though for jfltevzw?
[Verizon Samsung Galaxy S 4] SonicJoe:
It's my understanding that all "Global" phones are set this way as default. It is the global mode. So you can take your phone out of the country and it will keep working.
[Verizon Samsung Galaxy S 4] jkc120:
Ah right, forgot it was a global phone. But I have to believe the vast majority of people running cm on their jfltevzw are using it on VZW only :)

Anyway, good to know! And this will survive a dirty flash, yes? I won't have to keep setting it when I update?
[Verizon Samsung Galaxy S 4] scarmon25:
Once it is set you don't have to change it each flash
[Verizon Samsung Galaxy S 4] jkc120:
Ok, figured it was stored on the data partition somewhere, but wanted to confirm, thanks!

Unfortunately, I can't just update as I prefer TWRP and also I disable the capacitive buttons, enable nav bar, and change the DPI. But those are a simple script so my process has been to dirty flash, wipe dalvik/cache, flash nightly, reboot recovery, run my script, reboot system. Work fairly well so far :)
[Verizon Samsung Galaxy S 4] brandonair95:
Any way to remove that plus sign on the quick settings tab?
[Verizon Samsung Galaxy S 4] scarmon25:
It shouldn't be staying there. It should only show when your editing them under settings.
[Verizon Samsung Galaxy S 4] irfan9490:
Compatibility

Hello Everyone,

I just had a quick question that will my galaxy gear work with this rom? I really wanna try the rom but don't want to end up going back to stock.

Thank You
[Verizon Samsung Galaxy S 4] scarmon25:
I don't believe so. I could be wrong but since the gear is touchwiz based it would need a touchwiz ROM to work with it.
[Verizon Samsung Galaxy S 4] TMYINC:
Like scarmon25 said I believe galaxy gear is touchwiz dependent at the moment. There may be a way to mod the galaxy gear to work with aosp but that's out of my league. 4.3 TW roms are the way to go for now as far as galaxy gear goes.
[Verizon Samsung Galaxy S 4] brandonair95:
Not sure of you guys know this but I found a Watch On flashable zip for 4.4.2. I tried it and it turned off my TV.

So go here and scroll down to optional downloads. It'll be the first link.

Also thank his post. That guy has been trying to port his GE 4.4.2 to Verizon.

http://xdaforums.com/showthread.php?t=2539361
[Verizon Samsung Galaxy S 4] tjk639:
Is there a way to have the TW camera app on here?
[Verizon Samsung Galaxy S 4] papstar:
Negative.
[Verizon Samsung Galaxy S 4] tjk639:
Figured as much. I just saw the watch on app from above and thought it was worth a shot.
[Verizon Samsung Galaxy S 4] FernBch:
I see something good in the next nightly!

"add more vzw eri's"
[Verizon Samsung Galaxy S 4] scarmon25:
I saw that too. Funny cause it's in the USC build as well lol. USC and Verizon builds are almost identical except for build.prop and the eri.xml. Guess sometimes things don't change. That's how it was back in the Fascinate/Mesmerize days. Good times.
[Verizon Samsung Galaxy S 4] jkc120:
Can someone explain what eri's are and why they're good? :)
[Verizon Samsung Galaxy S 4] FernBch:
Read here where it says " Carrier configuration in the Android OS"

http://seasonofcode.com/posts/carrier-programming-on-cdma-android-phones.html
[Verizon Samsung Galaxy S 4] linuxthinker:
Is it just me or is the microphone broken in VoIP apps (Skype, GrooVeIP)? It seems to work with a headset but the built-in mic is broken. Reports of it being broken all the way back in December; it's got to have been fixed by now, no?
[Verizon Samsung Galaxy S 4] linuxthinker:
IMO, CM should set this to CDMA/LTE by default. The "Global" functionality is pretty badly broken on GSM carriers without replacing the rils with AT&T's rils.
[Verizon Samsung Galaxy S 4] FernBch:
Not necessarily, I haven't seen it mentioned in a few weeks. If no one reports an issue it won't be looked into.
[Verizon Samsung Galaxy S 4] jkc120:
Thanks. So this stuck out:

It sounds like it's not really that "exciting"? I mean, it's nice you'll see a real name of a roaming partner or something, but functionally eri additions don't do anything, at least if I'm reading that right? Still, nice to have, but at least personally I'm not in the habit of looking at the carrier string :)

BTW, has anyone flashed the 2/7 nightly? The 2/4 is working so well for me, I haven't been really interested in updating. I haven't had the ~10s UI freeze *knock on wood* on this build, that I've noticed. And the only other issue I found was not an issue (nav bar thing), so I'm a happy camper.
[Verizon Samsung Galaxy S 4] FernBch:
Flashed 2/7 this morning, so far seems good.
[Verizon Samsung Galaxy S 4] swordmastr54:
I 2nd this I flashed with KT kernal and everything is fine. Only issue that I've seen in the past few builds is that nav with Google force closes and is glitchy anybody else seen this.
[Verizon Samsung Galaxy S 4] jkc120:
So the 2/7 build and KT kernel work ok? No wifi issues? Which governor/etc are you using? I've had pretty good battery life with the stock kernel tbh, but I'm always looking for better battery :)
[Verizon Samsung Galaxy S 4] swordmastr54:
I use the script of his and lower the CPU setting I've had 2 days many times before.
[Verizon Samsung Galaxy S 4] jkc120:
Which script is that?
[Verizon Samsung Galaxy S 4] swordmastr54:
Ktoonsified script and undisputed 3 for the profile I think I just have the annoying issue where the screen won't turn on when somebody calls.
[Verizon Samsung Galaxy S 4] asianrage:
I've been having that same issues for months now. I don't think it's a Kernel issue.
[Verizon Samsung Galaxy S 4] brandonair95:
We solved that a couple pages back. It's a problem where dirt gets into your Proximity Sensor. I opened up the phone, cleaned it up with alcohol and a q tip and it works flawlessly again.

Look for bluelites post about it a couple pages back