yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] tvsamson:
Same here. Not terribly slow, but it says in lockscreen charging slowly. Also is it me or does this rom not have as many notification panel toggles?
[Samsung Galaxy S 5 Unified Development] Dabylpmis:
I'm on the same build and model and can confirm issue 1 and 3.
[Samsung Galaxy S 5 Unified Development] :
More CM Features

I made a Rom and also a flashable mod (for any cm13 rom) with more features. I can't post it yet since i'm still waiting for permission from someone that i've used files from.

See Attachments

If anyone wants to test the mod here's the link to my mega folder: MEGA

Bugs: - NavBar can't be disabled

Note: Just Flash over your current rom

Please don't report any bugs on this thread
[Samsung Galaxy S 5 Unified Development] Vampirøs:
well as a lot people said 11/11 build is awesome and almost stable and with xposed it a lot better , oh and i flashed open gapps mini pack

some force closes here and there i noticed ,one of them when i tried to change lockscreen shortcuts

and there is something that may some people never notice is that if you want to change quick toggles places

just long press on settings icon in notification bar and then you will get system ui settings under about phone, i think its kinda trick :p

thanks albinoman, thanks xda community :D
[Samsung Galaxy S 5 Unified Development] sadaniel79:
I tried, it doesn't work. Had to clean flash everything using 22/5
[Samsung Galaxy S 5 Unified Development] haggertk:
What I meant to imply was that I don't expect that Samsung will release N for the S5, so we will stay at M blobs and an Samsung M kernel snapshot. The S5 was released with K, so we got two major version upgrades out of Samsung -- kind of surprising. Once we get on top of the Samsung M kernel I expect that we'll start to play catchup with CAF (Samsung may have done a lot of that, but you don't get commit history from the snapshot).

I don't foresee that there will be any major showstoppers getting N on our devices, but that's only a guess. Heck, I use my 4 year old Galaxy S3 with CM13 as my "get it sweaty when running" phone.
[Samsung Galaxy S 5 Unified Development] SuperSandro2000:
Thanks for the quick awnser!
[Samsung Galaxy S 5 Unified Development] PorchSong:
Haggert,

With new bootloader's, modems, and kernel blobs, did camera2 api get included? I've searched around but can not find an answer, other than Samsung screwed us.

**Also amazing that two f%#king posts after your PSA, someone is complaining that their gapps are not working after flashing 20160525. Stunning. . . .

Porch
[Samsung Galaxy S 5 Unified Development] MVZE:
Is that why it doesn't let me download?
[Samsung Galaxy S 5 Unified Development] haggertk:
Looks like they did pull them. Just not in time for everyone...

https://plus.google.com/+CyanogenMod/posts/U1truK1Jo6i

---------- Post added at 01:37 PM ---------- Previous post was at 01:19 PM ----------

We haven't gotten that far yet. We have a kernel that compiles (with the new toolchain) and boots. I've only personally tested it against the old blobs, but everything seems to work the same as before with the exception of the camera. Next step will be to import the new blobs and figure out which previously untracked blobs are now dependencies of the tracked blobs (suck them in too). Then we will see what broke and what has to happen to get things back to a functional state.

Ozzy and I expect we'll need to modify the CameraWrapper somewhat.

Camera2 is a Java API that is certainly in CM, whereas the blobs are C libraries and the wrapper acts as C abstraction layer. We'll have to see if it looks like anything is obviously exposed in the blobs that would allow for the added capabilities of Camera2, otherwise we'll still be in a "Camera2/legacy support" state.
[Samsung Galaxy S 5 Unified Development] Zenns:
Yup updating to M Blobs would be important since it may be the last major update we will receive, as for the camera since we using proprietary blobs it may due to wrapper not inputting the correct values or certainly something isn't right over here, best bet is reversing the blobs and writing from scratch[emoji14]lol then we won't need so much work to be done, but what I can suggest do a comparison between those two app zooming in on white background etc you will notice a quality degrade. Anyway keep up the good work mate. The rom works very well and battery is wonderful marshmallow will refined it even more :)
[Samsung Galaxy S 5 Unified Development] Zenns:
So I took a look at the camerawrapper obviously we are missing a lot of information of how our chipset work anyway we are using Samsung isocell 16mp,

www.samsung.com/semiconductor/products/cmos-image-sensor/mobile-cis/S5K2P8?ia=217

Rewriting camerawrapper would help but we need to confirm how does it work first example, how the processing is done officially and maybe we can improve on our own further :) hopefully we can get stock quality or better.
[Samsung Galaxy S 5 Unified Development] systemcrash:
MM bits available here:

http://xdaforums.com/showpost.php?p=66938911&postcount=5474

or here when it is back up

https://www.androidfilehost.com/?w=files&flid=18028

https://www.androidfilehost.com/?w=files&flid=18030
[Samsung Galaxy S 5 Unified Development] haggertk:
Oh we have them, actually for every specific variant that has released a 6.0*. :)

The klte-common and klte parts of the proprietary blobs will be based on 900F and the vzw, spr, usc parts (radio-related mostly) will be based on their specific releases... just need to find the time to attack it.
[Samsung Galaxy S 5 Unified Development] juantoten:
I read this way way too late. I clean installed my SGS5 SM900F with the 20160524 nightly and I still encounter the following issues:

Fingerprint scanner can't recognize my fingerprint.

NFC tag for the system profile can't register my NFC tag. I'm using the Sony NFC tags from my Xperia.
[Samsung Galaxy S 5 Unified Development] Zenns:
[MENTION=2693412]haggertk[/MENTION] is the kernel changes in for klte based on the latest MM I believe we are still using LP Kernel as of now right?
[Samsung Galaxy S 5 Unified Development] haggertk:
The current CM-13.0 kernel is based on BOH4 (L) with a lot of CAF and other commits thrown on top.

The M kernel merge is build on the current CM-13.0 kernel plus the changes in the CPD7 OSRC snapshot, as compared to the BOH4 snapshot. You can preview here:

https://github.com/haggertk/android_kernel_samsung_klte/tree/cm-13.0-CPD7_merge
[Samsung Galaxy S 5 Unified Development] :
Did Google play services get fixed in today's nightly?
[Samsung Galaxy S 5 Unified Development] Cdub1976:
No issues here. I'm also on mm bootloader and modem so no issues there either.
[Samsung Galaxy S 5 Unified Development] :
I've flashed it and it works fine with a MM bootloader. Thanks.
[Samsung Galaxy S 5 Unified Development] andrepd:
I'm thinking of buying an S5 and flashing CM13 on it. Do stuff like the fingerprint sensor or heart rate monitor or air gestures work on cyanogenmod?
[Samsung Galaxy S 5 Unified Development] carabinieri5675:
Please read the first post. You will find there the answer.

Gesendet von meinem 3310
[Samsung Galaxy S 5 Unified Development] PorchSong:
Fingerprint: yes

Heart rate: yes (using heart rate monitor program from play store)

Air gestures: what type? You can wave on black lock screen and it will pulse notify you. But controlling screen with gestures, in not sure.
[Samsung Galaxy S 5 Unified Development] Zenns:
That's wonderful hopefully changes will be together with blobs can't wait to see the improvement :)
[Samsung Galaxy S 5 Unified Development] Moffe11:
How's the camera quality on snapchat in the latest nightly?
[Samsung Galaxy S 5 Unified Development] systemcrash:
Nightly: http://get.cm/get/jenkins/163276/cm-13.0-20160527-NIGHTLY-klte.zip

Samsung MM binaries:

BL: BL_G900FXXU1CPE2 ( https://www.androidfilehost.com/?w=files&flid=18030 )

CP: CP_G900FXXU1CPB8 ( https://www.androidfilehost.com/?w=files&flid=18028 )

Hardware klte (SM-G900F)

boots fine, works fine. Snapdragon camera works well. Never been able to record slow-motion video using snap. Tested it in a samsung ROM so I know the hardware is capable.

Google camera cannot connect occasionally when swapping back and forth between video/photo. ( http://www.apkmirror.com/apk/google-inc/camera/camera-3-2-045-release/ )

Any questions?
[Samsung Galaxy S 5 Unified Development] computererds:
I've been unable to flash any of the nightlys for the g900v. They "all Error 7" on me, even if I remove the 'assert' line from the updater-script file. I also can't git clone the ktlevzw source to compile my own because "warning: remote HEAD refers to nonexistent ref, unable to checkout."

Is anyone else trying the g900v builds and having the same issues?

Update: Nm, I took out the first *two* lines of the updater-script file and everything went swimmingly with the May 24th build. Cloning from git is still a problem though if the project owners read this.
[Samsung Galaxy S 5 Unified Development] haggertk:
What recovery are you using. You shouldn't have to delete any asserts, they were made compatible with most valid recoveries a while ago.
[Samsung Galaxy S 5 Unified Development] computererds:
TWRP 3.0--Yeah, I don't get it either, it read like it should be fine and matched the phone. This is the first I've used twrp 3 though.
[Samsung Galaxy S 5 Unified Development] haggertk:
Official Twrp for klte (no variants?). It should be identifying itself as klte and therefore passing the (kltevzw or klte) assert.

Something sounds off.
[Samsung Galaxy S 5 Unified Development] computererds:
Yeah, 3.0.2-2 for klte; the tar downloaded from dl.twrp.me/klte --I can say with certainty now that I've checked.
[Samsung Galaxy S 5 Unified Development] jt1975:
I used twrp-3.0.1-0-klte.img.tar on kltespr and it worked fine, have You tried that one
[Samsung Galaxy S 5 Unified Development] steveokinevo:
Are there any working links on the 2nd or 3rd post? None of them work.
[Samsung Galaxy S 5 Unified Development] omgbossis21:
I use the twrp recovery app from the playstore. Just select klte or your variant, verify recovery location and flash.
[Samsung Galaxy S 5 Unified Development] Bazirker:
I'm running TWRP 3.0.2-1 on ktlespr, and it isn't working correctly for me either.
[Samsung Galaxy S 5 Unified Development] Zenns:
I cant wait for mashmallow kernel and blobs to be merged in :)
[Samsung Galaxy S 5 Unified Development] babalas01:
e: zip verification error

HI,

since 20160517 nightly I'm not able to flash any following nightly anymore.

twrp 2.8.7 is used and is always exiting with some zip verification error.

Anyone has a hint for me how to fix that, workaround?
[Samsung Galaxy S 5 Unified Development] Here-to-learn:101:
I flashed (updated) klte to the latest today and had to disable zip verification and also manually navigate to update folder.
[Samsung Galaxy S 5 Unified Development] JamesKinds:
Same issue for me. I still let the nightly download via CM updater, but I now install it by rebooting intentionally into recovery and selecting a manual install of the new zip (don't forget to also wipe Dalvick/ART cache). Everything then works fine. I'm not sure why, but if CM processes the zip file following the OTA update, it leads to the corruption. Very marginally annoying, but definitely not a show stopper at all. This started a few nightlies ago
[Samsung Galaxy S 5 Unified Development] JulGer01:
Live Display does not work... Latest nightly. Just after boot up it shows for seconds but after that the screen looks just as usual. No coloring. It works manual. But not with automatic. Don't know when it started. Used to work in the past...
[Samsung Galaxy S 5 Unified Development] Jayzee_16:
Might be a dumb question, but do I need to root first before flashing this? Sort of my first time doing this on my GS5. I did flashed a custom rom on my old phone w/out root but that's an old phonee. I've heard Samsung locked the bootloaders or something. I have G900F unlocked model

Edit:// Decided to root it because why not? Anyway, I wonder if there's fingerprint on the 12/27 build so that i'll use that instead of nightly.
[Samsung Galaxy S 5 Unified Development] yurividal:
No, it does no. Use nightly.
[Samsung Galaxy S 5 Unified Development] Bazirker:
Are you using adopted storage? I think that's why it won't work for me.
[Samsung Galaxy S 5 Unified Development] babalas01:
Thanks that worked, as you described by downloading only in CM, and then boot manually into recovery and flash from there.
[Samsung Galaxy S 5 Unified Development] Moffe11:
Does anybody else fall in a reboot when making/recieving calls? I can't seem to find a fix
[Samsung Galaxy S 5 Unified Development] jose13683:
I had the same problem using deltadroid gapps with google dialer addon. If this is your case, you have to set google dialer as default dialer app as stated in deltadroid thread.
[Samsung Galaxy S 5 Unified Development] Incarniac:
This is the solution. It can be found in Settings -> Apps -> Settings (top right) -> Default Apps -> Phone app -> Choose Telephone.
[Samsung Galaxy S 5 Unified Development] sinisin:
Ive been running 5.1.1 for a long time. Sat on wifi all weekend and lost data today when I left the wifi spot. Could not for the life of me get data back, even after a clean wipe. I was running the stock 4.1.2 NE5 firmware which I suspect had something to do with it. So I Odined back to NE5 and then took the stock MM update. Flashed TWRP and it kept resetting the recovery back to stock when it rebooted the ROM so I finally just flashed TWRP with Auto Reboot and F Reset off and then did a full wipe and flashed CM13. Forgot to flash Banks Gapps initially and it gave me a setup wizard and Google Play Services force close loop. So I did another full wipe and flashed Banks gapps before the initial boot and now everything is working good, or as good as can be expected. Ive been reading this thread for a while now and was waiting for the MM Firmware/BL to work with it. My only real complaints are you can't set up your own contact profile(The Aqua circle guy bugs me, as I run a red/black theme and it throws it off) and there seems to be no way to set up notification quick settings. Ive tried turning the switches on and off and so on and nothing gets rid of the ones I don't need or adds the ones I do. Other then that everything seems to be pretty stable. Phones calls, text, MMS are all working. Hotspot Mod is good to go(tho I can't get the QS Toggle to show up in QS). Bluetooth is working although it only got a short test.

Thanks for all your hard work guys! Much appreciated here. :good::good::good:
[Samsung Galaxy S 5 Unified Development] Bazirker:
Are you using adopted storage?
[Samsung Galaxy S 5 Unified Development] Jayzee_16:
Hmmm. This might be an ot to op but For some reason Odin won't let me flash twrp. Keeps saying that it failed to flash. I have version 2.4.8. So meaning I haven't rooted the phone for me to install supersu.
[Samsung Galaxy S 5 Unified Development] Cdub1976:
Anyone have Bluetooth stutter while unlocking your device? Mine stutters heavily and I can't remember the last nightly that didn't have it. April time frame...
[Samsung Galaxy S 5 Unified Development] MVZE:
See this is the thing. Everyone says they have major Bluetooth issues constantly, but the only time I get it is when I do unlock my phone. So you're not alone.
[Samsung Galaxy S 5 Unified Development] MVZE:
So, this is my clock right now. No matter how I stretch it. Suggestions on how to fix?
[Samsung Galaxy S 5 Unified Development] AcidTone:
Always on roaming

I'm hoping someone on here can help me. Up until yesterday I've been running cm-13.0-20160216-UNOFFICIAL-kltedv, that I downloaded from this thread. It's been great however now that CM is releasing nightlies for my variant (KLTEDV) I thought I would upgrade to one of those, for no other reason than to have a working fingerprint reader again. This is where I messed up, in my wisdom I didn't backup before I switched and now I have an issue with the new version where no matter what I do my phone is permanently set to Roaming. I've tried other nightly releases, other MM roms and they all have the same issue so if anyone has any ideas on how to fix it or has a link for the old cm-13.0-20160216-UNOFFICIAL-kltedv nightly that would be fantastic.

Right now I'm running twrp-3.0.2-2-klte with cm-12.1-20151007-kltedv but I would love to be back on MM
[Samsung Galaxy S 5 Unified Development] nalgrim:
I have 20160217
[Samsung Galaxy S 5 Unified Development] j1gga84:
Hello,

something in advance:

I don't use CM13.0 at the moment but a ROM that is based on CM13.0 (Resurrection Remix 5.6.9) and I have an annoying error in the Log (CatLog) since ages that is also present in BlissROM and AICP and not yet solved.

I did not check it in CM13.0 but this error occurs in the log very often (see attached screenshot)

I would like to know if this error is also present in CM13.0 (that's what I guess)

Now my question: Does this error occur with stock kernel and/or boeffla on CM13.0 or is it not present at all?

I would like to localize that error and if it occurs with boeffla but NOT with stock kernel I would forward this issue to Lord Boeffla, if it does not occur at all I would contact the developer of the custom ROM and if it is present with boeffla AND stock kernel it is a CM issue I guess and has nothing to do with the kernel..

When I check settings - battery 'android OS' is on first or second place (10-15% after one charging cycle) and I guess that is has something to do with the PowerHAL thing..

Maybe [MENTION=2693412]haggertk[/MENTION] has an idea!?

thanks & regards
[Samsung Galaxy S 5 Unified Development] PorchSong:
To everyone experiencing problems. IF you are using exposed, greenify a different kernel, restoring your old apps AND data, using an odd gapps, and dirty flash, and are experiencing issues with this rom then it is YOUR fault. Period.

I have been flashing roms since the myTouch phone and the ONLY times I experienced issues is when I strayed from the path. The nightly 20160528 works perfectly on my G900T device. I clean flash on major revisions but use CyanDelta for daily minor updates. Again, no issues other than the ones that plague Cyanogen device wide.

Almost every issue I see is rooted in user error, and mostly with programs added on afterwards

If you do an utterly clean flash and run the rom without restoring your apps--meaning you only have Cyanogen and gapps loaded--and THEN and ONLY THEN still have issues, then we can help you. But I constantly see people complaining about this rom only to find out they use greenify, or exposed, or a different kernel.

This rom is damn near perfect. Your problems are user error.
[Samsung Galaxy S 5 Unified Development] Cdub1976:
Looks like you have the same device as me. Are you implying that you don't experience Bluetooth stutter after unlocking your device? Yes I use xposed and greenify but up until a couple of weeks ago I had no issues with bt stutter other than the normal stutter when wifi is enabled.
[Samsung Galaxy S 5 Unified Development] PorchSong:
Please reread. I said issues that have always plague these devices. I was implying Bluetooth as it is the main issue and always has been. I was not specifically singling out you. I was ranting about general complaints in here that always are tracked back to addons or user error.

As for your unlock Bluetooth stutter, have you tried turning off greenify and exposed? I don't use Bluetooth. So I can help you there.
[Samsung Galaxy S 5 Unified Development] Cdub1976:
The issue I was, I say was now, wasn't system wide as I didn't find much in the way of others having the same issue. I just did a clean flash with only Spotify installed and no stutter after unlocking. Now I have to go through the pain staking task of installing apps one by one until I can pinpoint which one is causing the issue.
[Samsung Galaxy S 5 Unified Development] PorchSong:
Ouch. I hate trouble shooting app by app. Good luck.
[Samsung Galaxy S 5 Unified Development] jt1975:
Deleted

---------- Post added at 05:38 PM ---------- Previous post was at 05:37 PM ----------

If You mean mounting the SD card as external storage then yes
[Samsung Galaxy S 5 Unified Development] Bazirker:
No, I mean the new Marshmallow feature that integrates the microSD card such that storage is automatically shared between the two.
[Samsung Galaxy S 5 Unified Development] corsetto:
Hi all, my cm13 (build 20160529) charging my battery very slow. With ampere and connected with AC measuring only 300 mA.

I have boeffla kernel and I setted charging mx 1800 mA.

It's a bug? it's cm13 issue or it's related to kernel?

Thanks
[Samsung Galaxy S 5 Unified Development] JulGer01:
Was that working before? Might be your loader or cable...
[Samsung Galaxy S 5 Unified Development] corsetto:
yes, for sure is not the charger because sometimes I saw same peak up to 1800 mA.

I will try anyway without custom kernel
[Samsung Galaxy S 5 Unified Development] PorchSong:
Shouldn't be kernel based. Battery charges while phone is off if plugged in. It might be a misreport by ampre due to kernel. Or more likely it's your cable or ac converter. I have multiple chargers, and only the one that came with phone and two others will do 1800. Others are around 900-1100. But 300 if really low. So sounds to me as a misreport.
[Samsung Galaxy S 5 Unified Development] JulGer01:
Also the charging port could be the culprit. Try cleaning the port and the plug.
[Samsung Galaxy S 5 Unified Development] MeisterManuel23:
Well I noticed when I flash a new nightly that the charging speed goes down to 400mA, after some time it goes back to 1800mA like it used to be.

I'm using a S5 Duos (klteduos/SM-G900FD)
[Samsung Galaxy S 5 Unified Development] sinisin:
I just wanted to report I have 0 issues with BT. No cutting, scratching, or issues when unlocking. It's flawless. 5/29 kltespr on MM firmware.
[Samsung Galaxy S 5 Unified Development] corsetto:
For me it's the same.

Did you have a custom kernel?

Inviato dal mio SM-G900F utilizzando Tapatalk
[Samsung Galaxy S 5 Unified Development] steveokinevo:
Can someone give a link to the proper downloads please? All the links on 1st page don't work. 404. I did manage to get this on here (after a little google searching) and working pretty good so far. Just wanna know the right place so I can find both regular and nightly. Although I'm not sure the difference of the 2. I just experiment with them. Thx for any help
[Samsung Galaxy S 5 Unified Development] luriert:
www.cyanogenmod.org

www.opengapps.org
[Samsung Galaxy S 5 Unified Development] haggertk:
The error is common in all AOSP ROMs and comes from one of the two below locations (in CM):

https://github.com/CyanogenMod/android_device_qcom_common/blob/cm-13.0/power/utils.c#L270

https://github.com/CyanogenMod/android_device_qcom_common/blob/cm-13.0/power/utils.c#L284

It comes from where we call into vendor blobs (/system/vendor/lib/hw/power.msm8974.so). We have some kind of API mismatch, but it's not limited to klte... I've never noticed my Android OS battery stats being so high, but I'm not discounting it possibly playing a part.
[Samsung Galaxy S 5 Unified Development] AcidTone:
That's been my experience as well which is why before writing anything here I did the following:

Wipe the Dalvik / ART Cache, System, Data, Cache partitions

Install the Rom

Wipe the Dalvik & Cache partitions

Install OpenGApps (I've tried Stock and Micro)

Wipe the Dalvik & Cache partitions

I then skip what I can of the setup wizard on first boot to make sure it's nothing to do with imported settings that's breaking it.

I also done those steps with versions 2.8.7.0 and 2.8.6.0 of twrp recovery in case that had something to do with it. It's very odd that CM 12.1 works though and as soon as I can get my hands on the original nightly that I had installed I'll load that back on to see if it works.
[Samsung Galaxy S 5 Unified Development] Cdub1976:
Looks like it wasn't any app at all. It's kernel related. I flashed boeffla and now my stutter issues have ceased.