Call for testing: Google/Huawei Nexus 6P (angler) owners
-
@Flohack running 8-cores, the latest system, rootfs, etc.
Camera working including flash, but when flash is used, the device freezes requiring manual reboot. after reboot, the flash photo is in the gallery, intact. Video does not work, but does not crash the camera either
Strange enough, flashlight does not work, even though flash does.
Rotation and all sensors consistently working, smooth as butter.
SSH and MTP mode work. RNDIS works
Still not working - audio in calls, bluetooth, hotspot.
You said anbox was included. I ran the procedure from the docs, still says not in the kernel. I tried to wget the anbox build for angler, it says no kernel for angler. Did I miss something?
-
@rocket2nfinity sorry I did not update the kernel image, since despite the standard Apps like calculator and system settings no other Apps would start. But I can upload the kernel and you can try for yourself.
-
Sorry also for Bluetooth, I need to replace 1 32bit binary with 64bit....
-
im going to try in an hour, however i got a question ,how does it work the gpu with the latest version , it uses some sort of nouveau drivers?,its laggy?, or the videos play niceley and it has acceleration? thanks for the hard work in the community,thumbs up guys you are the best.
-
@Girlycard777 said in Call for testing: Google/Huawei Nexus 6P (angler) owners:
nd it has acceleration? thanks for the hard work in the community,thumbs up guys you are the bes
Hi,
Ubuntu Touch uses the underlying Android drivers, as there is no open-source thingie for Android SoCs (Mostly Qualcomm and Mediatek, they dont publish anything). So, theoretically you can achieve the same performance as with Android.
However, currently our stack does not use HW acceleration in all the areas, probably video playback is the one where you notice this most. But, still its okay.
-
I grepped 'pulse' in var/log/syslog and got this for the time that I was trying to make a phone call:
8 13:48:35 ubuntu-phablet pulseaudio[2626]: [pulseaudio] sink.h: Assertion 'pa_object_refcnt(pa_object_cast(o)) > 0' failed at ./pulsecore/sink.h:306, function pa_sink_assert_ref(). Aborting. Jul 8 13:48:36 ubuntu-phablet pulseaudio[7983]: [pulseaudio] pid.c: Stale PID file, overwriting. Jul 8 13:48:36 ubuntu-phablet pulseaudio[7983]: [pulseaudio] droid-util.c: Requested sample rate 44100 but got 48000 instead. Jul 8 13:48:36 ubuntu-phablet pulseaudio[7983]: [pulseaudio] sink.c: Default and alternate sample rates are the same. Jul 8 13:48:36 ubuntu-phablet pulseaudio[7983]: [pulseaudio] droid-util.c: Requested sample rate 44100 but got 48000 instead. Jul 8 13:48:36 ubuntu-phablet pulseaudio[7983]: [pulseaudio] sink.c: Default and alternate sample rates are the same. Jul 8 13:48:36 ubuntu-phablet pulseaudio[7983]: [pulseaudio] module-droid-discover.c: Device has AudioFlingerglue Jul 8 13:48:36 ubuntu-phablet pulseaudio[7983]: [pulseaudio] droid-util.c: Failed to open output stream: -17 Jul 8 13:48:36 ubuntu-phablet pulseaudio[7983]: [pulseaudio] droid-sink.c: Failed to open output stream. Jul 8 13:48:36 ubuntu-phablet pulseaudio[7983]: [pulseaudio] droid-util.c: Failed to open output stream: -17 Jul 8 13:48:36 ubuntu-phablet pulseaudio[7983]: [pulseaudio] droid-sink.c: Failed to open output stream. Jul 8 13:48:36 ubuntu-phablet kernel: [ 109.700560] pulseaudio[7983]: syscall 389 Jul 8 13:48:36 ubuntu-phablet kernel: [ 109.700597] CPU: 0 PID: 7983 Comm: pulseaudio Not tainted 3.10.73-g45457ef #12 Jul 8 13:48:36 ubuntu-phablet pulseaudio[7983]: [pulseaudio] main.c: Sink sink.primary does not exist. Jul 8 13:48:36 ubuntu-phablet pulseaudio[7983]: [pulseaudio] main.c: Source source.primary does not exist.not sure if this is very helpful for troubleshooting the phone audio issues.
-
This post is deleted! -
where is the link to the arm64 rootfs ??
i found it
https://ci.ubports.com/job/xenial-rootfs-armhf/search/?q=xenial-rootfs-arm64 -
@Girlycard777 don't know if you saw this yet, but helpful when setting up
http://pad.ubports.com/p/nexus-6p-alphatesting -
@user yes is saw it but what i was searching was the arm64, but i found it
-
@Flohack what rootfs did you use? i used this https://ci.ubports.com/job/xenial-rootfs-armhf/search/?q=xenial-rootfs-arm64 and give me bootloop
-
-
@Flohack I'm curious to try it, Anbox, so please do when you get a chance. I had a similar issue with my x86 tablet anbox build, the same fix might work with this one.
-
booting succesfully with arm64 and 8 core , i want to test it ,i like it , Does anyone knows how to configure apt ... when i give apt update and apt upgrade give me some sort of configuration error which wont allow to lock dpkg files etc , with sudo and root acces
-
html antutu benchmark gave 4700 score
surprisingly testing the wifi net speed gave me more bandwidth than android stock (100mb/s) almost 802.11 gibit -
@Girlycard777 apt upgrade is not the way to update the system in UT. UT is locked down for security reasons, click packages being the way to install apps. Both apps and the system are updated via system updates in the settings panel
-
-
my music apps crashes , does anyone knows how to fix it? i tried uninstalling and installing
-
in the future what adreno drivers ye shall be using , i saw that freedreno with libhybris was the target , or you guys will be finnaly using just adaptations of vendor android partition? wayland is compatible?
-
@Girlycard777 The underlying driver for most Android devices will almost always be the original one. There is much too much other stuff thats more important, with a small team you need to be pragmatic: What works works. And it does not matter much what composer we have, be it Wayland or Mir, as long as we have the adaption to the Android API we can use that. That said, the roadmap is not set in stone, but now we need to progress with change to 20.04, Qt upgrade, location and other sensors improvement, making Non-Android phones work etc.
So not much work planned around the Android low level stuff. Its also changing too fast, there is already Android 10.
