yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Mini Original Android Development] Claudio4780:
I have made a few different Modem installations (Odin). The Mobile Network Status always shows me "Disconnected" Picture 1

On Picture 2 it shows me one Baseband. I might be wrong, but I think on L16 there were two Basebands listed.

Can anybody help me?
[Galaxy S 4 Mini Original Android Development] merlin133:
some roms before i had the same problem.

for testing -

twrp backup

i deleted my data (before i migrate my data - see link) and start a factory reset - sms are ok (HW+rom was ok)

only solution: Factory reset/install - migrate my data

https://xdaforums.com/android/apps-games/app-migrate-custom-rom-migration-tool-t3862763
[Galaxy S 4 Mini Original Android Development] sekret1:
A while ago I realized to my surprise, that our old little phone supports SD cards bigger than 64GB. The lineageos wiki tells us, that SD cards "up to 64 GB" are supported. I have a 200GB card, which works perfectly fine! It's being recognized as 256GB with 56GB being used already, so I guess cards with "real" 256GB should work aswell, maybe even bigger ones?! That's awesome, because it allows me to store my whole music collection on it, which is very large! :)

Just a fyi, if you didn't know. At least I have never read anywhere, that it's possible. And I don't know enough about SD cards, so this isn't obvious to me.
[Galaxy S 4 Mini Original Android Development] arco68:
Was this an issue with 17.1 build from last month, or the month before that?
[Galaxy S 4 Mini Original Android Development] marcdu30:
hello,

when I want to flash the latest GT-I9195 update, TWRP does not see the zip file. Am the only one? :confused:
[Galaxy S 4 Mini Original Android Development] kurtn:
Is it really a zip file? My downloads sometimes get renamed to ".bin"
[Galaxy S 4 Mini Original Android Development] marcdu30:
yes it is a zip file. i see it in file manager but it is invisible in TWRP
[Galaxy S 4 Mini Original Android Development] Claudio4780:
Hi arco. I tried to move unsuccessfully from L16 to the lineage-17.1-20201014 version (clean flash). Unable to tell you results of the earlier L17.1 versions.
[Galaxy S 4 Mini Original Android Development] kurtn:
Twrp can be switched to install IMG files. In that case it doesn't see zip.
[Galaxy S 4 Mini Original Android Development] marcdu30:
i noticed that the zip does not have the same permissions as another older version of the ROM
[Galaxy S 4 Mini Original Android Development] BeeJ1109:
Hi marcdu30,

I installed successfully 17.1 Oct release. On my SM-I9305T

Used .zip as downloaded from link provided.

What version TWRP are you using. I use v3.4.0-0 latest.

On another SM-I9305T I have LOS 16.0 acro is presently building Oct release.

I use TWRP v3.4.0-0 on all my 3 devices. 3rd has Stock ROM.

I use all 3 to compare data transfer speed tests.

Finding very slow 5-15 Mbps D/L on LOS 16 and 17.1, whereas Stock is 50-54 Mbps.

Using Stock Modem partition being vfat on all 3 devices. Stock EFS partition. Works on LTE Mobile Networks on all 3 phones as well.

So I suggest you update both TWRP v3.4.0-0 and ROM LOS17.1 downloads as per page 1 download locations. being mediafile.com. Also download fsfix to fix bootloops after TWRP Restore. Read notes on Page 1 by arco.

After successful install, can you please test data transfer speeds D/L and U/L. I use speedtest.net app. available on Playstore.

Cheers

BeeJ1109
[Galaxy S 4 Mini Original Android Development] marcdu30:
Hello,

I am not using your SM-I9305T version (I am using GT-I9195 and the version I am trying to flash is dated October 13) Whatever the version of TWRP the file is invisible

Thanks
[Galaxy S 4 Mini Original Android Development] MrGoodtunes:
Very unusual. In fact, TWRP has sometimes been able to work with files that some regular system apps can not. Might you have been looking in the wrong folder on TWRP?

What tests have you tried? If this were to happen to me, I would put the ROM's ZIP file in several different places (internal, external,...) and then boot TWRP to navigate around, looking for it.
[Galaxy S 4 Mini Original Android Development] marcdu30:
hello,

this is what I have already (several different places) done before submitting my first request for help here. All this is not very important...I will wait for the next update for the GT-I9195.

Thank you
[Galaxy S 4 Mini Original Android Development] gmlai:
Hello,

I am using this ROM about a month ad find it runs very smooth in my i9195.

The only "problem" is that it taks even 10 minutes to get a GPS fix. Am I the only one with this drawback?

Is there a solution to improve the GPS? I tried modifing gps.conf and other "tricks" without appreciable imporovements.
[Galaxy S 4 Mini Original Android Development] kurtn:
The real trick to speed up sattelite location fix i s to go outdoor. If you stay Indioor, you can use network location from GApps or microG.
[Galaxy S 4 Mini Original Android Development] BeeJ1109:
Hi marcdu30

Sorry selected wrong model I meant SM-I9195T samsung S4 mini I also have a S3 SM-I9305T

Difference in SM-I9195T vs SM-I9195 is only bigger battery 2100 mAH in Australian LTE version. Sold by Telstra & Vodaphone vs LTE International 1900 mAH. Which was also available by another Carrier being OPTUS.

As I already told you need TWRP v3.4.0-0. Earlier version v3.3.0 series will not work on LOS 17.1.

Suggest you check and update, as LOS 17.1 Oct. 13 Release works on my SM-I9195T.

http://www.mediafire.com/file/h7hhoa7r83otih2/twrp-3.4.0-0-serranoltespr.img/file

Best of Luck

Cheers

BeeJ1109
[Galaxy S 4 Mini Original Android Development] Mr.Shine:
Actually, this has nothing to do with the WiFi network being hidden or not. As the OP mentions, this happens with non-hidden networks as well.

The actual problem is that this ROM silently fails connecting to any network that offers PSK-SHA256 key exchange. Note that the network doesn't have to enforce PSK-SHA256, offering it is already sufficient for the connection to be unsuccessful.

Likely, this chipset, being 802.11n generation, doesn't support SHA256 key exchange yet (this was introduced with WiFi5/802.11ac generation). Nevertheless, the device should fall back to SHA1 key exchange (as long as the AP supports it) instead of failing.

If you have control over the AP, one workaround would be using WPA, not WPA2 (drastically lowering security, so not recommended!) Some APs also stop advertising PSK-SHA256 for WPA2 if you turn off IEEE802.11w (Protected Management Frames) - may be worth a try.

If you don't have control over the AP, you're s.o.l. at this time until the issue is fixed client-side.
[Galaxy S 4 Mini Original Android Development] Andy1767:
Hi arco,

not sure if there is a problem with the lineage-17.1-20201014-UNOFFICIAL-serranodsdd.zip build.

I did update the TWRP with the one in the first post, then I wanted to dirty flash from your LOS16 -> LOS17.

Got an endless boot. Then I reinstalled factory ROM, installed twrp again wiped all, changed data and cache to f2fs again like I used on LOS16 and then tried to install LOS17 again.

Again boots just endless (Lineage boot animation).

Not sure if the build has a problem or if it maybe lacks f2fs support?

Have you got any idea?

Thanks!
[Galaxy S 4 Mini Original Android Development] rho-bot:
General hint: never dirty flash between different LOS versions, nor same LOS version from different distributions.

Regarding Endless Boot: Don't allow TWRP to install it's App, its broken and prevents LOS booting...
[Galaxy S 4 Mini Original Android Development] Mr.Shine:
It's not so hard to use the "Search thread" function...
[Galaxy S 4 Mini Original Android Development] Andy1767:
Thanks Mr. Shine - that did the trick!

Yes, I know the search thread function is not that hard.

Problem is it was not that obvious that this was the problem. First I thought it has something to do with Magisk. So I searched for the wrong stuff.

And I did update (dirty flash) my Galaxy S5 LOS 16 (official) to LOS 17.1 (official) just a few days back. I use f2fs there on cache and data as well and it worked like a charm.

So in principle LOS 17.1 does support f2fs. Only this build does not whereas the LOS 16 build does.

And f2fs on cache and data does stress the flash less, so in principle it is a good idea to use it on old devices like this.

Maybe Arco can even add it some time later.

So only when I was writing my post the idea came to mind that maybe, maybe f2fs could be the problem.
[Galaxy S 4 Mini Original Android Development] hardcorenooker:
Hey arco68! Could you please post .config file for this kernel? Any patches of yours or is it just vanilla LOS upstream? I wish to add zRam support and other goodies.
[Galaxy S 4 Mini Original Android Development] rellieberman:
Hi arco68,

My s4mini has finally died and I felt it appropriate to thank you and the rest of the community here for the work that has giving such long life to my phone.

So thanks very much, It has been a pleasure. Hold on to your s4 minis guys, great phone and great community.

Ariel.
[Galaxy S 4 Mini Original Android Development] Manu Argueta:
Good day Arco68:

I just want to report black screen, also when I play music with any player it randomly stops more than once and finally that the sim card slot 1 does not work. I have flashed the 10/14/2020 build. Thank you in advance for your support.
[Galaxy S 4 Mini Original Android Development] arco68:
/proc/config.gz has the full config. I'm maintaining the kernel, so upstream and mine is the same.
[Galaxy S 4 Mini Original Android Development] mbaptist:
No Sims Detected

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

First of all, thank you very much for maintaining LineageOS for the S4 minis.

I tried your 17.1 image as well as a custom build on my i9192. Everything seems to work well, except that no sims are detected. I can see both IMEIs, so I suppose the modem should be working. When I flash the original firmware back, the sims are detected without a problem. Do you have a hint where the problem might be?

I tried my custom build first, with the lineage recovery. Then yours, with the same recovery. Will TWRP make a difference?

I am a long time developer (1986) working on computational solutions for technical problems with industrial applications (simulations, geometry, numerical data,...). I am very familiar with linux (and other Desktop/Server operating systems), but relatively new to the android world and to mobile phones (as a developer). I find the available information a bit too scattered and difficult to find. I would gladly do some debugging directly on the phone, to try and understand the issue, but I have no idea how to setup a debugging environment for android. Could you please point me to some documentation? I would be glad to contribute to keeping these devices alive in Lineage.

Thank you very much,

Best Regards,

Manuel
[Galaxy S 4 Mini Original Android Development] bierma32:
[MENTION=11222431]mbaptist[/MENTION]

If you are coming from Stock you have to update to the latest Modem and Bootloader Version. https://drive.google.com/file/d/15Q8mFw5SfgfnpSil5zJj6s-Dul6Rcwxg

Also update to the TWRP Version from arco68 See post #1

[
[Galaxy S 4 Mini Original Android Development] io2345:
Sorry wrong thread. Was intended to go to the Galaxy S5 thread. Admins, if possible, please delete.
[Galaxy S 4 Mini Original Android Development] carlos974:
Thanks to [MENTION=3044346]arco68[/MENTION]
[Galaxy S 4 Mini Original Android Development] mbaptist:
Thanks, now the sims are detected

[MENTION=5390857]bierma32[/MENTION] Thanks for the tip, updating the bootloader and modem worked tip top, no need to change the recovery.

Yet, I am still curious where this version of the firmware is coming from. My original firmware was indeed very old: it was my first smart phone, bought at amazon.de, but they sold me an iranian or iraqui version, which almost never got any updates (the last one in 2014). I looked at sammobile and saw a lot of more recent firmware versions, but not the one you shared (which I used, thanks). Is it also a Samsung Version of the the firmware, or does it contain any kind of "extra" engineering?

I am still very new in this world of android and mobile phones and I am trying to learn as I go...

Thanks!
[Galaxy S 4 Mini Original Android Development] bierma32:
[MENTION=11222431]mbaptist[/MENTION]

I copied the files from the thread of the official TWRP S4 mini.

https://xdaforums.com/galaxy-s4-mini/orig-development/recovery-twrp-3-2-1-0-t3736888

THX must go ripee.

To update Modem and Bootloader is the important thing if you come from Stock and want to change to LOS 16 / 17.
[Galaxy S 4 Mini Original Android Development] arco68:
First post updated with builds with November security patches.

The issue with camera preview sometimes having the wrong orientation should hopefully be fixed now.
[Galaxy S 4 Mini Original Android Development] Claudio4780:
Howdy arco.

Updated my 9195 from the October version. Now it gives me some fault with the SD-card. I can unmount/mount it and it shows me 2.29 GB used of 64,00 GB. Below it says, SD card Not inserted.

Unable to get into the phone from my PC. Says empty folder.

All apps installed on the card are not working. Unable to format the card as it times out.

Tried twice to flash the new version, same problem
[Galaxy S 4 Mini Original Android Development] arco68:
What filesystem on the sdcard?
[Galaxy S 4 Mini Original Android Development] BeeJ1109:
Hi ARCO,

I have no issues on my extSD cards, using exfat, or fat32 formats. 32, 64, 128 & 256 GB

Cheers
[Galaxy S 4 Mini Original Android Development] arco68:
I might have "accidentally" built the kernel without f2fs support, so if that's the filesystem you used,

try flashing this boot image in twrp: http://www.mediafire.com/file/ium85ql53566wpv/boot.img/file
[Galaxy S 4 Mini Original Android Development] Ginga97:
Your boot image fixed it for me. Thanks a lot!
[Galaxy S 4 Mini Original Android Development] TartempionVD:
Loss of GSM signal

Hello,

First of all, thank you very much for what you do.

I installed Lineage 17.1 on my i9195 and was very happy with it. However, I notice that the reception of the GSM signal is very weak and that at times it no longer receives. If I restart, it works a few hours and then more. Do you have a solution for me. Thank you again for your help.
[Galaxy S 4 Mini Original Android Development] bierma32:
After using Hotspot, reboot oft the phone . [MENTION=3044346]arco68[/MENTION]

With last November Version if got following issue.

If im using the Hotspot of the phone and i want to switch the Hotspot off the S4mini 9195 freeze and it reboots automaticly by it self.

Try it 3 times and always the same.
[Galaxy S 4 Mini Original Android Development] fikast:
Loss of GSM signal too
[Galaxy S 4 Mini Original Android Development] BeeJ1109:
Why are you still using GSM, sure your Carrier in your country is still Operational. Try 3G or 4G LTE.

Check your Network Provider Mobile Coverage Maps for info. Search on Google. Change settings in Phone . Select Network and scan.
[Galaxy S 4 Mini Original Android Development] kurtn:
Samsung custom ROMs don't have volte. So for telephony we need gsm. As soon as the last provider dropps gsm, I can scrap all my Samsung galaxies.
[Galaxy S 4 Mini Original Android Development] TartempionVD:
Thank you @ arco68 for your response. I am not sure I fully understand. What do you mean by talking about hotspot. On the other hand, am I to understand that you are advising me to restart my phone every time I want to call? Forgive my ignorance, but I don’t speak English and am not very familiar with hacking on these phones. Anyway, thank you for your help.
[Galaxy S 4 Mini Original Android Development] bierma32:
[MENTION=11177263]TartempionVD[/MENTION]

That was not an answere of your Post,

it was an Post to @ arco68
[Galaxy S 4 Mini Original Android Development] tM&M:
Hello,

Want to add that I have also been having cellular network issues for the last month. The first version of 17.1 I didnt note any of these issues, which I think was the August compiled version.

I am now testing the November one but what I experienced was no signal after moving around town in places with bad signal. Then in places I had reasonable signal, the network would not come back unless I forced to change the preferred network type or rebooted.

Tried a few days locked to 2G and default (4G) and had the same problems. Usually, I always used 3G network as preferred.

Was considering moving back to 16.0 until other people posted this was an issue for them also.

---------- Post added at 04:52 PM ---------- Previous post was at 04:47 PM ----------

BTW, don't know if this should be reported to LOS bug tracker but I've been having a strange issue with Files app.

Downloaded the new 17.1 ROM to internal ok. Then moved the ZIP to SDCard and it was renamed with a .JAR added to the end (still .ZIP).

Tried this 3 times and happened every time. Any feedback is appreciated.
[Galaxy S 4 Mini Original Android Development] BeeJ1109:
Hi,

Just delete .jar extension then .zip will flash using TWRPV3.4.0-0.

Try several apps that can read RSSI (Received Signal Strength Indicator), RXL, (Received Signal level) RSRP & RSRQ (Quality performance) on 3G & 4G LTE. Will also neighbouring cells from adjacent Cells or Sectors in same Base Station, which have 3 to 6 Sectors or close nearby alternate Base Stations. CID (Cell Identification) Details available, Carrier, Network, Band, lots of info available, even maps.

I use G-mon and G-mon Pro which are free to download on app store.

Change Mobile Network in Settings, Mobile Network, preferred network type, select either 2G, 3G or 4G.

Cheers
[Galaxy S 4 Mini Original Android Development] Skyty:
Has anyone had a problem using NetGuard on LineageOS 17.1? Anytime I enable it, it blocks all WiFi on my device rather than just specific apps. Any ideas?
[Galaxy S 4 Mini Original Android Development] pwsqssdi:
Ever since updating to this, my battery usage has shot up dramatically and I've experienced at least daily crashing. I have the 20201112 version on serranoltexx, with pico gapps (20201121), and I've rooted it with Magisk.

It mostly crashes when I'm not using it, at different times and intervals, seemingly randomly. When I see it crashing, it's just like I'd have accidentally locked the screen, but when I try opening it, it starts booting. Usually it crashes also while trying to boot, but usually starts up fine on second or third try. Any ideas what might be causing this? Is there ways I could debug it so it could maybe be fixed or do I have to go back to a older Android?

What comes to battery usage, it was recently replaced and on Android 6 my average charging interval was well over a day, just couple weeks ago. Now I need to charge twice a day, without change in actual phone usage habits. Now I can lose 10% of battery an hour after charging without using the phone (<1 min screentime). Normal battery drop overnight (when it happens to stay up for the night, which is kinda rare) now is about 30-35 %. Crashing seems to eat a lot more battery than the phone just sitting there, I've had over 50% disappear at some nights.

The only thing that comes to mind as difference to other users is that my old installation was encrypted, so I had to wipe absolutely everything, and reformat /data completely (had to change FS to something else and then back again in recovery) to get rid of the old encryption.

Update:

For some reason, after being unusably unstable for couple of weeks, it has now stayed up for almost a day, and battery usage has dropped dramatically, I've only lost 6% in 11 hours. Something has clearly changed, it's completely different now. Will update later on whether this was a temporary thing or not.

U2:

Seems it fixed itself, quite fast after posting. Weird. Maybe the XDA-gods saw my suffering and made my Android behave finally.
[Galaxy S 4 Mini Original Android Development] arco68:
First post updated with new builds.

December security patches

Fixed hotspot reboot

Fixed various audio issues
[Galaxy S 4 Mini Original Android Development] Ginga97:
Hey Arco!

Yould it be.... oops you did it again?

just trying the fix from last time and report back when it fixes it.

Just took longer than usual to detect the card. never mind.
[Galaxy S 4 Mini Original Android Development] kolAflash:
Just completely wiped an i9195 (serranoltexx) and installed lineage-17.1-20201215-UNOFFICIAL-serranoltexx.zip via the provided twrp-3.4.0-0-serranoltexx.img

Directly after installation (and also after a few successive reboots) the cameras are working fine.

After enabling device encryption the cameras stopped working.

Standard camera app and OpenCamera say they can't access the camera.

I attached some logcat output.

https://pastiebin.com/5fdd7942b535f

P.S. LineageOS-16.0 (lineage-16.0-20201107-UNOFFICIAL-serranoltexx.zip) doesn't have that problem.
[Galaxy S 4 Mini Original Android Development] arco68:
I'll take a look at it.
[Galaxy S 4 Mini Original Android Development] BeeJ1109:
Hi arco,

Download for i9195 keeps failing, tried several times since release. Download crashes and gives message. Please check, or upload the file again.

Cheers beej1109
[Galaxy S 4 Mini Original Android Development] arco68:
No issues with it here.

Any issues with MediaFire itself is outside my control.
[Galaxy S 4 Mini Original Android Development] MilkyWay20:
I use the integrated camera app. How can I switch the saved location to the SD card?

When I using OpenCamera I can select the SD card but all pictures are not visible in the gallery app and are not accessable with other apps like WhatsApp. Only the file browser could show me pictures from OpenCamera.
[Galaxy S 4 Mini Original Android Development] Thoadi:
You use access storage framework?

I use quickpic mod for gallery, works ok. I have to give rights at first time when I want to delete a photo. Sometimes access directly from open cam not work, I have to open Quickpic from drawer. But no issues. You are also rooted? Well, I don't think this is required...
[Galaxy S 4 Mini Original Android Development] Skerleton:
for I9195 is not working..cant install it because I9195 is serranovelte not serranoltexx
[Galaxy S 4 Mini Original Android Development] arco68:
https://review.lineageos.org/c/LineageOS/android_packages_apps_Snap/+/291025

Look up scoped storage and blame Google.
[Galaxy S 4 Mini Original Android Development] arco68:
I9195 = serranoltexx

I9195I = serranovelte

The hardware on them are very much different, so they can't use the same ROMs.
[Galaxy S 4 Mini Original Android Development] Skerleton:
can you make a build for serranovelte?..because i tried another verision of lineage 18.0 but there a lot of options doesnt exist..for example cant disable buttons backlight((((
[Galaxy S 4 Mini Original Android Development] DuKe 33:
my gapps failed to install.plz help me to fix this
[Galaxy S 4 Mini Original Android Development] kurtn:
Use arm Android 10 nano or pico open gapps
[Galaxy S 4 Mini Original Android Development] DuKe 33:
BRO TRIED BOTH STILL FAILED. IT IS SHOWING ERROR 65
[Galaxy S 4 Mini Original Android Development] kurtn:
I'm sure there is more text than "error 65". Wipe system and data and flash lineageOS 17.1 and GApps 10 in one twrp session.
[Galaxy S 4 Mini Original Android Development] arco68:
No, sorry I can't. I don't have this device and as I said the hardware is different, so it needs different kernel and device sources to build from.
[Galaxy S 4 Mini Original Android Development] tM&M:
Not really much to blame. As a system app, seems to only be required to give all file access to Snap - then it can write to the old SDCard DCIM.

Snap also saved to private folder on SDCard. It is just a matter of having Gallery also read this private folder instead of just the internal "DCIM" folder.

Without this, using LineageOS on older phones becomes rather pointless.

IMHO, 17.1 is one of the most bug filed LineageOS releases I've ever used. Lots of things don't work and seems more a beta software than the high quality Android I've been used to.