search

ubports / anbox

UT no longer packages Anbox and instead packages Waydroid. See https://gitlab.com/ubports/development/core/packaging/waydroid
GNU General Public License v3.0
22 stars 8 forks source link

BQ M10 HD: Anbox kernel is not installed #34

Open ghost opened 5 years ago

ghost commented 5 years ago

Hi, I want install Anbox in my BQ Aquaris M10 HD (OTA-8) I follow instructions (https://docs.ubports.com/en/latest/userguide/dailyuse/anbox.html#how-to-install). but after write "anbox-tool install" terminal say "Anbox kernel is not installed".

in first step: export CODENAME="cooler" && export PARTITIONNAME="boot"

ec-nebi commented 5 years ago

I confirm the same bug on my BQ Aquaris M10 HD (OTA-8). Flashed as follow and then impossible to install

$ sudo fastboot flash $PARTITIONNAME anbox-boot-$CODENAME.img
> target reported max download size of 134217728 bytes
> sending 'boot' (10868 KB)...
> OKAY [  0.455s]
> writing 'boot'...
> OKAY [  0.505s]
> finished. total time: 0.960s

I started with a "Legacy Android device" and follow the instruction here: http://docs.ubports.com/en/latest/userguide/install.html#install-on-legacy-android-devices

It looks like we are sending the image but that would be directly erased when rebooting. After flashing nothing changed by rebooting. Do we need to use Splashtools?

WolfgangZenner commented 5 years ago

I have the same problem today - is therea time, when it will work?

WolfgangZenner commented 5 years ago

I've just seen, that this issue is for HD, I have an FHD

RobertZenz commented 5 years ago

Same here with an FHD. Flashing the boot image works but does nothing.

JulianGro commented 5 years ago

Same here on M10 HD with OTA-9.

Here is my terminal output: https://gist.github.com/jug007/32c2d8d7f2fe216dd62ff5237f91e010

RobertZenz commented 5 years ago

So...is the whole anbox thing abandoned or did we just pick a bad time? @mariogrip

JulianGro commented 5 years ago

So...is the whole anbox thing abandoned or did we just pick a bad time?

I guess they don't really have anyone working on the M10 if they don't even have an M10 to test. If there is a person in charge of the M10, they might just be busy. Pretty normal stuff in the open source community, I guess.

RobertZenz commented 5 years ago

Pretty normal stuff in the open source community, I guess.

I was more referring to the whole activity of the repository than this single issue. It looks more like nobody is currently working on it.

Flohack74 commented 5 years ago

Its not abandoned, but we have a lot of higher priorities at the moment, which is due to the upcoming Android-free hardware like PINE phone or Librem5. We will evaluate on a later time how anbox will continue, as there are superheavy roadblocks there: hardware access must be shared between Android and UT apps, content exchange etc. TBH I have no idea if we will finde ever solutions for that.

RobertZenz commented 5 years ago

I see and already thought along these lines. I guess me and the others were just wondering what's up with the M10 (FHD) support, as it seems like somebody did find the time to build an image for it, but it's "just" not working.

minibootsmann commented 4 years ago

One year later and still the same issue. Bad luck for me, I bought a "well supported" device for UBPORTS and now I see that all is still work in progress. Very few apps, so I cannot use the tablet the way I intended to do. My last hope was anbox, but now all I can do is waiting for some fortunate coincidence which gives a willing guy enough motivation and resources to add some functionality to this device...

I know this is open source and all is done by volunteers in their spare time. I really appreciate that, but that doesn't change my situation. Even paying money would not really change the situation as one cannot buy spare time...

Flohack74 commented 4 years ago

The problem is that even if the kernel is published as open-source by the manufacturer (BQ and Mediatek in turn), the device tree is not. You will also notice that there is no official Cynaogenmod/LineageOS for those devices (BQ, Meizu) for probably the same reasons. So unless someone makes a working Android build there is little chance that we can ever apply the Anbox patches needed to those kernels. We are basically still using the boot and system images from Canonical, also the recovery. They had probably an NDA with BQ/Meizu, who in turn have an NDA with Mediatek, to be able to build binaries for those devices. Sadly Mediatek is a bad choice for open source efforts. When we say its a well supported device this applies up to the point where we cannot break the rules, and we also wont use unofficial sources patched together from XDA or other Internet places, where we do not know what people did. So even if you find unofficial CM/LOS ROMs for those devices, they are normally below our standards for trust and usability. Sorry to say, but thats the current state, and it probably wont change ever.

minibootsmann commented 4 years ago

Thank you very much for this clarification!

I did not realize that the android device tree is needed for anbox. As the situation with Mediatek and open source remained unsatisfactory, I always tried not to use android devices with such a processor. My naive hope was that for a device, which has full Linux support, all necessary information would be available. Well, now i know better and have do decide whether I keep trying to make this device usable for me or to search for another tablet with better support options.

Bsoupe commented 4 years ago

Any updates with OTA-13? I own a Aquaris M10 FHD, it was on the list of supported devices for Anbox on UBT, but German ubuntuusers forum say it doesn't work with the FHD model too!

Fuseteam commented 3 years ago

can this tested again with ota-16?

ghost commented 3 years ago

I can this week end. I'm now on Android but I can switch on Ubport for test.

ghost commented 3 years ago

Sorry for long time..... I go test this day

ghost commented 3 years ago

can this tested again with ota-16?

Not work:

$ adb shell phablet@ubuntu-phablet:$ sudo reboot -f bootloader [sudo] password for phablet: $ sudo fastboot flash $PARTITIONNAME anbox-boot-$CODENAME.img [sudo] Mot de passe de bourinov : target reported max download size of 134217728 bytes sending 'boot' (10868 KB)... OKAY [ 0.470s] writing 'boot'... OKAY [ 0.505s] finished. total time: 0.976s $ sudo fastboot reboot rebooting...

finished. total time: 0.052s $ rm anbox-boot-$CODENAME.img

phablet@ubuntu-phablet:$ anbox-tool install Anbox has not been enabled for this device. Please consult device maintainer.

edwaleni commented 3 years ago

A couple of things.

  1. Did you see if Anbox runs on current OTA-16 without the patching?
  2. (edit) rephrase - try running the script by replacing the reference calls set by the export

$ sudo fastboot flash $PARTITIONNAME anbox-boot-$CODENAME.img

$PARTITIONNAME should be replaced with the boot partition name unique to your device (ie: boot or bootimg) $CODENAME should be replaced with the name of the system (ie: cooler or frieza)

I am having the same issue and am going to reflash my M10 FHD to stock OTA-16.

ghost commented 3 years ago

1- Anbox does not appear to be present on the tablet with last update. 2 -I'm write at beginning: export CODENAME="cooler" && export PARTITIONNAME="boot" (in my case).

Gplinc commented 3 years ago

Hello, I was wondering what "Anbox has not been enabled for this device. Please consult device maintainer." means? I have a BQ M10 FHD with fresh OTA-17. The tools are there from the start with that message being output after anbox-tool install. Any advice is appreciated. Thanks.

Fuseteam commented 3 years ago

@Gplinc that means the kernel is not ready for anbox please follow the instructions on https://docs.ubports.com/en/latest/userguide/dailyuse/anbox.html