yashsingh1/xdaforums huggingface dataset:
[Galaxy S5 Mini Android Development] fidoedidoe:
Hi [MENTION=8002612]Panzerknakker[/MENTION] (FYI: [MENTION=330757]spook[/MENTION]city ; [MENTION=4613083]rodman01[/MENTION]).

It's been a while since I've built a rom (and I'd be the first to admit I'm no expert), but after reading your post(s) I thought I'd help by giving you another persons perspective.

Last night my build using Spookcity's github repo completed successfully. This morning I bit the bullet and (dirty) flashed my build (lineage-16.0-20190515-UNOFFICIAL-kminilte.zip) over the previously installed Spookcity's build (April version - sorry forgot exact date, but it was pre "enable HWC"). As part of my flash process I upgraded to TWRP 3.3.0 then, from within TWRP, I wiped: Dalvik; Cache; system. Afterwhich installed the rom, lastest gapps and magisk 19.1 (in that order). I know youre well versed at all this (as I have used your 15.1 builds in the past). Anyway, the intent was to simply qualify exactly what I did, oh BTW My build environment is Ubuntu x64 19.04, phone is G800F. The phone *booted successfully*, with no sign of the slow boot loop you reported. I have *not* clean flashed the phone as it's my GF's, so nothing I can try either (without causing me greif).

I created a (overly converluted) bash script that automates my build process (see: github). I'm sure you'll have no trouble understanding what it does, but as far as I can tell it's how you defined your build process in an early post. The one difference being I sync additional repos by Spookcity such as: android_device_samsung_smdk3470-common; android_device_samsung_kminilte; android_kernel_samsung_kminilte; etc; etc.

If* you decide execute the script, then please modify the variable definitions declared at the begining to better match your build environment.

Do let me know if any of the above needs clarifying.

BTW - your modified boot5.img you mentioned in an earlier post, I'd like to try it out. Is that simply flashed as "boot image" via TWRP or do I replace the boot.img within the ROM zip file with boot5.img (does it need to be renamed?).
[Galaxy S5 Mini Android Development] Panzerknakker:
Thanks, will try your script, and come back. I build on debian stretch.

And yes, just flash boot5.img with TWRP as image to "boot".
[Galaxy S5 Mini Android Development] spookcity138:
Thanks a lot for the log. I will try to have a closer look when I am not on my phone. I just had a random reboot for the first time in a few days. Nothing to do with the keyboard though,but my guess is this may also be related to the HWC. It seems as (in my case at least) it is about 90% fixed. I have tried to find out exactly how this was fixed on the galaxy S7,but I haven't had much luck. It seems as though these commits may have been made in a private repo. Which would be a real shame. I have looked at other ROM threads in the herolte forum and while they all say in their newest changelogs that HWC has been fixed. The links to their sources show nothing useful. I will try to dig deeper. Perhaps I am just overlooking things. In the meantime,if ppl are having issues just disable hardware overlays in dev options. Depending on my findings and others comments about this over the next few weeks I will decide whether or not to disable HWC in the next build again (assuming I am unable to find a proper fix)

Thanks for the info. you can just choose flash image in TWRP and then flash the boot5.img
[Galaxy S5 Mini Android Development] Panzerknakker:
Hi [MENTION=3865771]fidoedidoe[/MENTION],

built from start with your script, same result, does not boot.

I suspect therefore something being wrong with my build computer environment (debian stretch) that nevertheless builds 14.1 without problems.

I will set up another PC OS and come back. This is too weird.
[Galaxy S5 Mini Android Development] fidoedidoe:
Okay, best of luck. One final thought, do you think my dirty flash is obfuscating the result? Might be trying dirty flash to rule that out a false positive on my side
[Galaxy S5 Mini Android Development] rodman01:
Finally I decided to try a new build after a couple of weeks. And before synching I updated my SDK versions. Then deleted all folders of my working tree, not the repos, only the folders below and forced repo sync. Build finished with success and the best of all: RR build is booting again. So in my case it was not any of the codes, I am sure there had been mixed up something or SDK had been outdated.
[Galaxy S5 Mini Android Development] Asgabat:
with the latest buid it reboots every time I watch video (
[Galaxy S5 Mini Android Development] SpicyM:
1 reboot when I was writing an SMS and 2 when I was using the stopwatch
[Galaxy S5 Mini Android Development] Panzerknakker:
Build boots now.

Unfortunately changed two things simultaneously:

- Went to another machine (OpenSuseLeap 15.0)

- Did not use ccache

So the exact reason is unknown.
[Galaxy S5 Mini Android Development] fidoedidoe:
Glad you're resolved, even if the true cause isnt known.

Slightly OT. will you continue to build/publish 'hybrid' kernel (P + cherry-pick custom N) as/when there are changes. Are you open to sharing how you put your patch files together (here or by PM)?
[Galaxy S5 Mini Android Development] Panzerknakker:
Yes, when I build a kernel for myself I will share it here.

And yes, will put in on github.

In the meantime you can patch P kernel yourself

Apply 0001-prepare-cpufreq.patch

From ba57ae39df8ad9f175b53657539db7d771b76fd7 Mon Sep 17 00:00:00 2001
From: Markus Reichl <m.reichl@fivetechno.de>
Date: Mon, 13 May 2019 15:51:56 +0200
Subject: [PATCH 01/11] prepare cpufreq

Change-Id: I52dcb939dcfe7c9aa156d8423d491587c9ad30bc
---
drivers/cpufreq/exynos3470-cpufreq.c | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/drivers/cpufreq/exynos3470-cpufreq.c b/drivers/cpufreq/exynos3470-cpufreq.c
index be02a7d386c..22f7bd6b0cf 100644
--- a/drivers/cpufreq/exynos3470-cpufreq.c
+++ b/drivers/cpufreq/exynos3470-cpufreq.c
@@ -549,11 +549,11 @@ static int __init set_volt_table(void)
}

if (samsung_rev() >= EXYNOS3470_REV_2_0) {
-	max_support_idx = L1;
-	min_support_idx = L11;
-	exynos3470_freq_table[L12].frequency = CPUFREQ_ENTRY_INVALID;
-	exynos3470_freq_table[L13].frequency = CPUFREQ_ENTRY_INVALID;
-	exynos3470_freq_table[L0].frequency = CPUFREQ_ENTRY_INVALID;
+	max_support_idx = L0;
+	min_support_idx = L13;
+	//exynos3470_freq_table[L12].frequency = CPUFREQ_ENTRY_INVALID;
+	//exynos3470_freq_table[L13].frequency = CPUFREQ_ENTRY_INVALID;
+	//exynos3470_freq_table[L0].frequency = CPUFREQ_ENTRY_INVALID;
} else {
max_support_idx = L0;
min_support_idx = L10;
--
2.11.0

Then apply the other patches, they are unchanged cherry-picked from N_custom.
[Galaxy S5 Mini Android Development] Asgabat:
Guys how should i fix reboot problem?
[Galaxy S5 Mini Android Development] spookcity138:
Settings -> system -> developer options -> disable hardware overlays. This resets on reboot though.

I will probably disable HWC again for next build unless I have better luck in figuring out the full issue before then.
[Galaxy S5 Mini Android Development] Türschloss:
This is not fixing reboots using Spotify. Only the intervals of the reboots. :confused:

Thanks
[Galaxy S5 Mini Android Development] spookcity138:
Hmm,strange. And this used to work OK in previous builds? If so,I suggest just flashing the older build before HWC was enabled. This can be found by clicking the date in the changelog section of the main post.
[Galaxy S5 Mini Android Development] elsterkrug:
I've also had sporadic restarts lately. HW overlays is disabled. Nevertheless, it always comes back to reboots, regardless of video playback. It happens in all programs without recognizable pattern.

The Wlan crashes are just as sporadic. Sometimes it runs stable for a very long time, even in standby, then again completely unstable and constantly reconnects. Too bad, otherwise the ROM is great and I would like to stick with it. Thank you for the development and I hope for the small mistakes there are also solutions.
[Galaxy S5 Mini Android Development] Ti64CLi++:
In the latest build before HWC has been enabled I also have a lot of reboot when I watch video
[Galaxy S5 Mini Android Development] spookcity138:
Yeah,its a strange issue. I had a couple of reboots within 20 minutes while watching videos in the browser app. Then I decided to connect to adb to try and get a log...I spent a good half-hour and couldn't get it to reboot for anything. It is very sporadic indeed. Which makes it more difficult to try to solve. [MENTION=4613083]rodman01[/MENTION] also spent some time looking into this. At this point we are just unsure. I have reverted my commits enabling HWC,so next build will have it disabled again. I will try and get a new build up this weekend.

The same thing really with your Wlan issues. It is so difficult to solve these sporadic issues and this one i don't even have,so hopefully either LOS updates or some kernel commits I have been cherry-picking will eventually get this solved.

Hmm,strange. I don't think I had a single reboot in many months of using this ROM until i enabled HWC. Not sure why this is for you. Perhaps a new build over the weekend will solve it for you.
[Galaxy S5 Mini Android Development] Ti64CLi++:
I hope so.

Thank you again for your great work :)
[Galaxy S5 Mini Android Development] Morgan_Freeman:
So on the 11/5 build my phone at random time intervals only displays a blue rectangle at the top of the screen with the clock inside it. The only way of fixing that is taking out the battery and forcing a reboot (power menu doesn't work anymore). Before, on the April build that didn't happen anymore, though I don't remember if I changed any settings to prevent that, or it just didn't happen then. If anyone else has been experiencing this and maybe has found a solution, please let me know! Thanks in advance
[Galaxy S5 Mini Android Development] a-dead-trousers:
Thats "flip cover". Just disable it in the settings and you are good.
[Galaxy S5 Mini Android Development] a-dead-trousers:
Home screen crashes after changing wallpaper

hi @ all.

I've encountered a very odd problem:

After many considerations I decided to switch from my old 14.1 to 16.0. Because I didn't want to start fresh and loose all my data (SMS, Signal securitykey & chats,...) I decided to try a dirty flash. So I started with a backup of the old system using TWRP (This saved my life multiple times in the upcomming evets). Then I flashed the latest rom (20190513), latest Gapps and Magisk. After a reboot I had a little trouble with getting the Pixel launcher to work. But this obviously is a common problem (https://github.com/opengapps/opengapps/issues/727) and the fix was quite easy to implement. After that I checked if the system is stable enough for my daily routines and everything was running smoothly. Next I started to temper with various settings (dumbass) and suddenly I wasn't able to unlock my phone anymore. After swiping my unlock pattern the screen went black and after five seconds I was back at the unlock screen. Even entering the setting from the lock screen was impossible. Because I previously had problems with the launcher I suspected this was the cause. So I tried to change or uninstall it using either adb or TWRP but nothing worked. After some time and many failures I decided to start again (Thank god I did a backup). Restore, Installing ROM, Gapps, Magisk and I was back on track. Now being cautious after every setting I changed I check if the crash reoccoured. This way I found out that changing the wallpaper of the home screen was the culprit. Because I didn't find an other solution for changing the wallpaper from adb or TWRP I once more started from scratch. And this is where I stand now.

I'm quite sure that the wallpaper I previously had was from lineage itself. I'm also quite sure that the new wallpaper I used is from the gapps wallpaper package. Right after changing the wallpaper the home screen was working normally that is why I didn't notice the problem right away. After putting the phone away and then picking it up again it was locked and now I wasn't able to unlock it anymore because the home screen was crashing.

Long ago I used the wallpapers from gapps within my old 14.1 and didn't have any problems with them. Then suddenly after some time they seem to have vanished from my phone. I thought this was due to some copyright claims (It was that time with the EU IP lawsuits). So I didn't check any further and used one of the default lineage wallpapers instead. After changing to 16.0 and installing gapps again the wallpapers were back and so of course I changed them (a bad decision).

Now that I know what the problem is I want to know why changing the wallpaper is (currently) a no go. Preferably also finding a solution for this.

Is anyone willing to help me and testing changing the wallpaper while using pixel launcher to do so? Maybe also trying the same with other launchers (Google Now, Trebuchet, ...). I'm also currious if doing a dirty flash or a clean install makes any difference.

P.S.: Don't forget to do a backup ;)
[Galaxy S5 Mini Android Development] a-dead-trousers:
Changing the background of home screen triggers this problem.

Regardless which launcher I used (Trebuchet, Google Now or Pixel) as long as I changed the wallpaper either by long pressing on the screen or through settings I cannot return to the home screen after locking my phone. Also the before mentioned google wallpapers are not the culprit because even using one of my own pictures triggers it.

Can anyone tell where and how I should start logging this?
[Galaxy S5 Mini Android Development] spookcity138:
Interesting issue. Almost certainly related to dirty flashing over lineage 14.1, but you already know that. You might need to bite the bullet and do a clean install if you want to switch to this ROM.

As far as getting a log, I guess since you can't really get the phone working after locking it you'd have to connect to adb shell via a PC.

I can say that lineage has switched to using their own wallpaper provider in my latest build ( I will most likely not get to posting this up until tomorrow) I highly doubt this will change your situation much, but stranger things have happened.
[Galaxy S5 Mini Android Development] a-dead-trousers:
hi.

After two days of trial and error I took the bullet. With cloudstorage (for settings & data) the transition was much smoother than I initially expected. So now I'm a happy little LineageOS 16 user. :angel:

Anyway, thanks for your ongoing support!

P.S.: I already had the occasional (probably hwc related) reboot. I had Keepass running and was entering a passwort for a game and as soon as the overlay for storing/retrieving username and password showed up, the phone had some hickups and in the end rebooted. On other apps this worked without problems. So I will put this under the "random" folder and ignore it for the time being.
[Galaxy S5 Mini Android Development] spookcity138:
Updated

Changelog

* Synced LOS sources
* Latest security patches (June 2019)
* Disabled HWC (again)
* Merged latest lineageos/hardware/samsung sources into our hardware/samsung repo
* Fixed Netflix "device not compatible error" (Thanks to @SpicyM)
* Fixed LiveDisplay (Thanks to @rodman01 for his help) - NOTE: LOS is going with night mode as opposed to LIveDisplay. I have reverted some commits to keep LIveDisplay for now. This may or may not change in future builds.
* Updated power profile (Thanks to @rodman01)
* Bunch of kernel commits (wireless,security,ETC)
* Updated GMSCore prebuilt to latest for the microG build

Enjoy!
[Galaxy S5 Mini Android Development] Ti64CLi++:
Wow thanks a lot spookcity138 and rodman01 !!

Just with curiosity, how did you fix the Netflix bug?

And, now I have another problem which I had already in the previous version. I can't manage to install c4droid v6.97, or more precisely, the apk won't install, and I get a message which says that the apk cannot be installed, though this version has been specifically built for android 9 :(
[Galaxy S5 Mini Android Development] spookcity138:
The Netflix issue was solved by adding 2 proprietary blobs from another Samsung device to our vendor repo. [MENTION=9872116]SpicyM[/MENTION] got this working and sent me the info,so all credit to him.

Sorry,no clue about your issues with installing c4droid. I can't imagine that it's related to the ROM,but it is possible. I wish you luck with it.
[Galaxy S5 Mini Android Development] a-dead-trousers:
Hi.

First of all most of the ROM seems pretty stable. Even the previous HWC enabled one was running smoothly on my phone (desipte the occacional reboots when I did 3 to 4 things in parallel).

In comparison to 14.1 some changes "under the hood" seemed to have improved the overall handling (at least for me) quite a lot:

A rather anoying bluetooth problem I encountered was (finally) fxed. While pairing my phone to my car the onboard sound system couldn't display the current songtitle, tracknumber and so on. Now it works again like before the infamous "bluetooth security fix" back in 2017/2018 (I think).

The last 3 to 4 builds of 14.1 by [MENTION=8002612]Panzerknakker[/MENTION] seemed to have drained the battery a lot faster then before. I was down to only 1 day from previously 3 days. Now with 16.0 the drainage seems to be gone. 1 and a half days running and the battery is still araound 60%.

Despite all the other already mentioned issues with this ROM I encountered another one:

The fingerprintsensor on my phone is currently only able to store 3 prints. Everytime I try to register another one the app says "error during the registration". I don't know if thats a limitation of our rather old hardware or something else. At least It would be usefull to have another error message. Maybe there is some build-configuration/setting to tell the app that the hardware is only able to store X numbers of prints. Also every now and then the sensor seems not to "wake up" in time for unlocking the phone. I think back in 14.1 [MENTION=6225744]hennymcc[/MENTION] was able to "fix" this by waking up the sensor at least when the pattern/pin input showed up. So you weren't able to directly unlock your phone with fingerprint from deep sleep but at least you were able after "activating" the screen.

wkr ADT
[Galaxy S5 Mini Android Development] aelfinn:
First impressions are really good. Even the battery life seems to be rather decent. Anything special you’d like us to test?
[Galaxy S5 Mini Android Development] spookcity138:
Many thanks for the feedback and glad to hear it's mostly working out for you. I will try to have a look into the FP sensor issue. Honestly,I don't think I've messed with it at all for this ROM aside from I believe changing some permissions. I will see what I can do about this issue when I have some time.

Well,aside from the known non-working things (HWC,NFC,ETC) the only real thing is the WiFi disconnects that some have. I have never had this issue,but have been cherry-picking kernel commits to hopefully get this solved...and obviously also the reboot issues. This should no longer happen now that the HWC has been disabled again (I haven't had one yet) but certainly let me know if you do.
[Galaxy S5 Mini Android Development] flortsch:
The current rom works very well, battery time is also very good :) And since the second HWC-disabled build, reboots caused by UI quirks are gone. Besides the known issues I found that for me, video recording is not working with any app, also not with the recommended app in the first page of this thread. To me it looks like the app hangs in an internal call while the video is saved or stored to disk. I'll try to investigate this further.
[Galaxy S5 Mini Android Development] spookcity138:
Again, thanks for the feedback. Interesting that video recording isn't working for you though. I just tried using footej camera and it worked OK. I'm not sure why it wouldn't for you, but there def are still issues with the camera/video that I've spent a little time trying to look into without much luck as of yet.
[Galaxy S5 Mini Android Development] flortsch:
Maybe it's related to the fact that I was lazy and dirty-flashed your last HWC-disabled build. I will try a full wipe though :D
[Galaxy S5 Mini Android Development] Morgan_Freeman:
I'm not quite sure if this is related to the rom, but I have been unable to install apps that are larger than 150MB (guesstimate). For example I couldn't install angry birds 2. After the download has finished, it simply says: unable to install application. Not sure if this has been an issue in previous versions, because I haven't tested it out on there. Thanks in advance for the help
[Galaxy S5 Mini Android Development] spookcity138:
I just tried this with angry birds 2. It installed OK via the apkpure app as I'm using the microG build (no playstore)

I can't really say why you're having issues. Storage problem? Playstore related?

Perhaps try to grab a log to figure out what's happening.
[Galaxy S5 Mini Android Development] bravur:
Is there any chance to support NFC? (It would be beneficial to connect a blood glucose meter.)

Thank you for your great work!
[Galaxy S5 Mini Android Development] elsterkrug:
The new ROM has been running reliably for a few days. No restarts. Thanks a lot for this. The Wlan crashes, however, are still there, irregular, but still, especially in standby. What experiences do others have with their Wi-Fi?

Except for the occasional Wlan crashes, the ROM runs great and is fully suitable for everyday use, thank you very much.
[Galaxy S5 Mini Android Development] spookcity138:
Very unlikely that NFC is ever going to work with this ROM sadly. I've looked into this, but it would require a fair amount of work and more skill than I possess. Our chipset isn't that common, so unless some dev decides to fix NFC for our chipset or I can get a prebuilt from Lineage 15.1 working - I've tried without luck, NFC on Android 9 isn't going to work.

Thanks a lot for the feedback. Sad to hear the disconnects are still there. Strange issue. Hopefully with time I'll stumble upon a fix.
[Galaxy S5 Mini Android Development] Morgan_Freeman:
I tried it using the Apkpure app (actually didn't know that existed, thanks for enlightening me) and now everything is working fine. So it seems to have been a problem with the play store. Thanks anyway
[Galaxy S5 Mini Android Development] Tureilu:
WI-FI

Since I activated Auto-Reconnect WI-FI with Location (Energy-Save Modus) enabled WI-FI Connection isn't loosing connectivity anymore.
[Galaxy S5 Mini Android Development] aelfinn:
I can’t seem to find that in the settings. Any pointers? :confused:

Edit: Oh, I should say that my device is on crDroid v5.5 (20180610)…
[Galaxy S5 Mini Android Development] elsterkrug:
[MENTION=4672508]aelfinn[/MENTION] I also find no attitude for the flipcover. Under 14.1 I could turn it off. Here I helped myself so that I deactivated the app flipflap.apk with TB.
[Galaxy S5 Mini Android Development] Mint Julep:
It's called "smart unlock" if I remember correctly
[Galaxy S5 Mini Android Development] elsterkrug:
[MENTION=9938146]Tureilu[/MENTION]: I tested the settings. It seems to be more stable. Of course, it is at the expense of the battery life. In standby my phone still loses the connection sometimes and connects only when unlocking. [MENTION=8518458]Mint Julep[/MENTION]: Under this setting, I find nothing to turn off the flip cover. At 14.1 there was a separate item in the settings called "Flipcover". This does not exist at 16.
[Galaxy S5 Mini Android Development] warhook76:
[MENTION=9741880]elsterkrug[/MENTION]. I found it in conectet Devices!

Greetings

Gesendet von meinem SM-G800F mit Tapatalk
[Galaxy S5 Mini Android Development] elsterkrug:
[MENTION=6973316]warhook76[/MENTION]: There I only find settings for Bluetooth, but not for flipcover.
[Galaxy S5 Mini Android Development] Peter_Petersen:
[MENTION=9741880]elsterkrug[/MENTION]

hey,

i found this on 'connected devices --> connection settings --> smart-cover'

(Verbundene Geräte --> Verbindungseinstellungen --> Smart-Cover)