~ceo_of_programming

Trackers

~ceo_of_programming/dummy

Last active a month ago

#154 Android problems: emulators are now x86; example has glitch a month ago

Comment by ~ceo_of_programming on ~eliasnaur/gio

It seems, that attached files are ignored? They are here: device log emulator log

I forgot to delete the previous message after clicking on reply.

#154 Android problems: emulators are now x86; example has glitch a month ago

Comment by ~ceo_of_programming on ~eliasnaur/gio

The emulator is Android 10; API 30; x86. The device is a Motorola Condor (Moto-e) with Android 7. Go version is 1.14.4 on Debian amd64.

On the emulator logs, I noticed complains about missing OpenGL support and "Unexpected CPU variant for X86 using defaults: x86". Note the capital "X". It also complained about missing instructions, probably because of the ISA mismatch:

Mismatch between dex2oat instruction set features to use (ISA: X86 Feature string: -ssse3,-sse4.1,-sse4.2,-avx,-avx2,-popcnt) and those from CPP defines (ISA: X86 Feature string: ssse3,-sse4.1,-sse4.2,-avx,-avx2,-popcnt) for the command line:

The SSE instruction family is used for vector processing, so I suspect that might be the reason why OpenGL is not working. The device version does not complain about OpenGL not working.

Logs attached. The emulator log is obnoxiously large, if your text editor can't open it, try emacs or 'cat log.txt | egrep "kitchen"'.

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Sunday, August 9, 2020 4:24 PM, ~eliasnaur outgoing@sr.ht wrote:

On Sat Aug 8, 2020 at 02:07, ~ceo_of_programming wrote:

The android

sdk only emulates versions after 7 (nogaut) on x86, I assume the binaries generated are for arm because they crash on the emulator.

gogio generates binaries for all supported architectures, and I use the Android emulator all the time without issue. Please provide details (android version, x86 or x86_64, Gio program) and more importantly, any crash notices from adb logcat.

Running on a real device

works but the demo "kitchen" flashes the screen after every step of the "loading bar widget". After it "loads" the flashing stops but the entire UI is very laggy.

Unfortunately I'm not yet experienced enough with

go to pinpoint where to make the fixes.

That's unfortunate. Which device? Anything interesting in adb logcat? The flickering sounds similar to the ChromeOS issue fixed by

https://gioui.org/commit/e381ff40d66b, but I assume you're using at least that version. I can't explain the lagginess.

Overall the

project seems very cool, also great choice of hosting.

Thank you.


View on the web: https://todo.sr.ht/~eliasnaur/gio/154#comment-13422

#32 Sourcehut Pain Points a month ago

Comment by ~ceo_of_programming on ~eliasnaur/gio

I was greatly surprised to find gio on source hut. I really like the ability to interact through email, possibly without creating an account. I avoid interacting with projects hosted on github since they were acquired by microsoft, I've met many others that do the same.

On the matter of source hut being "hard" to use: I had difficulties with github as a novice. For some time I would just give up on anything hosted on github because I couldn't understand/find the clone button. Sourceforge on the other hand had a big and nice download button.

Give time to time, email is a very low entry barrier. And it is not like there are many projects similar to gio.

#154 Android problems: emulators are now x86; example has glitch a month ago

Ticket created by ~ceo_of_programming on ~eliasnaur/gio

Hello.

The android sdk only emulates versions after 7 (nogaut) on x86, I assume the binaries generated are for arm because they crash on the emulator. Running on a real device works but the demo "kitchen" flashes the screen after every step of the "loading bar widget". After it "loads" the flashing stops but the entire UI is very laggy. Unfortunately I'm not yet experienced enough with go to pinpoint where to make the fixes.

Overall the project seems very cool, also great choice of hosting.

Bye.