yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 4 Unified Development] Ph3ar.:
Great work man . I believe this problem is with Lineage itself because I can testify the same exact problem is occurring with the sprint variant of the LG G3 . There is some common denominator from a common source for these devices and not isolated to a single specific device . I think a developer will need to identify the telephony issue and then submit a fix to Lineage for review or pass it on to whoever is in charge of fixing the lineage source for this issue which should fix the S4 , the LG G3 and who knows what other sprint device being affected with this bug. Hopefully [MENTION=5848265]npjohnson[/MENTION] will see your post and log and look into it .
[Samsung Galaxy S 4 Unified Development] electronspin:
sorry to quote to myself. It is only to complete the story:

Today I updated the LOS17.1 by OTA and after downloading and shutdown the mobile restarted into TWRP (323-0) and automatically did the flash of the updated release. Then automatically rebooted and now it works.
[Samsung Galaxy S 4 Unified Development] PurpleRain254:
I have a quick question....if anyone can answer it's alright...I've been experiencing some lag in the nightly builds...like I'd open an app an the screen just freezes...I'm using S4 i337m
[Samsung Galaxy S 4 Unified Development] electronspin:
Unfortunately after a good begin with this rom I am experiencing the same as you do. Some undesired lags sometime are happening. After some delay (1min) everything works again without any necessity to reboot. I am using galaxy s4 jfltexx. I hope someone can help to solve this issue.
[Samsung Galaxy S 4 Unified Development] PurpleRain254:
i wonder if its the jfltexx models being affected only
[Samsung Galaxy S 4 Unified Development] bschmidy10:
deleted
[Samsung Galaxy S 4 Unified Development] Hummtaro:
I experience the same thing on my jfltexx with both optimized and official lineageos.

But yesterday I removed my SD card and haven't had such a lag since then. Maybe it was just a coincidence. I'll probably see it tomorrow.
[Samsung Galaxy S 4 Unified Development] electronspin:
Actually I am using the SD card just as rom, indeed the SD now cannot be formatted at all due to FAT issue.

When I experienced the bootloop inLOS16 I found the SD card as the most probable culprit. Then when I flashed LOS17.1 I removed the SD card. Now I am using it again as a rom becouse I have a uge music library there, but I will follow your suggestion to remove it and see if the undesired freezes disappear. I will inform you in the next days.
[Samsung Galaxy S 4 Unified Development] Ph3ar.:
Here's a log I've taken to add to the info on what might be happening with this variant in case anyone wants to look it over. Towards the bottom is where the telephony and phone app start failing fatally. https://pastebin.com/T0sBzPyx . I can take logs but not much on understanding them .
[Samsung Galaxy S 4 Unified Development] Hummtaro:
Although it seemed to happen less often without sd, I still had a few lags. Then i reverted back to Los16 to rule out a hardware failure and i can say it runs much smoother and completely lagfree.. So something must be wrong with Los17 on jfltexx..
[Samsung Galaxy S 4 Unified Development] PurpleRain254:
agreed maybe future updates will fix it
[Samsung Galaxy S 4 Unified Development] electronspin:
I think the same as you do.

Nevertheless at beginning before install any app the official los 17.1 seemed very good, but now is presenting lags that i do not understand. now i installed the same apps that I had on los16. So i am thinking to come back to los 16 or try optimizedlos17 just to evaluate any difference.
[Samsung Galaxy S 4 Unified Development] Hummtaro:
At least for me Los17 and OptLos17 were the same..

To me it feels like a behavior that I know from broken computer hard drives, CD-ROM drives and floppy disks. The entire system freezes while waiting for a response from the drive.

Maybe it could be similar on Los17 but because of a bug rather than broken hardware..
[Samsung Galaxy S 4 Unified Development] electronspin:
I was supposing due to my external SD card that was broken but now I have a new one and nothing changed, so the lags do not depend on hardware (supposing no issue on mobo)..

It should be due to a software bug. Indeed I have a logcat full of errors but I do not understand why.

I did a full wipe before flashing LOS17.1 and picogaps and magisk then I used apps all coming from playstore, but I did not use the LOS recovery to flash LOS17.1. So I would like to test if optLOS17.1 (flashable through TWRP) will do the same, hoping not of course. Otherwise sadly I will come back to LOS16 or LOS14 that is still working on another S4 (with broken CDMA chip) that I m using just as remote wifi camera.
[Samsung Galaxy S 4 Unified Development] vip5912:
Last Builds for jfltexx Date 2020-04-23 ???

https://download.lineageos.org/jfltexx

nightly	17.1 lineage-17.1-20200423-nightly-jfltexx-signed.zip 2020-04-23

I have installed Image Date 2020-04-29.
[Samsung Galaxy S 4 Unified Development] PioneerSeeker:
infact i was trying to help the developer that galaxy s4 is too old with less ram and 2600 mah battery for these kind of wonderful and amazing and excellent latest roms. i just was trying to explain that they should optimize a little bit their excellent build for that old and childish phone... because lineage pie runs smooth and fine than this beautiful 17.1

i apologize if you are offended btw
[Samsung Galaxy S 4 Unified Development] twilightened:
Hi everybody. My mom is currently using an i9505 with the official Lineage 16. Is Lineage 17 an essential update? Is there any positive impact on battery life? In Lineage 16, i can not activate gps for example. Does Lineage 17 fix that?

Thanks for the replies.
[Samsung Galaxy S 4 Unified Development] kurtn:
You can activate GPS. You need much time and good sight. 17.1 doesn't make it better. Buy your mom a s5.
[Samsung Galaxy S 4 Unified Development] vip5912:
I used LOS 17.1 one month. Now I have no problems with it. Battery is OK for me (I charge phone once a day). GPS is working well (several seconds for fix position).
[Samsung Galaxy S 4 Unified Development] @kel@:
Someone tried to make a backup via TWRP and then restore the system?Through TWRP 3.3.1-1 is not restored, and how to win lineage-17.1-recovery I do not know.
[Samsung Galaxy S 4 Unified Development] kurtn:
You need twrp and this: https://xdaforums.com/galaxy-s4-min...-lineageos-17-1-s4-mini-t4045147/post82015861
[Samsung Galaxy S 4 Unified Development] @kel@:
You can write a little more, I use Google translator and it's not always clear? Here I installed lineage-17.1, make a backup via TWRP,and it does not recover, What to do?
[Samsung Galaxy S 4 Unified Development] kurtn:
Go to twrp. Restore your data and system 17.1 backup. Flash arco's ZIP file. Boot into system.
[Samsung Galaxy S 4 Unified Development] @kel@:
So the backup is not restored, it reaches the loading animation and keeps spinning and spinning.
[Samsung Galaxy S 4 Unified Development] testerS4:
I think I would have experienced that before. After restore, try installing the last LOS 17.1 version without deleting anything.

(sorry for Engl ... I use translators)

__________________________________________________ ____________

Device: I9515 (Jfvelte)

TWRP 3.3.1.0

Baseband I9515XXU1BPK3

Kernel 3.4.112
[Samsung Galaxy S 4 Unified Development] electronspin:
I do not know why but actually I cannot update the LOS17.1 directly from the update menu. It tells me that faild to connect to the server and ask me to check the internet connection, but the wifi perfectly works and internet is available on the browser for any search.

what can i do?
[Samsung Galaxy S 4 Unified Development] kurtn:
Wait! Download server is down.
[Samsung Galaxy S 4 Unified Development] ram365:
No more builds?
[Samsung Galaxy S 4 Unified Development] xperanto:
LineageOS servers hacked

As stated on their twitter-account https://twitter.com/LineageAndroid/status/1256821056100163584, LineageOS-servers were hacked on may 2nd.

On https://status.lineageos.org/ you can check wether or when and which part of the infrastructure is back and online.

Older builds are not affected and downloadable.

So please be patient and stay tuned, until the buildservers are re-set up checked. Safty first ;).
[Samsung Galaxy S 4 Unified Development] joam280:
Pin code access does not work and mobile data does not work either. I hope to help

Enviado desde mi Nexus 9 mediante Tapatalk
[Samsung Galaxy S 4 Unified Development] flamadiddle:
jfltevzw mdk issues

Does anyone know if the LineageOS recovery for jfltevzw is loki'ed?

https://download.lineageos.org/jfltevzw

I have the Verizon GS4 with MDK bootloader and a loki'ed TWRP 3.3.1-1, but I can't run this ROM with it. Every time I install it (after wiping/formatting data), I receive the "System Software Not Authorized" error.

I'm able to go back to recovery and flash LOS 16.0 and all is well, but I'd really like to upgrade to 17.1. So I'm thinking maybe 17.1 can't work with TWRP on jfltevzw and I need the LOS Recovery. Hence my question. Thank you for any help.
[Samsung Galaxy S 4 Unified Development] testerS4:
The S4 Verizon is if I am not mistaken the i9515 or jfvelte? I have the same. However, I use TWRP 3.3.1.0. What is the error there? I have no difficulties with all 17.1 offered so far.

(sorry for Engl ... I use translators)

__________________________________________________ ____________

Device: I9515 (Jfvelte)

TWRP 3.3.1.0

Baseband I9515XXU1BPK3

Kernel 3.4.112
[Samsung Galaxy S 4 Unified Development] flamadiddle:
No, the S4 Verizon is the SCH-I545 / jfltevzw. This is the LineageOS Device page for it: https://wiki.lineageos.org/devices/jfltevzw

This Galaxy S4 requires the Loki hack for recoveries since the bootloader is locked.

The error I receive after a clean install of LOS 17.1 is:

I am unable to boot into the system with this error message. I can only get to Download or Recovery modes. From there, I can do a clean install of 16.0, and everything works fine. But I want to get 17.1 working. So that's why I'm asking if the LOS recovery is Loki'ed.
[Samsung Galaxy S 4 Unified Development] pedramtt:
my experience about the best settings for not heating up :

resolution 960*540

dpi 240

lower dpi than 240 the phone dialer doesnt work . everything else works

Gpu 200 on demand

Cpu all core running at the same time. low: 386 high: 918 interacive is faster than ondemand . but I dont remeber why I choosed Ondemand at the end

and you can for example play Alien Shooter for as long as u want with a cpu degree between 48 to 50

or surfing the web ... etc ... with long battery life

otherwise with default setting with extreme battery saving after 15 min the cpu goes to 57 and up to 68

Its from day one corona came I have tested all the possible Cpu settings, and thats the best settings

and ofcourse lower the DPI to 160 for example has cooler cpu for a longer time

please becarufull when entering the numbers of dpi and resolution
[Samsung Galaxy S 4 Unified Development] vip5912:
The LOS 17.1 freezes every day. The only solution is reboot.
[Samsung Galaxy S 4 Unified Development] kurtn:
The last release thing is in common for all onfficial devices. Development hasn't stopped

https://www.reddit.com/r/LineageOS/comments/gfudkv/comment/fpvrfpe
[Samsung Galaxy S 4 Unified Development] vip5912:
Thanks for status.
[Samsung Galaxy S 4 Unified Development] EliezerB:
Which version can I load onto I337UCUGOC4 ?
[Samsung Galaxy S 4 Unified Development] npjohnson:
None, your bootloader is permanently locked.
[Samsung Galaxy S 4 Unified Development] EliezerB:
Am I able to load any "modern" version of Android with ADB or otherwise - or is this device truly permanently stuck on 5.0.1?
[Samsung Galaxy S 4 Unified Development] npjohnson:
You are stuck with 5.0.1 ROMs, specifically TouchWiz based.
[Samsung Galaxy S 4 Unified Development] rollmeister:
I installed 17.1 on the S4 Active (GT-I9295) using current TRWP along with Gapps pico and Magisk. Previous LOS 16.0 install used F2FS on System & Cache partitions but LOS 17.1 ended up failed boot with boot animation repeating, so F2FS is not supported on LOS 17.1. Personally, I rather use LOS 15.1 if the camera and bluetooth were stable. Testing bluetooth while using google maps navigation tomorrow, if no issues with BT won't report anything here.

Battery over one hour did not go down 1%. That is wihout sim card or wifi.
[Samsung Galaxy S 4 Unified Development] exvanderlord:
The site still appears to look dead:

https://download.lineageos.org/jactivelte

And there are also still no updates since 2020-04-22, just fixes for the next build:

https://www.lineageoslog.com/17.1/jactivelte

Would it all ever be back again?

And how are things with development now?

Wishing developers to be strong and all regards!
[Samsung Galaxy S 4 Unified Development] kurtn:
There are posts on lineageOS reddit channel

Today a test build started

https://buildkite.com/lineageos/android
[Samsung Galaxy S 4 Unified Development] Exodusnick:
Sonntag, 03.05.2020 16:48 Uhr

https://winfuture.de/news,115639.html ( German )

Security breach: Hackers could access LineageOS servers

Picture source: Public Domain

A security hole in a framework has allowed attackers to access the infrastructure of LineageOS. Although the hackers had access to the servers, no sensitive data was apparently stolen. The team is working on closing the vulnerabilities.

LineageOS is a mobile operating system based on Android, which was then known as CyanogenMod. As ZDNet reports, last night unknown hackers managed to penetrate the infrastructure of LineageOS. However, the attack was discovered before any damage could be done.

Sensitive data was not stolen

According to the LineageOS team, no sensitive data was stolen. Keys used to sign official versions are stored on other systems.

The attackers have exploited a vulnerability in the open source framework Salt. The software is used to manage servers in data centers or other internal networks. At the beginning of the week, two serious vulnerabilities that allow hackers to take over Salt servers were published. In some cases attackers have managed to install a backdoor.

Under normal circumstances, salt servers should be operated behind a firewall and should not allow requests from the Internet. However, this is not the case in many networks. A few days ago, patches were made available against the two security holes.

The LineageOS team reacted immediately to the attack and temporarily took all servers affected by the attack off the network. The developers are currently working on fixing the vulnerabilities so that such an attack cannot be carried out in the future. Who is behind the attack and what goals were pursued with it is still completely unclear at this time. Hacker, hack, code, programming, hacker attack, programming, HackingPublic Domain

Translated with www.DeepL.com/Translator (free version)

https://www.zdnet.com/article/hackers-breach-lineageos-servers-via-unpatched-vulnerability/

https://twitter.com/LineageAndroid/status/1256821056100163584
[Samsung Galaxy S 4 Unified Development] A.MushtaqAli:
Finally dark mode for default AOSP apps like dialer contacts and messaging
[Samsung Galaxy S 4 Unified Development] kurtn:
You talk about develoer option override force dark ?
[Samsung Galaxy S 4 Unified Development] A.MushtaqAli:
Changes on

Www.download.lineageos.org/jfltexx/changes
[Samsung Galaxy S 4 Unified Development] kurtn:
Good news. Old aosp apps get brushed up by lineageOS. Google has no love for open source. Makes proprietary apps.
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
... and maybe - if I pick it right - more good news:

the/a buildsystem is "flying" again:

https://buildkite.com/lineageos/android/builds?state=running
[Samsung Galaxy S 4 Unified Development] kurtn:
Experimental

https://ftp.fau.de/lineageos/exp/jactivelte/
[Samsung Galaxy S 4 Unified Development] curiousrom:
LineageOS Automated Builder Relaunched!

Good news some regular nightly builds 20200529 are available for download now!

For example:

HTC One: https://download.lineageos.org/m8

Galaxy A3 (2016): https://download.lineageos.org/a3xelte

LG G3 (T-Mobile): https://download.lineageos.org/d851

***
[Samsung Galaxy S 4 Unified Development] vip5912:
https://download.lineageos.org/jfltexx

lineage-17.1-20200529-nightly-jfltexx-signed.zip :good:
[Samsung Galaxy S 4 Unified Development] js-xda:
Did you test the build already by any chance? I downloaded it but decided to wait before applying it to upgrade from 16.0 to 17.1 as I can't download the SHA256 hash for verification so far. Seems to be a general issue with the new builds.
[Samsung Galaxy S 4 Unified Development] Houndcatcher:
Hi I have and it all seems fine except I have an issue with the Setup not completing and force closing currently. I've nopt had a chance to try to fix that yet...
[Samsung Galaxy S 4 Unified Development] vip5912:
No. I will try on weekend. :)
[Samsung Galaxy S 4 Unified Development] xperanto:
I did. here on my device, everything runs fine so far, but i did`t update the LOS-recovery yet.

Did you sideload the zip using ADB by any chance? If so, it should be the "famous 47% bug", which is not related to the rom itself.

Anyway, thank you all at LineageOS!
[Samsung Galaxy S 4 Unified Development] Houndcatcher:
Think I sideloaded the original zip but have updated ever since but this has only just appeared! Is there a fix?
[Samsung Galaxy S 4 Unified Development] vip5912:
FYI: LOS 17.1 update 29.05.2020

I did update by air: Setup - Update (only download new image), reboot to TWRP recovery, install from /data/data/lineage update (I have encrypted data and Magisk ).

All working fine.
[Samsung Galaxy S 4 Unified Development] xperanto:
No, there isn`t as far as i know. I ran into the same issue, seemingly being stuck at 47% when i sideloaded the firs LOS via adb, but remembered having the the same issue years ago with another device, so don`t be bothered.

The reason seems to be that default ADB Android/Google, when i remember correctly, sideloads the rom not just once, but "2.2 times" (cant remember which parts) for safety measures, hence the 47%, and LOS just sideloades "once" in one flush. So don`t be bothered, it is just "counting wrong" and if the commandline returns to twrp/los-recovery after 47% everything is fine.

I would appreciate it, if they update the LOS-intallation instruction accordingly, too.

If you still feel uncomfortable sideloading via adb, use the updater (never tried or used it) or just download the rom on your device and update it manually in recovery (as i prefer,because holding available the previous and actual zip on exfat and therefore "on the go" isn`t such a bad idea at all. just in case).
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
jfltexx, update by air.

all smooth.

- TWRP and no gapps, Magisk here -
[Samsung Galaxy S 4 Unified Development] js-xda:
Dirty flash of jfltexx 17.1 (20200529) over last 16.0 (20200325) via TWRP without GApps & Magisk. Initially massive battery drain (1 %/5 min) but stabilizing overnight (forecasted runtime 2 d; UPDATE: current forecast 1,5 d with remaining 50 % and same as actual for the past 50 %).
[Samsung Galaxy S 4 Unified Development] @kel@:
Please tell me how to make a backup copy of the system for further recovery? I can't restore it via TWRP.
[Samsung Galaxy S 4 Unified Development] kurtn:
https://xdaforums.com/galaxy-s4-min...-lineageos-17-1-s4-mini-t4045147/post82015861
[Samsung Galaxy S 4 Unified Development] @kel@:
It really works, thank you. :хорошо:
[Samsung Galaxy S 4 Unified Development] Savatage76:
hello, why stock music player doesn't show album under artist?

thanks
[Samsung Galaxy S 4 Unified Development] llluuuzzziii:
sometimes it will...

sometimes u tap at this album it shows tracks from another...

Merde! ;o)
[Samsung Galaxy S 4 Unified Development] Yasiel98:
Yes you can

Step 1 download the Program, 7-Zip File Manager

2nd step Download the recovery lineage-17.1-20200422-recovery-jfltexx.img Step

3 Rename lineage-17.1-20200422-recovery-jfltexx.img file to recovery.img

4th Step open 7-Zip File Manager and go to the address where recovery.img is, give a Clip in the File and go to the upper left corner add

You will get a window, look for Archive Format, select Tar and click Ok and a File will not be created. tar flash by Odin and Ready

I hope it has been a great help
[Samsung Galaxy S 4 Unified Development] kukele:
Problem seems to be fixed with the newest builds. I didnt have any freezes for a couple of days now
[Samsung Galaxy S 4 Unified Development] Hummtaro:
Same here! No freezes anymore! :)
[Samsung Galaxy S 4 Unified Development] Eguy:
I'm having a flickering pink screen and it makes the phone (jfltespr) unusable since the builds resumed. It was fine before May 30th.
[Samsung Galaxy S 4 Unified Development] xperanto:
GPS runs fine here, even with AGPS disabled (since https://review.lineageos.org/c/LineageOS/android_packages_apps_LineageParts/+/273326/you have to disable AGPS in carrier conf file and in gps.conf point suppl to localhost) and you will get a gps-position-fix within seconds.

But -fingers crossed- have a look, what will be re-implemented again in the next build:

gnss-legacy: Bring back GLONASS:

https://review.lineageos.org/c/LineageOS/android_hardware_lineage_interfaces/+/276315/

:)
[Samsung Galaxy S 4 Unified Development] kurtn:
Can you share your modified files, please?
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
what is your time for the first fix with your modified gps.conf and settings ?

less than 120 s ?

~ 120 s is my best value I can get for the first fix.

All/most subseq. fixes are < 60 s, though.
[Samsung Galaxy S 4 Unified Development] ticktockman123:
LOS 17.1

Hey all,

I have spent the last two months flashing, meditating and then flashing again to get my JFLTE Galaxy S4 to run Android 10.

I have finally gotten a JDCTeam optimized 16 to hold on for which i have a backup saved from the fresh install and another with apps/magisk on top so I can revert to them anytime., but no matter what I do LOS 17.1 flashes succesfully boots, then powers itself off a minute or two after the Home Screen appears (or setup screen depending if I had opted to flash gapps in).

I have discovered that if I leave the device connected via USB to the computer it will not power itself off. But sure enough once I unplug USB it powers itself off.

Has anyone has success with this? I have flashed this every way and 6 ways to Sunday and same result. Used JFLTExx then patched the updater script on JFLTEspr, LOS 17.1 every nightly build. V2-5 of Optimized LOS. I have used LOS recovery, JDCTeam recovery, TWRP recovery, I have adb sideloaded, dirty flashed, clean flashed you name it.

Same result everytime. System runs awesome until I unplug it from USB then it powers off.

I have read so many threads my mind is mushy. If anyone could throw me a rope or point me to a thread that shows how to resolve this I would be greatly appreciative.

I will also post this in the JDCTeam thread, hopefully thats not too redundant.
[Samsung Galaxy S 4 Unified Development] Ph3ar.:
Go to airplane mode and turn your wifi on. Then unplug USB . If I do that mine doesn't reboot but that's only because I've turned off telephony. The rom runs perfect in every way but until someone fixes the issue it's going to stay like this. I have logs and have offered to send them. Waiting to hear back from the OP . Apparently some internal service called rescue party reboots it to recovery on mine after some part of telephony fails 5 times it triggers a reboot to recovery. Is your's only rebooting to the system or to recovery? BTW I don't have to edit the build prop with the airplane mode work around. Also having the device plugged into a pc disables rescue party and I suspect airplane modes does as well.

---------- Post added at 04:47 PM ---------- Previous post was at 04:41 PM ----------

I don't have the pink screen . Is your phone provisioned and telephony working ? If so you may be the only person in the world with a jfltespr on 17.1 that is or was working fine . Can you tell us a little more about it ? Thanks