yashsingh1/xdaforums huggingface dataset:
[Galaxy S5 Mini Android Development] spookcity138:
Thanks for the feedback...

- Yeah,battery life seems to be rather dependent on the user. It seems to be somewhere between horrible and good :D

My battery life is very acceptable,but some have said otherwise. I'm not fully sure what would cause the battery life to be so drastically different for some users though.

- The only options for battery is the standard icon and in settings -> battery you can choose to show text. I'm not sure if the other battery styles are going to make it to Pie or not.

- I have not built the LiveDisplay HAL on this ROM. I have tried in the past without luck. There are a few versions of LiveDisplay 2.0. I've tried to build a couple (including the obvious Samsung version) and both result in a black screen upon boot. The log was complaining about missing proprietary libs,so IDK. I think maybe we are missing something on the kernel side for this to work. Perhaps I'll try to build version 1.0 and see if that works.

Also,I saw you commented about the Netflix fix that was posted a bit ago. There is something more to it than what was posted I think as I have tried to get it to work this way with no luck. We already have the libwvdrmengine lib,so I added the libdrmclearkeyplugin from out stock ROM. Tried Netflix and it didn't work. Then I grabbed those same 2 blobs from the S5 plus just out of curiosity and it still didn't work. So if [MENTION=9872116]SpicyM[/MENTION] sees this i would love for some more info on this as I would like to fix it if possible.
[Galaxy S5 Mini Android Development] Astoralis:
Thank you spook so much for this ROM im using it for some months now. Its pretty awesome and runs fine.:good:

I got some issues but they are not to bad:

1. Batterylife is kinda short. Most times its good enough to get over the day but sometimes batterydrain is super hard and depletes around 40% in 1h. Its really rare and i cant reproduce it but with powerbank not a real problem, just a bit annoying sometimes, restating fixes this.

2. I got hard stutters while charging the phone. The keyboard is delayed super hard sometimes when i try to delete a letter it takes 1-2 sentences... generaly it just stops reacting but do all the typing "at once" after the lag. When i unplug its normal again, but loading and typing is kinda impossible. EDIT2: Problem disappeared after flshing the new modem... Im happy but confused

3. My Notification-LED is broken. With the last build it worked fine, then i flashed newest build and it just stoped working. I didnt really care, dont need such stuff, but then suddenly after 2 weeks and some restarts ofc. it started glowing afeter a restart and doesnt stop. I cant change color or anything its a bit annoying in the night but not a real problem. Noone else wrote something about that, maybee its only me with that random behaviour. Edit: After flshing newest baseband with Odin it seems to work properly now. Didnt wipe cache/dalvik or anything... That doenst make much sence imo, but im not a phonedev at all, so...

4. The problems with WLAN and moblie data some people already wrote about. Nothing new from my side, but after reboot mobile data works fine again. flightmode on/off doesnt do the trick sadly. Edit: changed to your modem, gonna post an update if DC,s wont occur anymore

5. Camera, well i dont care about that, just wanted to mention^^

Thank you anyways for saving our phones! Super awesome work you did there.:good:
[Galaxy S5 Mini Android Development] Juanube:
Thanks for keeping alive our S5mini!

Great job
[Galaxy S5 Mini Android Development] vjgrace:
Thanks for the suggestion Spookcity. Tried from the latest modem downloaded from Sammobile (G800FXXU1CPI1, build date 10-29-2018) and flashed it after flashing this latest rom (had to use the older TWRP to flash the modem, but easy enough to reflash the latest TWRP). I found after doing this and using this rom for 3-4 days, not one data disconnect...can't guaranteee that this was the resolve, but it appears that it looks like it helped.

Another issue/question: when calling or receiving calls and immediately going to speakerphone others can't hear my voice (can also randomly occur and often with increased background noise...issue not apparent on nougat)...additionally, if I was to answer the call or call out, not on speakerphone and then transition to speakerphone the success is better (however still increased background noise). If I don't use speakerphone, no issues whatsoever.

Just wondering if others were having this issue or if there was a resolve as I use speakerphone regularly.

Thanks so much Spookcity for doing what you do to keep this phone current, I am so appreciative. :good:
[Galaxy S5 Mini Android Development] MvC89:
Hello,

due to my poor english, i did not understand which baseband version (G800FXXU1CPI1 or G800FXXU1CRG3) you are using for working mobile data. Would you please clearify this for me?

I flashed this promissing ROM three days ago having baseband G800FXXU1CRG3 and stockROM before. Can't get a mobile data connection since moving to this lineage-ROM.

Thanks in advance
[Galaxy S5 Mini Android Development] ruebenkraut:
Interesting. I've just re-flashed to stock rom, and while I was on the second most recent baseband before (ending on CRB1, according to another thread on here), I'm now on CRG3 like spookcity. Fresh from the minor success of having not screwed up re-flashing the stock rom with heimdall, I'm tempted to try lineage again straight away to see if this has resolved the issue. Then again, MvC89 is on the same version and seems to have issues (though I would sometimes get mobile data in the past, it was more a general network problem.) Mobile data on stock is pretty crap still, but at least I can receive calls. Just to make sure, if I flash lineage now, the updated baseband will remain, right?

gonna use the phone for a couple of days to make sure I get reliable signal on stock and there's no hardware fault , then try again and see if the new baseband resolves the problem.
[Galaxy S5 Mini Android Development] aelfinn:
Using default settings, GPS seems to be borked (testing with GPS Test). Very few satellites, some called “00“ or “?”, some with wildly implausible signal strength values of over 120, no fix. On the latest XenonHD, everything is fine on the same handset, fix within 10 seconds.

Has anyone tested different GPS conf files or any other tweaks?
[Galaxy S5 Mini Android Development] Brummschaedel:
Don't know, wether it might help you, but there was an idea in the lineage 14.0 thread: https://xdaforums.com/showpost.php?p=75037334&postcount=1585

For me, GPS works fine, first fix is slow, but then it is quite stable.
[Galaxy S5 Mini Android Development] flortsch:
I also tweaked my gps.conf to get a faster fix. Here is a good guide which explains why some of the example gps.conf files out there are wrong and how a proper conf file should look like: https://rootzwiki.com/topic/28989-the-end-all-be-all-guide-to-your-gps/
[Galaxy S5 Mini Android Development] dank2019:
Hi all,

first of all, I want to thank spookcity138 for all the effort done so far to keep my small phone alive.

Most of the things are working properly. But I've one issue no one else reported so far. My phone app is crashing repeatedly. Crashing means, the upper screen is complete blue, the lower black and I can only answer phone calls - nothing else is working anymore. In order to fix this, I have to do a hard reset.

I have 2 of the minis with the latest build. The crash happened on both. On one more often then on the other one. Nevertheless, both are affected.

Any idea, what I can do? Sometimes, I have to restart my phone 5 times a day.

Thank you

Daniel
[Galaxy S5 Mini Android Development] metterschling:
Daniel, please search this thread, this was discussed before. Hint:you need to disable "flip cover" in the settings.
[Galaxy S5 Mini Android Development] s5minimalist:
I'm wondering about the messaging app (SMS): On my old Phone (CM12) the contacts used to have different colors, on this Rom every contact/thread is green? Does that have to do with the introduction of dark mode into the Messaging App?

Another thing is that I don't seem to get notifications for unread SMS via the Notification LED. Already tried to add App-Specific settings in the Notification light settings (only available here via Settings Search), but to no avail. Anyone else experiencing this?

Thanks, sorry if drifting OT
[Galaxy S5 Mini Android Development] Kenarude:
So I reverted back to the standard build (many issues with microg, apps crashes, missing libs, storage issue, gps issue, .... It can come from me, not knowing how set microg configuration) adding gapps nano and that fixed move to internal storage issue.

Video recording still not working well.

Thank you.
[Galaxy S5 Mini Android Development] Panzerknakker:
Building

Hi Rick,

tried to build it with.

#!/bin/bash
repo sync
cd device/samsung/smdk3470-common/patch
./apply.sh
cd ../../../..
source build/envsetup.sh
lunch lineage_kminilte-userdebug
croot
mka clean
mka bacon

Build runs successfully but the phone keeps stuck on booting this build within the Samsung logo.

Flashing the kernel (boot.img) from this build as image with twrp onto your last build boots.

So it is something in lineage?

Thanks,

--

Markus
[Galaxy S5 Mini Android Development] spookcity138:
Hey Markus,

Hmm,thanks for the heads up. I am not real sure what the issue is. I would have to think it does indeed have to do with LOS sources though. Hopefully this is a simple issue to resolve as I am just now planning to build an update to release tomorrow or so and really don't have a ton of time to look into fixing things. I am going to build in a bit,so we will see. Fingers crossed. I'll report back when I find something out.

Follow up:

My build boots without issues,so it must be some weird "hiccup" or something with your last build. I do not know what else it would be. I did have a bunch of kernel commits (that I just pushed) but it would be an amazing coincidence if that was the problem as the commits were for other things (wireless,security stuffs etc)

Also,I always do a clean flash. Not sure why this would suddenly be needed,just throwing that out there. Perhaps a clean build will solve this for you as I have no other local changes.

I will post my updated builds tomorrow sometime.
[Galaxy S5 Mini Android Development] spookcity138:
updated

Didn't have much time at all this month to look into the remaining issues,so a smaller changelog. Mostly just kernel commits as a start to hopefully fix the WiFi disconnects that a few are having.

Update on remaining known issues:

* HWC -Still no idea how to fix this. It seems to only crash with certain popups ( caused by libdisplay and surfaceflinger) I have not found any other devices with this issue. I have looked into it a bit more with no luck. Not sure this will get fixed unless it miraculously fixes itself with source updates.

* NFC - Good chance this will never work.

* SELinux - Unless someone else comes on board to do this or I find A LOT of free time this will also more than likely never work.

* Camera/video recording -What to say, I don't know what the issue really is with this. i will look into this more when I have time,but have no idea if this will ever get any better than it is now.

* WiFi disconnects - Only a few seem to have this (I do not) Its a strange issues an I am currently unsure of the cause. Hopefully some of the new kernel commits will have some effect.

* Mobile data issues - This is a somewhat recent issue that has been brought up. I have no issues with mobile data,but some apparently do. No idea right now what the issue is. My suggestion is to try a newer baseband if you have these issues. Perhaps even go as far as flashing the latest stock Samsung ROM before flashing this one.

* GPS - while it mostly seems to work (for me at least) it is nowhere near perfect. In honesty I have not done anything really to GPS for Pie. I will look to improve this in future builds.

Changelog

* Synced LOS sources
* Latest security patches (May 2019)
* 100-ish kernel commits (Mostly wireless,HID and security related things)
* Added libdrmclearkeyplugin proprietary blob (A start to fixing Netflix issues I think)

Enjoy :good:
[Galaxy S5 Mini Android Development] Mint Julep:
Hey spook!

I used your roms for 2 years before moving to G930F and I'm very grateful for your work.

I know that G93x have the same HWC issue on pie and that someone is working on it (they claim he's close to solve the problem. A matter of weeks apparently)

I'm no dev at all, but maybe if they solve the problem for this device, it could help you.
[Galaxy S5 Mini Android Development] spookcity138:
Hey,thanks a lot for that info! I couldn't find any other devices in my searching with this issue. Apparently I didn't search well enough :D

Hopefully when/if they fix this it will be something easily translated over to this device. I will keep an eye on their progress. Thanks again!
[Galaxy S5 Mini Android Development] Mint Julep:
Hey

Ivan just posted a build with working HWC on LOS 16 for G93X

Hope it will help ?
[Galaxy S5 Mini Android Development] spookcity138:
Many thanks for the update. I have looked around and am not 100% sure how he fixed it,however I have found a small temporary patch committed a few days ago in the trelte-common repo that has worked. Dumpsys SurfaceFlinger output shows HWC is enabled and in my short time testing I have not experienced any reboots. So it seems as if this is solved. Thanks a ton for pointing me in the right direction! I really appreciate it.

If I find the time I will try to post a new build with working HWC soon.
[Galaxy S5 Mini Android Development] Panzerknakker:
Building

Hi Rick,

Tried from start today, build builds successfully, but does not boot.

Your build boots fine.

The kernel from my build runs fine when flashed onto your build.

repo init -u https://github.com/LineageOS/android.git -b lineage-16.0
repo sync
git clone https://github.com/Spookcity/android_.repo_local_manifests -b P .repo/local_manifests
repo sync
cd device/samsung/smdk3470-common/patch
./apply.sh
cd ../../../..
source build/envsetup.sh
lunch lineage_kminilte-userdebug
croot
mka bacon

Any idea?

Has somebody else built successfully?
[Galaxy S5 Mini Android Development] spookcity138:
Hmm,very strange. I honestly have no idea sorry. Perhaps clear your ccache if you use that? I don't have any uncommitted local changes,so I'm not real sure what the issue would be. Unless I messed up the commits when I updated my local manifest? Are you sure all of the correct repos are being downloaded and going in the proper locations? I'm curious as well if anyone else is building if it has worked for them. I really have no clue. Sorry,wish I could be of more help.

Another Update

HWC enabled and working.

Changelog

* Enabled HWC - Credit to Lukas0610 for a temporary patch (with thanks to @Mint Julep for pointing me in the right direction)
[Galaxy S5 Mini Android Development] Morgan_Freeman:
Minor bug in Titanium Backup (TB).

In the TB app the "Preferences" button, where you can specify the backup location for example, is missing. On a Resurrection Remix Rom the menu was there, I haven't tested it on any other Rom.

Thanks in advance for the help!

Edit:

Just found out you can access the Preferences over the "Problems?" Button
[Galaxy S5 Mini Android Development] elsterkrug:
[MENTION=7065337]spookcity138[/MENTION] Thank you for your work, the ROM is getting better.

I have the last two ROM's from 12. and 13.5. Installed. In terms of wireless stability, there seems to be improvement after the first two days. The connection aborts are rare, but not completely gone. Also, the connection seems to be relatively stable in the standbay and not always break off, but only rarely.
[Galaxy S5 Mini Android Development] rodman01:
I have the same problem with my latest RR build weeks or even months ago. I had not dived deeper in this problem, because of several reasons (time, Motivation, etc). Anyways, I remember at the very first of my build tries for the S5 mini, I got strange build errors and after changing the build command from make or mka to brunch the errors where gone. Don't know yet whether this could also solve the boot problem, but spook: which build command are you currently using? And maybe on the weekend I will sync my sources again and also try a new build with the fixed hwc. also to check whether the boot problem is still there. Many thanks spook for your effort and your support for this device.
[Galaxy S5 Mini Android Development] spookcity138:
Interesting, i don't do anything special when I build. Just apply patches,change back to main folder...then run source ./build/envsetup.sh -> lunch lineage_kminilte-userdebug and then mka bacon. i never croot,but that's not gonna be the issue. I am at a loss honestly. I am very curious what the issue may be at this point as well. Please keep me posted if you figure it out,thanks.
[Galaxy S5 Mini Android Development] mongo0:
Many thanks for all your hard work and efforts to keep this device going!

I can report that Crdroid and AEX Pies build and boot fine.
[Galaxy S5 Mini Android Development] Panzerknakker:
Could not get my builds out of the slow bootloop.

At least here is boot5.img a OC-Kernel:

https://www.androidfilehost.com/?fid=1395089523397965635

This is from Spookcity's P kernel branch, enriched with some of his N_custom patches.

Kernel Adiutor Mod works on the voltages.

0001-prepare-cpufreq.patch
0002-1.6ghz-OC-and-initial-voltage-stuffs.patch
0003-voltage-table-access.patch
0004-GPU-OC-to-533mhz.patch
0005-GPU-OC-to-600mhz.patch
0006-CPU-voltage-control.patch
0007-lib-int_sqrt.c-optimize-square-root-algorithm.patch
0008-af_unix-speedup-proc-net-unix.patch
0009-lower-ARM_MAX_VOLT.patch
0010-GPU-optimization-flags.patch
0011-audit-Make-logging-opt-in-via-console_loglevel.patch
0012-audit-No-logging.patch
[Galaxy S5 Mini Android Development] spookcity138:
Thanks a lot for building and sharing this. I hope you're able to sort out your build errors. So confusing. You could find out exactly what is going on by connecting to adb shell. You need to edit the common.mk file within the vendor/lineage/config directory before building though. Because although I added a bunch of adb props. I apparently didn't add the proper one(s) to disable adb authentication. I ran into this when I was messing with updating some proprietary graphics blobs and was getting bootloops. I needed to edit this file to enable adb connection without authentication. There is certainly a better way,but this was the fastest and easiest at the time.If you decide to do this just change this:

From:

ifeq ($(TARGET_BUILD_VARIANT),eng)
# Disable ADB authentication
PRODUCT_SYSTEM_DEFAULT_PROPERTIES += ro.adb.secure=0
else
# Enable ADB authentication
PRODUCT_SYSTEM_DEFAULT_PROPERTIES += ro.adb.secure=1
endif

To just:

PRODUCT_SYSTEM_DEFAULT_PROPERTIES += ro.adb.secure=0

Then connection will be no problem.. This is something I will look into fixing at some point.
[Galaxy S5 Mini Android Development] elsterkrug:
Unfortunately, I was happy too early. There are still very frequent Wlan crashes. And also the problem that breaks off the wlan in standby and reconnects when unlocking. How about the others who had problems with the wifi? What can you report?
[Galaxy S5 Mini Android Development] mongo0:
Well, I'm not sure if it still persists. In my office wifi signalhas always been not that good and at home I can't tell for now...

However, I can see that at least dhcp lease time isn't honored by the s5mini. I'm running dnsmasq and set lease time for 8h. But in fact, there are DHCPDISCOVER every 2-3 hours during the night.

Maybe someone else can confirm this, since I had similar issue with AppleTV and it could be just my router..
[Galaxy S5 Mini Android Development] SpicyM:
I just put two files libdrmclearkeyplugin.so & libwvdrmengine.so (from a lineage 16.0 rom for S5 Gxxx) in /system/vendor/lib/mediadrm/ but maybe only lbdrmclearkeyplugin.so is needed.

A restart is necessary. No need for a Netflix account to test.

I have also Magisk 19.1 & MagiskHide 4.01-v52

I sent both files to spookcity138
[Galaxy S5 Mini Android Development] SpicyM:
I just flashed lineage-16.0-20190513-UNOFFICIAL-kminilte and the only thing i had to do was replace the 2 files. They were from 2009. I tried only libdrmclearkeyplugin.so but both are necessary.

No restart required.
[Galaxy S5 Mini Android Development] Friedensfurz:
Hey [MENTION=7065337]spookcity138[/MENTION] , Google has a tool called audit2allow and what it does is it collects the SeLinux violations in Permissive mode and auto-generates a valid config. Enjoy ;)
[Galaxy S5 Mini Android Development] spookcity138:
Many thanks for this and for the 2 files. I will add them and include them in the next build.

Wow,well isn't that brilliant. Thanks a ton for that info. I will look into this and if i can sort it out hopefully we can knock this off of the not working list too.
[Galaxy S5 Mini Android Development] ben smith:
Hi [MENTION=7065337]spookcity138[/MENTION].

I'm testing the latest build and it's crashing a lot.

Android gets stuck when it pops up the virtual keyboard and then soft reboots.

I bet it's the HWC patch or something else since the previous builds did not have this issue.

Would you perhaps consider disabling HWC for now?

Thank you for you for work on this ROM :)
[Galaxy S5 Mini Android Development] Panzerknakker:
No problems here.
[Galaxy S5 Mini Android Development] Andrea224:
No problem here too.
[Galaxy S5 Mini Android Development] spookcity138:
No problems here either. While this does sound like the problems HWC was causing before the potch I have to think this can't be the cause. Why it would work for most, myself included, but not you would be strange. Either way, you can disable HWC by enabling developer options ( settings -> about phone. Then click build number a few times) Then in developer options click disable hardware overlays.

This does reset after a reboot however, so you would need to do this anytime you reboot.
[Galaxy S5 Mini Android Development] Brummschaedel:
No problems with the keyboard for me. :)
[Galaxy S5 Mini Android Development] ben smith:
Thanks. I'm not sure what it is but yesterday the phone rebooted 3 or 4 times during the day.

I cannot replicate the bug reliably, but it always happened when the virtual keyboard was supposed to open (as I was starting to type a message in Telegram).

I can try to get a adb logcat from a crash for further info.

I'm glad it's working for everyone else, but then again it might be something that just doesn't get triggered easily :silly::confused:
[Galaxy S5 Mini Android Development] jori55:
no problems here as well