yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] phalkon30:
Bumping this, just read through 40+ pages to find it. We're having great very similar issues again starting sometime in September, I'll give this a try again.

Edit: just tried, got an immediate accurate fix in maps (was previously using cell and WiFi for semi accurate location).

Anybody else confirm? Page 463 (or maybe 436, lol don't remember now) have discussions on the commits to fix this bug

Sent from my SM-G900R4 (klteusc) running CM13 9.12.16 with xposed
[Samsung Galaxy S 5 Unified Development] Reechings:
Sorry for OT but does anyone know a way of allowing the screen to be turned off while casting? My work S5 on KitKat I can do screen mirroring and turn my display off and on with no interruption to audio and no other issue. When I try that while casting on my other S5 with CM, the screen goes off but when I wake it I can't unlock the phone any more and have to reboot manually.
[Samsung Galaxy S 5 Unified Development] phalkon30:
I use screen casting all the time on cm and have never had that issue. What version of cm13 are you using?

Since you posted the same thing in the RR thread, are you running a custom kernel like boeffela? What modem/baseband are you on?

Sent from my SM-G900R4 (klteusc) running CM13 9.12.16 with xposed
[Samsung Galaxy S 5 Unified Development] ScratMan38:
May you have an app that may set the phone to deep sleep / doze immediately after screen off (like Greenify, for example).
[Samsung Galaxy S 5 Unified Development] Reechings:
You are right that I am using Resurrection Remix and sorry I didn't make that clear. It is good to know that it does work normally on CM13, so you can turn the screen on and off with no issue?

I don't think it is a kernel or greenify issue as it does it with stock or boeffla and the music doesn't cut right off when the screen goes off. It seems like possibly a lock screen overlay issue or something as when I wake the screen it still shows the last screen I was on but acts like I am on the lockscreen. I don't have the lockscreen set to use the last image or anything and have a lockscreen wallpaper set. Must be a result of the advanced lockscreen options on RR.
[Samsung Galaxy S 5 Unified Development] heisenberg17:
No' it's not. There is a unofficial build for G900H but camera and other stuff is not working

http://xdaforums.com/galaxy-s5/development/rom-unofficial-cyanogenmod-13-0-galaxy-t3325783
[Samsung Galaxy S 5 Unified Development] dbart2:
I got lock in the 'note5 MM port' ROM, pulled battery, installed CM nightly, clean install, GPS working.

I think bug might be fixed anyway.
[Samsung Galaxy S 5 Unified Development] FlemishDroid:
I got a bootloop after dirty flashed latest DevVorteX build so I used aroma filemanager in recovery and I removed the supersu file from /system/addon.d and dirty flashed latest DevVorteX build again and it booted fine. I immediately saw the superuser icon in statusbar when system booted so I have root and I can write to /system in Root Explorer without problems. I also changed Selinux with Selinux mode changer so it's permissive again.

Verstuurd vanaf mijn SM-G900F met Tapatalk
[Samsung Galaxy S 5 Unified Development] GartimusPrime:
I am trying to build for klteusc and every build I do just bootloops and I can't even get adb to work to get logs. Any ideas before I start beating my head against a wall?
[Samsung Galaxy S 5 Unified Development] NightMare870:
I take it there's no fix for this currently. It does suck that if you miss the call and don't see the number when it's ringing, then you can't call back because it shows unknown. Everything else on this is great, I've had no other problems whatsoever.
[Samsung Galaxy S 5 Unified Development] FlemishDroid:
I tried BETA-SuperSU-v2.52 but it also gave bootloop. I tried with Selinux set to permissive but it also bootloop. I changed Selinux with the app Selinux Mode Changer but I'm pretty sure the app changes the Selinux status when rom is booted so it doesn't matters when system boots. I hope Supersu works again one day but the built-in Superuser works so no big deal for now. ;)

For the people that missing the feature "kill app with back button" it's back on DevVorteX build go to settings --> developers settings

Verstuurd vanaf mijn SM-G900F met Tapatalk
[Samsung Galaxy S 5 Unified Development] mvalcar:
SD problem

Problem with SD card in ktle cm13

When install the last build then no recognized my external SD card and give me only the format possibility

Can I maintain my data and no formating the SD card ?...in the normal roms never must be ..

thanks in advance
[Samsung Galaxy S 5 Unified Development] FlemishDroid:
I had some problems with my external sdcard and I copied everything to my pc and formatted my sdcard in CM13 settings and it works perfect now.

Verstuurd vanaf mijn SM-G900F met Tapatalk

---------- Post added at 03:05 AM ---------- Previous post was at 02:59 AM ----------

When DevVorteX build booted for the first time I had root and could write to /system but after 1 reboot I also couldn't write to /system anymore. :(

The build was working great but I reverted back to Albinomans build because of the Supersu (bootloop) and built-in Superuser (no write to /system) problems.

[MENTION=5354353]DevVorteX[/MENTION]

Is it possible to reverts the Selinux commits and built rom? I only ask it's possible no demand for new rom. ;)

Verstuurd vanaf mijn SM-G900F met Tapatalk
[Samsung Galaxy S 5 Unified Development] mostyle:
I had this happen once the first boot but then hasn't happened again..

I am having a strange occurrence though.

Background:

S5 G900T (TMO variant) running generic klte running on AT&T network.

When the device initially boots it takes anywhere from 15 to 30 secounds to see the cell network. Upon seeing the cell network I then have data but it is HSPDA+ (shows as H rather than LTE icon. It stays this way for about 20 minutes (on HSPDA+) and then seemingly randomly switches to LTE. Happens consistently. Also when this happens I will consistently lose carrier if the data has to switch data speed tiers (say from 3h>H or LTE<H). It's most notable notable when terminating a phone call as the data signal trys to jump from H to LTE.

Previously I was using KLTE 12.1 and the curious thing here is that it used to perform in exactly the same manner as how 13 is behaving now. The last time I remember it was one of the August nightly builds of KLTE 12.1. I don't update regularly when using official CM release so when I finally updated builds it was in late September or early October but when I did all of the issues were gone. Instant cell network, LTE etc. It has been that was on every update to 12.1 since.

Just struck me as odd that what appears to be the exact issue has appeared (at least to me) now in 13.

As one final check I backed up the 13 install before restoring the 12.1 and upon seeing the 12.1 restore was fine retried the 13 backup (redundant yes, but want to see if there could have been an intermittent carrier issue with AT&T) and it was indeed behaving as described still.

Not complaining here mind you.. Just passing on info. After a day or so on 13 I restored my 12.1 backup and the device works perfectly again.

Your efforts are appreciated. Thank you.
[Samsung Galaxy S 5 Unified Development] AuGmENTor:
If you use Google voice you can go into that and see missed /recent calls.
[Samsung Galaxy S 5 Unified Development] altojd:
well, i've installed the new build over 11/11 (after wiping cache, dalvik and system) and opengapps of 11/13.

had beta supersu on my 11/11 build. root is working great after second boot, can read and write to external sd card and selinux is set for enforcing.
[Samsung Galaxy S 5 Unified Development] Vampirøs:
so you're not having any problems?
[Samsung Galaxy S 5 Unified Development] altojd:
definatelly not. the new build runs flawlessly
[Samsung Galaxy S 5 Unified Development] iamnotkurtcobain:
Tried it, not working but thanks.
[Samsung Galaxy S 5 Unified Development] altojd:
what exactly doesn't work?
[Samsung Galaxy S 5 Unified Development] iamnotkurtcobain:
SuperSU and R/W.

Flashed build 11.11. and SuperSU.

Flashed build 19.11. over it and bootloop.
[Samsung Galaxy S 5 Unified Development] altojd:
be on 11/11. flash beta supersu 2.52.zip and reboot.

go to recovery again, wipe cache, dalvik and system. don't wipe data.

install the new build and open gaps of 11/13. DON'T FLASH supersu again.

reboot. on my klte it worked
[Samsung Galaxy S 5 Unified Development] jejemc:
Hello impossible to change the image profile of the latest version ;)

but works on the old ;)
[Samsung Galaxy S 5 Unified Development] Mr. Robot:
Is it stable? Right now I have this http://xdaforums.com/galaxy-s5/unified-development/rom-cyanogenmod-12-1-android-5-1-t3066252 Should I flash this rom ? I asked this because I like 12.1 very much and I don't know if I should upgrade to this version.

sorry for noob question

-------------------------------------------------------------------------

[MENTION=2585765]humercab[/MENTION], so should I wait for a fix (stay at 12.1) or it will be fixed very soon (flash 13.0) ? does it have nightly versions like 12.1 (updates almost every day) ?
[Samsung Galaxy S 5 Unified Development] humercab:
I us it as daily driver for 14 days and it is great and stable. The only problem with latest version is with root..It is not working...
[Samsung Galaxy S 5 Unified Development] WuNgUn:
Also just noticed that the screen wakes when plugging in and unplugging from the charger. Jeezus, it's like I'm running TouchWiz again!! Noooooooo!

Gotta make these bugs a priority!

:)
[Samsung Galaxy S 5 Unified Development] rbimdxe:
So far, have no issues with DeVortex's build. Been running for about an hour and root is fine for me, was running 20151111 with SU2.52 fine, and just dirty flashed 20151119 and Benzo GApps over the top and root from Dev Options works for Titanium Backup so far, haven't tried others as out to dinner.
[Samsung Galaxy S 5 Unified Development] Bryanx86:
Confirmed GPS working accurate now
[Samsung Galaxy S 5 Unified Development] aguarello:
GAPPS links are not working, i thought of getting them from opengapps, but when I read on first post "No other gapps currently supported" I got confused. What does it mean "no other gapps currently supported" and why? where should I get them then? Thanks!!! :)
[Samsung Galaxy S 5 Unified Development] donj001:
For whatever it's worth, I flash open gapps on cm routinely without any abnormal results. Hope this helps.
[Samsung Galaxy S 5 Unified Development] rayzen6:
Hi [MENTION=2693412]haggertk[/MENTION]. I hope all is good with u? May I ask you how cm14 going for klte. Like what is status now? We r not in hurry, just plz you could able to tell us what's the Major things are working and not? Like ril,camera etc..

Thanks for ur and team's hard work.
[Samsung Galaxy S 5 Unified Development] schliflo:
Don't ask for status or ETA's - simply follow the progress over at gerrit or GitHub:

https://review.cyanogenmod.org/#/q/project:CyanogenMod/android_kernel_samsung_klte

https://review.cyanogenmod.org/#/q/project:CyanogenMod/android_device_samsung_klte-common

https://github.com/CyanogenMod/android_kernel_samsung_klte/tree/cm-14.0

https://github.com/CyanogenMod/android_device_samsung_klte-common/tree/cm-14.0
[Samsung Galaxy S 5 Unified Development] rayzen6:
Lol bro its not an eta. Also I wrote we r not in hurry. Status updates are usually given by devs at XDA. There's no rule regarding it. I know what to follow. But things are not like that lol. All things maybe not updated at gerrit too.

I have full respect for devs working on it. Thx devs.
[Samsung Galaxy S 5 Unified Development] Bec de Xorbin:
Any bugs? Battery backup good? When CM14?
[Samsung Galaxy S 5 Unified Development] javelinanddart:
Everything we're doing is publicly available, like [MENTION=5929231]schliflo[/MENTION] mentioned

Asking us for status updates is annoying, if devs choose to provide status updates, good for them.

Even you said that it's "given by devs" not asked over and over again by users, which is called bugging the devs.

The status update of what is working and what is not can easily be tracked by our patches on gerrit.

Battery backup? you mean battery life? That's pretty good

I haven't noticed many bugs on CM13

On your last question: Don't ask for ETAs, ever. Bugging devs for status updates and ETAs is the #1 way to tick them off.

We spend our free time doing this, and if we're getting ticked off,

we'll move onto something that won't tick us off, and leave Android behind.
[Samsung Galaxy S 5 Unified Development] rayzen6:
I just asked once here bro. But seriously I have very much respect for you guys. Sorry if I annoy or hurt u. Never mind me. Thx.
[Samsung Galaxy S 5 Unified Development] Bec de Xorbin:
Thank.
[Samsung Galaxy S 5 Unified Development] javelinanddart:
The over and over again part is just as a whole, not trying to say it's JUST you who's asking :)
[Samsung Galaxy S 5 Unified Development] Triviox:
"process system isnt responding" after all reboots

Hello people!

My device said "low space"; i have a 32 GB memory with data of apk there (i havent low space!!), i did reboot and problem was fixed :D .. but, now, after all reboot i have messege "process system isnt responding.. close?". I press "acept" and phone works OK, but it apears after all reboots!!

Someone know why that bug? I flash update to last night to try fix (and problem still not fix); im with supersu rs1 2.78 systemless + suhide 0.53 + xposed systemless 68.2 (to have "safetynet OK" + "xposed"). I had not problem for more 24hs (im with cm13 since last 24hs or 30hs :D ), but now, i do wipe dalvik/cache, and update to last night, and after all reboot said the same messege "proccess system.." :(

Any idea? Thanks!

PS: I attach "liveboot.log"; maybe some1 can see there whats the problem :D

PPS: Before it, i today saw some apk arent ready to use after update, i think "need more time" to be "rigth to use" ; for exemple Firefox or Facebook arent ready to use after reboot, is it normal? Thanks!
[Samsung Galaxy S 5 Unified Development] igorescu04:
Hi guys, just want wo share my impression with the latest nightlies.

I have been testing the latest nightlies past week and I must say I'm impressed, no single FC, all is working so smoth and fast.

The only thing that made me change again to stock was the camera quality. It remains like the only thing that doesn't stand for against stock.

I reached one day at 4hours of sreen with the stock battery and a full day of use. This is really somethingelse.

Great work of the [MENTION=6921782]Cyanogen Dev Team[/MENTION]

Hope there will be something done with that in the future.

Regard.
[Samsung Galaxy S 5 Unified Development] htb2050:
You aren't even using and are on stock so why does it matter? ????
[Samsung Galaxy S 5 Unified Development] igorescu04:
it matters because there's always someone who need know what to espect installing the latest nightly.

I have that doubt, tryed it and shared my opinion? What's the matter with you? woke up on the wrong side ob the bed?
[Samsung Galaxy S 5 Unified Development] htb2050:
Wrong side of the life actually.
[Samsung Galaxy S 5 Unified Development] TiVa:
Hi,

My amoled screen is flickering like crazy on low brightness... I know this isn't a CM bug but just the amoled (reverted back to stock, tried new versions of cm, old ones... it always returns). The thing is it only happens on very low brightness. That wouldn't be a problem you think: just don't go that low in brightness. And you would be correct, if only the dimming function wasn't that low.

I found the MM GravityBox on xposed can edit the brightness, and this works, but Gravitybox for just a little tweak was a bit overkill if you ask me. So I tried to decompile framework-res.apk to set the minimumbrightness and dim brightness a bit higher. Any chance this could be a setting we van edit in cm? That way i don't have to recompile Evert time...
[Samsung Galaxy S 5 Unified Development] Reechings:
It's never going to be quite as good as stock but I am using Snap Camera HDR with saturation set to +2 and it feels pretty close to me.
[Samsung Galaxy S 5 Unified Development] 0kti:
I have the same problem on my phone

Galaxy S5 Tapatalk
[Samsung Galaxy S 5 Unified Development] TiVa:
Pretty sure it's hardware, so too bad... It get's worse too. My screen won't turn on sometimes while the softkeys are. I can see a flash and then dark again. Don't have warranty either so i ordered me a OnePlus 3. Did want to try a new battery first but didn't found anybody to test it with.

I did recompiled the framework-res.apk of sundays nightly so that brightness can't go under 20 and added a custom quicktoggle to launch a dark transparant layer with tasker to darken the screen when at night and in bed. Perfect way to pass the Next 5 weeks before the OP3 arives...
[Samsung Galaxy S 5 Unified Development] SuperSandro2000:
Had the same problem. I did a repair three months ago with tripped Knox. If you still have warranty repair it asap but flash stock via Odin first.
[Samsung Galaxy S 5 Unified Development] TiVa:
Don't have waranty anymore... But thanks for the advice
[Samsung Galaxy S 5 Unified Development] aguarello:
I'm having this issue as well, as soon as I flashed the ROM. I just flashed and started using CM for the first time and this haven't EVER happened before. I've been on stock Android since I bought this phone and as I said, never had any problems, so I think there's a chance that this is not hardware related. Any thoughts?
[Samsung Galaxy S 5 Unified Development] TiVa:
Really doubt it. I restored a nandroid from a Touchwiz rom, factory reset, clean install,... and still had the issue.

I think it's just coincidence on your part. My rom worked nice for months when this flickering suddenly started.
[Samsung Galaxy S 5 Unified Development] Bryanx86:
Maybe we all flashed the screen to death, lol, mine does it on Phoenix ROM but hasn't done it on cm, even at lowest brightness setting. Getting two years out of a phone and development still going strong I can't complain at all.:svetius:
[Samsung Galaxy S 5 Unified Development] oia12344321:
I also have flickering, only bottom + some yellow horizontall bars on low brithgness. I use "velis auto brightness" to keep my brightness over 20...**** amoled screens...they burn in...damage over 1 and half year...is ****
[Samsung Galaxy S 5 Unified Development] javelinanddart:
To all having brightness issues, we raised the min brightness from 2 to 10, both for manual brightness and auto brightness, this change should be present in the next nightly

We do not have the issue, so it's hard for us to investigate it :/
[Samsung Galaxy S 5 Unified Development] rayzen6:
Wow bro ur in JDC team r8?? Wow nice to see you here. I remember my old days with i9505. Still i9505 is champ with JDC team.
[Samsung Galaxy S 5 Unified Development] TiVa:
Thanks for this! As stated, I really don't think you guys should investigate. I restored an nandroid of Alliance Rom and when I never had issues on that ROM the flickering returned when restoring the rom and I did a full wipe before restoring it. It can't be kernel too, because on Alliance Rom I was still using stock kernel... I really think that the S5 has a screen issue. If you google about it, a lot of people are complaining, and I really doubt they are flashers...

I hope the technology improved these last years and my One Plus 3 won't get this issue...
[Samsung Galaxy S 5 Unified Development] ScratMan38:
NOOOOOOOOOO !!!!!!! :crying: :crying: :crying:

10 is much too bright while in the dark ! :(

Forcing everybody to have a brighter screen to workaround a hardware issue faced by a few is not a solution.

CM was so nice in the dark with its low minimum brightness compared to stock...

Or at least please provide a setting so that user can choose the minimum brightness he wants.
[Samsung Galaxy S 5 Unified Development] htb2050:
Get the app midnight in playstore. It provides a best of its kind filter during the night. This current brightness was still too bright for me so I always used that to further reduce the white light while using the phone during night.
[Samsung Galaxy S 5 Unified Development] htb2050:
Guys any one using adoptable storage on this Rom? How is it working? And also during rom updates does it stay that way or does it cause any issues? Also if I have adoptable storage on the rom and then do a dirty flash on another cm13 based rom and restore my apps then would it read the data of the previous rom like it currently does?
[Samsung Galaxy S 5 Unified Development] ScratMan38:
I already used this kind of app in the past, and it's not user friendly at all. First, some are not free, and it adds some notifications and often require user intervention to correctly adjust the brightness.

Having a system that correctly handles the brightness like CM with auto brightness down to 2 and Live Display on automatic is a much better solution.
[Samsung Galaxy S 5 Unified Development] htb2050:
Check out this blog by a guy running s5 some great tutorials in there. https://jdrch.wordpress.com/
[Samsung Galaxy S 5 Unified Development] Bluefreak1988:
Hey!

I heard about the actual Cm13 version. I used it months before but I moved back to CM12.1 because the bluetooth connected to my car radio for media connection, but not for headset conenction.

Now I did a clean flash from 12.1 to the actual ZNH5YAO0J4-klte, but I still have the same problem:

Bluetooth media possible - Bluetooth phone calls impossible.

Is there any fix outside, that I didn't find?

I tryed "BT Music", which works great for Galaxy S4, but It didn't solve my problem.

I really would like to use CM13, but headset functionality is mandatory.

Can somebody help here? Thank you!!!

Phone: Samsung Galaxy S5 G900F - klte

Car HiFi: JVC KD-R871BT

Rom: CM 13 ZNH5YAO0J4-klte

Kernel: CM 13 - 3.4.0-gab6c9c7

Baseband: G900FXXU1BOL3
[Samsung Galaxy S 5 Unified Development] phalkon30:
What date rom did you try, something recently? Bluetooth works great for me on all 3 headsets, both speakers, and over 15 cars of all brands that I've tried. Both calls and music.

It really should be working for you

Sent from my SM-G900R4 (klteusc) running CM13 9.12.16 with xposed
[Samsung Galaxy S 5 Unified Development] Bluefreak1988:
I tried 13.0-20160820.

It really should, I'm desperate...
[Samsung Galaxy S 5 Unified Development] ScratMan38:
Connect to your car, and check in the parameters of your BT peripheral that it is enabled for both call and media.
[Samsung Galaxy S 5 Unified Development] Bluefreak1988:
I tried! should work, but it doesn't . With CM12.1 it works perfectly!

Both enabled - media and phone! =(
[Samsung Galaxy S 5 Unified Development] TiVa:
I do the same with tasker. I force a black 80% transparency overlay on my screen. Added a custom quicktoggle to activate it: the night filter one. It's the best I could come up with... Anyway. If you are suffering from this start looking for a repair or another phone. It will get so bad your screen won't turn on everytime when you try to turn it on. I guess it's because of the dimming that happens when you turn off/on your screen...
[Samsung Galaxy S 5 Unified Development] javelinanddart:
It is COMMON to work around HW issues with SW, just look at the linux kernel.

As opposed to this solution, do you have a better one to filter this change for users who are having hw issues?

Also, if you're using your phone at night, another solution, as opposed to using an app, is to reduce the color intensity in settings across all colors and that will dim your screen as well
[Samsung Galaxy S 5 Unified Development] :
Isn't it strange to assume that 50 or so people all of sudden began having hardware issues? It's more likely than not that the flickering issues are software related, because many stated that screen dimming worked just fine on TouchWiz. Apart from that, maintainers mentioned a patch set that may have been responsible for the issue: https://review.cyanogenmod.org/#/c/163854