On 04/16/2017 03:35 AM, Reg Tiangha wrote: > On 04/16/2017 01:44 AM, Vít Šesták wrote: >> Yes, other apps are working after reboot. Maybe I broke it with pm. >> >> * `pm` command in Android seems to be broken – it segfaults and it seems >> that no app can be started then (though other will continue working) >> * Calculator app works, Settings app works, E-Mail app seems to work, too.. >> Maybe the Gallery 3D just has some 3D acceleration issues, but other apps >> are OK. >> * adb lolcat and adb shell are your friends, it shows what is happening >> * adb shell might be needed before adb lolcat >> * don't worry about timeouts – app window can be shown even after timeout >> * Somewhat laggy and CPU hog – maybe related to OpenGL. >> * Not sure how to install apps. I've tried adb install FDroid.apk and it >> passed, but it does not seem to be installed. >> * The desktop files sometimes disappear. >> >> Maybe we should turn off GPU rendering in developer options. Unfortunately, >> I cannot enable developer mode in Settings app. It seems we sould have to >> disable ro.kernel.qemu.gles and qemu.gles in /system/build.prop, but I am >> not sure if this is easy. The build.prop might be a RO part of the snap. >> There is a similar file in /data, not sure what we can override there. >> >> I am not sure if Anbox utilizes OpenGL. Maybe some lowlevel approach >> bypasses the mesa library, which can decide to use llvmpipe. >> >> Regards, >> Vít Šesták 'v6ak' >> > You're right; everything in the > snap/anbox/common/app-data/applications/anbox directory disappears for > some reason. No idea what to do about that. However, you can still > launch stuff from the command line if you remember the commands from the > ..desktop files. When they reappeared again after a VM reboot, I copied > them all to another directory just so I could see the launch commands > when I needed them. > > I've installed stuff with FDroid and adb and it does work; .desktop > files do get generated in that directory. But as you said, they > disappear sometimes. > > I managed to enable Developer Mode, but clicking on it does nothing. > Clicking on it from the side menu just kicks you back to the main > Settings screen. The Anbox people say this is a slimmed down version of > Android 7.1.1; is it possible that Developer Mode wasn't compiled in? > > I installed Build.prop editor from F-Droid and tried to set > ro.kernel.qemu.gles and qemu.gles to 0 using that. I'm not sure if it > did anything, but after a reboot, Gallery 3D doesn't even start. I don't > know how to revert what I changed though to see if it really had an > effect (can't find a way to delete those entries; long pressing does > nothing and I don't know where it saves its data to) but maybe that's a > route to go if it does work. Make sure to back up the VM first, though. > > Does this Android image allow for root? If so, it might be possible to > install a text editor that works with root to try and see if editing > /system/build.prop persists across a reboot. But I too am now out of > time again at the moment. > > One last idea: The Anbox docs say it's possible to use your own Android > image file. So maybe it's possible to build one that doesn't have the gl > stuff enabled. That could be another thing to try as a last resort, > especially if build.prop is read-only. >
One last thing: I tried to install Busybox from F-Droid, and while it said that /data had about 4.6GB free, /system has 0GB, which implies to me that /system is either read-only or really is just an image file that you can't modify. System: * device: Anbox * android: 7.1.1 * architecture: x86_64 Free space: * /data: 4.6G * /system: 0 Latest BusyBox: * version: v1.25.1-meefik * applets: 334 items * size: 1665860 bytes * md5: 146921ec514d4828748a226dbed2fc25 Installed BusyBox: * not installed -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/ocveba%24mhd%241%40blaine.gmane.org. For more options, visit https://groups.google.com/d/optout.
