yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 4 Unified Development] vip5912:
FYI:

OTA update to 2021.04.22 is working well.

Update file export is also working well.
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
yup !
[Samsung Galaxy S 4 Unified Development] sw_strange:
Updates with Linage Recovery/Updater worked well this morning. Last week, I had to do the updates by dirty sideloading it. This week, I just let it do it's Linage stock update, worked perfectly. Note: I am not using Magisk.
[Samsung Galaxy S 4 Unified Development] Gitanitos:
Good news, my GT-I9505 is updating automatically at this moment ("Update recovery" option disabled).

Next step, activate the option to update the recovery and see if this works well.

Thanks @npjohnson for your incredible work
[Samsung Galaxy S 4 Unified Development] npjohnson:
the recovery image updates the second you check the box.

after you update OS, it updates the recovery on the next boot during boot animation.

Have fun! Good to hear.
[Samsung Galaxy S 4 Unified Development] js-xda:
Seeing several reports about the OTA updates giving issues and it being apparently solved in the 210415 build, I would like to share an observation - and thank the developers for all their work!

On an I9505 (jfltexx) which I upgraded via dirty flash from 17.1 to 18.1, I wasn't able to export the downloaded 210422 update what I tend to do on that device before installing. Wasn´t possible resulting in an error - I checked on permissions and also reset all data of the updater (not settings). After successful OTA update to 210422 (had done the update before on another I9505 without issues and therefore dared to do even with this error), it was possible to export.
[Samsung Galaxy S 4 Unified Development] bersem:
it exports the file but where ??

EDIT: its now located in :

Android/data/org.lineageos.updater/files/LineageOs updates

regards !
[Samsung Galaxy S 4 Unified Development] droi1:
for those with same problem -> can't restore gdrive backup (Apps/device settings) mindthegapps try this Guide (german website)

Android-Sicherungen: Backup und Restore manuell durchführen | ZDNet.de

Wenn das in Android integrierte Backup nicht funktioniert, muss man sich über adb Zugriff auf den Dienst bmgr verschaffen. Damit ist auch eine manuelle Wiederherstellung von zuvor gespeicherten Daten möglich.

www.zdnet.de

Important: Skip setup wizard completly on first boot LOS 18.1 don't connect wifi/mobile data.

Login later in your Google Account with "Complete devices setup" enable usb debugging connect to PC start minimal ADB and follow website Guide above.

Now evrything is restored completly!
[Samsung Galaxy S 4 Unified Development] Franz666:
Thanks for a great ROM again!

Does anybody have problems with USB storage as well? At my I9505 a 4GB USB drive connected with an OTG adapter is not recognized under LOS 18.1. But I can use it in the file manager at twrp-3.5.2_9-0. It also works at another S4 GT-I9505 still with LOS 17.1.

Only other devices like a mouse are running.

Any ideas?

Regards!
[Samsung Galaxy S 4 Unified Development] pocketrule:
USB otg is unfortunately broken at the moment. But you can get access to your external storage by installing MiXplorer (which I recommend in any case) and "enable otg" in settings -> more settings
[Samsung Galaxy S 4 Unified Development] Savatage76:
hello!

why if I use home button for turning screen on, the screen goes To homepage and doesn't remain in app that was opened before the screen turn off? thanks
[Samsung Galaxy S 4 Unified Development] orse04:
Hello, the hotspot goes out when the mobile data is switched on.
[Samsung Galaxy S 4 Unified Development] Blackeyse:
happens to me too
[Samsung Galaxy S 4 Unified Development] npjohnson:
Fixed exporting updates. Current build should be able to.
[Samsung Galaxy S 4 Unified Development] npjohnson:
Should be fixed in next build.
[Samsung Galaxy S 4 Unified Development] vip5912:
FYI: There are many Changes to be included in next build:

https://download.lineageos.org/jfltexx/changes/

In particular: long press back to kill app, USB otg, etc.
[Samsung Galaxy S 4 Unified Development] js-xda:
Is it by design that updates are now exported to "/sdcard/Android/data/org.lineageos.updater/files/LineageOS updates" and no longer to "/sdcard/LineageOS updates"? Something related to permissions?
[Samsung Galaxy S 4 Unified Development] npjohnson:
Yes, it's forced due to Android's "Scoped Storage"
[Samsung Galaxy S 4 Unified Development] Ericeric2020:
title suggests "All variants" , but does it support i9500 then?
[Samsung Galaxy S 4 Unified Development] kurtn:
All snapdragon variants. Your exynos is stuck at nougat

LineageOS Statistics

stats.lineageos.org
[Samsung Galaxy S 4 Unified Development] Ericeric2020:
Thank you for clarifying. When i saw "all variants" i got pretty excited. Bummer i hate exynos :p
[Samsung Galaxy S 4 Unified Development] DerGriechisch:
Gt-i9506 is missing these arent all s4 variants
[Samsung Galaxy S 4 Unified Development] Lycon70492:
Currently running official lineage os 17.1 on the jfltexx (GT I9505) and official twrp 3.4.0.0.

Is there anything in particular I should do before installing lineage os 18.1; for example, version of official twrp to use, twrp format data etc?
[Samsung Galaxy S 4 Unified Development] kurtn:
You are good to go. If you want to format data, do it. If you don't, all your apps and data will survive. Except email.

If you had GApps installed and don't format, you need to flash android 11 GApps immediately after 18.1
[Samsung Galaxy S 4 Unified Development] karlico:
Thanks for this great rom! Getting the newest android on this 2013 phone is just amazing.

I installed the newest lineage recovery, from 2021-05-13, and it wouldn't flash the OS succussfully. Tried with the OS versions from 2021-04-22 and 2021-05-13. Outputs from the abd sideloading below(phone). The phone would then reboot back to stock rom. On the computer side the adb output updates stopped at 94%. I believe the first 2 red lines with errors(phone) popped up at 47% and the next identical ones at 94%

Then I installed twrp instead of lineage recovery. ABD sideloading the OS went absolutely fine. And as the instruction says I did get the following error message which is fine: "If the process succeeds the output will stop at 47% and report adb: failed to read command: Success."

s4 version is GT-I9505.

EDIT: Managed to boot into stock recovery instead of lineage recovery. Because I booted stock rom after flashing lineage recovery.
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
does the sha256 checksum of the downloaded LOS match ?
[Samsung Galaxy S 4 Unified Development] x2k13:
from https://wiki.lineageos.org/devices/jfltexx/install

5. Sideload the LineageOS .zip package:

On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.

On the host machine, sideload the package using: adb sideload filename.zip.

Tip: If the process succeeds the output will stop at 47% and report adb: failed to read command: Success.

The output on your display, Manual Mode...I've never seen that during sideloading. 🤔
[Samsung Galaxy S 4 Unified Development] karlico:
I'm pretty sure I checked the checksum for OS zip files. I am trying to recheck now. The 05-13 version is fine. However the os version I flashed secondly, yesterday, was not 04-22, but 04-15 according to my local file. I am not able to find the checksum of that version anymore as it is not listed on the official download site. Weird I guess.

I did not check the checksum for lineageos recovery file.

I used those installation instructions step by step. But had to use another computer after I'd installed lineage recovery as I was not able to get adb to work on the first computer.

The menu on lineage recovery did not match the instructions 100% . I had an option directly from the main menu that said "Apply update from ADB" which I used.
[Samsung Galaxy S 4 Unified Development] x2k13:
Are you running Windows or Linux on the computer you use to connect to the phone via adb? Asking bacause on Linux using adb is really stable and easy to setup, it's in the package repos of all major distros.

I used to do it on Windows but that drove me nuts, always something that didn't work as it should.
[Samsung Galaxy S 4 Unified Development] karlico:
I'm using windows on the computer I first tried to sideload the OS. Was not able to get that to work out.

Then I switched to a linux computer. And yeah a flawless ADB experience.
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
yup, checked that by just exchanging the numbers of another checksum link.

why weird ?

I guess nobody will download an month old file, even when in newer one's security patches went in.

It would just waste storage (summing all devices over time with each ~0.5 GB in size per week)
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
it's windows build in and a /the feature :LOL:

- a linux user (~20 year's) fed up cleaning registries by hand ... -
[Samsung Galaxy S 4 Unified Development] Lycon70492:
I like to report that installation of lineageos 18.1 with the current setup was a success. I did not twrp data format before installing as there wasn't a need for it. I also installed MindtheGapps for the first time as I typically use Opengapps and magisk v23.

As for lineage-18.1-20210513, USB OTG isn't working, which I'm guessing its a known issue.

Aside from the new method of taking a screenshot, is there anything from Android 11 is notably different from Android 10?
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
for LOS 18.1

Changelog 25 - Exemplary Eleven, Ravishing Recorder, Captivating Calendar, Beaming Backup

Ohai there, it's been a while

lineageos.org
[Samsung Galaxy S 4 Unified Development] 0xfab1:
Unfortunately, I did not have a good experience with the upgrade of my GT-I9505 from 17.1 to 18.1.

Before I started, I made a full backup with twrp 3.5.0_9-0 (= latest official version). I selected all partitions in twrp for this purpose. After that I tried to upgrade from LOS 17.1 to 18.1 as some users here in the forum described it, i.e. I proceeded like one installs a Nightly::

* Installed lineage-18.1-20210506-nightly-jfltexx-signed.zip

* Installed MindTheGapps-11.0.0-arm-20210412_124103.zip

* Wiped Cache/Dalvik

* Booted system

After booting, the lockscreen appeared after some time and after I entered my PIN and left the lockscreen the system just stopped. I finally rebooted the device by long pressing the power button but unfortunately without success - after the lockscreen it was all over again.

At this point I wanted to restore the backup I had made just before. And here came the big negative surprise: After restoring everything from the backup, I cleared Cache/Dalvik and let the system boot normally ...and it started in revovery mode (?!). I then tried several times to boot the device from twrp normally, also with the variant that I first selected Power Off in twrp and then turned on the system with the power button. Then I restored the backup again and repeated everything. But all this did not help, the device remained stuck in recovery mode.

Finally, I proceeded as described in the OP, i.e. following the instructions in the wiki, where among other things the data partition must be deleted (= the device must be newly set up, which is partially facilitated by Google backup data). And finally it worked: LOS 18.1 boots normally and so far I haven't found any bugs.

*** At this point a big thank you to the developers for this ROM and for the long lasting support of this device! ***

The reason why I made a rather long post here is my negative experience (= warning) that with twrp 3.5.0_9-0 the device cannot be fully restored when restoring a full backup and that you end up in a state where the system cannot boot normally anymore. I wonder if anyone else with a recent or the latest twrp version was able to restore a full backup and then had a working device again. If so, how exactly did you create the backup and what exactly did you restore?
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
to my taste there are some other questions left over:

1. has someone mangaged to restore an Los 17.x backup on an Los 18.1 successful ?

2. same as 1. , but this time with the lastest TWRP, which is twrp-3.5.2_9-0

Download TWRP for jflte

Download TWRP Open Recovery for jflte

eu.dl.twrp.me

3. does a google-backup restore really wipe the data partition the same way as a Stock or TWRP recovery wipe/format does ?

see

Upgrade LineageOS on jfltexx | LineageOS Wiki

wiki.lineageos.org

point 5.
[Samsung Galaxy S 4 Unified Development] therob2:
Are there already any issues with random reboots we knew from 17.1 from time to time?

As I did not read anything in this thread can I expect they are gone? Or the formerly affectec peaple did not upgrade yet?

And any complaints about WiFi-reconnects known from 17.1?

(Talking about GT-I9505 and GT-I9515)
[Samsung Galaxy S 4 Unified Development] antoniorecio:
Thank you very much to JDCTeam for this ROM.

I did a clean install and everything seems to work fine but, i can't encrypt phone.

When I choose Encrypt phone, the phone reboots, showing a screen with the Android image laying down for a second or so, and then reboots normally again, but not encrypted.

Is it only me or encryption does not work?

Regards and thank you.
[Samsung Galaxy S 4 Unified Development] 0xfab1:
Hi rw_on_xda

Thanks for your reply.

As for 1: Dunno + that was part of my question.

As for 2: AFAIK, twrp-3.5.2_9-0 was not yet the latest official twrp version when I upgraded from 17.1 to 18.1 a few days ago (2021-05-09). I believe that at my upgrade time 3.5.0_9-0 was the latest official twrp version. twrp-3.5.2_9-0 must have been released very recently, right?

As for 3: AFAIK, No. I.e. Google Backup/Restore does not wipe anything at all - if everything works out, the apps from the Play Store with their settings are reinstalled and set up reasonably well.

As for 4: Yes, as I wrote before, I followed strictly the instructions in the wiki for my 2nd (and successful) attempt to upgrade.

As for 5: What's your point?

I guess the new question now is whether twrp-3.5.2_9-0 can fully back up a device and then fully restore it again if necessary?

Quite a few open questions about TWRP that rw_on_xda and I have raised. Maybe someone knows more about this - thanks in advance for anyone who can shed some more light on these questions!
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
I downloaded TWRP 3.5.2_9-0 at 2021-04-09 (write date on my disk), so ~5 weeks !

Point 5 is the Point 5 in the linked document (... no wipe => no boot... => less fun)

okay I should have written "see Point 5" ...

the "new question" is fastest answered, when *you* have tested it.

no ?

well, long version:

I guess you're at it right now and I further guest the most of us have a full configured system since some time and a successful restore isn't in the pipe right now and as always "Never touch a running system".

*I* take Twrp backups on an more irregular basis, esp. *not* for restoring over different LOS version (17 => 18)

why ?

well, upcoming bugs in an "clean installed LOS" are bugs belonging to that special LOS version.

while - at least I could imagine - a system "hoked up" with an backup from the previous LOS release I guess that point is not 100 % clear.

I only have sort of 20 apps running on my device, contacts and calendars are synced from my pc [1], mails are on an imap server and on a new release in any case I look through *all* settings.

so, actually no need to do backup's.

wait.....,

there is one special case:

when someone in this forum raised the alarm flag: "new nightly does something weird" I make a backup before installing the new nightly....

[1]

on linux: thunderbird with addons (sogo, TbSync, Provider for CalDAV & CardDAV) and radicale

on the phone: DAVx and opentask

why should I sync my adressbook, etc. with google ?

do they sync their's with me ? :cool:
[Samsung Galaxy S 4 Unified Development] pocketrule:
No, you're not the only one 😳️

Obviously, when you format /data in TWRP (e.g. to get rid of an existing encryption), the /data partition is formatted completely, so there's no space left for important encryption information. 😬️

Have a look here for a better description and solution 👍️

Fixing LineageOS encryption issue · Temp title

thomas.blarre.net
[Samsung Galaxy S 4 Unified Development] Retrial:
Just an information for ppl who use GApps, NikGApps CORE version working in ARM devices.
[Samsung Galaxy S 4 Unified Development] vip5912:
I had random reboots in 17.1 regularly.

After I installed 18.1 (clean install in begin of April) I have no one random reboots.
[Samsung Galaxy S 4 Unified Development] vip5912:
I have no problem with encrypt phone.

I made clean install 18.1 by official LineageOS Wiki:

https://wiki.lineageos.org/devices/jfltexx/install
[Samsung Galaxy S 4 Unified Development] 0xfab1:
If an easy upgrade is possible, then of course I'll try that first. And no matter which way I try first, before that I make a backup ... which then, if you really need it, must really work ... and that was not the case here.

Well, custom ROMs are fun, but playing around with them also means to me that I can help myself when something goes wrong. And this is where I've always been able to rely on TWRP/Nandroid backups in the past.

By restoring a full backup, you should be back to the point when the backup was created. At least that's the claim TWRP makes. And I have always been able to rely on it in the past when facing problems with release upgrades.

I too have only the bare essentials and a few apps installed on my S4. For me, the device is a fallback in case the smartphone I use daily is lost or broken, i.e. the installed apps on the S4 are registered for banking and other services that require a smartphone for login or confirmations.

I don't really rely on Google for upgrades either, but after the failed backup restore, I was quite happy to have the apps and some settings back quite quickly via Google. The rest I have done as far as possible with Titanium Backup - unfortunately TB is no longer maintained - which makes it all the more important that TWRP backups work.

When I have a little more time, I'll do a factory reset, install the latest TWRP version, and set up the S4 from scratch. After that I will do a TWRP backup, do a factory reset again and restore the backup. That will be the acid test for me to decide if TWRP can really be relied on for the S4.

Has anyone tried this with a recent TWRP version lately? If so, it would be exciting to hear whether and how well this has worked.
[Samsung Galaxy S 4 Unified Development] droi1:
are you using TWRP? Then use old TWRP 3.2 and everything works newer TWRP often not working with encryption....

reboot problems are gone ;)

Wifi is the same stable/unstable for me as in 17.1 so not the best but for me this was since Stock ROM the case.
[Samsung Galaxy S 4 Unified Development] antoniorecio:
Thank you very much, @pocketrule. You nailed it.

I followed instructions from the URL you pointed me to, and I have successfully encrypted the phone.
[Samsung Galaxy S 4 Unified Development] antoniorecio:
Thank you, @droi1

I used latest TWRP. The problem it seems to be the format of /data partition. I followed instructions of the OP where it says to format /data partition. This way the filesystem take all the partition space. It seems that you need an additional 16Kb at the end of partition to be able to encryp the partition. So I had to shrink filesystem by 16KiB.

It's explained in a URL posted by @pocketrule at post #130 (https://xdaforums.com/t/official-li...xy-s4-all-qcom-variants.4255313/post-85028669). I followed that instructions and successfully encrypt the phone.

Maybe older versions of TWRP let those last 16 KiB of /data partition unused.
[Samsung Galaxy S 4 Unified Development] antoniorecio:
Thank you, @vip5912.

Maybe the /data partition formatting from lineage os recovery let unused the last 16 KiB of partition that it seems to be necesary to enable encryption. Anyway, I could shrink /data filesystem by 17 KiB following instructions from URL of @pockectrule post.
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
then you should investigate your whole wifi equipment.

Cause I - IIRC - never have had wifi problems since 2013 with cyanogen/LOS or stock.

And if I do not recall correct (cause my "RAM" was "build" 1961) wifi problems had been temporary.

Usually I run wifi with constant 433 Mbit/s on 5 GHz with WPA3 and PMF.

on your wifi router check:

- channel 13 or the channel the strongest neighbour you see (yes the same channel[1] ) for 2.4 GHz wifi

- channel >100 for 5GHz wifi (cause at least my router transmits with 1000 mW with that channels versus 200 only)

- wifi 5 GHz is lesser used

[1]

If you've ever played with apps what displays wifi signals you know some are displayed as parabola's.

where the parabola's cross each other there is most demolition of the signal.

there are only to ways to prevent that

- the channels of the participants (the apex of the parabola's) are far away, so they don't cross [2]

- the channels are the same

for the last one:

one would think it would lead to an complete demolition of the signal, but it isn't that way.

my observation here where that I get the best signal when I choose the same channel as the strongest neighbour. I guess both wifi then send with full speed at different time frames => no or less demolition.

and btw in physics I've learned waves with same frequency add their amplitudes (in the worst case to zero when frequency shift is 180°).

It seems wifi waves do something similar apart from that you never get the doubled amplitude (doubled wifi speed).

cause of this physically behaviour we are able to fight noisiness with 180° shifted noisiness (amplitudes added to zero)

[2]

for 2.4 GHz wifi it is said participants should have at least 5 channels distance from each others in wifi network with 11 or 13 channels in total only.

you could image your self how that works out if you're living in area with ~40 wifi neighbour networks...

so the same fixed(!) channel of the strongest neighbour seems to be the best, additional cause I know most wifi router are configured with "auto channel".

so they move away by time when 2 or more participants constantly sending on the same channel...
[Samsung Galaxy S 4 Unified Development] vip5912:
I also never have had wifi problems with cyanogen/LOS or stock.

I use 4 WiFi APs (TP-Link, Apple, D-Link) in different rooms with 2.4 and 5 GHz (I use fixed channels).

Phone uses 2.4GHz for long distance, notebook uses 5GHz for speed.
[Samsung Galaxy S 4 Unified Development] 0xfab1:
Hi droi1

I had the same Wi-Fi problems as you describe here a couple of years ago. I was able to solve the problem by updating the firmware.

Very good and detailed explanations as well as background info on how to update the firmware can be found in the (somewhat outdated) OP of this thread.

A current collection of firmware and quick guides can be found in this thread (= grab the firmware from there and not from the first link). I recommend that you use the update variant "Combined Bootloader & Modem".

Hope this helps.
[Samsung Galaxy S 4 Unified Development] droi1:
thanks i have already newest Modem XXUHQK1, i noticed it happens when my Wifi is changing from 5ghz / 2,4ghz and vice versa. Wifi on S4 is reconnecting directly when Phone Screen goes on / waking up. Is it possible with an App to force 5ghz only? I know i can change it in my Router but so i can change things without affecting my other Devices.
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
well, it *might* come with a drawback: more battery consumption, *but* I'm not 100 % sure.

with an nearly complete idle phone, wifi and BT both off, 2G and modem on QK1 I saw with my original first battery ~15 % drain on LOS 17.1.

Now I see with a new battery, LOS 18.1 and original stock modem (PK2) only ~8 % drain over the last 7 days and I have done an LOS update which alone took 6 %.

well, several things have changed simultaneous (new battery, new LOS version), so I'm not sure it was the modem FW.