ubports / anbox Goto Github PK

1. Please check that no similar bug is already reported. Have a look on the list of open bugs at https://github.com/anbox/anbox/issues

2. Make sure you are running the latest version of Anbox before reporting an issue. Update snap to latest: snap refresh --devmode --edge anbox

3. Make sure you have debug logs enabled:
   sudo snap set anbox debug.enable=true

4. Reproduce the error while debug logs enabled.

5. Run the anbox logs collection utility and attach the tar file.
   sudo /snap/bin/anbox.collect-bug-info

6. ** Please paste the result of anbox system-info below:**

[please paste printout of `anbox system-info` here]

Please describe your problem:

What were you expecting?:

Additional info:

** Please paste the result of anbox system-info below:**

phablet@ubuntu-phablet:~$ anbox system-info
version: local-/bin/sh: 1: git: not found
cpu:
  arch:
  brand:
  features:
os:
  name: Ubuntu
  version: 16.04.7 LTS (Xenial Xerus)
  snap-based: false
kernel:
  version: Linux version 3.4.0+ (ubuntu@M4Master) (gcc version 4.9.3 (Ubuntu/Linaro 4.9.3-13ubuntu2) ) #3 SMP PREEMPT Fri Sep 25 11:53:44 UTC 2020
  binder: true
  ashmem: true
graphics:
  egl:
    vendor: Android
    version: 1.4 Android META-EGL
    extensions:
      - EGL_KHR_get_all_proc_addresses
      - EGL_ANDROID_presentation_time
      - EGL_KHR_image
      - EGL_KHR_image_base
      - EGL_KHR_lock_surface
      - EGL_KHR_gl_texture_2D_image
      - EGL_KHR_gl_texture_cubemap_image
      - EGL_KHR_gl_renderbuffer_image
      - EGL_KHR_fence_sync
      - EGL_KHR_create_context
      - EGL_EXT_create_context_robustness
      - EGL_ANDROID_image_native_buffer
      - EGL_KHR_wait_sync
      - EGL_ANDROID_recordable
      - EGL_HYBRIS_native_buffer2
      - EGL_HYBRIS_WL_acquire_native_buffer
      - EGL_WL_bind_wayland_display
  gles2:
    vendor: n/a
    vendor: OpenGL ES 2.0 ((null))
    extensions:
      - n/a

Please describe your problem:
With the help of @UniversalSuperBox I was able to prepare Modified boot.img for N7 2013 (deb)
Modified Kernel code of deb/flo: https://github.com/ameyagokhale/ubuntu_kernel_xenial/tree/flo

When I try to execute anbox-tool install I get this:

phablet@ubuntu-phablet:~$ anbox-tool install
/home/phablet/anbox 100%[===================>] 207.16M  4.32MB/s    in 45s
start: Job failed to start
start: Unknown job: anbox-session


^CTraceback (most recent call last):
  File "/usr/bin/anbox-tool", line 329, in <module>
    enable()
  File "/usr/bin/anbox-tool", line 192, in enable
    waitForAnbox()
  File "/usr/bin/anbox-tool", line 180, in waitForAnbox
    time.sleep(1)
KeyboardInterrupt

Anbox-tool status shows this:

phablet@ubuntu-phablet:~/anbox-data$ anbox-tool status
Kernel: OK
System: OK
Enabled: YES
Running: NO

Output of lxc-console

phablet@ubuntu-phablet:~$ sudo lxc-console -ndefault -P /home/phablet/anbox-data/containers -t0
default is not running

Due to which adb devices shows nothing:

phablet@ubuntu-phablet:~$ adb devices
List of devices attached

phablet@ubuntu-phablet:~$

Already tried rebooting but that didn't help.

Also tried disabling/enabling anbox:

phablet@ubuntu-phablet:~$ anbox-tool disable
Anbox is alredy disabled

phablet@ubuntu-phablet:~$ sudo anbox-tool enable
start: Job failed to start
start: Unknown job: anbox-session

^CTraceback (most recent call last):
  File "/usr/bin/anbox-tool", line 329, in <module>
    enable()
  File "/usr/bin/anbox-tool", line 192, in enable
    waitForAnbox()
  File "/usr/bin/anbox-tool", line 180, in waitForAnbox
    time.sleep(1)
KeyboardInterrupt

phablet@ubuntu-phablet:~$ sudo anbox-tool status
Kernel: OK
System: OK
Enabled: YES
Running: NO

phablet@ubuntu-phablet:~$ sudo anbox-tool disable
stop: Unknown job: anbox-session
stop: Unknown instance:
Anbox is now disabled

phablet@ubuntu-phablet:~$ 

What were you expecting?:

The container should be visible in adb devices (anbox should work) and I should be able to install and use Android Apps.

Additional info:

I would like to be able to access the / sdcard directory to see all the videos, images, and other files that I have stored, I was googling and I saw that some use sshfs to do it when they emulate Android
https://askubuntu.com/questions/893090/how-do-i-mount-my-androids-filesystem-over-the-network-with-sshfs

Xiaomi Redmi 7 anbox offline ,music & gallery black screen,webview don't work.
channel download stable & devel

I would like the "navigation bar" to be enabled, most of all the "back" and "menu" buttons (como en Sailfish OS), for old and new applications that still use them and are not handled with gestures

SYSTEM

• Oneplus One (bacon)
• OTA-11 16.04

Hi Everyone,

I was able to successfully install anbox on my Oneplus One (Ubuntu 16.04). I was also able to pull apk's from my android device and push them to my ubuntu-touch device. I tried the following two methods of installation:

• adb install my_app.apk

 sudo mv my_app.apk ~/anbox-data/data
$ sudo lxc-console -ndefault -P /home/phablet/anbox-data/containers -t0
$ cd ../data && pm install my_app.apk

Both methods successfully install my_app.apk and it shows up in the app scope once I refresh it (with a swipe down). However, when I launch the newly installed apps, they just hang on the opening. For instance, spotify just shows the spotify logo. Hopper just shows a white background.

Perhaps these were not installed successfully, but from the instructions I could find, these were the recommended ways. I'm aware that anbox is extremely experimental at this point so perhaps these apps just don't work. In that case, has anyone been able to successfully install and deploy an android app on a OPO? If so which one?

I was curious to know, in addition to the above, if there were another way to install android apps in anbox? Thanks in advance.

Good day to all!

I do have two Nexus-5 ubuntu touch devices, anbox was working on both of
them.

Yesterday i ran a system upgrade on one of them, a complete reinstall on the other (because of
other issues). The ubuntu touch version now is 16.04.

I then flashed the latest hammerhead anbox image onto the devices, as usual.
As a result all network functionality was lost, the phones could not connect to either the
wifi-network or function as a telephone, they did not even recognise the SIM-card.

I tried sveral reinstallations on one of the phones, both ubuntu stable and edge, always with the
same result.

They work normally, since i reinstalled ubuntu touch - albeit without anbox, of course.

What now?

Rainer

In system settings, it only let's me view more, than Airplane mode, VPN, and Network settings reset.

Rather than letting me connect and use my WiFi.

Currently no way of knowing if a messaging app has messages waiting or notifications.

This is possible an anti-feature and even could be not possible, but thought I would log it anyway since it's likely to come up.

Please describe your problem:
I run anbox on UT device lavender dev build. I try to install yandex music app and just after few moments phone is freezing and reboot the graphical environment.

What were you expecting?:
Anbox work well and not freeze all system, if problem appear it just crash the app not entire system.

version: local-/bin/sh: 1: git: not found
cpu:
 arch:
 brand:
 features:
os:
 name: Ubuntu
 version: 16.04.5 LTS (Xenial Xerus)
 snap-based: false
kernel:
 version: Linux version 3.4.0-Sultan-CAF (mariogrip@mariogrip-elem) (gcc version 4.8 (GCC) ) #2 SMP PREEMPT Sat Aug 11 19:42:30 CEST 2018
 binder: true
 ashmem: true
graphics:
 egl:
   vendor: Android
   version: 1.4 Android META-EGL
   extensions:
     - EGL_KHR_get_all_proc_addresses
     - EGL_ANDROID_presentation_time
     - EGL_KHR_image
     - EGL_KHR_image_base
     - EGL_KHR_lock_surface
     - EGL_KHR_gl_texture_2D_image
     - EGL_KHR_gl_texture_cubemap_image
     - EGL_KHR_gl_renderbuffer_image
     - EGL_KHR_fence_sync
     - EGL_KHR_create_context
     - EGL_EXT_create_context_robustness
     - EGL_ANDROID_image_native_buffer
     - EGL_KHR_wait_sync
     - EGL_ANDROID_recordable
     - EGL_HYBRIS_native_buffer2
     - EGL_HYBRIS_WL_acquire_native_buffer
     - EGL_WL_bind_wayland_display
 gles2:
   vendor: n/a
   vendor: OpenGL ES 2.0 ((null))
   extensions:
     - n/a

Please describe your problem:
Cannot copy from Ubuntu Touch and paste within any Anbox app.

What were you expecting?:
Was expecting a shared clipboard to make the integration of Anbox apps and Ubuntu Touch more seamless.

Additional info:
Without out this, it can get very frustrating for a user using a Password Manager with an array of long passwords.

1. Please check that no similar bug is already reported. Have a look on the list of open bugs at https://github.com/anbox/anbox/issues

2. Make sure you are running the latest version of Anbox before reporting an issue. Update snap to latest: snap refresh --devmode --edge anbox

3. Make sure you have debug logs enabled:
   sudo snap set anbox debug.enable=true

4. Reproduce the error while debug logs enabled.

5. Run the anbox logs collection utility and attach the tar file.
   sudo /snap/bin/anbox.collect-bug-info

6. ** Please paste the result of anbox system-info below:**

[please paste printout of `anbox system-info` here]

phablet@ubuntu-phablet:~$ anbox system-info
version: local-/bin/sh: 1: git: not found
cpu:
arch:
brand:
features:
os:
name: Ubuntu
version: 16.04.5 LTS (Xenial Xerus)
snap-based: false
kernel:
version: Linux version 3.4.0-cyanogenmod-g2669fa0 (jenkins@ubports-build) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Fri Jan 4 02:24:40 CET 2019
binder: true
ashmem: true
graphics:
egl:
vendor: Android
version: 1.4 Android META-EGL
extensions:
- EGL_KHR_get_all_proc_addresses
- EGL_ANDROID_presentation_time
- EGL_KHR_image
- EGL_KHR_image_base
- EGL_KHR_lock_surface
- EGL_KHR_gl_texture_2D_image
- EGL_KHR_gl_texture_cubemap_image
- EGL_KHR_gl_renderbuffer_image
- EGL_KHR_fence_sync
- EGL_KHR_create_context
- EGL_EXT_create_context_robustness
- EGL_ANDROID_image_native_buffer
- EGL_KHR_wait_sync
- EGL_ANDROID_recordable
- EGL_HYBRIS_native_buffer2
- EGL_HYBRIS_WL_acquire_native_buffer
- EGL_WL_bind_wayland_display
gles2:
vendor: n/a
vendor: OpenGL ES 2.0 ((null))
extensions:
- n/a

Please describe your problem:
I noticed that there are two copies of the .desktop files:

one set (a): .local/share/applications/
another set (b): .local/share/applications/anbox/

Causes some software to read both and double the icons:
https://gitlab.com/ubports/apps/sprint/issues/2

What were you expecting?:

One set of icons. Maybe newer version of anbox have moved the icons, but did not remove the old location.

Additional info:

• Device: Arale (but surely device-agnostic)
• Channel: Devel
• Build: Any recent ones

Steps to reproduce

As described in this sister issue:

#24

Following the standard guide to install Anbox, with the bespoke Arale image shared in this forum thread:

https://forums.ubports.com/topic/1679/how-to-anbox-for-meizu-mx4-arale

This was working fine initially. I installed APKs for stores including FDroid and Yalp and a few random apps. I then tried to install Amazon Kindle*. This was evidently a bad idea because it destabilised Anbox and therefore Ubuntu Touch. As I relate in the other issue, it is currently unknown how to undo this mistake and therefore in hindsight Kindle should not have been installed.

*Note: Just today, I installed the snap-based Anbox on Ubuntu 18.04 on a laptop for testing. I tried to install Amazon Kindle here too via Yalp (spoofing the laptop as a Fairphone 2), but it said it was not compatible for my (emulated) phone. Now I'm not sure if that means for Anbox on an x86-64 snap-based system, or for Anbox on any system, but given it completely hobbled Anbox on my MX4, I suspect it might be the latter.

Expected behavior

Kindle is evidently a problematic app for Anbox on any system. It can be safely assumed that there are other apps which would also be deemed problematic, whether they aren't compatible with the emulated environment, if they have malware or if the required Google Play Services or hardware sensor requirements aren't available, etc. It seems that the snap-based Anbox system for desktop Linux distros have warnings and even outright prevent these apps from being installed. This should also be present on Ubuntu Touch's Anbox implementation (and could vary from an outright block for malware and fully incompatible apps, to a warning that e.g. the GPS the app depends on might not (or definitely is not, depending on the hardware) be available on your phablet). Not sure how this would work, but at minimum it should mirror the way it's done on Yalp for snap-based implementations (and ditto on other free app stores).

Actual behavior

This is not the case. Yalp allowed me to install Kindle with no warnings or blocks, and now my Anbox installation is hobbled. This might be dangerous for other users if system-destabilising apps are allowed to be freely installed (the Android/Anbox system setting of "Allow installation of apps from unknown sources" nonwithstanding, because with Anbox we are forced to rely on this and not the Google Play Store for our apps). Even granting that users should employ common sense and not install apps flagged up online as malware, without a warning or prevention for benign (that is, non-malware, but nevertheless system-destabilising) apps such as Kindle, the system can still become hobbled and therefore it makes sense for UT's Anbox implementation to include the same safety measures as in other implementations (such that the responsibility for installing apps carefully is not solely in the user's hands/discretion).

Logfiles and additional information

Where would I find relevant logfiles for this issue? And remember, if I need to have Anbox enabled to obtain these files, the short time the OS can run whilst it is enabled might even prevent me from being able to obtain them in time.

Please describe your problem:
There's no on-screen keyboard

What were you expecting?:
On-screen keyboard so that you can type things into android apps.

Additional info:

Add support for native ubuntu touch keyboard

I keep getting a error message, it says "Invalid APK file". I have tried multiple files and always get the same message. I have tried using the whole file name as it shows up in my downloads folder. The one file had () in it, then it would give a syntax error. Which is confusing as that is in the name. Is there a special format that the name needs to be in? or does the file need to be extracted first?

Here are the full file names I've tried
com.waze_4.80.60.601-1022751_minAPI21(arm64-v8a,armeabi-v7a)(nodpi)_apkmirror.com.apk.download
Waze GPS Maps Traffic Alerts Live Navigation_v4.80.0.1_apkpure.com.apk

I'm using a Volla Phone, I know it is not on the list of compatible phones, but anbox seems to have installed correctly.

Is it possible to run anbox on arale (meizu mx4)? It's so sad that I only have one supported device which cannot run anbox....

Hello,
it isn' t possible to install Android apps on FHD10 tablet.
Getting this messages:

It isn't possible to write in the directory: no space left on device.
Thank you :-)

Device: FP2
Channel: 16.04/RC (2018-W48)
Anbox-Version: don't know (did "anbox-tool upgrade" today)

Problem description:
Running anbox version to find out the version to enter above, I get the following error:

anbox local-/bin/sh: 1: git: not found

What were you expecting?:
I was expecting to get some version number output.

Additional info:
I made the root fs read-write and installed git, but that doesn't help, the problem remains.

• Device: Arale
• Channel: Devel
• Build: Any recent ones

Steps to reproduce

Following the standard guide to install Anbox, with the bespoke Arale image shared in this forum thread:

https://forums.ubports.com/topic/1679/how-to-anbox-for-meizu-mx4-arale

This was working fine initially. I installed APKs for stores including FDroid and Yalp and a few random apps. I then tried to install Amazon Kindle*. This was evidently a bad idea because it destabilised Anbox and therefore Ubuntu Touch. Android apps would not run, and on every boot, I would have about 1-2 minutes before a restart was forced. My only recourse was to rush to run anbox-tool disable. This stopped the problem, but of course also stopped Anbox and did not allow for full triage of the problem. I tried to do a full rm -rf *indle* to purge the APK and all of it's installed folders; this did not help. Today, I attempted a reflash of the 16.04 devel image (no wipe) to try to purge Anbox, and also ran sudo apt remove anbox-tool && sudo apt purge anbox-tool. I then repeated the kernel flash and installation procedure.

*Note: Just today, I installed the snap-based Anbox on Ubuntu 18.04 on a laptop for testing. I tried to install Amazon Kindle here too via Yalp (spoofing the laptop as a Fairphone 2), but it said it was not compatible for my (emulated) phone. Now I'm not sure if that means for Anbox on an x86-64 snap-based system, or for Anbox on any system, but given it completely hobbled Anbox on my MX4, I suspect it might be the latter.

Expected behaviour

After a (presumably) full purge of all things Anbox, reflash of Ubports, Anbox kernel flash and Anbox reinstallation, the former problem would vanish at some point and Anbox would no longer be non-functional as the assumption is that the system is starting from fresh with regards to the program.

Actual behaviour

The expected behaviour does not occur. At no point does the critical problem of a hobbled Anbox installation become undone. Surprisingly, not even with the Anbox kernel flash. Therefore, it is imperative for Ubports to either document ways from a system admin perspective or via some uninstaller tool to entirely wipe all traces of Anbox from the phablet, at all levels, including kernel. This should permit a fresh installation to be done exactly as the original first installation was done, and then the user can continue using Anbox (armed with the knowledge and experience to avoid installing certain APKs, in this case Amazon Kindle) without issues. This is especially important for when Anbox is intended to be entirely stable and becomes a part of the system image for a future UT OTA. If this cannot be done, the only remaining option is to completely wipe and reinstall Ubuntu Touch, which for obvious reasons is very undesirable.

Logfiles and additional information

Where would I find relevant logfiles for this issue? And remember, if I need to have Anbox enabled to obtain these files, the short time the OS can run whilst it is enabled might even prevent me from being able to obtain them in time.

There were some recent reports by other people that the FP2 is not supported by anbox. See https://forums.ubports.com/topic/3968/anbox-not-supported-on-fp2 and https://forum.fairphone.com/t/ubuntu-touch-with-threema-on-anbox-where-are-the-files/53768/6

In fact I found a recent change that I think is the reason for this problem:
e117ed1

That commit added a .lower() on the device name in

["getprop", "ro.product.device"]).strip().decode("utf-8").lower()

This is then checked against https://cdimage.ubports.com/anbox-images/devices.json
But there the FP2 is listed in upper case.

I followed the ubports instructions to install Anbox on Ubuntu Touch, Nexus 5. What are the steps to uninstall it?

Thank you

Link the folders / sdcard or / storage / sdcard1 or / data / media / 0 to access the data that matters most and not to the anbox system

I followed the instructions here, flashed the frieza kernel to the device and when I ran the anbox-tool install command it printed out

Anbox has not been enabled for this device. Please consult device maintainer.

Retried multiple times and it always did the same. What am I doing wrong?

Device: PRO 5
Channel: 16.04/rc
Anbox Version: 2018-09-16 whatever is most recent.

It seems when you have a picture into the Gallery, and you open the Gallery it crash.

Device: FP2
Channel: 16.04/devel
Anbox Version: 2018-09-16 whatever is most recent.

When running anbox apps, the device gets quite hot. It seems to be requiring a lot of power. App performance is a bit laggy, especially on touch input. Not sure if it's related or not.

Hello. Hello.
On a Meizu pro5 in 16.04 dev
I'm trying to install anbox according to the tutorial:
https://docs.ubports.com/fr/latest/userguide/dailyuse/anbox.html?highlight=anbox
But I have errors when loading and therefore I can't install it.
see below:

Could someone help me?

Anbox should build a bridge to retrieve the Android app notifications on UT

1. Please check that no similar bug is already reported. Have a look on the list of open bugs at https://github.com/anbox/anbox/issues

2. Make sure you are running the latest version of Anbox before reporting an issue. Update snap to latest: snap refresh --devmode --edge anbox

3. Make sure you have debug logs enabled:
   sudo snap set anbox debug.enable=true

4. Reproduce the error while debug logs enabled.

5. Run the anbox logs collection utility and attach the tar file.
   sudo /snap/bin/anbox.collect-bug-info

6. ** Please paste the result of anbox system-info below:**

[please paste printout of `anbox system-info` here]

Please describe your problem:

What were you expecting?:

Additional info:

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"

We still have a some commits that's not upstreamed

These are:

• Mir rootless more
• Add support for /dev/anbox-binder
• Add option to choose binder with envar
• Scaling things
• Various small patches

There is also ubports specific things, like init files, debian packaging and scripts, we might want to move these out to a submodule

If I switch my phone (UT 16.04 2018-10-10 dev channel) to vertical (with WhatsApp running), anbox does not resize the app screen. The app is located unresized on the left side, with a black area at the right.

Hello,

I just installed Anbox on a fresh install of Ubports for Nexus 5 (16.04 stable channel).
Then I installed the latest stable apk of Waze (4.49.1.2) but it keeps crashing at start-up.

At the beginning I had a pop-up ask to grant access to localization that I was unable to accept (it had no effect when clicking) but I went around this allowing directly rights to Waze in anbox settings.

Now I'm passed that, but Anbox is looping a couple of time at Waze start-up, the last display shows the lower bar of Waze, but then it crashes definitively.
I tried several times, after reboot as well: same behavior.

I hope there is a way to make Waze work on Anbox, it is really the only application that is missing for me on Ubuntu Touch. Previously I had a Nexus 4 with dual boot to get it, but it is no more recommended now (no OTA update).

I think it is easy and systematic to reproduce but let me know if you need any more data from me.

Thanks in advance for your support, and thanks again for the great work done on Ubports and Anbox, coming from an old Canonical version of Ubuntu Touch, I can see a huge progress, keep going that way :)

RIght now the anbox-tool is cli only, and we would need a gui application to do the same tasks (and more)

It needs to be able to:

• Install anbox container
• Update anbox container
• Remove anbox
• Disable / Enable anbox
• Install android apks/apps
• Remove android apps
• List all android apps

Extra functions:

• Clear data/apps
• Bind mount folders bi-direct

This should be implemented with a dbus api on the anbox daemon side to handle the different function, then a gui applications should use that dbus api.

library "libgui.so" wasn't loaded and RTLD_NOLOAD prevented it
version: local-/bin/sh: 1: git: not found
cpu:
  arch:  
  brand: 
  features: 
os:
  name: Ubuntu
  version: 16.04.6 LTS (Xenial Xerus)
  snap-based: false
kernel:
  version: Linux version 4.4.144-g9f246a1 (jenkins@ubports-build) (gcc version 4.9 20150123 (prerelease) (GCC) ) #1 SMP PREEMPT Tue Mar 24 11:13:32 CET 2020
  binder: true
  ashmem: true
graphics:
  egl:
    vendor: Android
    version: 1.4 Android META-EGL
    extensions:
      - EGL_KHR_get_all_proc_addresses
      - EGL_ANDROID_presentation_time
      - EGL_KHR_swap_buffers_with_damage
      - EGL_ANDROID_create_native_client_buffer
      - EGL_ANDROID_front_buffer_auto_refresh
      - EGL_KHR_image
      - EGL_KHR_image_base
      - EGL_KHR_lock_surface
      - EGL_KHR_gl_texture_2D_image
      - EGL_KHR_gl_texture_3D_image
      - EGL_KHR_gl_texture_cubemap_image
      - EGL_KHR_gl_renderbuffer_image
      - EGL_KHR_reusable_sync
      - EGL_KHR_fence_sync
      - EGL_KHR_create_context
      - EGL_KHR_surfaceless_context
      - EGL_EXT_create_context_robustness
      - EGL_ANDROID_image_native_buffer
      - EGL_KHR_wait_sync
      - EGL_ANDROID_recordable
      - EGL_KHR_partial_update
      - EGL_KHR_create_context_no_error
      - EGL_KHR_mutable_render_buffer
      - EGL_EXT_yuv_surface
      - EGL_EXT_protected_content
      - EGL_HYBRIS_native_buffer2
      - EGL_HYBRIS_WL_acquire_native_buffer
      - EGL_WL_bind_wayland_display
  gles2:
    vendor: Qualcomm
    vendor: OpenGL ES 2.0 (OpenGL ES 3.2 [email protected] (GIT@8209866, I528a81912f)
    extensions:
      - GL_OES_EGL_image
      - GL_OES_EGL_image_external
      - GL_OES_EGL_sync
      - GL_OES_vertex_half_float
      - GL_OES_framebuffer_object
      - GL_OES_rgb8_rgba8
      - GL_OES_compressed_ETC1_RGB8_texture
      - GL_AMD_compressed_ATC_texture
      - GL_KHR_texture_compression_astc_ldr
      - GL_KHR_texture_compression_astc_hdr
      - GL_OES_texture_compression_astc
      - GL_OES_texture_npot
      - GL_EXT_texture_filter_anisotropic
      - GL_EXT_texture_format_BGRA8888
      - GL_OES_texture_3D
      - GL_EXT_color_buffer_float
      - GL_EXT_color_buffer_half_float
      - GL_QCOM_alpha_test
      - GL_OES_```depth24
      - GL_OES_packed_depth_stencil
      - GL_OES_depth_texture
      - GL_OES_depth_texture_cube_map
      - GL_EXT_sRGB
      - GL_OES_texture_float
      - GL_OES_texture_float_linear
      - GL_OES_texture_half_float
      - GL_OES_texture_half_float_linear
      - GL_EXT_texture_type_2_10_10_10_REV
      - GL_EXT_texture_sRGB_decode
      - GL_OES_element_index_uint
      - GL_EXT_copy_image
      - GL_EXT_geometry_shader
      - GL_EXT_tessellation_shader
      - GL_OES_texture_stencil8
      - GL_EXT_shader_io_blocks
      - GL_OES_shader_image_atomic
      - GL_OES_sample_variables
      - GL_EXT_texture_border_clamp
      - GL_EXT_multisampled_render_to_texture
      - GL_OES_shader_multisample_interpolation
      - GL_EXT_texture_cube_map_array
      - GL_EXT_draw_buffers_indexed
      - GL_EXT_gpu_shader5
      - GL_EXT_robustness
      - GL_EXT_texture_buffer
      - GL_EXT_shader_framebuffer_fetch
      - GL_ARM_shader_framebuffer_fetch_depth_stencil
      - GL_OES_texture_storage_multisample_2d_array
      - GL_OES_sample_shading
      - GL_OES_get_program_binary
      - GL_EXT_debug_label
      - GL_KHR_blend_equation_advanced
      - GL_KHR_blend_equation_advanced_coherent
      - GL_QCOM_tiled_rendering
      - GL_ANDROID_extension_pack_es31a
      - GL_EXT_primitive_bounding_box
      - GL_OES_standard_derivatives
      - GL_OES_vertex_array_object
      - GL_EXT_disjoint_timer_query
      - GL_KHR_debug
      - GL_EXT_YUV_target
      - GL_EXT_sRGB_write_control
      - GL_EXT_texture_norm16
      - GL_EXT_discard_framebuffer
      - GL_OES_surfaceless_context
      - GL_OVR_multiview
      - GL_OVR_multiview2
      - GL_EXT_texture_sRGB_R8
      - GL_ARB_texture_barrier
      - GL_KHR_no_error
      - GL_EXT_debug_mark
      - GL_OES_EGL_image_external_essl3
      - GL_OVR_multiview_multisampled_render_to_texture
      - GL_EXT_buffer_storage
      - GL_EXT_blit_framebuffer_params
      - GL_EXT_clip_cull_distance
      - GL_EXT_protected_textures
      - GL_EXT_shader_non_constant_global_initializers

Please describe your problem:
When trying to open an app and play music, no sound is comming out despite sound working with native apps.

What were you expecting?:
Hearing the audio :)

Additional info:
The fix describe by @c4pp4 in the uports' forum post (Sony Xperia X (suzu/F5121 & F5122)) resolve the issue.

The issue has been marked as resolved in anbox#904 but looks like the issue is still here.

Fix proposed
Replace the /system/etc/media_codecs.xml file in this image by this one http://dpaste.com/2H2CP58

<?xml version="1.0" encoding="utf-8" ?>
<!-- Copyright (C) 2012 The Android Open Source Project

     Licensed under the Apache License, Version 2.0 (the "License");
     you may not use this file except in compliance with the License.
     You may obtain a copy of the License at

          http://www.apache.org/licenses/LICENSE-2.0

     Unless required by applicable law or agreed to in writing, software
     distributed under the License is distributed on an "AS IS" BASIS,
     WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
     See the License for the specific language governing permissions and
     limitations under the License.
-->

<!--
<!DOCTYPE MediaCodecs [
<!ELEMENT Include EMPTY>
<!ATTLIST Include href CDATA #REQUIRED>
<!ELEMENT MediaCodecs (Decoders|Encoders|Include)*>
<!ELEMENT Decoders (MediaCodec|Include)*>
<!ELEMENT Encoders (MediaCodec|Include)*>
<!ELEMENT MediaCodec (Type|Quirk|Include)*>
<!ATTLIST MediaCodec name CDATA #REQUIRED>
<!ATTLIST MediaCodec type CDATA>
<!ELEMENT Type EMPTY>
<!ATTLIST Type name CDATA #REQUIRED>
<!ELEMENT Quirk EMPTY>
<!ATTLIST Quirk name CDATA #REQUIRED>
]>

There's a simple and a complex syntax to declare the availability of a
media codec:

A codec that properly follows the OpenMax spec and therefore doesn't have any
quirks and that only supports a single content type can be declared like so:

    <MediaCodec name="OMX.foo.bar" type="something/interesting" />

If a codec has quirks OR supports multiple content types, the following syntax
can be used:

    <MediaCodec name="OMX.foo.bar" >
        <Type name="something/interesting" />
        <Type name="something/else" />
        ...
        <Quirk name="requires-allocate-on-input-ports" />
        <Quirk name="requires-allocate-on-output-ports" />
        <Quirk name="output-buffers-are-unreadable" />
    </MediaCodec>

Only the three quirks included above are recognized at this point:

"requires-allocate-on-input-ports"
    must be advertised if the component does not properly support specification
    of input buffers using the OMX_UseBuffer(...) API but instead requires
    OMX_AllocateBuffer to be used.

"requires-allocate-on-output-ports"
    must be advertised if the component does not properly support specification
    of output buffers using the OMX_UseBuffer(...) API but instead requires
    OMX_AllocateBuffer to be used.

"output-buffers-are-unreadable"
    must be advertised if the emitted output buffers of a decoder component
    are not readable, i.e. use a custom format even though abusing one of
    the official OMX colorspace constants.
    Clients of such decoders will not be able to access the decoded data,
    naturally making the component much less useful. The only use for
    a component with this quirk is to render the output to the screen.
    Audio decoders MUST NOT advertise this quirk.
    Video decoders that advertise this quirk must be accompanied by a
    corresponding color space converter for thumbnail extraction,
    matching surfaceflinger support that can render the custom format to
    a texture and possibly other code, so just DON'T USE THIS QUIRK.

-->

<MediaCodecs>
    <Decoders>
        <MediaCodec name="OMX.google.mp3.decoder" type="audio/mpeg">
            <Limit name="channel-count" max="2" />
            <Limit name="sample-rate" ranges="8000,11025,12000,16000,22050,24000,32000,44100,48000" />
            <Limit name="bitrate" range="8000-320000" />
        </MediaCodec>
        <MediaCodec name="OMX.google.amrnb.decoder" type="audio/3gpp">
            <Limit name="channel-count" max="1" />
            <Limit name="sample-rate" ranges="8000" />
            <Limit name="bitrate" range="4750-12200" />
        </MediaCodec>
        <MediaCodec name="OMX.google.amrwb.decoder" type="audio/amr-wb">
            <Limit name="channel-count" max="1" />
            <Limit name="sample-rate" ranges="16000" />
            <Limit name="bitrate" range="6600-23850" />
        </MediaCodec>
        <MediaCodec name="OMX.google.aac.decoder" type="audio/mp4a-latm">
            <Limit name="channel-count" max="8" />
            <Limit name="sample-rate" ranges="7350,8000,11025,12000,16000,22050,24000,32000,44100,48000" />
            <Limit name="bitrate" range="8000-960000" />
        </MediaCodec>
        <MediaCodec name="OMX.google.g711.alaw.decoder" type="audio/g711-alaw">
            <Limit name="channel-count" max="1" />
            <Limit name="sample-rate" ranges="8000-48000" />
            <Limit name="bitrate" range="64000" />
        </MediaCodec>
        <MediaCodec name="OMX.google.g711.mlaw.decoder" type="audio/g711-mlaw">
            <Limit name="channel-count" max="1" />
            <Limit name="sample-rate" ranges="8000-48000" />
            <Limit name="bitrate" range="64000" />
        </MediaCodec>
        <MediaCodec name="OMX.google.vorbis.decoder" type="audio/vorbis">
            <Limit name="channel-count" max="8" />
            <Limit name="sample-rate" ranges="8000-96000" />
            <Limit name="bitrate" range="32000-500000" />
        </MediaCodec>
        <MediaCodec name="OMX.google.opus.decoder" type="audio/opus">
            <Limit name="channel-count" max="8" />
            <Limit name="sample-rate" ranges="48000" />
            <Limit name="bitrate" range="6000-510000" />
        </MediaCodec>
        <MediaCodec name="OMX.google.raw.decoder" type="audio/raw">
            <Limit name="channel-count" max="8" />
            <Limit name="sample-rate" ranges="8000-96000" />
            <Limit name="bitrate" range="1-10000000" />
        </MediaCodec>
        <MediaCodec name="OMX.google.flac.decoder" type="audio/flac">
            <Limit name="channel-count" max="8" />
            <Limit name="sample-rate" ranges="1-655350" />
            <Limit name="bitrate" range="1-21000000" />
        </MediaCodec>
        <MediaCodec name="OMX.google.mpeg2.decoder" type="video/mpeg2">
            <!-- profiles and levels:  ProfileMain : LevelHL -->
            <Limit name="size" min="16x16" max="1920x1088" />
            <Limit name="alignment" value="2x2" />
            <Limit name="block-size" value="16x16" />
            <Limit name="blocks-per-second" range="1-244800" />
            <Limit name="bitrate" range="1-20000000" />
            <Feature name="adaptive-playback" />
        </MediaCodec>
        <MediaCodec name="OMX.google.gsm.decoder" type="audio/gsm">
            <Limit name="channel-count" max="1" />
            <Limit name="sample-rate" ranges="8000" />
            <Limit name="bitrate" range="13000" />
        </MediaCodec>
        <MediaCodec name="OMX.google.mpeg4.decoder" type="video/mp4v-es">
            <!-- profiles and levels:  ProfileSimple : Level3 -->
            <Limit name="size" min="2x2" max="352x288" />
            <Limit name="alignment" value="2x2" />
            <Limit name="block-size" value="16x16" />
            <Limit name="blocks-per-second" range="12-11880" />
            <Limit name="bitrate" range="1-384000" />
            <Feature name="adaptive-playback" />
        </MediaCodec>
        <MediaCodec name="OMX.google.h263.decoder" type="video/3gpp">
            <!-- profiles and levels:  ProfileBaseline : Level30, ProfileBaseline : Level45
                    ProfileISWV2 : Level30, ProfileISWV2 : Level45 -->
            <Limit name="size" min="2x2" max="352x288" />
            <Limit name="alignment" value="2x2" />
            <Limit name="bitrate" range="1-384000" />
            <Feature name="adaptive-playback" />
        </MediaCodec>
        <MediaCodec name="OMX.google.h264.decoder" type="video/avc">
            <!-- profiles and levels:  ProfileHigh : Level52 -->
            <Limit name="size" min="2x2" max="4080x4080" />
            <Limit name="alignment" value="2x2" />
            <Limit name="block-size" value="16x16" />
            <Limit name="block-count" range="1-32768" /> <!-- max 4096x2048 equivalent -->
            <Limit name="blocks-per-second" range="1-1966080" />
            <Limit name="bitrate" range="1-48000000" />
            <Feature name="adaptive-playback" />
        </MediaCodec>
        <MediaCodec name="OMX.google.hevc.decoder" type="video/hevc">
            <!-- profiles and levels:  ProfileMain : MainTierLevel51 -->
            <Limit name="size" min="2x2" max="4096x4096" />
            <Limit name="alignment" value="2x2" />
            <Limit name="block-size" value="8x8" />
            <Limit name="block-count" range="1-196608" /> <!-- max 4096x3072 -->
            <Limit name="blocks-per-second" range="1-2000000" />
            <Limit name="bitrate" range="1-10000000" />
            <Feature name="adaptive-playback" />
        </MediaCodec>
        <MediaCodec name="OMX.google.vp8.decoder" type="video/x-vnd.on2.vp8">
            <Limit name="size" min="2x2" max="2048x2048" />
            <Limit name="alignment" value="2x2" />
            <Limit name="block-size" value="16x16" />
            <Limit name="block-count" range="1-16384" />
            <Limit name="blocks-per-second" range="1-1000000" />
            <Limit name="bitrate" range="1-40000000" />
            <Feature name="adaptive-playback" />
        </MediaCodec>
        <MediaCodec name="OMX.google.vp9.decoder" type="video/x-vnd.on2.vp9">
            <Limit name="size" min="2x2" max="2048x2048" />
            <Limit name="alignment" value="2x2" />
            <Limit name="block-size" value="16x16" />
            <Limit name="block-count" range="1-16384" />
            <Limit name="blocks-per-second" range="1-500000" />
            <Limit name="bitrate" range="1-40000000" />
            <Feature name="adaptive-playback" />
        </MediaCodec>
    </Decoders>
    <Encoders>
        <MediaCodec name="OMX.google.aac.encoder" type="audio/mp4a-latm">
            <Limit name="channel-count" max="6" />
            <Limit name="sample-rate" ranges="8000,11025,12000,16000,22050,24000,32000,44100,48000" />
            <!-- also may support 64000, 88200  and 96000 Hz -->
            <Limit name="bitrate" range="8000-960000" />
        </MediaCodec>
        <MediaCodec name="OMX.google.amrnb.encoder" type="audio/3gpp">
            <Limit name="channel-count" max="1" />
            <Limit name="sample-rate" ranges="8000" />
            <Limit name="bitrate" range="4750-12200" />
            <Feature name="bitrate-modes" value="CBR" />
        </MediaCodec>
        <MediaCodec name="OMX.google.amrwb.encoder" type="audio/amr-wb">
            <Limit name="channel-count" max="1" />
            <Limit name="sample-rate" ranges="16000" />
            <Limit name="bitrate" range="6600-23850" />
            <Feature name="bitrate-modes" value="CBR" />
        </MediaCodec>
        <MediaCodec name="OMX.google.flac.encoder" type="audio/flac">
            <Limit name="channel-count" max="2" />
            <Limit name="sample-rate" ranges="1-655350" />
            <Limit name="bitrate" range="1-21000000" />
            <Limit name="complexity" range="0-8"  default="5" />
            <Feature name="bitrate-modes" value="CQ" />
        </MediaCodec>
        <MediaCodec name="OMX.google.h263.encoder" type="video/3gpp">
            <!-- profiles and levels:  ProfileBaseline : Level45 -->
            <Limit name="size" min="176x144" max="176x144" />
            <Limit name="alignment" value="16x16" />
            <Limit name="bitrate" range="1-128000" />
        </MediaCodec>
        <MediaCodec name="OMX.google.h264.encoder" type="video/avc">
            <!-- profiles and levels:  ProfileBaseline : Level41 -->
            <Limit name="size" min="16x16" max="2048x2048" />
            <Limit name="alignment" value="2x2" />
            <Limit name="block-size" value="16x16" />
            <Limit name="block-count" range="1-8192" /> <!-- max 2048x1024 -->
            <Limit name="blocks-per-second" range="1-245760" />
            <Limit name="bitrate" range="1-12000000" />
            <Feature name="intra-refresh" />
        </MediaCodec>
        <MediaCodec name="OMX.google.mpeg4.encoder" type="video/mp4v-es">
            <!-- profiles and levels:  ProfileCore : Level2 -->
            <Limit name="size" min="16x16" max="176x144" />
            <Limit name="alignment" value="16x16" />
            <Limit name="block-size" value="16x16" />
            <Limit name="blocks-per-second" range="12-1485" />
            <Limit name="bitrate" range="1-64000" />
        </MediaCodec>
        <MediaCodec name="OMX.google.vp8.encoder" type="video/x-vnd.on2.vp8">
            <!-- profiles and levels:  ProfileMain : Level_Version0-3 -->
            <Limit name="size" min="2x2" max="2048x2048" />
            <Limit name="alignment" value="2x2" />
            <Limit name="block-size" value="16x16" />
            <!-- 2016 devices can encode at about 10fps at this block count -->
            <Limit name="block-count" range="1-16384" />
            <Limit name="bitrate" range="1-40000000" />
            <Feature name="bitrate-modes" value="VBR,CBR" />
        </MediaCodec>
        <MediaCodec name="OMX.google.vp9.encoder" type="video/x-vnd.on2.vp9">
            <!-- profiles and levels:  ProfileMain : Level_Version0-3 -->
            <Limit name="size" min="2x2" max="2048x2048" />
            <Limit name="alignment" value="2x2" />
            <Limit name="block-size" value="16x16" />
            <!-- 2016 devices can encode at about 8fps at this block count -->
            <Limit name="block-count" range="1-3600" /> <!-- max 1280x720 -->
            <Limit name="bitrate" range="1-40000000" />
            <Feature name="bitrate-modes" value="VBR,CBR" />
        </MediaCodec>
    </Encoders>
</MediaCodecs>

Not really sure what it does, but tested on my device (Xperia X) and it resolve the issue. May be further test is needed ?

as OpenStore you can install the .clicks, it occurred to me when downloading WhatsApp.apk from the official website and click on the file manager to install and it came out as a message that OpenStore could not install it.

1. Please check that no similar bug is already reported. Have a look on the list of open bugs at https://github.com/anbox/anbox/issues

2. Make sure you are running the latest version of Anbox before reporting an issue. Update snap to latest: snap refresh --devmode --edge anbox

   • I get bash: snap: command not found. I installed anbox yesterday using https://docs.ubports.com/en/latest/userguide/dailyuse/anbox.html

3. Make sure you have debug logs enabled:
   sudo snap set anbox debug.enable=true

   • I get bash: snap: command not found

4. Reproduce the error while debug logs enabled.

5. Run the anbox logs collection utility and attach the tar file.
   sudo /snap/bin/anbox.collect-bug-info

6. ** Please paste the result of anbox system-info below:**

[please paste printout of `anbox system-info` here]

Please describe your problem:
When an app I use opens a webview, the webview crashes.

Steps to reproduce:

1. Install Husky (https://f-droid.org/en/packages/su.xash.husky/) and open it
2. It asks you for an instance, give ilja.space[1] (you can use any pleroma or mastodon instance, this is the one I use) and press the "login with pleroma" button
3. Now a webview will open to an oauth loginscreen on the instance, but the webview crashes. Husky keeps running, but since the webview needed for oauth crashes, I can't log in.

What were you expecting?:
To log in and use the app 🙃

Additional info:

This is on a FP2 running Ubuntu 16.04 (2021-W10)

[1]

Device: PRO 5
Channel: 16.04/rc
Anbox Version: 2018-09-16 whatever is most recent.

Hi Marius,
i have found out something when i startup my Pro 5 into the morning it seems something is doing things in the background and eat a lot of memory of the system, as scrolling go verry slow and not smooth like normoly i dont know if that would be a bug or not.

I have found out when you let be the Pro 5 for 10 mins then it runs and scroll again like it has to be.

BTW: I have the same Android apps also on my FP2 and on the FP2 i dont have this issue. About getting hot on FP2 i dont have that also not.

The open source application Yalp (which lets you download Google Play apps) crashes