Pixel 3a issues

matteo

Hi dear Pixel 3a owners,
I wanted only to check with you a couple of issues I noticed while I'm daily driving it, out of the autobrightness not working, which is a known issue haunting all Halium9 devices. Just to be clear, I'm on UT devel channel.

When in a call, the screen remains on when I put it close to the ear and the proximity sensor doesn't seem to be effective, although it isn't in a general failure since I double checked with sensorStatus app and it works; is it confirmed proximity sensor not working in a call?
Vibration, even if enabled in Settings, doesn't seem to work while the phone is getting a call ringing with sound. Is it also confirmed misbehavior?

I still need to check if bluetooth is working: I was able to paire the phone with my car but no clue yet if it is an actual tethering or just as clumsy as I read somewhere for different devices. A positive note I didn't expect is related to the hotspot working seamless out of the box

rik

Note that the above problems seem resolved now (autobrightness now working, screen turning off when near face, vibration working, and bluetooth pairing).

matteo

@rik thank you, I've been following all those issues and opened bug reports on Github which were very soon tackled by Alfred. The future seems bright for the Pixel 3a and this is now my daily driver phone.

Albator

Tried Unav and it looks like there's no GPS sync. Unav stay at 'Wait for GPS'.

Lakotaubp

@albator If it is working on the Pixel give it at least 45 mins for a first fix and set the screen switch off to never. Best to do it otside too or at least by a window.

Albator

@lakotaubp Thanks, i'll give it a try.

Clint

Could this have something to do with the problem we're seeing? https://github.com/ubports/ubuntu-touch/issues/1837 If so, it's not obvious to me there is a solution. @UniSuperBox posted "Funny enough, you can get another shell into the device in this state. Running sudo reboot there causes the Pixel 3a to boot into the selected mode, but the Volla Phone does not." but I don't know how to use this information to complete the install. BTW: I tried using UBports 0.8.8 ... but I ran into the same problem.