@WillemHexspoor sorry been gone for work the past two weeks. Yes I flashed the correct version both android 9 and ut 16.04/20.04. I've since flashed android 12 and gave the phone to my son and am waiting to purchase another phone but the two I bought were listed as unlocked G020C models and both received were Verizon G020A models. I specified which model I wanted and it had a sticker on the front as G020C but Google label on box was G020A and had Verizon sim. Contacted seller, returned, and was told I would get correct but got a different device with same G020A package. Waiting for that return to process and find a different seller now but it's just weird that it worked on my device previously when I tried it before.

Hi,

just to let you know this problem has been solved for me by upgrading to 20.04 base (OTA-3). I had to re-enable developer mode after the upgrade.

For some reason device is weirdly named by lsusb, but transfering files works again, adb shell too.

@Peter-Gamma scrcpy is a Java tool, pretty sure that's not going to work for us. Plus, it revolves exclusively around Android frameworks which we also lack.

@jojumaxx Please leave the "text box 1 -> show" or put this block to the end. Because the first "show" leads to an update of the screen which will kill the value in the "text box" (without 1) 🙂

@maceda said in Bricked BQ Aquaris M10 when installing:

I'll try to migrate it to the last version as soon as I have some experience with that.

Let us know how it goes! Personally I'm not comfortable installing anything if it can´t be done with the installer.

@augi Welcome to the forums.

You can, but it would mean remounting the root filesystem read/write, modifying your /etc/hosts file and then remounting the root filesystem read-only again.

Also your changes might be overwritten / reverted when you update the OS via the Settings (never use apt unless you know what you are doing)

The uAddBlock app in the OpenStore works in this way.

@YangTegap if it is stuck at the bootloader unlocked screen, all is not lost. It looks like you were not on the correct Stock ROM. The device has to be on Android 9 for UT to install. Go to XDA- developers forum and search for the correct ROM and you can flash it through fastboot.

If the device sticks at dm-verity, it usually means the battery is on its way out.

Link to XDA forum here.

Flash back to Android 9 and set it up, then start the UT install again.

@arubislander Thank you so much....that worked!

Thank you both.
I've figured out what the issue is.
The Installer for MacOS has been compiled for Intel processors.
It does not work with the new M1 chip.
Either due to incompatibility with the new chip, or Rosetta is unable to work via USB Debugging/ADB for some reason.
When I tried to install using an old Macbook Air with an Intel processor, then the installation worked.

@djjonas13 said in Vaio TL10:

Estou querendo colocar em um Tablet Vaio TL10, o Ubuntu Touch, ele suporta?

"I want to put Ubuntu Touch on a Vaio TL10 Tablet, does it support it?"

No, that is not a supported device. You can see which devices are supported on the device page.

And please post in English in these forums, because that is the language that is spoken here. Thank you!

@arubislander Thank you!

@s710 I downloaded the Whattsapp Web app from the online OpenStore using Morph to find and download it. I then installed it on my OP6 UBports (20.04) phone. It works after a fashion, it has not been updated for a while (April 23). It is hard to get it to adapt to the phone screen. I would probably work on a "as necessary" basis....but not really suitable for regular daily use - that is just my opinion and I have only tried it on my phone.....but it does actually work.

@MrT10001, my deep respect! It worked!

Thank you so much!

@MrT10001 Thanks for the tip, much appreciated.

@PublicLewdness If you have got to Recovery, erase (format) the DATA partition and try again. It is common to say the device is unsupported in the Installer if you have the device at Fastboot. Just manually select it from the devices drop down box.

@DPITTI

Yes miatoll support wireless display on the devel channel as I pointed out in my first replay. This feature was implemented about month ago on the focal port. It is also available on the xenial port from long time.

@domubpkm

Hmmm... that's unfortunate. Though under Xenial (on my Nexus 5), i at least received a notification error. So i knew someone tried to send me something.

The problem now is i don't even get an error. So I won't ever know that a group message was ever attempted. And i can't ask the sender to send individually if i don't know that they've tried to send me something.

So this is a bit of a pickle... Hmmmm.

-Fizz

@ancientsounds

Another experiment with USB audio

Trying to work out how to automatically switch to USB-C when I plug in the headphones (rather than switching manually as previously discussed, by typing on the command line).

pacmd load-module module-udev-detect

works, partly: that is, it will detect the headphones when plugged in, and shows “Usb speakers” when turning the volume up or down. BUT playing music using the Music app doesn't work, i.e. no sound comes out. So manual switching is still necessary when using the Music app.