yashsingh1/xdaforums huggingface dataset:
[Galaxy S 5 Android Development (Snapdragon)] xtexistenz:
Hey Corinna,

I don't think it is normal for a phone to drain any battery when it is in complete deep sleep as my stats showed (check out this thread reply please: https://xdaforums.com/showpost.php?p=74601052&postcount=33335 ), nothing in the OS used the battery, so it must be something wrong in the kernel, maybe a sensor is always running and I want to help and fix that but I will need some help from you to get started with this and learn how you build and test it, can I send you a PM here?

The stock OS/kernel never had any drain problem, same with my S4 mini, I still have the stock OS (kitkat 4.4.2) on it and it is not draining any battery when I don't touch it, and it is draining less battery than LineageOS when I use it, and the battery in the phone is very very old and also smaller.

Please let me know if you want my help.
[Galaxy S 5 Android Development (Snapdragon)] Air1980:
https://xdaforums.com/galaxy-s5/dev...axy-s5-lte-t3534283/post74226531#post74226531

The battery drain in my case came from from a broken light/proximity sensor.

After changing the sensors the battery life/stanby mode is amazing even with an old battery.

---------- Post added at 11:57 AM ---------- Previous post was at 11:53 AM ----------

Hi there.

Is there any way to change device name in Lineage os 14.1 through settings or adb terminal?

The computer sees my device with the old name given in Marshmallow stock rom,even if i change wi-fi,bluetooth,hostname in developers options and user name in accounts.

Thanks.
[Galaxy S 5 Android Development (Snapdragon)] cvxda:
I don't have any real drain. My five devices take between 0.4% and 1.0% per hour and every device is different, for no apparent reason, even running the very same build.

I'm doing nothing different than described in this build HOWTO, apart from the fact that I'm doing this on Fedora, rather than Ubuntu.

I'm certainly happy to get help, but I'm not going to hold hands. I have enough stuff to do as it is. The aforementioned description should get any dev up and running.

Corinna
[Galaxy S 5 Android Development (Snapdragon)] xtexistenz:
I don't think I have anything broken.. it started right after I switched to LineageOS from stock.

But even 0.4% per hour shouldn't be normal (my s4 mini with stock OS proves me this) if everything is off and in airplane mode. If it is with the wifi and/or mobile network on, then yeah, that sounds normal. Can you please confirm if your tests were with airplane mode on?

Thanks a lot for the link, that's all I needed.

Do you think I should try to wipe everything and clean install it again, or it would make no difference? I do wipe the cache and dalvik when I install updates.
[Galaxy S 5 Android Development (Snapdragon)] ali.akbar01:
Can I flash aroma version of GAPPS and remove stock lineage os by Google counterparts? Will the aroma version work and will the Google counterparts remain without being replaced by stock lineage os apps when flashing update?
[Galaxy S 5 Android Development (Snapdragon)] cvxda:
Your assumption that every device should behave the same is flawed. The S4 has a totally different SoC and chipset. For instance, the S4 SoC has the radio on-chip, while the kccat6/lentislte radio is a separate chip connected via USB. Imagine the differences in chip usage. And this is, of course, not the only difference.

I tested with Wifi and mobile on. Airplane mode doesn't make sense, it's too artificial. In terms of SoC differences, as outlined above, there's also no guarantee that secondary chips are going into a battery saving mode, just because you switched off radio or wifi.

You should take into account that we got *some* kernel from Samsung, but not a complete one: For instance, the Wifi driver is missing. Qcacld-2.0 is under a dual license, BSD or proprietary. Apparently Samsung opted for proprietary and given the base license they don't have to open up their optimizations at all. All we have is the OSS qcacld-2.0 in its base form, with no idea if and what Samsung tweaked. We also got the kernel settings, but not necessarily the optimized variant, just some variant which is set up for debugging in the first place. Last but not least, there are also entry points in the kernel which Samsung exported for the purpose of control from user space. However, for obvious reasons we're lacking these user space tools.

Whatever we do, we *might* be able to come close to the battery usage of a stock system, but given that Samsung doesn't open up everything, we're always a step behind.

Actually, every time you wipe your caches, you have to expect a higher battery usage for a while since android will set up stuff in the background it won't have to do with filled caches. A new installation is worst. You should wait a couple of hours to make sure the system has settled and only then load your battery and check battery usage. In testing I had new setups with 3%/h battery usage which only settled after a while.

Corinna
[Galaxy S 5 Android Development (Snapdragon)] DienoX:
[MENTION=3419717]cvxda[/MENTION]

Does anyone have voLTE and voWifi?
[Galaxy S 5 Android Development (Snapdragon)] xtexistenz:
I didn't say that, I'm not expecting them to behave the same, I'm just saying that the s4 mini was always an inferior phone, it was a big battery improvement for me when I switched to s5 plus and the phone is faster too, but with LineageOS it seems the s4 mini is doing better in terms of battery life with a very old and degraded battery, and I thought the whole point of a custom ROM is to have something better, sure don't get my wrong, LineageOS is a lot smoother and nicer, but for me the most important thing is the battery life, and well.. maybe I miss being able to record videos at more than 30 fps and I liked the samsung camera app. Hopefully there will be a way to get it to work one day..

I knew about the cache wipe thing and always waited a while for it to settle before doing any tests.

Thanks a lot for all the info! I might try the stock rom again for a while and compare it again and post here what I found.
[Galaxy S 5 Android Development (Snapdragon)] DienoX:
[MENTION=3419717]cvxda[/MENTION]

Could you add support for WireGuard?

https://www.xda-developers.com/wireguard-vpn-project-support-android-roms/

https://xdaforums.com/android/development/wireguard-rom-integration-t3711635
[Galaxy S 5 Android Development (Snapdragon)] max6698:
Broken dialer in recent compiles

Hi [MENTION=3419717]cvxda[/MENTION],

recent RIL kernel patches may have broken the dialler

Details:

I compile LineageOS for my lentislte using the instructions at https://wiki.lineageos.org/devices/lentislte/build

My last 2 compiles have included a broken dialler. When I try to dial a number, the call doesn't complete. If I try to hang up, it doesn't complete hanging up either. The broken compiles are named lineage-14.1-20171124_052411-UNOFFICIAL-lentislte.zip and lineage-14.1-20171129_221934-UNOFFICIAL-lentislte.zip. The gmt timestamps in those filenames give a pretty good clue about which fixes are included, as I did a "repo sync" immediately before each compile. (Patch timeline here: https://www.lineageoslog.com/14.1/lentislte ). Additionally, I did a "make clobber" before creating the second zip.

My broken compiles include a lot of RIL kernel related patches. My problem may impact multiple people once those RIL patches make their way in to a weekly build.

Reinstalling lineage-14.1-20171118_235115-UNOFFICIAL-lentislte.zip gives me a working phone again.

Thanks for bringing LineageOS to my lentislte :)
[Galaxy S 5 Android Development (Snapdragon)] knojap:
Hello, can anyone explain me the difference between the unoffiial and official version of this rom?

thx
[Galaxy S 5 Android Development (Snapdragon)] wilmsn:
As far as i know an official build is only produced by the maintainer of the device. Unofficial build may be produced by anyone as the whole source is open source.
[Galaxy S 5 Android Development (Snapdragon)] foxi007:
Hi,

yes please do this, here is the same problem
[Galaxy S 5 Android Development (Snapdragon)] xtexistenz:
I'm back on the stock 6.0.1 Samsung ROM - https://www.sammobile.com/firmwares/galaxy-s5/SM-G901F/PHN/download/G901FXXS1CQI5/191101/

A few days have passed since I used it and the difference is big for me for standby battery life, I didn't even bother testing it with airplane mode on, I've left it overnight with just mobile network on and there was actually zero battery drain (which is weird, I need to test this again, the network should use a tiny bit), same setup and apps as I had on LineageOS, so again there is a problem with the LineageOS/kernel, but there isn't a huge difference in battery drain when I actually use the phone (screen on time), I get maybe a little more battery with the stock ROM, it's hard to tell as LineageOS has the idle draining problem to begin with (again I think it's maybe a sensor not turning off or something). But overall, more battery life with stock ROM and I think the phone doesn't get as hot either when I use it.

I'll come back with a BetterBatteryStats log and screenshots to prove what I'm saying.
[Galaxy S 5 Android Development (Snapdragon)] bud7dha:
I've owned a g906s since it came out 3.5 years ago. Cell standby and phone idle have always topped battery stats when I don't use my phone a lot. I've tried all stock roms since 4.4.2, countless TW mod roms on KK, LP, and MM; I've also tried AOSP roms like CM 12.1 & 13, RR, Mokee,, and LOS 14.1 and numerous custom kernels on TW and AOSP. Those two stats have never changed when my device is idle. Since MM came out, the idle battery drain was about the same whether I used stock, stock mod, or AOSP. With LOS 14.1, I don't use GAPPS at all, and my battery life is better than stock (less than 0.5% per hour on idle), whether I use my phone a lot or not. That said, every device is different; individual usage and preferences vary; batteries age, and so on. Without detailed system and kernel logs over the course of 2-3 battery cycles, it's impossible to say LOS, it's kernel, or both is the cause of your battery drain. BBS won't reveal much about kernel issues related to wakelocks (or partial wakelocks) which could be draining your battery. If you're having better luck with stock, then maybe it's more suited to your needs.
[Galaxy S 5 Android Development (Snapdragon)] The Child of 13th:
Really thanks for the support [MENTION=3419717]cvxda[/MENTION], rom is great and all, but is there a way to improve camera quality, on stock camera quality is much better
[Galaxy S 5 Android Development (Snapdragon)] FatBoyNate:
no gsensor cardboard broken

umm latest nightly and theres no gyroscope support did u forget to fix it? phones worthless without it.
[Galaxy S 5 Android Development (Snapdragon)] quphkzie:
what happened to previous builds? Cannot find it in this website: https://www.lineageoslog.com/14.1/lentislte

---------- Post added at 07:10 PM ---------- Previous post was at 07:06 PM ----------

no december build for lentislte? https://download.lineageos.org/lentislte
[Galaxy S 5 Android Development (Snapdragon)] k2828:
clean installed and encrypted latest nightly:

random restart and stuvk in bootloop afterwards. happend two time while in idle now.
[Galaxy S 5 Android Development (Snapdragon)] quphkzie:
latest build sucks! very laggy.
[Galaxy S 5 Android Development (Snapdragon)] xtexistenz:
Sorry, I was busy and needed my phone, I've done the test last night on the stock Android 6 Samsung ROM for 12 hours with just mobile network on and it dropped to 97%, there seems to be an initial battery drop (I think at around 2%, I believe batteries never really charge fully to 100%) as shown in the screenshot, I think it actually drained around 1%, maybe if I would've done the test for more time it would show less drain / hour.

So this is 0.2% / hour stock ROM vs 0.8% / hour LineageOS (and this test was done with airplane mode on: https://xdaforums.com/showpost.php?p=74601052&postcount=33335). I think this is a bit of a difference, 4 times more drain on LineageOS.

I've even tried one with wifi on and it dropped to 95% so that would be about 2% more battery drain for the wifi over 12 hours, the exact same 2% difference I saw on LineageOS when I tested it with wifi on. I think (based on my estimates) LineageOS uses around 10% of battery for no reason over 14 hours.

[MENTION=3419717]cvxda[/MENTION]: I think you should reopen my bug report as it still stands as a problem - https://jira.lineageos.org/projects/BUGBASH/issues/BUGBASH-842?filter=allopenissues

Thanks
[Galaxy S 5 Android Development (Snapdragon)] quphkzie:
[[[[[[[[[[[WARNING!]]]]]]]]] for lentislte (s5 lte-a) users, don't download latest build which is dec 7. it's very laggy and unresponsive. i hope dev will fix this. [[[[[[[[WARNING]]]]]]]]]]
[Galaxy S 5 Android Development (Snapdragon)] DienoX:
I had the same problem. After a few hours I could not stand it and went back to the previous version.
[Galaxy S 5 Android Development (Snapdragon)] quphkzie:
so it's really this build that causes the lags then. thanks! nay i know what build date you are using now?
[Galaxy S 5 Android Development (Snapdragon)] quphkzie:
hi, first of all i have the november 30 build for lentislte or galaxy s5 lte-a because latest build (dec 7) is very laggy and unresponsive. but now my problem is google feed is saying "can't reach feed right now" seems like the google app is not connected to wi-fi. but all apps seems fine. i wish dev won't delete this post or ignore it. hoping for dev's reply thanks!
[Galaxy S 5 Android Development (Snapdragon)] phamanhvu01:
It's worth nothing that for me, Marshmallow AOSP builds (such as MoKee or CM13) tend to have similar if not better, deep sleep than stock ROMs....
[Galaxy S 5 Android Development (Snapdragon)] dplant:
I have a weird, infrequent bug with my Galaxy S5 since I installed Lineageos (currently using 14.1-20171207-NIGHTLY-klte). A few times per month my phone will wake up from sleep with this screen:

https://xdaforums.com/picture.php?albumid=14630&pictureid=56713

https://i.lensdump.com/i/mBscc.jpg

From there the power button will put it in and out of sleep and plugging in the charger changes the blue area to yellow.

Nothing else works, and I have to remove the battery and reboot. Does this ring a bell?
[Galaxy S 5 Android Development (Snapdragon)] Stamgastje:
Yes -- it is related to the Flip Cover settings. Have a look here:

https://xdaforums.com/galaxy-s5/dev...axy-s5-lte-t3534283/post71605146#post71605146

https://xdaforums.com/galaxy-s5/dev...axy-s5-lte-t3534283/post71613237#post71613237
[Galaxy S 5 Android Development (Snapdragon)] dplant:
Thanks a lot! The flip cover was indeed enabled in the settings, so I turned it off.
[Galaxy S 5 Android Development (Snapdragon)] Recycool:
Hi, I just reinstalled the ROM after a long time, and it feels so slow and sluggish, takes a lot of time to open any app, and even in-app it is so slow, as an example on instagram just to load the DM section takes like 2-3 seconds loading, what happend? Is beacuse of the "new" thermal throttling? Is there any way to get the old, no thermal throttling, wihtout root? I loved how snappy this ROM was back then.. and now it just feels worse than the stock.

Apart from this, I just received a call and the other person couldn't hear me until I pluged in the some headphones.
[Galaxy S 5 Android Development (Snapdragon)] quphkzie:
yeah same with me
[Galaxy S 5 Android Development (Snapdragon)] qianoo:
20171213

Hello,

I recently encrypted my Phone after flashing 20171129.

After (successfully?) upgrading from 20171206 to 20171213 today, my phone told me that the password/pattern is right, but the data is damaged (trying to force me to factory reset...).

Wiping cache/dalvik didn't help, but reflashing 20171129 (because of minor problems in 20171206) fixed it again.

By the way, I'm using this ROM since 17/05 and everything but the camera is working flawless (no unresponsiveness with 20171206).

Thanks for showing me how cool the S5 realy is!
[Galaxy S 5 Android Development (Snapdragon)] sentryx:
Same bro. Had the headphones bug since i first flashed it two months ago. Had it as a daily driver and it was running smooth until last week when it started lagging in every app and even worse while multitasking (even with kernel auditore on performance settings with all cores enabled to 2.4ghz while phone awake) and i decided to go back to the official rom.
[Galaxy S 5 Android Development (Snapdragon)] quphkzie:
try flashing the nov 30 build
[Galaxy S 5 Android Development (Snapdragon)] tni.andro:
Performance issues

The performance problems various people mentioned were probably due to the CPUSETS kernel config that was enabled in the 2017-12-06 build. This was reverted and you should give the 2017-12-13 build a try.
[Galaxy S 5 Android Development (Snapdragon)] Gogikerman:
Hi

How to root lineage OS installed. G901f kccat6 ? Please

Link for tutorial. Thank s.
[Galaxy S 5 Android Development (Snapdragon)] quphkzie:
flash latest supersu zip file via twrp recovery
[Galaxy S 5 Android Development (Snapdragon)] Gogikerman:
Thanks. .Okay
[Galaxy S 5 Android Development (Snapdragon)] bschtl:
I can confirm that the performance problems are gone with the 2017-12-13 build.
[Galaxy S 5 Android Development (Snapdragon)] Hans Maise:
2017-12-06 build was running w/o problems, yesterday i updated to 2017-12-13 and got stuck with bootloop. Now i'm back on 2017-12-06 ... Anyone else with that problem / any idea? Or just wait for next update ?
[Galaxy S 5 Android Development (Snapdragon)] quphkzie:
what s5 variant u have?

---------- Post added at 06:07 PM ---------- Previous post was at 06:03 PM ----------

December 7 build for lentislte is very lag and unresponsive i don't know the latest build (dec 14). i haven't tested it yet.
[Galaxy S 5 Android Development (Snapdragon)] bschtl:
Sorry I forgot, G901F / kccat6.
[Galaxy S 5 Android Development (Snapdragon)] quphkzie:
ahh oki
[Galaxy S 5 Android Development (Snapdragon)] Hans Maise:
sorry, forgot to write the model i use: it is G901F / kccat6
[Galaxy S 5 Android Development (Snapdragon)] LCFM:
Huge battery draining during night off SM-G901F

Hi there,

First, thanks for your work guys I really appreciate to get the latest security updates & a blank os on my phone where I can installed everything I want.

But as the title said I got a huge battery draining problem during the night.

I lose around 20 to 40% when my phone is switch to airplane mode during night.

I already get the problem once previously after first flashing attempt where i saw my phone completely off in the morning so I decided to trying reflash the rom again to see if it solve the problem but apparently it didnt.

After checking the battery section I saw that lineage os drain like 13% well android platform drain around 12% & 11% for standby.

I hadn't that kind of draining problem well I was on the lastest stock ROM so definitely not a hardware problem.

I have the latest build from 13122017 so if u could help me I would really appreciated.

Thanks.
[Galaxy S 5 Android Development (Snapdragon)] quphkzie:
3% on lineage os system.
[Galaxy S 5 Android Development (Snapdragon)] LCFM:
Back up, looks like the issue fix by itself as don't have such huge battery drain (think the battery wasn't calibrated with new system yet ;) )

Anyway wanna know if u gonna released a new build before Christmas ??? :o

And what about Oreo (Lineage OS 15) on this device ???

Thanks :cyclops:
[Galaxy S 5 Android Development (Snapdragon)] pbecks1963:
There i go again...

Hello,

I am about to flash my sm-g901f to Lineage OS 14.1. I am on stock Android 6.01. Baseband: G901FXXU1CPJ1 / Build: G901FXXS1CQI5. Phone is rooted , twrp is installed as recovery. Backup's are made. Is my bootloader good enough? :confused:

ps: (is this still the right way to do it?)

1) factory reset

2) flash rom / gapps (zip files are on external sd-card)

3) wipe (dalvik) cache

4) reboot / wait a while (don't look at battery stats for a couple of days)
[Galaxy S 5 Android Development (Snapdragon)] wilmsn:
I tried LOS even with a bootloader that was a little older than yours. So i expect it would work.

Just try it, there is no extra risk if your bootloader is a little older.

Your steps are also OK. Do the factory reset in twrp just before installing the new rom.
[Galaxy S 5 Android Development (Snapdragon)] tni.andro:
Make sure you have TWRP 3.2.1 installed. 3.2.0 has major issues with a lot of the internally used programs crashing.
[Galaxy S 5 Android Development (Snapdragon)] pbecks1963:
Juist wanted to say: all is well! Phone is purring like a kitten.
[Galaxy S 5 Android Development (Snapdragon)] quphkzie:
can anybody confirm the lag issues for lentislte build dec 21 has fixed? im still in nov 30.
[Galaxy S 5 Android Development (Snapdragon)] bud7dha:
No lag here. On the build that gave some folks lag and battery drain issues, there were two cpu hotplugs enabled in the kernel at the same time (mpdecision and intelliplug). Now, there's only mpdecision available. There have been some typical cpu governors (i.e., ondemand, performance, userspace, etc.) added as well if interactive isn't sufficient for your needs. Those governors may have been there already, but this is the first time I'm noticing them through Kernel Adiutor.
[Galaxy S 5 Android Development (Snapdragon)] quphkzie:
thanks mate.
[Galaxy S 5 Android Development (Snapdragon)] Kernle 32DLL:
Hmm, what happend to the 20171221 build for kccat6? The other variants seem to have a build.

https://download.lineageos.org/lentislte

https://download.lineageos.org/kccat6
[Galaxy S 5 Android Development (Snapdragon)] andreoide:
Hmmmm indeed. Hmmmm

:cowboy:
[Galaxy S 5 Android Development (Snapdragon)] shm0:
hi

when i try to connect to an ap with 802.11w enabled it doesnt work.

here is some adb log

WPA: IE in 3/4 msg does not match with IE in Beacon/ProbeResp (src=ap-mac-here)

CTRL-DEBUG: ctrl_sock-sendmsg: sock=9 sndbuf=163840 outq=0 send_len=85

CTRL_IFACE monitor sent successfully to /data/misc/wifi/sockets/wpa_ctrl_862-12\x00

WPA: RSN IE in Beacon/ProbeResp - hexdump(len=26): 00 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 00

WPA: RSN IE in 3/4 msg - hexdump(len=26): 00 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 00

wlan0: Request to deauthenticate - bssid=ap-mac-here pending_bssid=00:00:00:00:00:00 reason=17 state=4WAY_HANDSHAKE

TDLS: Tear down peers

wpa_driver_nl80211_disconnect(reason_code=17)

i nulled the hexdumps.

the pending_bssid was actually all 0s.

if someone could have a look at this please. thank you.

merry christmas everyone!
[Galaxy S 5 Android Development (Snapdragon)] pbecks1963:
I deactivated bluetooth a couple of days ago. When i try to activate it, it won't go on. is this a bug? is there a work-around?
[Galaxy S 5 Android Development (Snapdragon)] LCFM:
Thanks for the new build :p

Hi,

Just to say thank you for the new build (20171227) on the Galaxy S5 Plus (kccat6).

Update via OTA perfectly ;)

Keep up & don't drink to much this weekend.

LCFM.
[Galaxy S 5 Android Development (Snapdragon)] Hans Maise:
Something "strange" - solved - ... a help for someone else ?

My phone is a " kccat6 " ... last running LOS was 20171206.

Update to 20171213 caused "bootloop" , so i went back to 20171206, later on back to 20171129 ...

Today i flashed the actual update 20171227 ......... again bootloop :(

Back again to 20171129 i updated TWRP from 3.1.0-2 to 3.2.1-0 and tried again ... same result.

While 20171227 was looping ... i had an idea and removed the sdcard ... and it works !!!

I put the card in again -> bootloop ... crazy!

It´s a ~2year old Samsung EVO+ 64GB , formatted as "internal" .

Hope, this can help if one has same "strange" problem :)