[01:20:34] *** Quits: NavitLogger (~NavitLogg@pizarro.uberspace.de) (Will I dream?)
[01:21:03] *** Joins: NavitLogger (~NavitLogg@pizarro.uberspace.de)
[01:21:03] *** Server sets mode: +nrtz 
[01:21:34] *** Joins: jkoan (~jkoan@pizarro.uberspace.de)
[01:21:34] *** ChanServ sets mode: +o jkoan
[01:52:48] *** Quits: OLFDB (~olfdb@213.220.159.8) (*.net *.split)
[01:53:57] *** Joins: OLFDB (~olfdb@213.220.159.8)
[07:13:10] *** Quits: Navit (~Navit@ec2-34-214-224-248.us-west-2.compute.amazonaws.com) (Read error: Connection reset by peer)
[07:13:11] *** Joins: Navit1 (~Navit@ec2-34-214-224-248.us-west-2.compute.amazonaws.com)
[07:13:11] *** ChanServ sets mode: +v Navit1
[07:14:04] *** Navit1 is now known as Navit
[18:19:44] <Navit> <jkoan> Hi mvglasow, didn't had the time to test the android debugger with android 11, but one question arrived. Have you configured hardware acceleration?
[18:22:45] <Navit> <jkoan> Will hopefully test this afternoon myself
[18:25:40] <Navit> <jkoan> Found this link https://developer.android.com/studio/run/emulator-acceleration
[18:40:01] <jkoan> mvglasow: just tested the emulator itself setup with android studio. I have choosen the the Pixel 4 with the Playstore and used the x86 image which was recommended
[18:42:22] <jkoan> emulated Performace was set to automatic and the performace is great
[18:42:28] <Navit> <jkoan> https://cdn.discordapp.com/attachments/500190750085087235/839935161814482984/unknown.png
[18:42:56] <Navit> <jkoan> https://cdn.discordapp.com/attachments/500190750085087235/839935277577011200/unknown.png
[18:46:44] <Navit> <jkoan> video quality was limited for upload but the smoothness is like in real live
[18:46:44] <Navit> <jkoan> https://cdn.discordapp.com/attachments/500190750085087235/839936231386644520/untitled.mp4
[18:49:51] <mvglasow> looks like I never enabled qemu accelaration, just installing it to see if that helps, thx for the pointer
[18:50:31] <mvglasow> but I have another problem with the emulator: hardware buttons do nothing on Android 11 (earlier images worked)
[18:51:23] <Navit> <jkoan> I just tried the hardware button to shot the system down, that worked flawlessly
[18:51:50] <Navit> <jkoan> Have you enabled hardware acceleration within your bios?
[18:53:17] <mvglasow> should be (I am using VirtualBox all the time), I'll check next time I reboot
[18:55:34] <Navit> <jkoan> Just check if /dev/kvm is available. Also you can not use any other virtualization technology while using the android emulator. And acceleration within a VM can't really work
[18:57:35] <mvglasow> yep, I got /dev/kvm
[18:58:25] <Navit> <jkoan> Then kvm should be enabled
[18:59:00] <mvglasow> I"m just recreating the AVD, just to make sure I'm starting with a clean slate
[19:00:01] <Navit> <jkoan> Good idea, that was also the reason for the screenshots
[19:10:33] <mvglasow> ...still waiting for the HD to go quiet, so far the thing won"t even go into settings
[19:14:14] <mvglasow> System UI keeps stopping... this thing is broken by design, I feel
[19:16:44] <Navit> <jkoan> What are you using for the avd? Also android studio?
[19:17:25] <mvglasow> no, I don't have Android Studio, I created the AVD from the command line
[19:17:49] <mvglasow> I try to avoid AS
[19:20:05] <Navit> <jkoan> If I could export you something I would do so. Is there some sort of configuration?
[19:20:46] <mvglasow> for the AVD? configs should be in ~/.android/avd
[19:20:55] <mvglasow> one subdir for each AVD
[19:21:31] <Navit> <jkoan> Will start my pc again and check :)
[19:21:33] <mvglasow> files ending in .img or .qcow2 are disk images, which may get large
[19:21:48] <Navit> <jkoan> Yes of course :D
[19:27:10] <Navit> <jkoan> https://cdn.discordapp.com/attachments/500190750085087235/839946412891963433/config.ini
[19:27:11] <Navit> <jkoan> https://cdn.discordapp.com/attachments/500190750085087235/839946417048780820/hardware-qemu.ini
[19:27:49] <Navit> <jkoan> jan@jan-pc:~/.android/avd/Pixel_4_API_30.avd$ find . ./quickbootChoice.ini ./emulator-user.ini ./AVD.conf ./sdcard.img ./emu-launch-params.txt ./cache.img ./snapshots ./userdata-qemu.img ./config.ini ./multiinstance.lock ./sdcard.img.qcow2 ./userdata-qemu.img.qcow2 ./version_num.cache ./encryptionkey.img ./encryptionkey.img.qcow2 ./cache.img.qcow2 ./hardware-qemu.ini ./tmpAdbCmds ./userdata.img ./read-snapshot.txt
[19:27:50] <Navit> ./data ./data/misc ./data/misc/pstore ./data/misc/pstore/pstore.bin jan@jan-pc:~/.android/avd/Pixel_4_API_30.avd$ 
[19:28:25] <jkoan> i thin this is the most important detail
[19:32:10] <mvglasow> just recreated the AVD, before the first launch it just has two files, config.ini and userdata.img (the latter just being 1 MB in size)
[19:32:27] <mvglasow> will try dropping in your coinfig.ini before first launching it
[19:33:08] <jkoan> you need to adjust the paths, for me its /home/jan i think you will need to change this
[19:38:23] <mvglasow> I adjusted a few other things as well, such as display resolution and density, let"s see
[19:41:03] <Navit> <jkoan> Fingers crossed
[19:41:18] <mvglasow> yea, me too :-)
[19:44:33] <mvglasow> this seems to work better indeed, save for the minor glitch of emulating an XHDPI screen on a 100-ish dpi LCD
[19:45:05] <mvglasow> everything's there and seems to work, except that text is close to illegible
[19:45:35] <Navit> <jkoan> Could you match those settings? For me it worked
[19:46:45] <mvglasow> well, I changed paths (also from Google Play to Google APIs), as well as x86 to x86_64, and I got a device that boots and seems to work
[19:46:55] <mvglasow> no crashes so far, and HW buttons seem to work as well
[19:48:03] <Navit> <jkoan> Really nice, now the most relevant remaining question would be what's the difference
[19:53:09] <mvglasow> between device configs? or between Android 10 and 11?
[19:58:06] <Navit> <jkoan> Between those config files.
[19:59:03] <Navit> <jkoan> Of course we also need to fix Navit on recent android versions, but for now I am meaning the configs.
[20:15:14] <mvglasow> yours has a bunch more options
[20:16:46] <mvglasow> hw.arc (no idea what this is for), hw.cpu.ncore. all of hw.device.*, hw.gpu.* and a few more (which don't look related to me)
[20:17:16] <mvglasow> and hw.device.* is different
[20:17:52] <mvglasow> but I can do a few more tests when I get to it
[20:20:16] <Navit> <jkoan> I would think that hw.gpu is the most relevant. Arc could stand for Audio return channel, probably for Android TV boxes
[20:23:57] <Navit> <jkoan> # Chrome OS devicesname = hw.arctype = booleandefault = noabstract = Chrome OS device (App Runtime for Chrome)description = The emulated device is a Chrome OS machine.
[20:24:08] <Navit> <jkoan> # Chrome OS devices name        = hw.arc type        = boolean default     = no abstract    = Chrome OS device (App Runtime for Chrome) description = The emulated device is a Chrome OS machine.
[20:24:13] <Navit> <jkoan> Ah, better
[20:24:27] <Navit> <jkoan> https://android.googlesource.com/platform/prebuilts/android-emulator/+/master/linux-x86_64/lib/hardware-properties.ini
[20:34:57] <mvglasow> thanks, I'll have a look at it, but that might take a while (currently busy preparing my move)