yashsingh1/xdaforums huggingface dataset:
[Verizon Galaxy S 5 Android Development] haggertk:
Absolutely, there is no need to do a clean installation between different builds/nightlies of the same CM version (e.g., CM13.0). The normal way to dirty flash is to flash the new version and then wipe cache and dalvik.

That said, sometimes something just isn't working right and good clean flash is beneficial. As an example, I had a problem when klte-common changed from the old stock camera app to the new camera app -- until I clean flashed there was no stock camera app available in the app drawer. Same with fingerprint -- wasn't working at all until I just went ahead and clean flashed.
[Verizon Galaxy S 5 Android Development] coopmaster:
Sweet thank you.
[Verizon Galaxy S 5 Android Development] De_stroyed 1:
do i need to download the superuser zip and flash it too haha
[Verizon Galaxy S 5 Android Development] haggertk:
You can, and some like it better than CM's built-in superuser, but it is known to cause some problems sometimes. Basically use at your own risk. I use the built-in.

For built-in: Enable developer options menu by tapping build number in About Phone about 10 times (toast notification will yell you when it's done). Then back out and in Developer Options enable Root Access.
[Verizon Galaxy S 5 Android Development] coopmaster:
You have to make sure to flash the newest version of superSU binaries or else you will find your self in never actually starting

---------- Post added at 03:08 AM ---------- Previous post was at 02:51 AM ----------

How do i install xposed on this ROM?
[Verizon Galaxy S 5 Android Development] haggertk:
All y'all are on your own regarding SuperSU and Xposed. Never used them and not going to chase down problems with messed up modules.

Google is going to have to be your friend. I'd go with "Xposed CM13.0" and maybe throw a "klte" into the search string.
[Verizon Galaxy S 5 Android Development] coopmaster:
Thank you for the response, as ive noticed quite alot of responses that are negative but thank you for answers all my annoying questions
[Verizon Galaxy S 5 Android Development] haggertk:
I apologize if I'm coming off overly negative. There are a lot of great tools out there that can be added to a CM/AOSP ROM, but every tool, every Xposed module, adds one more variable that could end up causing problems, especially when there may be incompatibilities between those variables.

My goal is to try to lock down, and hopefully get formally maintained, a rock-solid CM13.0 base. The amazing communities behind those amazing tools are best able to support those tools. The thing to keep in mind is that you basically have a bog-standard KLTE ROM now! With very few exceptions, if you find help for KLTE then you have help for this!

I probably need to put one of those dumb disclaimers in the OP that problems when Xposed/custom kernels/SuperSU/blah, blah, blah are installed cannot really be supported. At least by me. :p
[Verizon Galaxy S 5 Android Development] coopmaster:
Oh no thats not what i mean i just always see replies that are like cant you read you idiot and im saying you didnt do that.
[Verizon Galaxy S 5 Android Development] tbclandot:
Hey h thanks for this I'm debating about flashing this because I want Android M but I have a gear s and that's a touchwiz thing darn the plot thickens lol how does flashing a recovery go when you have safe strap installed do you just flash it in safestrap and it gets overwritten?
[Verizon Galaxy S 5 Android Development] bpham:
You'll want to flash TWRP through odin once your bootloader is unlocked.
[Verizon Galaxy S 5 Android Development] Ursader:
Installed this last night and so far no issues. Everythings been smooth, no errors. Never even had any problems with my service like was mentioned in an earlier post, although I haven't tested MMS yet. Also noticed my phone charges at 1800mah using the factory 2amp charger rather than 1200mah on the stock rom. I'm assuming thats related to the kernel, that or Ampere is reporting it wrong.

Thanks for your work on this!
[Verizon Galaxy S 5 Android Development] TioCareca:
I installed today and when phone is in standby it became very hot and with a big battery drain and then reboot by itself... anyone with the same problem?
[Verizon Galaxy S 5 Android Development] coopmaster:
This is because its either downloading in the background or doing something. When i installed mine it was hot and then now its fine.
[Verizon Galaxy S 5 Android Development] TioCareca:
I instaled gsam battery Monitor, underclock cpu turn off all apps internet bluetooth NFC and sync... It does the same... cyanogen system and kernel are always waking cpu...
[Verizon Galaxy S 5 Android Development] coopmaster:
Well maybe its because we need to flash a custom kernal?
[Verizon Galaxy S 5 Android Development] TioCareca:
??? Didnt know that...
[Verizon Galaxy S 5 Android Development] coopmaster:
well i mean if your coming off from your bootloader being locked then your probably running a kernal optimized for 5.x.x or 4.x.x but when i start my s5 it says something about the kernal usally so it probably would be a good idea to have a custom kernal. i have been looking at this one but i dunno if it would work http://xdaforums.com/galaxy-s5/orig-development/kernel-tw5crazy-kernel1-v124-8-15-t3185767
[Verizon Galaxy S 5 Android Development] TioCareca:
Maybe you right... i will lurk moar... But CM rom got a kernel of is own...
[Verizon Galaxy S 5 Android Development] coopmaster:
I think i might make a backup and then try flashing it and then i will tell you if it worked. I mean since our bootloader is unlocked and twrp a brick seems to be pretty hard to do well not hard but semi-hard haha
[Verizon Galaxy S 5 Android Development] TioCareca:
wipe data, cache, dalvik and system, if you can wipe internal sd too as it can contain some leftover files, but not realy needed...

If you flash a official stock rom by odin, you may lock your bootloader again, but you can use some custom touchwiz rom from [MENTION=1949695]jrkruse[/MENTION]...
[Verizon Galaxy S 5 Android Development] sdsubball23:
Thanks. By internal sd do you mean folder on the phones internal memory or the Microsd card?

Also, do you know if I can flash a custom touchwiz rom without having to relock my bootloader and by flashing it in twrp from my Microsd card?
[Verizon Galaxy S 5 Android Development] TioCareca:
Yes internal memory, and yes you can flash a custom in twrp and the bootloader will still be unlocked...

EDIT: If you not yet chosed what rom to use, try this:

http://xdaforums.com/verizon-galaxy-s5/development/purenote-5port5-1-1-rom-t3346368

as in my opinion by far the best tw rom out there...
[Verizon Galaxy S 5 Android Development] roguethree:
What did you say to VZW to get a new SIM when you went into the store? I'm in the same boat & can only connect when on LTE/CDMA.
[Verizon Galaxy S 5 Android Development] bclay12:
Anyone get HD calling on this ROM working?
[Verizon Galaxy S 5 Android Development] roguethree:
I was on rooted 4.4.4, updated to rooted 5.0 via jrkruse's instructions, then unlocked the bootloader via these instructions. Somewhere along the way I lost the ability to connect to a mobile network. I flashed back to unrooted PB1, but still could not connect. After reading various posts, including the entire of this thread, I was able to get service back by switching from LTE/GSM/UMTS to LTE/CDMA (and maybe it's just me but this feels like a slower connection). It looks like my SIM card is borked and I'll need to get a new one. If this is the case, should I root, unlock the bootloader, and reflash CM13 again BEFORE getting a new SIM or will that matter? If this isn't the case, what else can I try?

Also, when I was on CM13 for that brief period, making any call via the Google Dialer app caused a reboot. I was on the 5/14 nightly build* if that helps. I didn't set it as the default dialer, which was potentially the problem, but I thought I'd bring it up just in case.

*Apparently the 5/14 build was never pushed out so I have no idea how I got it. I could swear I got it from the CM site but it is no longer listed there. Your guess is as good as mine.
[Verizon Galaxy S 5 Android Development] t_house:
I am having random reboot issues. My phone will reboot on its own but never fully boot up. It will sit in a boot loop. Til today it wasn't an issue but it did it over night causing myself to not have an alarm go off. It fixes with a battery pull but if there is a way to fix this I'd love to know.

Sent from my SM-G900V running CM 13 Marshmallow
[Verizon Galaxy S 5 Android Development] Thorkle:
I just told them that I used the *228 dial code to try speed up my phone and it turned my LTE card into a 3g card. So long as it is a corporate store they replace it for free no problem. I called customer service first and they left a note on my account, but that wasn't necessary even.

---------- Post added at 12:33 AM ---------- Previous post was at 12:28 AM ----------

I messed up my sim card during installation too, and I took my phone in and got a new sim for free while on cm13, and it worked fine. The guy working there actually asked me about how to do it himself haha. They just switch the sim, and it works, unless the sim card isn't the issue

---------- Post added at 12:36 AM ---------- Previous post was at 12:33 AM ----------

Full data and cache wipe is always a good start. Otherwise you can try other kernels, that might help. Check out some kernels in the unified sgs5 forum. I think I'm using the kltevzw boeffla kernel, and it works great for me. Much better than the stock cm13 kernel.
[Verizon Galaxy S 5 Android Development] sdsubball23:
Did you try open camera app? I get more sharper pictures with it, though I think the pics may not stand out as much as the stock touchwiz camera app.
[Verizon Galaxy S 5 Android Development] cargohook:
I've tried updating to the 5/19 and now the 5/20 nightlies, but I'm getting the issue that attempting to place any phone call with the google dialer results in a reboot. I'm on the 5/20 CM13 nightly now with Open Gapps Stock 5/20, so no, roguethree, it doesn't have anything to do with whether the google dialer is set to default or not ... it's a bug. It's extremely frustrating, I can't even make a call.

Prior to this I was on the 5/4 nightly with no problems. Any ideas?

UPDATE: I'm going to try to re-install the 5/20 nightly with Open Gapps Micro and see if I still get reboots with the CM13 dialer, and report back.

UPDATE 2: The CM13 dialer on the 5/20 nightly with Open Gapps Micro works correctly. The bug is with how the 5/20 nightly interacts with the Google Dialer. I assume the same must be true of the 5/19 nightly as well. I'm not sure when this problem initially arose, but as I said, the 5/4 nightly didn't have this problem.
[Verizon Galaxy S 5 Android Development] adrenalinetaco:
I seem to not be able to boot with the Open Gapps Pico package, with the May 20th nightly. I just get an infinite boot loop. Any suggestions?
[Verizon Galaxy S 5 Android Development] adrenalinetaco:
I've tried it with multiple updates, probably important info. For some reason, it worked perfectly when I made a .md5 file to go with CM zip and installed with zip verification enabled.
[Verizon Galaxy S 5 Android Development] jmetcalfe84:
Anyone else have issues after trying to setup Whatsapp on the latest nightly? I've had Whatsapp installed since I switched over to CM13 last month but forgot to set it up. I use it to communicate with my younger brother over in Japan (Marines). When I went to go set it up I walked through all the settings and everything seemed fine for a minute but then the phone rebooted. When it came back up it reboots after showing the main lock screen for like 5 seconds. Not sure what to do now so I rebooted to recovery and dalvik wiped and re-installed the latest nightly to see if will help.
[Verizon Galaxy S 5 Android Development] yfz350:
I noticed my default phone app was blank after installing Open Gapps Stock and caused reboots as you're describing.

Check here: Settings > Apps > Gear (icon at the top right) > Default Apps > Phone app

Changing it to the Google Phone Dialer fixed the issue for me.

Also, you might can try the latest version from N preview 3 apkmirror
[Verizon Galaxy S 5 Android Development] tinroofrusted:
Anyone else having to manually install updates lately? It was working fine until the last couple weeks. Didn't change my recovery.
[Verizon Galaxy S 5 Android Development] twolostminds:
I am having a bit of a duh moment here and cannot get into USB Settings.

I need to change my settings from AP to CP and from MTP + ADB to RNDIS + DM + Modem.

*#0808# isn't doing it and well......help?
[Verizon Galaxy S 5 Android Development] TioCareca:
Do a clean flash...
[Verizon Galaxy S 5 Android Development] TioCareca:
Yep, thats a price to pay for cm...
[Verizon Galaxy S 5 Android Development] haggertk:
PSA!!!

DO NOT flash cm nightly 20160525 - the backup tool got borked so it doesn't keep your gapps.

If you already flashed you will have to start anew clean. :(

Fix is merged for the next nightly.
[Verizon Galaxy S 5 Android Development] purplepenguin:
welp FML flashed newest nightly - wish the changelog had big bold letters like the forum...
[Verizon Galaxy S 5 Android Development] haggertk:
I'm in the exact same state -- watched it boot up and then started yelling at my daily driver. Then I switched to the private IRC channel and saw other people yelling too. Started the clean install, got to the "restore apps" part, and then just left my phone at home on the wifi and went to work.

They ended up pulling the nightly, just not in time for all of us:

https://plus.google.com/+CyanogenMod/posts/U1truK1Jo6i
[Verizon Galaxy S 5 Android Development] mattwood2000:
Going through the same issues right now...restoring my backup. But, on a side note, anyone working with the merged SDCard storage? Obviously its not and automatic I had to manually flash the update file. Is this the expected methodology to flash updates when the SDCard is merged?
[Verizon Galaxy S 5 Android Development] cubajean10:
higuys quick question before i mess everything up i'vebeen running this for a few months just fine and i tried to update to yesterdays nightly , went to tw recovery and just tapped install and reboot to system. it's been at the cm system logo loading for a while i removed the battery tried a again and the same just a loop . i messedup didnt back up what should i try o and btw i was using boeffla kernel,

PD: mine wwas 5/24 nightly
[Verizon Galaxy S 5 Android Development] TioCareca:
Always do a backup, now you know why...

boeffla kernel is now gone as you flash a rom that got is own kernel... Go to recovery clean cache and dalvik, if the phone still dont boot (10 to 15 minuts to boot) you have to wipe system, data, cache, dalvik and start fresh with rom, gapps and all what you use...

If you got something that dont want to lose do a backup and later recover what you want with nandroid manager after you fix all...
[Verizon Galaxy S 5 Android Development] jdrch:
Small plea to put details like this in the top of the post. I flashed the testing tar.md5 file using ODIN and my S5 won't boot into recovery now. Please guys, you save so much headache by providing specifics up front.

That said, what do I do now? Last time I checked Flashify didn't work with CM (Or maybe I'm wrong about that?)
[Verizon Galaxy S 5 Android Development] haggertk:
Which tar.md5 did you download specifically? The old test1 is no longer there, but this one is good for our phone:

https://idlekernel.com/twrp/klte/testing/twrp-3.0.2-3-shim-klte.tar.md5

What specifically happens when it tries to boot into recovery?

And yes, flashing works with CM. I use it every day.
[Verizon Galaxy S 5 Android Development] jdrch:
The tar.md5 file is the one I used in ODIN.

Recovery mode bootloop happens. The logo appears with the usual rebooting message, then the screen flashes and the process repeats.

As for Flashify, it only works if you set SELinux to permissive, which, you know, is another detail no one happened to mention or tell how to work around. Had to hunt that answer down for myself: use this http://xdaforums.com/showthread.php?t=2524485
[Verizon Galaxy S 5 Android Development] haggertk:
Flashify does not require permissive. It only requires root privs granted.

Flash the linked tar.md5 in the ap/phone slot in Odin.
[Verizon Galaxy S 5 Android Development] jdrch:
Not on my SM-G900V running the official May 24 build (or any previous build I've tried it on). I always get an error message saying Flashify can't get root because it can't access SU in CM (I may have those details slightly wrong) and SELinux isn't set to permissive. Only after changing SELinux to permissive did it finally prompt for root properly and then work.

That's exactly what I did. All I got for my trouble was a recovery bootloop.

Anyway in the end setting SELinux to permissive using that app got Flashify to work, after which I flashed the twrp-3.0.2-3-shim-klte.zip file, which worked and didn't bootloop.

I'll add the above to my all-in-one every-single-detail SM-G900V CM13 installation guide later this week. Thanks!
[Verizon Galaxy S 5 Android Development] haggertk:
That's weird, really weird regarding Flashify. I've never set any of my devices to permissive and Flashify works fine, requesting root privs appropriately.

That specific recovery will likely disappear soonish. [MENTION=5672995]jcadduono[/MENTION] made that to test out incorporating the bootloader shim patch that allows the same kernel to work on both K/L and M bootloaders. When something greater than the current 3.0.2-3 shows up here, things will clean again. You can take a look at the 3.0.2-3 directory for the current mess. The "L" file will work for us, but it's confusing ("I'm running an M ROM, why do I have to use this "L" recovery?").
[Verizon Galaxy S 5 Android Development] jdrch:
Thank you so much for the details, man. I've updated my guide accordingly. That information definitely helps a lot.

Also, which version of Flashify are you using?
[Verizon Galaxy S 5 Android Development] haggertk:
1.9.2
[Verizon Galaxy S 5 Android Development] jdrch:
Ah. Found reason for difficulties and fixed. Thanks again.
[Verizon Galaxy S 5 Android Development] jgoulet:
Has anyone found a solution to the voicemail problem? I know it's been asked about a couple times already, but I haven't found an answer.
[Verizon Galaxy S 5 Android Development] cubajean10:
no dialer

Thanks, I did a full wipe but now every time i dial someone the cm logo pops up starts loading and goes back to home screen without making the call. I tried the build from 22nd and 24 same thing , could it be gapps 6.0 super 5/25? im trying gapps 6 stock 5/26 as i type will update

---------- Post added at 01:32 PM ---------- Previous post was at 01:08 PM ----------

i just read this on the log :you installed google dialer please set it as default phone application to prevent calls from rebooting your phone
[Verizon Galaxy S 5 Android Development] ldeveraux:
Nope, we keep asking, not fixed.

---------- Post added at 06:32 PM ---------- Previous post was at 06:31 PM ----------

I have to keep up with the klte development! Does this newest testing twrp still allow access to external sd?
[Verizon Galaxy S 5 Android Development] jgoulet:
What are people getting for battery life on this?
[Verizon Galaxy S 5 Android Development] sdsubball23:
Anyone know where I can find info on what got fixed and changed for the updates?
[Verizon Galaxy S 5 Android Development] puterdoc:
Here is the changelog link if that's what you wanted.

https://www.cmxlog.com/13/kltevzw/
[Verizon Galaxy S 5 Android Development] jdrch:
At least 2 of the builds so far this week have rendered my SD card corrupted. I'm wondering if it's due to flashing them from the SD card using the TWRP test build linked to in the OP.

I'm thinking of flashing back to Ktoonsez' TWRP & using that instead.

Does anyone know if the SD card problem is due to the recovery, or CM, or something else? Any ideas? This week has been a total nightmare with bugs & I'm pretty frustrated.
[Verizon Galaxy S 5 Android Development] puterdoc:
I had a similar week, just as frustrated yet continued to tell myself that's part of testing. No it didn't really help me either. The last time I even made a backup in TWRP to be ready for a failure, but noooo. it wiped the card and the back up too. So you aren't alone. It even said my SD card was invalid. Did this specifically happen do to adopted storage being used? I thought the TWRP dir was on the internal memory, but the cmupdate was on the SD card so can't say if where the update comes from has any effect.

Now I backed up then copied to my computer both the TWRP dir and the entire adopted storage contents. It unfortunately adds 20 mins to the process and requires computer. Until this past week I had not reset or full wiped my phone in a month or more of updates, and updated every day. Five minutes on wifi and poof new days version.

With the latest update so far the only reoccurring issue I have is the Bluetooth sharing fails. Happy with most else and on most builds love the battery life. Even listened to music while cutting grass and very few skips. Is anyone else getting the media volume keeps going back up on its own. GPS almost blew out my ear when I needed to turn left.
[Verizon Galaxy S 5 Android Development] lowfront:
I updated my nightly a couple days ago and have awful Bluetooth issues now everyone seems to talk about with CM.

The nightly I was using from a month ago didn't have this Bluetooth stutter issue.
[Verizon Galaxy S 5 Android Development] jdrch:
Same here!!! OMG I'm not alone. I made a nandroid backup to my adopted storage and the update corrupted the storage, thereby wiping out the backup. I was dumbfounded.

Yes. Ironically it's only happened with [MENTION=5672995]jcadduono[/MENTION]'s testing TWRP build, but the only reason I started using his build in the 1st place is so I could do nandroid backups to my adopted SD after the infamous May 25 CM build Google Play Services bugs required a fresh install as the only available fix (the other option was a nandroid backup, which I didn't have at the time. Lesson learned). So all I wound up accomplishing was replacing one megabug with another ... I almost feel like I'm losing my mind haha.

I suspect that flashing the update .zip from the adopted storage is either corrupting the adoptable storage or changing the "marker" (possible incorrect terminology) the OS uses to identify the SD card, thereby rendering unrecognizable on subsequent boot. I'm going to try putting the following on next update:

1) Place update .zip in internal storage at /data/Media/0/twrp

2) Reboot to recovery

3) Switch storage to internal within TWRP

4) Dirty flash update

5) Wipe cache/dalvik

6) Reboot into system

and see what happens. If the same thing happens again I'll probably switch back to KToonsez' build anyway.

Get the Monoprice USB OTG cable and USB 3.0 drive mentioned here, then format the drive as exFAT. Connect the drive to your phone and select it in TWRP, then use it as backup storage. Disable MD5 creation as the update .zip doesn't have that anyway and works just fine. If you that, backing up will take you between 4 and 5 minutes. MD5 creation lengthens that to 8 minutes, and enabling compression + MD5 takes around 20 min as you said.

Same here. Everything was going so well; since May 25 it's been 1 disaster after another. Fortunately all the important stuff on my adoptable storage is backed up via BitTorrent Sync so the effort to restore it is minimal.
[Verizon Galaxy S 5 Android Development] talktosamson:
This and the quality of TW camera vs. CM camera is the reason I'm staying with lollipop.
[Verizon Galaxy S 5 Android Development] ldeveraux:
I realize that Verizon is releasing their MM update soon, but I was seriously considering rolling back from CM13. I heard that LL has the bluetooth stutter too, not the case?