yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] jkc120:
True, but we don't yet know what causes the need to do this right?
[Verizon Samsung Galaxy S 4] jamesd1085:
Might just be like a glitch on off switch...it says it turns on but doesn't actually have the proper code to turn on all the way...
[Verizon Samsung Galaxy S 4] cixelsyddyslexic:
3/13 build fixed the APN/MMS issue for me. No new bugs noticed.
[Verizon Samsung Galaxy S 4] vdefender:
Yipeeee!!!!

Edit: CONFIRMED! ME TOO!! YEYEYEYEY
[Verizon Samsung Galaxy S 4] jamesd1085:
Did 3/14 nightly get you USC guys fixed up?
[Verizon Samsung Galaxy S 4] jkc120:
Don't think so :(
[Verizon Samsung Galaxy S 4] jamesd1085:
Did you try a clean flash...I had to on vzw...I tried dirty flashing 3/13 over 3/11 and still had the no APN blah blah going on...works perfect after clean flash though
[Verizon Samsung Galaxy S 4] jkc120:
I dirty flashed 3/13 over 3/3 and it was fine. I was referring to the USC specific problem of not being able to get 3g that scarmon25 has reported.
[Verizon Samsung Galaxy S 4] scarmon25:
I clean flashed today's build. No 3G. I formatted boot, system, cache, and data/media and flashed. No go.
[Verizon Samsung Galaxy S 4] jamesd1085:
Man that's crappy...my faith in cm has faded a bit with these unified builds and all the bs that came with them...I don't wanna jump ship for other ROMs just yet I have been happily using cm for years...hope these issues get ironed out soon
[Verizon Samsung Galaxy S 4] swordmastr54:
So do I just flash this for it to get a fix on me in GPS or what?
[Verizon Samsung Galaxy S 4] scarmon25:
Buddy I'm right there with ya. I personally think it would have been a lot better if they had done a unified CDMA and unified GSM build. To me it seems like it was rushed. I have supported CM and the devs for years. I've went on vengeful quest to destroy kangers of CM code and the devs that have worked on it. Calling it their own. But I am like you. Don't want to jump ship yet. And even if we did all the other ROMs use CM device trees so any issues like this will most likely carry over into that build.

It seems like any unified builds have this issue. AOKP doesnt because they remain separated. So I look at it as this is how it is for now. Might as well ride it out. Nothing else out there I like as much as I do cm.

---------- Post added at 03:56 AM ---------- Previous post was at 03:45 AM ----------

May bring back some hope for some of these issues.

http://www.cyanogenmod.org/blog/this-week-in-cm-mar-14-2014
[Verizon Samsung Galaxy S 4] jamesd1085:
Agreed...3_13 is the first 100% working build I have had(recently flashed and no bugs yet)since the first unified builds... Hope we are back on the right path
[Verizon Samsung Galaxy S 4] scarmon25:
3/3 was the last build I had 3G on. But with this news hopefully that will be fixed before long.
[Verizon Samsung Galaxy S 4] jamesd1085:
3/3 was pretty good for functionality but I got some random reboots which I hadn't seen for quite some time...I'm all good for now
[Verizon Samsung Galaxy S 4] vanberge:
Do you guys have the little up/down arrows indicating data transfer?

Not sure when it happened but I don't see them now. Had it on at least 3/14 and 3/15

---------- Post added at 06:50 AM ---------- Previous post was at 06:47 AM ----------

Edit..

They work on LTE but not on wifi
[Verizon Samsung Galaxy S 4] mcconvict:
Liquid Smooth has none of the issues that's cm based. Not trying to promote, just letting a fact be known
[Verizon Samsung Galaxy S 4] SinfulRoad:
It's promoting and no thanks, no problems here. Rather use a ROM that's been along a lot longer than that. Should also add you seem to be the only one saying on their thread that you have no problems, but others are.

Sent from my Unicorn'd S4
[Verizon Samsung Galaxy S 4] mcconvict:
I meant specifically the problem that has been going since the 3rd. Every ROM has issues. Someone said all the other cm based ROMs were having the same problem since the unified builds started. I simply stated that one did not. So relax and have a coke and a smile :)
[Verizon Samsung Galaxy S 4] rajones19:
Are there any known issues with BLE on CM11? Is anybody using FitBit, or any of the other fitness bands? Now that Jawbone's UP24 is Android-compatible, I'm thinking of making the leap - but if there likely to be problems, I'd rather find out ahead of time than learn the hard way. Thanks in advance.
[Verizon Samsung Galaxy S 4] FernBch:
Does anyone know if GPS is still borked on the VZW GS4? That is the only thing keeping me from coming back to CM11 from 10.2.1.
[Verizon Samsung Galaxy S 4] jkc120:
You have to:

1. flash a TW .zip

2. (in the same recovery session) flash the GPS fix .zip

3. boot into TW, get a GPS lock in google maps

4. reboot back to recovery, and restore your cm11 backup

Then GPS should work. Go back a page or two and you can find the TW zip and GPS fix zip that should work.

GPS works fine for me now!
[Verizon Samsung Galaxy S 4] FernBch:
The first time it quit I did the following:

1) Restored nandroid of stock rooted MDK.

2) Booted and obtained a GPS lock in moments with Maps and GPS Status & Toolbox. GPS functioned properly with both apps.

3) Repeated step 2 with CM10.2. GPS worked correctly.

4) Clean flashed CM11 GPS did not work.

I have not tried the zip (it is downloaded). I still hesitate because I do not want to have issues every time a new nightly comes out.
[Verizon Samsung Galaxy S 4] jamesd1085:
It works fine...but to get it going if you do have problems restore your stock backup and get GPS lock then restore back to cm11...GPS fix zip is an unnecessary step
[Verizon Samsung Galaxy S 4] JaeKay:
Anyone have a problem with the latest nightly where the screen won't boot up after a reboot?
[Verizon Samsung Galaxy S 4] jkc120:
Anyone here use faux kernel? I had tried 016 a while back and the signal bars were wrong I guess due to the signal reporting. I just noticed an "r2" version released a few days later and I'm wondering if that was a fix for the signal info. http://faux.romhost.me/jfltevzw/kk44/
[Verizon Samsung Galaxy S 4] moparfreak426:
what? I've heard you can set everything in hangouts but ive liked all over and can't find a way just to change the mmsc url
[Verizon Samsung Galaxy S 4] swordmastr54:
A lot of new updates for the next nightly a lot of it seems GUI fixes the rest I don't understand can anybody clarify it for me?
[Verizon Samsung Galaxy S 4] bsimpson1:
looks like there are quite a few changes to graphics/gpu-related stuff as well
[Verizon Samsung Galaxy S 4] jkc120:
For the person who noticed the WiFi traffic arrow indicators had disappeared the 3/16 nightly should have fixed it, according to the changelog.
[Verizon Samsung Galaxy S 4] vanberge:
yep... confirmed fixed!
[Verizon Samsung Galaxy S 4] radpp16:
M4 delayed?
[Verizon Samsung Galaxy S 4] crossen0:
Someone said earlier that build failed for our device so we aren't getting one?

---------- Post added at 10:43 AM ---------- Previous post was at 10:39 AM ----------

I'm using another aosp ROM currently but I want to run cm. If I get a GPS lock right before I boot into recovery to flash this do you think I'll be successful in getting a lock on cm?
[Verizon Samsung Galaxy S 4] jorceshaman:
It didn't exactly fail, it was never planned. The maintainers for all the new unified builds decided that they're too new for the M4 release. We'll probably see M5.
[Verizon Samsung Galaxy S 4] Lw00d:
i clean flash 3/15 yesterday , i dont have any of the issues people are reporting. no sms issue, no gps issue, everything i have tried works. i just flash it yesterday morning , will report if i find something.
[Verizon Samsung Galaxy S 4] swordmastr54:
I just dirty flashed today's build and my GPS seems to be better not sure if its spot on but its really close.
[Verizon Samsung Galaxy S 4] mjforte:
Anyone else have this problem. Happens every once in a while when I turn my screen on.
[Verizon Samsung Galaxy S 4] bsimpson1:
I've never had issues with gps in any of the recent builds but the magnetic sensor hasn't seemed to be working for quite a while.

---------- Post added at 08:43 PM ---------- Previous post was at 08:41 PM ----------

Yes, just a few seconds ago, actually. I wasn't really paying attention to what i was doing before i noticed it, so I'm not sure what i did to produce it.
[Verizon Samsung Galaxy S 4] swordmastr54:
That tends to only happen to me after I dirty flash a nightly on a background it messes up like that I go in and switch backgrounds then switch it back.
[Verizon Samsung Galaxy S 4] scarmon25:
I've notice if you're in an app in landscape mode and lock the phone. Then that will happen when you unlock it. I actually flashed 3/16 from a fresh Odin to stock and so forth. Testing it out with the switching background though.

Edit. Changed background. Still does it if I lock the phone while in an app and in landscape mode.
[Verizon Samsung Galaxy S 4] ecsnead69:
Can Xposed be used on CM? Thanks
[Verizon Samsung Galaxy S 4] OneNutShort:
I've successfully used it with CM in the past, but a recent attempt to install it on the latest nightly totally failed, and left me unable to boot. Flashing the nightly build again solved the problem, but obviously left me without xposed, and wasted about 10 minutes of my life. I guess what I'm trying to say is give it a try, but make sure to backup. It should be noted that I was also using Ktoonz kernal at the time, not sure if that matters.
[Verizon Samsung Galaxy S 4] bsimpson1:
Yes. Not all modules are compatible with CM, however. Be careful of modules intended for AOSP ROMs in particular, and learn how to disable xposed from recovery in case something goes wrong.
[Verizon Samsung Galaxy S 4] rajones19:
This. My GPS is fine - but my compass has its directions swapped. Google Sky, and the other astronomy apps are thoroughly confused by this.
[Verizon Samsung Galaxy S 4] jkc120:
That's a known issue and there is nothing CM can do about it afaik. We need the binary blobs/drivers for this to work, which we don't have or haven't figured out how to integrate into cm11 yet.
[Verizon Samsung Galaxy S 4] rajones19:
Thanks for the info on this. Hope they get what they need or get it figured out; from where I sit, this is the only 'flaw', although that may be too strong a word.
[Verizon Samsung Galaxy S 4] swordmastr54:
Yeah just tried the GPS its still not working right it can't get a lock on me.
[Verizon Samsung Galaxy S 4] FernBch:
Thanks for posting this info as this is what I was curious about. I use this feature quite frequently and if it isn't working correctly then I need to hold off on coming back to CM11. Where I work is very rural and I use the compass with a couple map/GPS apps to find some locations and knowing which direction to head is crucial.
[Verizon Samsung Galaxy S 4] jkc120:
If you get stuck I think the only way to get GPS back is to get a lock in Touchwiz then restore cm11. It'd be interesting to see what changes when this is done (assuming something in a partition or something you can query before / after). Then it might be possible to either fix it in cm or have a less evasive fix than having to flash TW and go back.
[Verizon Samsung Galaxy S 4] jamesd1085:
Make sure to back up before flashing next nightly if you are using custom kernel... Lots of kernel changes that might conflict until next kernel update
[Verizon Samsung Galaxy S 4] papstar:
Anyone able to successfully disable hardware keys? I'm using a zip that disables them, but I have to flash it after each nightly and a cm option would be much easier.
[Verizon Samsung Galaxy S 4] crossen0:
I was on a different ROM and was having the same issue so flashed the MK2 modem again and got a lock instantly. Maybe it'll work?
[Verizon Samsung Galaxy S 4] bsimpson1:
If you're using dalvik there's an xposed module called xposed additions that does it. I'm pretty sure there's also a way to disable them via an addition to build.prop

---------- Post added at 03:36 AM ---------- Previous post was at 03:33 AM ----------

Sorry, just looked at the rest of your post and neither of the ways i suggested would persist after flashing a newer nightly either.
[Verizon Samsung Galaxy S 4] swordmastr54:
Flashing the modem didn't seem to do anything about the GPS I'll have to wait or try a tw ROM anybody know a good tw ROM?
[Verizon Samsung Galaxy S 4] jkc120:
I just have a little script I use in a .zip that I flash after I update cm, but it looks like perhaps a commit went into the 3/16 nightly that would allow disabling them:

http://review.cyanogenmod.org/#/c/60659/

Which nightly are you on? I'm still on 3/13, since I've had no issues with it, but if you're on 3/16 maybe see if you can find the option?

---------- Post added at 09:12 PM ---------- Previous post was at 09:10 PM ----------

Question for you - when I flashed the MK2 modem a while back, this app: https://play.google.com/store/apps/details?id=com.cc.signalinfo stopped showing me the CDMA/LTE signal levels properly. Can you see if it works ok now w/MK2 and cm11? I went back to MJ7 and didn't want to update it again until it's fixed, though the radios worked fine.
[Verizon Samsung Galaxy S 4] jkc120:
Has anyone flashed 3/17 yet?

Any word on 3/17 yet? Any issues that weren't there previously? I hard that the camera may have been borked in 3/16, but was supposed to be fixed in 3/17.

---------- Post added at 07:17 AM ---------- Previous post was at 06:44 AM ----------

On VZW, the 3/17 seems good so far. LTE works, MMS works, GPS still locks. No issues noticed so far!

---------- Post added at 07:41 AM ---------- Previous post was at 07:17 AM ----------

Oh and I don't usually use BT, but I was able to pair with a Chevy Traverse without issue and the song title showed correctly. FWIW...
[Verizon Samsung Galaxy S 4] BaronLager:
Continuously get the "Camera has stopped." Error
[Verizon Samsung Galaxy S 4] jkc120:
Hmm, strange. Clean flash or if not, what did you dirty flash over top of?
[Verizon Samsung Galaxy S 4] BaronLager:
Dirty flashed over 3/5, *I think*.

I just went in to App Manager and cleared cache and data... seems to be functioning fine now. Guess I should have tried that earlier. :silly:
[Verizon Samsung Galaxy S 4] jkc120:
heh, that was going to be my suggestion, but I figured I'd ask first if you flashed over top of something else or if it was clean first :) Beat me to it! :good:
[Verizon Samsung Galaxy S 4] scarmon25:
Seeks like for uscc o my lockscreen and 3G is left.
[Verizon Samsung Galaxy S 4] asianrage:
I'm on the 3-16 nightly. I use HDWidgets all the time and I'm noticing a weird overlay issue when trying to use the app. It's as if the screen info keep getting layered/stacked on one another as you go from one screen to another. I don't know if this is something that's on HDWidgets' side, but I didn't get this issue when I was on the 3-15 nightly.
[Verizon Samsung Galaxy S 4] papstar:
That commit is the reason I asked, lol. I don't have the option on the 3/16 nightly. I use the script AOSP_navbar_enabled.zip. Is that the one you created? Can't remember where I found it.
[Verizon Samsung Galaxy S 4] jkc120:
Hmm yeah, the only option I see, which has been there a while, is to disable the backlights. I have my own .zip I created, but it also sets my DPI to 361. I can tweak it to only disable nav keys (via an edit to key layouts) and enable sw nav via build.prop edit in a bit once my kids are in bed for you!
[Verizon Samsung Galaxy S 4] jkc120:
Just remembered the way I do it is to have my zip just run a script from /data/local/bin I created (i.e. instead of shelling out each command inside the update-script).

But essentially, I'm just running these sed commands (overkill, but I was lazy and didn't want to find the right .kl files heh):

I can give you the .zip and .sh script to put in /data/local/bin (you'll have to make /data/local/bin and made the .sh script executable) but what you were previously doing should work, I'm assuming it's doing the same thing as the above, or something similar.
[Verizon Samsung Galaxy S 4] jackburnt:
I'm having the same issue on on a clean flash. Very strange.

Though, I'll take that issue over the APN issue from a few days back.
[Verizon Samsung Galaxy S 4] scarmon25:
Looks like 3/18 fixed the locksceen. Vide camera is broke though. B
[Verizon Samsung Galaxy S 4] jkc120:
Hmm, video camera works on 3/17. I guess one of those two camera commits broke it, though they looked harmless enough and I'm not sure why they'd affect the camcorder.
[Verizon Samsung Galaxy S 4] scarmon25:
Me either. Is yours broke too?

---------- Post added at 06:07 PM ---------- Previous post was at 06:04 PM ----------

I just replaced the camera2.apk with the one from 3/17. Video camera works again. :)
[Verizon Samsung Galaxy S 4] jkc120:
I'm still on 3/17. And now you've scared me away from 3/18 :p If no one else chimes in, I can flash it later for you and test.
[Verizon Samsung Galaxy S 4] scarmon25:
Just replace the camera apk with the one from 3/17, that way you get your lock screen fixed and camera/video camera
[Verizon Samsung Galaxy S 4] jkc120:
Observation: LED notifications (last first)

Not a bug at all, but something I did notice. I can't remember if it was when I went from 4.3-based AOKP to cm11 or if it changed in cm11, but I like the change.

Specifically, the LED notification order. Let's say I get notifications like this:

10:00 - incoming gmail (red LED)

10:05 - google hangouts message (green LED)

10:10 - incoming SMS (blue LED)

Previously in AOKP (and I *think* in earlier cm11 builds), what I would have seen was:

10:00 - red LED

10:05 - red LED

10:10 - red LED

i.e. until I clear that red LED, despite other notifications w/different colors, I still see red.

The way it works now, what I see is:

10:00 - red LED

10:05 - green LED

10:10 - blue LED

Why do I like this better? It's simple - if I see a notification, and don't care about it, the new way it works I don't have to pick up my phone and swipe away/clear the notification. I can just leave it and then if I see one I DO care about, I can wake my phone.

This is especially nice because I have a word game I play and with a ton of games open, before it was annoying because I'd have to clear the notification in order to see if I get an SMS or gmail message, etc.

Just an observation and I like the new behavior :)

---------- Post added at 10:13 AM ---------- Previous post was at 10:12 AM ----------

I don't use the lock screen, so I hadn't noticed that particular bug.
[Verizon Samsung Galaxy S 4] jkc120:
SMS messages staying marked read - weird

So on the 3/17 nightly, I'm noticing a weird thing I've never seen before.

Basically, sms threads are showing as "unread" even though I've read them and have even tried going into the thread and back out of it. I have found no way to have them mark read. Very bizarre.

I thought it was 8sms doing it, but I switched back to the default messaging app and it's doing the same thing now, so it seems ROM related.

Anyone else seeing this? Super annoying...
[Verizon Samsung Galaxy S 4] vdefender:
Yep me too. Came here to see if anyone else was having the issue.
[Verizon Samsung Galaxy S 4] jkc120:
Are you on 3/17 or 3/18? Hoping 3/19 fixes it, but I'm not sure what kind of commit to look for. Hmm...

Ugh this is super annoying. I might have to restore a backup.
[Verizon Samsung Galaxy S 4] rexdog1888:
Similar issue, however for me pressing read(in the notification bar, it's the middle button) makes it finally register as read
[Verizon Samsung Galaxy S 4] jkc120:
I dirty flashed back to 3/13. Couldn't take it anymore. lol
[Verizon Samsung Galaxy S 4] crookedview:
Try this - long press on the specific thread in the conversation list, you should get a little envelope-ish icon with a check mark in the bottom-right corner - press on that. It will confirm if you want to mark the conversation as unread, press yes or OK. Now just press on the conversation and back out. Should be marked as read now. I had this same problem with a few conversation threads.
[Verizon Samsung Galaxy S 4] jkc120:
Cool, but it's still annoying and I think I know why it is doing that. When a message comes into a group text if you ha e group MMS enabled, it seems to get confused and it transitions from a thread of regular sms with that person j to the MMS thread, but in the old nightlies it would move out of the individual thread and into the group thread and it seems in 3/17 it leaves a dangling reference to it in the individual thread.
[Verizon Samsung Galaxy S 4] vdefender:
I'm on 3/17
[Verizon Samsung Galaxy S 4] papstar:
Jkc, I'm all set with the script, no need to go out of your way. Thank you for offering though.

On another note, just had my SD card Mount unexpectedly. Rebooted, reseated SD card, nothing. Any ideas?
[Verizon Samsung Galaxy S 4] jkc120:
Well, had the random sms thread being marked unread issue after the 3/13 dirty flash so I restored my nandroid of 3/13.

WTF still doing it after I restored my nandroid!!

Maybe 8sms is at fault and corrupts things. I'll have to try restoring my nandroid then NOT updating to their latest version, but others are seeing this and not sure what sms client they are using. *confused*
[Verizon Samsung Galaxy S 4] jkc120:
It looks like it may actually be 8sms' recent update causing this:

- 3/13 with 8sms version 1.24 - no issues

- 3/17 with 8sms version 1.24 - I THINK no issues (don't recall how long after I updated that I updated 8sms)

- 3/17 with 8sms version 1.26 - unread sms issue

- 3/13 restored nandroid with 8sms version 1.24 - no issues

- 3/13 restored nandroid with 8sms version 1.26 - unread sms issue

I have to say, the 8sms dev is awesome. I've been emailing him back and forth and he's working on a debug build for me to test out as he's keen to squash this bug as well :)

So curious - of those seeing the unread sms issue (which, in the past, HAS been an android issue, but this seems different) how many of you are using 8sms? If not using 8sms, which sms client?
[Verizon Samsung Galaxy S 4] space_pimp:
I'm wondering if anyone has this issue with CM11 and Google Maps.

You're using google maps navigation and you turn off the screen. Then the screen lock sound plays twice, kind of overlapping itself.

This is no urgent problem, but I'm curious if anyone else has this problem, or can replicate it?
[Verizon Samsung Galaxy S 4] crookedview:
I had the issue and I only use the stock messaging app.
[Verizon Samsung Galaxy S 4] BaronLager:
Keypad issues

Here's my latest issue, and I've tried to search, but haven't found anything... My keypad just freezes when I'm trying to key in my pin number for my voicemail, or any other "Press 1 to continue" type function when I'm on the phone. It isn't the dialer, because that works fine, it's the keypad that pops up after the phone has connected. (see attached picture.)

I did a complete clean install of 3/18, after noticing this issue after I did a dirty install of 3/17.

I have to pull the notification bar down and hit the "hang up" button to actually hang up the call, because the big red hangup bar on the keypad screen is rendered useless.

I've tried to go thru all the dialer associated apps and clear data, etc., but nothing seems to help.
[Verizon Samsung Galaxy S 4] datboiro:
I've been having a process.phone stopped error since last week. Did an update Saturday morning and ever since I can't get anything JFLTE to play correctly. I've tried 5 different nightlies, and had to flash a jan7 nightly to get my phone operational again. The only thing I can say, with certainty, is that my phone never connects to the cell tower and there's no way to get into the mobile network settings. I usually search until I find my solution... but I honestly need help. Anyone?!
[Verizon Samsung Galaxy S 4] jkc120:
Weird, I haven't tried 3/17 or newer with 8sms 1.24 but it most certainly happens with 1.26 8sms regardless of cm11 version.