yashsingh1/xdaforums huggingface dataset:
[Verizon Galaxy S 5 Android Development] jdrch:
Yes, but that's a moot point when:

1) There's no milestone build available.

2) There's nearly no way of predicting each build's bugs.

3) Each build's bugs are independent of how often you update.

4) Each nightly has its own minor bugs and quirks which are tolerable in the short term only because there's a chance they could be fixed in the next build but would be intolerable in the long term.

5) Nightlies aren't built for long term stability and can only reasonably be expected to be stable up the time of the next release. In other words updating daily prevents you from experiencing issues that occur only over continuous uptime periods longer than ~24 hours.

6) Any bugs in a particular build are only resolved by updating. It's unreasonable and disingenuous to suggest users wait longer than the next nightly to at least test whether a particular issue has been fixed.

For example, the May 25 build KOed the installation of anyone who flashed it regardless of whether they updated daily or annually.

---------- Post added at 01:09 PM ---------- Previous post was at 01:06 PM ----------

I get TW-level results from Camera MX, which is free, actively developed, and has a beta channel in the Play Store.
[Verizon Galaxy S 5 Android Development] puterdoc:
I completely forgot I purchased a cardreader+hub for my phone as more of a novelty a while back. Never even used it. Am backing up to it now. It has usb and all the memory card slots so I am set.

As mentioned above, I update every time I see an update for the purpose of progressing the testing and hoping for better each time. All while knowing it could go wrong. Rarely does it go as bad as this week but obviously it can. I was at my daughters house when it did it and I didn't get mad, I just jumped online, grabbed the CM of yesterday and the GAPPS and poof working phone again in 20 mins even if not personalized. True without access to a computer I would have been phoneless. Even before that when I lost all my google account info, the phone still worked as a phone and that is to me the requirement.

Its a gamble to get the pluses of these alternative packages. My first hack was my S1 and did it for the battery extension. Kept it running for 4 years due to "testing" and the Dirty Unicorn team. That is the biggest for me on this one too, battery life. The rest is just icing even though I miss some of the tweaks from DU. I will take more precautions which we should do anyway, but I won't down any build and will continue to use and test. I admit not trying the other build you spoke of.

I don't get Bluetooth quality issues on calls. Other than dropping the connection to the Bluetooth, calls are fine. Internal voice apps, music, GPS, etc stutter. Last build did well for me though. As said before, for some reason the volume on these things seem to magically turn up on their own and deafen me. Unlinking them has helped some. But volume controls have some quirks for sure yet I do like the ability to increase when needed. Figure its a catch 22.

As far as camera, I have had mixed results. I use the check deposit and Shop Savvy app. It takes a bit to get it to focus on both check and UPC sometimes. I also have to take pick of serial numbers on things too and it performs fine for me.
[Verizon Galaxy S 5 Android Development] lowfront:
I just reverted to my backup and good to go again. CM13 is amazing as long as your Bluetooth is good. Camera is fine just explore different camera apps.
[Verizon Galaxy S 5 Android Development] rauleeros:
I currently have problems with the bluetooth too. Do you know when were these problems not present? (Which nightly)

Thanks!
[Verizon Galaxy S 5 Android Development] jdrch:
Out of curiosity, when the adopted storage failure happened which TWRP build were you using, and were you installing the update from the SD card or from internal eMMC storage?
[Verizon Galaxy S 5 Android Development] lowfront:
13.0-20160501-NIGHTLY-kltevzw
[Verizon Galaxy S 5 Android Development] rauleeros:
Awesome! I'll try it, thanks!
[Verizon Galaxy S 5 Android Development] ldeveraux:
Were you just throwing that it there, it was that a serious answer? I don't know if a build of cm that doesn't have bt issues...
[Verizon Galaxy S 5 Android Development] lowfront:
I didn't have any Bluetooth issues until I recently updated off that nightly.

I wouldn't have used CM from the start if I couldn't listen to Bluetooth in my car without a stutter.
[Verizon Galaxy S 5 Android Development] damagi123:
ive never found one that didnt have BT issues. Something about this phone
[Verizon Galaxy S 5 Android Development] ldeveraux:
Someone a while back said that even the LL kernels have bt stutter. It's the only reason I stayed with cm13. Maybe that was just him?
[Verizon Galaxy S 5 Android Development] jdrch:
I think I solved the adoptable storage corruption on update issue.

TL;DR: even though [MENTION=5672995]jcadduono[/MENTION]'s TWRP build mentioned in [MENTION=2693412]haggertk[/MENTION]'s OP can read adopted storage, Do NOT reboot into System from TWRP with any external storage inserted or attached. You run the risk of the storage being corrupted at the data level.

Longer story: I did a nandroid backup to USB OTG in TWRP and then rebooted into system with the USB storage still selected. Upon reboot, I discovered that the USB drive was corrupted. It seems the test build corrupts ANY currently selected non-eMMC storage during reboot. The way to avoid this is to:

1) Disconnect/remove any external storage (USB, microSD, etc.) before rebooting into System.

2) Always ensure internal storage is selected before rebooting to system from TWRP.

So far I've installed the May 31 and June 1 builds using 1 & 2 above and had no corruption issues, so I think I fixed that problem. I've PMed jcadduono about the issue.

Does anyone know the official thread for [MENTION=5672995]jcadduono[/MENTION]'s TWRP build? I think this is a bug that needs to be fixed.
[Verizon Galaxy S 5 Android Development] twolostminds:
I would like to use my VZW S5 running CM 13 on The Peoples Operator, runs on the Sprint network. Do I need to follow this guide, "[GUIDE] Add all GSM and LTE bands to your phone" to add the TPO/Sprint bands to my modem or will just inserting the TPO SIM automatically do it. If I have to do it I can follow the instructions in the guide but I can't seem to find a way to change USB from AP to CP. Could someone please give me a nudge in the right direction?
[Verizon Galaxy S 5 Android Development] akinsella85:
Has anyone found a solution for the accelerometer problem? I can not get mine to work for more than a couple of minutes after a clean install no matter which build I use. Even flashing back to older versions does not fix the problem. This is starting to drive me crazy not being able to rotate the screen or use the accelerometer for any games. Thanks
[Verizon Galaxy S 5 Android Development] sdsubball23:
I'm on an old nightly from 5/12.

Does anyone know if any of the updates added a number pad to the top of the stock keyboard? It only shows up for me when I'm typing in a password box. In other places when I'm typing, it doesn't show it.

Also, I've had some bugs with my typing where I can't accept a word without it autocorrecting. To get around it I have to type a period or type something and erase that part of it or maybe something else to keep the word from being autocorrect.

Another bug I've noticed is when I'm typing and if I sometimes go back to something I previously typed to edit it, it erases part of my writing in that area where I tried to edit.
[Verizon Galaxy S 5 Android Development] purplepenguin:
I believe those are all things I experienced before even touching this ROM. I think unrelated, but not sure.
[Verizon Galaxy S 5 Android Development] jdrch:
Get a 3rd party keyboard like Swiftkey for that.

---------- Post added at 05:18 AM ---------- Previous post was at 05:16 AM ----------

PSA: jcadduono's TWRP build page now advises users to install the latest mainline klte build from twrp.me, and test builds are no longer available.
[Verizon Galaxy S 5 Android Development] puterdoc:
twrp-3.0.2-2-test1-klte.zip

I changed to -3 when I last posted. No issues since. I did make backups to a thumb drive and a TF card but I never tried them out to see if they were good beyond them verifying.

Am now using twrp-3.0.2-3-shim-klte.zip. I went to twrp.me and don't see this. Should I not be using it, and if not what to replace it with? The ones before -2 didn't support adoptive at all I thought.
[Verizon Galaxy S 5 Android Development] jdrch:
That's interesting, because twrp-3.0.2-3-shim-klte.zip is the build I had problems with. Switched to twrp-3.0.2-2-klte.img as currently advised at the testing builds page though.
[Verizon Galaxy S 5 Android Development] perfectswanson:
I've heard the same, but I found that marshmallow in general has Bluetooth issues. That's why a lot of Bluetooth apps haven't been updated. Everyone is still learning the BT stuff in marshmallow. I just wish I could port cm12 to vzw S5, but I'm still learning and am not confident. So my BT stuff like sixaxis will work. Marshmallow is just not ready. I still have the cm11 rom for the dev edition, but I got an error after I had tried installing it again: the rom is for vzwklte, but this is a "vzwklte"... Must be the unlocked bootloader or something else I had changed.
[Verizon Galaxy S 5 Android Development] haggertk:
Ok, so who wants to test out a build using the MM kernel (and MM camera libs) merge? In particular, I'd like people who can do a good A/B comparison mainly to see if something that works with the current official kernel also work with the new kernel and that there aren't any regressions (stuff broken with new kernel actually works with old kernel).

Without further ado:

kltevzw: https://www.androidfilehost.com/?fid=24562946973631507

It is equivalent to the 20160603 official nightly with the addition of MM kernel and camera blob merge.
[Verizon Galaxy S 5 Android Development] talktosamson:
I'm currently on the modified PD1, rooted/unlocked. Do I just flash this through twrp? Will I be able to restore my backup and still be unlocked? I'm willing to test as I really want the TW camera, but to run CM13.
[Verizon Galaxy S 5 Android Development] haggertk:
Unfortunately, this won't get you the TW camera, it just updates the proprietary libraries that interface with the camera hardware... Same old Snap camera. Others have reported that Open Camera has about the same image quality as TW.

If you still want to test, it gets flashed in TWRP just like a normal CM install.
[Verizon Galaxy S 5 Android Development] tydiamond11:
Delete
[Verizon Galaxy S 5 Android Development] purplepenguin:
proprietary libs to CM? or to some other organization??
[Verizon Galaxy S 5 Android Development] haggertk:
All CM builds include a number of proprietary files copied from the Samsung official releases. These files are the secret sauce that allows for actual direct access to specifics parts of the hardware. They are also the most stupidly painful things to figure out because they are documented and figuring out the interface can sometimes be like stumbling around in a littered pitch black room to find a light switch that can be located anywhere.

For example, these two files are the lists of files that go into our builds.

Copies of these are not stored in official CM repositories, but you can be certain that CM isn't doing the extract_files thing that is officially documented in the build wiki with every device known to man USB connected to the build servers...
[Verizon Galaxy S 5 Android Development] perfectswanson:
Samsung released some libs, though for developing right? That's how we have beaming service, and fingerprint scanner, but not heart rate?

---------- Post added at 11:14 PM ---------- Previous post was at 11:10 PM ----------

Also been on this build all day, and it works great. I think BT improved. Less hiccups.
[Verizon Galaxy S 5 Android Development] purplepenguin:
Thanks for explanation! I would love to mess around but too cautious since daily driver. I need to be reachable/available for work. (Prob shouldn't even be flashing nightlies every few days for the risk ;) )
[Verizon Galaxy S 5 Android Development] TRONA2000:
Tried it but I kept getting a "Bluetooth share has stopped working" message every few minutes so I went back to the latest nightly. Do you think wifi calling will get incorporated into your CM nightlies now that it's supported on MM? Apologies if it's not appropriate to request features. Thanks again for your work.
[Verizon Galaxy S 5 Android Development] TioCareca:
Does anyone uses the MM bootloader with this rom?
[Verizon Galaxy S 5 Android Development] TioCareca:
Proximity sensor not working 07/06 build, anybody got the same problem?

Edit: Never mind, its just my custom kernel that have a problem...
[Verizon Galaxy S 5 Android Development] Excelsior88:
Has anyone lost their 5g wifi with the latest nightlies?
[Verizon Galaxy S 5 Android Development] CZGunslinger:
I'm getting the Bluetooth share has stopped working also.
[Verizon Galaxy S 5 Android Development] DarkenedMatter:
Curious why on Global it doesn't say that I am on the Verizon Wireless service? Trying to find out if I did something wrong along the way. LTE generally works. I was still getting texts though and can make calls but didn't know if there was a specific reason for that to happen.
[Verizon Galaxy S 5 Android Development] ldeveraux:
Yes, on 6/7 nightly I can connect to my 2.4, not my 5.
[Verizon Galaxy S 5 Android Development] paradox923:
Same here.

Also getting this since 6/7 build.
[Verizon Galaxy S 5 Android Development] ferg40:
Same...
[Verizon Galaxy S 5 Android Development] obsidian1918:
Flashed this ROM after unlocking my bootloader, but the dialer doesn't work

Hey, don't know if anybody will see this, but I flashed the CM13 ROM on my kltevzw after unlocking my bootloader and installing twrp, and everything runs flawlessly except that my phone reboots anytime I try to call someone or whenever I get a call. Has anybody else had this problem and/or knows how to fix it?
[Verizon Galaxy S 5 Android Development] Dullawolf:
Crap, me too. I was just jumping on here to say the exact same thing. I'm updating to the latest nightly to see if it fixes it.

*UPDATE* latest nightly didn't fix it. Phone still reboots when trying to call out
[Verizon Galaxy S 5 Android Development] obsidian1918:
Hey so I actually just found the solution elsewhere in the thread. All you have to do is set the phone as the default app in your application settings. For some reason, there is no default app previously listed, but manually doing it solved the problem for me. Best of luck!
[Verizon Galaxy S 5 Android Development] Dullawolf:
Dude, you're a lifesaver. Thanks!

[MENTION=2693412]haggertk[/MENTION] wanna put this in the first post? so people don't freak out too much
[Verizon Galaxy S 5 Android Development] tydiamond11:
If only we could figure out that Bluetooth share crash thing that would be great!
[Verizon Galaxy S 5 Android Development] orangesrhyme:
I was looking for a solution earlier today, and apparently some people found success with an LG (either the G2 or the G3*) by copying the /bluetooth folder from the stock ROM and overwriting CM's.

Here's the link to the thread if somebody wants to look into it. I'm not at my PC right now, otherwise I'd be down to give it a shot... Even though it's CM12.1 and not 13. And it's a diffferent phone. Still, the concept might carry over.

*Edit: Neither. Still an LG phone so *shrugs*
[Verizon Galaxy S 5 Android Development] yfz350:
I installed June 8 nightly this morning, have used bluetooth a few times today and haven't experienced any bluetooth crashes. It does still have a few seconds of bad quality bluetooth audio on the lock screen issue.
[Verizon Galaxy S 5 Android Development] haggertk:
Done
[Verizon Galaxy S 5 Android Development] haggertk:
I've don't have this problem, but my BT use right now is fairly limited to Fitbit and my Bluebuds X headphones. I'm on the other side of the world from home and don't have access to too much a variety of BT devices.

I'm in the process of merging blobs and this will include the latest BT firmware. In about 24-48 hours I should have some test builds ready to go. There may be some compatibility issues with the new BT stack in the kernel, LP blobs, and some pairings.

Kind of a "is it plugged in" troubleshooting step -- please don't be offended... Have you tried going into Settings->Apps (show system apps), force stopping Bluetooth Share, and then clearing data? Back in the old days (CM11/12*) there were periods of time where I had these issues and I could fix/mask it by clearing BT Share data.
[Verizon Galaxy S 5 Android Development] tydiamond11:
I tried that but nothing worked it will not let me clear data or stop it.
[Verizon Galaxy S 5 Android Development] Outbreak444:
I've been wanting to update to CM13 from stock lollipop since I found out about the ability to unlock our bootloaders. The only thing holding me back is if VoLTE and the mobile hotspot mod isn't available yet. I tether my phone every day and I also video chat with the girlfriend when I am on travel. I have searched in the CM changelog's, this thread, along with the other thread that they direct you to for questions on what features there are. I have read some posts saying that VoLTE is working, and others saying that it is not available which doesn't make sense really. So before I make the next step I would really like to know if these two are available in CM 13.
[Verizon Galaxy S 5 Android Development] paradox923:
I unpaired everything then cleared data then rebooted, issue stoppes for me and BT is back to normal on last night's 6/9 build. On the BT stutter issue I used to have that going back to stock lollipop. In my tasker I added a line that sets cpu to performance when i am connected. Haven't had any stutter since.

Edit: meant 6/8 build, apparently i was still asleep went i typed the above.
[Verizon Galaxy S 5 Android Development] Excelsior88:
I have to go back to the 6/2 build to get the 5g wifi to work again but no longer have the build on my phone so no more 5g for me until it's fixed.
[Verizon Galaxy S 5 Android Development] orangesrhyme:
Haha, no offense taken! I actually hadn't seen that particular remedy. That said, I gave it a shot and Bluetooth share still wigs out a little bit. That said, it has yet to completely shut down BT and force a reboot*, so that's good :) looking forward to the new builds!

Side note for everybody else, has anybody used Google Play Music regularly with this ROM? With data and wifi off, and listening on my BT earbuds, it noms up a good bit of battery. Not to the point of unusability, but I unplugged about 2 hours ago and I'm already down to 76%! But yeah, any reports from other peeps on here about their experience with GPM+CM13 for kltevzw would at least help to soothe my conscience, haha.

*UPDATE: Bah, spoke too soon... BT shut off and won't turn back on without a reboot. If anybody can suggest some Shell commands I can have Tasker push that'll help streamline that process, it'd be much appreciated.
[Verizon Galaxy S 5 Android Development] puterdoc:
(me too) The Bluetooth issue has been constant on anything past 6/2 for me. I have rolled back the last few days each after running them for a few minutes and losing Bluetooth all together. It wasn't intermittent for me, gone stayed gone. I tried to shut it down and it wouldn't even let me force a close and restart. I have also had reboots on the newer builds. Did not continue to use todays as soon as it lost BT I changed back as

its a must for me on calls. Choppy music or even GPS I can handle, no headset not so much.
[Verizon Galaxy S 5 Android Development] ldeveraux:
I love the idea of cm13, but for me, the negatives outweigh the positives here. I really hate to say it, since I REALLY appreciate op's work on it. But the Bluetooth, kernel, memory issues, battery life, crash on reboot, it's just too much. Maybe it's the kernel, or cm in general, but whenever the deodexed, rooted 6.0.1 rom is released, I'm going to try it for a while.
[Verizon Galaxy S 5 Android Development] softwarestealer0:
Even tho it's old, I've been running 5/10 since it came out and I have none of these issues experienced in the thread
[Verizon Galaxy S 5 Android Development] Aceshootn:
I too have been frustrated about CM13. I gave it one last time and here is what I found. I'm on 2016-06-05nightly. Using GAPPS from the same time frame. I put both on the microSD card. I removed card and wiped

everything

from the phone. Inserted the card and installed rom and gapps using TWRP. Using stock kernel, I adjusted "swappiness" from 100 to 30. So far no random reboots. The bluetooth is not perfect. I'ts tolerable. I've found if the phone just sits and is not used while streaming pod casts from wifi (company hot spot) to the car bluetooth there is very minimal skipping. However, If i activate the phone, it goes skip happy. If all stays this good, I'll keep this version until a major change, or a stable is released.
[Verizon Galaxy S 5 Android Development] paradox923:
6/11 build is causing me bootloops. Installs from twrp, reboots, optimizes apps, gets to finishing and reboots then hangs on blue cm boot animation. Wiped and restored to 6/10 build.
[Verizon Galaxy S 5 Android Development] Bass Clef Builder:
Same problem for me.
[Verizon Galaxy S 5 Android Development] puterdoc:
Ditto

I jumped back to 6/2 as that's whats been working for me 98% solid. Is 6/10 doing better with the Bluetooth share close?
[Verizon Galaxy S 5 Android Development] y2kbaby2:
Where did you get the 6/2 build from? As for 6/10, It hasn't crashed for me yet and I've had it for 24 hours.
[Verizon Galaxy S 5 Android Development] paradox923:
So far so good, no BT issues atm.
[Verizon Galaxy S 5 Android Development] jmetcalfe84:
I had about 6 bluetooth crashes yesterday on it. Its weird though if I reboot then its fine on the first connect but if you loose it or turn it off then on then it crashes. 6/11 build isn't working for me either just bootloops.
[Verizon Galaxy S 5 Android Development] paradox923:
I haven't replicated it yet, but my last BT crash occured after i was talking and the call ended. My music resumed playing but when i stopped driving and shut Jeep off, BT wouldn't disconnect automatically or manually, then crash. Today things seem to be running well tho.
[Verizon Galaxy S 5 Android Development] CZGunslinger:
6/11 build bootloops for me also. Had to roll back to an older version I just happened to have on an sdcard.
[Verizon Galaxy S 5 Android Development] haggertk:
My fault on the bootloop guys... no excuses, I got sloppy and didn't include one file in the vibrator fix commit. At least it will be fixed tomorrow. :(

http://review.cyanogenmod.org/#/c/149043/
[Verizon Galaxy S 5 Android Development] paradox923:
Hey no worries, and great work on all you've done thus far many, many thanks! Twrp bkp saves the day.
[Verizon Galaxy S 5 Android Development] johnnyrichter:
Don't sweat it bro. We all make mistakes. Keep up the awesome work!
[Verizon Galaxy S 5 Android Development] CZGunslinger:
Yeah no biggie. To echo the above posters, thanks for all the hard work! A hiccup here and there is expected.

BTW I rolled back to the 5/30 build and it is really stable.
[Verizon Galaxy S 5 Android Development] luis4995:
deleted
[Verizon Galaxy S 5 Android Development] purplepenguin:
praise jesus I checked the forum first and got the 12th build instead of flashing 11th blindly lol
[Verizon Galaxy S 5 Android Development] paradox923:
6/12 working well, no BT issues so far, everything else running smooth.
[Verizon Galaxy S 5 Android Development] johnnyrichter:
Ever since fully rooting/boot unlocking and getting on this ROM I've had some weird boot/reboot issues that happen occasionally.

Sometimes my phone will lock up and reboot itself. Sometimes if I turn the phone on, or reboot it, it gets stuck at the CM animation and I have to perform a battery pull. I don't know why, and updating nightlies hasn't resolved it yet.