Anbox Installation issue
-
After flashing the kernel patch in the instructions, the Anbox installer says device is not flashed.
Please advise.
Set the export command as noted and downloaded the frieza image file.
Device is in Developer Mode.edwaleni@edwaleni-R2700:~$ adb shell
phablet@ubuntu-phablet:~$ sudo reboot -f bootloader
[sudo] password for phablet:
edwaleni@edwaleni-R2700:~$ sudo fastboot flash boot anbox-boot-frieza.img
target reported max download size of 134217728 bytes
sending 'boot' (11308 KB)...
OKAY [ 0.316s]
writing 'boot'...
OKAY [ 0.528s]
finished. total time: 0.844s
edwaleni@edwaleni-R2700:~$ sudo fastboot reboot
rebooting...finished. total time: 0.102s
edwaleni@edwaleni-R2700:~$ adb shell
phablet@ubuntu-phablet:~$ anbox-tool install
Anbox kernel is not installed! Please flash this first!
phablet@ubuntu-phablet:~$ -
@edwaleni
Since OTA 16 (your device has OTA 16 installed right?), you no longer have to flash kernel.
As your device has anbox patchs if i refer to device page : https://devices.ubuntu-touch.io/device/frieza/Only thing you should have to do, i believ is running from terminal device :
anbox-tool installSee this thread : https://forums.ubports.com/topic/5769/anbox-in-ota-16-release-candidate/22?_=1619142277010
-
The instruction page states:
*Some devices require you to install a custom Linux kernel to use Anbox. These devices are:
Meizu Pro 5 (codename: turbo, name of the boot partition: bootimg)
BQ M10 HD (codename: cooler, name of the boot partition: boot)
BQ M10 FHD (codename: frieza, name of the boot partition: boot)*
I am running OTA-16 (20210305)
-
@edwaleni So i believed wrong :grinning_face_with_sweat:
EDIT : and well, it seems a long time issue (last posts are from you maybe?) : https://github.com/ubports/anbox/issues/34
-
Actually that is not me.
And I have to apologize for not searching these forums in more detail. I certainly am not posting just to make people go look up stuff for me.
I had flashed my M10 FHD to Android from Ubuntu years ago and now am coming back via UB Ports. So I am quite new to this specific arena.
I don't think I will be as "touchy" as those users are, but I am sure I am seeking the same kind of functionality they are, to expand their productivity from click apps to include Android apps.
So when I loaded UB Ports and being based on Linux, I started looking at containers, kvm and other types ways to do this.
The alternate ROM community for Android with the M10 FHD is all over the place where most will boot, but various little details won't work. Ubuntu and UB Ports thus far are where everything works, but the ecosystem appears small.
It seems being a Mediatek ARM based tab is causing a lot of developer grief in alternate ROM's.
Getting back to Anbox.....I will do more research on what you have provided and if needed will reset it back to stock and start over.
-
@edwaleni said in Anbox Installation issue:
Actually that is not me.
That could have be as he got the exact same issue :grinning_face_with_smiling_eyes:
Anyway as you can see, i also have a mediatek based device, one of the legacy canonical one like yours, but still, a pain in the... bottom... for devs.
I switched to ubport not so long time ago too, untill then i was still on last canonical uTouch OTA.
Wish you luck with anbox.
