Offline
@trashcat said in Call for testing: Google/Huawei Nexus 6P (angler) owners:
@Flohack i originally installed with the helium installer and then reinstalled with the installer and had no problems.
Same here, everything seems to be working fine. Now on devel channel 
Great news to see our device officially promoted into the installer!
Sorry to bump this again, but it would have probably been lost in the original N6P thread now that it is closed. Just pasting from https://forums.ubports.com/post/41423:
I'm not sure whether this is a device specific issue, but one thing I have been experiencing since the beginning with this port is the following:
https://github.com/ubports/ubuntu-touch/issues/1174
In a nutshell, the pictures taken with the camera always have the same orientation relative to the phone, instead being rotated properly relative to the ground by using the reading from the accelerometer.
I know this is more of an annoyance rather than a critical bug... Any known solutions or workarounds?
I'm not sure whether this is a device specific issue, but one thing I have been experiencing since the beginning with this port is the following:
https://github.com/ubports/ubuntu-touch/issues/1174
In a nutshell, the pictures taken with the camera always have the same orientation relative to the phone, instead being rotated properly relative to the ground by using the reading from the accelerometer.
I know this is more of an annoyance rather than a critical bug... Any known solutions or workarounds?
I've been doing some more testing:
After many reboot and test cycles the TTFF has been improving. Now it is more in the order of 5 to 10 mins.
Occasionally, after reboot it would not get a fix at all (waiting at least 30+ mins), with the only solution being a reboot. Maybe related to the bug mentioned by @rocket2nfinity ?
I also tested getting location this morning, having had a successful fix last night and no reboot in between. It only took 2 mins.
To give some more context: I haven't used the GPS much since my initial testing of this port in August (staying at home and all). At the time it worked well as @Flohack described. Recently I tried it again a few times and it was not working (hence my original post). Now I see that after many attempts it is sort of "warming up" and performing better. This is pure speculation from my part, but I suspect there is some kind of caching that helps the GPS get subsequent first fixes faster. Over time, if not used frequently, this information becomes outdated. Maybe this is why there is such thing as AGPS? (which, as far as I understand, is not available in UT).
Anyway, I don't think there is much more to do here. Maybe we should mark this as "solved". Thanks everyone!
I will keep doing some more tests. I'd be happy to help testing if there are any projects that aim to improve the overall performance of GPS on UT.
Some time ago we got a teaser about this:
@flohack said in Call for testing: Google/Huawei Nexus 6P (angler) owners:
just a heads-up we are working now on getting the fingerprint reader done. I can already scan fingerprints, unfortunately I cannot activate the locking right now
Since things are shaping up nicely for this port, I figured I'd ask for an update on this low-priority feature. Also, I'd be glad to help testing if needed.
Hi Wouter,
Thanks for the detailed instructions.
I was able to succesfully build Sensorstatus with clickable and deploy it via ssh. I cannot say the same about sensorfw and crossbuilder though.
I can build and generate the deb files with
crossbuilder --architecture=arm64
but if I attempt to deploy them with the --ssh= argument it fails. It asks for the ssh password several times at the beginning, then it builds everything, and it will ask for the password again at the end, several times. Always fails to accept it.
I have also tried to set up my ssh keys first. This prevents the password prompts, giving instead a wrong password error automatically at the end of the build process.
Any ideas?
If not, perhaps I can instead deploy the deb files manually...
@rocket2nfinity what is the procedure to set anbox up on the N6P?
Some time ago we got a teaser about this:
@flohack said in Call for testing: Google/Huawei Nexus 6P (angler) owners:
just a heads-up we are working now on getting the fingerprint reader done. I can already scan fingerprints, unfortunately I cannot activate the locking right now
Since things are shaping up nicely for this port, I figured I'd ask for an update on this low-priority feature. Also, I'd be glad to help testing if needed.
@jimbusch MTP didn't work for me for a long time either, but it is currently working on devel.
@flohack I can confirm video recording is working now for both cameras!
I can't play the videos on the phone though, had to watch them on the pc.
@flohack @rocket2nfinity Indeed, only the back camera is rotating pictures properly.
Could it have been the Qt 5.12 update?
I just realized now that this problem has been solved (devel). Camera now rotates images properly. I don't know exactly when it happened.
In any case, great work!
@flohack said in GPS not working:
Not that when you close an app with location, GPS will stop so it looses track of all satellites. Thats a privacy feature ^^
About that... it can also be an anti-feature, for instance for the purpose of tracking your sport activities. This point has already been raised before, for example here: https://github.com/ubports/ubuntu-touch/issues/1067
I've been doing some more testing:
After many reboot and test cycles the TTFF has been improving. Now it is more in the order of 5 to 10 mins.
Occasionally, after reboot it would not get a fix at all (waiting at least 30+ mins), with the only solution being a reboot. Maybe related to the bug mentioned by @rocket2nfinity ?
I also tested getting location this morning, having had a successful fix last night and no reboot in between. It only took 2 mins.
To give some more context: I haven't used the GPS much since my initial testing of this port in August (staying at home and all). At the time it worked well as @Flohack described. Recently I tried it again a few times and it was not working (hence my original post). Now I see that after many attempts it is sort of "warming up" and performing better. This is pure speculation from my part, but I suspect there is some kind of caching that helps the GPS get subsequent first fixes faster. Over time, if not used frequently, this information becomes outdated. Maybe this is why there is such thing as AGPS? (which, as far as I understand, is not available in UT).
Anyway, I don't think there is much more to do here. Maybe we should mark this as "solved". Thanks everyone!
I will keep doing some more tests. I'd be happy to help testing if there are any projects that aim to improve the overall performance of GPS on UT.
So apparently the GPS works now, it just takes a loooong time to get a fix, which makes it unusable in practice. Specially since you need to keep the screen on and the app focused while you wait. My experience wasn't like this a few months back when I first tried UT on the NP6... how is it for you guys?
I don't know if it had any effect, but I did a complete reinstall from scratch. I first tried the GPS on android and it took circa 30 mins to get a fix. Then on fresh UT it was more like 20-25 mins. Finally I restored my backed-up userdata and it also worked after some 20 mins. Once there was a first fix, other apps were able to almost immediately (~ 1 min) get location info. Although maybe this was cached info or something?
Btw, the warnings/errors in the output of test_gps that I reported a few days back are still present, so they seem to be harmless.