The screen artifacts, I have seen reported by someone under all OSes on the same device, and it was very present. Don’t quite know what topic it is anymore.
For the freezes, not that I have seen, but it doesn’t mean it doesn’t exist.
Yeah, I know, I get a bit fed up sometimes as well… I don’t have as many reboots (around 1 a day, perhaps more if you count hardware reboots when it falls) and only rare freezes (once or twice a week).
For the freezes: I would guess the RAM is not following perhaps, I’m constantly around 1,5-1,6 GB and I think a lot of things such as browser tab cache get deleted very quickly, and it might be that when you have many things running in background, it doesn’t manage anymore (most of time for me the freezes are preceded by a general slow-down). Perhaps it’s also linked with the number of apps you have (I’m around 250, I should get rid of useless ones, although it might not make a big difference) and the internal storage (I’m at 29,77GB out of 32, probably not enough left, and you?). Perhaps having some task killer like Drowser/Greenify/SuperFreezZ could work? Doubt it, but worth a try.
For the screen artifacts: Mystery… Maybe the firmware? I would have to try with a first gen display to see if there’s a difference, although I’m not expecting any… Will try sometime. For me they appeared at some point, I don’t remember seeing any, 6 months ago. The first time they appeared and I noticed it because I had read of these software glitches on the forum was in Oct 2021 on a small area, according to my screenshot, and now I have some on the whole screen nearly every day. I didn’t change anything to my system at this point I think, except regular updates.
And for the reboots, that’s probably the kernel or the firmware.
Hi, I had the same issue on a “defective” matherboard and I could not get rid of it, cause apparently it was not a software issue.
I changed the matherboard and did not happen to me again.
So I am worried that there is not much you can do
Hm, if it is a hardware defect it would not be nice. I guess you don’t have any idea to really proove it (logs, tests, …)?
Unfortunately my LOS-issue on GitLab was also closed with a small comment that FP or QCom should do something about this, its no LOS issue :-/
And finally I want to share this funny screenshot I recently made after SystemUI crashed, and afterwards all my app-symbols looked black/white-striped … in the main app menu just the apps which I also placed on home screen looks crazy, all other apps not beeing on home screen are still normal. funny funny. For me this doesn’t look as a real hardware thing…does it to you?
Hi,
I have experienced the same issue under Lineage, /e/ and FPopenOS. There were some differences, but it was basically the same issue. Under one of the OS (don’t remember if it was /e/ or Lineage), I had more frequent reboots, but under others, the app freezes instead and I can get to the home screen and use other apps without problems. Then after 1-2 minutes, I get an error message saying that the frozen app doesn’t react, so I can close it and reopen it.
I am using FPopenOS right now and have been for a year I guess. I wanted to give Lineage another try as it is the OS that I liked the most and had been using the most before the issues, but I have been too lazy to do it…
Thanks for this topic reference, was of great help and describes exactly my current proplem. Now I changed in developer settings the “Animationsdauerfaktor” (animation duration factor?) from 1.0 → disabled - and until now all the apps with animations which triggered before a crash doing this not anymore. Instead of the animation just a arrow is displayd - looks ugly, but functionality is not limited in my view and it doesn’t crash.
So I will try to keeping FP2 alive with this a little bit longer … 6 years and counting …
I just struggled a bit getting Magisk installed after flashing LOS 18.1. Is there already a main wiki post / detailed guide about install Magisk on fairphones?
I basically followed the Magisk install doc:
I tried both
the “adb sideload a Magisk zip” - way (mentioned as depricated)
the "patch boot.img and fastboot flash boot /path/to/magisk_patched.img " - way
but I always ended up, that the FP2 does not boot anymore (stays in the first “FAIRPHONE POWERED BY android” welcome screen).
Any idea/suggestion/idea what I’m doing wrong? Maybe is Magisk 24.2 not really working for the FP2 yet? (will give it another try with 24.1 now - not sure how I get to the point to already use 24.2 EDIT: was marked as suggested in Izzy-Droids Repo … - seems to be still a beta right now ‘2022-03-07T23:00:00Z’ → GitHub - topjohnwu/Magisk at v24.1 )
EDIT: 24.1 works …
Regarding docs/wiki note:
I just found this for the FP2, but only with links and no real details. How to root my FP2 with LineageOS 17
A wiki note might also show the differences for the FP3 and FP4 (maybe the boot.img approach works or is needed there) or just link to existing other docs (maybe there are already dedicated threads or wiki entrys for the FP3 and FP4). For the second way (patching a boot.img) I think it might also worth to mention where to get the boot.img (Magisk install doc does not really say something about it)? I assume extracting it from your rom’s build zip which you plan to install, right?
Also a point which can be mentioned - a recommended moment when to setup Magisk? Directly after the LOS flash or boot the OS ones and e.g. set up encryption and then setup Magisk…
there was a how to that is obsolete in my eyes as Magisk recently changed “a lot”. For FP4 we have a good guide on how to root with Magisk, don’t know about FP3 havent searched for it.
Übrigens ist die “alte” Methode (= Magisk.zip via TWRP zu flashen) bei mir die, die am zuverlässigsten funktioniert hat.
Should be part of the wiki note and as explained maybe just link the other descriptions/guides for the other fairphones (and do not double the info). I think about some kind of “master-note”.
Maybe I will prepare something as soon I my phone is set up again
I updated my post above and the “sideload zip” way (nr. 1) worked fine with Magisk 24.1
This here is the LOS thread, nothing Magisk specific and when you feel something is not up to date, then either rewrite thewiki, or if the topic is no wiki, then yes write a wiki or I can make the topic a wiki for you to update?
Edit:I see you should be able to open the old topic and make it a wiki on your own😉
Thanks for this little add. This was, what I wanted to know. For Magisk 24.2 I can tell it does not work with a patched Magisk boot.img. I took one from FP Open’s zip as wall as one in the latest LOS Zip → no success in both cases. As the old (sideload zip) way worked for Magisk 24.1, I did not try the patch boot image way again with this Magisk version.
Regarding TWRP:
I was always a TWRP user, but this time (as I read some difficulties - probably only regarding encryption) I used the LOS Recovery.
At the end I mostly used the wipe possibilities and adb sideload and this is possible with LOS Recovery as well.
TWRP always had difficulties with encryption on FP2, but for this release of LOS (18.1), TWRP has also difficulties with the LOS OTA updates: the two times I tried I got a not-booting device after performing a Lineage OTA update
.
)
This was, what I wanted to know. For Magisk 24.2 I can tell it does not work with a patched Magisk boot.img. I took one from FP Open’s zip as wall as one in the latest LOS Zip → no success in both cases. As the old (sideload zip) way worked for Magisk 24.1, I did not try the patch boot image way again with this Magisk version.