yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] curiousrom:
New Battery Life

What is the brand & weight of your new battery?

See Fake vs OEM S5 Samsung Battery.

If it's a fake OEM or third-party battery with a weight of 40~40.2 grams instead of 45~45.2 grams like original Samsung for S5 then it will have a smaller real capacity & battery life. And their capacity drop faster over time.

Also the battery usage @ idle is important because all the power the S5 is using @ idle is less power left for Screen On Time (SOT).

See this post I made in the BetterBatteryStats thread & the attachments: Galaxy S5 LineageOS 16.0 Battery Usage @ Idle and also Most Recent BetterBatteryStats & Proper Dump Settings if you want to try BBS.

I am attaching here the GSam Battery Monitor screenshot that I posted there. It was taken on July 14, 2019. In the bottom of it you can see that the stats are cumulative since Mar 16, 2019. That's the day I did a clean install of 16.0 including Format Data instead of a simple Data wipe & installed this Gsam app afterwards.

So that's 4 months of battery stats with my old 2015 S5 OEM Samsung battery:

Average Per Complete Charge

Battery Life: 1d 1.6h (6h 39m Active)

Screen On: 5h 41m (6h 44m Max)

Since Mar 16, 2019

Obviously the kind of apps you are running with the screen on will have an impact too.

For example I am a New York Times subscriber. I was using the New York Times app & noticed a huge %/hour of battery consumption by this app in Gsam & LineageOS battery stats. Now I am using a browser to login & surf New York Times and it's consuming only 1/3 of the app's %/hour.

I apply the optimization tips described here including using Privacy Guard Advanced: Remove Animations UI Speedup Test - Taming Google & Apps and keep the screen brightness low except when outdoor.

***
[Samsung Galaxy S 5 Unified Development] nate121:
Turns out it was a sim and data plan related issue, finally got it working.?
[Samsung Galaxy S 5 Unified Development] jpulido09:
SD Maid is giving error saying that i do not have privileges to move any apps to SD card. is there an existing report? I searched throughout thread for 4 hours and i found only something called F-Droid. Does anyone know how to move apps to SD? Or is F-Droid the only way? I haven't looked into F-droid rabbit hole if there is one. From what I gather this seems the only way. So can we do this with stock lineage settings?

I am on july 24 build using g900T.
[Samsung Galaxy S 5 Unified Development] Ibuprophen:
I've seen this similar thing happen to someone and it was resolved by flashing AddonSU and granting root permissions.

LineageOS doesn't have Root by, default. This is why this is provided as an optional extra for those who does want Root.

~~~~~~~~~~~~~~~

Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
[Samsung Galaxy S 5 Unified Development] kurtn:
F-droid is something completely different. Yes, kind of rabit hole. It's an app store for for open source apps. It's the key to setup lineageOS without GApps.
[Samsung Galaxy S 5 Unified Development] Sobhan Mazaheri:
Hi

Two problems

1- Notifications do not appear until I turn on the screen (sms-apps Notifications- miss calls)

2- screen sometimes turns black for a few seconds, and ringtone, music player, and call frequents history disappear.

Is it a solution to these problems or is it related to kernel problems?
[Samsung Galaxy S 5 Unified Development] RBraverman:
IS there a easy/quick way to connect the phone to a PC and have the ext sdcard look like a removable drive?

Stock the S5 can change the USB, but this doesn't so that I can get to it and map t. I've tried a webdav server but really not what I want as it WON'T recognize the external card.
[Samsung Galaxy S 5 Unified Development] kurtn:
So you have selected adopted storage for your SD
[Samsung Galaxy S 5 Unified Development] RBraverman:
Correct.
[Samsung Galaxy S 5 Unified Development] Sobhan Mazaheri:
?????????

Can anyone guide me?:confused:
[Samsung Galaxy S 5 Unified Development] kurtn:
https://xdaforums.com/galaxy-s5/unified-development/rom-lineageos-16-0-t3850840/post78635977

Souperclean install
[Samsung Galaxy S 5 Unified Development] curiousrom:
No SMS Messaging Notification & Screen Turns Black?

You don't give any setup description which makes it difficult to troubleshoot. :eek:

"1- Notifications do not appear until I turn on the screen (sms-apps Notifications- miss calls)" - The stock LineageOS 16.0 Messaging app had a bug with the LED notification not working by default but it was solved with the patch Messaging: And there shall be light (LED) available in LineageOS 16.0 build 2019-07-26 or newer.

If you are running LineageOS 16.0 build 2019-07-25 or older you can solve this manually with: > Settings > Apps & notifications > Messaging > Notifications > Messages > Advanced > & make sure that Blink light is toggled on.

I don't know what that is exactly but just in case do the same for > Settings > Messaging > Notifications > Channel human readable title 1 > Advanced > & make sure that Blink light is toggled on.

If you leave the S5 alone for 15 minutes or so it goes into deep sleep (Doze) and there is a Messaging SMS notification delay until the next Doze maintenance window which is usually 15 minutes or less regardless of the Messaging app notification and battery optimization settings which is set to Not Optimized by default for the Messaging app.

The attached screenshot is of > Settings > Apps and notifications > Advanced > Special access > Battery optimization. Or search for optimization in Settings.

Additionally I did set com.android.smspush to Not optimized & it did not change anything about the SMS notification delay while in Doze. So that seems like a bug.

I don't get any LED notification delay while in Doze with WhatsApp or Reddit for example even if they are set to battery Optimize.

Or while in Doze you get an instant Messaging notification by manually turning on the screen.

***

With the stock LineageOS Phone dialer app I do get an instant blue LED Missed call notification when the screen turns automatically off after the call is not answered.

In LineageOS 16.0 you can search for Light in Settings and change the LED colors & behavior for different apps which is pretty cool IMO.

***

"2- screen sometimes turns black for a few seconds, and ringtone, music player, and call frequents history disappear." - My screen never turned black for a few seconds nor did the S5 turned off or rebooted by itself (as you wrote in your post before you edited it) even once since I did a S5 super clean install 4 months ago.

My screen turns off automatically only according to my > Settings > Display > Advanced > Sleep setting.

That's on a Galaxy S5 G900M LineageOS 16.0 klte build 2019-07-31 + Open GApps Pico + LineageOS AddonSU, no custom kernel or system mods of any kind.

***
[Samsung Galaxy S 5 Unified Development] Paul_Lunardi:
hi all,

I couldn't figure out a way to draw a circle around an image to highlight something in a screenshot. I was trying to do this with the editor in the lineage gallery. is it possible to request such a feature if it's not already available.

Thank you
[Samsung Galaxy S 5 Unified Development] kurtn:
I don't think lineageOS team will react. Try https://f-droid.org/app/com.simplemobiletools.draw.pro
[Samsung Galaxy S 5 Unified Development] Sobhan Mazaheri:
Thanks for your guidance

first problem is due to the option being enabled in >ambient display< of the attached file.

And the second one I did a super clean install and I'm testing.
[Samsung Galaxy S 5 Unified Development] Sobhan Mazaheri:
Maximum charge

I bought a new battery for my device, installed the latest build (Galaxy S5 G900FD LineageOS 16.0 kltedous build 2019-08-02 + Open GApps Pico) How many hours of normal charge should it have?
[Samsung Galaxy S 5 Unified Development] lecorbusier:
Until it's full.

I cannot explain that, but you may notice a big increase in standby and screen-on time after the first couple of charges, then dropping to a boring gain of about half an hour, which reflects the normal wear of a 2-4 years old battery.

The rest of the formerly glorious battery life is lost forever due to increased demands of OS, apps and content.

I wouldn't have cared about half an hour more or less, when i got 7,5h of screen on time with my S5 four years ago. But the increase from 4 to 4,5h i got from my new battery some weeks ago was worth it. Makes the phone just about useable again.
[Samsung Galaxy S 5 Unified Development] curiousrom:
Re: New Battery Life

You did not reply to my questions here New Battery Life : What is the brand & weight of your new battery?

Did you try to analyse your battery life with GSam or BetterBatteryStats as suggested in that post?

***

I'm not sure I understand.

If asking how long you can use the S5 running LineageOS 16.0 on a full charge see post linked above.

If asking how long it takes to charge the battery it depends on the charger & the quality of the cable. See S5 Battery Charging - Fake 100%

***
[Samsung Galaxy S 5 Unified Development] djlooka:
Installing lineage-16.0-20190805-nightly-klte-signed.zip results in a bootloop every time for me.

Can anyone confirm this?
[Samsung Galaxy S 5 Unified Development] yoshkapundrick:
No bootloop on my 900t.
[Samsung Galaxy S 5 Unified Development] shkedov:
No bootloop on kltechn here (G9006V).

What klte do you have? Did you wipe /data /cache properly? Did you try also wiping /system?
[Samsung Galaxy S 5 Unified Development] Ibuprophen:
I had no issues on my G900V & G900T devices (that I had Dirty Flashed both earlier today). :eek:

If you require further assistance, suggestions, recommendations, etc... we need a little more information to go on.

Are you actually experiencing a Bootloop (when a device gets to a point during boot and then restarts only doing the same thing again)?

~OR~

Are you Stuck in Boot (when the device gets to a point during boot and remains there)?

Did you perform a Dirty Flash (updating a previous installation of the "Official LineageOS 16.0" build)?

~OR~

Did you perform a Clean Flash/Installation?

What exactly were the steps you had taken/performed within TWRP?

Did you grab a copy of the TWRP Logs afterwards?

~OR~

After experiencing your issue, manually entering TWRP Recovery and obtaining the TWRP Logs?

Thank you for your time and understanding with this clarification... :thumbup:

~~~~~~~~~~~~~~~

Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
[Samsung Galaxy S 5 Unified Development] Chatbox:
I have a G990F with the latest build of LineageOS (as of today).

For the past year (since I switched over to LineageOS from the official Samsung ROM), my G900F boots fine into Android, however, it does take a rather long time to boot through the Samsung logo during power on. Is this behaviour the same for everyone here?
[Samsung Galaxy S 5 Unified Development] BlueCyclone:
This is normal behavior since Oreo. IIRC something to do with a race condition at boot, so max cores is limited to 1 during boot
[Samsung Galaxy S 5 Unified Development] lecorbusier:
Sometimes, and i had/have this also with Pie based official RR and unofficial LOS 16 on my Note 10.1, part of the ART binaries get re-compiled at boot. Titanium backup can find & clean up the trash left behind, dometimes hundreds of megabytes of code, which take their time to get compiled.
[Samsung Galaxy S 5 Unified Development] djlooka:
It's ok, I could successfully restore the previous version so no harm done.

I've recently switched to the microG releases so I was wondering if it could be a mainline issue or not. It sounds like it isn't, so that's probably all I needed to know, thanks.

Given that, please ignore the rest of this message if it's against the rules.

It rebooted a couple of times and then automatically rebooted into TWRP.

I tried both with the internal updater and by manually downloading the latest release and installing it via TWRP.

When in TWRP, I installed it, then cleaned Dalvik and Cache.

Nope.
[Samsung Galaxy S 5 Unified Development] fparri:
Is this ROM usable as a daily drive? I would like to install it on my niece's Qualcomm S5, actually using an Android 7.0 RRemix ROM.
[Samsung Galaxy S 5 Unified Development] kurtn:
Yes
[Samsung Galaxy S 5 Unified Development] odoll:
I 'd support that. My wife's S5 is running with this version seamlessly since a long time. The only annoying thing for her is the BT audio issue in her car.
[Samsung Galaxy S 5 Unified Development] GalaxyS3only:
Hey!

I installed official LineageOs 16 20190808-nightly-klte

On my S5 (klte) but can't connect to my (hidden) wifi...

I came from 15.1 and did a complete wipe+data format+uninstalled magisk before

Then i installed lineage+magisk 19.3, seems to work but it can't find the hidden wifi, ssid and password are correct and wifi is working on other phone, some suggestions or known bug?

Thx & GreeTz
[Samsung Galaxy S 5 Unified Development] guest4711:
For testing you should unhide your wifi. Does your device connect now?

If not you may have problems with your wifi settings (e.g. you use a channel which is valid in Germany but your device thinks you are in US. This may occur if you setup your phone without simcard inserted.)
[Samsung Galaxy S 5 Unified Development] pslag01:
If you have magisk v19+ for SU, try setting it to 'Core Only Mode' first. (i.e., magisk manager / settings / check 'core only mode').

Works on my G900P (kltedv, Sprint).
[Samsung Galaxy S 5 Unified Development] lecorbusier:
Due to a bug in TWRP the system partition may not be mounted during installation of magisk.zip. My standard procedure for a clean install was for years to install rom, gapps and su tool in one go. Now i install them seperately, but without quitting TWRP in between, and check whether "system" is mounted before installing Magisk.

That was a necessity for installing Los 16 on my Note, but would've probably also worked when i suddenly could no longer dirty and clean install any Los 14 roms on my S5 one or two years ago. Restoring backups still worked. I just quit to RR then, until recently...

Converting from another su tool to magisk could be difficult. That was an issue, when custom roms were usually rooted.
[Samsung Galaxy S 5 Unified Development] curiousrom:
S5 LineageOS Update 2019-08-11 - Security Bump - Very Long Boot

FYI in the S5 LineageOS Update 2019-08-11 or newer there is a August 2019 security bump (Android 9.0.0 release 46).

The patches were made by S5's LineageOS dev [MENTION=2693412]haggertk[/MENTION] & Thanks to him for that. :good::)

Downloaded & installed successfully via the LineageOS built-in OTA Updater & after the automatic reboot as seen in the screenshot: > Settings > About phone > press on Android version 9 > Android security patch level: August 1, 2019.

The Vendor security patch level remains @ August 1, 2017 because the vendor is Samsung & it is not publishing security patches for it's S5 proprietary blobs anymore since August 2017 & nobody can do anything about it.

***

Very Long Boot Time & Backup

Thanks to [MENTION=312853]Chatbox[/MENTION] for his recent boot time question, I used a stopwatch to check the boot time @ every step when updating which I do not do often.

After the update was downloaded, from the moment I tapped on OK in > Install > Apply update > OK (screenshot) it took about 7 minutes to install automatically & full reboot to System which was very long as usually it takes about 3m30 on my S5.

I was starting to worry if I got caught in a bootloop after 5 minutes. :eek:

So I suggest you do a full backup in TWRP before applying 2019-08-11 if you don't have a recent one which is good practice anyway IMO. Always include the important EFS Partition as seen in the TWRP screenshot. I use SD Maid > AppCleaner to clear the cache of all apps & make the TWRP backup smaller. (screenshot)

If you could use a stopwatch when applying the update I would be curious to compare with what I observed:

Tap OK, the S5 automatically boots to TWRP, installs the update & reboots.

It took 1m43 for the aboot (bootloader) Samsung Galaxy S5 splash screen to appear.

It took 2m20 for the LineageOS boot animation to start which is actually when the kernel is loaded. See the last attachment for a S5 boot sequence flowchart.

@ 6m50 a chirp notification sound was heard while still in the LineageOS boot animation.

The S5 fully booted to the Home screen after 7 minutes.

Note that your boot time may vary depending on if you have a GApps package, Magisk or other zip's flashing automatically after each update like I do and all the other changes seen in https://download.lineageos.org/klte/changes/ since the last time you updated.

If you update manually you could start monitoring the time it takes after clicking on reboot to System in TWRP.

Thanks in advance. :good::cool:

***

That was updating to 2019-08-11 via OTA Updater on a Galaxy S5 G900M LineageOS 16.0 klte build 2019-08-04 + Open GApps Pico + LineageOS AddonSU, no custom kernel or system mods of any kind.

***
[Samsung Galaxy S 5 Unified Development] cgsjr:
BOOT time after latest 2019-08-11.

SM-G900v

TWRP 3.3.0.0

Have Open GApps, (I think its Pico), and LineageOS AddonSU.

1) moved file onto SD card.

2) flash manually using TWRP.

3) manual wipe dalvik and cache.

4) restart system == 2 minutes and 48 seconds till lock screen appears.
[Samsung Galaxy S 5 Unified Development] Ibuprophen:
Were you aware the current version of TWRP being 3.3.1-0?

Just an FYI... :)

~~~~~~~~~~~~~~~

Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
[Samsung Galaxy S 5 Unified Development] BitingChaos:
It looks like the (post) August 12th, 2019 builds FINALLY addressed the SD card size display bug.

32GB cards appeared to be 64GB, 64GB cards appeared to be 128GB, etc.

https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/252493
[Samsung Galaxy S 5 Unified Development] dundidit:
Just received Messaging notification sound 51 minutes after receiving sms( reported by phone). Don't know about led blinking but, it was working when I picked up the phone. G900W8 with Aug 11 update with Greenify, but the messaging app is not set to hibernate. Would someone please have a peek at logs attached. Oh ya using stock lineage messaging app
[Samsung Galaxy S 5 Unified Development] mastawindu:
Good job thanks

Just tested the last build on my old G900F, it works flawlessly, thanks a lot for your work
[Samsung Galaxy S 5 Unified Development] curiousrom:
Greenify & Messaging SMS Notification Delay - LineageOS 16.0

The problem is Greenify as the most recent version @ the present is Greenify 4.6.3 Beta & it's not optimized for Android 9.0 Pie on which LineageOS 16.0 is based.

I installed it via Play Store & use it once in a while but have it frozen (disabled) 99.99% of the time.

I use App Freezer for that app & others that I don't use often because you can add some apps to Favorite & when pressing on the apps you get infos like path, services, etc. but several others can "freeze" like Titanium Backup, SD Maid, etc.

As you can see in the screenshot I managed to reproduce your stock LineageOS Messaging SMS notification delay of 50 minutes with Greenify 4.6.3 Beta & it's Agressive Doze setting enabled.

I left the S5 alone for at least 15 minutes so it goes in deep Doze then using a spare phone @ 5:22 I wrote the SMS "Greenify 5:23" and when the clock showed 5:23 I sent it. As soon as I received a LED & sound notification I made the screenshot.

***

Afterwards in Greenify I disabled all the hibernation & doze options, froze it, rebooted & ran the same test. There is a Messaging SMS notification delay until the next Doze maintenance window which is usually 15 minutes or less.

Check Settings > Apps and notifications > Advanced > Special access > Battery optimization: Messaging & Phone should be disabled: "Not optimized" as per the default settings (screenshot). Or search Settings with optimi.

I found a tweak that makes the stock Messaging SMS notifications appear in 1 minute or less even when the S5 is sleeping but I'm testing the impact on battery life & will post about it later.

Read this Is Greenify recommended with Android 9 Pie thread with several posts by Recognized Contributors & Senior Members who used to be Greenify users on older ROMs like me but now don't recommend it on Pie.

Instead of Greenify I apply the optimization tips described here including using Privacy Guard Advanced: Remove Animations UI Speedup Test - Taming Google & Apps.

Doze is very efficient on LineageOS 16.0 IMO.

See No SMS Messaging Notification about the settings in LineageOS 16.0.

Interesting: Android Developers > Docs > Guides > Optimize for Doze and App Standby. Especially the Understanding Doze chapter.

***
[Samsung Galaxy S 5 Unified Development] cispinox:
Does anybody know why the Google configuration crash at the last step? I dont know what to do.
[Samsung Galaxy S 5 Unified Development] dundidit:
I switched over to Google Messenger and sound notifications were back to normal, although no blinking led. I'm using 4.5.1 and not the beta. After reading the posts you suggested (thank you) I have uninstalled Greenify, returned back to stock Lineage Messaging app and will see how things go.

Update: Nope that didn't work. Going back to Google Messenger as default app, might have to do a clean install. Any ideas, anyone
[Samsung Galaxy S 5 Unified Development] CHGICEMAN:
How is with you the battery consumption with the last LOS version?

---------- Post added at 09:16 AM ---------- Previous post was at 09:13 AM ----------

How long does the battery last for which SOT?
[Samsung Galaxy S 5 Unified Development] curiousrom:
Re: S5 LineageOS 16.0 Battery Life

It depends on many variables. :eek:

See New Battery Life and/or search thread with battery life.

***

I don't know what to suggest as you don't give any troubleshooting info. :rolleyes:

Are you talking about the Setup wizard on first boot after installing LineageOS 16.0? :confused:

***
[Samsung Galaxy S 5 Unified Development] Gorilla Daddy:
greenish flickering display? kernel solution.

Hi, I have three s5s. Below a certain power level (brightness), the displays start acting weird and flashing green. It happens on stock. It happens on lineage. It makes autobrightness unusable. Setting a fixed, higher brightness only partially fixes the problem. It's extremely annoying because even if you set the display at full brightness, the OS will fade out the screen (by internally decrementing the panel brightness) on idle & it looks horrible. If the display would never go below a threshold brightness, it wouldn't greenish flicker.

There's a functional fix, which would extend the life of our aging displays.

I tried pascua28's kernel, specifically the change by andip72, and confirmed working the minimum brightness fix for the green screen flicker. Their tiny kernel change fixes the green/flickering on my 3 different S5s: klte & klteduos:

https://github.com/pascua28/s5-kernel/commit/0a5c96e60aff94f2ea5eb7b0512c7150d5242c2c

Before, I was thinking of modifying the framework-res.apk resource values for the minimum brightness & brightness lux table mapping. But that's a static solution, that would be useful only for a particular phone. It's useful to be able set at runtime a minimum brightness, which the above kernel patch would allow. On some phones, they still might have some range in which the panel operates normally, but each is different.

Just a switch to disable brightness controls, and forcing maximum brightness always at the kernel level, might be a simple solution. Maybe to avoid a UI change, if brightness is set to the highest (255) & the slider is disabled in the taskbar & autobrightness is disabled then activate this kernel level minimum brightness = maximum brightness.

Any chance we could get some sort of minimum brightness fix integrated into the official lineage os? S5s are getting older, and whenever the ambient temperature drops (winter), this problem probably exists on a good percentage of the phones still in use.

Thanks in advance for your help.