yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] Chris123NT:
They're not going to revert it, they want to find a "different fix", meanwhile the setrate fix meant not having to hack sensorservice to hell and back again lol.
[Verizon Samsung Galaxy S 4] scarmon25:
Yeah I should have worded that better. I read the commit that had been undone and was watching for a commit that coincided with the sensor service

---------- Post added at 09:55 PM ---------- Previous post was at 09:51 PM ----------

Which looks like there is a ton of commits in the next build. So not sure if any of those touch that particular issue. Just have to wait and see :)
[Verizon Samsung Galaxy S 4] reinert012:
Also getting solid green light, running ktoonz.
[Verizon Samsung Galaxy S 4] FernBch:
Surge posted up a flashable zip with the MK2 modem and nonhlos.bin here:

http://xdaforums.com/showthread.php?t=2487298
[Verizon Samsung Galaxy S 4] scarmon25:
Flashed the one with the hlos modem and everything seems to be working just fine.
[Verizon Samsung Galaxy S 4] scarmon25:
Seems like I can turn WiFi off but not back on til I reboot since I flashed the modem. Not sure if that is indeed a modem issue or something I just missed being a issue. Flashed back to the MDK modem and all is well again so either isolated to me or indeed a modem issue.
[Verizon Samsung Galaxy S 4] ups2525:
I have been round and round on this problem. Go back probably 10 pages and you'll see my notes. I think the WiFi power saving mode causes and or contributes to the problem. I think its a Sammy issue now you can turn it off in TouchWiz via the Samsung hidden menu and the WiFi is rock solid thereafter. I have searched to the ends of the earth and cant figure out how to turn this off on an AOSP ROM or get to the Samsung hidden menu for that matter. There is an option in systemsettings>wifi>advanced>wifioptimization which I have disabled but to no avail, problem is still there.

Have we had a build since 12-17?
[Verizon Samsung Galaxy S 4] Alxoom33:
I have had wifi problems on newly flashed update, which were fixed for mearly flashing latest KToonsz kernel. I take it you can now see your SD card on this ROM.:sly:
[Verizon Samsung Galaxy S 4] scarmon25:
Flashed the new build. Sadly rotation still isn't fixed but I understand why. It'll be fixed soon enough

---------- Post added at 04:22 PM ---------- Previous post was at 04:10 PM ----------

Well I wiped cache and dalvik and it seems to be working now. Hmmm

---------- Post added at 04:24 PM ---------- Previous post was at 04:22 PM ----------

Proximity sensor still seems borked. Putting the phone up to the ear while on call leaves the screen on. Again kind of expected that
[Verizon Samsung Galaxy S 4] reinert012:
Just reported i am getting a solid green charge light on ktoonx OTA 12/18 build, without the kernel i dont have the problem.
[Verizon Samsung Galaxy S 4] reinaldistic:
Its more to kToons to fix that than CM
[Verizon Samsung Galaxy S 4] reinert012:
great, thanks. Wasn't sure where to post it.
[Verizon Samsung Galaxy S 4] RedBullet:
Good enough?

So is this good enough to use yet? What are the major issues with current builds?
[Verizon Samsung Galaxy S 4] scarmon25:
It has its little quirks here and there. Nothing too major. Rotation doesn't work occasionally and proximity sensors are not working. Those should be fixed soon I would think.
[Verizon Samsung Galaxy S 4] vanberge:
I'm using 12/12 build as my DD and it's pretty solid.

I can't pick my SD card for camera storage, and I dont have an option to remove the input / keyboard notification icon in the task bar.

Waiting for a some of the quirks scarmon mentions to get wrapped up before I move on to newer builds.
[Verizon Samsung Galaxy S 4] vanberge:
Just when I was thinking about jumping off of m9.... ?
[Verizon Samsung Galaxy S 4] gonzlobo:
Stay with m9.
[Verizon Samsung Galaxy S 4] .Ejekt:
Clean flash of 9/11, I don't have a single issue.
[Verizon Samsung Galaxy S 4] whiteout7942:
Same here. Clean flashed and everything is working so far. GPS was not locking but I just needed to restore my old gps.conf file and it locked on right away. Compass works fine on 9/11 build. You need to be on the stock kernel right now because the CM team apparently did some big changes that messes with custom kernels (wifi not turning on).
[Verizon Samsung Galaxy S 4] vanberge:
Well gosh dang it you guys now I want to go back to the nightlies... Dont enable my flashaholism.
[Verizon Samsung Galaxy S 4] whiteout7942:
I would maybe hold off if you are comfortable on M9. I have a feeling an RC is coming soon with the way things are running right now. The kernel is pretty stable now :)
[Verizon Samsung Galaxy S 4] FernBch:
Maybe I will clean flash the latest......
[Verizon Samsung Galaxy S 4] jkc120:
The overly loud and distorted max volume bug still exists so hopefully M10 comes soon so we can file an official bug.
[Verizon Samsung Galaxy S 4] gt5oh:
Just installed M9 -- first time on CyanogenMod in over 3 years... How do I tell if I am on 4G or 3g ?

Edit Nvm just realized wifi was on

does this come with an updated radio or do we need to install that ourself?
[Verizon Samsung Galaxy S 4] jkc120:
ROMs should not be touching radios generally speaking, and that's the case for cm11 as well.

FWIW, I have had no issues with NC5 MODEM+NON-HLOS from here:

http://xdaforums.com/showpost.php?p=46550751

invisiblek I think mentioned latest should be what to use at this point, though others will probably work fine.
[Verizon Samsung Galaxy S 4] drt054:
I was on Liquid Smooth for about a day but had to cone back to CM.. It's a sickness I tell ya. Luckily copied the gps.conf along with the liquid wallpapers since they are pretty sweet decorations.. But clean flashing 9/11 everything looks good.
[Verizon Samsung Galaxy S 4] gt5oh:
If I installed a radio on a previous rom and did a clean wipe to install CM does that erase the previous Radio & Kernel?
[Verizon Samsung Galaxy S 4] hlxanthus:
Radio is an entirely different partition and will survive a wipe. Kernel is replace with every new ROM install
[Verizon Samsung Galaxy S 4] MustGoFast:
ummm.. Help Please.

So now I can edit APNs (sort of).. I go into the menu, make the changes listed before, click save and then that APN that was selected disappears. I tried restoring to default and got a new list entirely... still no working MMS..
[Verizon Samsung Galaxy S 4] jkc120:
After you reset, make sure it's set to Verizon internet and then back out, change network mode to 3g then back to LTE, then reboot. It *should* stick and MMS should work after the reboot.
[Verizon Samsung Galaxy S 4] MustGoFast:
I'm not haveing an issue with the change sticking, I'm havgin an issue with the APN name dissapears entirely from the list after i save an edit.

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

in fact now I get an error that says "no apn specified on the device" when I try to send an MMS message.
[Verizon Samsung Galaxy S 4] shpotik:
I have a couple questions.

1.Just wondering why are there releases almost everyday?

2.do I have to flash clean or is a dirty flash good enough over a previous release?

3. Is there a way to see the change logs for the fresh releases.

Thanks
[Verizon Samsung Galaxy S 4] jkc120:
Sorry, I wasn't clear. You should NOT be editing anything. After a flash, go into the APN settings and reset them, then back out and change the modes as described.

---------- Post added at 09:58 AM ---------- Previous post was at 09:56 AM ----------

There are NIGHTLIES every day, not stable releases. Use these at your own risk. If in doubt, flash M9.

I would recommend a clean flash unless you are already on a recent cm11.

Change logs can be seen in settings or here: http://www.cmxlog.com/11/jflte/
[Verizon Samsung Galaxy S 4] FernBch:
1) They are called nightlies. They are development builds of CM11. Everyday the developers make changes and release a new build for us to try if we wish and we report our experiences here. There is one caveat, since they are nightlies there is no "official" bug reporting. That's why we post our issues in this thread.

2) If you are coming from any ROM other than Cyanogenmod11 it is highly recommended to clean flash the first time. After that you can dirty flash each nightly. If there are major changes (especially kernel related) or you are suddenly having issues a clean flash may also be recommended. In Settings>About Phone>Cyanogenmod Updates you can see the new nightlies. Just hit the refresh. You'll need to go into settings and choose development channel and you can also choose to check manually, weekly, daily, or twice daily (they only come out once/day).

3) Go into Settings>About Phone>Cyanogenmod Updates and tap on the name of each nightly and you should see the changelog.

You must have a custom recovery such as CWM (6.0.5.0 is the latest) or TWRP. If you are on Safestrap you will not be able to run CM.

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

Also, if you are experiencing an issue, read through the last few pages of the thread. Someone else may have also reported it along with a fix or work around.
[Verizon Samsung Galaxy S 4] MustGoFast:
I was trying the guidance from post 3395 to edit the APN.

---------- Post added at 12:19 PM ---------- Previous post was at 12:18 PM ----------

I was trying the guidance from post 3395 to edit the APN.
[Verizon Samsung Galaxy S 4] jkc120:
That was a temporary workaround. They sorted things a week or so back, so all you should have to do is reset the APNs, toggle mode to 3g and back to LTE then reboot. But if you tried to edit the APN you probably have to wipe and flash again or restore your nandroid and re-dirty-flash. You can try just dirty flashing the same build on top to see ifnit helps but your APNs might be hosed until you do a wipe or flash over your restored nandroid.
[Verizon Samsung Galaxy S 4] MustGoFast:
No worries. I'll wipe reflash and try again when I get a bit of time since it didn't break anything that wasnt already broken.

I'm pretty sure I tried just doing a "reset" on the APNs with no luck at all though.
[Verizon Samsung Galaxy S 4] FernBch:
I just reset APNs to default, dialed *#*#4636#*#*, reselected LTE/CDMA(Auto PRL), and rebooted and MMS started working for me.
[Verizon Samsung Galaxy S 4] gonzlobo:
For those having MMS issues, are you using Hangouts or the default messaging app? I've been completely screwed up since I moved to hangouts. I never know if I'm texting from my vzw number or google voice. Jeez, what a mess. :)
[Verizon Samsung Galaxy S 4] jkc120:
never mind. I'll avoid *****ing but suffice to say MMS continues to break. I think the unified builds have really caused at lot of problems that weren't there before. I hope the ROI is there for the cm team, because I can't perceive any benefits to the end user, quite the contrary.
[Verizon Samsung Galaxy S 4] FernBch:
Seems I may have spoken too soon. Flashed 9/13 earlier and MMS is borked.

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

Confirmed. MMS is definitely borked. On previous builds I could only send until using one of the afore mentioned work a rounds to get it working. On 9/13 I can neither send or receive and the fixes do nothing to resolve the issue.

---------- Post added at 10:36 PM ---------- Previous post was at 10:04 PM ----------

For the sake of troubleshooting I attempted to send an MMS on both mobile data and WiFi. Attached is a logcat while making the attempt.

https://www.dropbox.com/s/fyh9tmbz3c3rtzc/Log_2014-9-13_19-34-00.txt?dl=0
[Verizon Samsung Galaxy S 4] FernBch:
I have noticed something else about the latest nightly.

When browsing the web scrolling up and down on a page becomes quite sluggish and even unresponsive (swipe up and down results in no actual scrolling). Once this happens the web browser also becomes unresponsive and will not load pages. The only way to restore proper browser behavior is with a reboot. This same behavior became very noticeable last month in the week or so before the experimental build and related kernel changes (not sure if there is a correlation to recent changes or not).

Logcat of behavior attached - related info should be somewhere near the end of the logcat.

https://www.dropbox.com/s/udbh009yaysuf9e/Log_2014-9-13_20-39-24.txt?dl=0
[Verizon Samsung Galaxy S 4] jkc120:
I think I am steering clear of any nightly with APN anywhere in the commits from now on unless it has the word fix ;)
[Verizon Samsung Galaxy S 4] FernBch:
Okay, Okay. I'll be the guinea pig......lol.
[Verizon Samsung Galaxy S 4] jkc120:
And for that, we thank you ?
[Verizon Samsung Galaxy S 4] FernBch:
Hey, the way I see it it can't get much worse. Some kind of display/scrolling issue came up (surface flinger related?), MMS completely borked again, compass orientation still not working properly, BT issues are hit and miss, and this distorted ringtone/notification tone issue. And I clean flashed 9/13, too. Did I miss anything?

I am learning something here.

1) Make nandroid before installing next nightly.

2) flash nightly. A clean flash has been required more frequently that usual. Until the unified builds I could go months dirty flashing, now if I can go a month is rare (more like weekly).

3) Clean flash if there are major or kernel changes.

4) Test the crap out of it, especially recently reported items.

5) Restore nandroid if it's unbearable.

6) Post up what I find and any workarounds, if I discover any.

Yeah, that about covers it, I think.

---------- Post added at 12:31 AM ---------- Previous post was at 12:22 AM ----------

Oh, and the issue I was having with my Jabra is back. I paired it no problem. This is how it goes.

Turn Jabra on.

Turn BT on.

Jabra connects.

Here's where it goes south. When I turn the Jabra off the BT tile says it's still connected. So I cycle BT off and back on. When I turn the Jabra back on it will not connect until I cycle BT off and back on again. The button on the earpiece no longer does as it should either. Answering/hanging up calls with it is hit or miss, too.

I'm gonna leave BT on and set the S4 down and see if the wakelock issue has returned as well.
[Verizon Samsung Galaxy S 4] jkc120:
Thank you for testing for all of us!
[Verizon Samsung Galaxy S 4] FernBch:
You're Welcome.

On a positive note the wakelock issue with msm_serial_hs_dma has not returned.
[Verizon Samsung Galaxy S 4] gonzlobo:
Contemplating what I'm going to do.

Running fitsnugly's 0912 kang, but started having the usual bt issues. I have 12 nandroids on my NAS, but unfortunately I don't know which is the latest M9 (note to self: generate a text to tell me what's in those zips). If I don't have a suitable M9 nandroid, I'll completely wipe, install M9 and never upgrade again.

Ever. :)
[Verizon Samsung Galaxy S 4] FernBch:
Or you could do like me. I use RomManager and rename my nandroids.
[Verizon Samsung Galaxy S 4] gonzlobo:
I can see it now: :)

cm11_0914_goodWifi_badGPS_badMMS

cm11_0914_badWifi_badGPS_badMMS

cm11_0914_goodWifi_goodGPS_badMMS

cm11_0914_badWifi_goodGPS_gooddMMS

Just messing around. I know s/w developing is tough, but the new kernel has growing pains.
[Verizon Samsung Galaxy S 4] FernBch:
New kernels almost always have growing pains. Those growing pains will also get resolved, they always do.
[Verizon Samsung Galaxy S 4] gonzlobo:
Good idea about renaming nandroids. With an absolutely clean install, I used TWCP to rename my backup cm11_m9_clean.zip.
[Verizon Samsung Galaxy S 4] FernBch:
There'll be no more guessing which is what. I generally keep two nandroids. I have a stock MDK and the latest CM11. I'll backup every two or three day unless I see kernel changes or a big changelog.
[Verizon Samsung Galaxy S 4] jkc120:
9/14 is out, they must have changed the schedule for when builds are initiated. I see no APN or MMS related commits, so likely MMS is still hosed.
[Verizon Samsung Galaxy S 4] FernBch:
I think the schedule just altered itself. I've been watching the buildbot the last few. There have been a couple new devices added and the schedule runs alphabetically. Things just shifted a little.

As for me, I'm a glutton for punishment. I've downloaded 9/14 and will be flashing in a few......

---------- Post added at 07:40 PM ---------- Previous post was at 07:01 PM ----------

Well, 9/14 is up and running. I see the same issues I reported earlier are still present.

The only new thing I saw was the hand-off from WiFi to mobile data doesn't succeed. I had to cycle airplane mode after turning WiFi off. After a reboot airplane also had to be toggled.

I dialed *#*#4636#*#* and reselected LTE/CDMA Auto PRL, rebooted and same issue.

I dialed *#*#4636#*#* again and was messin around in there. Didn't change anything but was looking and the items in the phone info menu (shows after tappin the upper right). I noticed the bottom menu item said enable data (thought it was already). I opened each item and used the back button to exit without making any changes. After viewing one of the sub-menus the bottom item changed to disable data (Again I changed nothing) so I backed all the way out and rebooted.

After doing this the hand-off from WiFi to LTE seems to be working.

Here's a logcat for anyone who may be interested.

https://www.dropbox.com/s/u3788h6u44ud4ct/Log_2014-9-14_16-24-22.txt?dl=0
[Verizon Samsung Galaxy S 4] rpitera:
I've been sitting at 8/20 nightly all this time thinking it was just me. Been busy with two web projects and one branding project so I never had time to hit the forums until now. So I guess it wasn't just me... So what is the last nightly that worked?
[Verizon Samsung Galaxy S 4] jkc120:
Not sure, maybe 9/10 or 9/11? I'm still on 9/5 which is working well.
[Verizon Samsung Galaxy S 4] FernBch:
The last nightly that worked best for me was 9/11.

---------- Post added at 11:28 PM ---------- Previous post was at 11:01 PM ----------

Something strange just happened. I received a MMS from one of my friends. Earlier when I tested it (tried sending a pic to myself) it failed.

Hmmm................

---------- Post added 15th September 2014 at 12:14 AM ---------- Previous post was 14th September 2014 at 11:28 PM ----------

Tested MMS again. Seems I can receive but not send. Usually it will send but not receive. Guess I'll look for a fix if one exists.
[Verizon Samsung Galaxy S 4] papstar:
Same here. Can receive but cannot send MMS.
[Verizon Samsung Galaxy S 4] FernBch:
Well did some quick searching and checking and haven't found a workaround for MMS. Receives but won't sent.

Logcat while trying to send.

https://www.dropbox.com/s/m1t3odih31zz2d8/Log_2014-9-14_21-48-42.txt?dl=0
[Verizon Samsung Galaxy S 4] Alarbus:
M9 works. And I'm staying there for a while. I really need MMS and Bluetooth to work, so I stay with M9 and check to see if it's safe by refreshing this page. :)

Also, thanks guys! I definitely appreciate the testing.
[Verizon Samsung Galaxy S 4] jkc120:
just had a SoD on 9/5 so I'm not sure that issue is 100% squashed....unless something past 9/5 eliminated it 100%
[Verizon Samsung Galaxy S 4] .Ejekt:
Back to m9 wopwopwopwop
[Verizon Samsung Galaxy S 4] wowthatisrandom:
FYI MMS will be fixed in the next nightly.

this was the fix for those who r curious - https://github.com/CyanogenMod/android_bionic/commit/8a2d041a2fce6b557cabd212af68a521a02de55a
[Verizon Samsung Galaxy S 4] FernBch:
That would be cool. It reminds me of what I saw in my logcats when MMS failed to send.

This one has the possibility of helping avoid SoD's (which I haven't seen since clean flashing 8/30)

http://review.cyanogenmod.org/#/c/73253/
[Verizon Samsung Galaxy S 4] rajones19:
Compass is still borked on M10. Back to M9!
[Verizon Samsung Galaxy S 4] jackburnt:
Is compass actually fixed on M9? I thought it was a Samsung issue, not a CM one?
[Verizon Samsung Galaxy S 4] rajones19:
It is fixed on M9 if you use Faux kernel.
[Verizon Samsung Galaxy S 4] FernBch:
Look back in the last few pages, a bug report was created for the compass in M9. The compass has not worked 100% correctly since the beginning and initial reports from around the web have labeled it as a "Sammy" issue. When the last version of Android hit the scene Samsung had not provided proper firmware for the orientation sensor, I believe. There has been some things done to use the magnetic sensor but it has not resulted in a properly working compass to date.

Not everyone uses or has success with non stock kernels. Since the release of M9, CM has made some changes and I have read that third party kernels are not working with anything after mid August nightlies release, unless they have caught up to CM. I do not know if it will work with M10 or not.
[Verizon Samsung Galaxy S 4] ahaynes42:
Wifi randomly disconnects and reconnects on m10.
[Verizon Samsung Galaxy S 4] rajones19:
I do not believe they have caught up, and I doubt any of them are working with anything past M9. It was right about that point when CM changed their kernel. I have not always been a fan of non-stock kernels, but someone had reported that the compass worked with Faux kernel, so I tried it - and viola! Working compass for the first time since what seemed like forever. I have been trying the nightlies every so often, and following your daily travails with the new releases (thanks for all your testing!). For me, for now, M9 with that kernel seems to be the magic combination.
[Verizon Samsung Galaxy S 4] lx1907:
Anyone else have a disorted notification sound on m10? Flashed on top of m9
[Verizon Samsung Galaxy S 4] FernBch:
That issue showed up about 3 weeks or so ago in the nightlies and has been mentioned here. The workaround is to drop your volume a notch or two.
[Verizon Samsung Galaxy S 4] lx1907:
Thanks.. Sorry i missed that being lazy..
[Verizon Samsung Galaxy S 4] FernBch:
Don't worry about it, you're welcome.
[Verizon Samsung Galaxy S 4] ahaynes42:
M10

This is the worst M release I've seen in a long time. Data connectivity drops out, wifi drops, bluetooth is very unstable. I can't even pair my Pebble with the phone anymore. Back to M9 it is I guess. You'd think with all the millions in funding Cyanogen Inc has received, they might be able to release a decent piece of software.
[Verizon Samsung Galaxy S 4] FernBch:
While I will agree that this M release of cm it's not the most stable , you must remember that an M build is not a release candidate it is just a milestone. Because of this there are bound to be problems cm11 is still in the development stages. The kernel was recently revamped so there are bound to be some lingering issues until they get the kinks worked out.
[Verizon Samsung Galaxy S 4] ahaynes42:
Yeah, when you put it that way, I guess I can't really be annoyed by it. It's just frustrating. Kernel issues are a pain, but I do have faith they will get worked out.
[Verizon Samsung Galaxy S 4] FernBch:
That's the spirit!

But I do feel your pain, it can be frustrating sometimes.
[Verizon Samsung Galaxy S 4] jkc120:
audio distortion bug

Has anyone filed a bug for the audio distortion now that we have a M release to file against? If not, I can do that...
[Verizon Samsung Galaxy S 4] FernBch:
I have not.
[Verizon Samsung Galaxy S 4] jkc120:
ok, I filed one. If they ask for a logcat, I'll need someone on M10 to provide one as I'm not on M10 :)
[Verizon Samsung Galaxy S 4] FernBch:
Man, I'm depressed. [emoji20]

Came in from work all excited to flash 9/16 and there isn't one. I guess the build failed for today. Oh well, there's always the next one.

[emoji3]
[Verizon Samsung Galaxy S 4] FernBch:
Noticed another item to add to the BT list today.

It already does:

If BT is on and I turn my Jabra on it will not link up until I power cycle BT.

When I turn my Jabra off my S4 does not know it. Looking at the tile says it is still connected. When I turn the Jabra back on I have to cycle BT before it connects.

The new one is:

If I have BT on, Jabra connected, and walk out of range the Jabra will disconnect from the S4. When I walk back in range the Jabra will not reconnect until BT is cycled.

It actually doesn't surprise me.