yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 4 Unified Development] therob2:
short questions to the maintainer or to the community: how high are chances to see LOS18/Android 11 runnung on the S4 - I guess after some hard work still has to be done? Are there any showstopper known or could this became maybe reality? Or is there indeed already any work going on (I don't know where to check this)?

And in general: has the 32-Bit CPU (Snapdragon 600/ARM) an limitations in using LOS/apps in the near future (2-3 years) or are any problems with missing 64Bit-Support still some years away? Do you think for a basic (non-game) usege scenario the limited 2GB RAM is a real showstopper?

Background of my question is, if it is worth to have an refurbished S4 + LOS as a basic, low-price and eco-friendly smartphone also for a couple of years or if the end-of-life of S4+LOS is near?

Any thoughts? Cheers, Robert
[Samsung Galaxy S 4 Unified Development] pocketrule:
As there's no LineageOS 18 atm, even no announcement for it, it will take for sure at least half a year until there - might be - a version for the galaxy s4. As Google is crippling each new version by implementing new "security" features, I'm not very eager to see a new LineageOS version as I have been in the past.

And as the main development for the device is done by 2 developers you can't demand they will port the new version, because - as you've stated correctly - to get the update running on that old device, many system and kernel tweaks are neccessary. That's quite a lot of work without proper appreciation (instead some user complaining something's not working or taking too long to implement).

But: Even if there won't be a LineageOS version 18 for the Galaxy S4, you'll get at least official updates for about 1,5 years as LineageOS provides regular updates for the current and the version next to last. So, you can expect an official LineageOS-Version as long as there's no official LineageOS 19. And even if the device is not supported anymore, you could continue to build the rom yourself, as the sources are updated even for outdated versions. There are build instructions e.g. for jfltexx which you can find here: https://wiki.lineageos.org/devices/jfltexx/build

So if you try to push it to the limits, you could have an up to date LineageOS 17 for at least 3-4 years from now on. The key point is though: Do you really want to buy such an ancient device for daily use for the next years? I'm quite impressed by the current performance of it, but of course, you regularly recognize, that the galaxy s4 is a very old device now. For me, it's ok, I use it as daily driver and don't have ambitions to change soon, but especially 2 GB ram is almost a bit insufficient nowadays - even for non gaming purposes.
[Samsung Galaxy S 4 Unified Development] vip5912:
:good:
[Samsung Galaxy S 4 Unified Development] js-xda:
Well said and a good reminder! Running now the second S4 with an up to date OS in my family without any issues. Thank you to all contributors making this possible! :good:
[Samsung Galaxy S 4 Unified Development] slev!n:
I dirty flashed this ROM over Lineage 16 (i9505). I wiped system, cache and dalvik cache and flashed the latest build. Super good job, everything seems to work fine except disabling password when beeing at home (system profiles). I already deleted the old profiles and created new ones but still the same: always need to enter my password when Im in my home wifi. That sucks a lot :/ So is it a matter of dirty flashing or a known issue in this ROM?
[Samsung Galaxy S 4 Unified Development] :
The wifi works fine, so i belive the problem was caused by your dirty flashed instalation, so my recomendatiom is to do a fresh install and the problem is gone.
[Samsung Galaxy S 4 Unified Development] js-xda:
Sudden reboot issue

I am lately experiencing sudden reboot issues with two independent i9505 devices:

before each sudden reboot, the mobile is in active use (various apps like WhatsApp, Bluetooth data sharing or browser) - not in standby

freeze and sometimes black bars on the screen

reboot incl. request for entering SIM PIN (that's why I can say for sure that happens only in active use)

Both devices operate on LineageOS 17.1 (one upgraded from 16.0, one clean installation) without any GAPPS or Magisk or alike. I started observing the first cases around early August and run usually on a recent build. Also observed with almost latest (24.8.) build. One device runs with TWRP 3.4.0, the other one the previous (3.3.1?).

Anyone observing similar issues?
[Samsung Galaxy S 4 Unified Development] droi1:
can anyone recommend working gapps and lineage 17.1 version to me?

I Tried several openGapps Nano

5 September 2020 & older with lineage-17.1-20200827,0813 and 0730.

nothing worked. When phone clean install i choose my last Google backup in setup wizard but after that -> black screen setup wizard starts new no backup aviable anymore, really want to use my google backup, my phone works but with no backup...

sry for bad english
[Samsung Galaxy S 4 Unified Development] kurtn:
Looks like your GApps are working well, but your Google backup is broken. Simply try any phone with stock Android and factory reset.
[Samsung Galaxy S 4 Unified Development] droi1:
my google backup is same version from lineage-17.1-20200827.

strange thing my 17.1 google backup works with lineage 16.0 no black screen here in setup wizard, only thing i get Google assistant error "not updating"... but i prefer to use 17.1 = more updatet ROM. The Problem is not my backup its the Setup wizard broken in 17.1 with gapps

*update

lineage-17.1-20200827 + nano gapps 20200430 skip install wizard and do later wifi connection for "setup your phone" at least my Apps are now back other stuff is not importet but better then nothing. Also with this old Gapps version Google assistant error "not updating" is gone.

also i noticed in older lineage+twrp versions encryption worked fine. now with lineage 17.1 TWRP 3.4.0.0 you can't decrypt the phone in Recovery not even asked for PIN. So i had to remove encryption because i want use twrp backup.
[Samsung Galaxy S 4 Unified Development] ftp_gsd:
Galaxy s4 i337ucsgok3

Is there any option to upgrade Galaxy s4 i337ucsgok3 to LineageOS 17.1, please help with steps incase any..
[Samsung Galaxy S 4 Unified Development] kurtn:
https://download.lineageos.org/jflteatt
[Samsung Galaxy S 4 Unified Development] xperanto:
[MENTION=8031265]kurtn[/MENTION]

Hi kurtn,

in relation to this post

does this still work for you?

It doesn`t update LOS-recovery on my device, even if it is enabled in developer options.

In addition, since it is possible to update recovery within the device itself without hooking it up to i.e. heimdall as mentioned, does anyone know about the "commandline-fu" to do this "manually" with a downloaded recovery-image on a local terminal on the device itself?

Would be great to be able to this!
[Samsung Galaxy S 4 Unified Development] kurtn:
The twrp app can flash any recovery when given root acces. How do yoy know the developer option doesn't enable recovery update?
[Samsung Galaxy S 4 Unified Development] rjt2291:
Does camera save to SD work properly for anyone? Mine has never worked right on this build but instead of saving it to SD card/DCIM or SD card/Pictures, every picture saves to 'SD card/Android/data/org.lineageos.snap/files'. They also don't show up in Gallery so I have to go find them. I'm using SGH-M919.
[Samsung Galaxy S 4 Unified Development] xperanto:
This is due to the "Scoped storage", introduced in Android 10, already discussed with some workarounds here:

https://xdaforums.com/showpost.php?p=82992685&postcount=437

[MENTION=8031265]kurtn[/MENTION]

For Twrp i know, but i`m using LOS-recovery for now and since the sourcecode of it is updated quiet often (not on every ROM-update, but "heavyly" under construction) it would be nice to be able to update LOS-recovery independly without hooking it up to a Comp.

Maybe i got it wrong. For my understanding or i "assume" that the LOS-update-App (which i find quiet usefull in the meantime) should download and update the LOS-recovery, too if it is enabled in the developer options. But it doesn`t, nor it is updated in any other way and no way to update *.img within itself.

Maybe i should have asked: What does or should the option to update recovery in developer options do? because for me it doesn`t do anything or did i miss anything?

The installed LOS-recovery version is shown on the "welcome-screen" when booting into it.
[Samsung Galaxy S 4 Unified Development] droi1:
you can also use Google Files App, at least it is a fast and easy way to move Pictures & Videos to SD Card https://support.google.com/files/answer/9712028?hl=en
[Samsung Galaxy S 4 Unified Development] curiousde2002:
Anybody can help?
[Samsung Galaxy S 4 Unified Development] arco68:
1. It should be permanent by design, so I don't know why that's happening for you. I haven't seen it here.

2. Google removed support for wifi display since Android 9. If you have a Chromecast and the Home app installed, you can use that to cast.

3. I don't have the equipment to test and try to fix it.
[Samsung Galaxy S 4 Unified Development] ze7zez:
Miracast on android 9/10/11

Can and should Miracast eventually work on android 9/10/11 or not?

I ask out of sheer curiosity.

Could you refer to the following information as a person with extensive experience with source code?

1. I can confirm that Miracast works in 3 custom ROM with android 9 for OnePlus One (bacon).

2. The BuzLightSabre user confirms the correct operation of Miracast in official LineageOS 17.1 on Xiaomi Pocophone F1 (beryllium).

3. Google in documents

https://source.android.com/compatibility/11/android-11-cdd

https://source.android.com/compatibility/10/android-10-cdd

https://source.android.com/compatibility/9/android-9-cdd

describes:

5.8. Secure Media
If device implementations support secure video output and are capable of supporting secure surfaces, they:

[C-1-1] MUST declare support for Display.FLAG_SECURE .
If device implementations declare support for Display.FLAG_SECURE and support wireless display protocol, they:

[C-2-1] MUST secure the link with a cryptographically strong mechanism such as HDCP 2.x or higher for the displays connected through wireless protocols such as Miracast.
If device implementations declare support for Display.FLAG_SECURE and support wired external display, they:

[C-3-1] MUST support HDCP 1.2 or higher for all external displays connected via a user-accessible wired port.

.
[Samsung Galaxy S 4 Unified Development] xperanto:
At least to

To my knowledge, MHL (usb to hdmi) is disabled permanently, when "knox warranty void" is triggered, i.e. by flashing and booting a custom kernel. You can check "knox warranty void" by booting into bootloader-mode. If it says "knox warranty void: 0x1" in the left upper corner, it was already triggered.

Since i got my s4 used, and it was already triggered, i can`t tell you if the it is triggered also by LOS, but i guess it is.

Edit:

Forgot to say, of course mhl doesn`t work on my device with knox void. I tried mhl even with the stock rom when i got my phone with knox already triggered.

Further reading here https://xdaforums.com/showthread.php?t=2764954

Despite the explenations of "punishing" users in that post, my personal guess is that they disabled MHL with custom kernels/roms to prevent screenrecordings/grabbing of DRM-protected content via hdmi.
[Samsung Galaxy S 4 Unified Development] arco68:
Miracast works in Lineage 16.0 (Android 9), since we brought back what Google removed to support it.

In Lineage 17.1 (Android 10) it was not brought back, so Miracast won't work there.

And I'm talking about WFD (WiFi Display), and not MHL.
[Samsung Galaxy S 4 Unified Development] arco68:
Can someone with the Sprint variant test this build and see if SIM card is reckognized?

http://www.mediafire.com/file/bur9cmxdpojb2ix/file
[Samsung Galaxy S 4 Unified Development] ze7zez:
Then, shouldn't we believe that BuzLightSabre casts the screen in Android 17.1 using Miracast (of course through WFD, because everything else is not Miracast)?

edit.

He uses a Panasonic DVR, which is a certified device.
[Samsung Galaxy S 4 Unified Development] Max Frost:
Testing , Will let you know soon.
[Samsung Galaxy S 4 Unified Development] philsilvers:
Hi all, here is a link for lineage-17.1-20200924-nightly-jfltexx.tar.md5

https://drive.google.com/file/d/1nReUJBHthDsjwFqwyyXmH86keaZ-uzau/view?usp=sharing

This is my personal Odin version and comes preloaded with OpenGapps - Pico.

I hope it will help a few people.

This is ONLY for the I9505 model

Install ONLY coming from Stock

Use Odin v3.13.3

When flash finished and boot logo shows -

Remove & replace battery, then -

You will need to go to recovery and Factory Reset.

Good luck.
[Samsung Galaxy S 4 Unified Development] Paddy's:
Whatsapp call, speakerphone problem

Hi , this rom is great but i noticed that during a call using whatsapp or google duo,even if i activate the speakerphone , the audio only comes out from the little call speaker on top .

If i insert a jack 3.5 mm during a whatsapp call ,the audio automatically switches to the main loudspeaker on the bottom .I have to go to audio settings and change the speaker setting to hear the audio from the earphones using the 3.5 jack .

Speakerphone works only during a call using Facebook messenger lite , but there is an annoying echo .

Is it possible to fix these problems ?

Thank you for your support with this great rom .
[Samsung Galaxy S 4 Unified Development] arco68:
Thanks for your thorough testing. Indeed, this is very strange, and I don't have any reasonable explanation for it.

If you do an upgrade from 16.0 to 17.1 without wiping, does it work then and survives a reboot?
[Samsung Galaxy S 4 Unified Development] Max Frost:
No sir , not at all. When you flash 17.1 over .16 and reboot there is no sim card present. If you breeze back over my post I tried it a couple of times . Interestingly prior to the merge of the fix a couple of months back that stopped the reboot to recovery problem you could dirty flash 17.1 over 16 and simcard was present with working telephony retained even when updating to a new build . So looking back before the fix I'm confirming you could dirty flash 17 on 16 , have sim card , data and telephony permanently , surviving reboots , updates etc . First build after the merge of that fix I'm confirming you could no longer flash 17 over 16 without loss of sim card and no telephony. I don't know whether CRD has a different tree or version of it , whether they are no getting part of the source from Lineage that's causing this issue or what. I even have a SprintLG device that's affected exactly as this Samsung S4 that is exactly duplicated with the CRD phenomena . LOS for that LG doesn't find the sim card but the CRD beta build for the LG does . This indicates to me it's a LOS problem associated with Sprint devices and not an individual maintainers build. 17.1 from the start on the devices was brought up with an error , bad commit or something. Something about an app was faulting causing those devices to fault out and rebooting to recovery. When they fixed it I don't think they fixed it right and that's why we lost the sim card. I'm not a developer , just a good tester but I firmly believe to solve this problem one would need to go back and look at what occurred going from a perfect working 16 to a broken 17 from the beginning . What caused that app fault. We know this can work now because we have perfect working CRD builds on both devices , the Sam and LG Sprint devices. Does CRD use a different app from the one that was causing the reboots. Honestly it looks to me like LOS just stopped whatever was causing the machine to reboot and the root cause of the fault is still disfunctional/faulting but not innitiating the reboot any longer The JDCTeam build of LOS Optimized also doesn't work. but the JDCTeam CRD build does. LOS Optimized shares the problem with LOS .
[Samsung Galaxy S 4 Unified Development] arco68:
CRD uses CAF as the base for their ROM, while Lineage uses AOSP. But CRD has also merged the same "fix" that Lineage has. They are implementing a lot of the same stuff and fixes that Lineage does, but their core base is different.

Here's another test build: http://www.mediafire.com/file/2jr1foldtc3vqkc/lineage-17.1-20201004-UNOFFICIAL-jfltespr.zip/file
[Samsung Galaxy S 4 Unified Development] Max Frost:
Yesssssss!

Houston, The Eagle Has Landed !! Yessssss Yes Yes !! Hallelujah !!! . Total success. I did several clean wipe test . Once after CRD , once after LOS 16 and a previous 17.1 official not working build . I then did a dirty flash over an LOS 17.1 non working build and it worked fine too .

The results were sim card detected , telephony and data working perfectly. Reboots , flashes , dirty flashes all good. I declare this rom is fixed and ready to go :) . You must tell me what you found that fixed it hehe :) .
[Samsung Galaxy S 4 Unified Development] arco68:
Wow! Good news indeed! :)

Actually, there's several things I added/changed that I thought would help fix it. Now I have to narrow it down and find the exact thing that fixes it. So I'll be making some more test builds until it's found.

Thanks for the feedback. :)
[Samsung Galaxy S 4 Unified Development] arco68:
Here's next test build for Sprint variant.

http://www.mediafire.com/file/tbpwg6rg15xivmf/lineage-17.1-20201005-UNOFFICIAL-jfltespr.zip/file
[Samsung Galaxy S 4 Unified Development] Eguy:
I'm excited for the Sprint variant to get back on official status. I am still running the build from 4/22 since it was the last usable version for me before the pink screen flickering that appears to have been fixed. It does have the major lag issues that have also apparently been fixed. Thanks for the hard work, arco68!
[Samsung Galaxy S 4 Unified Development] Max Frost:
With this build we did lose the simcard . No telephony or data .
[Samsung Galaxy S 4 Unified Development] arco68:
Ok, next test build.

http://www.mediafire.com/file/1nml9w4fr8x28ai/lineage-17.1-20201006-UNOFFICIAL-jfltespr.zip/file
[Samsung Galaxy S 4 Unified Development] Max Frost:
This build works . Sim card present , tested phone call and LTE data . Confirmed working good .Heading to bed but if you need anything else tested I'll get on it first thing in the morning . Thank you for your efforts..
[Samsung Galaxy S 4 Unified Development] arco68:
Next test build: http://www.mediafire.com/file/jwi1adjm22gd0c8/lineage-17.1-20201006-UNOFFICIAL-jfltespr.zip/file
[Samsung Galaxy S 4 Unified Development] Max Frost:
Sorry for the late response [MENTION=3044346]arco68[/MENTION] . This build is also working . I'm only making a call , checking data , browsing and speed test. . No gapps installed. If there is anything else you want me to look at let me know. Anyway still good.
[Samsung Galaxy S 4 Unified Development] arco68:
That's great! Almost have it figured out now what fix is needed. Just need one or two more test builds to confirm.

http://www.mediafire.com/file/58w8wzkg9w1s0r8/lineage-17.1-20201007-UNOFFICIAL-jfltespr.zip/file
[Samsung Galaxy S 4 Unified Development] Max Frost:
Good morning . With this build we lost sim card . No Tele/Data . Ready to test the next one :)
[Samsung Galaxy S 4 Unified Development] Max Frost:
Just so you know ,tomorrow I'm having an operation to remove part of a lung. I doubt I'll be functional for testing a build after tonight and early in the morning until Friday maybe. I can test through tonight and early in the morning. I just didn't want you to think I wasn't paying attention tomorrow if you put a test build out and I don't respond. I'll be in the hospital a few days and bringing my phones with me. That's the reason I've been jumping on these builds and testing as quick as I can , to help us get this device ready to get back on the LOS build que . Thanks
[Samsung Galaxy S 4 Unified Development] arco68:
Interesting. It's not the thing I thought would fix it then. Lets try the other thing then. Has to be it.

Will fire up a build as soon as I can.
[Samsung Galaxy S 4 Unified Development] arco68:
No worries man. Health comes first. I'll try to put up a build within the next 4-5 hours. If you're not able to get at it, then no problem.

Good luck with the operation.
[Samsung Galaxy S 4 Unified Development] arco68:
Hopefully this is it.

http://www.mediafire.com/file/oqnudfom6fr34ks/lineage-17.1-20201007-UNOFFICIAL-jfltespr.zip/file
[Samsung Galaxy S 4 Unified Development] Ph3ar.:
Get well bro
[Samsung Galaxy S 4 Unified Development] Max Frost:
Thanks for your well wishes . Now here's the results. The sim card is working again with tele and data .

I also went back to the previous build to be positively sure I hadn't made an error . I clean wiped and flashed again with the same results , not working .As far as testing right now I'd rather do this than watch tv and Im just killing time until tomorrow so I can test builds tonight and in the morning , I enjoy this so no worries.Thanks
[Samsung Galaxy S 4 Unified Development] arco68:
Thanks for your help with testing. That was it, and testing can end now, and support for official builds can be restored. Expect it back in a few days. For those interested, this is the fix: https://review.lineageos.org/c/LineageOS/android_frameworks_opt_telephony/+/261168

Thanks again and good luck tomorrow.
[Samsung Galaxy S 4 Unified Development] Eguy:
Great to hear, I'll download it as soon as it is published to LOS Updater! Many thanks.
[Samsung Galaxy S 4 Unified Development] Max Frost:
Awesome . I'll be looking forward to it. Thanks for your patience and perserverence .
[Samsung Galaxy S 4 Unified Development] Eguy:
I flashed the official nightly today and it fixed almost all my problems. The phone works so much better than it was on the April build. I am still getting random black screens where I have to hit the power button and turn it back on to restore the screen and also I had the phone reboot on me while using Firefox. Other than those issues, all the lag is fixed, wifi/BT issues appear to be gone, and no flashing pink screen!
[Samsung Galaxy S 4 Unified Development] DrFlaisch:
Hi and thank you for maintaining this old device!

I'm using a GT-I9515 (jfvelte) as a spare phone, while my daily LG G3 is waiting for its "new" used mainboard from China but that's a story for itsself... Anyway, I noticed that data is not working on October 10th build of LOS 17.1. That's kind of frustrating and I'm wondering, if there is a way to work around it or another build to install to get data to work properly. Since I noticed, the Sprint variant seems to have similar issues too, I would really appreciate some hint.

Enjoy the weekend!
[Samsung Galaxy S 4 Unified Development] Max Frost:
[MENTION=3044346]arco68[/MENTION] [MENTION=2687630]Eguy[/MENTION] , I know exactly what you mean about the black screen . I'm home from the hospital recovering now and plan on trying get that logged somehow. It's very random and it sort of seems like some random crash where the phone just goes black for about 15 to 20 seconds and then recovers. The question is [MENTION=2687630]Eguy[/MENTION] , is this a new problem or was it also doing it on the April build you've been running ? The answer is very important so we can determine the timeline of when this issue popped up. It might be a kernal crash but it acts just like a UI restart as well. The thing is when it recovers everything is still intact , example being , I was in the middle of typing a text and when the phone recovered I opened Messenger and the text I was typing is still there and not lost. It's so random I'm not quite sure how to log it. Maybe there is some crash or kernal log somewhere that records it [MENTION=3044346]arco68[/MENTION] ?

So far everything else is doing great , good response , no FC's . I had half of my right lung removed removed a week ago due to lung cancer so I haven't really been able to test. yet but I am ready to do whatever you need to solve it arco. Thanks