yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] FernBch:
MMS sends and receives just fine, GPS gets a lock quickly, the compass orientation changes as the S4 is rotated but still behaves weird (same issue), data handoff between different sources (WiFi to LTE to 3G and back) works fine. I just haven't tested Bluetooth to see if I still have the same issue with my Jabra.
[Verizon Samsung Galaxy S 4] whiteout7942:
Running 9/27. It still has the same issue as before. But it's not a huge deal I just have to toggle BT off and then on to get it to connect to my car system. But after I turn my car off it still thinks it's connected and continues to play my music app. I can still receive calls through BT and the end and answer buttons respond just fine to the phone from my car system. At least the core function of streaming audio and calls still work its just the auto connect and disconnect that has problems

Other then that I don't see any other problems so far. We are getting close to RC I can feel it :)
[Verizon Samsung Galaxy S 4] FernBch:
Go into Settings>Bluetooth and see if the auto connect/disconnect works as it should. My Jabra will do what it should from there but not from the home screen. Calls on it are not an issue either it's just the connect/disconnect action.
[Verizon Samsung Galaxy S 4] FernBch:
Anyone know anything about cm-11-20140928-EXPERIMENTAL-RIL-jflte.zip?

I think I'm gonna run a backup and give it a shot. [emoji41]
[Verizon Samsung Galaxy S 4] MustGoFast:
Any word on when BT might get restored? I got a moto-360 last night and the disconnect/reconnect failure plaguing BT on CM has gone from moderately annoying to OMG I WANNA KILL MY PHONE.

---------- Post added at 03:19 PM ---------- Previous post was at 02:52 PM ----------

Read in another thread this might be kernal related.. anyone having better luck with BT on a different kernal, if so which.
[Verizon Samsung Galaxy S 4] FernBch:
Last I heard the other kernels have to be updated to work with the latest CM code. That was a week or two back and may have changed.

Update:

I flashed the experimental build this morning and have played around enough that I am at 10% battery. So far I have noticed the following:

The compass appears to be working. Using GPS Status & Toolbox I was able to get a lock fairly fast. I was also able to calibrate the compass and the orientation was correct. The compass pointer in other apps was not working but it hasn't for quite some time across the nightlies and experimental builds.

Upon initial boot I did not have to take any action to get mobile data to connect after disconnecting from WiFi. I haven't tested yet but I am going to guess that data handoff will work, too.

I also had no issue turning BT on for the first time after boot. When I paired my Jabra it connected properly. When I turn it off and on my S4 recognizes it being turned off and on and connects/disconnects as it should.

So far all seems to be working properly.

In the time it took to type this message I have dropped to 4% battery. That said I am going to hit the charger and do a reboot and see how things behave afterwards.

Overall I am quite satisfied at this point. Thanks to invisiblek and the CM Team! Great Work!!!

Edit:

I almost forgot. I did see a message about an overflow error related to surface flinger in the logcat. Here is from me going through everything after first boot this morning.

https://www.dropbox.com/s/8qla0kz4pnu36hx/Log_2014-9-28_13-25-32.txt?dl=0
[Verizon Samsung Galaxy S 4] MustGoFast:
PLEASE GIVE US AN UPDATE post reboot. Also when does that code find it's way into a nightly?
[Verizon Samsung Galaxy S 4] FernBch:
The timeline of a third party kernel update is solely up to who writes the kernel. It happens every time CM makes major changes, which I think they have done 2-3 times since releasing CM11.

As for the "post reboot" BT update, it's still borked. [emoji20] It also affects WiFi.

Kinda went like this......it got really weird. Something is definitely screwy.

Everything was fine BEFORE the reboot. BT would connect/disconnect to/from my Jabra at will. WiFi, BT, and Mobile Data all played well together and did not interfere with each other.

AFTER the reboot BT would not connect/disconnect to my Jabra when it was turned off/on without cycling BT off and back on. What I saw in my logcat and what WiFi did is where it gets weird.

My BT Jabra will only auto connect/disconnect when I got into Settings>Bluetooth. When in there it works like it should. When trying from the home screen it will not automatically connect when turned on unless BT is cycled. Once connected and then turned off it will not show being disconnected (when looking at the tile) until BT is turned off.

I then went into logcat to see if there was anything noticeable and I saw a line repeatedly pop up saying that the wpa_supplicant failed to initiate an AP scan. Just kept coming up line after line after line. It stopped when I turned BT back off.

I then noticed that my WiFi had disconnected and I was back on LTE. I cycled WiFi and it would not reconnect. I then cycled airplane mode and WiFi reconnected.

I have also noticed a drop in battery life recently. I have a feeling that is due to the wpa trying to get a successful AP scan but I am not positive (just a theory).

Bluetooth is definitely still borked and interfering with WiFi as well. I am guessing that the issue with the two has been present probably as long as the BT issue has been and I just noticed it today. I also saw a line in my logcat (error message) says that a Bluetooth permission is missing.

I personally am not so sure that this issue is related to the stock CM kernel. I believe there were some kernel related changes during mid August (right around the time the 9/18 experimental came out) but BT didn't break until late August/ early September. I also saw a bug report at JIRA saying something real similar to what I saw.

Whatever the problem with BT is this one, IMHO, is a major issue. It is keeping many people away from CM right now. I have seen the activity in this thread drop sharply since this BT issue arose.

Logcat is as always attached:

https://www.dropbox.com/s/mwherhpzy2yg4dp/Log_2014-9-28_15-34-15.txt?dl=0

Hopefully they can nail this one down pretty soon.

---------- Post added at 07:45 PM ---------- Previous post was at 07:03 PM ----------

Don't know if it is useful but here is the last_kmsg after the last reboot.

https://www.dropbox.com/s/4nc7dzuhs9c6895/last_kmsg?dl=0
[Verizon Samsung Galaxy S 4] MustGoFast:
SUMMARY == DAMN!

Thanks for the update Fern... I really hope they do something.. otherwise I'm looking for a good ROM to switch to until then (any suggestions) was thinking of trying Carbon (didn't see any BT issues in their threads, as it seems to plague several right now).
[Verizon Samsung Galaxy S 4] FernBch:
YW

They'll do something just not sure how long it will take.

I'm just a die hard CM fan. It'll get better.............
[Verizon Samsung Galaxy S 4] gonzlobo:
I've been interested in switching too. If other ROMs are misbehaving, I'll stay put with M9.
[Verizon Samsung Galaxy S 4] MustGoFast:
I am too, but I've been saying that for far too long and am getting wandering eyes now, especially with the new smartwatch.. that has greatly compounded my annoyance with the BT issues. I was accepting that it worked like **** in my car, but eventually basic features not operating are going to send me away.
[Verizon Samsung Galaxy S 4] ahaynes42:
I've tried other roms in the wake of the bad kernel and BT. What I've found is that no other ROM has every feature I want . Guess I'll just stay on M9 until a new reliable kernel comes along. Thanks FernBch for keeping us updated. Here's to hoping for an RC or stable release within a month or two.
[Verizon Samsung Galaxy S 4] FernBch:
This looks interesting

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

Maybe it'll fix the BT issue........

---------- Post added at 10:39 PM ---------- Previous post was at 10:17 PM ----------

Came home from work this evening and discovered that the handoff from mobile data back to WiFi is borked. Cycling WiFi off and back on did nothing. Had to cycle airplane mode in order to get my WiFi to connect.

Logcat attached (look somewhere near the bottom):

https://www.dropbox.com/s/6jde6bt33abvzqx/Log_2014-9-29_19-35-49.txt?dl=0
[Verizon Samsung Galaxy S 4] MustGoFast:
Doesn't look like it if you look into the code...

Sadly I updated to the latest nightly and now can't even connect to my brand new smartwatch.
[Verizon Samsung Galaxy S 4] FernBch:
I'm not a developer and may not know what I am talking about, but for me personally, I am not so sure all this trouble with data handoff, WiFi, and BT is kernel related. I think the last kernel mod was around three weeks ago and everything seemed to be working for a few days afterwards. Just my humble opinion.
[Verizon Samsung Galaxy S 4] Alarbus:
Looks like Invisiblek is working on it - http://review.cyanogenmod.org/#/c/74265/
[Verizon Samsung Galaxy S 4] FernBch:
No new build again today, it failed. [emoji20]
[Verizon Samsung Galaxy S 4] stoicwood:
I can't attest to some of the issues others are having with the latest nightlies. I went back to M9 because I hadn't given it an honest try, and other than missing features that have been added since, I saw no real change. My issue with LTE / cell never working together was not fixed, so I again assume that it is something with my rebuilt device.

For WiFi to cell hand-off, I have not had any trouble. I do use Tasker to toggle data and WiFi regularly, so this may be automating the same process performed by toggling airplane mode. It is the same with BT, but I don't use it other than with an OBDII adapter in my car.

I just wanted to throw in my piece for those who have been watching from the sidelines, because for my general use, I have had no more problems with the latest nightlies than with M9 which seems to be the last good stable.
[Verizon Samsung Galaxy S 4] FernBch:
I guess maybe it is kernel related......

I need to understand code and how it goes together more.
[Verizon Samsung Galaxy S 4] whiteout7942:
It is definitely kernel related. He's basically requesting to revert a part of the kernel that is potentially causing the problem. Back in mid august there were big changes to the kernel from the GT-I9505_KK_Opensource_Update9 merge. Doesn't mean this will fix BT for sure but there is a good chance. The revert request is under review.
[Verizon Samsung Galaxy S 4] FernBch:
I remember that. I think it was about the same time the experimental came out. Maybe I'm not remembering right but I don't remember having this much trouble with BT until about Sept. 1st or so.
[Verizon Samsung Galaxy S 4] .Ejekt:
And no one has the 8/18 zip available?
[Verizon Samsung Galaxy S 4] FernBch:
I wish I kept 8/29 or 8/30. They worked well for me. This issue seems to be a hot topic. It is commented on quite a bit over at JIRA, too. I have a feeling it will be resolved soon.
[Verizon Samsung Galaxy S 4] MustGoFast:
Invisiblek - Any chance you can spare a moment to give us a more official update on what's going on with BT and what you're working on? We saw some reverts in the changelogs (above).

Is there anything I can do to help fix the problems (error logs, test builds, etc?).
[Verizon Samsung Galaxy S 4] BaronLager:
I have 8/29: http://goo.gl/dNcZh0
[Verizon Samsung Galaxy S 4] FernBch:
I have no problem testing whatever comes and providing results, logcats, last_kmsg, or whatever else is needed.

I run the stock kernel, messaging app, etc.
[Verizon Samsung Galaxy S 4] drt054:
I love CM11, but been using SlimKat for about 2 weeks now. No problems with BT, WIFI, GPS, LTE, MMS. They used a CM Kernel in their 8.0 Stable Build. Maybe something in there could help??
[Verizon Samsung Galaxy S 4] jkc120:
The SOD issue is still there for me on the 9/25 nightly. With both dalvik and ART and maybe not as often but probably once every day or two.
[Verizon Samsung Galaxy S 4] FernBch:
Flashed 10/1 this morning. At first, everything was looking good. My Jabra would properly connect and disconnect. It did not matter if I was in the settings menu, looking at the BT tile, or at the homescreen.

So, I rebooted. Everything seemed fine. For about 5 minutes. After that BT would not connect without cycling BT off and back on like before. I did notice something new today. When cycling BT off and on with the tile I could see WiFi cycling off and on, too. It seems like there is more work to do before this BT/WiFi/Data issue is fixed.

I also checked the compass/GPS. The orientation is still screwy. Location locked quickly but orientation was very slow. Once it settled on the proper direction I rotated my S4 the orientation began to move towards the correct direction but it rotated past and kept on going.

I have also noticed that speech to text is no longer properly. When you start the service and begin to talk it always missed the beginning of your statement. Even waiting a moment does not help. This started with the last build.

I'll test more today and report back any other items or workarounds I come across.

Logcat attached:

https://www.dropbox.com/s/muvh514aqfrxjb3/Log_2014-10-01_06-38-00.txt?dl=0
[Verizon Samsung Galaxy S 4] MustGoFast:
Fern -> Is anyone looking at logs from here? I haven't seen a response from a dev in quite a while on this.

PS. The Carbon Nightlies play a little bit nicer, but have the same problems.
[Verizon Samsung Galaxy S 4] FernBch:
I am not positive. I have seen invisiblek visit once in a while. I have always gone on the premise that someone is looking and word is making it back to somebody. I have also posted over at JIRA with the same info. I would be very disappointed if all these logcats I have posted are falling on deaf ears.

---------- Post added at 12:30 PM ---------- Previous post was at 12:27 PM ----------

Made my first phone call today and just as I suspected, the button on my Jabra still does not hang the current call up.
[Verizon Samsung Galaxy S 4] Alarbus:
Yeah, the Gerrit link I posted the other day is in Open, not Merged, so nothing's changed.
[Verizon Samsung Galaxy S 4] wowthatisrandom:
i built a rom with that commit, doesnt seem to have fixed it for you, pm me if you have any interest in trying it.
[Verizon Samsung Galaxy S 4] phonedawg:
What you are posting here is very helpful to the nightly users. But I don't know if these reports are given high priority by the CM devs.

The best bet is to also create bug reports for the recent milestone release - M10 had many of the issues we still have.
[Verizon Samsung Galaxy S 4] vanberge:
Fern what you do here is profoundly helpful.. Even if only for other users.

I hope invisiblek and any other devs are making use of your hard work
[Verizon Samsung Galaxy S 4] FernBch:
Me too. I honestly can't believe that it goes unnoticed. I have posted BT info and logcats over at JIRA along with a detailed description of what I did and what happens. If M11 is going to be more stable that M10 it would be helpful as we would see the commits in the nightlies first.
[Verizon Samsung Galaxy S 4] FernBch:
Well I flashed 10/2 this morning. I honestly got what I expected.

BT is still hosed. The Jabra will not auto connect/disconnect. Data handoff from WiFi to mobile data is broken. When rebooting/starting up mobile data will not auto connect. Airplane mode must be cycled. I can't turn WiFi on without a reboot. I can't turn BT on without a reboot.

There are all kinds of error messages showing up in my logcat.

Some BT related, some relating to a problem with mmc/mnc, the wpa_supplicant failing to initiate an AP scan, and on and on and on.

IMHO, 10/2 is bad enough that I will not run it. 20 min of testing and I'm going back. 10/1 is still hosed up but at least it is usable.

Logcat attached:

https://www.dropbox.com/s/92rcu2wssm2o9cs/Log_2014-10-02_09-10-51.txt?dl=0
[Verizon Samsung Galaxy S 4] gpz1100:
If one was to jump in on the CM11 bandwagon, which release is most stable at this time?
[Verizon Samsung Galaxy S 4] FernBch:
I believe M9 is what everyone is sitting on. The latest nightlies have a couple issues.

---------- Post added at 02:30 PM ---------- Previous post was at 02:06 PM ----------

Just discovered something else. I cannot read my device and transfer files to a PC when connected via USB. Don't know how many days it's been broken but it did work last week.
[Verizon Samsung Galaxy S 4] gonzlobo:
M9.
[Verizon Samsung Galaxy S 4] vanberge:
I'm running it as well. I'll live with things this way for a little longer but honestly I may have to jump ship here. I'm a very patient guy and respect everything that volunteers put out there for users in the realm of amazing open source software; but I can't help feel like this ROM on this device is sort of being abandoned.

The thread doesn't have many posters to it regularly anymore and issues have really persisted for a very long time while Fern has done an amazing job providing testing and documentation for all the stuff he has found wrong.

I'll stick it out a little longer because I have not run anything else besides CM for as long as I can remember, starting with 7.2.

Cheers everyone who's hangin in there.
[Verizon Samsung Galaxy S 4] wowthatisrandom:
so a little update, i stopped into the cm irc and spoke to invisiblek heres what he said regarding bt issues

[15:23] <invisiblek> i'll put this on priority for the weekend, been fighting this new sas card for a few days and havent done any dev
[Verizon Samsung Galaxy S 4] FernBch:
Took the words right out of my mouth.

---------- Post added at 05:16 PM ---------- Previous post was at 05:05 PM ----------

Thanks. Maybe things will move in a positive direction again.

I must admit, I have been a fan of Cyanogenmod since the days of the DroidX. It has all the features I like and anything special I want is usually easy enough to achieve.

Lately it seems like more items are getting broken and nothing is being fixed. BT is a big issue to many, but not the only one. There are issues with data connectivity, data handoff from one network type to another, and the compass has not worked right in months. To top it off I find out today that I can no longer transfer data to a PC. Something has got to give sooner or later or the rest of us will slowly move on because we do feel abandoned and left behind.

Just sayin..........
[Verizon Samsung Galaxy S 4] wowthatisrandom:
based on our conversation id say Invisiblek doesnt use a gs4 as his main device anymore so if we want things fixed we gotta tell him. I know he doesnt come around here much, but hes always in the #cyanogenmod & #cyanogenmod-dev irc channels. i think IRC is the best way to contact him and JIRA is the best way to file bug reports.
[Verizon Samsung Galaxy S 4] FernBch:
Do you have links? I know about JIRA and have posted a few times complete with logcats but I've never hit up the IRC Channel. You can PM ke if it's something that shouldn't be public. I don't wanna a PITA, either.
[Verizon Samsung Galaxy S 4] wowthatisrandom:
no problem your doing all the PITA work for us lol, im happy to help where i can. The easiest way is just use the freenode webchat.

(there are also apps you can download for your phone/comp if your prefer)

to use the webchat:

go to http://webchat.freenode.net/

make up a nickname

in channel put in #cyanogenmod

fill out captcha

click connect

if cm requires you to have a registered nickname you can do so by following this guide. its basically 1 command to register your nick

to speak "at" someone just start typing their username and hit tab it will complete their username making it look something like username: Then you just type ur message hit enter and thats it.
[Verizon Samsung Galaxy S 4] rpitera:
Try being stuck on 8/29.... I'm backing up and I'm going to try a clean install. But first I'm going to flash Slim kat and see if I have any better luck. I too have been with cm since my droid days but it seems like things stopped working since they merged the builds. I'll let you know how I make out.
[Verizon Samsung Galaxy S 4] vanberge:
Yeah i might clean flash back to m9 until this build gets straightened out or i ultimately decide on a different rom
[Verizon Samsung Galaxy S 4] FernBch:
With the 8/29 or 8/30 build I restored my stock nandroid, then clean flashed CM. It was working very well for me. There was nothing I couldn't work with that way.
[Verizon Samsung Galaxy S 4] gonzlobo:
Folks that use ROMs like CM are those that like being on the leading edge. Part of being on the leading edge is buying the latest and greatest phones. Sadly, those leading edgers have moved on from the S4 (especially the vzw version), partly because it's 'not cool' anymore, plus the asshats at vzw make the s4 a painful platform on which to develop.

Frankly I like being on the leading edge, but BT absolutely has to work. It hasn't worked consistently since M9, so I don't flash. I don't even have the urge to crackflash anymore because I know the new kernel broke lots of stuff and it's not getting fixed. I'll stay on the S4 because I get great battery life and it's still a good phone. Frankly I'd drop vzw in a hearbeat, but tmobile gets 0 reception in my hangar, so I can't move to them.

All that said, it's free software, so I appreciate those that contribute.
[Verizon Samsung Galaxy S 4] .Ejekt:
8/29 > 8/18??
[Verizon Samsung Galaxy S 4] FernBch:
Anyone know anything about this?

cm-11-20141003-EXPERIMENTAL-SPRINTMMSTEST-jflte.zip

I see it has a Sprint label, but...............
[Verizon Samsung Galaxy S 4] wowthatisrandom:
i dont know but maybe related to this commit
[Verizon Samsung Galaxy S 4] FernBch:
Makes sense

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

Flashed 10/3 this morning.

I can transfer files to the PC again so that is working.

Upon initial boot I had no mobile data connection, WiFi was on, and BT was off. I cycled airplane mode and when I cycled it back on WiFi turned back on, mobile data connected, but BT also turned on. My Jabra was already on so it connected. Looks like nothing has changed much.

I'll run few a few things later on and post up a logcat at that time.
[Verizon Samsung Galaxy S 4] HowardZ:
I encrypted my S4 last night, and when booting TWRP it does not prompt for the encryption password, and thus will not work.

This is strange because TWRP prompts for the encryption password on my Nexus 7 LTE.

Is there some other custom recovery for the S4 which works with Cyanogenmod on an encrypted phone?
[Verizon Samsung Galaxy S 4] FernBch:
You could try CWM, 6.0.5.0 is a touch recovery, and is officially supported by CM.
[Verizon Samsung Galaxy S 4] HowardZ:
I just tried installing v6.0.5.0

Same problem - it will not prompt for encryption password and then does not mount some partitions
[Verizon Samsung Galaxy S 4] FernBch:
Are you on a nightly or an "M" release? If it's an "M" build you can go to JIRA and submit a bug report. Include a logcat if you can, you can also include a log from CWM.
[Verizon Samsung Galaxy S 4] djhotpocket:
I've been running omnirom for the past month due to issues with CM not working with my LG G Watch (BT related)and its mostly stable(except for random BT disconnect/reconnect issues in my car). I flashed euroskank's latest cm 11 build last night which had the kernel revert cherry picked. My BT is absolutely flawless now for in car and android wear usage. However using Google maps and anything GPS related is totally screwed. Kinda robbing Peter to pay Paul since GPS is borked but I did miss CM. Anyone have any experience with euroskank's cherry pick builds and the GPS issues?
[Verizon Samsung Galaxy S 4] wowthatisrandom:
so your watch now shows "connected" not "connected, running sync loop" ?
[Verizon Samsung Galaxy S 4] djhotpocket:
No, it always did and still does say connected running sync loop. My issue was the watch would disconnect and reconnect every 45 seconds or so, showing the little cloud with a line through it icon in the watch face. It happened ever since the kernel changes in cm 11 for the galaxy s 4.
[Verizon Samsung Galaxy S 4] .Ejekt:
I've been flashing updates through CyanDelta and I'm really not running into any problems. Proximity sensors work most of the time (not always) and rotation is fine.