yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Mini Original Android Development] Thoadi:
let me know if update helps. But looks like it's Pie related. Volume is predefined in mixer_paths.xml and for most user it's to quiet. But need a solution to adjust, office :angel: or pub mode :silly:

Edith: Updated and it's working again.
[Galaxy S 4 Mini Original Android Development] arco68:
New builds with October security patches released.
[Galaxy S 4 Mini Original Android Development] IronRoo:
Yes, real dumb security.
[Galaxy S 4 Mini Original Android Development] gcs88:
[MENTION=5700793]emey05[/MENTION] did you get SantanderSign app working?

other banking apps working fine using magisk hide but not this SantanderSign app.
[Galaxy S 4 Mini Original Android Development] emey05:
Yes I did, but not with Magsisk, just the low level way patching boot image (ro.debuggable=0), removing "su" and 3 other files just like the addonsu-remove package does, additionally renaming /system/xbin to /system/ybin and patching /system/build.prop replacing "userdebug" with "user" and removing all references to lineageos. ro.lineageos* entries are simply deleted. All this is packaged into a new zip file I called addonsu-remove-full. I also made the opposite package addonsu-full, which will revert everything including reinstalling "su" so I can switch to root and back from recovery as I like.

Don't forget to switch off "root" in settings->system->developer options as long as you have root access as you can't do this after booting with ro.debuggable=0.

Use MindTheGap for gapps (necessary). Running Santander SmartSign requires an internet connection otherwise it fails with "internal error". No need for installing a google account.

I buyed this used S4 mini from ebay exclusive for use with banking apps. No contacts, no calendar nothing personal besides the banking apps.

My daily driver is a Samsung S5, rooted with Magisk and no gapps at all.
[Galaxy S 4 Mini Original Android Development] klausenbusk:
[MENTION=3044346]arco68[/MENTION] could you apply this change to the kernel: https://github.com/LineageOS/androi...mmit/f44b4b19da1541fce8440ffa1e59cdb722cf10b5 ?

It should fix the Syncthing reboot issue.
[Galaxy S 4 Mini Original Android Development] arco68:
Sure. Will do.
[Galaxy S 4 Mini Original Android Development] gcs88:
after upgrading baseband to I9195XXUCQL2 mobile cellular stay connected. but still have trouble to get internet connection working. in quick tile mobile data says lte. which logs are needed for this?
[Galaxy S 4 Mini Original Android Development] dudoedu:
Late sms notification

Today I found on reddit lineageos a thread titled "LineageOS 16 Delayed SMS notification on OnePlus One".

The workaround described by XDA curiousrom seems to solve my problems with late notifications on receiving sms.

Tested with lineage-16.0-20191015-UNOFFICIAL-serranoltexx, clean install.

Using

adb shell dumpsys deviceidle

should show "com.android.messaging" in the whitelist system apps.

If not you have to correct this with:

adb shell dumpsys deviceidle whitelist +com.android.messaging

and restart the phone.

Works. Great.

Thanks a lot [MENTION=4122877]curiousrom[/MENTION]
[Galaxy S 4 Mini Original Android Development] jason972000:
[MENTION=3044346]arco68[/MENTION],

I'm still following along building this 16.0 rom for serranolteusc.

I've noticed for the past several weeks that in call voice audio can get really choppy where I need to reboot my device to get clear in call voice audio again.

It almost seems like other audio use cases cause it.

For example, I'm watching Netflix when a call comes in that I answer. Or, a call comes in while listening to a stream of music to my Bluetooth speaker.

I'm thinking something audio related is not getting cleared for in call voice to work properly. If I can figure how to reproduce it, I'll try to grab some logs.

Curious if others have experienced this on los 16.0?
[Galaxy S 4 Mini Original Android Development] Mau3000:
Is a stable version but the radio need atention.

Hi! I have a I9192 and installed the Lineage 16.

It's estable. Was a GOOD job, guys!!!

The radio App does not play on speakers and no record in live radio. Please, if possible, fiz this on next version. Thanks!
[Galaxy S 4 Mini Original Android Development] gcs88:
it looks like with the latest update from SantanderSign App it's possible without this :good:
[Galaxy S 4 Mini Original Android Development] ljimenez93:
I updated LOS 16 from 20190709 to 20191015. I wiped system partition and flashed new build. Everything fine except for Google Play Services keep stopping over and over. Then I rebooted and after Lineage logo turned off, ir automatically rebooted into Recovery mode. So I restored a previous backup. I'm using twrp posted here on my serrano3gxx.
[Galaxy S 4 Mini Original Android Development] kurtn:
Wiping system means, you destroy all update survival scrips in system/addon.d - your GApps didn't survive the flash. Don't wipe anything.
[Galaxy S 4 Mini Original Android Development] arco68:
Jason, since you're able to build yourself, there's a few things you can try...

From the latest patches added in https://github.com/LineageOS/android_hardware_qcom_audio/commits/lineage-16.0-caf-8960, revert those that might be relevant to the issue, and test.

Also the latest audio related patches in https://github.com/LineageOS/android_device_samsung_serrano-common/commits/lineage-16.0, revert and test.

Let me know what you find.
[Galaxy S 4 Mini Original Android Development] arco68:
Fixed for next build.
[Galaxy S 4 Mini Original Android Development] 01mf02:
I just tested build 20191015, and the call volume seems to be fine! (Without needing to change any config file manually.)

Thank you for maintaining the S4 builds, Arno!
[Galaxy S 4 Mini Original Android Development] sabotage154:
hello. can anyone confirm that the vpn >always on vpn > block VPN feature works on this ROM? on stock pie roms the vpn >always on vpn >block VPN feature kills the network connection as soon as vpn connection is dropped. i noticed on some lineageos ROMS on other devices the vpn > always on > block VPN feature is broke.

Can anyone confirm that the vpn > always on vpn > block vpn feature works on this ROM? thank you
[Galaxy S 4 Mini Original Android Development] fdxw:
First, arco68 thank you for maintaining s4mini builds.

Just upgraded from your latest Android 8.1 LineageOS 15.1 (August 2019 security fixes) to 9.0 lineage-16.0-20191015 (October security fixes). I noticed the Linux kernel version still being 3.4.113, this is very old since it's from 2016. Is this the actual true kernel version and aren't there many security vulnerabilities within this old kernel?
[Galaxy S 4 Mini Original Android Development] KyeWalker:
Big shout out to ARCO!!! Thanks for another great build and your continued support on the s4mini

Wanted to ask the community if anyone has had 4g issues. Phone has been in the cupboard for a bit so havent been around.

I've been using custom ROMs on this device since CM11 so modems update to date, it was a clean install, I came from the last CM13 SNAPSHOT and had no issues with 4G but LOS 16 no 4G just about get a 3G connection.

Service from provider is fine and flashing back to CM13 fixes 4G

Can't seem to find anything on this thread.

From UK if that makes a difference.

Thanks in advance!!!
[Galaxy S 4 Mini Original Android Development] dop251:
I've noticed that after a clean install the 'Preferred network type' is set to 3G. Changing it to LTE fixed the problem for me.
[Galaxy S 4 Mini Original Android Development] KyeWalker:
Hey thanks for the reply, I forgot to add that was the first thing I looked at, I've attached a screen shot to show. I've noticed after a few hours it will switch to 4G, work for an hour but then its like my phone goes into aeroplane mode, shows 4G but don't get phone calls/text and can't send either. Reboot fixes but back to 3G
[Galaxy S 4 Mini Original Android Development] dop251:
Maybe worth double checking you're on the latest modem (I9195XXUCQL2), see https://xdaforums.com/galaxy-s4-mini/general/modem-samsung-galaxy-s4-mini-gt-i9195-t3390780

I vaguely remember I had a similar behaviour before upgrading to this modem....
[Galaxy S 4 Mini Original Android Development] Arslan140:
Black screen bug

Hi [MENTION=3044346]arco68[/MENTION]

I am using I9192 and latest October build

I recreate Black screen bug and many other users also report that so it's not just I9192 specific

Applies on both I9190/5 as well

I recreate this bug by playing 360p video in mx player and zoom in and out many times (fast) and than I got black screen

fix I found is to press the power button (it will lock the phone obviously) and press it again and the phone is back to normal.

Here is the log
[Galaxy S 4 Mini Original Android Development] wackendf:
Wifi Problem

I updated today to the version from 15th of October. I made fresh installation and i have wifi problems. The data rate is very low or breaks up during a file transfer. With other devices i don't have any problems. It was OK with the old ROM too.

I have installed the newest modom and bootloader firmware.

Is this a known problem and how can i fix it?

Thanks in advanced.
[Galaxy S 4 Mini Original Android Development] fdxw:
Additionally to my last post: [MENTION=3044346]arco68[/MENTION] Do you think it would be too much work upgrading to a maintained longterm kernel release 3.16? Although it's only projected to be maintained until 04.2020, so maybe it's not worth it.

[MENTION=3044346]arco68[/MENTION], do you have devices in mind that you would be upgrading to? (I also have a OnePlus 6 and so far nothing to complain about).
[Galaxy S 4 Mini Original Android Development] Mrisaac:
I updated my phone from the 052019 build to the 102019 build and now it won't boot up. It stays on the lineage OS screen for a long time then boots back to recovery. Any ideas?
[Galaxy S 4 Mini Original Android Development] kurtn:
Any bad addons? Wipe system and flash to get rid of.
[Galaxy S 4 Mini Original Android Development] Mrisaac:
That fixed it. Thanks!
[Galaxy S 4 Mini Original Android Development] arco68:
Upgrading to a newer kernel is just too much work, and not worth it.

I have a Galaxy A3 running stock as my daily driver.
[Galaxy S 4 Mini Original Android Development] curiousrom:
LineageOS patch - vendor: Add messaging app to power whitelist

[MENTION=3044346]arco68[/MENTION] - Hello, I'm posting here because I saw that you merged recently the LineageOS patch vendor: Add messaging app to power whitelist

I don't know your Reddit handle, you blocked PM's & wanted to attract your attention to this post in the LineageOS sub: Messaging Notification Delay - The Fix is in The Tubes!

Maybe you could run the same tests as I get a 45 minutes Messaging notification delay (screenshot) in deep idle on Galaxy S5 G900M LineageOS 16.0 klte build 2019-11-02 + Open GApps Pico + LineageOS AddonSU.

Thanks for your time & contributions to the LineageOS project. :good::cool:

Saludos!

***
[Galaxy S 4 Mini Original Android Development] helium314:
Recently my GPS locations have wrong dates. The time is correct, but the rest is from March 2000.

This is likely an effect of a GPS rollover, S4 Mini is listed in the impacted devices: https://rntfnd.org/2019/10/16/lookout-gps-rollover-problems-still-to-come-for-some-phones-and-pads/

I am not sure whether it is possible to fix this, but since accuracy and position are still correct, a workaround by checking GPS times and possibly adding 1024 weeks seems doable.
[Galaxy S 4 Mini Original Android Development] limeflow:
Just created GPS tracks on both of my GT-I9195. They show the correct date and time.
[Galaxy S 4 Mini Original Android Development] helium314:
Strange... my 9195 definitely shows the wrong date. Using SatStat to show date, LOS build from October. Same on my 9192, but that is still on LOS 14.1 based AOKP.

Maybe because I don't have Gapps installed?
[Galaxy S 4 Mini Original Android Development] limeflow:
I installed SatStat now and it also shows wrong date.

My GPS-tracks were created by LOCUS and I browsed the data via an editor.

<trkpt lat="48.594694" lon="8.851064">

<ele>453.64</ele>

<time>2019-11-07T09:38:15.980Z</time>

<pdop>20.00</pdop>

The time shown is GMT local time was 10:38

---------- Post added at 04:35 PM ---------- Previous post was at 04:21 PM ----------

Just did the same test with OSMAND. The track aslo shows current date.
[Galaxy S 4 Mini Original Android Development] arco68:
I can confirm your findings, which is weird, because whitelisting the app should have fixed it. So I don't really know what's going on unfortunately. From looking at the app sources though, it seems like it's using some pre-kitkat AlarmManager interface for the notifications. The app hasn't really been maintained by Google for several years, so my guess is that it would need to be updated to use the new AlarmManager interface in Android. But that's outside of my abilities though.
[Galaxy S 4 Mini Original Android Development] helium314:
[MENTION=9512129]limeflow[/MENTION]

From what I understood by looking at the source, Osmand is using system time because "there is a bug on some devices with location.getTime()" (https://github.com/osmandapp/Osmand...c/net/osmand/plus/OsmAndLocationProvider.java)

So I guess that apps that rely on location.getTime(), like SatStat or the µlogger I use, will report the wrong time.

Since this apparently affects more devices that might not get updates it should be considered in the apps. But I still think it is good thing to have the OS report the correct GPS time...
[MENTION=3044346]arco68[/MENTION] is this possible / easy to fix?
[Galaxy S 4 Mini Original Android Development] limeflow:
[MENTION=7936379]helium314[/MENTION]

Thank you to clearify this.
[Galaxy S 4 Mini Original Android Development] kdolum:
Completely disable battery optimization (doze)

I learned how to completely disable "battery optimization", which seems to be the same thing known as "doze". Thanks to [MENTION=8772965]dudoedu[/MENTION] for alerting me to the "dumpsys" command. To disable the whole feature say "dumpsys deviceidle disable", e.g., using adb shell. Of course then you need to make sure your phone is not full of bloated background processes that drain your battery. In my case, I did not see any increase in battery usage.

This does not last over reboot. I attempted to fix it by putting the command in /data/local/userinit.sh, but that gave the error "Can't find service: deviceidle". Maybe it is executing too early. I was able to get it working by executing the same command after reboot using Tasker. (It takes Tasker a number of seconds after the phone appears to be completely restarted before it actually runs the script. That's no problem here, but confused me when debugging.)
[Galaxy S 4 Mini Original Android Development] kdolum:
Built-in speaker doesn't work except for calls

Using this ROM, the built-in speaker on my I9195 works only for talking on the phone. For media, alarms, notifications, and ringing I get only silence. Adjusting the call volume in settings gives the test tone through the speaker. Adjusting any other volume gives silence.

Earbuds work fine. A bluetooth speaker works fine.

My built-in speaker worked normally in my previous ROM, which was lineage 14.

Any ideas? Thanks!
[Galaxy S 4 Mini Original Android Development] RB1109:
switching between apps / canceling apps

Hello - awesome work you do!

Have a short question:

I installed an older version of lineage-16 by mistake from mediafire were [MENTION=3044346]arco68[/MENTION] shares the latest one. Everything so far works fine. Unfortunately the function of the button left to the home button to list running tasks / apps, switch to one of them or even cancel them is not available. Will this be in the latest version I have seen there (2019-10-15)? And if so - what steps do I have to go, can I just put the file together with the Gapps to the SD- Card and install them or do I have wipe something first and to start with flashing Samsung firmware?

Many thanks in advanced!
[Galaxy S 4 Mini Original Android Development] kurtn:
You can downoad any twrp flashable rom zip file you like with your phone. It's stored in internal sd downloads folder. Go to twrp wipe system, data and caches. Install the zip from download folder.
[Galaxy S 4 Mini Original Android Development] Curver33:
Im dont know the standard function of this button with a fresh intallation of Lineage16. But you can configure the function of the buttons in settings/system/buttons
[Galaxy S 4 Mini Original Android Development] RB1109:
Super - Up and running again, list running apps using the left "soft" button is working, I'm happy Thank you very much!
[Galaxy S 4 Mini Original Android Development] kurtn:
Settings system buttons. There you can assign various actions to short/long/double press
[Galaxy S 4 Mini Original Android Development] fdxw:
Understandable that putting much work for such rather old/slow hardware at this point is not profitable. I often use OsmAnd+ (get the Plus version from F-Droid) and on the S4mini it's really slow compared to the OP6, also not enough space for putting maps on. The S4mini has no real advantages anymore except size (smaller display tho) and weight, the non-pentile AMOLED matrix is nice as it's full RGB resolution but was not used in many/any other devices.

I checked Galaxy A3 but it's like 1 year newer (the Qualcomm version), so not much/any better.

Ok, if you switch to any newer devices you may post it as I'd say you have built a community and trust.
[Galaxy S 4 Mini Original Android Development] kurtn:
If you have a look at gerrit, you will see, arne contributes much work to galaxy s4. Many variants are now official.
[Galaxy S 4 Mini Original Android Development] fdxw:
I think I noticed that some time ago. I mean something newer like SD820 at worst. S4mini is so slow sometimes that I think that the S4 wouldn't be much better. But thanks for the suggestion.
[Galaxy S 4 Mini Original Android Development] RB1109:
rooting is not as easy as expected

I tried some root zip files already. None of them is working even if they all run through the install process without any problem. At the end the root checker app says it is not rooted and the app (airaudio) which needs root access says the same.

I searched for root options recommended on lineageOS site for version 16. So the addonsu-16.0-arm-signed.zip didn't do the job and the UPDATE-SuperSU-v2.82-20170528234214.zip didn't either. I used the last version found on SUPERSU page with no better result. Witch one do you use and where to get it.? Thanks again
[Galaxy S 4 Mini Original Android Development] kurtn:
Addonsu 16 arm. You messed up your kernel with all that rooting. Wipe system, flash rom and addonsu and GApps if you need. Tap build number several times to get developer options. Enable root in developer options.
[Galaxy S 4 Mini Original Android Development] carlos974:
New update LineageOS-16.0 !

See OP (first page)

Thanks to [MENTION=3044346]arco68[/MENTION] :good:
[Galaxy S 4 Mini Original Android Development] Thoadi:
Magisk
[Galaxy S 4 Mini Original Android Development] arco68:
Su is actually built-in, so to enable root all you have to do is enable it in developer settings. Shouldn't need to install addonsu package.
[Galaxy S 4 Mini Original Android Development] RB1109:
Yes, you are right! Thats what I thought this morning while I was jogging :) This is all working now the way it should! Thanks a lot!
[Galaxy S 4 Mini Original Android Development] arco68:
New builds with November security patches released.

Links in first post.
[Galaxy S 4 Mini Original Android Development] BOTUS:
no idea if you guys aware (or if related) but...

all the satellites were supposed to move round a nineteen year cycle 6 April 2019 so they all think its year 0... whereas many old sat nav devices think its year 20 so can't get the correct year and get a muddle on. Clocks tend to work but daylight saving loses the plot.

modern stuff is supposed to know how to cope and or needs a firmware tweak
[Galaxy S 4 Mini Original Android Development] cybermcm:
Need help. ERROR: 7 Want to try this ROM but no luck. TWRP 3.1.1.0 showing E3004 "This package is for device:... this device is .

It seems that my device is missing its "branding".

It's an I9195, I can flash lineage-14.1-20180624-nightly-serranoltexx-signed but I can't flash lineage-16.0-20191113-UNOFFICIAL-serranoltexx. Any ideas (read a lot in the forum but no real solution)?
[Galaxy S 4 Mini Original Android Development] paulholland:
Maybe you need a more recent version of TWRP. I am using TWRP 3.3.1. on the GT-9195I and no problems with flashing LineageOS16.
[Galaxy S 4 Mini Original Android Development] MikeT.:
You need TWRP 3.3.1

https://twrp.me/samsung/samsunggalaxys4minilte.html
[Galaxy S 4 Mini Original Android Development] cybermcm:
[MENTION=5780724]paulholland[/MENTION] and [MENTION=8171333]MikeT.[/MENTION]: Thanks four your reply, installed current TWRP version and now it is working! I recently checked the version and didn't pay enough attention, 3.1.1 was somehow converted to 3.3.1, but only in my mind ;)...
[Galaxy S 4 Mini Original Android Development] birarvindersingh:
Arco, can you compile LOS 17 for S4 Mini? I want to try out Android Q, appreciate your work?. I tried all the LOS 14,15,16 builds compiled by you. ?

Please if you can compile LOS 17, it will be much appreciated ?
[Galaxy S 4 Mini Original Android Development] npfp:
Hi arco68,

----thanx again, for keeping my phone alive !! Now more than before, as Google apparently dropped security-support for android 7.1.2 .---- I reverted to LOS16 from /e/ (community-build still relying on LOS14.1)

Greetings from Mainz, Germany
[Galaxy S 4 Mini Original Android Development] slukk1:
It's normal. Test build)
[Galaxy S 4 Mini Original Android Development] HemanthJabalpuri:
https://opengapps.org
[Galaxy S 4 Mini Original Android Development] Malbo4:
Installed this new build as an update over the preivious build (with opengapps nano) from august via TWRP on my I9195.

When I want to start playstore it wants to pop up but screen stays blank white.

I cannot open my contact list, wants to open but gets kicked by an very shortly popping up small window. These two trigger on and off.

Here in germany I like to use an app called Regenradar. Its an app which shows rainclouds on an map of germany.

Same behaviour like with my contact list.

My guess is that something out of androids security features blocks these apps.

I could'nt find a way to turn this off so temp I will switch back to the last build from august.

Anyway, thanks for your engagement to give an older I9195 some newer OS :good:
[Galaxy S 4 Mini Original Android Development] mdhuma:
Any solution?
[Galaxy S 4 Mini Original Android Development] Aztek92:
Nothing to do with that, I also installed the new build as an update. Did you happen to flash official gapps with it?

Someone before encountered a problem flashing gapps along with android pie buld, so here's the right order:

1. Flash system + addational zip with Magisk if interested in root

2. Run system

3. Flash GAPPS and reboot

4. Install apk Magisk Manager

By now I can confirm that flashing new build as update works just fine. I also flashed official gapps over old ones (in seperate flash session just in case).
[Galaxy S 4 Mini Original Android Development] berkayy154:
Button customize is not working.

Camera app is returning can't connect to the camera when take photo.

Browser error: ERR_CLEARTEXT_NOT_PERMITTED when go to www.facebook.com (with http) (all http links same error, it does not remote https)

Night mode not working

Browser file download not working
[Galaxy S 4 Mini Original Android Development] Mohammed Bhere:
Will be available for I9192?

Thanks for all work
[Galaxy S 4 Mini Original Android Development] Aztek92:
Yeah, indeed. But only on back camera when using flash - if that somehow will help to debug problem.

Did anybody face problem with Magisk Manager not launching?

Nevermind, I hide magisk behind random signature in the system, that moved app to external stroage.
[Galaxy S 4 Mini Original Android Development] mdhuma:
Yes! I faced , after I moved to internal storage problem solved.