Beta Bug-Reports - CatWithCode
-
@dobey what is the GitLab repo address?
There is no FP5 device page so hard for users to find.Edit :
And it seems there is no issue area for FP5 already.
https://gitlab.com/ubports/porting/community-ports/android11/fairphone-5/fairphone-fp5/-/issues@CatWithUT
What android version was on your phone before installing ?
I bought my FP5 pristine couple months ago and it was shipped with android 13, and i see port is halium 11, so android 11 needed, and downgrading is not an option due to anti rollback s..tuff
-
@Keneda Device came with android 13, It was ported on halium 11. It works
-
@Keneda 13. I read the installer and it sayed install 13 first.
-
K Keneda forked this topic
-
13 is best, then we get the latest drivers. The drivers (vendor partition) are for android 11 regardless anyway. they work fine across android version due to treble and common qcom stuff.
-
Has this been updated to the latest? since some of these issues should be fixed by now. We do have a system image (installer) image now.
-
@mariogrip Last updated 7.10.24 (I added a time stemp to the first post so the last update can easylay be determined) what has been fixed? (So i know what to test for). [ Also: Im currently sick so might need a few days until I can test]. BTW. I will be also happely Daly driver test it on the fp5 as soon as basics (call and SMS and LTE) and waydroid works. (I will have a second phone on me just in case but it don't want to use it for 3 apps I really need all the time. Then it would not be a Daly driver test lol).
-
@Keneda Is there a place were I can see the current fixes / commits? In this not much changed so that can not be what @mariogrip ment: https://gitlab.com/ubports/porting/community-ports/android11/fairphone-5/fairphone-fp5
-
@CatWithUT
That should be there yes...
But only porter can tell this, and also where can we report issues as https://gitlab.com/ubports/porting/community-ports/android11/fairphone-5/fairphone-fp5/-/issues doesn't even exists. -
@Keneda I already know the issue page, thx
. I can wait until a dev has time to tell us,, no hurry 
.I'm sure Somewhere or somehow the fixes for fp5 must are verifiabley documented. (Stuff like commit tags or something).
This is invaluable for testers to see if its time to do another round of checking or trying features. Installing, testing, reflashing to an Android state and rebuilding, even with tools, is time consuming.
Noone has a fp5 just for that testing on there desk. It is there daily drive 99% of the time. Better to make sure it is worth it.
-
I have a few days where I don't need my phone 24/7, which means I'm doing more testing. I have just updated the text above.
Some things work better now but a few is still in need of work.
I will keep updating the #1 post in this thread and will update all information over on my website with a few workarounds as soon as I'm done.
I will also add a section to my website on how to configer Libertine Firefox to get a better working webbrowser for now. (Scaling, Touch, UI, ...) At the moment the progress seems good.
If I should test or log something specific, let me know.
