yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Mini Original Android Development] msbln:
Awesome! Changelog?

Thanks for the serranodsdd-ROM, no serious issues for months!

Is there a changelog for the Nightly-Builds?

edit:

Anyone's memory as bad as mine? Here comes the obvious answer:

download.lineageos.org/serranodsdd/changes
[Galaxy S 4 Mini Original Android Development] kornis01:
Sure, thx for help. Screenshots are embedded as attachment

Odin ver 3.10.7

Samsung USB Drivers 1.5.51.0

stock firmware I9195XXSCQAE_I9195XEOCOD1_I9195XXSCQAE_HOME.tar.md5

TWRP 3.2.1-0 official and TWRP 3.1.N1-0 (download from https://wiki.lineageos.org/devices/serranoltexx/install)

lineage-14.1-20180216-nightly-serranoltexx-signed.zip

OpenGApps 18.02.2018, ARM, 7.1, pico

Steps:

0. factory reset in stock recovery

1. enter download mode

2. run Odin

3. connect usb cable (Odin recognises device)

4. Click AP, select stock firmware tar.md5 file, Click start, end with success (two screenshots)

5. restart to stock rom

6. reboot to stock recovery -> factory reset

7. reboot in download mode

8. flash twrp 3.2.1-0 official in odin -> success (F.Reset Time unchecked, just after reboot enter

recovery to finish twrp installation; two screenshot)

9. in twrp: wipe (swipe) + advanced wipe (two screenshots) + format data (screenshot)

10. reboot to recovery

11. connect usb, mount data (enable mtp), copy lineageos and opengapps zips

12. disconnect usb, disable mtp

13. Error 7 (TWRP not proper TWRP Version), install via TWRP (install->image) version 3.1.N1-0

13 install LOS (screenshot), wipe dalvik/cache

14. install OpenGApps (screenshot), wipe dalvik/cache

15. reboot system

16. bootloop ... ... ...
[Galaxy S 4 Mini Original Android Development] bierma32:
1. So long as if got installed LOS 14.1 , I used the TWRP unofficial from neozone Version 3.1.1.x with out problem's.

2. Has you got an ext. Sdcard. Copy the ROM and Opengapps ( Nano Version ) on the card.

3. For flashing the TWRP use Odin 3.07 or 3.09

3a. At Odin check only Fac.reset, if you see the Pass icon boot directly with the Buttons into the Recovery.( do not boot into System )

4. Go to advanced wipe , wipe cache ,dalvik, System. Data, and Data media.

5. Go Install

Select the Rom and Opengapps

6. Select. Wipe Cache and Dalvik.

7. Reboot System, takes up to 10 min.

Mount nothing !!!!!!!

This way works for me more than 5 years. Also on LOS 15.x
[Galaxy S 4 Mini Original Android Development] kornis01:
The same result :/

is that possible that simlock cause this issue? Because today i realized that my device has simlock...
[Galaxy S 4 Mini Original Android Development] Brentana:
Do not Disturb

Hallo,

i'm wondering if there is a way, a switch or something else that have the ability to disable Do not Disturb mode when calling.

If i remember well there was something like that on AOSPExtended or AICP ROM, so i searched in LOS but no lucky...

thanks, regards,

Luciano
[Galaxy S 4 Mini Original Android Development] alnaloty:
same with me, i9192
[Galaxy S 4 Mini Original Android Development] Luigi.tsukune:
well i have i9192 too

month ago i decided to flash rom stock, to keep original my device only disabling apps i not use, but is not the same, I got tired because apps was consuming more ram, and i hate touchwiz so i rooted and installed recovery again, do a full a wipe, flashed last lineage build and pico gapps, but after 10 minutes when lineage logo load, it got stucked again in booting logo, i waited 1 hour, and it never ends load, i remove the battery, put it again, finally show start screen but apps started to stop working, i tried to do another full wipe and installation, same result, and finally go back to rom stock with odin...........

i noticed my device in rom stock got security updates from samsung, getting security patch to 2017 and in info "about phone" it shows a security info to boot, I did not insist more and keep rom stock for a month, but 2 days ago decided to flash rom stock again with odin to try without updating, this rom is from 2015, i did not allow it to update to that security patches from samsung, i proceed to root and install recovery, and try to install lineage, and it works!

i have last build and everything works fine and smooth.

my advice is if you come from rom stock but allowed updates from samsung, this will not you allow to load Lineage and maybe others custom roms, because it have a security update in the kernel and boot, it allows root and flash custom recovery, but dont load custom roms.
[Galaxy S 4 Mini Original Android Development] kornis01:
I ll try it tomorrow, maybe this is a cause...

I think that i tried various rom versions but i am not sure exactly...

edit: no success, still bootloop...
[Galaxy S 4 Mini Original Android Development] paradiselost28:
Hi,

First of all, thanks a lot for this GREAT ROM !

I wanted to flash Lineageos 14.1 on my old S4 Mini (I9195) and everything was fine : flash TWRP Recovery with heimdall, wipe, flash LineageOS ROM + root + GAPPS.

My only problem is the yellow warning message "Set Warranty Bit : kernel" on startup

Is is possible to "fix" this ? I know it is the Knox Samsung Security but don't really know how it works.

My LineageOS is booting fine, TWRP too, and i have root access.

Thanks a lot for your help !
[Galaxy S 4 Mini Original Android Development] mielletseed:
There is no fix - the bootloader is detecting the not signed kernel and shows this message ...

You only see it a very short time at boot up - learn to live with it ;)
[Galaxy S 4 Mini Original Android Development] paradiselost28:
Thanks for answering mielletseed. Too bad there is no "fix" for this.

I just hope there is no limitation with number of flash (i want to update this nice release very often)

Have a nice day !
[Galaxy S 4 Mini Original Android Development] Luigi.tsukune:
that depends of life time of your eMMC writing and reading processes
[Galaxy S 4 Mini Original Android Development] VikSn0w:
After the installation of LineageOS the device says No Sim Detected, please help me
[Galaxy S 4 Mini Original Android Development] bierma32:
More Details please.

1. from which Version you are coming, Stock or Customrom ?

2.Which Recovery you are using TWRP from neozone or TWRP official ?

3. is your Phone SIM locked ?

Are you tried to go back to Stock and see it is working ?

Have you create a EFS and Modem Backup ?

Have you restored some Datas from Backup ?
[Galaxy S 4 Mini Original Android Development] Pup0:
View Cover problem

Hi,

ROM is SUPER!

But here is a problem with original View Cover. Turn ON/OFF of display go normal, but it is not possible acccep incoming calls or turn off alarmclock throgh the window of cover.

PLS. Have You some reason?
[Galaxy S 4 Mini Original Android Development] Poluxor:
Guys

There is posobility to enable landspace mode for main menu?

Like this: https://i.ytimg.com/vi/9vGfj2WZZxE/maxresdefault.jpg

If no do u know which rom provide this?
[Galaxy S 4 Mini Original Android Development] turbare:
Did anyone successfully went back to stock firmware after being on Lineage? If yes, how?
[Galaxy S 4 Mini Original Android Development] bierma32:
Wipe factory reset and your int.Sdcard ( Data media )

Flash Stockrom with Odin. All is done.
[Galaxy S 4 Mini Original Android Development] Luigi.tsukune:
last saturday i returned from lineage wihout issue because i was having issues with battery, but it was the battery, so i bought a new one, to back to stock i always first go to twrp recovery, do a full wipe, go to "reboot option" and select power off, then just flash rom stock with odin and its boot succesfully,

as bierma32 says, if you just flashed with odin and dont boot, just go to recovery and do a data factory reset and a wipe cache partition,

i dont know if i want back to lineage, i hate touchwiz, but i noticed rom stock+root+deleting unnecessary apps it becomes smooth

is more being lazy than nerve to back to lineage xD
[Galaxy S 4 Mini Original Android Development] Bernd.Defy:
Try this: https://xdaforums.com/showpost.php?p=72236050&postcount=1188
[Galaxy S 4 Mini Original Android Development] IronRoo:
Anyone else got problem with Signal Private Messenger keep stopping since this weeks update 0317?
[Galaxy S 4 Mini Original Android Development] IronRoo:
it would seem to be this issue, affecting all builds with March security patch running Signal beta ver & several other apps

https://github.com/signalapp/Signal-Android/issues/7534

Devs are working on it, it seems, it affects other apps also
[Galaxy S 4 Mini Original Android Development] DonQuichotte:
Hi,

no problems with Signal on "lineage-14.1-20180317-nightly-serranoltexx-signed" here. All working fine.
[Galaxy S 4 Mini Original Android Development] IronRoo:
Thanks mate! What version of Signal are you on, ver 4.15.5 or earlier? I am on the beta channel ver 4.17.4, but it first crashed on 4.16 the day I updated LOS, I thought 4.17.4 was going to be the fix, unfortunately not.

It seems it's only Signal versions after 4.15.5 that now use the hardware keystore (instead of software, actually I didn't think we even had a hardware security chip) which are affected or the cause is our blob :confused: (I think I am missing something as doesn't quite make sense to me, this is what the devs are saying https://jira.lineageos.org/browse/BUGBASH-590)

So long story short, don't update Signal to 4.16+, or you might get issues (though one post implied it might not always break, so back up your messages first to be safe)
[Galaxy S 4 Mini Original Android Development] DonQuichotte:
Hi IronRoo,

right now I'm on Signal v4.16.9. On your linked Signal Github issue tracker they assume it happens only when updating to a new security patch level. For quite some time I update phone only when new monthly security patch levels are released and don't take the weeklies...just for the record.

Regards DonQuichotte
[Galaxy S 4 Mini Original Android Development] IronRoo:
Oh, OK , one comment said it happens only "sometimes" that LOS messes up data .....

I think I was on 4.17.3 when I updated & Signal first failed. Thanks
[Galaxy S 4 Mini Original Android Development] chillilounge84:
Hello everyone! chillilounge84 here.

I'm stock with the 14.1.1 build from April 2017 that [MENTION=5416372]csendre[/MENTION] compile. I want to upgrade to this official build, but I don't know a thing that I would thank for clarify it:

What about the backups? From the apps like the ones that one could create with TitaniumBackup or the NANDdroids?

This is the main reason that I had no upgrade when it became official. I really would thank any help.

PD: I use TWRP as my recovery.
[Galaxy S 4 Mini Original Android Development] gaga-man:
Hi,

is there an app like apps2sd on the i9195 with latest LOS 14.1 working with selinux enabled?

Thanks for your hints

Berny
[Galaxy S 4 Mini Original Android Development] heilbron:
I'd suggest to you to get Titanium Backup from Play Store and backup the apps where the data is important to you!

Then follow the guidelines for a clean installation and then reinstall the backupped apps one-by-one! Enjoy!
[Galaxy S 4 Mini Original Android Development] chillilounge84:
Well, I didn't understand...

In the OP, it says do not restore backups or something like that. That's the thing I wanna know. Also thank for your response!
[Galaxy S 4 Mini Original Android Development] heilbron:
The only contradiction to the OP I can see is, that I like to use Titanium Backup (PRO). You might want to restore and reboot the apps (sort of) two-by-two. And if something breaks just delete its data again. Sometimes Titanium can even help to migrate the data of systems apps....
[Galaxy S 4 Mini Original Android Development] chillilounge84:
So, the thing is ONLY restore the apps one by one?

Well, I use the standard Titanium Backup so I don't believe I would have issues...
[Galaxy S 4 Mini Original Android Development] Mohammed Bhere:
I want IOS11 font for LOS ?
[Galaxy S 4 Mini Original Android Development] gabilloillo:
Excelente ROM, working perfectly, thnx =)
[Galaxy S 4 Mini Original Android Development] kentchristopher:
What kernel and baseband is everyone using? I'm running the March 17 build and I've been having issues with the GPS being unresponsive (not getting registering any satellites) and the phone not getting a signal, both issues fixed with a reboot. Needing to reboot once in awhile is one thing, but needing to reboot twice in 3 hours... that's another. :)
[Galaxy S 4 Mini Original Android Development] IronRoo:
I just use the kernel that comes with each ROM update , haven't noticed any changes in GPS performance , someone was having issues end of last year, was it igo app?

using 19195XXUCQG1 baseband (for LTE only) nor problems with loss of signal.

I would try the kernel that comes with ROM, before looking for other cause.
[Galaxy S 4 Mini Original Android Development] kentchristopher:
That may have been me you're referring to as I've posted about troubles with GPS with this ROM before. I'm using the included kernel, so this makes me think (again) there really is some issue with my baseband (unless it's the hardware).

If anyone has been using an i9192 (dual SIM) with no problems using Lineage, I'd appreciate hearing what baseband you're using so I can give it a shot.
[Galaxy S 4 Mini Original Android Development] ptr1968:
gps fix

The S4 (mini) when they getting older can have hardware problem with contacts of gps and gsm signal. It easy to repair, like on the youtube link below.

I didn't do the alupaper but bend the contact a bit up and put little silver paste/ copper grease. Also do the contact of gsm antenna. After this better signal and nomore need to reboot.

https://www.youtube.com/watch?v=kMNb8BVr540

I've had several s4 mini now, and been on oreo and nougat, but marshmallow has by far the quickest gps fix
[Galaxy S 4 Mini Original Android Development] kentchristopher:
After spending the past day or so trying to flash a different version of the stock ROM in order to change basebands, with the idea to then flash back up to this ROM and hope my connection and GPS problems were cured, I can say with great confidence that baseband DOES matter with this ROM - something which doesn't seem to be mentioned in the OP or first few pages of this thread.

I flashed a 4.4.2 stock ROM which happily gave me much-improved phone signals and snappy GPS fixes, so from that I knew it wasn't a hardware issue. (Not a surprise, really.)

However, once I began the process of trying to flash back to Lineage 14.1, the problems began: over and over again at first boot, the phone would do a half-second vibrate after a few minutes, shortly after the Lineage title would appear, then disappear again, sometimes with a split-second flash of a warning screen saying an app had stopped working. Then it would return to the Lineage loading animation and sit there endlessly. Rebooting never fixed the issue, nor did reflashing or doing factory resets (before flashing, after flashing, both - didn't matter). I tried different recovery methods (3 versions of TWRP, Phil's Touch, CWM).

Curiously, CM11 and CM13 both worked fine after flashing (using TWRP 3.0.3-1, for reference, though I don't think the recovery version would've mattered).

What finally got me into a working Lineage 14.1 was flashing a bootloader & modem file for my i9192 which I stumbled onto in this thread for TWRP 3.2.1-1. Whether this will solve my more long-term problems with GPS, only time will tell. But at least I have a device that gets phone signals and a GPS fix and isn't needing to be rebooted every few hours (so far).

Given this, for the benefit of all users, I think it would be wise to come up with a list of working basebands compatible with this ROM for each device version (i9190, i9192, i9195) and get this info included in the original post, preferably with links.

So, if you're reading this, and you've been running this ROM and things have been working great, PLEASE go into your About Phone and mention which baseband version you're using!

I appreciate the suggestion, but for anyone else who encounters GPS problems, I would suggest eliminating other possibilities before messing around with the hardware. By flashing a stock ROM, it was clear to me that this wasn't a hardware problem, as the GPS got a fix almost shockingly fast on a stock 4.4.2 ROM.

Faster than stock, you think? I tried CM13 briefly today in trying to figure out what was going wrong, and the GPS Test results seemed fine, but my sense was that they still weren't as good as stock.
[Galaxy S 4 Mini Original Android Development] ptr1968:
Yes, the original rom was terrible for me, many random shutdowns.

With cm13 i'm using fastergps (not in store anymore, but can find apk) this i set my specified region, usual gps fix in 1-15 sec.

CM14 en 15 have no glonass fix.

Which baseband are you using now then? And in which country are you

(i'm using baseband i9195XXUCPI1 now )

peter
[Galaxy S 4 Mini Original Android Development] chillilounge84:
Hi [MENTION=694563]kentchristopher[/MENTION], after downloading google maps from the store to test the GPS I found that works fine.

I put a screenshot of my system info & baseband.

Also I want to thank [MENTION=4203728]heilbron[/MENTION] for the help that he give me. I did the steps from the op (also flashed the migration zip!) and ONLY restored 1 by 1 app at the time. Now I'm enjoying the official ROM, except for the battery that runs out a little bit more than before. By the way thanks bro! :good:

PS: GPS did not want to work until the service asked me to allowing the maps app to use the GPS and it selected the option "High Accuracy". Apparently ONLY with this option will work, no with the other 2 options. I will put a screenshot too.
[Galaxy S 4 Mini Original Android Development] andros90:
[MENTION=3044346]arco68[/MENTION], I use the latest official build, but when I try to record a call, that noise gets in the way of recording my voice, the link with audio is a recording I made https://vocaroo.com/i/s1sZ72yLBdbu

My model is I9192
[Galaxy S 4 Mini Original Android Development] kpjuk:
I9195 stuck on downloading screen

Hi guys,

I tried to update my phone to LineageOS, and the first step was to install Twrp. I used ODIN to install TWRP, but whenever it reboots, it comes up with the Downloading screen. Any ideas how I can break out of this to get LineageOS on to my phone?

Kev
[Galaxy S 4 Mini Original Android Development] mielletseed:
Are you sure you have an I9195 and not a I9195I (value edition) or when you have an I9195 did you flash I9195I's TWRP?
[Galaxy S 4 Mini Original Android Development] kpjuk:
Your correct, I have an I9195l edition, and the TWRP version was I9195. I thought this would be good for all I9195 versions ?

Is there anything I can do to recover? When I turn it off, it turns itself back on into Downloading mode. I can't enter recovery mode, it defaults to the Download Mode.

ODIN doesn't pick up a com port, so I can't even use that to reflash.

The bottom line on the screen says in Blue

SECURE DOWNLOAD : ENABLE
[Galaxy S 4 Mini Original Android Development] mielletseed:
No, the I9195I is completely different inside, it's a seperate model ...

pull the battery and try then to enter download mode and then flash the stock rom or maybe you just can flash the correct TWRP directly
[Galaxy S 4 Mini Original Android Development] kpjuk:
Thanks mielletseed,

I have removed the battery and left it for 90 minutes. When I plug the battery in it starts automatically and shows the following screenshot

[IMG="Galaxy S4 mini screenshot"]http://www.stosys.com/Odin.jpg[/IMG]

The bottom line in blue says

SECURE DOWNLOAD : ENABLE

I can't get into the recovery option.

Any ideas?
[Galaxy S 4 Mini Original Android Development] kpjuk:
OK, so if I hold the power vol down and home key and keep them pressed down , I eventually get the initial download screen appearing which gives me a chance to cancel the download. More importantly, if I then connect the USB and hit the vol up button on the phone, Odin recognises that the phone is connected so I hopefully can flash the stock ROM. I'm just downloading it now, so fingers crossed........
[Galaxy S 4 Mini Original Android Development] kpjuk:
i9195I

Good News,

I downloaded the stock firmware from Sammobile and it flashed OK.

Thanks for your help guys, its really appreciated. I just need to find the right TWRP version so I can get LineageOS on now .

Kev J.
[Galaxy S 4 Mini Original Android Development] mielletseed:
But get the right one for your device! This one is not fitting ...
[Galaxy S 4 Mini Original Android Development] hrodeberht:
What can I do?

lineage-14.1-20180331-nightly-serranoltexx-signed.zip

got 404 not found when I try downloading with updater/mozilla firefox.

Regards

hrodeberht

Best wishes

hrodeberht
[Galaxy S 4 Mini Original Android Development] ghines:
Yep, link is broken.
[Galaxy S 4 Mini Original Android Development] hrodeberht:
Where I can I report, exist that possibility?
[Galaxy S 4 Mini Original Android Development] Freddew:
Hi,

I think reporting it right here, like you've already done, makes a lot of sense.

Work may already be in progress to solve the problem.

Thanks for reporting it :)
[Galaxy S 4 Mini Original Android Development] IronRoo:
In case you didn't know you can also download it manually, link working currently

https://download.lineageos.org/serranoltexx
[Galaxy S 4 Mini Original Android Development] hrodeberht:
Yesterday I tried with Browser (Firefox) and the download doesn't worked too. But its repaired. Both methods are working yet. Updated already today to newest lineageos.

Thank you.

Regards

hrodeberht
[Galaxy S 4 Mini Original Android Development] csendre:
I tested call recording on a clean install of the latest (03/31) official nightly and I could not reproduce this noise on a 9192. I made two recordings, both were good.
[Galaxy S 4 Mini Original Android Development] andros90:
Did you talk on the recording? This noise only appears from the moment I speak.
[Galaxy S 4 Mini Original Android Development] csendre:
Yes. I recorded a 20 minute conversation with a friend. I am thinking it may be microphone sensitivity related. Your recording sounds like distortion due to high gain.

I have an idea, will play around with audio HAL settings on my phone.
[Galaxy S 4 Mini Original Android Development] DalvikCacher:
I have flashed lineageos and gapps. It works alright except while my phone is opening it says at top left of the screen "set warranty bit:kernel" In addition I did not wipe dalvik cache. Is that the cause of this warning?
[Galaxy S 4 Mini Original Android Development] mielletseed:
No. The "warning" is because you aren't using stock rom / stock kernel signed by Samsung ...
[Galaxy S 4 Mini Original Android Development] Kotbest:
I have flashed my 9190 with 14.1.

Everything fine, but i little disapointed when using S-View cover. I can't answer incoming calls (screen doesn't response) and i don't see statusbar (battery level, notifications etc) like in stock firmware.

Flip-case settings is on.

Any suggestions?
[Galaxy S 4 Mini Original Android Development] Brentana:
Same problem here, exactly the same, I9195.

It seems to me that the audio gain, for my voice, is too high: only in recording of course, no problem in normal usage.

Tested another (ACR) app with audio gain selectable: +4db cause the same noise

regards, Luciano
[Galaxy S 4 Mini Original Android Development] Brentana:
Hi all, HELP please....

Lately, when i receive a call o making a call, i can't hear the people on other side of the line.... The strange is that the person i'm in conversation can hear me without any problem....

If i'm making a call, when this thing is happening, i can't even hear the classic tu-tuu......

Often, the phone spontaneusly reboot itself.

If the phone reboot, or i reboot the phone, for some time all is ok, then suddenly.... bang! really annoying.

This was happening in the past, then i had a period of happy time when i flashed a new modem, because i thought the problem was modem related.... but, after flashing LOS february release, the situation is coming back. Tried any new LOS release with no solution....

Before completely erase and trying to reinstall everything, anyone has an idea of what could be the cause and a solution?

Thanks, Luciano