yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Mini Original Android Development] Catfish78:
Hello,

try to re-download the build. I had the same on some phones when the downloaded build was corrupted.

Regards
[Galaxy S 4 Mini Original Android Development] arco68:
New builds. Some more options should be working now, and Snap camera is included this time.
[Galaxy S 4 Mini Original Android Development] Aztek92:
Ok, I tested new build.

So... buttons settings finally work! We can turn off backlight and assign different functions to each key. We can enable on-screen nav bar, tho we still can't use swipe up on home button gestures (Android Pie's new navigation).

Profiles for battery are back - we can again set performance profiles for power save or performance. There are 2 settings for automatic power save, which is probably a simple mistake. One under "Battery Saver" which allows to automatically save power at any point under 70% and one under "Battery saver and performance", with options limited to Never, 5%, 15% and 25% (Arco - pls don't remove the first option :D). There is a lot of new (old) quick tiles - NFC switcher, Caffeine, Heads up, Live Display tiles are back. And ofc camera is working now even with flash.

Still in settings but doesn't work:

Network traffic monitor doesn't work at all (not showing up in status bar).

Changing Style options still crashes the settings app.

[MENTION=3044346]arco68[/MENTION]

Again - since Quickstep launcher is gone, can we somehow flash it to replace Trebuchet and get new app switcher design? Or if is it not too much to ask - can you make a separate branch with new launcher if flashing is impossible?
[Galaxy S 4 Mini Original Android Development] afatsumlug97:
gonna downloading new build with todays official gapps, will post the results tomorrow, have to sleep right now :)
[Galaxy S 4 Mini Original Android Development] bierma32:
Boot Ingo TWRP ,advanced wipe select the Option repair.

Other Question ? Have you got Magisk installed ?

If yes flash an old Boot .IMG , Magisk make also some reboots.
[Galaxy S 4 Mini Original Android Development] rho-bot:
Have you allowed TWRP to install its System App? If yes, go back & disallow, as this will definitely block LOS from booting

This will be the same issue with other system apps which come without proper permission xml file. TWRP definitely needs to fix this.
[Galaxy S 4 Mini Original Android Development] Skenkz:
In the menu Advanced have I to select "Fix Recovery Bootloop"?

do you think this can solve my problem?

---------- Post added at 02:58 PM ---------- Previous post was at 02:55 PM ----------

Yes i allowed TWRP to install its System App.

How can I remove this type of permit? in which menu do I find it?

Thanks,
[Galaxy S 4 Mini Original Android Development] rho-bot:
Just reflash the LOS ROM, this will delete the TWRP app, and you will be reasked again, this time deny.

Under settings, you can disable the check for TWRP app, not to be asked again.
[Galaxy S 4 Mini Original Android Development] Skenkz:
ok rho-bot i'll test in the nex days. Did you have the same problem? Did removing those permissions work?
[Galaxy S 4 Mini Original Android Development] bierma32:
I never have installed the TWRP from Recovery or App Store.

If you go advanced wipe and format or repair system partion , this will remove the TWRP App.

Than you must reinstall the ROM and Gapps ( if you want it )

Also if you want to install Magisk than you must boot into the LOS , go back to TWRP and flash Magisk.
[Galaxy S 4 Mini Original Android Development] Humphrey.Bear:
Hi,

I upgraded my UK GT-I9195 recently using the instructions at theupgradeguide.com

All went (surprisingly) well, and everything seems to be working ok. This has given my beloved S4 mini a new lease of life - many thanks and much appreciation to arco68 for all your hard work :good::)

Just a couple of niggles arising:

1. Tried to install OpenGApps packages, but got capacity errors on the system partition for anything larger than the "micro" package. Did anyone else get this, or was it just me? I assume this is down to the size of the (stock partition), which may be configured differently by other providers?

2. I am also getting the problem where the screen goes blank during a call and you can't wake it up with any button:

I have set the power button to end calls, but this does not help if I need to use the keypad during a call (unless I only use speakerphone, which is not really acceptable). This is a real pain, and potentially a deal-breaker :(. Does anyone have a fix for this?
[Galaxy S 4 Mini Original Android Development] kurtn:
S4 mini is easy to tear down. Clean proximity sensor.
[Galaxy S 4 Mini Original Android Development] BeeJ1109:
Hi [MENTION=3044346]arco68[/MENTION]

Good Job on this latest release ROM

Just flashed this ROM on my i9195T.

Almost every thing working Great.

One issue. Where Some Apps required Root Access

ExtSD Card has R/W access. Works, but others not working.

Checked Platform.xml has External SD card Read/Write permission. Found the normal parameters missing. Why??

Some apps require these parameters to move apps from internal memory to SD card.

Titanium Backup, also need these parameters to work. Backup files to extSD.

I can edit the file to restore the file back to normal, as same, as Stock, and other LOS ROMs.

Why has this ROM's Platform.xml been modified.

Several lines removed under

permission name = "android.permission.

Read _External_Storage. 1 line

Write_External_Storage. 3 lines

Access_All_External_Storage. 3 lines

Cheers
[Galaxy S 4 Mini Original Android Development] IronRoo:
[MENTION=5899217]Humphrey.Bear[/MENTION]

1. Yes same for everyone, only two smallest gapps packages nano & micro will work, just add any missing apps you want later from Play
[Galaxy S 4 Mini Original Android Development] Humphrey.Bear:
Hello Kurtn,

Many thanks for the response. It looks like it is the proximity detector.

I really didn't fancy pulling the phone apart - I have a history of finding spare parts after I reassemble... :rolleyes:

Found a number of posts in other forums recommending blowing air down the earpiece. It would appear that there is no separation between the two components, so any dust getting into the (open) ear-piece can work its way around and block the proximity sensor :(

Tried it, and it seems to have worked!! (at least temporarily) :)

---------- Post added at 16:37 ---------- Previous post was at 16:31 ----------

Tried to use a gapps-config file to selectively exclude some items and it loaded, but the phone then just hangs when booting up :(

In the end I loaded the pico package and ended up with a nice clean OS (which is fine by me), and loaded just the apps I need from Play :good:
[Galaxy S 4 Mini Original Android Development] steve8x8:
Not having the display updated after a sleep (no lock choice made) has been puzzling me for quite a while. After adding "swipe unlock" this has disappeared - now I'm wondering whether this is a general bug (of LOS, of this build) or specific to by S4mini? Notifications on the lockscreen don't seem to be affected...
[Galaxy S 4 Mini Original Android Development] mtrantalainen:
If I remember correctly, if you get an incoming phone call in this state, the top of the screen will be orange.

I actually know the reason for this. The bad news is that your motherboard is dying. Or actually the failing thing is the Sandisk flash chip on the motherboard. However, unless you've a replacement chip and reflow soldering station, it cannot be fixed. It's time to make backups fast and order a replacement board now. The good news is that a new (recycled) motherboard should cost around ~10€ including postage from aliexpress.com.

I had similar random failures for a couple of months until the phone did hang one last time and after I hold the power button long enough, nothing happened. After gooling for long enough, I was able to get the device to boot directly from a special sdcard (this device has nice unbrick feature where if an sdcard contains full device image at the start of the card - that is no partition table or anything) it will boot from the sdcard instead of internal flash and enter download mode. I was then able to figure out that the flash chip had died and nothing could be written on it.

I replaced the motherboard and the phone is still running fine. Running this LineageOS 9.0 by Arco86.
[Galaxy S 4 Mini Original Android Development] tonny1999:
Help

please help I want to flash and it always gives me error 7 with the latest version of TWRP. Please help me with a link to the appropriate recovery and the steps please.
[Galaxy S 4 Mini Original Android Development] kurtn:
There is more text than "error 7". Make sure your phone is exactly what you think
[Galaxy S 4 Mini Original Android Development] sharkcow:
No, no, no.

It's simply the smart cover feature getting triggered by some magnet (maybe just a speaker of a laptop or the like) getting too close to the phone. Just go to settings->connected devices->connection settings (my translation, might be off a bit), disable the smart cover feature and you're fine! (That for once seems to be a default-enabled feature that really acts like a bug to many... :rolleyes:)

sharkcow :good:
[Galaxy S 4 Mini Original Android Development] jkronegg:
I have two GT-I9195 (seranoltexx) on which I installed lineage-16.0-20190814-UNOFFICIAL-serranoltexx.zip with open_gapps-arm-9.0-pico-20190819.zip: LineageOS is working well on one phone, but on the second phone, I cannot send or receive SMS.

I did a full reinstallation of the second phone with lineage-16.0-20200515-UNOFFICIAL-serranoltexx.zip : I now can send and receive SMS.

The following features are now working on both phones:

- email (send and receive)

- SMS (send and receive)

- phone calls (send and receive)

- photos (storing to phone or SD card)

- gallery (reading from phone and SD card)

- web browsing (both on wifi and 4G)

I didn't test the other features.
[Galaxy S 4 Mini Original Android Development] xyfek:
Hi guys, I've tried flashing this ROM using the latest version of TWRP but I'm getting an error 7, what can I do to fix this?
[Galaxy S 4 Mini Original Android Development] kurtn:
What does the text around error message say?

Try that recovery ?

https://xdaforums.com/galaxy-s4-min...-lineageos-17-1-s4-mini-t4045147/post81671141
[Galaxy S 4 Mini Original Android Development] xyfek:
I was going to do it again to tell you the message, and this time it's flashing! Will see if it works in the end, but it seems it needed a reboot after wiping, does that make sense?

From my google search history there was another error before, something like "E1001: Failed to update system image" and then the error 7 message in red.

It's all done now, will reboot and see if it works!
[Galaxy S 4 Mini Original Android Development] SnowBalls:
After upgrading my S4 mini to this rom a few weeks back, I got this same issue. I never had this issue before the upgrade. A program on my phone was saying that my proximity sensor wasn't sending a signal like it was supposed to.

Thankfully, the other posters here were correct. I disassembled the phone a little to get to the proximity sensor on the inside, detached and pulled it out, and cleaned it gently with a q-tip and alcohol, then I cleaned the little window for the sensor on the screen panel the same way, let it dry for a minute or so, then I tested it while it was still disassembled by holding the battery on the back. It worked. I put the phone back together and it still worked. I just did this yesterday, but so far so good.

I followed this video (=4sOKKoxu3L4 on youtube since I can't make a link) for instructions on how to tear the phone down. He gets to the proximity sensor around the 6 minute mark. Note you don't have to take out every single part he takes out. Just take out the ones you need to get to the proximity sensor. Also note one of my screws was stripped so it had to be drilled, which made the whole process take a lot longer. Otherwise this would have been a pretty easy task.
[Galaxy S 4 Mini Original Android Development] arco68:
First post updated with links to TWRP 3.4.0 images. Note, these are my builds and contains some fixes and changes not in official ones.
[Galaxy S 4 Mini Original Android Development] jkronegg:
I always have to reboot after wiping, otherwise the ROM fails to be installed.
[Galaxy S 4 Mini Original Android Development] arco68:
Sorry guys, I found that roms before Android 10 doesn't flash with the TWRP 3.4.0 I uploaded. I've fixed it and re-uploaded new builds. It's a bug in official TWRP as well.
[Galaxy S 4 Mini Original Android Development] steve8x8:
Sorry for my ignorance [MENTION=3044346]arco68[/MENTION] but what does twrp 3.4.0 address that 3.3.1 does not have (or does wrong)?
[Galaxy S 4 Mini Original Android Development] arco68:
Afaik, mostly better support for system-as-root, which is used in Android 10. Probably other improvements as well.
[Galaxy S 4 Mini Original Android Development] steve8x8:
What's the status of Glonass support? There are rumours that the official builds for S3 Neo (s3ve3gxx, 16.0) now have it...
[Galaxy S 4 Mini Original Android Development] steve8x8:
OK, so probably it's safer now to not change the installed recovery (with 16.0 on top). Will reconsider if I ever move on to 17.1 ;)
[Galaxy S 4 Mini Original Android Development] helium314:
Using a build with (almost) latest sources Glonass somewhat works.

According to SatStat and GPSTest Glonass satellites are used, but I see no improvement. Sometimes the phone finds only/mostly Glonass satellites, in such cases I never got a position even with up to 7 satellites used.
[Galaxy S 4 Mini Original Android Development] tonny1999:
Help

Do you know if someone is working on some PE build for the i9192? It is a great rom that is outdated ?
[Galaxy S 4 Mini Original Android Development] ripee:
I may update my pie thread, if I have time.
[Galaxy S 4 Mini Original Android Development] BeeJ1109:
Arco68 are you using Telegram, I sent you a PM, in regards to some issues with ROM 17.1 and TWRP 3.4.0.

Friendly Suggestion, You should add links are available on page 1, so everyone knows where to find the new builds.

Cheers
[Galaxy S 4 Mini Original Android Development] arco68:
Yes, but I don't like using it for support queries. I've answered your question in 17.1 thread.
[Galaxy S 4 Mini Original Android Development] steve8x8:
Um... with 20200713 build, I'm getting random Bluetooth crashes, about once or twice per week. This didn't happen with the previous versions (I've been using 0311 and 0515 before). Only one device is connected - it's a BLE glucose sensor; losing that temporarily is highly undesirable. Sometimes BT can be re-enabled but most of the time I've got to restart the phone.

Is this a known problem, or is there a change between 0515 and 0713 that could be blamed? Can I safely roll back to (i.e., dirty flash) the 20200515 ROM?

Edit: Why does a post often get duplicated?
[Galaxy S 4 Mini Original Android Development] MrGoodtunes:
That would likely fail. Best way to roll back is to restore the backup you stored right before updating. Or, if you still have some past backup, restore and then flash forward to 0515. You can always just give your dirty roll back a try, but (of course) store a backup first.
[Galaxy S 4 Mini Original Android Development] SnowBalls:
Two questions

Hello,

My phone is GT-I9192

Rom I have installed: lineage-16.0-20200515-UNOFFICIAL-serranodsdd.zip

(Please see posts #1368, #1372, and #1401 of this thread for more info on my install steps if needed.)

I'm having an issue where my screen goes black on its own during regular use. It seems to happen most often when I'm using the Youtube app and/or when I have my torch enabled. Basically it seems to happen more when I'm doing intensive activity with my phone rather than using just one non intensive app (like the calculator) by itself. When it happens, I fix it by pressing the power button to sleep the phone then pressing the power button again to wake it. I tried deactivating LiveDisplay but that didn't resolve it. I opened the phone recently to clean the proximity sensor, but I do not believe I damaged any internal components when I did so. My camera and flash still work fine. I can't think of anything else I might have done to trigger this issue. I recognize it could be a hardware issue, but I do want to note it didn't start happening until right after I upgraded from stock rom to my current rom.

Are my only options to flash stock to test if it keeps happening (i.e. to test if it's a hardware issue), then to flash the current rom after that? Any other ideas I could try before I go down that route?

Question 2: should I update my modem as well? If so, are these instructions still current/accurate?

https://xdaforums.com/showthread.php?t=2768593

Also, I can't find the modem rar file I would need. That thread doesn't have one for USA, and if I click "Mirror for all modems" the website times out. I checked that website multiple times over the past few weeks and it just always times out.

Thanks a ton. I appreciate any and all responses.
[Galaxy S 4 Mini Original Android Development] kurtn:
So flashing latest stock firmware seems like a all-in-one solution. You get latest modem and keep it when flashing custom ROM.
[Galaxy S 4 Mini Original Android Development] BeeJ1109:
Hi arco68,

Can you please provide me the source link for TWRP v3.4.0-0 for i9195. Samsung Galaxy S4 mini. Branches in Github.

Looking for a way to modify Flags in Modem Partition to add Can_be_Mounted Can_ be_Wiped to Can_be_Backed_Up IsPresent. in Tab 4 8.0 MilletWiFi TWRP v3.4.0-4. Build by matteo0026. So TWRP Backup and Restore can wipe the partition before reflashing the Modem.

Thanks for your assistance.

Cheers
[Galaxy S 4 Mini Original Android Development] arco68:
Sources are here: https://github.com/arco/android_bootable_recovery

Build it in Oreo (Lineeage 15.1) after cloning to bootable/recovery-twrp

Then build with "WITH_TWRP=true mka recoveryimage" after lunch target.
[Galaxy S 4 Mini Original Android Development] BeeJ1109:
Hi arco,

Thanks for info.

Did you not mean Launch, not Lunch. Does not make sense!!!!!!

Do you know anything about offline charging and what commands or repository are used for this function.

Instead of only charging, whilst device is online or switched on.

Cheers
[Galaxy S 4 Mini Original Android Development] arco68:
I mean like this:

. build/envsetup.sh
lunch lineage_serranoltexx-userdebug
WITH_TWRP=true mka recoveryimage

What about offline charging? When you boot into that mode, a charger service is started:

service charger /system/bin/charger
class charger
critical
group system
seclabel u:r:charger:s0

The sources are here: https://github.com/LineageOS/android_system_core/tree/lineage-17.1/healthd
[Galaxy S 4 Mini Original Android Development] mtrantalainen:
Android build machinery uses some weird nerd humour and "lunch" is the command required to do full build that took historically so long that it's time to go for a lunch while waiting it to complete. Alternative interpretation is to select "what to have for lunch" and then cook the selected variant.

For details, see https://source.android.com/setup/build/building
[Galaxy S 4 Mini Original Android Development] BeeJ1109:
Hi arco68,

Any updates on LOS ROM 16 ie Security patches for OCT,

Similar update as per LOS 17.1 inc Modem speed patch.

Cheers

BeeJ1109
[Galaxy S 4 Mini Original Android Development] arco68:
Yeah, as soon as I have the time I'll make builds.

Not sure what that modem speed patch is though.
[Galaxy S 4 Mini Original Android Development] BeeJ1109:
Hi Arco,

Modem is very slow on D/L anyway between 5 & 15Mbps not 50+Mbps on Stock.

Got same result on 17.1 Oct build, where you indicated was fixed.

My Suspicions are Lineage repos that are available for several devices Samsung phones and Tablets all exhibit same slow performance on either Modems using emmc or vfat format. But still using the Stock modem untouched work very fast and stable.

Whereas LOS fluctuate either at start or as download transfer speed goes up or down or both during the speed test. I repeat several times over day every few days, to eliminate NBN congestion. IE more users slower the speed. I also use same carrier for comparison to reduce the anomolies.

I have provided you results of my testing 3 of GT-i9305T being Stock 4.4.2, LOS 16 & 17.1.

Same problem with my Tab SM-T330. Stock emmc vs LOS 16 emmc or vfat, build by Matteo or 17.1 by DJAB.

Cheers
[Galaxy S 4 Mini Original Android Development] arco68:
I never said it was fixed. I just reported the speeds I was getting, when testing different Lineage roms as they were.

And emmc or vfat has no relation to network speeds.
[Galaxy S 4 Mini Original Android Development] BeeJ1109:
Hi arco,

Sorry about misunderstanding about fix. I think you meant Chrome lock up fixed.

Further about emmc or vfat, I am looking for a reason for slow download results.

I have experimenting with TWRP versions on Tab 4 SM-T330 builds by Matteo0026.

Further searching I found, using ROM LOS 16 built in August, both emmc or vfat, provided +50 Mbps D/L results, so updating to later ROM builds, he may have, (whilst compiling) got sometime wrong, causing my slow network results.

It is a matter of eliminating any causes, to arrive at the solution. Then move on to next problem.

But I see a lot, Devs are trying to fix multiple issues, all at once, then get confused with what was fixed, only to use the wrong template in future builds.

My main issue has always been, was the ability to wipe modem partition, before reflash, knowing that reflash is clean, instead of dirty. This happens with "vfat is being wiped before reflash". Whereas "emmc is not wiped before reflash". So any issue is left, behind from previous build, is still there, and only been overwritten with update. Result ending with failure, and lots of effort to fix.

Only way I have found is to totally wipe and reflash STOCK ROM. Then Backup with TWRP FULL NANDROID ALL partitions. Then you have a fresh clean backup to restore any partition, as required, when a fault causes boot loops, boot failures etc. Then flash the new Custom ROM.

No one has really explained why emmc modem CANNOT include WIPE, whereas vfat can be wiped.

It is only a option in flags, that should be included in TWRP v3.4.0-x Template repos created for each device TeamWin's TWRP RESPOSITORY in Github,

Some Samsung devices use emmc format in Stock ROM Modem partition, whereas others use vfat format in Stock ROM.

Therefore why the difference, I am asking.

I just wish I had the knowledge to build a TWRP and include my change to add wipe flag into a emmc build.

Regardless of ALL that info, There is still a great difference in performance between STOCK and your Custom LOS 16 and LOS 17.1 builds on my GT-I9195T phones.

Cheers

BeeJ1109
[Galaxy S 4 Mini Original Android Development] 76vitaha:
Arco 9 i9195 end?
[Galaxy S 4 Mini Original Android Development] lxdb_official:
Hello community,

can someone tell me which bugs exactly are there when using this rom and is it usable as a daily driver ?

Thank you
[Galaxy S 4 Mini Original Android Development] arco68:
New builds with November security patches available in first post.
[Galaxy S 4 Mini Original Android Development] BeeJ1109:
Hi arco,

Download file from page 1 links for i9195. Why extension being .jar instead Of normal. zip as listed.

I just removed .jar extension. Zip is installable in TWRP. as is. But just curious why the .jar is added by mediafire servers.

Any fixes, included except security patch.

Cheers
[Galaxy S 4 Mini Original Android Development] Whitest:
Hi [MENTION=3044346]arco68[/MENTION] - thank you for all your support, time and effort put into LineageOS on the S4 Mini.

I’d like to try building Lineage 16 myself, could you maybe help me with some quickstart setup instructions to start my first build? I saw your references to the sources used for this, but couldn’t figure out yet how to combine the multiple repos for building Lineage 16 for the S4 Mini