Minimum Android API Version

Help
#21

I didn’t see your commits to openfl/openfl on GitHub. I suppose you didn’t push your changes yet.

Once you do, how do I test this? Is there any way to avoid uninstalling and reinstalling OpenFL using a zip download of the GitHub repository? (I’m pretty new to Haxe/OpenFL still).

#22

It’s in Lime, we might be close to a release, otherwise you could just test the changed manually.

If you’re familiar with GIT, you can clone the Lime repository using the instructions on it’s README.

Otherwise, the changes are in a couple Java files, like this: https://github.com/openfl/lime/commit/7a3617fc7819534ef5823a44bb20a86896b0956f

#23

Oh, I see – Haxelib allows me to specify a location without touching the existing location, so I can switch back and forth without much work.

I’ll wait for a release. I am close to releasing my game, but I still need a few more days.

Do you have an approximate ETA for the release?

#24

probably in the next week

#25

That soon? I’ll definitely wait it out.

Also, what are the official “channels” for release? Is it possible to get email notification (eg. via a mailing list), or is there an RSS feed I can tap into?

#26

Back to this one again - I’m still not able to run on my old 2.3.5 device nor in the emulator with a similar 2.3.x version. This was using the latest limes - either 2.0.6 Lime and I also tried the latest lime dev repo.

Another post is reporting similar issues : Doesn't run apk on old Android API [SOLVED]

#27

I recently changed the emulator in dev to use X86, I’m not sure how old of an emulator would work, as I (think?) that older API emulators do not support host GPU mode, which means that the GLES2 API breaks.

Do you get any specific errors trying on a device?

#28

I’m still seeing these messages in the logs on the device when targeting min-android-SDK=10

but there is a lot of other guff being produced in the log so it’s difficult to narrow it all down to something specific.

#29

That’s strange. Both of these are guarded by version checks, the onStart call to setSystemUiVisibility is behind something that should work for only API 16 or newer devices (the method itself was added in API 11) and the onTrimMemory call is added for API 14 or newer devices.

#30

Just saw another post about a similar issue, perhaps we need to use Java reflection on these calls

#31

When I had a look at the code I noticed the guards and equally couldn’t understand why the calls were seemingly being made.

#32

I think I read something about some systems reading the whole Java file and throwing up its hands “I don’t know what that is!” before it even executed the code

#33

I’m targeting version 19. Getting this error:

...\Android SDK\tools\ant\build.xml:601: The following error occurred while executing this line:
...\Android SDK\tools\ant\build.xml:653: The following error occurred while executing this line:
...\Android SDK\tools\ant\build.xml:698: null returned: 1

Using the following in Project.xml

<android target-sdk-version="19"/> 
<window hardware="true" allow-shaders="true" require-shaders="true" fullscreen="true" if="cpp"/>
<window vsync="true" antialiasing="1" if="cpp"/>
<window orientation="landscape" if="cpp"/>

openfl: 3.5.3
hxcpp: 3.2.94
lime: 2.8.2

I tried lime -clean as suggested on StackOverflow. Also have the latest SDK. still getting the error.

#34

Would you mind trying an OpenFL sample, and see if it works for you?

I think Ant might have some difficult to understand errors, which might occur from spaces in your directory path, or spaces in the project or output file name :confused: