Excellent, thankyou for the tip.

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Sunday, January 10th, 2021 at 23:36, Elias Naur <mail@eliasnaur.com> wrote:

> On Sun Jan 10, 2021 at 20:24, Loki Verloren wrote:
>
> > just updating, I got an apk file in the end, and the app doesn't run, immediately closes and pops up a process died error.
> >
> > So I guess I'm gonna have to work with the simulator to debug why it's not working. To be honest I'm not sure if apps with
> >

ah yes, apologies, just had to add, it built fine with the latest SDK, and NDK version 20. At least it made an apk file anyhow.

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Sunday, January 10th, 2021 at 21:24, Loki Verloren <stalker.loki@protonmail.ch> wrote:

> just updating, I got an apk file in the end, and the app doesn't run, immediately closes and pops up a process died error.
>
> So I guess I'm gonna have to work with the simulator to debug why it's not working. To be honest I'm not sure if apps with
>
> so many child processes are very straight forward to deploy onto android or ios devices. We have seen other, simpler apps
>

just updating, I got an apk file in the end, and the app doesn't run, immediately closes and pops up a process died error.
So I guess I'm gonna have to work with the simulator to debug why it's not working. To be honest I'm not sure if apps with
so many child processes are very straight forward to deploy onto android or ios devices. We have seen other, simpler apps
build and run fine on android so far but I have not yet seen Pod run on one. There's so many factors in it that I
couldn't even hardly speculate what the bug is. It could be the spawning of child processes, it could be the UDP4
multicast in the miner component, it could be something to do with writing files (everything writes to the system profile
folder, how I set it up made things work with another app a colleague is working on, allowing it to display PDF files,
generated by a pdf generator script.), it could be pprof, or something else that is loaded at the start that hasn't got
proper android support. When I come to doing this task, I will just work with emulators until it even shows the unlock page.

Thanks for the help guys :)

Sent with ProtonMail Secure Email.

sorry, wasn't clear. That was the version. Obviously d8 is not in version 27.

I am upgrading the sdk build tools to the latest, since as I am understanding everyone, that's what is
supposed to be done. Hopefully after this I get a build :/

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Sunday, January 10th, 2021 at 19:00, Loki Verloren <stalker.loki@protonmail.ch> wrote:

> this is what I'm getting now, on version 29 as well as previous versions:
>
> gogio: exec: "C:\\Users\\loki\\AppData\\Local\\Android\\Sdk\\build-tools\\27.0.1\\d8": file does not exist

this is what I'm getting now, on version 29 as well as previous versions:

gogio: exec: "C:\\Users\\loki\\AppData\\Local\\Android\\Sdk\\build-tools\\27.0.1\\d8": file does not exist
exit status 1

why is it looking for that? The installed version 27 also gave the same error.

I am using NDK 20

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Sunday, January 10th, 2021 at 18:32, Loki Verloren <stalker.loki@protonmail.ch> wrote:

Specifics really help a lot, I am trying this now.

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Sunday, January 10th, 2021 at 18:12, Lucas Rodrigues <inkeliz@inkeliz.com> wrote:

> That is what I'm using to build Android apps that runs on Android 5 up to Android 11:
>
> Java SDK 11 (the "javac.exe").
>
> Android 10 (Q) SDK (API Level 29). (the "SDK Plataforms" on Android Studio").
>

Ah, thanks for the explanation. No, I want it to work on 5.1 if possible. Or at least 7.

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Sunday, January 10th, 2021 at 17:00, Lucas Rodrigues <inkeliz@inkeliz.com> wrote:

> > Maybe you are misinformed. I'm pretty sure I can't run an SDK 25 app on SDK 24 based device.
>
> I have encountered this problem numerous times in the past because I am so often with 2
>
> years old hardware. 'this is not compatible with your device'. Because of SDK version.
>

The total opposite. So you are saying that what I can get built on the latest version with the latest SDK should work
on nougat devices? As far as I understand it, in general lower sdk versions can run on everything later, so
the minimum target being ... above 27, literally means I can't test my app on my physical devices.

As far as I understand it, from version 5, android has per-app based profile folders and linux container based isolation.
For the most part, 5 is the minimum target, which is 24, iirc. They have been entirely idiotic with their version
bumping since 25. The version numbers are nearly useless at telling you anything about how much api breaks they have
made.

Ok, Anyhow, that flag will be useful. I want it to support min 5.1, if possible, if not, at least version 7...
I don't think there is many devices still running older than this. The other thing is that it is intended that the
target market for our project will potentially have old android versions, such as the ones that are made in India.
In my opinion, the main reasons to upgrade are security, several apps I used to use can't run on my devices anymore
because of this. The vendors of these devices never bother to upgrade the version ever, except in rare cases, and

except you just said you won't do the work yourself. And you already published those notes.

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Sunday, January 10th, 2021 at 16:31, Elias Naur <mail@eliasnaur.com> wrote:

> On Sun Jan 10, 2021 at 14:46, Loki Verloren wrote:
>
> > Maybe you can c&p those notes you just wrote into the section on gioui.org on building for android,
> >
> > to prevent others from having to ask this question again later.
>

Well it was at least a month since the commit had been made, when I discovered it was gone.
It was exactly the one that afterwards a LOT of breaks happen. I picked that commit precisely
because the next one broke my build.

Are you trying to tell me that android 11 apps can run on an android 7 device? Since when?

Maybe you are misinformed. I'm pretty sure I can't run an SDK 25 app on SDK 24 based device.
I have encountered this problem numerous times in the past because I am so often with 2
years old hardware. 'this is not compatible with your device'. Because of SDK version.

Maybe the numbers of android 7 devices remaining favours your perspective on this but
if I can't run an app on my blackview bv6000, I am mystified as to what substantial feature
is missing that meant the app developer didn't use an earlier version that still has
physical devices capable of running it and not the newer version.