[OFFICIAL] LineageOS 18.1 for the Samsung Galaxy S4 (All QCOM Variants)

Search This thread

npjohnson

Recognized Developer
No, I don't think I have any other magnets attached.
I'm just using an authentic S-View phone case from Samsung.

While the clock face doesn't show up when I close the lid of the flip case,

In the Settings app:
Apps & notifications -> Notifications -> Notification history

shows:
Recently dismissed -> FlipFlap: Smart cover detected

and this latter has the correct timestamp matching the time when I closed the lid.
I can also hear a phone ring upon closing the lid when sound is turned on.


For the record, I have another phone with LineageOS 18.1 installed, namely LG G3, which also makes use of FlipFlap for almost similar functionality: the circle area of its flip case should show a clock face upon closing its lid.
Here too, this used to work properly with stock firmaware, but not anymore once LineageOS was insatlled.

Regarding this, the maintainer of LineageOS for LG G3 model kindly answered to my inquiry yesterday: he said he in person is using an authentic quick circle case for LG G3 phone and confirmed that it is working very well.

So now I suspect somes OS settings I make out of habit is preventing FlipFlap from functioning correctly, but I have trouble narrowing it down.
If you go to connected devices, Smart cover, what does it show you?
 
  • Like
Reactions: pocketrule

kitros3942

Member
May 27, 2023
11
1

Attachments

  • Screenshot_20230529-110034_Trebuchet.png
    Screenshot_20230529-110034_Trebuchet.png
    120.4 KB · Views: 38

kitros3942

Member
May 27, 2023
11
1
This will probably not be of much help, but I tried to make this feature work properly by fiddling with various settings.
Then I noticed that when I turn on USB debugging and run adb shell from my PC wirelessly, there is a high chance that the clock face will show up upon my closing the lid of the flip case, only it will show up for some seconds, then disappear, then show up and disappear again endlessly until I re-open the lid. Once this behavior was triggered, I couldn't find a way to suppress it (either make the clock face not show up altogether or make it show up only for once) by tampering with settings save turning off the USB debugging.
 

rw_on_xda

Senior Member
Jun 24, 2013
470
251
Berlin
Specifically, the clock face does not show up in the rectangular area of the flip case upon closing its lid.
I've a Spigen Slim Amor here

S-View functionality is working: shows the clock,date when the Home button is pressed.
even with "smart cover" off I see the Status bar line (provider, signal strength, charge), but no clock, date
I'm on lineage-18.1-20230515-nightly
 
  • Like
Reactions: pocketrule

kitros3942

Member
May 27, 2023
11
1
I've a Spigen Slim Amor here

S-View functionality is working: shows the clock,date when the Home button is pressed.
even with "smart cover" off I see the Status bar line (provider, signal strength, charge), but no clock, date
I'm on lineage-18.1-20230515-nightly
Thanks for your feedback.
I'll wipe my phone, re-install LineageOS and see how things go over the weekend.
 

rw_on_xda

Senior Member
Jun 24, 2013
470
251
Berlin
hint:
my slim amor doesn't have a magnetic closure.
what seems to be for the Samsung's be the case
- me is unsure -
 

kitros3942

Member
May 27, 2023
11
1
Thanks for your feedback.
I'll wipe my phone, re-install LineageOS and see how things go over the weekend.

Hi,

I wiped my Galaxy S4 and re-flashed LineageOS.

Sorry, it took a lot longer than expected, as I had lots of data to back up.

This is how I've proceeded:

- I downloaded the latest official rom file (i.e. lineage-18.1-20230515-nightly-jfltexx-signed.zip) onto the external sdcard of my S4

- turned off the phone and took out the microSD card.

- booted to LineageOS recovery (Home + Volume UP + Power)

- Factory Reset -> Format data / factory reset

- turned off the phone via menu entry from recovery

- re-inserted my external sdcard

- re-booted to LineageOS recovery (Home + Volume Up + Power)

- 'Apply Update -> Apply from Android', then navigated to the file 'lineage-18.1-20230515-nightly-jfltexx-signed.zip' on the external sdcard and flashed it.

- 'Reboot system now'


Then the phone seems to work fine, but unfortunately the functionality still doesn't work.

Settings such as sounds and notifications naturally seem to have been reset, but closing the lid of the flip case just turns off the screen, it does not display the clock-face.

Maybe I'm missing some very simple setting which should have been set up upon booting the freshly installed OS?


Also, what I don't understand is that Google PlayStore is installed by default, despite the fact that I wiped my phone and did not side-load Google Apps.

So I suspect the above procedure does not completely erase the previous installation, and I hope someone will point me in the right direction with regards to doing this properly.

On a related note,:

- At some point in the past I unsuccessfully tampered with Google Apps entry within '/addon.d/' to fix PlayStore which kept crashing, which made LineageOS unable to boot. Upon applying mindgapps addon from LineageOS recovery, LineageOS booted again, PlayStore was not fixed, though.

- Around that time, I also tampered with '/system/build.prop' to deal with an app which refused to run on non-stock firmware. As I could not make this work, I reverted the built.prop file to its original version, but I'm not entirely sure about this.

I wonder if my messing with the above system files influenced the OS not to be properly wiped.
 
Last edited:

kurtn

Senior Member
Hi,

I wiped my Galaxy S4 and re-flashed LineageOS.

Sorry, it took a lot longer than expected, as I had lots of data to back up.

This is how I've proceeded:

- I downloaded the latest official rom file (i.e. lineage-18.1-20230515-nightly-jfltexx-signed.zip) onto the external sdcard of my S4

- turned off the phone and took out the microSD card.

- booted to LineageOS recovery (Home + Volume UP + Power)

- Factory Reset -> Format data / factory reset

- turned off the phone via menu entry from recovery

- re-inserted my external sdcard

- re-booted to LineageOS recovery (Home + Volume Up + Power)

- 'Apply Update -> Apply from Android', then navigated to the file 'lineage-18.1-20230515-nightly-jfltexx-signed.zip' on the external sdcard and flashed it.

- 'Reboot system now'


Then the phone seems to work fine, but unfortunately the functionality still doesn't work.

Settings such as sounds and notifications naturally seem to have been reset, but closing the lid of the flip case just turns off the screen, it does not display the clock-face.

Maybe I'm missing some very simple setting which should have been set up upon booting the freshly installed OS?


Also, what I don't understand is that Google PlayStore is installed by default, despite the fact that I wiped my phone and did not side-load Google Apps.

So I suspect the above procedure does not completely erase the previous installation, and I hope someone will point me in the right direction with regards to doing this properly.

On a related note,:

- At some point in the past I unsuccessfully tampered with Google Apps entry within '/addon.d/' to fix PlayStore which kept crashing, which made LineageOS unable to boot. Upon applying mindgapps addon from LineageOS recovery, LineageOS booted again, PlayStore was not fixed, though.

- Around that time, I also tampered with '/system/build.prop' to deal with an app which refused to run on non-stock firmware. As I could not make this work, I reverted the built.prop file to its original version, but I'm not entirely sure about this.

I wonder if my messing with the above system files influenced the OS not to be properly wiped.
The flip case thingy can be set up under unser settings - connected devices

To remove GApps you have to additionally wipe system partition before flashing.
 
Last edited:
  • Like
Reactions: pocketrule

kitros3942

Member
May 27, 2023
11
1
The flip case thingy can be set up under unser settings - connected devices

To remove GApps you have to additionally wipe system partition before flashing.

I fiddled with the settings you referred to, but can't seem to make it work.

And thanks for the GApps tip, I'll re-flash the OS later today.

maybe a sensor, etc. problem ?
- there should be something that signals the phone/OS the case is closed/open -

Have you tried to check the case functionality on stock ?

On stock firmware, the clock-face used to worked flawlessly with the flip case. Also the flip case is incidentally an authentic S-View case from Samsung, as far as I can tell. So I have trouble understanding why this is not working.

edit: to elaborate, the flip case *is* functional, as the screen turns off when I close the lid, and turns on upon re-opening it. My problem is that the clock-face will not show up properly, no matter what I do.
 
Last edited:
  • Like
Reactions: pocketrule

RoboRebel

New member
Jun 12, 2023
3
0
Hi everyone,
I have installed UNOFFICIAL version (with GApps), it works great, but when I update stock Chrome that built into the firmware (83.0.4103.106) to the latest version from Play Store (114.0.5735.61), it stops rendering pages, and shows blank page upon loading (though with clickable invisible links, if you manage to hit one).
There was the same effect when I installed OFFICIAL version, adding GApps from MindTheGapps-11.0.0-arm-20220217_095902.zip.
Does anyone know a solution to this problem?

The version I installed is from the 1st thread message: https://updater.oddsolutions.us/#/devices/jfltexx/builds , I tried lineage-18.1-20230506-UNOFFICIAL-jfltexx.zip and also the latest 20230612.
Thank you!
 

RoboRebel

New member
Jun 12, 2023
3
0
Update: tried open_gapps-arm-11.0-nano-20220215.zip (which contains no Chrome) with OFFICIAL ROM lineage-18.1-20230515-nightly-jfltexx-signed.zip (no Chrome either), installed latest Chrome 114.0.5735.131 from Play Store, and the same problem with blank pages persist. At first I thought preinstalled Chrome from MindTheGapps somehow interferes with the one I install from Play Store, but obviously this is not the case. It looks like the latest Chrome from Play Store just doesn't work on latest LineageOS 18.1 builds for jfltexx. Can anyone confirm this? Any other ideas I can try?
 

kurtn

Senior Member
Update: tried open_gapps-arm-11.0-nano-20220215.zip (which contains no Chrome) with OFFICIAL ROM lineage-18.1-20230515-nightly-jfltexx-signed.zip (no Chrome either), installed latest Chrome 114.0.5735.131 from Play Store, and the same problem with blank pages persist. At first I thought preinstalled Chrome from MindTheGapps somehow interferes with the one I install from Play Store, but obviously this is not the case. It looks like the latest Chrome from Play Store just doesn't work on latest LineageOS 18.1 builds for jfltexx. Can anyone confirm this? Any other ideas I can try?
Try other browsers.
 
  • Like
Reactions: pocketrule

RoboRebel

New member
Jun 12, 2023
3
0
Thanks for the suggestions!
It looks that you were right -- it's Google's fault after all: Chrome beta 115.0.5790.32 seems to work just fine. Hope it will be fixed in the next stable Chrome release.
 
Last edited:

Retrial

Recognized Contributor & Translator
Jun 10, 2015
3,398
10,134
Athens
Samsung Galaxy S4
Xiaomi Poco F1
Unofficial - built once a month by me, includes GApps and Pixel goodies:
  • jactivelte (GT-I9295)
  • jflteatt (SGH-I337) - Please note you will need to be on bootloader I337UCUAMDB or I337UCUAMDL
  • jfltespr (SCH-R970/C/X, SPH-L720)
  • jfltevzw (SCH-I545) - Please note you need to be on bootloader I545VRUSMDK
  • jfltexx (GT-I9505, SGH-I337M, SGH-M919) - NOTE: GT-I9505G is supported in this build, but due to system size space limitations it will not fit any form of GApps package.
  • jfvelte (GT-I9515/L)
Hi npjohnson, I just noticed you provide unofficial builds for S4. Beside the GApps build-in, what Pixel goodies includes and is there any other difference vs official builds?
Thanks!
 

mentat

Senior Member
Feb 9, 2007
425
276
Big Thanks to npjohnson for supporting our Galaxy S4 devices.
I just updated my old SGH-I337M using twrp-3.6.1_9-0-jflte with
lineage-18.1-20230815-nightly-jfltexx-signed + MindTheGapps-11.0.0-arm-20220217_095902
Performance is far better than expected (for this ancient device).
Thanks, Again.
 

orangepowerpokes

Senior Member
Sep 3, 2016
120
34
Wow I stumbled on my old S4 and was curious what traffic on xda. Years ago, I wanted to flash the older s4 but got stuck somewhere. The lockpad on the boot screen shows unlocked... I wonder if I dig in to see what ATT variant I have maybe I can flash LOS (?) :)
 
  • Like
Reactions: kurtn

Top Liked Posts

  • 3
    Thank you for your quick reply , english isn't my first language but for what i've get , lineageos 18.1 will not be killed but kind of freezin state ? But if the pattern is correct everytime a new lineageos version rise out the older one is killed so lineageos 18.1 will stand for another year and after that will be stopped no?
    "For another year" was correct from the point the changelog 27 was published - which is about one year ago. So, it is not clear yet how things will be in near future.
    2
    I guess a partly answer is here:

    => "Deprecations"

    My view (me is unsure):
    LOS 18.1 might be dead, when LOS 21 hit the scene ...
    There are many deaths the S4 can die. Better have a backup strategy
    2
    maybe los 19.1 will be officialy drop on our s4
    I guess that won't happen (old Kernel and BPF)
    1
    ...
    long time into the s4 custom roms and i wanted to know how long this rom (lineageos 18.1) will be supported ? ...

    I guess a partly answer is here:

    => "Deprecations"

    My view (me is unsure):
    LOS 18.1 might be dead, when LOS 21 hit the scene ...
    1
    Thank you for your quick reply , english isn't my first language but for what i've get , lineageos 18.1 will not be killed but kind of freezin state ? But if the pattern is correct everytime a new lineageos version rise out the older one is killed so lineageos 18.1 will stand for another year and after that will be stopped no?
    I can't get all what you mean, but the last month we got bug and security fixes, see:
    https://download.lineageos.org/devices/jfltexx/changes

    the kernel 3.14.x isn't maintained anymore
    I currently can't tell if this rises security concerns, but as you could read in my previous link between the lines that developers need to have to do some extra work to support the S4.
    I guess it's questionable if they will do the next year too.
    So I could image S4 might be dead next year (but can't tell for sure) and I start thinking about a newer device (Pixel 8/8a, FP5)
  • 6
    Hey all, I am moving and therefore the unofficial update server/wiki will be down for a few days. Likely Wednesday, Friday at the worst.

    Don’t panic when links in the OP don’t work, and your Updater app says something like “Can’t connect to server”. It is planned outage.

    Thanks, see you on the other side!
    4
    Hey y'all - Unofficial build server/download portal is back up.

    It may be hit and miss tomorrow as I rewire everything, but everything /should/ be functional for now.

    Thanks!
    3
    Thank you for your quick reply , english isn't my first language but for what i've get , lineageos 18.1 will not be killed but kind of freezin state ? But if the pattern is correct everytime a new lineageos version rise out the older one is killed so lineageos 18.1 will stand for another year and after that will be stopped no?
    "For another year" was correct from the point the changelog 27 was published - which is about one year ago. So, it is not clear yet how things will be in near future.
    2
    maybe los 19.1 will be officialy drop on our s4
    I guess that won't happen (old Kernel and BPF)
    2
    I guess a partly answer is here:

    => "Deprecations"

    My view (me is unsure):
    LOS 18.1 might be dead, when LOS 21 hit the scene ...
    There are many deaths the S4 can die. Better have a backup strategy
  • 33
    lineage-os-logo.png

    Samsung Galaxy S4

    Code:
    - Your warranty is now void.
    - You have been warned.
    - Use at your own risk.

    Introduction:
    This is the Official Lineage OS 18.1 thread for all Galaxy S4 variants.

    Downloads:
    Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.

    Official Builds:
    • jactivelte (GT-I9295)
    • jflteatt (SGH-I337) - Please note you will need to be on bootloader I337UCUAMDB or I337UCUAMDL
    • jfltespr (SCH-R970/C/X, SPH-L720)
    • jfltevzw (SCH-I545) - Please note you need to be on bootloader I545VRUSMDK
    • jfltexx (GT-I9505, SGH-I337M, SGH-M919) - NOTE: GT-I9505G is supported in this build, but due to system size space limitations it will not fit any form of GApps package.
    • jfvelte (GT-I9515/L)
    Unofficial - built once a month by me, includes GApps and Pixel goodies:
    • jactivelte (GT-I9295)
    • jflteatt (SGH-I337) - Please note you will need to be on bootloader I337UCUAMDB or I337UCUAMDL
    • jfltespr (SCH-R970/C/X, SPH-L720)
    • jfltevzw (SCH-I545) - Please note you need to be on bootloader I545VRUSMDK
    • jfltexx (GT-I9505, SGH-I337M, SGH-M919) - NOTE: GT-I9505G is supported in this build, but due to system size space limitations it will not fit any form of GApps package.
    • jfvelte (GT-I9515/L)

    If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.

    Known Bugs:
    • MHL doesn't work after LineageOS 14.1, and likely never will again, as Google dropped support for it platform-wide in AOSP.
    • Find any? Report them according to this guide.
    Notes:
    • The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
    Kernel Source: https://github.com/LineageOS/android_kernel_samsung_jf
    13
    As @npjohnson said...even my builds seems to work fine, they simply "bypass" some new, Android 12 stuff because our old device can't support.

    Go to data usage, via settings, and check any application data usage. Let's say Chrome. Regardless how much u use the Chrome, the data usage seems zero. That's the problem.

    I personally consider and respect the fact that lineageos wouldn't ship a build which includes a hacky thing that bypasses those network related stuff. This feature is a big change on Android platform, hence, I understand why LineageOS insist on a fix on this

    tl;dr, as nolen said, the problem is on the kernel side and since jf can't have that backported change (I won't mess with it personally), the solutions are 2.

    1. Someone will mess with jf kernel and will backport ebpf (as lineage page says so)

    2. We will restore iptables back. This is my approach and I will personally work on it too. Fixing this will help many legacy device come back but trust me... It's really hard to bring it back
    8
    VoLTE will never work on the S4, or the S5.

    These are from early VoLTE generations - in which there was no even semi-standard method to do it. Samsung and LG both stuffed it into the frameworks side java code and it's hopeless - there are too many subsystems working together on the stock ROM we just can't reverse engineer and tie together on LineageOS.
    6
    There is available 19.1 for S4 by @side so the story doesn't end up here.
    However, tbh LineageOS team shouldn't be so strict with legacy devices to get the tag Official. These devices are old now and needs some "hacks" in order to work which LineageOS team doesn't approve.
    Side is one of us. He's aware of the constraints lol.

    It's not "strict" - the "workaround" people keep linking LITERALLY just ignores the error - data restrictions, data management, and routing in general will always be 100% broken - and that will never be considered "working" - if someone makes that stuff properly work, even if tacky, we're no opposed - just that the current stuff isn't even a hack, it's just "ignore what's broken".
    6
    thanks for response and support
    This issue is now fixed. You will need to sideload the upcoming build by hand to get back on track though.

    Sorry for the inconveniences.