Posts made by stanwood

@libremax I'm glad to confirm that BT music player does perfectly work on both systems (Ford Sync + Seat media).
Sound's just perfect.
Notice: "Unknown artist + unknown track" are displayed on both screens. But this doesn't really matter to me.

So, to resume: On both systems:

Working:

. BT initial pairing
. Auto pairing
. Contacts synchronization
. Coverage signal shown on the car screen
. Name of the device well displayed
. Outgoing / incoming calls
. Vocal command
. In car microphone + High speaker
. Phone volume adjustment
. Music via Bluetooth on the car radio
. Auto swap in call mode

Not working:

. Battery status display
. In music mode: Displays the track being played
. Phone calls: Loud background noise covering much of the speaker's voice (recipient hears well)

Hope I've been this time clearer on my description

@libremax I meant, Bluetooth communication (incoming, outgoing calls) technically works...
So next step I'll try the BT music player on those devices.

I confirm that Bluetooth works on my both cars (Ford Sync + Seat media system) using Nexus 5 OTA-14. But there's an awful high-pitched background noise making the speaker's words almost inaudible. (on both systems) On the other hand, my interlocutor can hear me correctly.
All features are working well except the battery which is displayed as empty. I didn't try to hear my music via Bluetooth on those systems.

@nocomp Unfortunately the fix has been postponed to OTA-15: https://github.com/orgs/ubports/projects/24

However, the previously mentioned .deb file plugin works like a charm

@antonyj Indeed, do not download the Anbox image on the Nexus 5. It is already pre-installed by default. Doing so might creating bugs.

Just start here:
sudo mount -o rw,remount /
sudo apt update
sudo apt install anbox-ubuntu-touch android-tools-adb
anbox-tool install
exit

If you have an error message telling you an insufficient memory in /var, you can try as following:

sudo mount -o rw,remount /
sudo rm -r /var/cache/apt # delete the apt cache; frees space on system image
sudo tune2fs -m 0 /dev/loop0 # space reserved exclusively for root user on system image set to zero
sudo apt update # recreate apt cache to install Anbox and adb
sudo apt install anbox-ubuntu-touch android-tools-adb
sudo mount -o ro,remount /
exit

@maldukhn Don't know if it's related to your bug, but did you first install ADB and Fasboot on your PC? (sudo apt-get install adb && sudo apt-get install fastboot). Thoses packages are needed to install Ubuntu Touch on Android devices.

@MixMac Here we go! https://github.com/orgs/ubports/projects/24#column-11303039

Good new, project has been moved to « To do » in OTA-15 section.

@LRV Great Thank you.

@MixMac Unfortunately not. But it’s integrated in the OTA-15 Github « nice to have » section...

@domubpkm No, I installed Anbox on an experimental basis and tried a few Android apps. But didn't use Firefox as Morph is really fine for me. But I guess you can install Firefox not using Anbox but with Libertines. (easier way)

@haltriumph That's weird indeed. Try do the same process one more time. Also, check on your Google account that your contacts are still in the primary folder. Indeed, you'll find "Contacts", "Frequent contacts" and, right down the list: "Other contacts"... Sometimes, Google do upgrade it's interface and contacts may be moved into another folder ("Other contacts" in my case).

I have encountered the same problem on Ubuntu desktop a few days ago. I solved it by deleting my Google account, restart device and log back again.

@tgv34 Ok, so you might resize your memory partition dedicated to Anbox as follow:

sudo mount -o rw,remount /
sudo rm -r /var/cache/apt
sudo tune2fs -m 0 /dev/loop0
sudo apt update
sudo apt install anbox-ubuntu-touch android-tools-adb
sudo mount -o ro,remount /
exit

It should work fine after this.

@LRV Weird, OTA-13 did not change anything concerning Android kernels, that are already installed in the Nexus 5 Ubuntu Touch image.

However, since Anbox touches the root of the system image, it must be reinstalled after each OTA update:

sudo mount -o rw,remount /
sudo apt update
sudo apt install anbox-ubuntu-touch android-tools-adb
anbox-tool install
exit

Than re-install your .apk apps as described above. It should work.

EDIT: Do not load Anbox cd-image as it is already charged in the Nexus 5 by default...

@LRV Hi, if Anbox is already and correctly installed on your N5, you first need to download your apps in .APK file. You will find a lot of them here: https://apkcombo.com

Once your app is downloaded, open your terminal and type "cd Downloads", than type: "adb install /home/phablet/Downloads/my-app.apk" (replace "my-app.apk" with the exact name of your apk file)
Than type "exit".

Got it! Your app will appear on your home screen

Indeed, performing phone calls via bluetooth devices is still very random on UT. But situation is gradually improving....

@Tellina According to latest Volla phone development statement, phone calls with Bluetooth headset is still "to be done".
https://github.com/HelloVolla/ubuntu-touch-beta-tests/wiki/High-level-epic-overview-for-Ubuntu-Touch-port

However I have no idea on how Volla will send the future porting upgrades to the Volla phone community (Via UBports OTAs or through another way?...)

It's a known issue currently.
It should be fixed in next OTA-14.
In the meantime, you can try this workaround: (worked perfectly well for me as well as dozen users)

. Start to enable the access of "less secured apps" in your Google account. Than run as following:

1. From your device, download this plugin: https://github.com/rubencarneiro/account-plugins/releases
2. Open the terminal application (tap on ENTER key after each following command)
3. Type: cd Downloads
4. Type: sudo -s
5. Type: sudo mount -o remount,rw /
6. Type: sudo dpkg -i account-plugin-google_0.15.0ubports1local.1586944513_all.deb
7. Type: cd
8. Type: exit
9. Reboot your device
10. Open settings => accounts => select Google
11. Enter your e-mail address
12. Enter your password
13. Without enlarging the screen with your fingers, select: "Allow all actions"

Here you should be well connected to your Google account, which will automatically sync your calendar & contacts on your device

@wolfie Don't know about rooting FP2 before installing UT. But normally if stock ROM includes latest factory images & firmwares, it should work as described above. I guess

@wolfie Did you well activated developer mode as well as enabling USB debugging? Also your PC needs ADB and Fastboot.
Than reboot in bootloader (if needed type oem unlock at the connection). Than run the installer. Thanks to let me know.