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 ...I am having an issue with the jactivelte build regarding WiFi - it does not activate upon initial start and later restart of the device after installing the latest 17.1 build. Similar has been reported before for 16.0 (I haven't tried the bypass - it is no solution - via GAPPS) but the ticket has been closed. Anyone else experiencing the same issue?
screen blink pink and after that screen goes black. i have lock and unlocked my phone to bring screen back.
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.I have the same issue with the pink-black-screen outage and even the weird reboots
What I found out and I can reproduce it (not always but most of the the time) by going through the following steps:
1. at the homescreen swipe from down to up to get the list of app
2. then press the home button (middle hardware button)
3. Do these 2 steps round about 6-8 times! (swipe up and home button press)
4. press the power button short to put your phone on standby
5. then press the home button to wake it up
6. give your code (I use a pin code for screenlock)
7. after unlock do the procedure 1 and 2
=> it will go pink and black
Sometimes if you press the power button during this procedure or after this procedure the device "freezes" then it shows a black screen with 3 white bars and reboots.
Sometimes the pink-black-screen happens on steps 1 + 2 after doing it 6-8 times.
And most of the time it happens during typing - doesn't matter if SMS or messenger or just the searchbar of a browser or something else. It doesn't relly matter - it happens randomly.
But my reproduceable way is the way which I found to reproduce it most of the time thand finding out on which app and what task it happens.
It is sad that the developers are not able to find, reproduce and fix this annoying problem.
The ROM is very good as such. Sure it lacks a lot of nice features but at least it has the necessary features and is somehow solid - but this weird bug or should I say "feature"
And the very battery drain which got worse since somewhere October/November build - but sadly I can't remember exactly from which one this happened. I bought a brand new original Samsung but I still have to load it up every day.
May be I could help on investigating this issue with the screen problem.
to be checked !...
I ... set the performance profile to low ... to .... preserver some battery juice.
Sorry but for some odd reason my brain throws error logs on your argumentto 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 ???
care to load that error log's upSorry but for some odd reason my brain throws error logs on your argument
Thanks, will try.@therob2
As a workaround for the reboot I can just say: AVOID the powerbutton for putting the device in sleep and wakeup. Change to double-tapp the upper-taskbar and just the home-button for wakup. With this I am able to work with the phone without reboot. There is no other help or workaround as far as I checked.
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....So if more peope report back and state their issue and in a logical reproduceable way where the DEVs can go through it see what is going on - the ROM might get better!
maybe with an backup before ?
yup, I've changed my mind too.But I changed my mind and I said to my self: "Why not give them a chance and help as good as you can and let's see if it's realy worth it and if not at least I tried"
So if more peope report back and state their issue and in a logical reproduceable way where the DEVs can go through it see what is going on - the ROM might get better!
There is no VoLTE for any Samsung phone in lineageOS.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
in your dialpad.Code:
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...
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!
lineage 17.1 20210204 opengapps arm 10.0 pico 20210205 Magisk 21407 (canary)