yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] stoicwood:
Happy to hear people are having success with the GPS. I have been running the latest nightlies for a while since I couldn't stand to lose the latest features. The only issue I have had with the latest builds (currently running 10/19) is GPS locking quickly, but failing to update. It has been probably 1.5 - 2 weeks since a clean flash, so I'll give that a go and see if that fixes my issue. All data/SMS/MMS/BT that I have used work fine without any fiddling and I use Hangouts + Voice for those with questions about the difference.

To clarify: GPS locks correctly when location is turned on, but if I travel it will be inaccurate as if it is only using cell for location, updating infrequently and location being off (possibly tower location). It was too much for me to troubleshoot while traveling over the weekend and I haven't been using any navigation in a few days while in town to have given it a good test. I will use it more fully after a clean flash and post back if I come up with any issues.
[Verizon Samsung Galaxy S 4] FernBch:
FWIW, if anyone else is having issues viewing the changelog I created an issue for it.

https://jira.cyanogenmod.org/plugins/servlet/mobile#issue/NIGHTLIES-282
[Verizon Samsung Galaxy S 4] rajones19:
Did a clean flash of the 10/21 nightly, figuring I would try and get along without the compass. Now seeing system.ui force closes when trying to rearrange the quicksettings tiles. I swear, if it's not one thing, it's another. Getting to the point where TouchWiz is almost starting to look good. Back to M9. Again.
[Verizon Samsung Galaxy S 4] .Ejekt:
M94lyfe.
[Verizon Samsung Galaxy S 4] rajones19:
Sure seems that way!! LOL!
[Verizon Samsung Galaxy S 4] vanberge:
I'm on 10/21 and have had no problems. Been solid since probably 10/17 but I dont care about compass.

Stock kernel, Paranoid Gapps
[Verizon Samsung Galaxy S 4] FernBch:
I can confirm this issue. I tried to move a tile to a new location and when I let go for the change to happen I had an FC in systemui. I'll do it again, get a logcat, and create a new report at JIRA. Did this work previously? If so, when was the last nightly you remember it working. This info is needed for the JIRA report.

---------- Post added at 09:18 PM ---------- Previous post was at 09:17 PM ----------

Edit:

Can anyone on M9 (that snapshot works) confirm this?
[Verizon Samsung Galaxy S 4] rajones19:
Sorry, Fern, I can't provide much help. The tiles work on M9. Since then, my process has been 1) flash ROM; 2) do setup 3) install GPS Status and Google Sky Map; 4) check compass orientation; 5) restore nandroid to M9.
[Verizon Samsung Galaxy S 4] FernBch:
Ok, I have the logcat and can recreate the issue at will. I can move tiles one at a time but each move results in a FC of systemui.
[Verizon Samsung Galaxy S 4] FernBch:
Ok, here's the report at JIRA for the Tile/systemui FC issue.

https://jira.cyanogenmod.org/plugins/servlet/mobile#issue/NIGHTLIES-287

If you add anything please include a logcat if you can.
[Verizon Samsung Galaxy S 4] Train88:
I'm still currently on 10-13 and I successfully moved a tile without a crash.

Team BlackOut... or Back Out - "These colors that you've shined are surely not your style”
[Verizon Samsung Galaxy S 4] FernBch:
I received a message from Pshycol3oy, he thinks a particular commit was merged that may address the systemui crash. I'll let you know after flashing.
[Verizon Samsung Galaxy S 4] stoicwood:
With a clean flash of 10/21 I am seeing the following. Some of this is old news and some of it seems to be things other people have no issues with.

1. No GPS lock. I had thought previously that I was getting some GPS lock and it wasn't updating, but after testing with GPS Status & Toolbox it seems that I never get any GPS lock. I haven't heard of anyone else having this problem with the latest nightlies, so I'm confused on it.

2. The 180° compass is exactly the same for me as FernBch has documented well.

3. Proximity Sensor doesn't seem to work at all, showing "Near" constantly on Phone Tester. I would like to know for sure if anyone else has this issue.

4. As has been stated and reported a few times already, I can also reproduce the systemui crash moving tiles, but the tiles DO move. Hopefully the offending commit was found already, though.
[Verizon Samsung Galaxy S 4] Erievon:
So just to experiment, I dirty flashed from M9 to the 10/19 nightly. With the kernel change and blah blah I just wanted to see what would happen, even though a clean flash was recommended. Here's what I got:

I can move quick tiles around, no problem. GPS locks just fine, quickly too. WIFI, 3G, LTE handoffs are working with no issue. Bluetooth connects and disconnects as it should (little more on this in a bit).

Compass is out 180 degrees, I expected that.

Edit: I should mention I'm on the NC5 modem, have been since it came out.

For Bluetooth though, I have had this issue since I first loaded CM11, and it's never been fixed for me. I can't use Bluetooth with Google Now. If I set google now to record through the bluetooth, and then initiate a voice command, it will lock up google now to a point of non response, requiring a reboot.

Now, if I leave bluetooth connected, but turn off the setting for GNow to work via the bluetooth, all is well. I can use bluetooth for calls and such, and I can use the phone's mic and speaker for GNow with no issues. Anyone else see this issue as well?
[Verizon Samsung Galaxy S 4] stoicwood:
I placed my phone on a metal table and it straightened my compass almost perfectly.

Edit: Flashed 10/22 and the tile rearranging issue is fixed.

I may try clean flashing M9 to test everything, then dirty flashing 10/22 similar to Erievon. Got me curious.
[Verizon Samsung Galaxy S 4] FernBch:
GPS lock happens quickly for me. There were, however, two instances where it wouldn't. Try getting a lock and see it not work, immediately exit GPS S&T and reboot, then try again. Both times I would quicly get a lock afterwards.

For the BT/GNow issue try to get a logcat and/or last_kmsg and create and issue at JIRA. That is the best bet to get it fixed. The preferred way would be from a snapshot instead of a nightly. The exception would be if you know that it previously worked on a nightly then reporting a regression is ok.
[Verizon Samsung Galaxy S 4] stoicwood:
I'll give this a go after I get done playing with the M9 > latest nightly shenanigans and report back.
[Verizon Samsung Galaxy S 4] FernBch:
Flashed 10/22 a little while ago and I can confirm the systemui FC is fixed. I can rearrange tiles without issue.
[Verizon Samsung Galaxy S 4] FernBch:
Experienced something very strange a few minutes ago. If you have WiFi on and connected, have BT on paired or not paired, and cycle BT off and on with a long delay between the two (5+ sec min) everything is fine. If you cycle BT off and on with a short delay between the two WiFi and mobile data may disconnect. Mobile data usually reconnects quickly but WiFi does not. In order to get WiFi to reconnect usually you only need to cycle WiFi off and on but sometimes airplane mode must be cycled to get it back.

NOTE:

My BT devices work properly without any issues or workarounds.

NOTE#2:

As long as BT is cycled off and back on with a 5-10 second minimum delay between the two there are no problems.

Either way BT itself, IMO, is not broken and all the associated functions/features of my BT device work perfectly.

I have updated and attached a new Logcat to this JIRA report.

https://jira.cyanogenmod.org/browse/NIGHTLIES-245
[Verizon Samsung Galaxy S 4] gonzlobo:
Sounds like I need to temporarily flash this. I jump between 2 BT devices several times a day.
[Verizon Samsung Galaxy S 4] BaronLager:
Yep. I noticed this last night. I was trying to connect to my hot tub, and the WiFi dropped out, BT was cycling on and off, then everything went back to normal and worked fine. Weird, wild, whacky stuff.
[Verizon Samsung Galaxy S 4] stoicwood:
My experiment with clean flashing M9 then dirty flashing 10/22 had no adverse effects that I can see and fixed all issues I had with my GPS failing to lock. I have not seen that issue again.

Only current issue I see is the Proximity Sensor always reporting "Near" which I am waiting on someone else to confirm before I tear my phone apart. Tiles fixed, GPS lock fixed, BT and WiFi/Data fixed, etc.

I tried this with the setup above and can't reproduce what you have. I am connected to WiFi with BT on (no devices nearby), and I can toggle it at any speed with expected results. WiFi stays connected, no change to Data, and BT toggles.
[Verizon Samsung Galaxy S 4] Erievon:
It's always been a problem for me since CM11 began, so I can't report it as a regression. What I may do is live with it until the next snapshot, then report it officially.

But here's the thing, I've been dirty flashing since the beginning of CM11 too (I clean flash usually on a full version upgrade). Everything but this one item works perfectly for me, so I'm wondering if anyone else has tested this and has the same issue. If I'm the only one, then I may try a clean flash before I get the DEV involved with the issue.
[Verizon Samsung Galaxy S 4] FernBch:
I've cleaned flashed a couple times along the way, last time was with 10/13 so I'm not sure that will matter.
[Verizon Samsung Galaxy S 4] snakecharmer23:
A shot of compressed air might be all you need to fix the proximity sensor. Shoot it right into the ear piece (not your ear!). :good:
[Verizon Samsung Galaxy S 4] FernBch:
Flashed 10/23 today. So far I only see two things.

GPS/Compass: GPS lock works perfectly. Compass orientation correct when moving but off by 180° when stationary or walking. Issue open at JIRA.

BT/WiFi: Individually both items seem to be fine without issue. No workarounds required and my BT devices works flawlessly. If you cycle BT off/on without enough wait time between the off and on WiFi will disconnect. If you wait several second to turn BT back on WiFi is unaffected. For now just don't turn BT back on without waiting. Issue updated at JIRA.

Overall opinion. Still worthy of daily driving.

---------- Post added at 10:04 PM ---------- Previous post was at 09:52 PM ----------

So, What does everyone think?
[Verizon Samsung Galaxy S 4] vanberge:
I'm daily driving it since 10/17 and have been good with it. Thanks for all your help fern leading us through the dark times Lol.
[Verizon Samsung Galaxy S 4] FernBch:
I think it would be great to see a RC or Stable build before they get too deep into lollipop......
[Verizon Samsung Galaxy S 4] stoicwood:
Thank you for the suggestion, and I played with it a little bit further, but the more I look at it, the more it seems like a software issue. If I use the Phone Tester app, I can turn the screen off, then on, and it will show "Far" until I put something in front of it. After something has passed (even briefly) in front of it, it shows "Near" until I turn the screen off/on again. If no one else has this issue, then I could be unrelated software, but I thought someone else had mentioned proximity issues a few pages back.

Edit: I dug up a can of compressed air = fixed. Evidently the "on" sensitivity for the proximity sensor is higher than the "off" sensitivity. Conclusion: unrelated problem.
[Verizon Samsung Galaxy S 4] BaronLager:
I'd love to be using it, but for some reason, my MMS is broken. Tried Hangouts, Textra, and the stock messenger. Hit or miss getting images, absolutely no group texting. It was working just fine, then I did a clean install, and lost all functionality... yea, I would restore, but my SD card got hosed also, so I'm stuck. :crying:

I'm going to go back and try some experimental builds and see what happens.
[Verizon Samsung Galaxy S 4] BaronLager:
For what it's worth, I went back and did a complete clean re-install of 9/28, because that's what I remember running for the longest time. MMS was un-broken. Dirty install of 10/23, things working perfectly again. Must have something to do with the magic of 9/28
[Verizon Samsung Galaxy S 4] FernBch:
10/25 just dropped. Will be flashing as soon as the download completes.

---------- Post added at 07:48 PM ---------- Previous post was at 06:52 PM ----------

Here's my initial report of 10/25.

Upon initial boot up there is an issue with WiFi disconnecting when turning BT off. Once this happens WiFi will reconnect after a few minute wait but BT will not turn back on. After a reboot I could turn BT back on but doing so caused WiFi to disconnect again. I then cycled WiFi off and back on but it would not reconnect. I then turned Airplane Mode on. Mobile Data and BT turned off as expected but WiFi stayed on and connected. I then turned Airplane Mode back off. WiFi stayed on and connected and Mobile Data and BT came back on. After all this everything seems to work properly. I have added and update and new Logcats here:

https://jira.cyanogenmod.org/plugins/servlet/mobile#issue/NIGHTLIES-245

If you flash 10/25 and experience the above just follow what I did and everything should work again.

---------- Post added at 07:51 PM ---------- Previous post was at 07:48 PM ----------

As for GPS Status and Toolbox (I use it, too) I am getting a GPS lock in moments but the compass is still off by 180° only when stationary or walking. When driving orientation is correct because GPS calculates orientation.
[Verizon Samsung Galaxy S 4] gonzlobo:
Flashed today's build (first build for me in months). BT works nearly flawlessly.

My phone immediately switches between my headphone (Sennheiser M400) & truck stereo. After switching between the 2 no fewer than 10 times, I then paired up to all 3 computers in my house and transferred a small file between my phone and the computers. When that worked, I flawlessly connected to all 5 BT devices and had no problem switching amongst the devices.

Will evaluate all night tonight and Sunday. If it works, it will be my weekday driver.
[Verizon Samsung Galaxy S 4] thcaddict:
Am I able to install this on my MK2 verizon S4 with safestrap? I would really like to use something other than my stock rooted app that I've had for like 6+ months now =(
[Verizon Samsung Galaxy S 4] hlxanthus:
Sadly, no.
[Verizon Samsung Galaxy S 4] FernBch:
Anyone try CM11 with NG6_apnhlos yet or do I need to be the Guinea pig?
[Verizon Samsung Galaxy S 4] Alarbus:
I've been using NG6. Works fine. Signal seems about the same. When I update (which isn't daily), I dirty flash, and haven't been having the odd toggling issues you have, so maybe it's better in that regard?
[Verizon Samsung Galaxy S 4] FernBch:
Some of the users in the Int'l GS4 CM11 thread are saying the same thing as they are having the same issue. I guess I'll have to wait for 10/26 to drop to be sure. As it sits currently the issue persists with NG6.

---------- Post added at 10:22 AM ---------- Previous post was at 10:11 AM ----------

I may need to scratch that last thought. So far there is not a single new commit for today.....
[Verizon Samsung Galaxy S 4] FernBch:
Flashed 10/26, the WiFi disconnect when BT is turned off/on issue is still present. I guess it doesn't matter which modem or modem+apnhlos package is used. I have seen this with the MK2, NC5, and NG6 packages.
[Verizon Samsung Galaxy S 4] hlxanthus:
Curious how you are getting MMS working. Using hangouts. I have not been able to get it working on any newer build on cm or any ROM using cm device tree for jflte.
[Verizon Samsung Galaxy S 4] BaronLager:
I had the same issue, but as in my previous post, I fixed the problem by clean flashing cm-11-20140928-EXPERIMENTAL-RIL-jflte.zip, (https://download.cyanogenmod.org/get/jenkins/85180/cm-11-20140928-EXPERIMENTAL-RIL-jflte.zip), then dirty flashed up to what ever the most current version is.

After doing this, MMS worked perfectly, using Hangouts.
[Verizon Samsung Galaxy S 4] ctoph0:
So I'm on m9. What is the safest way to upgrade? What date is the most fully functional. Compass orientation isn't too much of a big deal to me.
[Verizon Samsung Galaxy S 4] FernBch:
Clean or dirty flash. Make a nandroid first. The latest nightlies have been fairly good again. Just a few issues which have been detailed in recent posts.
[Verizon Samsung Galaxy S 4] gonzlobo:
Backup first (as you always should).
[Verizon Samsung Galaxy S 4] .Ejekt:
I'm in the same boat. By the looks of it, whatever is most recent should be fine. Of course, a clean flash is always recommended. Pull the trigger, post your results.
[Verizon Samsung Galaxy S 4] ctoph0:
Clean m9
[Verizon Samsung Galaxy S 4] .Ejekt:
Just dirty flashed from M9 to 10/27. Seems to be working fine!

Edit: GPS, works. MMS, works. BT, works. Gonna miss my KToonz, but CM11 seems perfectly stable once again!
[Verizon Samsung Galaxy S 4] phonedawg:
Compass?
[Verizon Samsung Galaxy S 4] ctoph0:
On 1027 as well. Working like it should so far. Bluetooth came right up

EDIT: I was not able to get a GPS lock using 10/27, even with GPS Status.
[Verizon Samsung Galaxy S 4] stoicwood:
I dirty flashed from M9 a few nightlies ago, and have had only the reported issue of the compass showing around -180°. That is not fixed as of 10/27. Also, the issue with toggling BT off and on has not been present for me at all with a clean flash of M9 to a dirty flash of the more recent nightlies.
[Verizon Samsung Galaxy S 4] ctoph0:
I was not able to get a GPS lock using 10/27, even with GPS Status.
[Verizon Samsung Galaxy S 4] .Ejekt:
10/27. Seems MMS is temperamental. Can't find any consistency to the issue - sometimes it works, sometimes it doesn't - a reboot fixes it when it's borked.
[Verizon Samsung Galaxy S 4] stoicwood:
I haven't had an issue getting a quick lock in a few days. I haven't had to do any workarounds. Clean flash?
[Verizon Samsung Galaxy S 4] ahaynes42:
Same here. I've tried both Hangouts and stock messaging. What's weird about the Hangouts app is that my APNs are set to MetroPCS and Sprint, even though I'm on Verizon. When I try to modify or create a new APN, it won't save. The main APN settings under Mobile Networks are the correct Verizon ones, but it's the Hangouts settings that I can't modify.
[Verizon Samsung Galaxy S 4] ctoph0:
Seems like a group of us were on M9 and just updated with a dirty flash. I can not get a GPS lock on 1027. MMS through textsecure did not send upon first test

---------- Post added at 10:14 AM ---------- Previous post was at 10:07 AM ----------

I have noticed this same issue with hangouts, i left it for textsecure. After inputting the correct verizon intointo TS and running M9 MMS worked fine.
[Verizon Samsung Galaxy S 4] FernBch:
The BT issue seems to be fixed. For the BT/WiFi issue see if you get this:

Make sure WiFi and BT are on (easiest to check from the tiles as you can see everything at once). Then turn BT off and wait 10-15 sec (nothing strange happens), next turn BT on and wait several seconds. Many are reporting that WiFi disconnects but does not turn off after doing this. To get WiFi to reconnect turn Airplane Mode on and wait. Many will see BT and Mobile Data turn off but WiFi stays on and connects. Then turn Airplane Mode back off. WiFi stays on and connected and BT/Mobile Data comes back on and everything works properly after.

Try rebooting and see what happens after. I have seen two instances of this since 10/17 but GPS will lock after a reboot.

I can offer no help here as I use the stock messaging app. I would suggest making a detailed report at JIRA complete with logcats.
[Verizon Samsung Galaxy S 4] stoicwood:
Tested this and my results are the same with any interval of BT being off, 2 seconds, 10 seconds, 20 seconds, etc. WiFi remains on and connected and BT toggles appropriately. I know it probably doesn't count since I didn't get the first issue, but I toggled Airplane to test and it worked appropriately, turning off all radios, then back on.

Since I dirty-flashed from M9 about a week ago, I have not seen a single instance of GPS not locking immediately, but it could be as Fern pointed out and I have just been lucky.

I use Hangouts without any issue, but mostly Google Voice and rarely MMS even with it. I can attest to the APN settings in it being on Metro, but I don't know if it even pays attention to them. I'll try an MMS and see what happens.
[Verizon Samsung Galaxy S 4] heath2805:
Try "GPS fix" in play store. Worked for me.
[Verizon Samsung Galaxy S 4] ctoph0:
I'm back to m9 now

Sent from a toaster in space
[Verizon Samsung Galaxy S 4] FernBch:
Flashed 10/29 and I am pleased to report that everything is the same for me over the last few nightlies. GPS lock works, compass orientation is off by 180° when stationary/walking and is correct when driving, and WiFi still disconnects when I turn BT on. WiFi stays on and connects when Airplane is turned on. When airplane mode is turned back off WiFi, BT, and mobile data work properly. I have no issues with BT or connected devices. The WiFi disconnect can be readily repeated.

That is all.
[Verizon Samsung Galaxy S 4] stoicwood:
Also on 10/29 with the same results minus the BT and Airplane mode quirks. I am interested if anyone flashing clean to one of the later nightlies (10/17+?) has the same issue, and also if someone clean flashing M9, then dirty flashing one of the newer ones over it has this issue. I can't think of any quirks in my setup that would make these work properly for me.

So, the only issue I still see is compass orientation off by 180°.

I may turn off Tasker in case some of my profiles are somehow bypassing the quirks you see.
[Verizon Samsung Galaxy S 4] FernBch:
I did a clean flash of 10/18 and dirty of the nightlies after. I guess I should try M9 then dirty flashing the latest over and see what happens.
[Verizon Samsung Galaxy S 4] indolent:
I'm not sure if this is a CM issue or not, but is anyone having problems with driving directions since the latest google maps update (10/24)? I'm on M9. The driving directions no longer say exit numbers or street names. It's just the generic, turn right at the next exit, or turn left here, etc. Anyone else have this issue?
[Verizon Samsung Galaxy S 4] gonzlobo:
I have flashed the last 5 nightlies after a 2 month dry spell. All is well.
[Verizon Samsung Galaxy S 4] stoicwood:
I couldn't reproduce this issue on 10/30, but I probably didn't ever use turn-by-turn on M9 or most of the nightlies. It has been a while. I haven't heard of any problems with M9, so I would say it is probably not a CM issue. Try clearing Maps data and/or re-installing. My Maps version is 8.4.1.
[Verizon Samsung Galaxy S 4] indolent:
Yeah, I've cleared text to speech and maps data without help. Probably just need a fresh install.
[Verizon Samsung Galaxy S 4] Slim1023:
I've seen two different causes of street names not being read:

1. Text to speech not working properly. Make sure you go in and install the high quality package for it.

2. No, or poor data. Google needs data to speak to you.

Unfortunately, from what you're describing it seems like you're probably coming across a different cause, but figured I'd let you double check these issues.
[Verizon Samsung Galaxy S 4] FernBch:
Been playin around with modem packages for the last day. Yesterday I decided to reflash my modem. Started with the MDK+nonhlos to match my bootloader and ended with the NG6 modem. Today when I flashed the last nightly I seem to have one less issue. WiFi no longer disconnects when I cycle BT. It was fine when turning BT off but would disconnect when I turn BT back on. I wonder if things got a little out of whack over the last couple weeks.

If this holds steady I am down to one issue affecting me, compass orientation is still off by 180°.
[Verizon Samsung Galaxy S 4] TMYINC:
I had actually done this a while ago. I just reverted back to nc5 because my data speeds seemed better. Switched back to the mdk+nonhlos after the 3rd or 4th modem came out and have been flashing just the modems since.
[Verizon Samsung Galaxy S 4] FernBch:
I've always ran the MDK nonhlos but tried the NC5+nonhlos a couple weeks back hoping to fix the issue with the three I was having. The last few days I've been playin around tryin to get around the WiFi disconnect issue and figured I'd try it. Been good since.........