• Running app (like Android's Fitotrack)
• Smartwatch connect (like Gadgetbridge)

When I play audio over bluetooth using the music app, the sound quality itself is good but breaks up all the time. When I try to start a podcast using podbird when my bluetooth headphones are connected, the podcast doesn't even start.

Is this just a problem with my Oneplus3, or is this a general problem with UT, and what can I do about it?

Thanks for any help

@luksus Yes, using sudo I van install F-Droid.apk but it doesn't show up in the drawer.

@luksus I installed it an hour ago, and did a reboot, yes.

@luksus

Kernel: OK
System: OK
Enabled: YES
Running: YES

Now I'm confused.

Since Waydroid is not (easily) available for my OnePlus 3, I installed Anbox using the instructions at https://docs.ubports.com/en/latest/userguide/dailyuse/anbox.html#run-anbox-installer.

However, when I try to install an app using adb install, it sits waiting for devices, and then times out.

adb devices on my phone responds with:

List of devices attached
emulator-5558   offline

I tried adb start-server but I can't seem to get it running. Also, when I start one of the default apps, all I get is a black screen.

What do I do to start the adb server?

@luksus I actually bought a Pinephone, but the OnePlus 3 is so much faster and also has more memory. The only thing the pinephone has over it is the hardware kill switches.

I will try and install anbox and see if if performs. Thanks!

@luksus Interesting. Is there a way to get the right kernel or should I run anbox?

@arubislander Same result.

I run UT on a OnePlus 3 (stable channel). I have installed waydoird using:

$ sudo ubports-qa install xenial_-_android9_-_wayland
$ wget -O - https://github.com/Anbox-halium/anbox-halium/raw/lineage-17.1/scripts/install.sh | bash

Afterwards, I tried to run it using:

$ sudo /home/anbox/run-container.sh

This fails after:

modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/3.18.31-halium-gac6f57d5/modules.dep.bin'
modprobe: FATAL: Module binder_linux not found in directory /lib/modules/3.18.31-halium-gac6f57d5
modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/3.18.31-halium-gac6f57d5/modules.dep.bin'
modprobe: FATAL: Module ashmem_linux not found in directory /lib/modules/3.18.31-halium-gac6f57d5
mount: unknown filesystem type 'binder'
ERROR: Binder and ashmem nodes not found!

After this nothing happens for a second or two, then the screen goes black and the phone becomes unresponsive except for the power button, which allows me to reboot the phone.

Since apt doesn't work on UT, how do I install the required modules?

@fp2andfp3-user When I start waydroid as indicated, I see this output:

phablet@ubuntu-phablet:~$ sudo /home/anbox/run-container.sh
[sudo] password for phablet: 
modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/3.18.31-halium-gac6f57d5/modules.dep.bin'
modprobe: FATAL: Module binder_linux not found in directory /lib/modules/3.18.31-halium-gac6f57d5
modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/3.18.31-halium-gac6f57d5/modules.dep.bin'
modprobe: FATAL: Module ashmem_linux not found in directory /lib/modules/3.18.31-halium-gac6f57d5
mount: unknown filesystem type 'binder'
ERROR: Binder and ashmem nodes not found!

After this the screen goes black and the phone becomes unresponsive except for the power button, which allows me to reboot the phone.

How do I install the required modules?

@kriszie mount without arguments will show anything that is mounted, and where. So if it doesn't show /system than it means that partition isn't mounted, so you don't have to unmount it. Sadly, UT doesn't have lsblk, my usual go-to for finding out what devices there are, mounted or otherwise.

I had the same problem and decided to try and solve it by formatting both /data and /system. TWRP provides buttons to change the filesystem type for any partition, but afaik not to format any partition except /data. So using the UI I changed the filesystem of /data to ext4 and formatted it.

Then I went into a shell ($ adb shell on my PC but TWRP has an internal shell too) and unmounted /system to format it:

~ # mount

Note the block device /system is mounted on, then:

~ # umount /system/
~ # mkfs.ext2 /dev/block/<device>

(Yes, that's ext2, not 4, but it won't matter)

You can of course use the shell to format /data (and /cache) the same way if you want.

After that, I could install UT by not ticking the boxes for first install and wipe device.

I would be interested if others also succeed using this solution.