yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] javelinanddart:
Actually, plenty said that screen brightness was broken on TW too, but TW could also have a higher min brightness than CM.

It's not even necessarily sudden, but a lot of people buy the phone at release time, and their amoled's would've degraded since then based on their usage (so even users who bought it later but used it heavier could experience the issue) and how long they've had it, so it does make sense that it's happening around now, ~2.5 years from the initial release date, around the time most average consumers get new phones

Also, that is my patch set to fix it, so i'm not sure why you linked that :/
[Samsung Galaxy S 5 Unified Development] :
I'd assume that the patch was hacked to work. Nothing against you or your abilities as a developer, but I think that's not the root cause of it. I was trying to say that it's highly unlikely that ~50 people who never had hardware related issues started having them within last week or so. My father has an S5 too and I'd be willing to test the latest version of RR on his phone to see if it would flicker.
[Samsung Galaxy S 5 Unified Development] javelinanddart:
Yeah more data is always helpful to have, that'd be much appreciated.

It's hard to track down when it started because if it's happening on other roms or even TW (like a few mentioned) then it's not a bug with the ROM so people don't mention it.

I do agree that it's probably not the root cause, the brightness being too low, but I'm trying to treat the symptoms here, and since I ofc do not experience this issue, it's tough to track down.

I do have a sneaking suspicion that the issue has to do with PWM (something out of the user's control when they flash) but I'll have to see if I can dig into the code and change it, but even then, I still have no way to test it myself, and could introduce other issues. This was the most logical approach (imo) because all it does is raise the min brightness and it's very unlikely to cause bugs.
[Samsung Galaxy S 5 Unified Development] rayzen6:
I agree with u. never had any issue like this. Keep the gr8 work :good:
[Samsung Galaxy S 5 Unified Development] TiVa:
I can only speak for myself, but like I said, I also experience this issue when I reverted back to a TW based roms (also roms that can lower the brightness below the standard, I have to admit)...

But serious now, check this link: https://www.youtube.com/results?search_query=samsung+s5+flickering+screen

You'll find a lot of videos that have the same problem and in all videos the user is running TW.

50 people will be an understatement... I just asked to add a setting where I could change the minimum brightness so I didn't had to recompile framework-res everytime. Maybe I should open up a topic outside this topic to discuss this flickering, because I strongly believe this screen flickering is not CM related... But I do want to thank the dev team to try to fix HW issues with SW!
[Samsung Galaxy S 5 Unified Development] Qawnman:
No screen flickering issues here.

Bummer we all have to suffer with brighter screens at night now.

Maybe add an option in developer settings?
[Samsung Galaxy S 5 Unified Development] oia12344321:
We had flickering issue also on TW...but use programas like velis, lux to keep minimun brightness up...so is not an sw issue...is just the stupid amoled screen...ips a lot better (maybe not in black, but not that imoporant)...you will have too in future

But an option to choose minimum brithgness would be great :) all people would be happy
[Samsung Galaxy S 5 Unified Development] phalkon30:
If you're desperate, try upgrading to the latest nightly, there were Bluetooth fixes recently, I don't remember if before or after that date though. I'd guess it's your specific head unit if the latest nightly doesn't work since nobody else on a recent rom has the issue

Sent from my SM-G900R4 (klteusc) running CM13 9.12.16 with xposed
[Samsung Galaxy S 5 Unified Development] omgbossis21:
I'm not a big fan of the brighter screen either since I dont have the flicker. I may just continue to compile my own using the lower brightness. I planned to do some test builds for some camera mods Im toying with so I'll likely sync up and push back the dimmer values when I do.
[Samsung Galaxy S 5 Unified Development] Bryanx86:
If the brightness is that big an issue for you, just don't flash nightly past 9/27. This ROM is pretty much masterpiece without needing to flash a newer nightly.

---------- Post added at 07:28 PM ---------- Previous post was at 07:27 PM ----------

It would be great if you could get the s5 stock camera working in your unofficial build. Share if you can.:svetius:
[Samsung Galaxy S 5 Unified Development] omgbossis21:
There will be no stock camera app in cm, I'm trying to improve the picture quality of our existing cm camera.
[Samsung Galaxy S 5 Unified Development] Bryanx86:
Yea, I don't even think it would be possible without porting alot of TouchWiz framework to cm, which would really increase bugs. That is the only thing about stock that I like is the camera, really happy with cm. Thanks for your response. Hope you're able to upgrade cm cam.
[Samsung Galaxy S 5 Unified Development] Triviox:
Can in CM13 use heart /pulse sensor in S5? I installed S Health but cant find a way to use it :/

Thanks!
[Samsung Galaxy S 5 Unified Development] oia12344321:
Yes install healthservice.apk as normal apk (first open s health and than install it)

I also asked that few post back and someone answered me...credits to that good guy :))

https://mega.nz/#!E8Ex2R6a!vjLpYADk5CysfgRKN0jr1L3Tlbxnji6q4p39uutK3x8
[Samsung Galaxy S 5 Unified Development] Triviox:
Works!! i did try a similar apk before, but DIDNT OPEN S HEALTH FIRST (my mistake!)..

Thanks bro!!! :good:
[Samsung Galaxy S 5 Unified Development] zazolo:
hi everybody, I have my s5 which is showing its age

sometimes phone becomes unbelievably slow, apps stop working, reboots....

I'd like to try CM 13, but I read here and there of unrealiable bluetooth, low audio quality and volume..

I use bluetooth for garmin sportwatch sync, audio headsets, portable speakers, gopro and other cameras a lot. Do you know if these problems have been solved?

secondary feature I use a lot is peel smart remote, but seems to work (as I read a few posts before)

what do you think? If possible I'd like to get rid of stock rom (is space consuming, seems to eat MB without reason)

Is CM13 good for me or bluetooth is still an issue?
[Samsung Galaxy S 5 Unified Development] phalkon30:
Only one person (previous page) in the last month has had a significant bluetooth issue that I have seen. I use it every day on multiple devices, Bluetooth is flawless.

No idea on peel personally.

This phone flies on cm, it feels like it keeps up with anything out there outside of camera quality

Sent from my SM-G900R4 (klteusc) running CM13 9.12.16 with xposed
[Samsung Galaxy S 5 Unified Development] aguarello:
Guys can someone please guide me through the steps of updating the ROM from a snapshot to a newer one? I'm kinda new with CM so it would be really nice if you guys could help me out...

First, so I just need to flash the new firmware through recovery? (no wipe data necessary, right?) Do I need to reflash GAPPS as well? Do I need to flash Xposed again? (yes, I'm using Xposed)

And secondly, can I just use the inside the ROM updater that searches for the newest version of the ROM? Or is it better if I just manually download it and flash it through TWRP?

Thanks guys! I'm really enjoying this ROM, my phone feels like a new one since I installed it! :svetius: :)
[Samsung Galaxy S 5 Unified Development] phalkon30:
Doubt it's the only way, but here's what I do:

1. Download latest version through cm Downloader

2. Reboot into recovery

3. Wipe system, dalvik, cache

4. Install rom, gapps, and xposed in one shot through twrp

Has worked every time for me

Sent from my SM-G900R4 (klteusc) running CM13 9.12.16 with xposed
[Samsung Galaxy S 5 Unified Development] ScratMan38:
For HW issues faced by all users, yes, not to fix HW issues faced by 0.1% of the users of a device.

That would request user interaction everytime, so no, not an option.

True, this flickering issue is HW issue, users facing it should ask for a HW repair.

I used stock Touchwiz, and I can confirm lowest brightness is much higher than in CM when brightness is set to auto. That was one of the reason I came back to CM.

And what when there will be a big improvement somewhere in the code ? like power management or camera ? the day will come I will have to flash a newer nightly, and then ?

Low brightness in CM is a feature, that benefits from the AMOLED screen and its low power consumption when screen is dark.

In the past, there was an option in CMxx for the user to adjust the minimum brightness, but they removed it (maybe because some users set it to 0, making the screen black). Maybe it's time to put it back, with a limit at 2 by default.

And anyway, for those few requiring a higher brightness due to flickering, they can use the third party apps ; and at least it would not force everybody to have high brightness.
[Samsung Galaxy S 5 Unified Development] :
Here's an update on the situation:

I've tested AICP, Resurrection Remix (both official and unofficial builds), SlimROM and I've concluded that the flickering on my S5 is definitely hardware related. The builds I've tested were either 21.09. or 23.09. because those are the last builds that I didn't get flickering on. At this point, I'm not sure which part of the hardware is responsible for it. I've had similar issues on my S3 in the past and after I've bought a new battery (the old one had oxidized connectors and that's one of main causes of battery degradation and flickering issues) it worked perfectly. I'll edit this post tomorrow, when I find out if the battery is the cause of it (at least in my case).

Edit: I've just tested a new battery and I can say that the flickering issues are definitely display related, at least in my case. I encourage everyone to test a brand new battery to see what's the cause of flickering issues on their phones.
[Samsung Galaxy S 5 Unified Development] ScratMan38:
As said by javelinanddart, the display driver uses PWM to adjust the brightness of the LEDs. Its really efficient, but the issue is that it generates high current consumption peaks on the battery. So if the battery becomes weak, its internal resistance will increase, and the voltage seen by the driver will drop during the pulses ; and these drops can strongly disturb the driver.

You may try to play with an option in the "Live Display" settings, there is a "Reduce power consumption" option, I can see the screen becomes slightly dimmer when enabled. Previously it was not in the "Live Display" section, but directly in the Display options. Maybe it can help you.
[Samsung Galaxy S 5 Unified Development] TiVa:
I did play around with the "Reduce Power Consumption" but that didn't help. On the interwebz you can also find suggestions to disable HW layers that also didn't help at all...

Really curious about the battery check though. I knew it was HW related, but still in doubt if it was screen related or power... My battery is getting worse every day to be honest. Google (searching the web) says it's a amoled thing to have issues on low brightness, but google also tells me to disable HW layers. Keep us posted!
[Samsung Galaxy S 5 Unified Development] ScratMan38:
[MENTION=2693412]haggertk[/MENTION], [MENTION=7518817]cal002[/MENTION] and [MENTION=5341181]omgbossis21[/MENTION], I'm coming back to you with the RIL restart issue I'm facing since several monthes, making network disconnects every 12 minutes.

I made some trials with different modems and bootloaders, playing with APN settings for my service provider (Orange France, FTM), and I've found something new.

First, let me remind you the issue :

So playing with the APN didn't help. It worked for one day, and then the issue started again.

However, when forcing the network to 3G instead of the "recommended" LTE in the network type, there are no more disconnect. The network then becomes rock solid, but slower...

I tried to install stock Touchwiz ROM, and use it for (much too long) 15 days, and with LTE I had no disconnect. So it looks like there is something wrong in the RIL from CM13 with my provider (I never faced this issue with CM12.1, and it was not present with the first unofficial CM13 builds from Albinoman).

I know my service provider now supports VoLTE, and on CM13, when I make or receive a call while connected on a LTE network, I can see the phone looses the network connection after the end of the call. This doesn't occur on TW 6.0 ROM. Is there a parameter I need to set in order to allow CM support VoLTE ?

May one of you have an idea or suggestions so that I can debug this issue and make my LTE work correctly ?

Thanks a lot

---------- Post added at 04:48 PM ---------- Previous post was at 04:45 PM ----------

This kind of issue only appears on AMOLED because LCD are not able to dim their backlight to such low levels.
[Samsung Galaxy S 5 Unified Development] TiVa:
Also want to point out my phone does it too when charging, don't know if this change anything in PowerManagement...
[Samsung Galaxy S 5 Unified Development] omgbossis21:
Dont believe cm supports volte at all unless I missed it being added in? My phone still does it yet if I switch to 2g I connect just fine at home. Its when I leave it LTE preffered its a constant on to emergency connection all night. I had originally wrote it off to the fact that I'm sim unlocked on a T-Mobile device using net10 as my carrier who run off at&t. I'm also still using a T-Mobile WiFi calling router which I figured further confused it lol. I got my virtualbox back up last night, it crashed after switching around some display connections. I will log and see if I'm simply not switching from LTE to 2 or 3g or resetting radio like yours.
[Samsung Galaxy S 5 Unified Development] aguarello:
Video recording on Snapchat is not working (message: video recording failed), anyone else having this issue? I'm on the latest snapshot... was this fixed in the new nightlies? :eek:
[Samsung Galaxy S 5 Unified Development] ScratMan38:
I'm personally on a Orange branded phone, don't know if it's SIM locked or not, as I'm on Orange network.

I even flashed the latest modem from latest Orange Touchwiz ROM, but still same issue with LTE.
[Samsung Galaxy S 5 Unified Development] konichwa:
I never did respond about my weird issues with my android after recent updates since 9/10, i backed everything up (praise titanium backup pro), cleared everything 3x times, ran the clean install, and everything seems to be working great.

Now onto dirty flash of 9/27 . Lol

Thanks!
[Samsung Galaxy S 5 Unified Development] Disabledish:
It is working the real sensor? Or the flash led? I have the same problem. Sensor didn't work.. And I don't know what to do :(

Wysłane z mojego SM-G900T przy użyciu Tapatalka
[Samsung Galaxy S 5 Unified Development] Triviox:
The real sensor =)
[Samsung Galaxy S 5 Unified Development] phalkon30:
I assumed it was snapchats fault, but I have the same issue. Saw this fix posted for ghost (moto x) with people saying it fixes the problem but I haven't tried it yet.

Edit this line in the Build.prop file (better with Root Explorer) and then, reboot the device:

persist.audio.handset.mic.type=digital --> replace digital with analog

Sent from my SM-G900R4 (klteusc) running CM13 9.12.16 with xposed
[Samsung Galaxy S 5 Unified Development] rayzen6:
[MENTION=2693412]haggertk[/MENTION] and other devs working for klte.

Just wanna say thank you for ur hard work. Currently using aicp-n build based on cm14 by u guys. Its really awesome for a first nougat build. All is playing nice. Just a in call voice delay of 5-6 seconds and mobile data I think that too will solve eventually. And other minor bugs which I think are cm specific. Its really good I mean . its awesome. No random reboots or freezes etc. Also battery life seems as good as cm13. Deepsleep playing nice too.

I just want to say a big thank you to all who worked together to bring device for nougat. Tysm. :)
[Samsung Galaxy S 5 Unified Development] cal002:
Maybe you're not patient enough? It can take up to 30 seconds for the first measurement to complete.

I used Sensors Sendbox app from f-droid. When you put your finger on the sensor a red LED should light up when it's working.
[Samsung Galaxy S 5 Unified Development] Disabledish:
Maybe it is not working for me because I have 900t version of s5? Every app to measure just flash the led..

Edit. Ok I check the sensors sandbox and the sensor is working. When I touch it, it is flash ;) but it is not working in any application..
[Samsung Galaxy S 5 Unified Development] mmtrt:
[MENTION=1979346]phalkon30[/MENTION] that line don't exist in RR mm build.prop so tried added with digital and analog didn't do anything same error so I removed that line.

Solution: Its app fault or CM, Workaround is just Simple install older version of app [Snapchat 9.36.5.0] working fine and never update util this problem is fixed or will not be fixed IDK.
[Samsung Galaxy S 5 Unified Development] :
I've edited my post, but it didn't get bumped to the last page, so here's what I wrote:

Edit: I've just tested a new battery and I can say that the flickering issues are definitely display related, at least in my case. I encourage everyone to test a brand new battery to see what's the cause of flickering issues on their phones.
[Samsung Galaxy S 5 Unified Development] TiVa:
I was afraid it was screen related... I ordered a new phone so not gonna throw away money on a new battery...

I really hope the amoled that are fabricated today are better then 2-3 years ago...
[Samsung Galaxy S 5 Unified Development] airidosas252:
Every technology has it's limitations, plus it's harder to calibrate an amoled panel. And, flickering issue is not existant on my s5.
[Samsung Galaxy S 5 Unified Development] phalkon30:
Thanks for trying!

I also can't write text on landscape pictures in recent versions, maybe the old app will help that too.

Sent from my SM-G900R4 (klteusc) running CM13 9.12.16 with xposed
[Samsung Galaxy S 5 Unified Development] jeremiah.rs:
Does anyone know where I can find which MM blobs were merged into the kltespr releases?

I want to see which baseband I should stay on/upgrade to before reinstalling CM13 on my phone.

Thanks!
[Samsung Galaxy S 5 Unified Development] aguarello:
I've been doing some research and I think this definitely has to do with an incompatibility of CM camera API and (newest versions of) Snapchat. This is totally up to CM devs to fix. I highly doubt Snapchat devs will do anything to help us, they've never liked custom ROMS or system modifications, so we probably won't be getting support from them.
[Samsung Galaxy S 5 Unified Development] mmtrt:
I'm just testing alpha build of aicp n rom so Snapchat latest version is working fine there atm, this could be already fixed for cm14.
[Samsung Galaxy S 5 Unified Development] TEFjLONjDON:
Is there a link to alpha aicp N rom for klte?
[Samsung Galaxy S 5 Unified Development] Bryanx86:
Really off topic, but here https://www.androidfilehost.com/?fid=312968873555002281 Sorry for OT
[Samsung Galaxy S 5 Unified Development] TEFjLONjDON:
Greatly appreciated. Hope to post more relevant content here after install and testing. Thank u and other devs /testers for all work here.

---------- Post added at 13:49 ---------- Previous post was at 13:47 ----------

404 not found

Can't find it!

Seems like that URL doesn't exist. Or at least we can't seem to find it. We've even looked under the seat cushions and zip, nada, nothing.

back to top

?
[Samsung Galaxy S 5 Unified Development] Blackjubel:
https://www.androidfilehost.com/?fid=312968873555002281
[Samsung Galaxy S 5 Unified Development] Bryanx86:
It was because of the period behind the title, changed it now but i see someone else posted
[Samsung Galaxy S 5 Unified Development] TEFjLONjDON:
Well, I'm loving this AICP build so far.. Aww how I've missed AOSP.

I haven't noticed any bugs but......

I can't get my APN setting right... MetroPCS or T-Mobile for SM-G900T1 or SM-G900T.

or maybe it's because of the modem that gets flashed with the build.

Once I can get a cellular connection I will test further. Any body know if this is a radio issue caused by the modem?

PS. Bluetooth an GPS seem to work fine so far.

I'm using open GAPPS (aroma)

I flashed snap Cam for cm13 (works good.)

I can hardly wait for the release of Xposed made for sdk 24..

Today's build 100216 has fixed data and MMS just make sure APN settings are correct after.. PS I dirty flashed over 092616 version.
[Samsung Galaxy S 5 Unified Development] jdrch:
Is Play Services crashing for anyone else on the 20161002 build? Logcat is attached.
[Samsung Galaxy S 5 Unified Development] TEFjLONjDON:
It did for me too the first three attempts. I just flashed aroma with complete install only options I set was to not remove stock apps.

Wipe all partitions except sd and USB then reflash both also maybe try diff Gapps as long as it's for 7.0 sdk24
[Samsung Galaxy S 5 Unified Development] jdrch:
Aroma? What is that?

Also my intention is to not have to reinstall & setup from scratch (I do have a nandroid backup of the most recently working build though), so if anyone has any idea how to facilitate that, I'd appreciate it.
[Samsung Galaxy S 5 Unified Development] ScratMan38:
Hope this commit will be merged soon https://review.cyanogenmod.org/#/c/164226/
[Samsung Galaxy S 5 Unified Development] TEFjLONjDON:
https://goo.gl/photos/af39KJKgr1KQVaQ19[IMG="open gapps aroma download link"]https://goo.gl/photos/af39KJKgr1KQVaQ19[/IMG]
[Samsung Galaxy S 5 Unified Development] TEFjLONjDON:
OpenGapps project aroma installer package.

PS advice.

Restore nandoid backup. Retry dirty flash. Reboot system. If not successful reboot to recovery again make wipe all partitions except sd and USB then flash clean. Then flash Gapps if desired and setup from scratch.
[Samsung Galaxy S 5 Unified Development] jdrch:
Yeah I have 128 apps on my phone and it takes 3 days (since I have a day job) to set it up from scratch. Avoiding that is the entire reason I made a Nandroid backup so I'm doing it.

Any other solutions or ideas? Otherwise I'll probably just wait until next weekend to check for an update again as it seems most of the builds lately are borked to hell. I think I've had less than 10 builds run or update properly in the last 40 days. The previous issue was builds bootlooping. Pretty frustrating.
[Samsung Galaxy S 5 Unified Development] shirioko:
Deleted. Need coffee.
[Samsung Galaxy S 5 Unified Development] furkaan28:
Wrong thread
[Samsung Galaxy S 5 Unified Development] Atento:
Is there a thread for this rom?

EDIT: found it. Sorry for OT
[Samsung Galaxy S 5 Unified Development] boind:
Hey Guys,

i am trying to clean flash 20160927-NIGHTLY on my G900F. I am using TWRP3.0.2-2. Sadly i get stuck at "patching system image unconditionally...". Any ideas?
[Samsung Galaxy S 5 Unified Development] ikzouhetnietweten:
from 100 to 91 % battery when Im asleep (8 hours), thats not normal. My S3 was only to 98. I have the Boeffla kernel 3.2 beta CM. I have the most basic of basic, uninstalled even Email stock and music. and greenified apps/systemapps. I have g900FXXU1CPC9

Guess I will try another Rom and sleep a night and see if it's better.
[Samsung Galaxy S 5 Unified Development] ikzouhetnietweten:
allright, battery is just 1,5 yr old though. ll try the Alexander Rom and see what it comes up with tomorrow. :)
[Samsung Galaxy S 5 Unified Development] boind:
Is it a good idea to flash the newest stock-rom from sam-mobile and then cm? Or am I getting trouble with the bootloader then?
[Samsung Galaxy S 5 Unified Development] darksx:
That's too much,i lose maybe 1% over night,battery 1 year old without any tweaks,custom kernels etc.Just pure CM13:D