Android tests

[NiLSPACE]

the app doesn't restart. its just that it cleans the log on screen.

[Lapayo]

On my phone the debuglog doesn´t work O.o (Huawei Honor)
There is no output. After killing the process, because I thought it crashed I saw in the log file that the chunk generation was running. (Glorious 1.2 Chunks / Second)

[xoft]

It seems we'll need a proper callback mechanism into Java, so that:
1, we don't require the "read sensitive log data" permission
2, logging works even on weird android versions

Well, it seems FakeTruth is catching some sleep after his yesterday's midnight-oil-burning

[NiLSPACE]

Faketruth are you also planning on making it easier to configurate in the android version?

[FakeTruth]

It seems we'll need a proper callback mechanism into Java, so that:
1, we don't require the "read sensitive log data" permission
2, logging works even on weird android versions

Well, it seems FakeTruth is catching some sleep after his yesterday's midnight-oil-burning

As I stated in a commit log, callling Java functions from C++ is only allowed from a Java thread (not native thread). It's possible to call those functions from other threads, but it's messy. Threads need to be attached and detached to the JVM, confusing stuffs...

Also I was at family

Faketruth are you also planning on making it easier to configurate in the android version?

Not specifically for Android. I think the WebAdmin should be used for configuring the server.

[NiLSPACE]

Faketruth are you also planning on making it easier to configurate in the android version?

Not specifically for Android. I think the WebAdmin should be used for configuring the server.

thats a nice idea to be able to configurate the server with the webadmin
oh and a question. if you install the server on android does it install all the configuration files? like settings.ini and items.ini and does it install the core plugins + the webadmin's template.html

[FakeTruth]

Faketruth are you also planning on making it easier to configurate in the android version?

Not specifically for Android. I think the WebAdmin should be used for configuring the server.

thats a nice idea to be able to configurate the server with the webadmin
oh and a question. if you install the server on android does it install all the configuration files? like settings.ini and items.ini and does it install the core plugins + the webadmin's template.html

No it doesn't It only uses default settings, and those settings suck.
It does create a settings.ini file though

[FakeTruth]

As I stated in a commit log, callling Java functions from C++ is only allowed from a Java thread (not native thread). It's possible to call those functions from other threads, but it's messy. Threads need to be attached and detached to the JVM, confusing stuffs...

I think the easiest way is to create a message queue in C++. The log (or whatever that needs to communicate with Java) would add messages (instanced classes with a function, like Java's Runnable) to a queue. Then a Java thread will call a C++ function that reads these messages and execute them. This way we can be absolutely sure that these functions are always called from a Java thread (we know it will have enough memory etc.) without messing with attaching and detaching threads to the JVM

[xoft]

I think the easiest way is to create a pipe in C++ to which the server would write the log and Java (via C++ JNI) would read it. My Android-educated colleague hinted me at this solution.

---

There is also a way to call Java stuff from a C++ thread, but it's not so easy (need to call AttachThread(), with a parameter that is received on library load via OnLoad...() ) and I think the pipe solution is much easier and cleaner.

[FakeTruth]

I think the easiest way is to create a pipe in C++ to which the server would write the log and Java (via C++ JNI) would read it. My Android-educated colleague hinted me at this solution.

But isn't that severely limited to just the log/messages?

There is also a way to call Java stuff from a C++ thread, but it's not so easy (need to call AttachThread(), with a parameter that is received on library load via OnLoad...() ) and I think the pipe solution is much easier and cleaner.

I know... I've written about that...