yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] rhyzan:
Heya. We seemed to have some problems in the headphone in our device after the kernel rebase. Mine is SM-G900L and it's part of the korean variants (Sm-G900S/K/L). It's not one of the supported devices in CM13 but it probably will be in CM14.

What [MENTION=7060205]sunilpaulmathew[/MENTION] did (according to the man himself) is he grabbed the dt of stock, kernel of mokee, ramdisk of CM and mashed it up to a boot image (Let's call it Boot 1) and this was used to fix the headphone and wifi bug that's plaguing CM13 users back then (Thanks be to Sunil LOL). Another one is to replace the dtb of custom rom to the one in stock and keep the kernel and ramdisk as it is (Call it Boot 2). Both of these boot images allow korean variants to flash and successfully boot KLTE roms with various results.

Now, after the kernel rebase, we're having some problems with headphones (and proximity sensor in mine) not detecting by the device when plugged in. When flashing Boot 1 to a nightly after 10/10 will make the headphone and proximity sensor useless while camera works. Flashing Boot 1 to a nightly before 10/10 will break the camera but proximity sensor and headphone works. Flashing boot 2 to the newest nightly will break the camera but proximity and headphone works and vice versa when it was flashed to a old nightly.

To temporarily fix the headphone bug, we used Soundabout app to manually route the audio from the speakers to the headphone. But for me, it sound quality is pretty bad. Much like the ones in calls.

We could wait for the Mokee team to update their kernel since they're the only one we know that officially supports Korean variants but i would like to get your take about this... I could provide some logs and some files when requested. I hope you'll respond.

Great work BTW. Keep it up.
[Samsung Galaxy S 5 Unified Development] haggertk:
Yeah, the problem is that the Korean variants, like the Chinese and Japanese, have a different device tree, so a different dt.img is compiled into the ramdisk. I really need to create that kltekor variant that I've been pondering. Shouldn't be too hard, maybe I do it while watching college football today.

And now that I think about it, I need to pull the S and K variants out of the klte init/init_klte.cpp file... It isn't appropriate for them to use the unified GSM.
[Samsung Galaxy S 5 Unified Development] rhyzan:
Nice. That's what I was thinking but I was having second thoughts. I'm not really well versed about this. And I think it's a good decision to pull out S and K from the unified GSM and make a separate one. We have been asking for S and K users in our group who actually flashed the alpha build and if it worked. So far, no responses.

Thanks for this. So the official support for kltekor will start on CM14? If that's so we're looking forward to test it out!

Sorry if I sound too demanding or anything. Haha.
[Samsung Galaxy S 5 Unified Development] haggertk:
If you are feeling particularly adventurous, give this a try. Don't use any third party kernels/boot images/etc. It should work, but I don't have the device in hand to try myself.

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

If it works, please try to get other SM-G900K/L/S users to try too.
[Samsung Galaxy S 5 Unified Development] aguarello:
Latest snapshot is draining battery a lot faster than the previous one, just flashed it yesterday... What could it be? Any thoughts?
[Samsung Galaxy S 5 Unified Development] rhyzan:
Thank you so much. I'll report to you the results in a few days.
[Samsung Galaxy S 5 Unified Development] rhyzan:
Heya [MENTION=2693412]haggertk[/MENTION]. Upon flashing the KLTEKOR rom, the device is stuck on the bootloader screen for us L users. No word from S and K users in our group but I assume that it will result in the same thing. I'm actually afraid that no one wants to test this out in our group since some favor TW roms than CM. We tried both LP and MM bootloaders with no success. Clean flash.
[Samsung Galaxy S 5 Unified Development] TiVa:
Strangest thing over here:

Saturday morning I tried to revert to a touchwiz rom to check if it's my phone or CM causing the flickering when turning on/off my screen.

After a hassle to restore my messages with titaniumbackup and updating all apps on this touchwiz rom,

I made an error causing my phone to crash, so I restored the nandroidbackup I had from friday evening

(the same build i was suffering from the flickering when screen on/off).

Back on this build (so not the test build) I didn't had the screen on/off flickering issue since saturday morning...

Is it because I went back to touchwiz before restoring my nandroid? Just luck? Just time untill it happens again? I don't know.
[Samsung Galaxy S 5 Unified Development] rhyzan:
Got some feedback from 900S users. Still no luck in booting it up. Stuck at bootloader screen (clean flashed) with both LP and MM bootloaders.

So to sum it up, tested devices are L and S. Both stuck in bootloader screen.
[Samsung Galaxy S 5 Unified Development] haggertk:
I'll move this to a PM later today, but I'm going to pass you an eng boot.img and will need some logcats/dmesg logs. Probably something minor that needs tweaked.
[Samsung Galaxy S 5 Unified Development] DickyG:
Finally got around to flashing this ROM...thanks to the developers...everything is working fine...phone, internet, GPS, all apps, etc. The only problems were ones I knew I would experience and there doesn't seem to be any good workaround: (1) Can't move any user apps to SD card...tried formatting card as internal storage and was able to move apps. However, when I rebooted phone, all those apps disappeared from home screen. Also could not back up Titanium to SD card. So I reformatted SD card to external and I can now back up Titanium files to SD card...also photos and music and stored there. (2) Link2SD hasn't worked since Lollipop so I just did away with second partition and froze the app.

If anyone has any thoughts on these 2 issues, would appreciate it...otherwise, no problems.
[Samsung Galaxy S 5 Unified Development] 0kti:
Signal network issue is fixed?

Tapatalk - Galaxy S5
[Samsung Galaxy S 5 Unified Development] rhyzan:
Sure thing. Will shoot you a PM.
[Samsung Galaxy S 5 Unified Development] systemcrash:
Which 'latest'? Faster than previous which? names, dates, links!

Screen shots of power mgmt....
[Samsung Galaxy S 5 Unified Development] j1gga84:
[MENTION=2693412]haggertk[/MENTION]

could you please have a look at the attached screenshots of my logcat.

Do you know what could cause these 2 errors and if they are fixable? they are present very often in my log. :confused:

regards
[Samsung Galaxy S 5 Unified Development] aguarello:
It's back yo to normal, I don't know what it was... Maybe just the battery adapting to the new build. Thanks anyway! :)
[Samsung Galaxy S 5 Unified Development] Bluefreak1988:
Is there anybody else having problems with Bluetooth?

Asked some pages ago. Media is possible with my car but not phone calls.

Can't find calls a solution for that...

JVC KD-871BT is my car system
[Samsung Galaxy S 5 Unified Development] Ozzy2403:
Haven't noticed any BT issues. Can you please provide a dmesg and a catlog.
[Samsung Galaxy S 5 Unified Development] f0xy:
[MENTION=7518817]cal002[/MENTION] what are you on with these days? :)
[Samsung Galaxy S 5 Unified Development] ikzouhetnietweten:
What modem do i need to flash on CM13? Build cm_klte_userdebug 6.0.1 M4B30X
[Samsung Galaxy S 5 Unified Development] systemcrash:
null MODEM ;)

---------- Post added at 08:39 AM ---------- Previous post was at 08:37 AM ----------

[MENTION=2693412]haggertk[/MENTION]

Has this (new MM cam blobs) happened yet? I have held back on upgrading to newer kernel base nightly since camera is important function :)

Anyone else knows cam works on latest nightlies?
[Samsung Galaxy S 5 Unified Development] heshan_1010:
Nightlies since the 7th of October have been using the new kernel :)
[Samsung Galaxy S 5 Unified Development] ikzouhetnietweten:
Tnx, so is it a problem if I flashed a modem of Phoenix ROM? Tnx
[Samsung Galaxy S 5 Unified Development] LGaljo:
For Titanium Backup issue: You have to change storage provider from filesystem to DocumentProvider ;) Go to preferences > backup folder location > click on Storage Provider above DETECT! button.

I hope it will help you :)
[Samsung Galaxy S 5 Unified Development] j1gga84:
Is anybody using Boeffla kernel with official nightly and recognises a bigger battery drain while using the device? There are some people in the Boeffla thread complaining about the CPU stuck at around 1500 MHz very often while in deep sleep all is okay as usual!?

Regards

Gesendet von meinem SM-G900F mit Tapatalk
[Samsung Galaxy S 5 Unified Development] ikzouhetnietweten:
Have a look at my thread about idle Battery life, Boeffla 3.3 is the best result I got so far (0,2% / hour)

http://xdaforums.com/galaxy-s5/general/battery-life-screen-off-best-rom-test-t3476406
[Samsung Galaxy S 5 Unified Development] Arthur King:
You need to change the minimal frequency and then put it back to 300, it's like CM has 1.5 Ghz of min frequency as default
[Samsung Galaxy S 5 Unified Development] startas:
Hi all, i was using cm long time ago, right now i am on official samsung rom, so i want to ask for recent information. What is current kernel version? What is current installation instructions to get all stuff like gps working? I remember some hacks were needed. Also, were flashy/laggy/blinking animations fixed?
[Samsung Galaxy S 5 Unified Development] rhyzan:
Hmm...

Kernel is 3.4.0... I think

Nothing much. Just flash (this and gapps) and go.

Hacks? Don't remember any.

Never experienced any lags in animations. Gaming? A bit. Just change CPU Governor to Conservative.
[Samsung Galaxy S 5 Unified Development] startas:
I know that gps doesnt work by default, you had to enable it and get it connected on samsung rom, before flashing cm, otherwise gps will never find a signal.

I noticed some roms having 3.8 and 3.10 kernels, or at least saying so in description, so i was wondering if cm is moving on that front.

I noticed that animations/effects are laging sometimes or dont appear at all.

But that was like this spring or so, maybe something has changed?
[Samsung Galaxy S 5 Unified Development] omgbossis21:
GPS is an old issue thats been fixed, different ROMs use their own kernel to support their own features, no GUI issues for me. Sounds you were using it still in beta form, its an excellent daily driver now. The most noticeable issue is the camera quality but I haven't tried it since the MM merge.
[Samsung Galaxy S 5 Unified Development] startas:
Well, i was using nightly builds(almost daily), so it was up to date version of cm 13 for that moment.
[Samsung Galaxy S 5 Unified Development] Ozzy2403:
With tomorrows nightly kernel Version will be 3.4.10 and in some days hopefully 3.4.112. I don't know any bugs woth GPS BT wifi vor anything else. Just flash and it will work...
[Samsung Galaxy S 5 Unified Development] haggertk:
Thanks for all the hard work [MENTION=5991425]Ozzy2403[/MENTION]!

For all, if you don't see a nightly today it's because there is currently an upload problem between the build servers and download.cyanogenmod.org. I've notified a couple people, but I don't know if they were at BABBQ and traveling back. If your variant actually got a nightly today then look at the about phone and see if you aren't already running 3.4.10!
[Samsung Galaxy S 5 Unified Development] Ozzy2403:
You are working hard too for the bringup Kevin ;)

I'm really happy you joined klte development. That's the best time i've ever had with an other developer. Thanks for you and your work.
[Samsung Galaxy S 5 Unified Development] aguarello:
Any one else experiencing extremely lagging music animation on lockscreen? :confused:
[Samsung Galaxy S 5 Unified Development] MVZE:
Anyone else been having proximity sensor issues? Its been acting REALLY weird. When calling, it can sense when I put the phone close to my ear, but never detects when I pull it back. Anybody else having this?
[Samsung Galaxy S 5 Unified Development] Ozzy2403:
Everybody who doesn't want to wait for the next nightly. Here is a build i made yesterday evening: https://www.dropbox.com/s/cq6icyovue1557k/cm-13.0-20161023-UNOFFICIAL-klte.zip?dl=0
[Samsung Galaxy S 5 Unified Development] Adam77Root:
Could you guys revert the fingerprint HAL changes? While I'm all in for an open source version, this one is buggy: if you hold your finger over the sensor and turn the screen on / want to turn it off, it freezes and you have to remove the finger for it to work. Also, the bigger problem: it drains battery very fast. I was waiting for a few days to test it properly and now am sure this is the issue.
[Samsung Galaxy S 5 Unified Development] Fil in XDA:
The lag/frame stutters in gaming still exists in the latest nightly (haven't tested your build yet). I'd say gaming is more laggy than the stock rom. They say changing the cpu governor to conservative fixes the frame stutters but did not work on some of the users including me. The system is very fast & fluid though. And the music visualizer in the lock screen also lags but not permanent. It's just when you choose a next music track, lag happens. I know you devs are working hard building cm14 for our klte and finally making cm13 very stable as a daily driver by squashing out bugs. We thank you for doing free work for our devices. We users appreciate you devs a lot. So far those only two issues are the only thing that I've come across.
[Samsung Galaxy S 5 Unified Development] j1gga84:
[MENTION=5991425]Ozzy2403[/MENTION] [MENTION=2693412]haggertk[/MENTION]

I don't know if there are any issues with the CM stock kernel after switching to Android MM kernel sources but with boeffla kernel I have a bigger battery drain than before and I am not the only one, I also reported that in boeffla kernel thread..

Boeffla kernel is fully based on CM stock kernel so I ask myself if you also encounter a higher battery consumption after that change?

The thing is that the CPU stucks very often at 1574MHz when device is idle and screen is on, very rarely it goes down to 300MHz, which was the case before.. (I am using interactive/zen combination), no issues when device is in deep sleep.

maybe you could double check and monitor this behaviour with stock CM kernel over a longer time (24h for example) ?

Also Lord Boeffla said that after the kernel merge 2 cores stay active all the time, what is the reason for that change? does that not automatically means a higher battery consumption?

thanks & regards
[Samsung Galaxy S 5 Unified Development] Fil in XDA:
It happens to me also. I'm using the stock kernel. Even when touching the screen both core 1 and core 4 would ramp up to 1574 mhz and for me both cores usually goes back to 300 mhz. I always thought that it was for performance boost purposes but idk. No battery drain for me. Just my battery getting old and I might have to buy a fresh new one.
[Samsung Galaxy S 5 Unified Development] Ozzy2403:
At stock mm 2 cores stay online when the screen is on. Boeffla uses a dirty hack to disable this behaviour. Althought if this works wie won't push this hack to cm stock. I'm already locking if i find another solution to disable the second core.

And maybe there is more battery consumption due to fingerprint changes. But i don't habe enougj time for everything...
[Samsung Galaxy S 5 Unified Development] DragonQ:
Does anyone get Bluetooth audio playback without skips? At the moment I'm using the latest snapshot and I get a few skips on my 30 minute journey to/from work each day. Same for the previous snapshot from August. When I was using the stock ROM, I got no skips at all.

Apps running: Rocket Player, Google Maps

WiFi: Off

GPS: On

3G/4G: On

Any tricks to get this working or is it just a persistent CM13 bug?
[Samsung Galaxy S 5 Unified Development] phalkon30:
Audio skips have been gone for me since... July? Can't say I've seen any complaints recently either. I would think latest snapshot is new enough to include the latest fixes, but maybe install the latest nightly. Nightly right now is as stable as snapshots were and includes latest fixes

Sent from my SM-G900R4 (klteusc) running CM13 9.12.16 with xposed
[Samsung Galaxy S 5 Unified Development] Essentrix:
Minimum frequency doesn't seem to be sticking. Any thoughts? Using latest kltedv build.
[Samsung Galaxy S 5 Unified Development] Ozzy2403:
https://www.dropbox.com/s/qbiknwrpg4wr9f1/cm-13.0-20161024-UNOFFICIAL-klte.zip?dl=0

Built yesterday evening. Linux Version 3.4.12
[Samsung Galaxy S 5 Unified Development] cybertroll:
Two small bugs but rather annoying:

* Music does not seem to remember not to change the wallpaper of lock screen to album art when you turn it off. Everytime you start music again, you need to go and turn it on and off again even when it's off, in order to remove the album art from lockscreen

* AudioFX seems to forget the last setting when you start music. You need to go again to audioFX and run it, then it remembers the last EQ setting.
[Samsung Galaxy S 5 Unified Development] lukearan:
Is anyone else having issues with the fingerprint sensor being completely out of commission still? I tried removing them all and starting over in case the prints themselves had somehow been corrupted, but now it just says "enrollment not completed" without even giving me time to scan the prints. Been doing this since the last snapshot.
[Samsung Galaxy S 5 Unified Development] htb2050:
Fingerprints are messed up. I wonder why would we even want a broken thing in the rom. It murders the battery life too.
[Samsung Galaxy S 5 Unified Development] Adam77Root:
The previous version with original Samsung blobs was working well, the new open-source one is broken.
[Samsung Galaxy S 5 Unified Development] dpaivap:
Is possible to rollback to Samsung way?
[Samsung Galaxy S 5 Unified Development] madboyting:
How do I change the kernel on this ROM for the best battery life. I'm using boeffla as well and I'm experience abysmal battery life at least to me. Every hour battery drains 8-10% even with greenify killing all apps
[Samsung Galaxy S 5 Unified Development] Arthur King:
Well, you have the screen time at the same time that your battery goes down so I thin you have to check the bright of your screen. Also your mobile signal its so bad, usually having bad signal its a good way to have a battery drain
[Samsung Galaxy S 5 Unified Development] madboyting:
I turned all of that on later in the day around 40%. Without all of that it still drains 10 percent a hour idle. And how do I turn off mobile signal I don't even have a phone plan atm
[Samsung Galaxy S 5 Unified Development] madboyting:
I may just need a new battery?
[Samsung Galaxy S 5 Unified Development] Bluefreak1988:
Sorry for late late response Ozzy2403! I don't have a laptop to make ADB-logs in my car.

Is there any other way to make a log?

Bluetooth issue and what I tried:

I still can't connecht to my car radio JVC KD-871BT

I did a firmware update of the radio

I deleted all bluetotth connections

I made a radio reset every time I changed the ROM

I did a clean rom-install every time

With CM14 it's the same problem btw.

Rom-combinations I tried:

CM12.1 with

Bootloader: BL_G900FXXU1BPA2

Modem: CP_G900FXXUBOL3

---> Works great! Media and phone!

CM12.1 with

Bootloader: BL_G900FXXU1CPH6

Modem: CP_G900FXXU1CPH6

---> Media only

CM13 mit

Bootloader: BL_G900FXXU1BPA2

Modem: CP_G900FXXUBOL3

---> Media only

CM13 with

Bootloader: BL_G900FXXU1CPH6

Modem: CP_G900FXXU1CPH6

---> Media only

Slimrom with

Bootloader: BL_G900FXXU1CPH6

Modem: CP_G900FXXU1CPH6

---> Media only

What else can I try? How can I provide ADB-logs without a computer? :eek:
[Samsung Galaxy S 5 Unified Development] dimiav:
Does anyone knows why Cyanogenmod stopped the Nightly Builds?

I see that all the servers are IDLE and the last run was 3 days ago
[Samsung Galaxy S 5 Unified Development] htb2050:
Because there arent any changes day to day. Running the servers to produce the exact same file everyday isnt worth it.
[Samsung Galaxy S 5 Unified Development] dimiav:
same for all devices??!? as its not only for KLTE...

also I seen times where there were no commits at all and still a new nightly build was created.

currently there are about 10 new commits, half of them are KLTE related.
[Samsung Galaxy S 5 Unified Development] haggertk:
They're broken somehow. Over the weekend they were making builds but some were failing to upload. Several maintainers are asking for status/resolution in private channels.
[Samsung Galaxy S 5 Unified Development] Essentrix:
Enjoying recent updates. One bug after clean flash latest kltedv - contacts don't appear to be syncing. Dirty flash no problem.
[Samsung Galaxy S 5 Unified Development] l4nc3r:
Tried to install in KLTEVZW and it said not supported. Just letting you know.
[Samsung Galaxy S 5 Unified Development] phalkon30:
Because that's a klte version, you need a kltevzw version... Someone has to build one for you or just wait until cm nightlies come back on

Sent from my SM-G900R4 (klteusc) running CM13 9.12.16 with xposed
[Samsung Galaxy S 5 Unified Development] haggertk:
Jenkins was unborked, nightlies have begun again, and klte should be up in a couple hours.
[Samsung Galaxy S 5 Unified Development] Triviox:
A noob question..can we change the kernel when use CyanogenMod 13? I have cm13 in klte g900m.

Thanks!
[Samsung Galaxy S 5 Unified Development] l4nc3r:
Understand there's a difference, just didn't know there was a special build for KLTEVZW separately.

[MENTION=2693412]haggertk[/MENTION];

Thanks for fixing the nightly builds!
[Samsung Galaxy S 5 Unified Development] haggertk:
Oh, I didn't fix them, I was just part of the chorus complaining to the right people about them.
[Samsung Galaxy S 5 Unified Development] HulkSmashBurgers:
Anyone know if the latest nightly has the kernel fix for Dirty Cow (CVE-2016-5195)? I've been wanting to try this ROM out, but I've been waiting for that patch.

What current gapps is recommended?
[Samsung Galaxy S 5 Unified Development] haggertk:
Yes, https://review.cyanogenmod.org/#/c/166798/

It's actually been in since Friday morning, but build servers have been broken since then. Take any nightly dated 22 Oct or later.
[Samsung Galaxy S 5 Unified Development] HulkSmashBurgers:
Thanks.

This changelog doesn't list the CVE, so I didn't spot it. I used to run CM11 on an S2, and I would see security patches listed with CVE numbers. Wish they would still do that.

https://www.cmxlog.com/13/klte/
[Samsung Galaxy S 5 Unified Development] haggertk:
Sure it is. It's the very first (bottom) commit in the 27 Oct build.

We don't munge upstream commits. Linus didn't list the CVE ID in his commit message so we don't change that. I *normally* add it to the Gerrit change as a topic name, but I was in such a rush to click "submit" that I forgot on this one.
[Samsung Galaxy S 5 Unified Development] HulkSmashBurgers:
Edited my post. I meant to say that they didn't include the CVE#, which I'm used to searching for.

What is the current recommended gapps? Can I just grab somehting off opengapps.org?
[Samsung Galaxy S 5 Unified Development] haggertk:
I use opengapps mini, some prefer banks.

Aside from some people occasionally having issues with the really big versions, I haven't heard of anyone with issues with recent 6.0 opengapps versions. As I'm sure you know, opengapps can go from a great build one day to a terrible one the next day, so YMMV.
[Samsung Galaxy S 5 Unified Development] l4nc3r:
OpenGAPPS Mini ^^ I feel is the best package, perfect amount of Google Apps. And you can always add things later if needed from the Play Store. Arm(Non 64) 6.0 Mini from http://opengapps.org.
[Samsung Galaxy S 5 Unified Development] DragonQ:
The latest snapshot is from mid-October, it's definitely new enough. I still get skips though. I have no idea what causes them - I even had a system monitor app open once when it happened and there was no unusual CPU usage spike or anything.

I can't see anything relating to this in the recent changelogs at all.