ilovekiruna | hi everyone | 11:26 |
---|---|---|
ilovekiruna | sorry if I missed it, but I am wonering if or which devices also support android apps, beside sailfishX devices | 11:27 |
*** Mister_Magister_ is now known as Mister_Magister | 11:55 | |
T42 | <edp_17> None of them. | 12:07 |
T42 | <edp_17> You need to buy a licence for official devices to be able to run android apps. | 12:07 |
ilovekiruna | couldnt we realize that with anbox? | 13:08 |
T42 | <edp_17> We could, but Anbox currently doesn't work on sfos. | 13:10 |
ilovekiruna | I c :-( | 13:10 |
ilovekiruna | thanks for the information | 13:21 |
rinigus | mal: what is the state of 64bit support and aosp10? in the context of moving port into this combo? cc piggz | 16:09 |
mal | I had android 9 based 64-bit build working quite nicely, I haven't yet tried the android 10 build I made for fp3 | 16:11 |
piggz | whats the process for making a 64bit build? change PORT_ARCH ? | 16:12 |
mal | pretty much just that | 16:12 |
rinigus | OK, sounds simple enough. I guess we should start and then ask for help. | 16:14 |
mal | for 3.4.0 build there are some known bugs in aarch64 but those are mainly runtime issues | 16:15 |
mal | piggz: that reminds me that I should make a PR of the aarch64 fixes for community fingerprint support | 16:16 |
piggz | mal: you should | 16:16 |
rinigus | mal: sorry, what is the runtime in this context? | 16:17 |
piggz | are the repos for 64bit public? | 16:18 |
mal | rinigus: ohm and tracker issues at least if I remember correctly | 16:18 |
mal | piggz: there is the aarch64 target here http://releases.sailfishos.org/sdk/targets/ | 16:19 |
rinigus | mal: sounds like we should start testing conversation to 64 bit. | 16:23 |
rinigus | mal: what about aosp10 - are some docs planned regarding ports using it? Something like we had for aosp9 (build instructions for xperia 10) | 16:25 |
T42 | cfb014 was added by: cfb014 | 16:37 |
rinigus | (conversation as suggested by presage -> conversion) | 16:49 |
rinigus | tried to enable aarch64 at OBS. looks like :latest is not available for aarch64 - https://build.merproject.org/project/meta/sailfishos:latest | 20:19 |
rinigus | when testing with 3.4.0.24, I am getting "unresolvable" for all packages. see https://build.merproject.org/project/monitor/home:rinigus:toolbox?arch_aarch64=1&defaults=0&repo_sailfish_3_4_0_24_aarch64=1&unresolvable=1 | 20:20 |
mal | rinigus: aarch64 is not working on obs | 20:21 |
rinigus | mal: are there plans to fix it? | 20:22 |
mal | not sure, need to ask | 20:22 |
rinigus | mal: thanks! | 20:22 |
mal | rinigus: there will probably be some docs later, mostly the process is quite similar to android 9 | 20:47 |
mal | rinigus: some parts have not been merged yet like libhybris and droidmedia | 20:49 |
rinigus | mal: great to hear that it is similar to aosp9. hopefully missing bits will be merged sooner than later. | 20:51 |
mal | I probably should merge droidmedia tomorrow because it has been approved already, libhybris works but the PR is missing some cleanup | 20:53 |
rinigus | mal: nice! we can almost touch it :). please ask about obs aarch64 - it would be needed to make a shift simpler and add support for this arch by apps | 20:55 |
rinigus | even with non-steady API | 20:55 |
mal | rinigus: what do you mean by shift in this case, I doubt it's possible to update a port from arm to aarch64 without reflashing | 20:56 |
rinigus | mal: poorly worded by me then. no, I am not planning to update the port without reflashing on device. Ideally, if all works out, I would like to replace it with a 64 bit one and based on AOSP10. That should improve camera on sony tama (due to AOSP10) and allow to use latest flatpak runtimes (aarch64) | 20:59 |
rinigus | but we, as users, would have to reflash | 21:00 |
mal | ok | 21:00 |
T42 | 奥智惠 %lastname% was added by: 奥智惠 %lastname% | 23:44 |
T42 | 袁祥棠 %lastname% was added by: 袁祥棠 %lastname% | 23:58 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!