Beta Bug-Reports - CatWithCode

Fuseteam

@CatWithUT said in BUG: USB-OTG Hard Crashes Phone:

@Fuseteam That is what beta tester are for

hah! fair. I stand corrected XD

Fuseteam

@CatWithUT hmmm no hub, not sure then what it could be

Keneda

@CatWithUT
I'm not sure but I believe Waydroid needs some work on a device for it to work, are you sure the FP5 is "Waydroid ready" ?
I guess for now we should wait for the port to reach RC ou stable before taking care of Waydroid.

Keneda

@CatWithUT
That's one of prime UT dev, @dobey, that downvoted you lol, you can see it by clicking on the number of votes.
I don't know why, maybe a bad day for him

Second: In the linked blog entry in my profil here I have made a very extensive list of things that have been tested (to not spam this area with usless topics like "works lol").

That's maybe the reason for the downvotes.

You could use only one topic here to report all your testing.

CatWithUT

@Keneda Oh ok. Then i do that from now on. I did not know that it sould be done like this. My bad. sorry.
Then linking externaly is probably bad to. I will just clone my list here:

A list of stuff I tested with last tested Status and the Tickets if any (Copy of: https://catwithcode.moe/Blog/2024.10.07_Ubuntu_Touch_on_Fairphone_5/Ubuntu_Touch_on_Fairphone_5.html):

✅ WORKS | 📈 WORKS, BUT STILL TESTING | ➖ NOT TESTED YET | ⭕ ISSUES | ❌ NOT WORKING

    ✅ Install
    ✅ Setup
    ✅ Working with German SIM-CARD
    ✅ WiFi (With Network enforced Pi-Hole)
    ✅ Camera (Photo, Video, with and without Flash, Switching between cameras)
    ✅ LTE
    ➖ 5G
    ➖ VoLTE
    ➖ GPS
    📈 Battery Life - Seems to be ok. Not as good as LinageOS but ok.
    ⭕ Heat - The phone is a little hot. IDK. why. Could be the dev build with more logging in the background.
    📈 Performance (Can be a little laggy sometimes, but performance-intensive stuff like streaming 1080p@60fps is working great.)
    📈 SMS
    ✅ CALL (2G? 3G?)
    ✅ FLASH
    ✅ Vibration
    ✅ Screen Brightness (With and without Auto)
    ✅ Proximity
    ✅ Rotation
    ❌ Fingerprint reader (The OS knows it dose not work)
    ⭕ USB-OTG [BUG: USB-OTG Hard Crashes Phone (2.0 WORKS! 3.0+ CABLES CRASH.)]
    ✅ USB-HUB [Keyboard, Mouse and USB-Drive work]
    ✅ USB-AUDIO - Works perfectly... surprisingly.
    ❌ USB-VIDEO [Probably related: "BUG: USB-OTG Hard Crashes Phone"]
    ❌ Waydroid [BUG: Waydroid not working]
    ⭕ NFC [BUG: NFC works but no APP / Setting I found can read anything]
    ⭕ Bluetooth [BUG: Bluetooth is working, but cannot reliably connect to or read nearby devices.]
    ✅ Libertine (Tested with Firefox)

Keneda

@CatWithUT said in More detailed Beta-Testing Report:

Then linking externaly is probably bad to. I will just clone my list here:

Good.
So let say this topic is your testing report topic.
You can edit the title for it to be clearer.

I can merge your other topic with this one too if you're ok.

Thanks for your commitment in testing.

CatWithUT

@Keneda Yes pls do that. Thx I can not find the option to change the Titel

Keneda

@CatWithUT
Nevermind I'll do it ^^
But you shoul be able to do it by editing your first post, using the three dots on bottom right corner of the post.

CatWithUT

@Keneda Oh That is how you do that. Thanks. Also: Thanks for fixing the formating and putting it to the top of the topic.

Keneda

@CatWithUT
You're welcome ^^
Thank you for testing, again

dobey

@Keneda said in Beta Bug-Reports - CatWithCode:

That's maybe the reason for the downvotes.

Indeed, the forum is not a bug tracker, so many threads just to say "X is not working" is spammy. A single "testing progress" thread for a new port is fine I guess, but actual bugs should probably be filed in GitLab so they can be tracked and closed with "Fixes #NNN" in changes to code.

Keneda

@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

RyanAM

@Keneda Device came with android 13, It was ported on halium 11. It works

CatWithUT

@Keneda 13. I read the installer and it sayed install 13 first.

mariogrip

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.

mariogrip

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.

CatWithUT

@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).

CatWithUT

@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

Keneda

@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.

CatWithUT

@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.