yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Mini Original Android Development] icescalar:
Wanna push #799, we have the same problem.

We can easily reproduce it: If we have encryption enabled without password/screenlock, everything works. As soon as we have encryption enabled AND set a PIN/Pattern/Password, the phone looses mobile connection soon after boot. With this behaviour, encryption is basically useless...
[Galaxy S 4 Mini Original Android Development] cdurex:
Cast Issues Fixed

Hello [MENTION=3044346]arco68[/MENTION],

Awesome ROM as always. It seems that the latest build (lineage-16.0-20190516-UNOFFICIAL-serranoltexx.zip) fixed the Cast issues.

Here are some screenshots.

So we should update the OP with this info.:D:cool::fingers-crossed::victory:

Thanks again for keeping device alive.

All of my phone info on the signature.
[Galaxy S 4 Mini Original Android Development] sky0247:
how do i get google app.....tried with given link....showing error(not installing)......Using GT-I9192
[Galaxy S 4 Mini Original Android Development] kurtn:
Select correct version. Smaller is better.
[Galaxy S 4 Mini Original Android Development] Alienatick:
Choose pico gapps.
[Galaxy S 4 Mini Original Android Development] arlaor:
WIFI Lost

Hi [MENTION=3044346]arco68[/MENTION]

the wifi network is lost after entering airplane mode or after some time of operation and only recovers momentarily when the phone is restarted GTi9192
[Galaxy S 4 Mini Original Android Development] klausenbusk:
Any chance the Wireguard kernel module could be added?

https://xdaforums.com/android/development/wireguard-rom-integration-t3711635
[Galaxy S 4 Mini Original Android Development] ptr1968:
sound

On some apps the sound is gone, can't get it back, tried rebooting, sound settings etc.

Notification and ringing sound are ok.

But youtube sometimes ok but most it is mute, while volume is on.

Should it be hardware or software?

Peter
[Galaxy S 4 Mini Original Android Development] jason972000:
With the recent change to use klte ril on pie, the rom dialer does not recognize that I entered my voice mail password. This is from a build I did on 6/1/19 for my serranolteusc (us celluar s4 mini).

Arne, I know I had similar problems way back on KitKat and I had to substitute a blob from my device to get it working.

But with this klte ril I'm stuck. Any suggestions?

Edit: Actually mobile data isn't working either even though I can get into the voicemail system.
[Galaxy S 4 Mini Original Android Development] soulreaver13mejia:
If you place a personalized tone, when you restart the phone, the ones you already bring are set by default.
[Galaxy S 4 Mini Original Android Development] theeightstar:
I have a similar issue, WiFi disconnects after some time using Firefox with multiple tabs opened. It comes back if I close all tabs but one. It seems to be that when my phone runs out of memory it disconnects WiFi. Mine is a GT I9190.
[Galaxy S 4 Mini Original Android Development] klorgfasder:
Trouble with adopted storage

On my 9195 I installed the May update over the (good working) April one, wiped dalvik and cache, and after reboot the external sdcard (which is used as adopted storage) was reported as missing. I tried a few reboots and patience (wait 30 seconds before entering the sim's pin, which helped at earlier occasions) and it now it shows again under Storage.

But somewhere along the path I did something wrong, because while in the recovery it always shows as adopted storage and all the data is there, within Android it's not adopted storage and just contains the empty folder My Documents. But under setting, storage the sdcard shows the right size, the right amount of storage used, and the right options (rename, eject, format as mobile), but then again list only apps (15GB, but "no apps"), system, cache.

All apps that were installed on the sdcard are gone and worse, I cannot install them anew (error in playstore) the gallery naturally cannot find the pictures in DCIM, the filemanager crashes without a word, etc...

I have a complete backup. But before I wipe first the card (and possibly the phone if that did not help) completely and reinstall from scratch: Anything left I could try?
[Galaxy S 4 Mini Original Android Development] arco68:
Check logs if there's any selinux denials that needs to be sorted. Also try with permissive mode if you can.
[Galaxy S 4 Mini Original Android Development] arco68:
Have you tried with blobs from klteusc?

https://github.com/TheMuppets/proprietary_vendor_samsung/tree/lineage-16.0/klteusc
[Galaxy S 4 Mini Original Android Development] sky0247:
how do i get root access?
[Galaxy S 4 Mini Original Android Development] theeightstar:
I flashed Magisk to get root access.
[Galaxy S 4 Mini Original Android Development] kurtn:
Or https://download.lineageos.org/extras

And enable in developer options
[Galaxy S 4 Mini Original Android Development] klorgfasder:
Thanks!

There were quite a few SELinux denials in the log, but nothing conclusive (for me!). Changing SELinux to permissive, however, brought access to the sdcard's data back: The gallery finds the pictures in DCIM, the filemanager does not crash, and under setting, storage the sdcard now lists apps, pictures, videos, etc.

But: setting, storage, sdcard still lists 15GB for apps (nothing for all the others) but "no apps" when tapping on it. And all apps that were installed on the sdcard are still gone, are listed as not installed, but cannot be installed anew (error in playstore). I can install those apps via adb and the playstore updates without complains.

The only SELinix denial related to storage i found is:

But I think I broke something seriously and will go the way of wiping all and everything and start from scratch.
[Galaxy S 4 Mini Original Android Development] igor.jakovenko@gmail.com:
Samsung GT-I9190

Hey. everybody! I use Samsung GT-I9190 for several months? firmware 16.0 Everything works fine, but there is a small problem. The headset does not work properly (headphones). When an incoming call, the headset buttons do not work. Previously, the answer button worked with the original firmware and you could answer by pressing the button on the headset. And now pressing this button resets the incoming call and is not audible in the correspondent’s headphones. Is this something you can fix ??
[Galaxy S 4 Mini Original Android Development] arco68:
Root is already included in the ROM. Just enable it in developer settings.
[Galaxy S 4 Mini Original Android Development] arco68:
I tried adoptable storage on a clean install, and it seemed to work as it should here. Didn't see any unusual selinux denials in the log either.
[Galaxy S 4 Mini Original Android Development] jason972000:
I think that was it Arne.

I replaced libsec-ril.so with the one from klte, https://github.com/TheMuppets/proprietary_vendor_samsung/tree/lineage-16.0/klteusc/proprietary/lib/ libsec-ril.so and now my voice mail accepts input and mobile data is working. GPS seems good too but I'll have to see if it actually works with Maps driving directions in LTE and 3G modes to be sure.

I think the lib in TheMuppets for serranolteusc can be updated for 16.0.
[Galaxy S 4 Mini Original Android Development] arco68:
Great to hear. I've updated the blob now on Muppets.
[Galaxy S 4 Mini Original Android Development] franticfreddy:
Please update your 15.1 oreo rom.

Since this 16.0 have still much issues regarding selinux and sdcard storage.

regards.
[Galaxy S 4 Mini Original Android Development] klorgfasder:
Right. Just tested with the 9190: On a clean install no problems. I'll make that clean install on the 9195 soon, too. Meanwhile reinstalled all apps with Titanium Backup (adb installed that one) and phone works (with SELinux permissive) as expected again. I still think that I did something wrong.
[Galaxy S 4 Mini Original Android Development] arco68:
New builds uploaded with June security patches.
[Galaxy S 4 Mini Original Android Development] miccca:
perfect! many thanks
[Galaxy S 4 Mini Original Android Development] Claudio4780:
Wow arco. I went back to the May version. Latest update took off some of my apps. However main reason: Display does not give me option for battery usage in %
[Galaxy S 4 Mini Original Android Development] arco68:
I forgot to mention they brought back circle battery. Look in system/status bar. Battery % is there.
[Galaxy S 4 Mini Original Android Development] Claudio4780:
Thanxxx, was my stupidity:D
[Galaxy S 4 Mini Original Android Development] mielletseed:
Anybody knows what's about NLP (indoor location) - is it fixed now? In the way I use m device without NLP it is almost unusable...

Thanks
[Galaxy S 4 Mini Original Android Development] mielletseed:
to answer my question myself - it still seems not working.

any chance to repair this [MENTION=3044346]arco68[/MENTION]?
[Galaxy S 4 Mini Original Android Development] arco68:
Actually, I enabled it by default in the setup wizard in this build. Other than that, I don't think there's much else I can do, as I believe it depends on Google services.
[Galaxy S 4 Mini Original Android Development] chillilounge84:
Hi [MENTION=3044346]arco68[/MENTION], it comes with SELinux Enforced or Permissive this time?
[Galaxy S 4 Mini Original Android Development] mielletseed:
it's the "google location service" or "google location accuracy" ("Standortgenauigkeit verbessern" on my device in German). I can't turn it on. It was always enabled on my device but now it is disabled but when I enable it and leave that setting it stays disabled (when I come back to that setting)
[MENTION=9350973]All[/MENTION]: could you please check whether you can enable it or not

go to the main menu

tap Security & location and then Location

tap Advanced and then Google Location Accuracy

Is it enabled? If not, can you enable it and is it still enabled when you return to that setting?

I have a second device (i9195) with April's build and there the location accuracy is working but not on my i9192 since the May's build
[Galaxy S 4 Mini Original Android Development] kurtn:
I don't use GApps. But unifiedNLP from shadow53 works as ecpected.

---------- Post added at 08:09 AM ---------- Previous post was at 08:07 AM ----------

Enforcing in 0609 build
[Galaxy S 4 Mini Original Android Development] chillilounge84:
Awesome man! I will download it then.
[Galaxy S 4 Mini Original Android Development] Anirudh Kartik:
The camera app keeps failing. I apparently have the GT 19190 phone. I say apparently because my box says I have the 19192 dual sim version. But it fails to flash the twrp or custom roms of that version. It only accepts the 19190's development software.

My camera app works after the first boot. But then keeps saying camera error cannot connect to camera and reboots/ force close while clearing app cache and data doesn't work.

Only way to get it to work again is by doing a factory reset.

Any possible fixes?
[Galaxy S 4 Mini Original Android Development] Arslan140:
Using May build for I9192

Location accuracy working fine

It's disable by default (never used it before tho)

Enable it and close the settings

And when going back to location accuracy it's enable As expected

Using Pico Gapps
[Galaxy S 4 Mini Original Android Development] mielletseed:
Thank you very much! After your reply I wiped everything (/system, /data, /cache ...) and installed that ROM (june) along with nano gapps and with this clean install location accuracy is working fine for me too. So something went wrong for me in the may update ...
[Galaxy S 4 Mini Original Android Development] chillilounge84:
Did you flash the right phone version?
[Galaxy S 4 Mini Original Android Development] IronRoo:
Guess he means TWRP above

how many sim slots? What does it say under the battery? (or better still on the motherboard, if you did not buy it new from Samsung) Also maybe a phone information app will show you their pcb model or the modem installed will show the phone model (unless you also flashed wrong modem?)

I suspect you flashed the wrong recovery before so now it shows the wrong phone model. Should be able to fix by flashing stock with Odin, if I recall. See the Q&A thread, people have done this before (open new issue there if you still can't fix)
[Galaxy S 4 Mini Original Android Development] Anirudh Kartik:
I have the dual sim phone....

Yeah, I had flashed the wrong twrp!

I just flashed the 19192 img through the recovery and then I could flash the right rom.

I thought that flashing the wrong recovery would lead to some sort of brick. Didn't think it would accept the recovery, forget flashing a whole rom of another device.

Thanks for the help!
[Galaxy S 4 Mini Original Android Development] essenov:
I switched from CM13 to this Rom a month ago with the May update. Clean install. No major issues found. Generally I'm very happy with it after installing a few additional applications, like google phone.

When the phone is disabled and charging it was showing the percentage of the battery with CM13, but now it only shows animated battery. Any way to enable the percentage while charging disabled phone?
[Galaxy S 4 Mini Original Android Development] kurtn:
You can guess the soc from the animation. The amplitude of bar movement is higher in empty battery state.
[Galaxy S 4 Mini Original Android Development] Alienatick:
Hey [MENTION=3044346]arco68[/MENTION], I bring a log that can possibly tell you what makes the screen go black. If it does no help, I think the problem is in trebuchet, can say why, butbif you could review trebuchet's config maybe it would help.
[Galaxy S 4 Mini Original Android Development] soulreaver13mejia:
With the last update, the system is corrupted when it restarts after a couple of days of use and does not go beyond the samsung logo (GT-I9190)
[Galaxy S 4 Mini Original Android Development] qooleer:
Last build lineage-16.0-20190609-UNOFFICIAL-serrano3gxx make bootloop process before first reloading!

Please fix it!

Device Samsung GT- i9190 8gb rom

TWRP 3.3.1.0 Official.

Please fix bootloop from reloading device!
[Galaxy S 4 Mini Original Android Development] Arslan140:
Stuck on Samsung logo

Just clean install the latest June Built on I9192

It works fine SIM/Data etc(as expected)

But when reboot the device it stuck on Samsung logo
[MENTION=3044346]arco68[/MENTION] Can you look into this.

---------- Post added at 05:41 AM ---------- Previous post was at 05:38 AM ----------

It happened on restarting the phone

No matter which day you do

---------- Post added at 05:43 AM ---------- Previous post was at 05:41 AM ----------

[MENTION=3452328]qooleer[/MENTION] please provide logs.
[Galaxy S 4 Mini Original Android Development] ptr1968:
When updating within Pie, with TWRP is it better to WIPE cache, dalvik?

peter
[Galaxy S 4 Mini Original Android Development] bierma32:
If you come from LOS 15.x or lower than you need a clean install

If you come from LOS 16 and you update to a the lasted Version is it recommended to wipe cache and Dalvik.
[Galaxy S 4 Mini Original Android Development] Simaramis:
FIY I don't have any problems regarding bootloop or stuck at Samsung logo with my GT-9192. I formatted however, then clean installed June 6 version with TWRP 3.3.1-0 from here: https://dl.twrp.me/serranodsdd/twrp-3.3.1-0-serranodsdd.img.html installing apps now...
[Galaxy S 4 Mini Original Android Development] Arslan140:
LineageOS 16 June Built works fine after install

But when you do restart the phone or Power off and turn On it will stuck on Samsung logo.

I haven't try AOKP latest build So I cannot say if same thing happened to AOKP
[Galaxy S 4 Mini Original Android Development] mielletseed:
But this happens not for other - mine isn't stuck...
[Galaxy S 4 Mini Original Android Development] Simaramis:
I am unable to replicate your issue. I reboot and turn off like 20 times since install never stuck. Works fine with mine. What Rom were you coming from? Try formatting, then swipe everything, install latest TWRP. I don't think your issue is build-related.
[Galaxy S 4 Mini Original Android Development] mikko.rantalainen:
Boot loop with 20190609 on i9195

I'm running lineage-16.0-20190609-UNOFFICIAL-serranoltexx.zip on i9195 and the system was working fine and even SELinux was enabled. Great work!

However, out of blue my system no longer boots up today. I wrote about the issue to Android Enthusiasts at android.stackexchange.com/questions/213722/how-to-debug-boot-loop

Short summary:

- I'm able to boot to download mode

- I'm able to boot to recovery (TWRP 3.3.1.0)

- Trying to do normal boot results in normal boot screen with yellow "Set Warranty Bit : kernel" text in the top left corner. However, instead of going to LineageOS boot animation, the screen stays in this view for around 20 seconds and reboots again (some kind of boot-loop).

While installing the system I wiped system and data but not media and the system was working fine for a couple of days before this problem.

I'd like to provide additonal details if you need some info to debug this issue. However, I'm running on my backup phone right now and I would rather not wait for too much to get the main phone to usable state again. Obviously I cannot provide any additional details if I wipe the whole system and reinstall so I'm postponing that for some time if needed. I'm running Ubuntu 18.04 on my desktop machine and I can use heimdall and adb if needed. I can also compile software if needed for additional testing.

Any suggestions about how to proceed?
[Galaxy S 4 Mini Original Android Development] mikko.rantalainen:
Which phone are you using? I have similar problem with i9195 (see https://xdaforums.com/showpost.php?p=79742833&postcount=858) for details.

---------- Post added at 02:15 PM ---------- Previous post was at 02:07 PM ----------

Which phone do you have? I have the same problem with i9195. Also, it may only appear if battery is removed while the system is powered off.

Before trying this, make sure your backups are up to date because data wipe is required to get the device to boot normally until the actual cause is found.
[Galaxy S 4 Mini Original Android Development] laiskudeze:
The same problem: Boot loop with 20190609 on i9195
[Galaxy S 4 Mini Original Android Development] soulreaver13mejia:
I was stuck in the samsung logo, look for some solution and I saw a video about bootloop with linageos android version 7, according to the video it is that when it restarts when updating the linageos version, it returns to the TWRP recovery and does not start the system, I entered TWRP and I put the command line in the terminal function and just to test and gave a logical error and then reboot in the terminal and start the system normally, maybe this will help someone.

Related video: https://www.youtube.com/watch?v=g24qSJnfzfk&t=365s
[Galaxy S 4 Mini Original Android Development] mielletseed:
I have an i9192 (16 GB) and an i9195 (8 GB) both running June build. I'm sure I already pulled the battery since I use multiple batteries.
[Galaxy S 4 Mini Original Android Development] mtrantalainen:
It seems that the recommended solution in the video was to zero FOTA partition like this

dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota

I did try this and my boot loop was NOT FIXED. In addition, I failed to find any info about this FOTA partition. It's not part of the official firmwares either as far as I can see.

I also tried to run

adb logcat

before I try to boot the phone but the boot loop activates before adb connection is made. In fact, the phone does not even appear as USB device (according to desktop computer linux kernel) before the boot loop is hit.

---------- Post added at 08:25 PM ---------- Previous post was at 07:29 PM ----------

Do you have gapps installed? If so, which version?
[Galaxy S 4 Mini Original Android Development] kurtn:
You really scared me. I9195 no GApps unencrypded, SD as removable storage. updated by dirty flashing and wiping dalvic/cache. Twrp 3.2.3.0 no problem.

Powered off removed battery, pressed power button for complete residual charge drain. Reinserted battery. Power on. No problems.

Edit: ooos wrong thread! I did this on my daily driver with lineageOS oreo. Just booting up my secondary device with similar setup in pie: no problems
[Galaxy S 4 Mini Original Android Development] soulreaver13mejia:
I did not want to restart my phone, but I restarted it when I installed a magisk module and I no longer passed the samsung logo, I installed RR Pie and I had no problems.
[Galaxy S 4 Mini Original Android Development] Arslan140:
Same here

No bootloop problem with RR Pie June build for I9192

---------- Post added at 09:07 AM ---------- Previous post was at 08:59 AM ----------

I9192 and did clean install without Gapps
[Galaxy S 4 Mini Original Android Development] mtrantalainen:
Okay. It seems that if GApps has never been installed on the system this bug may not trigger.

I have i9195, open gapps arm 9.0 nano 20190614, Samsung 32 GB EVO microsd as adoptable storage and TWRP 3.3.1.0.

I guess the boot loop is timing related. My device does successfully boot maybe once per 20-30 reboots but I haven't figured out any logic there. I cannot connect with adb to the device before it reboots, I tried to zero FOTA partition, wipe the cache and dalwik cache, wiped the system and reinstalled just the lineageos (skipped installing gapps). It seems that the problem is caused by something in the data partition. It's really hard to figure out what since I cannot get any logs.

I also tried to follow instructions to get adb to work earlier (https://xdaforums.com/general/xda-university/universal-test-rom-build-didnt-boot-t3258818) but had no success with it.

---------- Post added at 03:45 PM ---------- Previous post was at 03:26 PM ----------

Do you know how to get logs from a boot loop when the device reboots before adb logcat can connect? I have a boot looping i9195/serranoltexx with build 20190614 in case it makes a difference.

---------- Post added at 04:06 PM ---------- Previous post was at 03:45 PM ----------

I was able to get some kind of log from /proc/last_kmsg. Be warned that I have no way to verify that this matches the boot loop. I kept shortly pressing volume up, home and power every now and then during the boot because it seems to allow longer boot process before restart so hopefully this log contains as much data as possible:

https://pastebin.com/x4ZVPp09