yashsingh1/xdaforums huggingface dataset:
[Galaxy S 5 Android Development (Snapdragon)] TheFixItMan:
Why are you using super su? That's really old & will cause you problems

Clean flash & use magisk for rooting

Also if you flashed Resurrection Remix why are you posting problems in a lineage os thread?

Don't flash stock gapps! It replaces apps (probably camera app) which is why I recommend nano if use open gapps
[Galaxy S 5 Android Development (Snapdragon)] oualid1998:
lineage-14.1-20180615-nightly-kccat6

Plez i need lineage-14.1-20180615-nightly-kccat6 any one can help me
[Galaxy S 5 Android Development (Snapdragon)] ovidiuionut:
https://we.tl/t-0PAj6xIMpq

it's only valid for 7 days.

Enjoy!
[Galaxy S 5 Android Development (Snapdragon)] xamio:
root is (temporary) re-enabled in lineage-14.1-20170124-UNOFFICIAL-kccat6xx.zip
[Galaxy S 5 Android Development (Snapdragon)] Azakhan:
Is it worth updating everytime a new version comes out? Or is it better to wait a while? I think updating every few days increases the chance for a bricked rom, doesn't it?
[Galaxy S 5 Android Development (Snapdragon)] schwatter:
Nah normally all fine, because xamio is not a nightly builder. He just build when something is improved or updated in the source. I never had a brick from him.
[Galaxy S 5 Android Development (Snapdragon)] Azakhan:
Alright, thank you.

I just updated to the 25-1-2017 build by doing a system and dalvik wipe before flashing. But after flashing the rom a few of my gapps were gone (like the playstore and gmail app), is this normal? All my other apps were still there.
[Galaxy S 5 Android Development (Snapdragon)] schwatter:
No that is not normal. I also wipe always dalvik and cache without problems like that.
[Galaxy S 5 Android Development (Snapdragon)] licha26:
[MENTION=3507554]Azakhan[/MENTION] It's normal, gapps are stored on the system partition. You said you wiped your system partition and thus you deleted your current gapps. That's not a big deal, you just have to flash them back and you're good to go.
[Galaxy S 5 Android Development (Snapdragon)] Kernle 32DLL:
Have been using the lineage build 20170118 (and as of yesterday 20170125) for around a week now, and have no complains. Everything works, and I didn't have any graving issues so far.

I did encounter bluetooth audio stutter once, but that disappeared after a restart, and has not returned yet. Might as well have been an app problem.

So I can recommend the current lineage builds as a daily driver!
[Galaxy S 5 Android Development (Snapdragon)] andreoide:
Remember he talks about "testrelease" SR3 ! SR3 is not in playstore... Wich could mean the playstore-version 2.79 could not work...?

Peace [emoji111]
[Galaxy S 5 Android Development (Snapdragon)] Stamgastje:
I agree, it is really stable now. The only minor issues are with video playback. But nothing that prevents using it as daily driver.

And moreover: much smoother than the stock ROMs!
[Galaxy S 5 Android Development (Snapdragon)] schwatter:
[MENTION=3507554]Azakhan[/MENTION]

Sorry i missread your post. So it's your mistake, because of wiping system as licha26 recognised correct.
[Galaxy S 5 Android Development (Snapdragon)] ruchern:
SR3 works with the 2.79 app you installed from playstore. If asked to update binaries, go ahead with it! :good:
[Galaxy S 5 Android Development (Snapdragon)] Stamgastje:
I can confirm that. I just backed up boot, system and data and immediately afterwards restored them. This previously resulted in FCs, but now it works without problems. So this bug, listed in the OP, can be closed:
[Galaxy S 5 Android Development (Snapdragon)] Tarzangold:
You could give me something exactly a guidance, this Twtp Bug is fixed.

Please a guide.

Waht this with restorerecon/data. ????
[Galaxy S 5 Android Development (Snapdragon)] Stamgastje:
Sorry, but I can't make anything out of this... :confused:
[Galaxy S 5 Android Development (Snapdragon)] andreoide:
When restoring recovery, in TWRP after restored and before reboot go back to: Advanced in TWRP than choose Terminal

There type : restorecon -R /data

Than reboot.

Voila no more com.android.phone crashing

Peace [emoji111]
[Galaxy S 5 Android Development (Snapdragon)] Stamgastje:
That was indeed the workaround for restoring older versions of this ROM. But this is no longer needed with the latest versions, as that bug was fixed.
[Galaxy S 5 Android Development (Snapdragon)] schwatter:
Xamio build again with su, but just for info, the orig su.zip for LOS is up.

https://download.lineageos.org/extras
[Galaxy S 5 Android Development (Snapdragon)] RAFUi:
I'm on the lineage-14.1-20170125 build and I'm using it as a daily driver. So far, everything has been great, I really didn't expect such a solid build from a "beta" build to be honest, but there are some small things that really bother me:

- In Facebook, when you play a video, usually it begins playing it first in SD and then, when it switches to HD, the video zooms in a bit. I found a workaround by hitting back once and then tapping on the video once again, but it annoying imo.

- The battery life is nothing to write home about so far, it's oke when it's in mobile standby (not connected to the WiFi), but when it's connected to the WiFi, it drains battery like mad, it didn't do that before with the ~stock Samsung ROMs that I had.

- The Adaptive Brightness doesn't really quite work ok, I've noticed that it has a chance of 70% of actually nailing the ambient light good. Also, with the Ambient Display on, when the screen lights up very dimly to show you something, and you tap the screen to see more/wake the phone, the screen remains in that dimly lit state, and there is no way of undoing that other than locking the screen and powering it back on.

These aren't really big usability features, it's actually really refreshing that the ROM has no big problems other than those rather small problems (tho I do miss the camera app that came with the Samsung stock ROMs, it was really great :< )

I would really like to see some updates to the battery life, because it's one of the main reasons I switched to this ROM (and now I don't really wanna go back to stock b/c of how smooth the OS is all-around) and it's really not that great over the stock ROM, I'd even say it's a bit worse.
[Galaxy S 5 Android Development (Snapdragon)] Stamgastje:
Coming back to the video scaling issue:

I've been capturing the logcat during playback of this video (full log attached). The playback starts around 13:56:25 and stops around 13:57:07 (video duration is indeed 43 seconds).

The hickup occurs around 13:56:34. The logging around that time shows that the NuPlayerDecoder sees an 'audio discontinuity' as well as a 'video discontinuity':

01-29 13:56:34.439 386 14319 I LiveSession: [audio] read discontinuity of type 6, extra = NULL
01-29 13:56:34.440 386 14319 I NuPlayerDecoder: audio discontinuity (format=1, time=0)
01-29 13:56:34.692 386 14319 I NuPlayerDecoder: [audio] saw output EOS
01-29 13:56:34.700 386 14298 W AMessage: failed to post message as target looper for handler 0 is gone.
01-29 13:56:34.703 386 14298 W Utils : track of type 'audio/mp4a-latm' does not publish channel mask, channel count 2
01-29 13:56:34.705 386 14388 I MediaPlayerService: MediaPlayerService::getOMX
01-29 13:56:34.705 386 14388 I OMXClient: MuxOMX ctor
01-29 13:56:34.706 379 1127 I OMXMaster: makeComponentInstance(OMX.google.aac.decoder) in mediacodec process
01-29 13:56:34.712 379 1126 E OMXNodeInstance: setConfig(17b00eb:google.aac.decoder, ConfigPriority(0x6f800002)) ERROR: Undefined(0x80001001)
01-29 13:56:34.712 386 14388 I ACodec : codec does not support config priority (err -2147483648)
01-29 13:56:34.714 386 14388 I MediaCodec: MediaCodec will operate in async mode
01-29 13:56:34.720 386 14298 D NuPlayerDriver: notifyListener_l(0xb068c000), (6, 0, 0), loop setting(0, 0)
01-29 13:56:34.727 379 14389 I SoftAAC2: Reconfiguring decoder: 0->44100 Hz, 0->2 channels
01-29 13:56:34.727 386 14317 I LiveSession: [video] read discontinuity of type 6, extra = NULL
01-29 13:56:34.727 386 14317 I NuPlayerDecoder: video discontinuity (format=1, time=0)
01-29 13:56:34.785 386 14321 D SurfaceUtils: set up nativeWindow 0xaa40b808 for 1280x720, color 0x7fa30c04, rotation 0, usage 0x42002900

After this moment, the video scaling is incorrect.

Not sure what causes this, but it may be a hint on what is going on here.
[Galaxy S 5 Android Development (Snapdragon)] ellmotion:
Thanks for this ROM.

But I have an issue, when my phone is in sleep mode and I have an incoming call, if I push on my home button, the incoming call screen disappears, and I haven't no way to answer.

Nobody has this issue ?
[Galaxy S 5 Android Development (Snapdragon)] TheFixItMan:
Uploaded to android file host

https://www.androidfilehost.com/?fid=1322778262904022506
[Galaxy S 5 Android Development (Snapdragon)] O SAPHIA:
Could you please fix some bugs?

I experience some bugs with my Samsung Galaxy S5 LTE+ (g901f, kccat6) where my music player crashes frequently and causes the System UI to break, so I have to restart and then it only works good again. I wanted to ask you: could that be fixed in yoir future updates, and maybe add some more adjustments and settings to manually decrease the fanciness/amount of things that are slowing the system down or cause problems? It would be very helpful. And also, I have realized that the hardware acceleration seems to be a bit weird or so, because at some games (including Geometry Dash), it works much worse with Lineage OS than with the normal Android OS I had installed since the beginning. It would be great if you could fix it. Thank you!
[Galaxy S 5 Android Development (Snapdragon)] andreoide:
Again or still... I wonder I am the only one???

Sometimes I can't make calls, only way to get simcard to work again is reboot TWRP, clear cache in TWRP , reboot.

It happens like twice a week or so.

Anyone?
[Galaxy S 5 Android Development (Snapdragon)] Oswald Boelcke:
No, you aren't the only one - at least, I'm with you. I was unable to fix the issue to a specific situation, it just occasionally occured; however, too often and too regularly to make LOS 15.1 my daily driver. Some type of (occasionally multiple) reboots "brought the SIM back" but I couldn't figure out a specific "reboot procedure". By the way, same applied to me with RR-O-v6.0.1 i.e. no way that that ROM could be the daily driver either. Meanwhile I've my very own opinion about Oreo for this device.
[Galaxy S 5 Android Development (Snapdragon)] andreoide:
Thank you Oswald,

But like a few month ago it was like everybody had this bug, than Corinna made a patch and as nice than the ROM was okay, and for me a good daily driver.

Only things came back after the weekly from 2weeks ago. I can not figure out why.

When it happens I get the sim " back" by reboot in in TWRP, there manually clear cache, reboot to system and voila.

I have no problem with that doing so, exept the fact I do not know how long I'm not reachable before being aware I have to reboot. People call me and get to hear things like:

".…. The person you try to reach is not available ...." bla bla etc.

Like I have turned off my phone, which is in real fact not the case, but they cannot reach me cause the bug is active......

On the other hand I now learned to live with it because meanwhile I know now the bug appears ONLY right after rebooting. When rebooted I have to check if I can make calls, and if I can, than the bug is not active. I will not have to be afraid it will become active spontaneously, it only appears (IF it appears, bug comes random) right after booting up. So if it works and I do not reboot , it's a good daily driver for me....

RR-O-6.x is no option for me, I like to keep things "light" and easy to handle, just the way this ROM is now. RR looks great and people love it, but its just not a thing for me, that's all.

And last but not least: I miss Corinna in forum, I know she said being away for some time but still... And wish she is doing okay :D
[Galaxy S 5 Android Development (Snapdragon)] Oswald Boelcke:
I'm convinced if the issue had been solved Corinna had changed the OP but at "known problems" it still states:

For me personally, I can live with quite a few things but this is a clear show stopper. Even a smartphone is a telephone in the first place.
[Galaxy S 5 Android Development (Snapdragon)] Hellisonearth:
since the nightly from last week, theres an issue with the opencamera (1.44.1) always freezing. only a reboot helps.

also, yesterday i had crazy battery drain. i was out for 5 hours with 70%, and then the battery was empty. completely blocked running services except twilight. and i only had mobile data on and checked the phone 2 times. which means i was not even using the phone.
[Galaxy S 5 Android Development (Snapdragon)] Zimbiocom:
Hi!

I'm on lineage 15.1 lentislte (SM G906S), can anyone help me about making shortcut app on homescreen? I have installed clean manager sdk.apk and I can see it on app manager. But no shortcut on homescreen and so I can't use the app
[Galaxy S 5 Android Development (Snapdragon)] andreoide:
Hi Hellisonearth,

First hell is not on earth, some will go there after this life here in dunia, but that's different cook.

I had issue with opencamera this morning: phone went in strange reboot when raking a picture. I say a strange reboot because I saw the moving "logo" of lineage for like 15 seconds and than it suggested being completely rebooted .Normally boot takes way more than a minute, but than after login with fingerprint the sim-card was not recognised so I had to reboot to TWRP and wipe cache manually and than after reboot all was normal again and I could make pics without troubles.

I had never such issues but just like you since the pre-last weekly there is something bad going on in the ROM.

I have no extra battery drainage.

I hope Corinna can have a look into the ROM as total at some day if she can find the time.

I saw she posted new RR for smG901F but I rather stick to this ROM......
[Galaxy S 5 Android Development (Snapdragon)] Hellisonearth:
thanks for the reply andreoide. since then, battery consumption is normal again, but i still dont know what caused the issue. i dont have facebook on my device etc.. it is optimized by me to not run useless apps in the background. however, i noticed the phone got warm in my pocket without using any apps.

as you point out, the camera is buggy together with the newer nightlys. i dont know if its the fault of the opencamera app or if the rom or if it both has an influence. however, it was always sluggish for me even before the problems. I put the LED light on in the camera app, it crashes and the phone leaves the LED light on. then you cannot disable it in the quicksettings anymore, it stays on. really not usable at the moment. also i can confirm, the SIM-bug is back.
[Galaxy S 5 Android Development (Snapdragon)] andreoide:
Hi again friend.

As Oswald earlier stated the simbug never was gone entirely but a few months ago it was like everybody had the bug all day long sorta speak off. Than someone made a change and Corinna (cvxda) implemented the change in the ROM after which it seemed over, or at least the bug came out very rarely. But since the pre-last update/weekly its back in all its glory, or so it seems.

I just tested if I have the same trouble you have with the led in open camera, but even rebooted twice and made pics in different resolution and with led on and off, I cannot say anything else than open camera works great. So what/why the strange reboot triggered by earlier this morning is a mystery for me. I am not a developer, nor programmer, nor hacker whatever. I just hang around in XDA for quite a while and enjoy rooting and custum ROM.

This beauty made by Corinna ( cvxda) is probably the best ROM I ever used as daily driver, and even with all bugs, reboots sometimes occur I'll keep it as daily driver, knowing/trusting it will be solved.

I hope more pple read here and maybe one of them can make a fix, solution or anything helpfull

Until than I suppose we just have to sit it out. :D
[Galaxy S 5 Android Development (Snapdragon)] bicker83:
Where I can download Lineage 14.1 ?
[Galaxy S 5 Android Development (Snapdragon)] TheFixItMan:
Read the previous page to this one
[Galaxy S 5 Android Development (Snapdragon)] edan13:
i've got a quick question

what are your standby times with one full charge?

my phone drops from 100% to below 5% battery within 10-12 hours WITHOUT being used at all (just deepsleeping all the time)

is that normal?
[Galaxy S 5 Android Development (Snapdragon)] andreoide:
I've got a quick answer:

Before post here as you do.... Try find the answer in this thread yourself by using SEARCH and search for things like "battery" or better: "battery drain"

It saves you (and us) lots of time.....
[Galaxy S 5 Android Development (Snapdragon)] edan13:
Thank you for that insightful and productive contribution..

Ofc i have searched , the Thing is that there are so many variables to consider. I was Just wondering if the stated battery Life is to be considered normal or if my battery specifically has maybe reached the end of its lifecycle
[Galaxy S 5 Android Development (Snapdragon)] andreoide:
How easy you give yourself answers to your own questions.... Amazing :D
[Galaxy S 5 Android Development (Snapdragon)] cvxda:
Lentis board revisions < 6?

Please, only lentislte users, and only if the board rev is < 6.

For a kernel code change I need to know if somebody here is actually running a

lentislte with a board revision less than 6.

Please run this on the command line:

tr ' ' '\n' < /proc/cmdline | grep androidboot.revision

If the number printed after the equal sign is less than 6, please report back.

Thanks,

Corinna
[Galaxy S 5 Android Development (Snapdragon)] PhilCapron:
Battery drain

For those who are reporting big battery drain (100 to 5 in 12 twelve hours is big!), I can only say that my figures are averaging out at 0.2% per hour. This is from Better Battery Stats with wireless switched off. These big battery drains point to a faulty install or app(s). All you've got to do is find it. For that you'll need some time and patience.ATB.
[Galaxy S 5 Android Development (Snapdragon)] rollinrollinrollin:
[MENTION=4402027]PhilCapron[/MENTION]

People experience that drain when the phone is powered off.
[Galaxy S 5 Android Development (Snapdragon)] andreoide:
Except when booting in TWRP and shut down/power off from there......

Strange but a proven concept.

:cowboy:
[Galaxy S 5 Android Development (Snapdragon)] rollinrollinrollin:
[MENTION=5156684]andreoide[/MENTION]

Can confirm, this is it!
[Galaxy S 5 Android Development (Snapdragon)] 0x000eHx:
Your command wont show anything on my rooted Stock Android OS, cause in my /proc/cmdline there is no entry androidboot.revision.

I used this command

tr ' ' '\n' < cat /proc/cmdline

to show me all entries and I got an entry "board_rev=2" (without androidboot.revision in front)

Is that what you are looking for?
[Galaxy S 5 Android Development (Snapdragon)] TheFixItMan:
No - to install a custom rom you need a custom recovery

The ota lineage updates will reboot into twrp recovery to automatically install (if latest twrp version)
[Galaxy S 5 Android Development (Snapdragon)] O SAPHIA:
A bug I experience now since the latest 2 builds

Hello, dear LineageOS-builders and developers. I am using LineageOS now for over a month on my Samsung Galaxy S5 LTE+, and I was happy since then, but it appeared that the hardware acceleration or so wasn't really properly done, because my phone started lagging on games like Geometry Dash, and still does. However, I found a new bug: I can't charge my phone completely to 94%, because when you try to charge it complete, it just shows 94% and loses a bit more energy. I hope you'll get both the device optimizations and the battery bug fixed. Thank you.

Message by "O SAPHIA!", written on a Packard Bell Easynote TK850
[Galaxy S 5 Android Development (Snapdragon)] tomsche:
A bug I experience now since the latest 2 builds

Hello,

I can confirm the descripted issue. Since the last two two builds my phone charge to 94% not more. After downgrading to the build from 29.10.2018 I can charge the battery to 100%.

Regards, Tom
[Galaxy S 5 Android Development (Snapdragon)] 12345caravan:
Same for me since the last two updates.....max 94%.
[Galaxy S 5 Android Development (Snapdragon)] stirrer17:
Hi,

first of all: Thanks Corinna, for your brilliant work! I really appreciate my phone is still up to date and that is due to your hard work.

As [MENTION=5156684]andreoide[/MENTION] stated I am also facing the "no service" Problem.

I am not able to tell, wether it occured since the lastest updates, but while I am roaming right now, the problem became worse.

It seems to me that the underlying problem is not just occuring duringg reboot or booting, from scratch but also when connection is lost while travelling?

Greets

Stirrer
[Galaxy S 5 Android Development (Snapdragon)] js-xda:
I did not realize it until reading this but I have the same issue. So far I was wondering more whether the battery is aging and has issues charging the last few percent. What I can add is that I observe at 94 % a flickering of the green LED which I did not notice before. I am using an Samsung Galaxy S5 LTE+ (G901F) running 20181106 build until now.

Another topic: Has anyone some info what the difference between 2018112 build and 20181113 build is? I guess something was fixed but curious what and the changelog is empty.

Update 20:20: Update to 20181113 build does not change anything about battery charging being stuck at 94 %.
[Galaxy S 5 Android Development (Snapdragon)] Hellisonearth:
Samsung Galaxy S5 LTE+ (G901F). Confirming the battery loading issue. what was the update on 13. november lineage-15.1-20181113-nightly-kccat6-signed.zip (after the 12 november update) about? quick fix? there is no changelog. thx
[Galaxy S 5 Android Development (Snapdragon)] TheFixItMan:
Lineage os are now building all 15.1 roms daily instead of weekly

All 14.1 roms for older devices will now be built monthly instead of weekly
[Galaxy S 5 Android Development (Snapdragon)] andreoide:
Same here, battery max load 94%, maybe it is 100%, but showing only 94%. Idk
[Galaxy S 5 Android Development (Snapdragon)] Zubagy:
Hey ya'll....is it me or has there been 4 updates constantly for the previous days.... Even today,.... Recieved an update
[Galaxy S 5 Android Development (Snapdragon)] rollinrollinrollin:
[MENTION=5018077]Zubagy[/MENTION] Read download.lineageos.org/kccat6/changes

...daily builds now but if there are no commits it makes no sense to install them
[Galaxy S 5 Android Development (Snapdragon)] Zubagy:
True... Mine to charged up to 94% but in order to get t to 100%, I restart the phone in recovery then charge it from there,, once it clock's 100, I reboot it to system and boom.... Full charge.

But, but, I am running the update that was released on 14th... That was yesterday... This time the battery charges upto 86%....but I use the same trick to get t to 100%.

There is a new update today, let me download it and see how all goes.
[Galaxy S 5 Android Development (Snapdragon)] andreoide:
I'm going to download&install too. Good idea bro :svetius:

I see on the download.lineages.org/kccat6 on 12, 13, 14 & 15-november now daily new versions. I can't find changes about them.
[Galaxy S 5 Android Development (Snapdragon)] Zubagy:
I did, I did not see anything. On the change log though... Today's update has a few stuff.... But the previous has non.

And, and..... Let me ask this, every time I make a phone call and place the phone on my ear, the screen gets a time out... But wen I put it off my ear... T stays off.... U till I pass a thumb across the sensors again.... Thats wen it gets back on. Is there a fiz for that.... Because am sure all yall working fine. Am using the lentislte (galaxy S5 lte-a) korea
[Galaxy S 5 Android Development (Snapdragon)] andreoide:
I updated and hung the phone on charger but still it sticks @94% .

So that's no change.

Where you read about the changes?

And and ... I do not have the "bug" you describe...

Idk why you have that ...

My phone is the kccat6.

Salem :svetius: