yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] Saber:
See this reddit post: https://www.reddit.com/r/LineageOS/...g_8_may_asb_jelly_donations_and_more/dh2f1vw/

Official lineage changelog: https://www.lineageos.org/Changelog-8/

Gello will remain the same on devices that currently have it, except that it will be updated with a newer chromium build. ;)
[Samsung Galaxy S 5 Unified Development] finotti:
Okay, I had replied saying I didn't have this problem, but I do. I just didn't try the "more" when sharing.
[Samsung Galaxy S 5 Unified Development] curiousde2002:
Hi everybody,

my G900F presently is on Alexndr's ROM, Version CQAV, Android 6.01 with exposed.

Now I want to upgrade to a nougat ROM and would like to ask a few questions:

Can anybody confirm that the camera is worse on lineage ROM than on stock ROM, as I read this somewhere ?

Would I have to flash bootloader and modem also (via Odin) as Alexndr always recommends to update these too when upgrading (My current Baseband Version G900FAXX1CQAV, Bootloader and CSC are G900FXXS1CQAV) ?

What is the difference between unofficial and official Lineage ROMs?

In some Hotel WiFis my connection frequently gets interrupted and reconnected again, only a problem when making calls like via WhatsApp or Viber, but still annoying.

I blame this on Marshmallow.

So any issues like this on Lineage OS 14.1 ?

Thank you very much in advance!
[Samsung Galaxy S 5 Unified Development] SuperSandro2000:
Camera is about the same. Use the one that comes shipped with the ROM or snap from playstore (or a comparable).

As long as you have a somewhat recent modem and baseband it should work. I think anything pre lolipop or marshmallow does not work. Not sure there as I always run the latest with not problems. If you use now a lolipop modem and you update to marshmallow you need to update your twrp or it does not work.

Unofficial are just builds by haggertk (hope got the name right). They are identical to official ones and are build for testing specific features/bugs or just when there were no official CM/los 14 builds. Just download from lineage and keep an eye on this thread.

Never got WiFi issues in hotels but the wifi in German hotels is mostly to crappy for that. (Or I stay in to crappy hotels) I normaly use "normal" calls for that.

Page 666. We should be careful. ?

Edit: sometimes I have WiFi drops at home with WhatsApp calling. Sometimes every hour and sometimes I can phone for 3 house straight. Don't know what causes it or how to fix it and never tested it on tw. Using cm since day 2.
[Samsung Galaxy S 5 Unified Development] iggysamsung:
I have a problem to counter the length of calls, because it starts counting from the moment when I call someone, not when the connection is established. Phone is G900FD.
[Samsung Galaxy S 5 Unified Development] 4rz0:
You'll have to add that there's currently no way to record 4k or slow-motion and that the S5's native fast HDR isn't supported.
[Samsung Galaxy S 5 Unified Development] SuperSandro2000:
HDR is supported and the s5 overheats anyway with 4k after a few secs.
[Samsung Galaxy S 5 Unified Development] curiousde2002:
Thanks for quick reply!

At home I never have these WiFi drops in the 2.4GHz, sometimes in the 5GHz.

What about 3rd party apps writing to external SD card?

Does it work or is there a workaround for that?

What about performance?
[Samsung Galaxy S 5 Unified Development] SuperSandro2000:
If they were updated since KitKat then it works. There are a few workarounds around but I personally don't use them. Performance is very good.
[Samsung Galaxy S 5 Unified Development] DragonQ:
Update to the GPS issue:

So far, the following workaround has a 100% success rate (after maybe 10 tries):

- Enable GPS

- Start "GPS Status & Toolbox" app

- Wait for it to lock onto satellites (can take 30-60 seconds)

- Open Google Maps and continue as normal

It's very annoying to have to wait that long and start the app manually but it works. I'm still open to ways of investigating the problem - can I use adb to find out what it's doing at all? The "GPS Status & Toolbox" app has the same issue as Google Maps in that it keeps dropping and re-searching but, unlike Google Maps, it eventually does get a stable lock for some reason.
[Samsung Galaxy S 5 Unified Development] sikhad:
Verizon g900v here on QB2 baseband, running May 3rd nightly.

Overall pretty good experience but a few builds ago I also lost fingerprint hardware support, updating LOS didn't solve the problem. Cellular radio also seems finicky - sometimes it will switch from 4g to 3g for seemingly no reason (coverage is good), and will get stuck until I turn airplane mode on/off quickly. I'd like to try the QA1 baseband to see if this fixes the problems, but I can't seem to find it. Any pointers? Should I ignore the baseband version and just clean install LOS?
[Samsung Galaxy S 5 Unified Development] 3mbedded:
Please address user's bugs and crashes

I greatly appreciate the author's effort in making the LOS builds available to us. I do wish some of the bugs users have reported here would be answered.

I have tried LineageOS on 3 devices: Samsung S2, Nexus 6 and the Samsung S5. I have to say, the builds for the S5 are the most unstable and buggy.

1. Since installing LOS on the beginning of April, I had 3 instances where the phone froze and I had to pull out the battery. All buttons would become unresponsive and would be stuck at the lock screen (either with screen on or screen doesn't turn on).

2. Web browser constantly crashes. Even basic web pages will crash the browser.

3. Photo editor is very buggy. Rotation is wrong, crashes when saving an edited picture sometimes.

4. Camera app on the LOS builds of the S2 and Nexus 6 have more filter options and shooting modes available that are severly lacking on the S5 build.

5. Yesterday, the phone screen would keep coming back on the lock screen after I checked for notifications so I had to manually power off.

6. When someone hangs up the phone, 3 strange beep noises are heard. Why do the other LOS builds not have this issue?

However, I will say I love the fast speed the S5 LOS build and it boots even faster than the Nexus 6 LOS build.
[Samsung Galaxy S 5 Unified Development] Dieexe:
What the hell? Camera is like twenty times worse
[Samsung Galaxy S 5 Unified Development] SuperSandro2000:
Processing is worse... But honestly it is worth. TW is crap
[Samsung Galaxy S 5 Unified Development] nwn9:
Installed it few days ago and everything seemed to be fine. Yet calling doesn't work - every time I answer a call, the microphone goes dead and both me and the person on the other side can't hear a thing. Also, there's no sound indicating that a call has been going. I also learned that microphone doesn't work at all - in calling, in recording sound and in voice conversations through Skype, Signal or other messaging app.
[Samsung Galaxy S 5 Unified Development] Dieexe:
Everything is worse*
[Samsung Galaxy S 5 Unified Development] pieceofphil:
What is wrong with you? Don't clutter this thread with a discussion about camera.

This discussion is as old as custom ROMs and has been the same on Xperia phones and even on the oneplus 3 the camera of the custom ROMs don't get near the quality of official ROM and that is one of the developer friendliest phones out there.

What I want to tell you, camera is one of these aspects that have never and most likely will never be as good on a custom ROM as on stock. Not because the developers don't want to but because it is half way impossible to implement such thing in a legal and functioning way.
[Samsung Galaxy S 5 Unified Development] Dieexe:
So what? I'm just telling the truth, not complaining or something like that. You're saying that camera is only a little bit worse when it's sooooo much worse
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
As long as Samsung keeps the source unpublished, no one will be able to make this camera better on our aosp roms. We are all helpless. So, no need to fight... Go back to TW ROMs, if camera is too essential...
[Samsung Galaxy S 5 Unified Development] J-Lindo:
I'm on the G900V too. I'm also on the QB2 baseband, but according to https://xdaforums.com/verizon-galaxy-s5/general/update-qc2-t3589413, there's a new QC2 update (the OP also has a link to his compilation of past updates).

On another note, I'm on the May 3rd build, and I'm having microphone issues too. When making an outgoing call, it wouldn't work (the two times I tried, anyways), but it went through when the other person called me. Also, Google Voice search didn't pick anything up from me. Bluetooth microphones (like in my car), however, works fine. I hope that's helpful in figuring out the issue. Otherwise, I love this build. Lineage just keeps on improving!

Edit: Well, I had microphone issues at first, but I can't seem to make them come back.
[Samsung Galaxy S 5 Unified Development] omgbossis21:
Thankfully I don't use my camera much. When I do I tend to take the same picture several times before it produces a usable image. The camera has issues focusing in lower light but outside seems decent enough.
[Samsung Galaxy S 5 Unified Development] E_Ben:
I am using an automagic (labview style tasker alternative) script for starting GPS Status & toolbox along witg apps using GPS. I think alternatively, GPS s&t has a setting to start it automatically along with GPS
[Samsung Galaxy S 5 Unified Development] DragonQ:
This isn't new; CM13 on my Galaxy S5 randomly rebooted every now and then, and my girlfriend's Galaxy S4 has battery usage issues ("Android OS" using way too much sometimes). Honestly LOS 14.1 is more stable for me than CM13 ever was but I'm sure there are still stability problems.

Never used it, just install a proper browser rather than use the built-in one.

Yeah I've noticed that photos display in the wrong orientation as well.

This has been the case for a while, sadly. I can't even see a way to get the flash toggle as an option on the main screen. The quality is also bad; I've tried two third party apps and they take much better photos for whatever reason (no it's not a filter effect).

I've had this too, it kept happening in the car when there was movement. Haven't found a way to disable it yet. :(

Haven't heard this before.
[Samsung Galaxy S 5 Unified Development] giatros:
There is no feature for USB reverse tethering... (the "USB Internet" option in settings). Am I missing something? Is that planned at all?
[Samsung Galaxy S 5 Unified Development] fitittome:
Did you see this? https://xdaforums.com/u/best-apps/app-reversetethering-noroot-t3316716
[Samsung Galaxy S 5 Unified Development] nictabor:
I second this. I also commented about the phone seeming to freeze a few days ago, but it wasn't until yesterday that I realized that the phone was actually powering off. The only way to get it back on is to either pull the battery or plug it in to charge.

I tried to wipe the phone and revert to the kltevzw build from 3/22 (I think, at any rate the last made) but TWRP won't allow me to install a version older than 3/31. I'm not sure if it is because I am using the modified version of TWRP [MENTION=2693412]haggertk[/MENTION] made or what. Anyone have any actual advice?? I also want to point out, especially for the "... I don't have those problems ... " people that I did not have any of these issues before changing from kltevzw to klte. Also, I have done a full wipe and fresh install on klte to make sure that there was no lingering garbage which was in conflict.
[Samsung Galaxy S 5 Unified Development] giatros:
Thanks! Yes, I am aware of this app (I haven't tested it on LineageOS).

There is a superior third party solution - an app called Simple-RT. The problem is both apps require a computer side server application to run, for a feature that can work without one...
[Samsung Galaxy S 5 Unified Development] jmlrbnsn:
Did you get an answer

I have very similar issue with Resurrection Remix. Installation went very smooth. All clean flash. Will not recognize SIM card. Was thinking of trying Linage bit seems to have same issue with Sprint
[Samsung Galaxy S 5 Unified Development] godofsalt:
Hey there, Am on The same phone. Here is my 2 cents...

Goto settings, and on top of the page press the "more..." link, you both, might want to check not only have the LTE ( which is recommended) and not 3g. If if already on LTE at boot, change it to 3G for a few minutes.... Then go back and switch it back to the recommended LTE... Might help.

Also while there in " more" network services take a second and double check that your on the correct "Access Points" again switch this to YOUR band, ( sprint, virgin, boost etc)

Hopefully this can fix your issuess.

Oh, if your phone was set to 3G from the start, ( after clicking on LTE, and having the correct access point, a reboot can also fix the issue)

Agian, hope this helps you both out.
[Samsung Galaxy S 5 Unified Development] E_Ben:
My user certificate for WLAN gets broken each time I dirty flash a new version of LOS. Anybody else experienced that?
[Samsung Galaxy S 5 Unified Development] jmlrbnsn:
Thank you
[Samsung Galaxy S 5 Unified Development] BrX91:
Did You tried to update baseband and modem? For me that fixed the issue with GPS.

Wysłane z mojego SM-G900F przy użyciu Tapatalka
[Samsung Galaxy S 5 Unified Development] 10goto10:
[MENTION=2693412]haggertk[/MENTION] and all, I think I finally figured out one of the cause of the excessive idle battery drain compared to stock (~1.3%/hr compared to <0.5%/hr): the proximity sensor doesn't get turned off when the screen is off and the device is idling (not awake). This happens even when ambient display is off, etc. Best way to check this is to point a camera to the screen when it is off and see if a light is on near the earpiece. (The light is invisible to the human eye.)

I say this because this exact issue occured on the early CM13 nightlies, but it eventually got fixed. (I didn't follow the changelogs closely at that moment though. Sadly idle battery life got worse on CM13 after the marshmallow official source merge.)

Can anyone else confirm this? Thanks.
[Samsung Galaxy S 5 Unified Development] fitittome:
Post more info on your phone. Model, Baseband etc. It will help. ;)
[Samsung Galaxy S 5 Unified Development] 10goto10:
Phone model: SM-G900F (S5 Intl, Snapdragon 801)

Baseband: G900FXXU1CPJ1 (the one from haggertk's afh folder)

ROM version: 14.1-20170503

'Regression' happened since the last 14.1 nightly before LOS went official. Clean-flashing and putting the phone in airplane mode doesn't reduce the battery drain by much.
[Samsung Galaxy S 5 Unified Development] fitittome:
???

Settings -> About phone -> Baseband Version

mine shows: G900FXXS1CQAV

In terminal what does:-

getprop ro.bootloader

reveal? mine shows G900FXXS1CQBW

Both would appear to be later versions. I got mine from here:- https://www.androidfilehost.com/?w=files&flid=142043 when there were some fingerprint related issues a month or so ago.

Not saying it will solve the problem, but it may help.
[Samsung Galaxy S 5 Unified Development] 10goto10:
It's G900FXXS1CPLV. I didn't notice that haggertk uploaded a newer one in March! Thanks for the heads up; will report after a few days with the newer modem.

[edit: with latest modem (confirmed via settings, did the battery pull trick before flashing via odin) the proximity sensor light's still on. Maybe I'll submit a proper bug report when I have time to re-clean flash the device.]

In the meantime, see if your proximity sensor lights up even without turning on ambient display when the screen is off, I just want to confirm whether this is just my problem or if it applies to you too.
[Samsung Galaxy S 5 Unified Development] fitittome:
I did check it, with a Canon EOS 1100D and didn't 'see' that it was on. but then I started to wonder if the Canon was capable of 'seeing' IR. I'll have a little experiment later at home, I have a spare S5 there to check, if it's still a problem.
[Samsung Galaxy S 5 Unified Development] DragonQ:
I have the latest version, doesn't help. I used SamFirm to grab the latest BTU firmware and it has these versions:

AP: G900FXXS1CQD1

CSC: G900FOXA1CPJ6

CP: G900FXXS1CQAV

The CP is the same as mine, not sure what my CSC is. I don't know what version the bootloader of this file is - would it be the same as the AP version number?
[Samsung Galaxy S 5 Unified Development] darksx:
2 days on stock and i can not believe how slow it is compared to Lineage.Do i need something special to enable led notification for missed calls,for messages all is ok,because i try with led blinker from store and it's working.What to do...
[Samsung Galaxy S 5 Unified Development] 10goto10:
I know, right? :D

Btw, check under Settings > Notifications > Gear icon > Notification light. For me missed call notifications works without any setup, but I use the stock lineage dialer instead of Google's.
[Samsung Galaxy S 5 Unified Development] darksx:
Thanks for the tip.By default notifications are disabled right,and i tried every combination.really weird and i am using stock dialer,i'll try later with google dialer.

edit-i just tried with google dialer and it works-i am confused really.
[Samsung Galaxy S 5 Unified Development] fitittome:
Mine seems to work as I would have expected.
[Samsung Galaxy S 5 Unified Development] cal002:
Do you have "Proximity wake" enabled? It is in Settings -> Display -> Ambient Display, but it can be enabled independently of Ambient Display.
[Samsung Galaxy S 5 Unified Development] 10goto10:
Yeah, that's already and always been off. I guess I can live with 1.3% battery drain/hr rather than sticking with stock... As I said, I'll clean flash sometime and submit a bug report if this still happens. Just for reference, keeping the device awake for sleep tracking (only uses the lowest cpu freq and acceleration sensor) uses 1.7%/hr.
[Samsung Galaxy S 5 Unified Development] fitittome:
Have you tried Forcedoze? It seemed pretty effective to me. No doubt it will raise other issues though. These things are always a trade off.
[Samsung Galaxy S 5 Unified Development] thaidroid:
FD is great no trade off, Ive used it since MM.The only thing I've ticked in settings is "ignore lock screen timeout" .
[Samsung Galaxy S 5 Unified Development] cal002:
In adb shell you can use "dumpsys sensorservice", among the spew of data it dumps

is also a list of active sensors and who is using them. E.g if I enable Proximity wake:

Active sensors:
TMG399X Proximity Sensor (handle=0x00000005, connections=1)
Socket Buffer size = 984 events
WakeLock Status: not held
Mode : NORMAL
1 active connections
Connection Number: 0
Operating Mode: NORMAL
com.cyanogenmod.settings.device.SamsungDozeService | WakeLockRefCount 0 | uid 1000 | cache size 0 | max cache size 0
TMG399X Proximity Sensor 0x00000005 | status: active | pending flush events 0

If you get that even though Proximity wake is turned off then maybe you can check

/data/data/com.cyanogenmod.settings.device/shared_prefs/com.cyanogenmod.settings.device_preferences.xml

or clear data from Settings app.
[Samsung Galaxy S 5 Unified Development] Viveraa:
I've also checked the sensor with a camera and mine stays off when the screen is off. My S5 KLTE still has a battery loss of 1-1.7% per hour during standby and will go from 100% to 88-90% overnight. Might be Samsung in general, no clue. My stock rom standby time wasn't much better than Lineage.
[Samsung Galaxy S 5 Unified Development] 10goto10:
Thanks for the useful tip! Seems like the proximity sensor is also off on mine, even though it shows on camera. Maybe it's another sensor? I don't know... The screen is off when I did this, so is the RGB / Light sensor turning on normal?

Active sensors:
TMG399X RGB Sensor (handle=0x00000006, connections=1)
Socket Buffer size = 984 events
WakeLock Status: not held
Mode : NORMAL
1 active connections
Connection Number: 0
Operating Mode: NORMAL
com.android.server.display.AutomaticBrightnessController | WakeLockRefCount 0 | uid 1000 | cache size 0 | max cache size 0
TMG399X RGB Sensor 0x00000006 | status: active | pending flush events 0
[Samsung Galaxy S 5 Unified Development] fitittome:
FWIW. I have auto brightness switched off. And under Settings->Display I switch off Adaptive Brightness. I often see lots of logspam esp. at low light levels. So I switch it off by habit.
[Samsung Galaxy S 5 Unified Development] t_house:
I am having issues trying to update my baseband, modem, etc. using the tar file that was made by our awesome OP. My bootloader version is currently BOD5 and Baseband is DPG2. My build is that of DQA1 from Feb 13. Every time I try to Odin in the update, my phone restarts only to have the SIM Card not being found and my phone process constantly stopping. Any ideas what the issue could be? My recovery is from March 13th. I would like to update to a current nightly.
[Samsung Galaxy S 5 Unified Development] thaijunk:
What type of of phone do you have? Is it the Verizon variant kltevzw or something else. The link OP made was specifically for Verizon.
[Samsung Galaxy S 5 Unified Development] jdrch:
I wrote a guide on how to do this for any Samsung device earlier this year. Should work for any S5.
[Samsung Galaxy S 5 Unified Development] godofsalt:
Ok you have to use Odin to do anything with Stock Firmware. I don't know what your lastest baseband or modem should be. However, I do know, that if you want the lastest you have to Odin. Might want to do little research on that. SAMMOBILE.COM... Is a good place to start.

If not you can always use either Samsung Kies or Smartswitch to actually get the true updated stock rom for your phone plus a few other things. Does take some time though, but results in the end are good.

Oh, don't forget Mar13 would actually be lastest security from Feb.

From that point , of course you can do anything

Hope this helps you out.
[Samsung Galaxy S 5 Unified Development] cal002:
Well, at least on my G900F the RGB sensor doesn't show on camera, only the Proximity sensor does.

And for me:

1. display on: RGB sensor on (with Adaptive Brightness, I'm always using it), Proximity sensor off

2. display off: RGB sensor off (AutomaticBrightnessController has nothing to do), Proximity sensor on (with Proximity wake, which I'm not normally using, only enabled for this test)
[Samsung Galaxy S 5 Unified Development] DragonQ:
Potential fix for GPS issues:

I flashed the latest Samsung stock ROM (it wouldn't finish booting but the flash supposedly worked) and then reflashed the 26/04/2017 Lineage OS build (only because I vaguely remember someone saying the 03/05/2017 build broke the microphone). I've only had 3 journeys so far but my GPS now seems fine. Before it would nearly always constantly drop out without the GPS Status & Toolkit workaround.

Not sure why this changed anything since I already manually flashed the latest modem and bootloader but oh well.

Turns out this didn't fix the problem after all. :(
[Samsung Galaxy S 5 Unified Development] BrX91:
What did you flashed by meaning modem and bootloader? I have used alexandr's packages from androidfilehost.

Wysłane z mojego SM-G900F przy użyciu Tapatalka
[Samsung Galaxy S 5 Unified Development] DragonQ:
Yes I used those, it didn't work for me. Only flashing the entire stock ROM seemed to fix it. The exact image I flashed is here.