yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 4 Unified Development] 2013Paco:
Tried a dirty install coming from lineage-16.0-20200325-nightly-jfvelte-signed.zip. That's what I did:

* Boot in TWRP recovery 3.3.1.0

* NO WIPE at all !!!

* Install lineage-17.1-20200404-nightly-jfvelte-signed.zip

* Install open_gapps-arm-10.0-nano-20200401.zip

* AGAIN NO WIPE !!!

* Boot into System - that's all

> all accounts from LOS 16 remain in LOS 17 (Email, Threema, Telegram, WLAN, Google are still alive! No need to activated again)

> all apps are present, no need to install them again

> first start of each app seems to me a little bit longer than before; but after opening them more times seems to me that they start quicker than first time

> touch screen sensitivity seems to be a little bit poorer than in LOS 16; have to tap often more than 1 times to get a reaction

** So for me: Quickest Upgrade ever! Great work and thanx to developpers! ***

Will try next OTA-Update, hope that this will install without problems. If not, I will report
[Samsung Galaxy S 4 Unified Development] Ph3ar.:
JFLTESPR Report- SPH-L720

Wow . This has got to be the easiest successful uprgrade ever . I dirty flashed 17.1 over 16.1 and OpenGapps pico gapps over version 16 gapps . I honestly didn't expect it to work but lo and behold it flashed fine , booted up perfectly and not the first FC so far . I tested about 25 apps and all worked . I then booted back to recovery and flashed Magisk 20.1 to regain root and that worked perfectly as well . This particular phone is not presently with a carrier so I can't check data or telephony . I didn't even wipe dalvik cache or system cache. Haven't had the first hiccup. My entire setup is intact . I had planned to clean wipe the phone but before I did I wanted to make sure my twrp recovery would be able to flash the zip and it did . I then took it a step further and flashed 17.1 gapps over the old gapps . I'm trying to detail this experience for other Sprint S4 users .Great job [MENTION=4710311]Mr. Johnson[/MENTION] .Thanks for your efforts . I will flash the same way on my other activated sprint S4 , check telephony and update this post .
[Samsung Galaxy S 4 Unified Development] DerHimmel:
Hello everybody. I installed LineageOS 17.1 with ARM 10 nano Gapps, via TWRP 3.3.1.0. Installation was successful immediately and i9505 works without any bootloop. Unfortunately GPS as in previous versions does not work. I then encountered this bug: both with whatsapp and with Telegram when I receive a voice message when listening to it the S4 (i9505) freezes, black screen and only solution to remove the battery. Anyone have the usual bug? Thanks. Translated with Google translator I apologize for incorrect words and wrong sentences.
[Samsung Galaxy S 4 Unified Development] bersem:
[MENTION=5848265]npjohnson[/MENTION] possible to enable hardware keys when using gestures ? If yes then in next nightly ??

Thanks for your hard work !!

Regards !
[Samsung Galaxy S 4 Unified Development] kurtn:
Is your proximity sensor OK?
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
GPS on *my* 9505 works on LOS 16 and 17.1
[Samsung Galaxy S 4 Unified Development] kurtn:
But it needs good sight and long time for first fix. Or do you see a network location and misinterpreted it as GPS?
[Samsung Galaxy S 4 Unified Development] NewIdenty:
Dirty upgrade from LOS 16 on i9515 now worked with no issues, used build 2020 04 03 and gapps nano.

Root on Lineage 17 apparently only works if you install Magisk, so i did that as well.

I installed the zips with adb sideload from TWRP recovery.
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
yes, it lasts somewhat long for the first fix.

and no, I see *GPS* and interpreted it as *GPS* :cool:

P.S.

not every Berliner is a blind Berliner, as most Bavarian's love to misinterpret. :laugh:
[Samsung Galaxy S 4 Unified Development] qandres12:
Why is it that everytime i adb sideload the lineageOS zip and then try to install the gapps and magisk, I get that this "adb: sideload connection failed: no devices/emulators found."

Im trying to install 10.1. it seems im able to install the lineage zip but not gapps or anything else. Then when i try to boot up the rom its starts a bootloop after typing in the wifi credentials. It will eventually boot into recovery stating that i cant boot up the system because it may be corrupted. Then i Have to flash to stock. Ive rinsed and repeated this process with all 10.1 zips

Is it also possible to allow lineage recovery to update via the sd card? Thats the only way i was able to install LOS16?? It was challenge trying to install it the first time but cause none of the instructions worked on the wiki and twrp wouldnt allow the zips to flash.

Device is SPH-L720T
[Samsung Galaxy S 4 Unified Development] qandres12:
Alright so I finally able to install LOS17.1. It took a bit of sidework on my part just like when I installed LOS16 and the setup was working fine until it powered off again. Im gonna try to dirty flash from 16 to 17.1 since clean installs didnt work. But it appears that LOS17. for the SPH-L720T are still bugged.

Edit: even dirty flashing didnt work. Still gives me the system may be corrupted message in recovery. Guess I'm stuck on 16 until its fixed.
[Samsung Galaxy S 4 Unified Development] mzahs:
Does this rom have root?
[Samsung Galaxy S 4 Unified Development] qandres12:
No you have root using your preferred method. There have a zip for it on their site or you can flash magisk or whichever othet method you'd like.
[Samsung Galaxy S 4 Unified Development] kurtn:
There is no lineageOS addonsu for 17.1
[Samsung Galaxy S 4 Unified Development] A.MushtaqAli:
screen blink pink and after that screen goes black. i have lock and unlocked my phone to bring screen back.
[Samsung Galaxy S 4 Unified Development] js-xda:
Odd enough, issue disappeared without any action but leaving it powered off for 10 days in the drawer due to lack of time to look further into it. Latest build installed only afterwards - downloaded via WiFi ...
[Samsung Galaxy S 4 Unified Development] moreorless:
deleted
[Samsung Galaxy S 4 Unified Development] js-xda:
I haven't observed the mentioned issues so far. I tried the procedure described by @moreorless both on S4 (GT-I9505) and S4 active (GT-I9295) with latest build (210121), no GAPPS, no Magisk or alike and no PIN/lock pattern (test devices) and could not reproduce. Which build are you using and which model? That could help the developers to narrow down.
[Samsung Galaxy S 4 Unified Development] 2013Paco:
Approx. since Xmas 2020 every updated version results occasionally in these two faults:

* Wifi watchdog triggered -> needs to restart

* SIM card not found -> needs to restart, too

My device is i9515 VE. Did everyone has same issues? Is there a workaround?

Thanx for help!!
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
to be checked !

give a dedicated task for a CPU to do.

1. with an CPU with limited frequency it needs longer to complete the task, that maybe means a longer time juice [at a low(er) level] is sucked.

2. with an CPU which is able to run at max. frequency the same task is completed in a shorter time, that maybe means lesser juice [at a high(er) level] is sucked.

which case really saves the most power ???
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
care to load that error log's up :cool:

serious:

well, I was arguing with two extreme points to make it clear.

the question remains: what's more costly ?

a short run with high frequency versus a long run with low frequency both for an identical task.

And of course thinks all the points between both extremes.

btw I was mention the sense of an statement made moons ago by an kernel developer who is working at power polices of Intel CPU's. IIRIR (not sure) it was about turbo modes of Intel CPU and the whole (!) costs not power consumption only.

anyway, I guess that thoughts and measurements were the starting point to invent the power profiles "Efficiency" and "Balanced"

to sum up and regarding your statement in #587 "low" means neither "snappy" and nor necessarily "powersaving".

that's my point.
[Samsung Galaxy S 4 Unified Development] therob2:
I also have random reboots once-twice a day (but just reboots after some secons of laggy UI, but without pink).

Are there any suggestions which settings should be checked/set for a workaround? Thus are there any SAFE settings to avoid/reduces random reboots or is it until now completely unclear by what it is triggered?

1) Above I read e.g. about the performance profile - are there any other "safe settings" I could try to improve situation until any change in ROM itself could be applied once narrowed down successfully?

Thanks for any hints!

I have an S4 GT-I9505 with 20210114-nightly and without Gaaps - and I think things get worse with an update in December (but don't know if this is true and when exactly - it's more a a feeling). Mostly reboots seem connected with any keyboard/typing-actions, but also after pressing "back" or "power" button it occurs - I could not find any real pattern.

4 other devices around in the family (I9505 and I9515) are running without any reboots.

2) And maybe here anybody knows: could it work (although not recommended I know) to dirty-flash 17.1-optimized over 17.1-nightly without loosing data/apps/settings? Maybe reboot-things are imrpoved there this way?
[Samsung Galaxy S 4 Unified Development] therob2:
Thanks, will try.

I fully agree and normally also try helping to fix issues. But as this is the daily device of my mom and I have no physically access very often and she don't have the skills to help here much it is hard to make this here .... thas the sad situation....
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
maybe with an backup before ?

but be aware:

somewhere (here ?) I've read something about "restore doesn't not work (flawless)" if something goes wrong.

yup, I've changed my mind too.

But temporally the other way around, cause - for my taste - the maintainer is not very responsive (maybe to much involved with releasing 18.1 - don't know - ), so *I* temporally moved to unofficial 18.1 (clean flash), cause this ROM here became and stayed that long unusable.

my bug report is some sides back ... (comment #547)
[Samsung Galaxy S 4 Unified Development] porklodeon:
Is there kernel file that I could used with this ROM. My phone goes into kernel panic once in a while with this rom mine is I337M jfltexx
[Samsung Galaxy S 4 Unified Development] rjt2291:
Surprisingly my SGH-M919 still works just fine on T-mobile despite their IMEI checker.:)
[Samsung Galaxy S 4 Unified Development] xperanto:
Could someone please tell me if he is capable of making VoLTE calls with jftexx?

...and tell me, if there is a switch in the networksettings?

To invoke networksettings simply dial

*#*#4636#*#*

in your dialpad.

Some carriers in my country think it`s a good idea, that every customer should ask for VoLTE individually, even if it is for free (depending on dataplan), so i can`t tell,if this is ROM-related or if the carrier didn`t activate it yet...
[Samsung Galaxy S 4 Unified Development] kurtn:
There is no VoLTE for any Samsung phone in lineageOS.
[Samsung Galaxy S 4 Unified Development] vip5912:
I had reboots regularly, almost every day: blocking, horizontal lines and rebooting.

I did the "correct" dirty update:

1. Make a full nandroid backup, just in case something goes wrong. You can use TWRP to do that. (TWRP > Backup > Select everything) [Optional]
2. Remove Magisk root with Magisk Uninstaller. (TWRP > Flash the uninstaller)
3. Reboot to TWRP and Wipe Dalvik / ART Cache, System and Cache.
4. Flash the ROM > GApps > Magisk Root Solution.
5. Reboot and Enjoy!

See:

https://xdaforums.com/t/s4-unified-collection-guides.4224933/

Now I have 3 days without rebooting.

lineage 17.1 20210204
opengapps arm 10.0 pico 20210205
Magisk 21407 (canary)
[Samsung Galaxy S 4 Unified Development] dick_vigarista:
HI, can anyone confirm if this ROM works with MHL adapters? I bought one and its not working. Just wanna know if it is the ROM or my adapter. Thx
[Samsung Galaxy S 4 Unified Development] Ph3ar.:
While I can say the JFLTESPR pretty much works perfectly it does have one serious issue . There is a direct fault between data and location . In other words LTE mobile data is fine until you turn on location and use an app such as google maps. As soon as you do it knocks out LTE so then you can't use maps for directions as you have no data. Turn off location and data instantly works again. If someone such as @npjohnson or @arco68 is willing to take a look I'll log it for you. I think the issue goes back to a few months ago when the reboot problem and data was fixed a commit that fixed it or one that was taken out . It's been like this ever since that fix was applied . It's not a new problem .Location and data have a direct conflict . It's not just maps but any app that accesses location. Thanks
[Samsung Galaxy S 4 Unified Development] xperanto:
I`m so sorry that I asked. Now that I have read more about the issue... bah who the **** implements such feature with multiple apis/confs and not just with a simple config.

And Samsung even implemented it proprietary...

Is there any way to check if arm-wb (dynamic from 6 to to 24kbps) is used for calls at least? I don`t mind that while calling it switches to a lower (e.g. gsm) band, but calling others sounds like "a call from the 80ties".
[Samsung Galaxy S 4 Unified Development] js-xda:
Samsung Galaxy S4 Active (jactivelte (GT-I9295)) "Recovery is not seandroid enforcing"

No actual question - rather for documentation if someone else runs into the same issue. Using TWRP as default recovery for all devices, I had with both 3.4.0 and 3.5.0 the issue that the Samsung Galaxy S4 Active was stating "Recovery is not seandroid enforcing" upon boot to recovery. Common recommendation is to check whether the latest firmware incl. baseband etc. is installed - yes, it is. Observed impact was that it was not possible to use the automated OTA update installation but I had to export them via the updater GUI within LineageOS and install them manually using TWRP. Tested the LineageOS recovery today and this one runs without the error message. To be seen whether automated OTA update installation script works - will update post then.

Update 26.02.2021: OTA update installation functioning without issues as well. As a side aspect, I am realizing also the really nice design of the LineageOS recovery - less technical details visible during OTA update flashing and factory reset than with TWRP but more comforting for non-technical users.
[Samsung Galaxy S 4 Unified Development] simonegalfano:
hai riscontrato problemi con le app Google? Uso quelli di agosto da molti mesi perché non completa la configurazione dell'assistente Google (voice match), mi da l'errore "problemi di connessione, riprova"
[Samsung Galaxy S 4 Unified Development] Zisshan Zens:
So After using couple of lineage OS roms and some other custom roms, Always on Vpn and block Connection without vpn doesn't seem to work after some searching I found out that other lineage users have the same problem.

I have tried a few different apps that have similar kill switch functionality but same problem presists

I don't know if this has been mentioned before or is not significant enough but I felt like putting it here.
[Samsung Galaxy S 4 Unified Development] SamsungNZ:
got an s4 today is this the best rom out there
[Samsung Galaxy S 4 Unified Development] therob2:
Is there any thread where we can follow/support/test the LOS18.1 for the S4 (for me: i9515) or does it not exist yet?

Is there any rough guess when it could go live (weeks or months?) - if there is already some work going on? Cheers, Robert
[Samsung Galaxy S 4 Unified Development] kurtn:
S4 will be among the first batch oft devices when 18.1 is released. You can watch them work in review.lineageOS.org
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
I was long suffering on the same issues and switched therefore to Optimized LOS 18.1 and the issues were gone.

IFAIK, Optimized LOS 18.1 and (what will be) official LOS 18.1 are nearly the same, so I guess the issues are also away.
[Samsung Galaxy S 4 Unified Development] js-xda:
From own experience and running several S4 on LineageOS 17.1 with and without OpenGAPPS Pico, I can say it works for me. Whether it is the best, I can't judge.

Please don't get me wrong - I understand fully your frustration. But it seems also to be an issue limited to certain circumstances. I haven't experienced either - tried several of the pointed out options to reproduce and can't so far on I9505s. So, this lack of reproducibility might contribute to the situation?
[Samsung Galaxy S 4 Unified Development] js-xda:
Indeed good to look at the differences - which have been posted before:

Adding for the S4 (GT-I9505), baseband is I9505XXUHOJ2.

Main difference I see is Magisk and GApps (assuming that you have them installed if using GoogleMaps) besides slightly different region/country version of baseband and the - now - more recent kernel etc. - have you tried on your devices without Magisk or GApps?
[Samsung Galaxy S 4 Unified Development] js-xda:
Sorry, missed that part on testing it with fresh installed LOS in the mentioned post indeed. Thank you for pointing out. Strange and would mean also chances of a hardware defect causing it are extremely slim. Just to be sure, I tested your step-by-step instruction once again right now with a factory reset S4 active (I9252) with 210225 LOS 17.1 build (plain without anything, using 210218 LOS recovery) and can't reproduce still. Same as when trying before also with an S4 (I9505). Not drawing any conclusions - just sharing observation on an issue that I haven't run into so far at all and trying to help.
[Samsung Galaxy S 4 Unified Development] js-xda:
For the very last test today, I am 100 % sure as I double-checked every step.
[Samsung Galaxy S 4 Unified Development] arco68:
You're aware that all other variants of Lineage are heavily based on the official one? Without the official Lineage and all the work we've put into it, both platform and kernel wise, they wouldn't even have half working roms. If they have some fixes that we misses, we do have an open gerrit were they can submit them for inclusion in official builds. Give back, and not just take I guess is what I'm trying to say. It benefits everyone.

Now, regarding the particular issue you're complaining about. I've spent countless hours and days looking into it, but just can't reproduce it here. If I could easily reproduce it, things would have been a lot easier to debug.
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
thanks for clarification and thanks for your work (over years, I need to mention).

it's the first time that *I* read that an involved developer is aware/working or was working on the issue.

I didn't really believe the issue was undergone, but no one really knew that, until now.

maybe former communication would have lowered the complains/frustrations.

some pages back you will find my bug report regarding that issue and also my offer helping to nail the bug down, but I got no response.

Okay, I said to myself - with an slightly feel of being ignored [1] - : the dev's might be overloaded releasing 18.1 ... -

anyway, I've tested @side's Optimized 18.1 for some days and it seems the issue doesn't exist there and so I'm confident it won't in your upcoming Official 18.1.

[1]

and here is the key where the harshness of warrantable complains starts to grow.

unable to reproduce the bug and unable to fix the bug are both the same frustration on different sides (dev, user).
[Samsung Galaxy S 4 Unified Development] arco68:
I'm pretty sure I wrote about it somewhere, or maybe I just forgot to. I do read all bug reports though, and tries to the best of my abilities to reproduce and fix them. But yeah, for 17.1 and 18.1 there has been quite a lot of work involved with backporting features and support to the kernel, to even have a bootable and working rom. This is not an easy task and requries quite some work, but since I make this work public, it also benefits other similar devices with the same kernel version.

This particular issue I think is caused by some bug deep inside the Android source, and somehow it affects the s4 devices. I do have hopes that in 18.1 it won't happen.
[Samsung Galaxy S 4 Unified Development] therob2:
I want to help to track this reboot-issue - here are details of my one affected device:

Model: Samsung Galaxy S4 / GT-I9505 / jfltexx / 16GB

Baseband-Version: I9505XXUHPK2

Kernel-Version: 3.4.112-g98a1e59 (2020-12-17)

Build-Number: lineage_jfltexx-userdebug 10 QQ3A.200805.001 3af21a1b2e

LOS-Version: 17.1-2020-12-17-NIGHTLY-jfltexx /TWRP 3.2.3-0

several reboots per week, sometimes several a day

sometimes only black screen which recovers after 5 min

sometimes complete reboot

mostly during/after typing something in SMS/Messages, but not always.

Not reproducable AFAI found

The suggested workaround "don't use the power button" reduced the reboot frequency to once every 2-3 days.

Making several LOS-updates since August doesn't changed situation noteworthy

I don't use a PIN, just "swipe away". No root/magisk, no gapps or other add-ons during flashing etc. Pure LOS17.1. Using SIM-Card of Fonic with LTE activated. Developer settings activated. Battery setting profile = efficiency

Trying to reproducable trigger reboot by this how-to by @moreoreless was not successfull for me (tested with swipe to top and PIN). I did not changed any game-driver etc.

Becaue it was the daily driver of my mom several apps are installed (e.g. WhatsApp, Conversations, OSMAnd, F-Droid, Aurora-Store, Firefox Klar/Focus, OpenCamera (buggy), etc etc), and I did not tested as fresh installed.

I have

one

GT-I9505 (jfltexx) with reboot problems (see above) -- and

four

GT-I9515 (jfvelte) with similar settings/software and also LOS17.1-official which do NOT show reboot prolematic (or at least way less - maybe once a month). I now replaced I9505 with a I9515 as daily driver and hope the best with LOS17.1 (or 18.1 in some time). Will give I9505 with optimized-LOS18.1 a try and gave my best to give some more information before changing ROM with this post (and this less detailed before).

Cheers, Robert

Edit 1: After I gave my mum a GT-I9515 (with jfvelte 17.1) I have her "rebooting" GT-I9505 (with jfltexx/17.1) at my hands and did not encounter any reboot in playing around with it. Only hardware difference is: no SIM, no SD-Card. I of course used it now differently (instead of daily driver=messages, calls, WiFi/mobile Data I now just played in fligth mode and had no reboot/crash for 2 weeks grabbing sometimes a day and typing in editor)....although I tried hard to follow "wild tapping instructions in this thread" of @moreoreless.....not one reboot :-/ Will now test mit Wifi enabled .... strange. But anyway it is non reproduceable .... but it puzzles me.
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
I know you're an very active person, otherwise we wouldn't have an so old device with current OS.

Thanks again.

how could I give an donation without having an paypal account ?

I'm living in germany, so I guess an currency exchange is involved.

Having relations in US maybe there is a way.

Is USA your country ?

Regarding the bug:

I would suggest to let 17.1 die, best with an warning about the bug on the first page, and concentrate on 18.1, cause I guess after it's released no one will further run 17.1.

it will lower your workload.

IIRC, crash happens - additional to @moreorless finding - when I

- have tapped with the finger half on the bottom bar and half on the screen

- dito, half on the right device frame and half on the screen

- just slided the status bar down

all were not producable
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
I'll check this tonight - havening a date with an dentist right now -
[Samsung Galaxy S 4 Unified Development] moreorless:
why hurry? there is no time pressure! this issue exists more than 5-6 months there is no hurry ;)

hope it won't hurt and get well soon.