[Porting] Call for Testers

[j0e]

I can confirm the GPS is working and it takes a while to get the position at least the first time. I used PureMaps. I am still running the first build has been published. Calls are woking fine for me both in and out and swithching audio through capsule/speaker/headphones.
The main issues i came across are just 2:
-bluetooth: i could pair my headphones but the connection is intermittant (while they're connected audio works). I couldn't pair a keybord.
-network switch: when i switch the wifi off or just go out o have to reboot the device to get mobile data working. It works fine the other way round.

[Lakotaubp]

Anyone else with mobile data issues? I cannot enter new APN settings. Well I can enter them but they are not saved.
Edit: After a few attempts I managed to edit one marked as Contract to my settings, so at least I have basic set up.

[j6]

Works
Actors: Manual brightness
Actors: Torchlight
Actors: Vibration
Bluetooth: Driver loaded at startup
Bluetooth: Enable/disable and flightmode works
Bluetooth: Persistent MAC address between reboots
Bluetooth: Pairing with headset works, volume control ok (pairs fine, volume control on headset separate from phone volume)
Camera: Flashlight
Camera: Photo
Camera: Video
Camera: Switch between back and front camera
Cellular: Carrier info, signal strength
Cellular: Data connection
Cellular: Incoming, outgoing calls
Cellular: MMS in, out
Cellular: SMS in, out
Cellular: Change audio routings
Cellular: Voice in calls
Cellular: Switch connection speed between 2G/3G/4G works for all SIMs (works with my sim)
Cellular: Enable/disable mobile data and flightmode works
Endurance: Battery lifetime > 24h from 100%
GPU: Boot into UI
Misc: Battery percentage
Misc: SD card detection and access - only for devices that support it (works when connected with usbc adapter)
Misc: Shutdown / Reboot
WiFi: Driver loaded at startup
WiFi: Enable/disable and flightmode works
WiFi: Persistent MAC address between reboots
Sensors: Automatic brightness
Sensors: Fingerprint reader, register and use fingerprints (Halium 9.0 only)
Sensors: GPS
Sensors: Proximity
Sensors: Rotation
Sensors: Touchscreen
Sound: Earphones detected, volume control
Sound: Loudspeaker
Sound: Microphone
Sound: Loudspeaker volume control
USB: MTP access
sshd
apt
USB keyboard and mouse

Works but sketchy
Misc: Online charging (Green charging symbol, percentage increase in stats etc) (works but no charging symbol)
WiFi: Hotspot can be configured, switched on and off, can serve data to clients (works, doesn't show as active in quick settings when enabled from system settings, had to reboot to connect to wifi after disabling hotspot)
Libertine kinda works (doesn't show any apps as installed in system settings but I was able to install and start a gtk application after several tries).

Doesn't work
Actors: Notification LED
Cellular: Switch preferred SIM for calling and SMS - only for devices that support it (only one sim slot works)
Misc: Offline charging (Power down, connect USB cable, device should not boot to UT) (doesn't work, boots into UT)

Untested
Cellular: PIN unlock
Endurance: No reboot needed for 1 week
GPU: Hardware video decoding
Misc: Anbox patches applied to kernel
Misc: AppArmor patches applied to kernel
Misc: Recovery image builds and works
Misc: Reset to factory defaults
Misc: Wireless charging - only for devices that support it (unsupported)
(Network: NFC - disabled atm due to no middleware)
(USB: ADB access - disabled atm due to no middleware)
USB: External monitor - only for devices that support it (unsupported)

Other
At first when testing with a sim from a mnvo the APN settings were set incorrectly and mobile data didn't work. Editing the APN settings manually was a little weird as @Lakotaubp mentioned above, the changes didn't seem to stick. I didn't try to get it working for very long because using a different sim card from a different provider worked flawlessly without manual intervention.
On the first day after installing, the about page of system settings showed the last update as being on 7/3/73 (time and date were set correctly in the OS). After a day this changed to the correct installation date.
Overall I think this is awesome, it's my first experience with UT and I'm going to try to daily drive it. Thanks to everyone for all the hard work.

[Lakotaubp]

@j6 I agree this is looking really good already. My mobile data was like yours detected incorrectly and I have now edited mms and data but new connections still not working. This is is the same on another device I noticed (but can't remember which just now, age strikes ) I do have notifications however and the button top lefthand side will put the phone into silent mode. Have yet to try vibrate on it's own. It is very quick and smooth though compared to the OP3 and has an on screen keyboard for setting up accounts, so easy now.

[Lakotaubp]

Just out of interest does anyone have the on screen stats and 4G on the mobile signal? Noticied 3G but not 4 yet.

[flohack]

@lakotaubp You can see only L for LTE, and yes, I had that here...

[Lakotaubp]

@flohack Think it was more of a network thing now. It is there but not that often. Thanks

[nfsprodriver]

Fingerprint reader seems to work now with the latest sensorfw changes in the devel channel (auto brightness also fixed).

[flohack]

@nfsprodriver on the 5T? I cannot believe it

[nfsprodriver]

@flohack Oh, there is a difference for the fp readers? Didn't know that. It's working on my OP 5 non T

[flohack]

@nfsprodriver Yes there is a difference which makes it disabled for unlock method selection, no one knows why.

[nfsprodriver]

Is it possible to merge the anbox-halium patches soon? It would be easier to test the latest Waydroid status without the need to flash the self built kernel after a daily devel update. Or are there negative side effects with these patches like power consumption?
Every time I tried to use Waydroid it didn't boot up because of vibrator issues. Is this something to be fixed before the merge?

[flohack]

@nfsprodriver My latest state is we have to wait for Wayland support and 20.04 is that not the case? My information says it needs changes in the rootfs as well...
I have no patches that I could merge therefore.
Please talk with the Waydroid developer Erfan first, I dont want to have a negative user experience with a half-baked Waydroid engine rolled out. That makes no sense. According to his last message its not ready for daily, and thats also my opinion.

[nfsprodriver]

@flohack I see your point. I'll try on with manual flashing and reporting the current state of functionallity here.
Anyway, did you have a look on the merge request in the kernel repo? This is also for the old anbox, which is basically running with this.

[flohack]

@nfsprodriver said in [Porting] Call for Testers:

did you have a look on the merge request in the kernel repo? This is also for the old anbox, which is basically running with this.

I saw it and I need to test it myself first to find out if this works or not. I hope I find time

[Eragon]

Hi, I'm new here, I own a OnePlus 5T.
I want to switch to a real Linux distribution, what's the state of this port ?
I need SMS, MMS, cals, network (LTE, WiFi), audio and Bluetooth.
I can help to test the device, and I'm OK with finding bugs.

[AppLee]

@eragon
You can find the state of a port at http://devices.ubports.com/

[flohack]

@eragon I think all of that should work ^^

[nero355]

@flohack said in [Porting] Call for Testers:

@thomas-k8s yes sorry, there is generally no VoLTE in Ubuntu Touch at the moment, and its very questionable if it will every be fixed, due to custom undocumented vendor applications. All mobile phone projects outside of Android and iOS struggle with that.

Even LineageOS does not support VoLTE on all ports.

BR Florian

I don't understand that one :

• LTE = 4G in general.
• VoLTE has always been optional.

So...

Is it possible to receive calls when connected via 4G or not ?!

My current 4G phone doesn't have VoLTE either...

[Lakotaubp]

@nero355 4G calls in and out = yes