yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] kyuubi08:
I noticed on my phone that the light sensor is acting up. If I go to swipe down, and accidently cover the light sensor, screen more or less turns off until its uncovered
[Verizon Samsung Galaxy S 4] darek65:
That's why I'm not going to upgrade to M10. BT is broken and I need BT to work well. I'm surprised that they released M10 knowing that BT is not working and has not been for a while.
[Verizon Samsung Galaxy S 4] FernBch:
I am not. You have to remember what the builds mean.

Nightly - Development stage. May be unstable and contain bugs. No guarantee that everything will work. Bugs not accepted. Report issues in this thread ONLY. If you find a fix, workaround, etc post that here as well. You are helping your fellow users here.

Milestone or "M" - This is a "Snapshot" of the current status of the development process. If one is published BEFORE a RC it may not be stable or have bugs present. Bugs CAN be submitted to the Bug Tracker. If you do submit bugs be sure to include a good clear description, can it be readily repeated, and always include a Logcat. Screenshots can also be included. Just saying it doesn't work right or my phone does/doesn't do "this" is only half of it. A Logcat has details about what is going on.

RC build - This is a Release Candidate. Most, if not all major items should be working properly. Some minor things may not be 100% correct. At this point new features and customizations might get introduced. Bugs should be reported through the JIRA bug tracker, be sure to include a Logcat.

Stable Release - No explanation needed. Bugs (if any) should be reported in the same manner as above.

---------- Post added at 09:44 AM ---------- Previous post was at 09:40 AM ----------

On a side note:

Drats! No new build again today. :( It failed in the buildbot......
[Verizon Samsung Galaxy S 4] darek65:
In the past, Milestone releases were free of major bugs. BT bug is as bad as it can be - at least to me.
[Verizon Samsung Galaxy S 4] FernBch:
True, usually they are fairly bug free. M releases use to come out before an RC, or less often anyway, but a few months back that changed. Now they are shooting for about once a month or so. The other difference is last month there was a major kernel revamp and the kinks are being worked out of it. The same thing happened with the first M build after unifying the builds.

The best thing everyone can do is to bear with it. When the new M, nightly, or whatever your preferred flavor is comes out, make a nandroid and try it. As said previously, the M builds have the bonus of official bug reporting. Use it and provide as much info as possible. THAT is what we as users and testers can do to help the developers make it better.
[Verizon Samsung Galaxy S 4] NickSaul:
Does anyone remember which nightly was the last one to have bluetooth, LTE, and GPS working flawlessly?

I remember having them not working, then working for like 2 builds not too long ago.
[Verizon Samsung Galaxy S 4] FernBch:
For me it was 9/12. The orientation sensor wasn't right but GPS and all worked.
[Verizon Samsung Galaxy S 4] rpitera:
What radio were you using with that Fern? Because at some point I flashed I545VRUFNC5 and I'm wondering if that's where my problems started. It's why I've been stuck on 8/20.
[Verizon Samsung Galaxy S 4] wowthatisrandom:
I personally have the best luck w MK2, NC5 was not a good radio for me.
[Verizon Samsung Galaxy S 4] drt054:
M9 and finally 9/11 for me but my GPS (NC5) was fubared after that along with some other issues. I am on Liquid Smooth right now, everything working great. Got a GPS lock in about 20 seconds without using GPS toolkit. But I will go back to CM once everything back to normal
[Verizon Samsung Galaxy S 4] FernBch:
I tried a couple radios but I always went back to MK2. After trying one or two others I decided MK2 is where I'm stayin.

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

I was just browsing the commits for the next nightly and I think I'll clean flash this one (if the build succeeds that is).
[Verizon Samsung Galaxy S 4] NickSaul:
Alright. Thanks. I just flashed back to the 9/11 nightly. We'll see how it goes.
[Verizon Samsung Galaxy S 4] ctoph0:
I'm on 9/11 and can't get MMS working no matter what I do. And with the new hangouts manually entering any setting and saving automatically disappears, so frustrating.

Sent from a toaster in space
[Verizon Samsung Galaxy S 4] FernBch:
Go to the APN menu, reset to default, exit the menu, go to the network mode an reselect LTE, exit the menu all the way out to the homescreen, then reboot. That has worked for most.
[Verizon Samsung Galaxy S 4] ctoph0:
I've done that numerous times without the success of downloading a single MMS message. Also I noticed in hangouts the MMS setting itself defaults to metroPCS settings while I am on Verizon.

Sent from a toaster in space
[Verizon Samsung Galaxy S 4] .Ejekt:
Was there ever an option to enable landscape orientation in the dialer or am I imagining things?
[Verizon Samsung Galaxy S 4] FernBch:
I don't use Hangouts so not sure what can help.

On another note, I flashed the latest build this morning and noticed a few things right off.

MMS seems to be fixed. I was able to send and receive (using the stock messaging app).

BT would not turn on. I went into Manage apps and cleared data for Bluetooth Share and NFC services, restarted, and BT turned on. I was then able to connect my Jabra. When I turn the Jabra off my S4 doesn't know it's turned off and won't connect to it when I turn it back on. So, as before, I go to turn BT off and back on to get it to connect. Now BT is stuck on turning off. Sounds like BT is a little hosed again and it is something I use everyday.

I also looking in Logcat during this and see entries popping up saying the wifi supplicant failed to initiate AP scan. Logcat attached.

https://www.dropbox.com/s/34vkbakokzdl0xo/Log_2014-9-18_07-07-50.txt?dl=0

Guess I'll try a clean flash and see if things are better.

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

After a reboot BT is now on and my Jabra is connected. I think I'll not mess with it as it seems to be working.

Also, after a reboot I have to toggle airplane mode to get a mobile data connection.
[Verizon Samsung Galaxy S 4] Slim1023:
This happened to me after dirty flashing from M9 to M10. Restored my M9 until I hear of a fix, which I'm guessing won't be until M11.
[Verizon Samsung Galaxy S 4] ctoph0:
9/18- photos sent and received via MMS on default settings. Hangouts does not correctly manage group messaging so I switched to stock messenger. I'm good for now

Sent from a toaster in space
[Verizon Samsung Galaxy S 4] jkc120:
speaker volume fix

Regarding the distorted max volume, Invisiblek's on it. He gave me a file to try, and it works though it reverted the entire commit which means in-call headset volume may go back down to levels prior to the commit. Not sure if he'll merge the entire commit or just tweak the % numbers for the speakers. But if you want to do it manually in the meantime, you can grab this:

https://raw.githubusercontent.com/C...cf131adb8f2c0b06/audio/snd_soc_msm_2x_Fusion3

And push it to:

/system/etc/snd_soc_msm/

I manually did it myself as I didn't have a USB cable. So from a terminal app you could:

su

mount -o rw,remount /system

cd /system/etc/snd_soc_msm/

cp snd_soc_msm_2x_Fusion3 snd_soc_msm_2x_Fusion3.bak

chmod 644 snd_soc_msm_2x_Fusion3.bak

cp /sdcard/snd_soc_msm_2x_Fusion3 .

mount -o ro,remount /system

reboot

I backed mine up just in case with the cp and chmod (to make the permissions match that of the original file in case I forgot later and restore it).

Works great here, sound can be at max volume now again without distortion.

Thanks Dan!
[Verizon Samsung Galaxy S 4] FernBch:
Flashed 9/19 this morning and have the following issues.

Bluetooth is still wonky. After the initial boot I could not turn BT on until after a reboot. My Jabra also has the same issues that have been there for the last 10 days.

WiFi supplicant is failing to initiate an AP scan (logcat below).

The handoff from WiFi to mobile data is not working. Mobile Data also does not automatically connect after a reboot.

MMS is working (stock app).

https://www.dropbox.com/s/50xeectmnxjuehf/Log_2014-9-19_09-53-59.txt?dl=0
[Verizon Samsung Galaxy S 4] ctoph0:
I noticed BT on 9/18 to be broken as well

Sent from a toaster in space
[Verizon Samsung Galaxy S 4] space_pimp:
Damn, FernBch is the real hero here. Flashing these wonky nightlies and reporting it so we don't have to!

Why is this WiFi to Mobile Data connect drop still an issue?? Seems like M9 is the best thing we have right now...
[Verizon Samsung Galaxy S 4] FernBch:
Flashed 9/20,this morning (clean this time). The only data I re stored was messages, everything else was set up fresh.

MMS is working (stock app).

GPS gets a lock quickly but the compass is still screwy.

The same BT issue is still there. For me the workaround is to turn BT off when my Jabra is off. When I want to use it I turn the Jabra on then BT and it will connect. I can talk and hear on it, the button answers calls but it doesn't hang them up. Kinda a PITA but hopefully this will get fixed soon. Seems lime BT issues take longer than most to fix.

Notification tones are no longer distorted.

Not sure about the data handoff from WiFi to mobile, etc yet. Will test it out and post up.

That is all I have noticed so far.
[Verizon Samsung Galaxy S 4] FernBch:
Well, so far the data handoff seems to be fine. Went out of WiFi and I think i to at least a no LTE area (maybe even no service) and everything seems good.

Now if BT would get straightened out almost everything would be golden........
[Verizon Samsung Galaxy S 4] gonzlobo:
Been on CM since 7 and I don't recall BT issues (otherwise I would've whined about them, heh). Haven't even bothered to flash for over 2 weeks. Not itching to either. Can't say I've ever said that.
[Verizon Samsung Galaxy S 4] jkc120:
Does the 9/21 download link work for anyone?
[Verizon Samsung Galaxy S 4] swordmastr54:
Yes I flashed it a few hours ago its been fine for me it had problems with data on first boot since then its been fine everything from what I can tell is working.
[Verizon Samsung Galaxy S 4] jkc120:
Yeah it finally started working for me, could be it was my local network.

---------- Post added at 10:27 AM ---------- Previous post was at 09:39 AM ----------

Dirty flashed 9/21 over top of 9/5 and so far so good. Haven't tried BT yet, but I don't use it very often. GPS and MMS both working ok. Compass I didn't try, but it's never worked.

*edit* I was on WiFi when it first booted and mobile data wasn't working. I had to reboot, airplane mode wouldn't turn things off fully so I couldn't turn airplane mode off so I tried rebooting and it hung so I had to hold the power button down to turn it off. After it booted again, mobile data is working though.
[Verizon Samsung Galaxy S 4] FernBch:
Runnin 9/21.

Compass is borked. Orientation does not move at all.

Bluetooth still does not work properly with my Jabra. I saw messages in the logcat saying a BT permission was missing and failure to connect an A2DP device.

I have also seen messages about a stack overflow error related to surface flinger and a few other items as well.

Logcat attached.

https://www.dropbox.com/s/f61bu9y7u7fddea/Log_2014-9-21_10-45-08.txt?dl=0
[Verizon Samsung Galaxy S 4] kyuubi08:
Still seeing same issues with the light sensor. If it's covered at all, screen turns off
[Verizon Samsung Galaxy S 4] FernBch:
Need a little more info, Are you on an M build or a Nightly? If it's an M build you can make an official bug report. Make sure to include a clear description and the inclusion of a logcat is preferred. This is the first time I have heard that one.

On another note I flashed 9/22 this morning.

The handoff from WiFi to mobile data seems to be working. I'll see later about LTE to 3G to no service and back.

GPS lock is good but the compass is still borked. Orientation moves today but it is off by 180 degrees.

Same issue with the Jabra and BT persists. Yesterday's logcat has the info so I won't post another for now.

That is all so far.......
[Verizon Samsung Galaxy S 4] rajones19:
FernBch, I looked up 'glutton for punishment' in the dictionary this morning, and there was a picture of you!
[Verizon Samsung Galaxy S 4] FernBch:
I contacted Webster and had them put that there.

---------- Post added at 12:35 PM ---------- Previous post was at 12:29 PM ----------

I decided to test the compass while driving today. I noticed the following:

GPS lock and orientation is correct almost instantly.

Orientation changes as my directions of travel changes. Everything seems to be good while moving. Not sure why it's funky when sitting still.
[Verizon Samsung Galaxy S 4] bsimpson1:
It's because a lot of apps will use an algorithm to detect when, and by how much your location has changed between a certain interval. If it detects a big enough change it ignores the compass and uses this to determine direction of travel. So technically it's not necessarily aware of which direction the phone is pointed. When it detects no significant change in location it relies on the compass. For me, the compass is working fine except for the fact that east and west are flipped, which is frustrating because it seems like it would be such a simple fix or the developers to implement
[Verizon Samsung Galaxy S 4] FernBch:
That makes sense. So that would mean that the compass is still borked in some way. That brings me back to the original issue with the compass and orientation sensor. In the beginning Samsung did not provide proper firmware for the compass and the orientation sensor so it really has not worked right since Android 4.4 hit the scene.

On a side note, the handoff in mobile data from LTE to 3G seems to be working well for me today. I have driven through areas that went from LTE to 3G to no service and back and I have not had to do anything to get mobile data reconnected.

---------- Post added at 01:03 PM ---------- Previous post was at 01:00 PM ----------

Just had a force close out of the blue in Google search. Logcat attached

https://www.dropbox.com/s/02s7c8ql6bjjn4o/Log_2014-9-22_10-01-39.txt?dl=0
[Verizon Samsung Galaxy S 4] phonedawg:
GPS data supercedes the compass data when you are moving. The best way to test the compass is to use a compass app on a phone that is not moving.
[Verizon Samsung Galaxy S 4] FernBch:
Like mine. My compass is also off on the orientation when not moving.
[Verizon Samsung Galaxy S 4] phonedawg:
I do not think this is an issue on the stock TW or GPE ROMs. Samsung can't afford a major bug like this when it is competing against the iphone. We will need someone using the stock TW or GPE ROMs to confirm.
[Verizon Samsung Galaxy S 4] FernBch:
I believe you are right on that point. I have heard reports from users of different roms saying that the compass works for them, as well as working on other kernels. I do know that users have commented about the poor functionality of the compass all through cm11.
[Verizon Samsung Galaxy S 4] phonedawg:
Can the compass 'drivers' (if I may say so) be pulled from the GPE ROM(which is AOSP) and made part of an upcoming CM11 nightly ROM? We can probably petition invisiblek to do this, if possible.
[Verizon Samsung Galaxy S 4] FernBch:
I could be wrong but I don't think it's that easy.
[Verizon Samsung Galaxy S 4] swordmastr54:
Has anybody tried encrypting your s4 on this ROM? What do you do and any issues?
[Verizon Samsung Galaxy S 4] Mitch8892:
Data and APN issues

I am having MMS issues still after doing all of the recommended fixes. I am on the 9/22 nightly. Upon reboot, data will not come back unless I turn 3G on, wait for it to connect, then switch to LTE. After that, MMS is a hit or miss.

If I am on WiFi and am in my normal LTE coverage area, I cannot send or receive MMS as I previously could.

I was going to go back to the 9/10 nightly where I had no issues but cannot seem to find a zip for it. Any help for these issues? Thanks
[Verizon Samsung Galaxy S 4] kyuubi08:
I'm currently on 9/18. Looks like it is an issue with the proximity sensor

https://docs.google.com/file/d/0BzHDZG3jE9RLNzN6QllXenUxa2M/edit?usp=docslist_api
[Verizon Samsung Galaxy S 4] FernBch:
Just flash 9 23, bluetooth is still borked

After the initial boot, Bluetooth would not turn on. I had to go in and clear data from NFC share and Bluetooth share then reboot the phone upon reboot bluetooth is on.

Issue I have with my Jabra not connecting when I turn it on is also still present.

After seeing the commits in today's build related to bluetooth I was hoping that it was fixed.
[Verizon Samsung Galaxy S 4] FernBch:
On a side note, the data handoff functions seems to be working properly. I have no issue automatically switching from wifi to LTE to 3G and back. I have been to various areas of service today and everything is working fine.
[Verizon Samsung Galaxy S 4] vanberge:
Did you do a clean or dirty?

I decided to try 9/23 so I clean flashed from M9 and my bluetooth was on at first bootup. I'll try connecting it to my jambox/car stereo this evening
[Verizon Samsung Galaxy S 4] FernBch:
Dirty flashed over 922. 922 was a clean flash. Had the same problem on the last 3 nightlies.
[Verizon Samsung Galaxy S 4] FernBch:
Just had SystemUI FC for an unknown reason. Logcat attached.

https://www.dropbox.com/s/n6ua9bee7esx7uk/Log_2014-9-23_15-34-10.txt?dl=0
[Verizon Samsung Galaxy S 4] phonedawg:
https://jira.cyanogenmod.org/browse/CYAN-5267 - the bug report I opened got a reply asking if the compass was still an issue in M10

I replied saying yes. Lets see if they fix this
[Verizon Samsung Galaxy S 4] wowthatisrandom:
looks like they have a bluetooth issue opened over at jira as well

https://jira.cyanogenmod.org/browse/NIGHTLIES-78

hopefully this one gets looked at soon
[Verizon Samsung Galaxy S 4] FernBch:
Saw both of those. Hopefully they will address them soon. The BT issue is the same as what I have seen.
[Verizon Samsung Galaxy S 4] FernBch:
Well Flashed 9/25 today. I have noticed the following:

After initial boot I was able to turn BT on with any hassles. BUT.

The logcat was repeatedly showing a message saying the wpa_ supplicant failed to initiate an AP scan until I turned WiFi off.

After I turned WiFi off I had to cycle airplane mode to get mobile data to connect. I guess the handoff from wifi to mobile data is flaked again :(

I turned my Jabra on and it did not connect (no surprise there). So, I unpaired and repaired it. Turning the Jabra off worked fine (S4 saw it was off and disconnected it). When I turned it on the S4 does not detect it, BT has to be cycled to get it to connect again (no surprise there either).

Logcat attached:

https://www.dropbox.com/s/3se4w7fmd04hqzi/Log_2014-9-25_06-39-25.txt?dl=0
[Verizon Samsung Galaxy S 4] stoicwood:
I just flashed 9/25. I have noticed the proximity sensor problems that others have pointed out, and it still seems to be present. Calls kill the screen, and I am unable to turn the screen back on without using the hard home button until the call ends. Which is interesting because I have the hardware buttons turned off. If I get within about 3 inches of the sensor, the screen goes out again. Gravity Screen app proximity settings don't seem to do anything at all, either.

Separately, I brought this phone back from a little over a year of being dead (broken digitizer), and have yet to be able to get simultaneous cell service and LTE out of it. I went from MDK stock-based ROM to CM11 somewhere in Sept. on a nightly. I flashed the MK2 radio at some point, and played around with settings all over the place, but I have yet to get anything but 3G or below except where I get LTE with some settings in *#*#INFO#*#* which then kill my cell service. I haven't been able to get back any LTE in the latest nightlies. I have been ignoring it since I thought it was similar to the hand-off issues people are mentioning, but it seems more like I might have missed some firmware updates while it was out of commission or something.

I doubt this is a CM issue at all, and if it isn't, feel free to ignore unless you have any tips.
[Verizon Samsung Galaxy S 4] FernBch:
You may want to read back through the last few pages. Others have had data/service issues and they seem to be related to APN handling as well as data handoff issues from one network type to another. There have been a few changes in the last 4 weeks and some of these issues seemed to start and come and go since.

On another note, the issue I had after initial boot with data handoff from WiFi to mobile data seems to have stopped after a reboot.
[Verizon Samsung Galaxy S 4] FernBch:
Well I take it all back. The issues that I have been reporting with Bluetooth and my Jabra earpiece are still present nothing has changed.

Logcat attached:

https://www.dropbox.com/s/ntlremr59t9tkum/Log_2014-9-25_10-15-49.txt?dl=0
[Verizon Samsung Galaxy S 4] stoicwood:
I have been following for a while and running nightlies on this phone while using another as my primary because of this issue. That's why I doubt it is a CM issue, but I will keep testing things to see if I can get some results. I tried M9 briefly, but probably not enough to give it an honest effort. I may give it another chance just to establish a baseline.
[Verizon Samsung Galaxy S 4] wowthatisrandom:
you should attach the logcat to that Jira post. i think we got a much better shot of it getting fixed over there.
[Verizon Samsung Galaxy S 4] FernBch:
I can't do a JIRA bug report. I'm running nightlies and bug reports are not accepted for nightlies
[Verizon Samsung Galaxy S 4] wowthatisrandom:
im pretty sure they are ok in the nightly regressions section, which the bluetooth bug is filed under, it has spots for which nightly it worked last in etc. maybe im wrong
[Verizon Samsung Galaxy S 4] FernBch:
I'll have to look into that. Thanks[emoji106]
[Verizon Samsung Galaxy S 4] .Ejekt:
Can anyone provide a link to the 8/18 build? It seems that that was the last to have the least amount of bugs. I'm still on M9 and started getting proximity sensor issues while in call and that's a deal breaker for me.
[Verizon Samsung Galaxy S 4] kyuubi08:
I agree on 9/18. Anyone have a link
[Verizon Samsung Galaxy S 4] .Ejekt:
He means 8/18 :P
[Verizon Samsung Galaxy S 4] FernBch:
Decided to clean flash 9/26 today.

I have noticed three things right away.

Once it was up and running and I had reinstalled and set up everything I toggled WiFi off to see if mobile data would connect. It did not until I toggled airplane mode off and back on. After that when WiFi is turned off mobile data picks up on it's own.

Bluetooth seems to be getting better but it still doesn't work as it should. I paired my Jabra and as long as I have the Bluetooth applet open in the settings menu it will disconnect and reconnect to my S4 correctly when I turn it off and hack on. If I exit the settings menu and turn my Jabra off the S4 does not detect it being off. It also will not automatically reconnect to it after turning it back on. At this point I have two options for connecting and disconnecting. I can only turn it off or on when the BT applet open in the settings menu or I can cycle BT off and on from the tile. I do not know how this affects the button on it as far as answering/hanging up phone calls. I will try to test during the day.

After a clean flash the compass is broken again. I get a GPS lock quickly but the orientation does not change when I rotate the phone. Calibrating the compass does nothing for this.

Logat attached. No compass info, only posted after testing data handoff from WiFi to mobile and back and testing BT functionality.

https://www.dropbox.com/s/xsnjml8jr6qyy0j/Log_2014-9-26_11-33-55.txt?dl=0
[Verizon Samsung Galaxy S 4] FernBch:
Flashed 9/27 a little while ago. All seems good so far. The only thing I haven't tested is BT to see if the issue of late has improved any.
[Verizon Samsung Galaxy S 4] .Ejekt:
MMS, GPS, it's all working?!