yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 4 Unified Development] qandres12:
Yeah I figured there was something wrong, guess this saves me some time tonight. Unfortunately I dont have have a Linux setup, even if I did I doubt i'd even be able to do a logcat since my phone stops being recognized by adb the second I flash the rom.
[Samsung Galaxy S 4 Unified Development] KRafi:
Too much hang!

My Galaxy S4 GT-I9505 (jfltexx) is hanging too much after installing Lineage OS 17.1. But my phone used to run better and smoother in Lineage OS 16. Please, solve this problem or tell me a workaround! Otherwise, I can't enjoy the latest Lineage OS and I'll have to roll back to Lineage OS 16! [MENTION=5848265]npjohnson[/MENTION] [MENTION=5968293]side[/MENTION] [MENTION=700912]arco[/MENTION]
[Samsung Galaxy S 4 Unified Development] DSGTS:
I''m not able to install Google Apps on S4 GT-I9505. Installed the Lineage Recovery and Lineage OS 17.1 via adb, but the google apps won't install.
[Samsung Galaxy S 4 Unified Development] Ph3ar.:
You'd be better off with twrp though since you can make a nandroid and restore your setup . With twrp you can get 16 set up like you want it and then dirty flash 17.1 and gapps over it and at least experience the rom . It runs pretty good on the sprint variant . I even have mine themed out with substratum . Updates are also working fine on 17.1
[Samsung Galaxy S 4 Unified Development] Ph3ar.:
Which gapps package are you trying to install ? What is occurring ? What is the build date on the rom your flashing ? Need more info..
[Samsung Galaxy S 4 Unified Development] DSGTS:
I tried the lineage-17.1-20200406-recovery-jfltexx.img, the 0405 and 0404 with the associated ROM. The gapps arm 10 nano and pico from 200404. I think that the problem is the recovery, I managed to flash it with the TWRP recovery. During the install with the adb sideload, after checking the package, at 46% it tries to start the installation and then it is aborting.
[Samsung Galaxy S 4 Unified Development] kurtn:
Get latest build
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
Is it just me ?

I'm unable to act on my calendar: change events, etc.

I'm only able to change the view: day, week, month.

what I also notice: my "calendar storage" is was always un-touched, even while I sync DAVx since days.

wired

Idea's ?
[Samsung Galaxy S 4 Unified Development] simonegalfano:
sorry but after 10 discussion pages I still haven't understood what is the correct method to install lineage 17. can you install with twrp or not?
[Samsung Galaxy S 4 Unified Development] 2013Paco:
Can confirm on my i9515 VE: Direct start of calender App impossible with error message "calender app closed repeatedly". interesting is, that with calender widget on start screen i can see actual entries and with MyPhoneExplorer i can sync entries as well as create new events. Did you try to sync your PC with your calender app, too? Same results - or is syncing impossible for you? Did you try calender widget?

---------- Post added at 21:28 ---------- Previous post was at 21:06 ----------

I tried TWRP 3.3.1.0 on S4 i9515 VE and TWRP 3.3.1.1 on S4 i9505 doing a dirty flash the same way on both phones - and it works on both phones. thats what I did:

* Coming from latest LOS 16 of 25/03/2020

* Boot into TWRP recovery

* Make a backup of LOS 16 first !!

* After backup is finished: NO Wipe of dalvic/cache/system!

* install latest LOS 17 and latest Gapps arm 10.0 (i used nano)

* reboot into system - that's all

* great advantage for me: Every account will remain. Email/Telegram/ threema don#t need to be registered new or restored from backup. Even my banking app (german DKB-Bank) works without any complaints

***** if you have secured your screen with a pin before, maybe the entering of your Pin lasts very long or pin has to be entered more than one times after every new start of your phone **

**** Some apps need a little bit longer for first starting after flashing - but than they react as quick as before ***
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
calendar starts without errors

widget works

sync works.

that's NOT the problem here !

the calendar events are viewable only.

no edit

no delete

etc.
[Samsung Galaxy S 4 Unified Development] 2013Paco:
Could you try to edit or delete Calender entries on your PC and sync them afterwards to your phone. Did this work - with my app "MyPhoneExplorer" I could manage it and sync with thunderbird/lightning... (but don't know if this worked with other apps, too!)
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
hell :crying:, is the youth of today, unable to read and understand (in this case simple questions) ?

sure, I'm able edit, etc. my calendars and events on my PC, syncing works too.

This isn't the point !!!

I need to edit, etc. my events on the phone, nothing else.

Please, answer my initial question:

are you able to edit/delete your events on the phone: yes/no ???

rw_on_xda

- only 59 ! years, .. - young !-

---------- Post added at 22:49 ---------- Previous post was at 22:29 ----------

might this

https://play.google.com/store/apps/details?id=com.tortel.syslog

help ?
[Samsung Galaxy S 4 Unified Development] arco68:
You can't. Google removed (yes it's stupid) this functionality from the app. We might replace it with another app.
[Samsung Galaxy S 4 Unified Development] DSGTS:
I tried latest build. No succes I tried on 9505 and 9515 and it doesn't work. I used the latest Gapps arm10 pico 20200408. During the installation on the adb sideload cmd at 47% it gives the error *failed to read command: No error
[Samsung Galaxy S 4 Unified Development] mimicon:
I was successfully put the latest build for 9295 as follows. First, use lineage-17.1-20200407-recovery and install lineage-17.1-20200407-nightly. After that I immediately reboot from recovery to bootloader and flashed TWRP recovery. After that I reboot to TWRP recovery and flash open_gapps-arm-10.0-micro.

It`s work for me
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
Thanks, I thought this already.

any recommendations ?

a short search results in "Etar":

https://f-droid.org/en/
[Samsung Galaxy S 4 Unified Development] Ph3ar.:
Nope , doesn't log startup . How can this app work when on a clean flash the phone boots and you can't even get through setup to add your account and go to playstore .?
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
you missed my keyword *might* !
[Samsung Galaxy S 4 Unified Development] simonegalfano:
I flashed version 17 last night, dirty flash of roms and gapps, I am pleasantly satisfied, it seems to consume less battery and it is fast, every now and then among the various menus it gets stuck. I noticed the presence of a new method to call the google assistant, via side swipes, do you know how to remove this option?
[Samsung Galaxy S 4 Unified Development] Ph3ar.:
You missed my keyword " nope" there's no might to it . If you can't set the phone up then you can't get to the point of installing an app . Even if you could install it then you couldn't log this problem with it . My nope actually addressed your keyword " help?" as well . Thanks
[Samsung Galaxy S 4 Unified Development] DSGTS:
As I mentioned in one of my previous posts, I managed also to flash the Gapps with TWRP, I just wanted to inform that flashing the Gapps with Lineage recovery was not working so far. I was hoping there was a fix for the Lineage recovery.
[Samsung Galaxy S 4 Unified Development] mentat:
[redacted]
[Samsung Galaxy S 4 Unified Development] arco68:
Yes, Etar is the one we're considering replacing it with. It's based on the aosp app.
[Samsung Galaxy S 4 Unified Development] 2013Paco:
Your reply speaks for itself. Obviously not every old man acts like a gentleman. Every further word seems to be unnecessary ...
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
where can I find it ?

thanks, etar is up and running

---------- Post added at 20:20 ---------- Previous post was at 20:12 ----------

I hope so ! :cowboy:
[Samsung Galaxy S 4 Unified Development] KRafi:
How should I root Lineage OS 17.1

I won't get support if use Magisk to root Lineage OS 17.1.! Then, which root method should I follow? Which root instructions, if I follow, I can expect support here? Please help [MENTION=5848265]npjohnson[/MENTION] [MENTION=5968293]side[/MENTION] [MENTION=3044346]arco68[/MENTION]
[Samsung Galaxy S 4 Unified Development] kurtn:
If you really need root for user apps, use magisk. If you have a problem that needs support, first make sure it is not caused by magisk.
[Samsung Galaxy S 4 Unified Development] KRafi:
But npjohnson said that I won't get support at all if I use Magisk?!
[Samsung Galaxy S 4 Unified Development] kurtn:
What support should you need?
[Samsung Galaxy S 4 Unified Development] KRafi:
Well, if I face problems or bugs in Lineage OS 17.1. Such as, if certain features don't work or my device doesn't work properly as it should. What usually users ask of when they contact a custom ROM dev?
[Samsung Galaxy S 4 Unified Development] kurtn:
Most of the usual user questions can be answered by other users. For a hardcore bug report the hurdles are high. I prefer to file bug reports with a fresh installed spare phone. - and no one forces you to install root on your phone.
[Samsung Galaxy S 4 Unified Development] ticktockman123:
Still getting used to XDA app. Hope someone sees this post.

I recently dug out a stack of old galaxy phones and have been tweaking them. All have worked out well cept. One is an S4 that has stumped me.

I have flashed RR9 ROM, multiple lineageos roms.

Every ROM seems to load up but gets stuck with a black screen. If I hold power I get a reboot.menu. if I tap the back button rapidly I can see a lineage/rr desktop. As soon as I stop.tapping it reverts to a black screen.

Any input? I have flashed and wiped dozens of ways.
[Samsung Galaxy S 4 Unified Development] kurtn:
Stock ROM is running well? You can reflash with Odin.
[Samsung Galaxy S 4 Unified Development] ticktockman123:
Is that going to get me to PIE or Q?

I have a 4.3 user backup and an Odin flashable stock ROM.
[Samsung Galaxy S 4 Unified Development] kurtn:
LineageOS 17.1 is android 10.0 "Q"
[Samsung Galaxy S 4 Unified Development] ticktockman123:
Yes. Lineageos 17 is Q.

Right now I am trying to get the desktop to work on lineage 17.

Were you thinking flashing back to 4.3 would help get los 17 working?
[Samsung Galaxy S 4 Unified Development] kurtn:
I hope, you follow the guide for your phone on wiki.lineageOS.org

What do you mean with get desktop to work?

There are many things you can do before flashing 4.3 stock ROM.
[Samsung Galaxy S 4 Unified Development] ticktockman123:
I follow instructions for ROM installs with care. Not my first device. I have successfully flashed many ROMs.

So far striking out on galaxy s4 sch r970

I have attempted flashed official los 17 and multiple optimized 15-17 ROMs by jcdteam.

After flashing with appropriate pico gapps and wipe dalvikcache. I reboot.

The first activation window appears, then I hit next/start.

After that it spins like it is trying to organize info then shortly.the screen goes dark.

If I tap the back button rapidly I can see that the home screen wallpaper is there with a dock and some icons.

As soon as I stop tapping back the screen goes black again. No home screen.

Sometimes I call the home screen the desktop.

I could flash back to an older version if you think that will offer insight.

Or is there a way to skip the new device configuration?
[Samsung Galaxy S 4 Unified Development] kurtn:
Don't flash GApps to confirm your procedures are OK.
[Samsung Galaxy S 4 Unified Development] qandres12:
Try starting on Los 16 and dirty flash using twrp. Something is wrong with the builds and they don't install properly.
[Samsung Galaxy S 4 Unified Development] ticktockman123:
I did a clean flash with no gapps previously and it did the same thing.

I will try los 16 with dirty flash later.tonight.
[Samsung Galaxy S 4 Unified Development] vip5912:
FYI: I9505: Clean Install LOS 17.1+Gapps(pico) - all is well

I used TWRP ([JDCTeam] TWRP 3.3.1-0 Custom builds - Build 2):

Factory Reset, Wipe system, data, cache, dalvik, micro SD.

Install LOS (lineage-17.1-20200410-nightly-jfltexx-signed.zip) + GApps (open_gapps-arm-10.0-pico-20200408.zip).

Wipe dalvik cache then reboot.

I did standard setup procedure (add account, set initial settings and so on).

I did first update to lineage-17.1-20200411-nightly-jfltexx-signed.zip by Setup - Update LOS.

Now all is well.
[Samsung Galaxy S 4 Unified Development] DaveWareRulesOK:
Very impressed at how easy it was to install 17.1 20200411 on top of 16.0 20200325 on my I9505.

The only thing I've found wrong is that grid size is missing from the home settings page.

I use 5 x 5 and the new default seems to be 4 x 5.
[Samsung Galaxy S 4 Unified Development] vip5912:
I did NANDROID backup by TWRP and installed Magisk.

Now all is well.
[Samsung Galaxy S 4 Unified Development] Houndcatcher:
I've just come to this from the 16.0 nightlies but all attempts so far result in a stall at the bootscreen. Tried different TWRP recoveries, various dates of 17.1 zip, clean and dirty installs and with and without Gapps. All result in the same boot loop. Any pointers? I'd try ADB but it's a long time since I've fiddled with that and I'd need to reinstall all the relevant stuff and probably relearn!!
[Samsung Galaxy S 4 Unified Development] kurtn:
My route was 16.0 clean flash with twrp. Change to lineageOS recovery, dirty flash 17.1
[Samsung Galaxy S 4 Unified Development] simonegalfano:
Did you flash rom and gapp from clean then? No problem?
[Samsung Galaxy S 4 Unified Development] vip5912:
I did clean install Official LineageOS 17.1 (+GApps).

Reboot.

Setup new installation (add accounts and so on).

Update to new Official LOS by Setup.

Reboot.

I installed Magisk by TWRP.

Reboot.

I restored my apps by Migrate (TWRP).

No Problem!
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
the "fiddleing with ADB" is just two times copy&paste:

1. adb devices

to see if the connection to the phone is there and

2. adb sideload <the favourite LOS ROM here>

I guess you're better off by following the links on page 1 in this thread, comment #8 (=> LineageOS Wiki)

steps:

a) make backup of your current rom and move it from the phone to a safe place

b) install LOS recovery

c) adb sideload the rom

I for myself is absolutely against dirty flashing, esp. when a version change (16 => 17.1) is involved [1] !

why ?

first I need to make clear that I currently don't know what's exactly left on the phone if I dirty flash !

But I guess there is something left and that might cause trouble.

esp. in the case of a crash/bug I always need to ask myself if the crash/bug was caused by the combination of "dirty flashed AND the currently running ROM".

By an clean flash there no such combination/question.

the crashes/bugs I see then are clearly caused by the ROM-Version I'm currently running [2].

that said it should be obvious that a clean flashed rom is easier to debug and (hopefully) fixable.

I also guess that I get more attention from the dev's when I have flashed the rom in an suggested way, he/she is able to follow to reproduce the bug, what also might mean that we/I get the fix quicker.

[1]

AFAIK, in Android 10 the boot mimik has changed.

To me it means dirty flashing a new version may have worked, but it doesn't mean it will work everywhere and everytime !

if you bricked your phone by "nailing" a ROM on it, cause it has worked nice in the past, you exactly know what I'm talking about ...

[2]

not exactly, cause there are apps too, but ....
[Samsung Galaxy S 4 Unified Development] simonegalfano:
I mean, did you do a clean installation or did you flash dirty from lineage 16 to lineage 17
[Samsung Galaxy S 4 Unified Development] vip5912:
I did clean installation from Optimized LOS 16.0 v14.
[Samsung Galaxy S 4 Unified Development] Houndcatcher:
Hi thanks for that :)

As I said I've tried various methods all using recovery and flashing the zip but I've not tried ADB mainly because I dson't have it installed on my iMac currently. I will try sideloading at some point when I have more time to sort it all out. I may also have a look at the JDC version too just to see if that works ok.
[Samsung Galaxy S 4 Unified Development] simonegalfano:
if you did it coming from Optimized LOS16, installing on it without formatting anything, it is not a clean installation; have you formatted before?
[Samsung Galaxy S 4 Unified Development] vip5912:
See my post:

I used TWRP ([JDCTeam] TWRP 3.3.1-0 Custom builds - Build 2):

Factory Reset, Wipe system, data, cache, dalvik, micro SD. <======!!!!!!!!!!!!!!!!!!

Install LOS (lineage-17.1-20200410-nightly-jfltexx-signed.zip) + GApps (open_gapps-arm-10.0-pico-20200408.zip).

Wipe dalvik cache then reboot.
[Samsung Galaxy S 4 Unified Development] Thingonly:
encryption bug?

encryption bug?, after push button smartphone encrypt shows few second the android logo and then the LOS logo in normal boot.

after enter the pin, go to settings and it's shown not encrypted :confused: can you fix it plz?
[Samsung Galaxy S 4 Unified Development] vip5912:
adb device unauthorized

LOS 17.1 (12.04.2020), all well, stable, fast, except:

$adb devices
List of devices attached
R31Dxxxx	unauthorized

There is no authorized request on phone.
[Samsung Galaxy S 4 Unified Development] Ph3ar.:
Make sure you've turned on ADB debugging under developer options . Also Revoke USB debugging authorizations under developer options to cause the phone to make the new request to authorize .
[Samsung Galaxy S 4 Unified Development] vip5912:
Naturally I already did USB ADB debugging ON and revoke USB debugging authorizations under developer options.

The result is the same.
[Samsung Galaxy S 4 Unified Development] kurtn:
S4 active: as soon as I plug in computer with running adb daemon, the "allow USB debugging" dialogue pops up.
[Samsung Galaxy S 4 Unified Development] vip5912:
Yes! I press OK and I see in notification area "you can connect with adb".

But on the PC I see "device unauthorized".
[Samsung Galaxy S 4 Unified Development] vip5912:
How to fix adb devices shows unauthorized device

Disconnect USB between PC and device.
Stop adb server by entering "adb kill-server" in command window.
On device use "Revoke USB debugging authorizations" in "Developer Options"
On PC delete "adbkey" file in user directory, for example "C:\Users\JohnDoo\.android"
Reconnect the device to the PC.
[Samsung Galaxy S 4 Unified Development] ticktockman123:
So I attempted a dirty flash and made progress. Now there is a desktop/home screen. But phone auto reboots after like 60 seconds.

I Odin flashed a stock firmware from team us cellular thinking I would go back and Dirty flash over that.

I'm now at 5.0.1. Stock gapps. But Odin won't detect my device, mtp/adb are not connecting. Windows keeps returning an error message no device descriptor available error message.

I am currently unable to heimdall flash lineage recovery which is probably why I had trouble flashing losQ first go around.

I didn't follow the directions explicitly. Sorry.

I tried.to.use twrp, then tried to use optimized twrp in attempts to load optimized los .

My about device:

Baseband =r970tysgpl1

Kernel 3.4.0-7913492

Etc..

Build lrx22c.r970tysgpl1

Se enforcing

Then hardware, software and Knox version data.

Any support appreciated ...
[Samsung Galaxy S 4 Unified Development] kurtn:
Follow that guide

https://wiki.lineageos.org/devices/jfltespr/install
[Samsung Galaxy S 4 Unified Development] KRafi:
How to check the build date of my installed LineageOS build? Can I check it from within LineageOS?
[Samsung Galaxy S 4 Unified Development] vip5912:
Setup - About phone - Android version
[Samsung Galaxy S 4 Unified Development] KRafi:
I want to know my build date, not android version!
[Samsung Galaxy S 4 Unified Development] vip5912:
Press Android Version and you will see all information about you current build.
[Samsung Galaxy S 4 Unified Development] Diabolik2770:
jfvelte and twrp

i can install latest build with twrp?
[Samsung Galaxy S 4 Unified Development] kurtn:
Ota update didn't work automatically in twrp. Had to manually select zip file. Magisk has been successfully restored.
[Samsung Galaxy S 4 Unified Development] adammanson:
https://xdaforums.com/showpost.php?p=82194439&postcount=83

Went back to LOS 16.0 two times now.

Got the same Freezing issue on build 2020-04-10 too

Will flash again in few days and check it...

any suggestions?
[Samsung Galaxy S 4 Unified Development] kurtn:
Try without GApps to make sure it's a lineageOS issue or a GApps problem.
[Samsung Galaxy S 4 Unified Development] kukele:
I have the same problem with build 2020-04-14 (jfltexx). I did a clean installation from stock rom without gapps, so thats not the problem.

I have also random freezes, most of the time during web browsing (fennec Browser)
[Samsung Galaxy S 4 Unified Development] nacho370zn:
I have the exact same auto reboot problem on LOS 17.1, tried it with and without gapps and the problem is still there. So I went back to an oreo rom I had in my sd and it works fine.

Help from anyone would be appreciated
[Samsung Galaxy S 4 Unified Development] testerS4:
Thank you for your work from 16.0 to 17.1. I am pleasantly amazed that the upgrade worked without errors. I went through all phases of LOS. It was only complicated from Oreo to Pie. That required a vendor image beforehand. I took the step to 17.1 today. The following initial situation: jfvelte, i9515, TWRP 3.3.1.0, last build LOS 16.0 March 2020. LOS 17.1_20200415 and Gapps arm 10.0 pico flashed directly via TWRP. System start OK. No crash, no boot loop. I had to flash Magisk 20.4 again. That was broken. EdXposed with the modules were all intact afterwards. The only thing I've noticed so far is that USB debugging is only recognized in TWRP mode on the PC.

(sorry for Engl ... I use translators)

jfvelte/SM-G i9515/17.1
[Samsung Galaxy S 4 Unified Development] Diabolik2770:
jfvelte and some sd card

jfvelte i9515

when i put apk and images in the sdcard the apk icon is not displayed.

and if I open the image nothing is visible.

but if I restart my smartphone, everything returns to normal ...

I've also tried other browsers but it's always the same thing.

I use a sdcard samsung

I remember that this also happened in lineage 14 but then the developer fixed it
[Samsung Galaxy S 4 Unified Development] vip5912:
Try this:

Disconnect USB between PC and device.
Stop adb server by entering "adb kill-server" in command window.
On device use "Revoke USB debugging authorizations" in "Developer Options"
On PC delete "adbkey" file in user directory, for example "C:\Users\JohnDoo\.android"
Reconnect the device to the PC.
[Samsung Galaxy S 4 Unified Development] electronspin:
Please, did someone a dirty flash of lineageos17 jfltexx + pico/nano gaps + addonsu using TWRP 3311 recovery?

does everything work perfectly or are there unexpected bugs?

Thanks a lot
[Samsung Galaxy S 4 Unified Development] testerS4:
Unfortunately it didn't work. :rolleyes:Thank you for your efforts.
[Samsung Galaxy S 4 Unified Development] side:
Hello everyone. i have read all the posts here ,and here are some notes from my....side

About installations and bootloops and such.

Thats how i would flash a new rom: Get latest TWRP, flash latest bootloader + modem from ODIN (ENSURE THAT ARE FLASHED CORRECTLY), format my data(optional) from twrp, wipe everything and maybe sdcard too, flash the rom, flash the gapps, reboot.

Dirty flashes etc are ok to be done but you take the risk....

The 'i' letter became bigger in order to point out that its my personal opinion.

I see some parasites here ...again.... About "i dev only the devices i have, not like lineage do"... Remember your past mate

Please post logs. here or at bug tracker at lineage

My personal tests according root, is only the magisk way....About the support....If the log proves that the root solution doesnt NOT affect the bug that you share, i

guess

that you will recieve support