yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 4 Unified Development] xperanto:
And you really think this "procedure" is a normal way to use your phone?

Of course by overloading your system with infinite inputs, especially with peformance settings to low, you can crash ANY system.

I`d suggest to set the performance up, use your phone in a normal way and see, if it occures again.

Beside your procedure, if you read other threads the pink screen mostly indicates a "slowly dying" hardware.

There are also so many other circumstances which can lead to such behavior.

e.g.

Do you really know, if your screens aren`t replacement screens ("original" or third party doesn`t matter) ?

Have they been "refurbished" ones?

did you buy them used and you don`t know their "curriculum vitae"?

Third party batteries which don`t meet the specifications?

I could go on and on...

Did you flash any experimental/unofficial or other custom ROMs beforehand? I had similar issues with the screen of an other handset of a different manufacturer, because a customrom changed values in nv-ram the official LOS didn`t even touch. Solution in my case on this specific device was to "pre-flash" an official rom and LOS was good again. Even if it`s anecdotic it shows there is more to that than your, sorry for the strong words, demanding arrogation.

Please always keep in mind: arco68 and the LOS team are doing all of this hard work for us all, for free, and google and the manufacturers have abandond your/our devices the moment we purchased them. with all the consequences their misbehaviour implies: be it artificial planned adolesence by software, security risks, enviromental damage due to their "throw old away, buy new mentality" and last but not least your purse.

So please, don`t be that demanding and keep down your huffy feelings. Be polite and at least thankfull in a constructive way e.g. at least post some logs...

Dear LOS-Team and @arco68,

thank you for the work you are donig. Without you, i wouldn`t even have/use a smartphone!
[Samsung Galaxy S 4 Unified Development] moreorless:
Of course not but I tried to find a method to provoke it in order to help the DEVs that may be they will find something in the logs which could give a hint. The issue occures just by normal usage and as I mentioned in my posts before which you obviously didn't read - that it will just happen if switch between apps (recent button) or just by typing or just a simple swipe-up of app menu. So it has nothing to do with overloading there is a bug in my opinion.
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
log is already there: comment #547

btw. my phone was completely new, bought 2013 in one german big electro market.

KNOX was untouched. Installed Stock was one release back.

the device only saw stock, CM (since 2013) and LOS, OPT-LOS.

always flashed according the ROM maintainers instruction

1st battery was exchanged ~Nov./Dec. 2020.

crash happend also with the new battery.
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
didn't hurt - so far -, but needs a 2cd date and that one could hurt.

my teeth issue is like the screen issue: unable to reproduce...
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
my varying parts:

baseband/BL: XXUHQK1

LOS: 17.1-20210211

Kernel: 3.4.112-g02796ea

recovery: TWRP-JDCTeam-3.3.1.0-build2

- EDIT -

setup the phone with last LOS 17.1 via clean flash under recovery

before install: wiped Dalvik, System, Cache, Data, Internal Storage

after install: left Dalvik as is

no gapps, just the pure LOS.

adjusted some setting (sound, display, dev. options,..., network)

last actions I did:

in "Network & internet" => Mobile network:

"Preferred network type" => 2G

"Data warning & limit":

- "Set data warning": ON

- "Data warning": GB => MB

- "Set data limit": ON

- "Data limit": GB => MB

back

"Data Saver": ON

suddenly the screen got unresponsive (no action while tapping on "<--- Network & internet") and ~5 seconds later the screen crashed (3 horizontal white bar's on an black screen (black/white alternating) for ~3 seconds) and then an reboot.

2. attempt.

again same setup.

without other adjustments the same Network settings as above.

no crash...
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
- scratched -
[Samsung Galaxy S 4 Unified Development] :
Good Day! Very Nice ROM and it's working fine. I have the SPH-L720 model and I seem to have lost my sound after flashing LOS 17.1. Is there any patch that can fix this?

I have another question, what magisk is best to root this device? Thank you! Have a nice day!
[Samsung Galaxy S 4 Unified Development] dfw123:
It can not flash. Does this support samsung s4 sprint L720T? Thanks.
[Samsung Galaxy S 4 Unified Development] kurtn:
L720T is not mentioned in wiki.lineageos.org
[Samsung Galaxy S 4 Unified Development] simonegalfano:
have I encountered any problems with the Googleapps Nano? I have been using those of August for many months because with the updated ones the configuration of the Google assistant (voice match) does not complete, it gives me the error "connection problems, try again" which Google app do you use?