yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Mini Original Android Development] mtrantalainen:
Here's a successful boot with previous release (lineage-16.0-20190516-UNOFFICIAL-serranoltexx.zip) on the same hardware:

https://pastebin.com/qW5bWbSE

Following differences may be important:

Unsuccessful boot seems to be missing following lines (these are from successful boot):

[ 4.263604] Atmel MXT336S 3-004a: 555clear_cover_enable = 0
[ 4.280085] Atmel MXT336S 3-004a: [GDC] changed gdc_value Init -> Init
[ 4.380405] Atmel MXT336S 3-004a: [GDC] changed gdc_value Init -> Init

(to be exact, the failed boot has similar lines once and successful boot has these twice - perhaps hardware has some quirk that requires doing this part twice or the hardware may fail to work? ... or perhaps this is the race that causes the problem in the first place?)

and a bit later FAILED boot emits

[ 8.981199] [mdnie lite] send tuning cmd!!
[ 9.191240] mipi_dsi_wait4video_done: video_done timeout error
[ 9.397894] mipi_dsi_cmd_dma_tx: dma timeout error
[ 9.401953] dumpreg: =============IT's Fail case ==============
[ 9.407752] [0000] : 03020202 03020202 03020202 03020202
[ 9.413093] [0010] : 03020202 03020202 03020202 03020202
...
[ 9.919273] [<c00140f8>] (unwind_backtrace+0x0/0xec) from [<c036b130>] (mipi_dsi_cmd_dma_tx+0x268/0x344)
[ 9.931237] [<c036b130>] (mipi_dsi_cmd_dma_tx+0x268/0x344) from [<c036b310>] (mipi_dsi_cmds_tx+0x104/0x17c)
[ 9.940088] [<c036b310>] (mipi_dsi_cmds_tx+0x104/0x17c) from [<c036bb78>] (mipi_dsi_cmdlist_tx+0x3c/0x54)
[ 9.951228] [<c036bb78>] (mipi_dsi_cmdlist_tx+0x3c/0x54) from [<c036bda0>] (mipi_dsi_cmdlist_commit+0x120/0x158)
[ 9.960537] [<c036bda0>] (mipi_dsi_cmdlist_commit+0x120/0x158) from [<c036beb8>] (mipi_dsi_cmdlist_put+0xe0/0x110)
[ 9.974576] [<c036beb8>] (mipi_dsi_cmdlist_put+0xe0/0x110) from [<c034c3b0>] (sending_tuning_cmd+0xbc/0xe0)
[ 9.983427] [<c034c3b0>] (sending_tuning_cmd+0xbc/0xe0) from [<c034cda8>] (mDNIe_Set_Mode+0x9d4/0xc6c)
[ 9.992644] [<c034cda8>] (mDNIe_Set_Mode+0x9d4/0xc6c) from [<c034d170>] (mode_store+0x94/0xbc)
[ 10.001342] [<c034d170>] (mode_store+0x94/0xbc) from [<c01b32e0>] (sysfs_write_file+0x108/0x13c)
[ 10.010102] [<c01b32e0>] (sysfs_write_file+0x108/0x13c) from [<c01598b0>] (vfs_write+0xac/0x160)
[ 10.019746] [<c01598b0>] (vfs_write+0xac/0x160) from [<c0159bfc>] (sys_write+0x38/0x64)
[ 10.026827] [<c0159bfc>] (sys_write+0x38/0x64) from [<c000de60>] (ret_fast_syscall+0x0/0x30)
[ 10.234579] mipi_dsi_cmd_dma_tx: dma timeout error
...
[ 11.345612] qup_i2c qup_i2c.3: Transaction timed out, SL-AD = 0x4a
[ 11.351869] qup_i2c qup_i2c.3: I2C Status: 110000
[ 11.356600] qup_i2c qup_i2c.3: QUP Status: 0
[ 11.360811] qup_i2c qup_i2c.3: OP Flags: b20
[ 11.365054] Atmel MXT336S 3-004a: mxt_read_mem fail[-110] address[0x10a]

From that on it looks like i2c bus is not in the correct state. I think this is a kernel bug in June build. Maybe the initialization code is erraneously skipped or there's some kind of race conditition where the initialization would be started too late?
[Galaxy S 4 Mini Original Android Development] arco68:
Not sure why boot fails for some of you guys, and it doesn't happen for me here. Nothing has been changed in kernel since previous build either. Weird.
[Galaxy S 4 Mini Original Android Development] Jules63:
I have loaded this rom now on my spare phone and it all looks very good, thanks arco68. A couple of things I notice is the auto screen brightness seems to not work correctly (the brightness tends to get too bright and stay there) and the wifi keeps dropping the connection when the phone sleeps even though battery saver is set to balanced.
[Galaxy S 4 Mini Original Android Development] cdurex:
Had some issues with bootloop and device not turning on lineage-16.0-20190516 build but strangely it was related to the battery. Bought a new one and problem disappear.
[Galaxy S 4 Mini Original Android Development] theeightstar:
Neither does it happen to me (GT I9190 + June update + GApps + TWRP 3.3.0).
[Galaxy S 4 Mini Original Android Development] Arslan140:
Looks like this bug only effect Lineage 16 june build

on the other hand RR pie june build works fine no bootloop at all(currently using it)

---------- Post added at 05:48 AM ---------- Previous post was at 05:39 AM ----------

:rolleyes:
[Galaxy S 4 Mini Original Android Development] chickenscanfly:
I had reboots and boot loops with the June build, which was Magisk related. I had Magisk 19.3 flashed. clean install (ROM then Gapps) then flashing Magisk 19.0 fixed it (I also used Magisk 19.0 for the April build with no issue).

I'm on GT-I9195 with twrp-3.3.1-0-serranoltexx.img.tar, lineage-16.0-20190609-UNOFFICIAL-serranoltexx.zip, open_gapps-arm-9.0-pico-20190612.zip, Magisk-v19.3.zip (updated from Magisk-v19.0 through the Magisk app).
[Galaxy S 4 Mini Original Android Development] mtrantalainen:
Could you save kernel log? Minimum steps to get log if you have a working adb and TWRP:

When the device is boot looping, press and hold VOLUME UP + HOME until the boot loop repeats and you get blue "RECOVERY" text in top left corner. Attach the phone to computer and wait for TWRP to finish booting (the order to attach the phone and TWRP booting is not important). Run following on the command line

# linux variant
adb shell cat /proc/last_kmsg > ~/Desktop/boot-loop-kernel-log.txt
# windows variant
adb shell cat /proc/last_kmsg > %UserProfile%/Desktop/boot-loop-kernel-log.txt

You can then copy-paste the full log to https://pastebin.com/ and share a link here.

Note that you must not remove battery or do anything between the boot looping and entering the recovery because the log from last kernel run is extracted from RAM during the recovery boot.

Long version: https://xdaforums.com/showpost.php?p=64043477&postcount=2
[Galaxy S 4 Mini Original Android Development] mtrantalainen:
Boot is quite CPU intensive and emmc (and possibly sdcard) is accessed in the same time. An old battery that may appear to work otherwise may fail to provide adequate power (ampere rating) and system will end up unstable.

I once had battery that caused random system reboots when the battery meter displayed anything below 50%. Replacing battery fixed the problem.

Apple didn't lie when they told that the OS update that slowed down old iPhones was intentional to avoid crashes. The correct fix is to make battery replacement easy (e.g. S4 Mini).
[Galaxy S 4 Mini Original Android Development] Alienatick:
[MENTION=3044346]arco68[/MENTION] now I'm sure it's Trebuchet/SystemUI causing the screen issue. I applied a theme in substratum and changed system font on LOS 15.1, and the same thing happened. If you could check it would be cool.
[Galaxy S 4 Mini Original Android Development] mtrantalainen:
I returned back to build lineage-16.0-20190516-UNOFFICIAL-serranoltexx and one thing that I can see is different is the Display settings options. June build allows setting mDNIe options which I remember to have played with. Perhaps the June build fails with some specific settings here (I think I selected Natural or Cinema and adjusted color temperatures). If you can give me a filename to extract from the TWRP backup, I can provide my exact configuration - I created a TWRP backup before wiping the phone again.

Do you know which kind of changes were made for mDNIe support regarding early boot process? Failed boot log (https://pastebin.com/x4ZVPp09) shows that userdata and cache were already mounted so user settings may affect the boot failure. Successful boot log emits

[ 10.252464] [mdnie lite] [B]is negative Mode On = 0[/B]
[ 10.252495] [mdnie lite] [B]negative off when resume, tuning again![/B]
[ 10.252495] [mdnie lite] mDNIe_Set_Mode start , mode(0), background(1)
[ 10.252495] [mdnie lite] = UI MODE =
[ 10.252495] [mdnie lite] = STANDARD MODE =
[ 10.252495] [mdnie lite] send tuning cmd!!

whereas failed boot log contains

[ 8.928002] [mdnie lite] [B]set background mode : 1[/B]
[ 8.936853] [mdnie lite] [B]mode_store, input background(1)[/B]
[ 8.941461] [mdnie lite] mDNIe_Set_Mode start , mode(0), background(1)
[ 8.954707] [mdnie lite] = UI MODE =
[ 8.971219] [mdnie lite] = STANDARD MODE =
[ 8.981199] [mdnie lite] send tuning cmd!!

My current guess is that the people with boot failing have been modifying mDNIe settings. If one doesn't touch those settings, the system will boot fine.
[Galaxy S 4 Mini Original Android Development] arco68:
June build switched to a livedisplay hal instead of the old java class, so that might be the reason yes.

https://review.lineageos.org/c/LineageOS/android_device_samsung_serrano-common/+/249222
[Galaxy S 4 Mini Original Android Development] Human_Number_103909909301:
Hello Arco thank you for keeping our devices updated. I just flashed this rom today and so far so good, cheers!
[Galaxy S 4 Mini Original Android Development] Human_Number_103909909301:
Well I turned off the phone and now I'm also getting that bootloop :/ [MENTION=9827937]mtrantalainen[/MENTION] thanks for the instructions on how to get the log here's mine ( https:// pastebin .com/U7R8MhQD ) Sorry for the format I'm not able to post links yet. ("To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!").
[Galaxy S 4 Mini Original Android Development] Terraandroid:
Excellent job ! Thank you ... GT I9195 serranoltexx EXCUSE MY ENGLISH...
[Galaxy S 4 Mini Original Android Development] Anirudh Kartik:
Is there a working sound mod for this Rom? I tried V4A but it made the camera crash.

Is there a Dolby zip?
[Galaxy S 4 Mini Original Android Development] kurtn:
I've had good results with v4a magisk module. No Dolby seen yet. AudioFX sometimes works well. In some cases i trigger audioFX by switching mono audio in accessibly menu.
[Galaxy S 4 Mini Original Android Development] TnA.Plastic:
I have a weird Battery-Drain since installing the June-build with the gapps from that day.

Mid-May-Build was working well with around 4days of Standby (while being connected to LTE).

Btw.: Is there a function to force 3G-only? That would be pretty cool, because I don't often need LTE on this phone and it runs for quite a while on 3G. I remember that it was possible with one of those tiles in the drop-down-settings.

Screen-Blanking-Bug still occurs. It however crashes to various colors, but it's only ever one color on the whole screen, once it gets triggered.
[Galaxy S 4 Mini Original Android Development] kurtn:
It's under settings network mobile advanced
[Galaxy S 4 Mini Original Android Development] TnA.Plastic:
Oh! Thank you very much!

Nevertheless, the battery draining-issue (since first June-version) and the display-blanking-bug (since every LineageOS 16.x) are still present.
[Galaxy S 4 Mini Original Android Development] kurtn:
General bug investigation: start with a clean installation and try to reproduce the bug by applying your modifications step by step.
[Galaxy S 4 Mini Original Android Development] TnA.Plastic:
Tried it with a clean install without and with gapps.

Dalvik cache, cache and system was wiped before as well... :-/

Anyway... I give it a new try on the next build. I only hope for the screen-blanking-bug to be resolved, because that's the most annoying thing!

Btw.: Does SuperSU work with this ROM?
[Galaxy S 4 Mini Original Android Development] kurtn:
[MENTION=5626369]TnA.Plastic[/MENTION]
[Galaxy S 4 Mini Original Android Development] mielletseed:
For me SuperSU stopped working with May or June build and I had to switch to Magisk.
[Galaxy S 4 Mini Original Android Development] chillilounge84:
I flashed this ROM severel times without GApps, and then once with GApps, and nothing had happen to me yet. I also rebooted several times with and without GApps and nothing.

Also removed my baterry for a couple of minutes and nothing too. My battery has a date of 2015.04.11 on the back wich is a consederably old battery, also it dosen't hold the charge as it use to do a year ago. So even if my battery is not working properly or not, I haven't experienced this yet.

Maybe it works for me because of this, I don't remenber touching thoose settings or maybe any add-on or pacakge haven't done yet.

BTW my phone is the GT-i9192 and the previous ROM was the Unofficial LOS 15.1, March 14th build. It was clean flashed, wipe out Dalvik/ART Cache, Chache, Data and System.

Super Su? Magisk? This ROM alredy have Root access on the Developer settings. The only one wich didn't had it was the Official LOS 14.1 version.

I had this issue on several past builds and LOS versions too, but recently I found a somewhat fix: if it happens, lock your phone by pressing the power button and unlock it againg with the same button. Screen goes normally after that.

This issue will be present anyway, but at least you could remove it without restarting the phone.

[MENTION=3044346]arco68[/MENTION] It's alredy implemented or I have to download a package on the link?
[Galaxy S 4 Mini Original Android Development] mtrantalainen:
Your log contains the same problem as mine did:

[ 8.834610] [mdnie lite] set background mode : 2
[ 8.846055] [mdnie lite] mode_store, input background(2)
[ 8.857958] [mdnie lite] mDNIe_Set_Mode start , mode(0), background(2)
[ 8.877735] [mdnie lite] = UI MODE =
[ 8.899252] [mdnie lite] = NATURAL MODE =
[ 8.923393] [mdnie lite] send tuning cmd!!
[ 9.161880] mipi_dsi_wait4video_done: video_done timeout error
...
[ 10.296444] [<c00140f8>] (unwind_backtrace+0x0/0xec) from [<c036b130>] (mipi_dsi_cmd_dma_tx+0x268/0x344)
[ 10.305081] [<c036b130>] (mipi_dsi_cmd_dma_tx+0x268/0x344) from [<c036b310>] (mipi_dsi_cmds_tx+0x104/0x17c)
[ 10.314817] [<c036b310>] (mipi_dsi_cmds_tx+0x104/0x17c) from [<c036bb78>] (mipi_dsi_cmdlist_tx+0x3c/0x54)
[ 10.325255] [<c036bb78>] (mipi_dsi_cmdlist_tx+0x3c/0x54) from [<c036bda0>] (mipi_dsi_cmdlist_commit+0x120/0x158)
[ 10.335235] [<c036bda0>] (mipi_dsi_cmdlist_commit+0x120/0x158) from [<c036beb8>] (mipi_dsi_cmdlist_put+0xe0/0x110)
[ 10.348573] [<c036beb8>] (mipi_dsi_cmdlist_put+0xe0/0x110) from [<c034c3b0>] (sending_tuning_cmd+0xbc/0xe0)
[ 10.357485] [<c034c3b0>] (sending_tuning_cmd+0xbc/0xe0) from [<c034cda8>] (mDNIe_Set_Mode+0x9d4/0xc6c)
[ 10.366763] [<c034cda8>] (mDNIe_Set_Mode+0x9d4/0xc6c) from [<c034d170>] (mode_store+0x94/0xbc)
[ 10.375370] [<c034d170>] (mode_store+0x94/0xbc) from [<c01b32e0>] (sysfs_write_file+0x108/0x13c)
[ 10.385075] [<c01b32e0>] (sysfs_write_file+0x108/0x13c) from [<c01598b0>] (vfs_write+0xac/0x160)
[ 10.393041] [<c01598b0>] (vfs_write+0xac/0x160) from [<c0159bfc>] (sys_write+0x38/0x64)
[ 10.401037] [<c0159bfc>] (sys_write+0x38/0x64) from [<c000de60>] (ret_fast_syscall+0x0/0x30)
[ 10.608545] mipi_dsi_cmd_dma_tx: dma timeout error

I think this is caused by non-default mDNIe settings ("LiveDisplay" or something like that in the settings). Your system seems to boot a bit slower than mine. I have replaced my motherboard due emmc failure. How old your motherboard is? (I'm asking because my device kept getting slower and slower before the emmc chip failed. I never figured out why it was slow until the emmc chip failed.)

---------- Post added at 06:02 PM ---------- Previous post was at 05:59 PM ----------

Thanks for the reference. I read through the patch and it looks fine to me, too. I remember that all the LiveDisplay stuff seemed to work fine when I changed the settings.

Perhaps i9195 has some still unknown hardware quirk that requires that the display is first set to default (standard) mode and changed to user defined mode only later. The May version (which I'm currently running) seems to do this kind of setting during boot.
[Galaxy S 4 Mini Original Android Development] TnA.Plastic:
Well, I know that... But SuperSU and Magisk are more flexible and powerful! ;)

THX for the confirmation!

We are not using these kind of tools to gather root, but to have a more sophisticated and powerful tool of control, which these 2 offer, compared to the original 'management'.

NO it does NOT! You are claiming bollocks here, sorry...

I doubt you know which bug we are referring to, because to my knowledge, this bug is and was only present on LOS16, neither before nor can it be 'fixed' (let's say 'worked around') via what you wrote...

That was THE VERY FIRST THING I TRIED...

Yes, it doesn't fix the issue at it's root, which is the only proper way of fixing it, thus I mentioned that the bug is still present and wait for future builds to fix this.

No, that doesn't work... (on my gt-i9195) I have to either hold Power for 10 seconds or pull the battery. No way around a full restart...

He solely stated there, that they have changed something to the sources... thus it already is (probably) in the June-build and it is suspected to cause the boot-freeze...

There is nothing about it, normal users have to care about and it is nothing to download...
[Galaxy S 4 Mini Original Android Development] Human_Number_103909909301:
[MENTION=9827937]mtrantalainen[/MENTION] Thanks for having a look at the log, you're probably right even arco68 said so. (For me reading the log it's like trying to read some strange language, I'm basically clueless. So I wouldn't be able to tell what's happening or what's wrong even if I wanted to). My board it's still the original :) I've purchased the phone 4-5 years ago (new) so I'd say at least that old. Now I've been using the 'lineage-16.0-20190516-UNOFFICIAL-serranoltexx' for 3 weeks and it's running great I'm really happy, no problems so far (Actually the only thing I found weird, is that under "Play Protect > settings" this section has no text, it's basically a blank page with two switches/buttons).
[Galaxy S 4 Mini Original Android Development] mtrantalainen:
As far as I know, it's not the years that destroy the emmc but writing to it (the emmc refers to flash memory chip by Sandisk soldered on i9195 motherboard). I purchased my phone used when Android 5.0 was still a new OS and I had to replace the motherboard (because that's easier than replacing the emmc chip) this summer and this phone has been my main phone for the whole time. Aliexpress.com has cheap used boards and the replacing the motherboard is not a hard task to do (you just need longish fingernails and a PH0 screw driver). If you ever need to fix anything on the hardware of samsung gt-i9195 (S4 Mini LTE), this is the video you want to watch: https://youtu.be/4sOKKoxu3L4

I assume that your second point was about Play store app and it's Settings - Play Protect - Settings view. It works fine with my phone having header "General" and one option for scanning the device for security threats and another option to send unknown apps to Google to improve harmful app detection feature (which seems to be opt-in by default). I'm running OpenGapps nano package dated close to lineage-16.0-20190516-UNOFFICIAL-serranoltexx build. Do you have custom theme installed? Google apps seem to have most problems with custom themes.
[Galaxy S 4 Mini Original Android Development] ThKr:
Question about security

Hi arco68,

Thanks for this - I installed it on my I9195 replacing the original (yet updated android 4.something), and it works much better now. However, I get a warning from the trust app that says:"this build was signed using public keys", and reading up on it it seems like a minor security issue, but is there a reason why you did it like this?
[Galaxy S 4 Mini Original Android Development] Human_Number_103909909301:
Yes that's exactly what I was referring to, it's something I noticed after the first boot, I like to go through every single option/setting after flashing. I'm not using any custom theme and I've installed the pico package ("open_gapps-arm-9.0-pico-20190620" to be exact). I searched for images to learn what the 2 options were, thanks for pointing them out anyway :) Its good to know that you're not having that issue, it looks like a me problem no big deal. (here's an actual screenshot btw).
[Galaxy S 4 Mini Original Android Development] arco68:
It's implemented in June build.
[Galaxy S 4 Mini Original Android Development] arco68:
It's nothing to worry about really. The warning can be disabled in Trust settings. It just means that the build isn't part of the official Lineage builds, but built by a 3rd party person, in this case me.
[Galaxy S 4 Mini Original Android Development] Spaceoid:
My "favourite contacts" tab in the phone app gets deleted quite often. The one with the star symbol, that shows all recently called contacts. Problem started around 3 months ago, clean flash didnt solve it - is this a common LOS/Android-problem atm? Anybody else experiencing it?
[Galaxy S 4 Mini Original Android Development] kurtn:
I only see deleted favourite if u do a clean install. Inport/export in vcf would be nice.
[Galaxy S 4 Mini Original Android Development] Thoadi:
I use exDialer 195. Not on Playstore anymore, but APK mirror. I can set to show only specific group of contacts and more options then standard dialer... dark theme!

Well, a new dialer with intelligent SIP when wifi available would be good, without the popup to choose SIM or SIP. Not possible to choose while driving (Bluetooth audio).
[Galaxy S 4 Mini Original Android Development] klorgfasder:
You mean the entries in that tab are removed/deleted or disappear (not the tab itself)? I have that, too: I mark contacts as favourites, they appear in that tab and, after a few days not having actually contacted them (by phone, sms), they disappear again - not calling/sms-ing anybody for a few days and the whole tab is empty. I so far thought of this as a misled 'optimization' of pie, but could not find any information in the net (search keywords produce too much irrelevant results).
[Galaxy S 4 Mini Original Android Development] Spaceoid:
Exactly this!
[Galaxy S 4 Mini Original Android Development] jimmynittio:
Absolutely brilliant

Hi arco68,

I upgraded my I9195 with your ROM last week and it's absolute perfection. Everything works beautifully.

Thank you so much.

Are you ever tempted to do one for the I9195I serranoveltexx?

I would love one of your builds on that phone.

Thanks again, you're amazing
[Galaxy S 4 Mini Original Android Development] bierma32:
https://xdaforums.com/galaxy-s4-mini/development/rom-lineageos-16-t3851339

Here are Thread for the I9195 I
[Galaxy S 4 Mini Original Android Development] Claudio4780:
Howdy. Does anybody know why my 9192 shows 2 x folders? Its android and Android with exactly the same content. If possible, which one can I delete without messing up my phone?

Please select attachment
[Galaxy S 4 Mini Original Android Development] alnagar_eg2004:
anybody tried it on GT-i9192 ??

thanks bro

Alnagar
[Galaxy S 4 Mini Original Android Development] Anirudh Kartik:
I think you can delete the android with the small 'a'. The capital one should be the one used by the phone.

---------- Post added at 06:14 PM ---------- Previous post was at 06:13 PM ----------

Yes, works perfectly fine!
[Galaxy S 4 Mini Original Android Development] alnagar_eg2004:
are there any screen shots for this rom on gt i9192 plz ??
[Galaxy S 4 Mini Original Android Development] ahmed20001:
Why SIM does not work how to solve this problem GT-i9192 Rom LINEAGE-16.0-20181210-UNOFFICIAL-SERRANODSDD SIM working on it well The ROM January, February, March, April, May and June SIM does not work in them So what is the problem
[Galaxy S 4 Mini Original Android Development] ahmed20001:
Csendre in Rom Aokp told me if you update the modem will work SIM is it really going to work or what
[Galaxy S 4 Mini Original Android Development] IronRoo:
Should do (make sure to back up your EFS partition with TWRP first, save it to external SD & PC it could save you a lot of trouble if it goes wrong)
[Galaxy S 4 Mini Original Android Development] Anirudh Kartik:
Here you go!
[Galaxy S 4 Mini Original Android Development] arco68:
New builds with July security patches available.
[Galaxy S 4 Mini Original Android Development] mielletseed:
yes, of course
[Galaxy S 4 Mini Original Android Development] fr@nx:
[MENTION=3044346]arco68[/MENTION]

Is your source code completely upstreamed to the Lineage repo? I would like to build a ROM myself with small changes that are important to me. Unfortunately, the build process is currently aborted with an error.

Thank you for your hard work.