yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] Cilraaz:
Ensure that your root settings in CM are set properly.

If you do not have Developer Options enabled:

Go to Settings -> About Phone

Tap Build Number until it notifies you that Developer Options is enabled (7 or 8 times, I think)

Go to Settings -> Developer Options

Scroll down to Root Access

Select either Apps only or Apps and ADB

You now have root access
[Verizon Samsung Galaxy S 4] ktraub:
Bluetooth still crashing

I've tried the 6/1 build and the 6/4 build and still getting Bluetooth Sharing crashes requiring a reboot to fix.
[Verizon Samsung Galaxy S 4] jackdubl:
Thanks. So, is no native tethering a known issue?
[Verizon Samsung Galaxy S 4] Cilraaz:
I've had no issues with tethering. What problems are you seeing?
[Verizon Samsung Galaxy S 4] jackdubl:
Turning it on from the settings doesn't bring up the quick settings toggle or status bar icon, so my first thought would be that it wasn't doing anything.
[Verizon Samsung Galaxy S 4] Cilraaz:
I get no status bar icon either, but it works. I believe that's basic CM functionality.

Edit: And you can manually add a quick toggle tile from the CM Notification Drawer settings menu.
[Verizon Samsung Galaxy S 4] jackdubl:
That's a bummer. Without that extra quick settings tile the quick settings don't pull down the screen far enough to collapse the notifications from expanded to single line.
[Verizon Samsung Galaxy S 4] Cilraaz:
I am also. You could try clearing Bluetooth Share data instead of rebooting, as that usually fixes the issues.

Try the 6/5 build (when it goes up in about 2 hours). If it is still causing issues, then the 6/6 build will have the Bluetooth cherry picks removed.

Edit: 6/5 build is up.
[Verizon Samsung Galaxy S 4] CyberZion:
I'm on 6-6 build and still having BT issues.

Other than that, all is good.
[Verizon Samsung Galaxy S 4] Cilraaz:
Two of the three Bluetooth cherry picks that I had been including were merged into the CM 12.1 branch. I'm removing the third pick for the 6/7 build. If it's still not working on the 6/7 build (available in about 2 hours), then it's a regression in the code that was merged sometime between late May and now.
[Verizon Samsung Galaxy S 4] Chaos2092:
Just out of curiosity, since I haven't messed with any custom kernels in quite a while, and certainly not since any Lollipop ROMs came to the Verizon S4: is anyone using a custom kernel to any great effect? And regardless, what ones would work for this ROM and are being updated?
[Verizon Samsung Galaxy S 4] ktraub:
6/7 Bluetooth still crashing

Cilraaz, 1st, Thank you for the builds. We really appreciate you efforts!

As to the Bluetooth Sharing crashes, I installed the 6/7 build this morning and it came up fine and connected to my Moto360 just fine. I then transferred several watchfaces between my S4 and my Moto360 without issue. The crash seems to come after running for over an hour. In this case, when a notification was attempted to be sent from the S4 to the watch.

Don't know if that info helps, but If there is any other info or debugging I can assist with, I'd be glad to.

Thanks again for the builds.

I really appreciate it.

-Kev
[Verizon Samsung Galaxy S 4] Cilraaz:
I think late May was when we had the best builds. The CM team merged the initial Bluetooth buffer changes right at the end of May, which is when I'd started having issues. I'm not really sure how to handle it, since it's already merged. Hopefully a couple of new Bluetooth changes come in soon that fix the problems caused by the last "fixes".

Did the 6/7 build seem any better than the few days before? I removed one Bluetooth change and was wondering if it made any difference.

I've used Ktoonsez kernel in the past. Somewhere in that thread there's a 5.1 version hiding. I think it was technically a "test" version, so he never edited it into the OP. I don't know of any big gains that I'd seen, and shortly after I just went back to the standard CM kernel. The Ktoonsez kernel also had an issue with color grading that required you to put all colors to 50%, which essentially cut your brightness in half. The default CM kernel has pretty much all of the settings that I regularly use (noop scheduler, ondemand governor, etc), so I don't see a whole lot of gain from a custom kernel.
[Verizon Samsung Galaxy S 4] ktraub:
Bluetooth more stable the end of May

Cilrazz, I agree that the late May builds were the most stable for Bluetooth for me as well. I was running a 5/28 build that had no crashes. My Bluetooth problems started when I went to the 5/31 build, so some time between 5/28-5/31 is where the change was that introduced the problems, at least for me.

Regarding the 6/7 build, I've been running the 6/7 build for about 4 hours now and had 1 crash about an hour in, so I rebooted then. The last 3 hours have had no crashes.

-Kev
[Verizon Samsung Galaxy S 4] Cilraaz:
Here's hoping that getting rid of that extra cherry pick helped some. There were no major changes for S4 devices or Bluetooth since the last pcm.counter pick and buffer pick were merged into the main branch on 6/6 (and therefore automatically included in the 6/7 build). The only new pick I've added in today's build (out in about an hour or so) was a fix that removes creation of /storage/sdcard0, which shouldn't exist.
[Verizon Samsung Galaxy S 4] Chaos2092:
Ah, gotcha. I've used ktoonz' stuff in the past too, never quite had the luck that others did. I liked Chronic a lot but that's not been updated in like a year I think. I've heard of Alucard for Lollipop (although idk about 5.1), but don't know of any dev thread and have had no experience with it whatsoever, so I've been sticking with the stock kernel myself. I like to tweak just a little bit but if I don't see any notable results I typically return to a stock kernel anyways. Thank you!
[Verizon Samsung Galaxy S 4] ktraub:
How do you reset Bluetooth Share data?

Hi Cilraaz,

I had a Bluetooth crash just now on the 6/8 build after walking away from my phone wearing my Moto360 watch. I went out of Bluetooth range and when I came back, Bluetooth Share on the phone crashed. I rebooted the phone and had to go to a meeting and when I came back, the same thing happened.

You mentioned before there was a way to 'reset' the Bluetooth data so that I could restart Bluetooth without have to reboot the watch . I know how to reset data for apps, but can't seem to find where I would reset the data for Bluetooth.

Can you tell me where I would go to reset the Bluetooth Sharing data?

Thanks in advance.

-Kev

Edit: Never mind. I found it in the Apps 'All'
[Verizon Samsung Galaxy S 4] Cilraaz:
I've posted a bug report in the CM jira to see if anyone can figure out the regression that occurred when some of the Bluetooth buffer changes were merged in. Hopefully someone will be able to take a look at it for the S4 and see why it's a problem with this device.
[Verizon Samsung Galaxy S 4] TheRealStarkman:
Relating to BT, I have an issue where I make a BT call(I have the media option turned off in the phone) and hangup. The screen will stay on and is unresponsive. If press the home button it will react to the button press and then the screen can be touched again and will turn off after the timeout. I hangup using the car's control. Anybody else see this or is this some weird interaction with some software I have installed?

Thanks
[Verizon Samsung Galaxy S 4] kd-:
Whatever build you were talking about seemed to work better than the current one - this build I could connect to my car and it crashed after a while. With 6/8 it crashed on connect this morning, I cleared data, and it seemed to work. But it seems to have crashed again without me noticing and this happened:

Kernel wakelocks from BBS: https://i.imgur.com/IXX6Lfd.png
[Verizon Samsung Galaxy S 4] ktraub:
Bluetooth crashing on latest builds

Cilraaz, thanks for putting in the bug report. Bluetooth crashed 4 times on my 35 minute commute home yesterday with the 6/8 build. Uggh.

Guess I'm back to GPE until this is fixed.

Thanks for your efforts.
[Verizon Samsung Galaxy S 4] Cilraaz:
I'm going to put together a test build here in a few minutes. This build will have reverted code from the Bluetooth buffering changes. It will essentially be like the May 28th build, as far as Bluetooth goes. I'll post again when it's up. I'm making the changes manually rather than just doing a cherry pick, so it might be a while (especially since my shamu build is still running).

If you guys could try that test build once it's up, I'd appreciate it.

Edit: Shamu ran really long and just finished. I've reverted the three commits that seemed to have caused issues, and I'm starting the compile now. It should be ready in an hour and a half or so.
[Verizon Samsung Galaxy S 4] Cilraaz:
The test build with the reverts is now up. Feel free to give it a try and let me know how the Bluetooth works. Make sure you grab the one labeled test.
[Verizon Samsung Galaxy S 4] kd-:
The test build seems to work OK for me... still have the FC issue right when I connect to my car but clearing BT share data / turning it back on seems to allow it to work for a while.
[Verizon Samsung Galaxy S 4] Cilraaz:
Would you say it's back to the last May (28th or so) status, where it was working around 90-95%?
[Verizon Samsung Galaxy S 4] kd-:
I'd say it's close - I haven't done too much testing other than music streaming in the car using Google Music and a quick BT phone call, which both worked. The most frustrating experience I've had is where a BT call drops off without me noticing... but I haven't had a phone call long enough to see if that still happens yet.

If I decide to stop being lazy I'll test out the BT headphones and Nike+ when I get a chance :)
[Verizon Samsung Galaxy S 4] kd-:
OK so I tested it out and the same issue I had before is cropping up again - when Nike+ says something (e.x. "beginning workout") it causes Google Play to be unable to play music, and I hear no output on the BT headphones. Logcat attached, just in case someone can make any sense of it.
[Verizon Samsung Galaxy S 4] Cilraaz:
Dumb question, but you did grab the test build, right? There's a 6/10 normal version and 6/10 test version. It looks like there were only 2 downloads of the test version, so I just wanted to confirm that you'd grabbed the right one.

I'll be building updated versions today, both normal and test, but they won't be out for several hours.
[Verizon Samsung Galaxy S 4] kd-:
Yep, that was the one - I went to the separate "tab" on the download page or whatever for test builds.
[Verizon Samsung Galaxy S 4] Cilraaz:
Ok. I just wanted to double check. I noticed some WiFi connection data during the Bluetooth errors in your logcat. Some people in the CM jira (bug report facility) have complained of exaggerated Bluetooth issues when WiFi is activated (specifically on the S4). Can you try to reproduce the problem you're having without WiFi being active on the phone? That might provide extra data that I can include for the CM team.

There were a bunch of changes merged for the audio/video framework on 6/11, but nothing specific to Bluetooth has been added/changed/removed since the 6/10 build. I don't know if the A/V changes would impact the Bluetooth problems the S4 is seeing. So, I'm not sure if today's test build will operate any differently than the 6/10 test build. In any case, I'm currently building shamu, then I'll build a "normal" jfltevzw, then I'll build the "test" jfltevzw. The test build will probably be up in about 4-5 hours.

I can confirm, however, that the Bluetooth issue is an S4-specific problem with CyanogenMod (there are a couple other devices with the problem, but very few). The Nexus 6 that I have now has zero Bluetooth problems. Pandora doesn't transmit metadata, but I think that's app related since every other app transmits metadata. Otherwise, I've seen zero crashes or other issues that I had on the S4. People have stated in this thread that other ROMs also don't have the problem. I have no clue what CM managed to break that causes this issue on only a handful of devices.

I checked on the bug report that I'd posted on the CM jira. I had updated a previously "resolved" bug report. Apparently, they're refusing to re-open that bug report. So I'm going to use your logcat (since I can't generate my own) to open a new bug report.
[Verizon Samsung Galaxy S 4] Cilraaz:
A new normal build and test build have been put up. The test build is identical to the normal build, except the Bluetooth buffering changes (99518, 100055, and 100056) have been reverted. This puts Bluetooth back to the state it was for the 5/28 build, when there were far less Bluetooth Share crashes. Let me know how it goes.
[Verizon Samsung Galaxy S 4] masters:
Do you guys seem to have any problems with the camera crashing and/or being slow ?

For some reason, besides the Bluetooth share problem, my camera crashes and I also get the location light flashing/flickering in the status bar.
[Verizon Samsung Galaxy S 4] kd-:
I've had that happen before, and occasionally I'd get a camera-related wakelock that would drain the phone or a "Can't connect to camera" error. Haven't seen it in a while now though, but typically a reboot fixed it.
[Verizon Samsung Galaxy S 4] masters:
I wonder if the FNK1 modem would influence anything beyond the cell service.

I flashed the FNK1 modem only from the below source about a year ago. I did it because the original stock MDK was purported to not talk to XLTE.

http://xdaforums.com/showthread.php?t=2487298

Mine is I545VRUFNK1 and is there any benefit to change?
[Verizon Samsung Galaxy S 4] Cilraaz:
Modems should only affect cellular reception and functionality (XLTE, VoLTE, etc).

On the other issues:

Bluetooth:

There have been no further Bluetooth patches merged or proposed. I'm not sure I can get it working any better than the current test builds at the moment. I am scouring the gerrit daily looking for changes, though.

I will continue making a "normal" build and a "test" build.

The normal build will be the full cm-12.1 branch with no reverts and the cherry picks mentioned on the website.

The test build will continue to have the Bluetooth buffering changes reverted and the cherry picks used in the normal build added.

Camera:

I never had any problems with the camera. However, I used a PA Gapps, which I believe replaces the default camera app.

The only changes merged since 6/1 for the camera app are:

96221: Add Storage preference

Allows the user to change the default storage path

100114: Fix storage location NPE

Fixes a potential issue with the storage location being null

100869: Fix Undo button behavior

Fixes incorrect logic on the undo button, causing it to disappear when it shouldn't

I don't know if any of these changes will fix the issues you've been seeing with the camera.

Please continue to let me know of any new problems, positive changes to known problems, and any regressions that occur.
[Verizon Samsung Galaxy S 4] masters:
Argh, just flashed the 24th test build and get no SIM card now.. Will have to try to fix tomorrow.

Edit

Flashed back to my backup and cellular SIM works.. Might try to flash the non test one. If that doesn't work then I'll do a full wipe and flash.
[Verizon Samsung Galaxy S 4] Cilraaz:
Nothing SIM related was changed in any of my builds. I'm not sure why it would have given you any connectivity issues.
[Verizon Samsung Galaxy S 4] masters:
I was confused also, I can't think of a reason that it would knock out cellular, but after several reboots and letting it sit..

Even removed the sim and put it back in and it still had the no SIM icon and in the About Phone section there was no SIM information.

So I figured to post about it to see what responses I'd get back.. I might try again.

I have a Pebble Time watch and it works, except when I set the pebble watch to navigate I get the BT Share and the BT shuts off..

EDIT: Again.. Yep flashed the TEST 624 again and flashed the nonTest one both show ...

No SIM card - No Service

-Sigh-
[Verizon Samsung Galaxy S 4] Cilraaz:
The 6/25 normal build is up now. The test build should be up in 20-30 minutes. I haven't changed anything relating to networking, though, so I'm not sure if it'll be any better for you.
[Verizon Samsung Galaxy S 4] talz13:
My wife's phone was having battery drain and other issues on an older cm12.1 nightly, so I just flashed her phone last night. First with 6/25, and had the same problem... No SIM / Emergency Calls Only. So I flashed 7/1 over that and that appeared to have brought the SIM back online. Her phone had been having regular issues with mobile data, so I attempted to go to the APN settings and restore to default.

However, that just managed to wipe the APN settings out entirely! Now it gets no data service, and trying to manually enter an APN results in no new APNs being shown on the screen. Several reboots and a nandroid restore later (back to before I started flashing last night), and still no APNs. So right now it's sitting on the kitchen table on wifi, but can't get connected to the mobile network!

I've read around a bit, and found numerous references to the /data/data/com.android.provider.telephony/databases files being corrupt / unreadable / permissions issues. I moved this folder to a backup location and rebooted the phone. After it came back up, it had recreated that folder structure (evidenced by current timestamps), but still no mobile data / APNs.
[Verizon Samsung Galaxy S 4] masters:
What I ended up having to do was ODIN back to MDK and everything involved with that (root/recovery/etc). (Word of warning, it tried to pull the over the air update. I kept killing it until I had it rooted with recovery and froze the updater) . What was weird was that I flashed to a known good backup of mine (before I had troubles) and it went back to "No SIM", so I had to reflash Odin back to MDK and I took it to the 5.0.1 rom with OC1 modem and it works fine now. Long process though with restoring titanium backups.
[Verizon Samsung Galaxy S 4] Cilraaz:
I still have no idea about the SIM or APN issues, as I didn't pick anything relating to those parts of the code. I can only guess that CM merged something in that caused it, though it should have affected all CM-based ROMs at that point.

In any case, a new build is coming up today. Sorry for the delay, but I've been sick for the past 2 weeks and then there was the holiday. This new build will include a cherry pick that should finally fix the compass issue that has apparently been a problem for the S4 since at least CM12.1. I'll also still be making the "test" version that reverts the last 3 Bluetooth changes. I don't know if it's worth it to use the test version over the standard version, but I know before those last three Bluetooth changes, I had the best luck with my phone and car working together. Let me know if it's even worth building the test versions anymore.
[Verizon Samsung Galaxy S 4] Cilraaz:
I had an issue with the server yesterday. It compiled the normal jfltevzw and shamu builds, but never compiled the test build for jfltevzw. That was remedied today and all three builds are up.
[Verizon Samsung Galaxy S 4] Cilraaz:
Since the test build hasn't been downloaded much recently and the amount of time it takes to add another compile, I'm discontinuing the test build. I will continue building for jfltevzw and will be adding trltespr, which is the Sprint Samsung Note 4.
[Verizon Samsung Galaxy S 4] Cilraaz:
Starting with the 7/27 build, there was a new change cherry picked. Change 103111 claims to fix some disconnect issues with Bluetooth and certain car head units. Please let me know if there is any improvement.
[Verizon Samsung Galaxy S 4] magiin:
I seem to only be having MMS issues with this ROM, otherwise, completely flawless.

Internet and regular SMS work, but MMS does not. Anytime I try to alter the APN, it fails to save or breaks.

Anyone else still having this issue (currently on the 7/27 build)
[Verizon Samsung Galaxy S 4] Cilraaz:
I remember having issues on the S4 with MMS and CM 12.1. I had to change the APN information, which I don't remember ever failing to save. Unfortunately, I don't have an S4 currently to test the builds on, so I can't really be of much help in troubleshooting.

Bluetooth seems to be working for you, though?
[Verizon Samsung Galaxy S 4] Cilraaz:
I have shifted to a CM13 build for the S4. If you're interested, the download links have been updated in the original post. I don't have a phone for testing, so I can't speak to the quality of the builds. If anyone would like to test and let me know, that'd be great.
[Verizon Samsung Galaxy S 4] gpz1100:
Going to give this a try in a few days. Currently have the GPE rom on my mdk device. It works good, but 6 has some nice power saving features.
[Verizon Samsung Galaxy S 4] Jalh:
Let us know how it works.
[Verizon Samsung Galaxy S 4] faciar:
I have been on this rom for a few days, so I may as well share my experience.

I'm using the build from 1-14 with OpenGapps nano from the same day. I installed using TWRP 2.7.0.5.EXT4. I'm using the MDK non-hlos with the OF1 modem. The rom I was on previously was Pheonix.V11.

Installation and initial setup was as easy as expected. Restoring backups from tibu was painless. 4g/3g, wifi, and gps (except the compass) have been working as expected.

I use hangouts for sms and mms messages seem to work, slowly.

Some apps (root explorer and waze to name a couple) seem to crash due to permissions issues, but the apps I use on a daily basis seem to all be fine, fortunately.

The speed and battery usage of the rom has been excellent. Both seem noticeably improved from my previous rom, but I don't have any numerical data to back this up. Also, I have not had any lockups or any issues requiring a reboot.

Besides the permissions issues affecting some apps, the biggest reason to stay away from Marshmallow roms would be the known issue with SuperSU (See the CM12.1 thread in original dev). If you need SuperSU for xposed or anything else, then this rom probably won't fit the bill. The built in super user worked for me in tibu and the power menu app I use which is all I needed.

I would say, that anyone curious about Marshmallow should at least consider making a nandroid backup of their working setup and giving it a shot. I know that my requirements are extremely simple compared to most, so take this with a grain of salt, but I will be using this rom as my daily from now on. :good:
[Verizon Samsung Galaxy S 4] Cilraaz:
Today's build cherry-picked in a GPS change that may or may not fix the compass.
[Verizon Samsung Galaxy S 4] faciar:
I clean flashed the build from the 22nd. The compass does seem to work, but I haven't had a chance to really try it out as I'm snowed in.
[Verizon Samsung Galaxy S 4] Synomenon:
CM13 dead for the Verizon S4?
[Verizon Samsung Galaxy S 4] gomangoman:
I'm running the 3/9 nightly.
[Verizon Samsung Galaxy S 4] Cilraaz:
I was away for a while and then had a few days where the build refused to compile because they added a dependency without notification. There's a new build up as of today.
[Verizon Samsung Galaxy S 4] Neffy27:
I flashed the ROM with no issue, I only have one word... SMOOTH. I then went back into recovery and flashed the latest nano ARM 6.0 gapps only to be met with mass setup has stopped msges. I navigated down through the menu in between the split seconds of dismissing the popups, to factory reset. It is now stuck in TWRP Recovery Bootloop. It does not go pass the TWRP logo, goes black, then repeats. adb reboot doesn't stop it from going into recovery and taking the battery out doesn't either, any ideas?
[Verizon Samsung Galaxy S 4] Neffy27:
I pulled the battery out and held volume down + power to force it to download mode. From they, I just cancelled and let it reboot normally. Booted to lock screen, if I unlocked, I'm met with the mass pop ups of setup wizard and Google has stopped. Ended up odining the stock kernel, that allowed TWRP to boot and restored my back up. I really want to flash this again because of how smooth it ran before attempting to install gapps.

Is there a known good version of gapps to use or was I just unlucky?