LÖVE

LÖVE-Android • Re: IAP(In App Purchase)

2015-01-17T19:11:10+00:00

Hi everyone,

first of all thanks for both the iOS and Android ports, those are really awesome!!!

I think the proposed solution of creating the hook to be able to call native API is a great idea.
I love how not bloated the ports are and I would prefer for them to stay that way.

Having said that if such hooks are not possible, I'd like to know if someone can write a small guide on how to integrate those native functions for people that want to for example to integrate the native microphone or camera, or enable leaderboards.
I don't really know where to put my hands with that and a small guide would probably help startup these modules by the community.

Thanks,
Gianmichele

Statistics: Posted by gianmichele — Sat Jan 17, 2015 7:11 pm

LÖVE-Android • Re: love-android-sdl2 (native, 0.9.0)

2015-01-13T20:10:29+00:00

atos93 wrote:
i have this error
Code:
atos@atos-1011PX ~/love-android-sdl2 $ ant debug [...] -build-setup: [getbuildtools] Using latest Build Tools: 21.1.2 [echo] Resolving Build Target for love_android_sdl2... BUILD FAILED /home/atos/Android/Sdk/tools/ant/build.xml:542: Unable to resolve project target 'android-19'

Either set android:targetSdkVersion in AndroidManifest.xml to 21 or install the Android SDK Build-tools Rev. 19.

atos93 wrote:
i have this errorand
Code:
atos@atos-1011PX ~/love-android-sdl2 $ ant debug Buildfile: /home/atos/love-android-sdl2/build.xml BUILD FAILED /home/atos/love-android-sdl2/build.xml:56: sdk.dir is missing. Make sure to generate local.properties using 'android update project' or to inject it through the ANDROID_HOME environment variable. Total time: 2 seconds

Running the suggested 'android update project' fixes this.

Statistics: Posted by fysx — Tue Jan 13, 2015 8:10 pm

LÖVE-Android • Re: love-android-sdl2 (native, 0.9.0)

2015-01-13T15:10:38+00:00

i have this error

Code:: atos@atos-1011PX ~/love-android-sdl2 $ ant debug Buildfile: /home/atos/love-android-sdl2/build.xml -set-mode-check: -set-debug-files: -check-env: [checkenv] Android SDK Tools Revision 24.0.2 [checkenv] Installed at /home/atos/Android/Sdk -setup: [echo] Project Name: love_android_sdl2 [gettype] Project Type: Application -set-debug-mode: -debug-obfuscation-check: -pre-build: -build-setup: [getbuildtools] Using latest Build Tools: 21.1.2 [echo] Resolving Build Target for love_android_sdl2... BUILD FAILED /home/atos/Android/Sdk/tools/ant/build.xml:542: Unable to resolve project target 'android-19' Total time: 6 seconds

and

Code:: atos@atos-1011PX ~/love-android-sdl2 $ ant debug Buildfile: /home/atos/love-android-sdl2/build.xml BUILD FAILED /home/atos/love-android-sdl2/build.xml:56: sdk.dir is missing. Make sure to generate local.properties using 'android update project' or to inject it through the ANDROID_HOME environment variable. Total time: 2 seconds

Statistics: Posted by atos93 — Tue Jan 13, 2015 3:10 pm

LÖVE-Android • Re: love-android-sdl2 (native, 0.9.0)

2015-01-13T11:06:43+00:00

fysx wrote:
Muris wrote:So I was wondering if there is an easy way to completely remove the vibration support from the löve?

The easiest would be to adjust the function vibrate() in GameActivity.java to do nothing.

Oh, umm I mean it crashes on pause because of:

Code:: vibrator.cancel();

I was lucky to catch the point of where vibration is set from one of the commit texts. Then I tried modifying the code as following, and it seems that I can then remove the permission without crashing the application:

Code:: in begin of gameactivity.java private static Vibrator vibrator = null; in oncreate: context = this.getApplicationContext(); if( context.checkCallingOrSelfPermission("android.permission.VIBRATE") == context.getPackageManager().PERMISSION_GRANTED ) { Log.d("GameActivity", "Permission for vibrator granted."); vibrator = (Vibrator) this.context.getSystemService(Context.VIBRATOR_SERVICE); } and on destroy / pause if( vibrator != null ) { Log.d("GameActivity", "Cancelling vibration"); vibrator.cancel(); } and then in vibrate function if( vibrator != null ) { vibrator.vibrate((long) (seconds * 1000.)); }

With this it seems that the android application can be run without giving any permission at all. Maybe you cannot use all the features like internet etc. from love-application but from user point of perspective the application should be safer to use.

Statistics: Posted by Muris — Tue Jan 13, 2015 11:06 am

LÖVE-Android • Re: love-android-sdl2 (native, 0.9.0)

2015-01-13T10:13:39+00:00

Muris wrote:
So I was wondering if there is an easy way to completely remove the vibration support from the löve?

The easiest would be to adjust the function vibrate() in GameActivity.java to do nothing.

Statistics: Posted by fysx — Tue Jan 13, 2015 10:13 am

LÖVE-Android • Re: love-android-sdl2 (native, 0.9.0)

2015-01-13T00:42:07+00:00

I was playing around with this, and managed to compile the sources. I've been mostly using the precompiled version for app testing, but today I decided to try and see if what I for the game that I have now works on compiled version.

I was happy to notice that it does work, and I even managed to remove some of the activities from the game (I personally do not want to give a random application license to use internet, but rather just not use the app at all), but I noticed that vibrate thing is the only one that cannot be removed without actually making the game crash when pausing(switching app). So I was wondering if there is an easy way to completely remove the vibration support from the löve?

Also I was happy to notice that it is possible to save and load files without the need to give permission for external storage.

Statistics: Posted by Muris — Tue Jan 13, 2015 12:42 am

LÖVE-Android • Re: IAP(In App Purchase)

2015-01-12T23:10:58+00:00

Mmmmm... PAI....

Statistics: Posted by Jasoco — Mon Jan 12, 2015 11:10 pm

LÖVE-Android • Re: IAP(In App Purchase)

2015-01-12T14:13:46+00:00

That IAP API should be called PAI.

Statistics: Posted by Robin — Mon Jan 12, 2015 2:13 pm

LÖVE-Android • Re: appt.exe stopped

2015-01-12T09:54:27+00:00

Can you provide logs? I.e.: https://bitbucket.org/MartinFelis/love- ... iki/Logcat

Statistics: Posted by fysx — Mon Jan 12, 2015 9:54 am

LÖVE-Android • Re: love-android-sdl2 (native, 0.9.0)

2015-01-12T09:53:34+00:00

Abregado wrote:
I've been making some prototypes and testing them on my Android Tablet as well as sending them to some friends to test. Some of them get the blue love stacktrace screen when the app crashes, but none of my devices do.

Is there a way to enable this per device?

Older versions of LÖVE for Android (i.e. < 0.9.1) had problems printing the stack-trace as the font rendering was not properly initialized and therefore only showed the blue screen.

Do you have more detailed information what versions of LÖVE you are using? Also the type of Android devices and their Android versions would be very helpful.

Statistics: Posted by fysx — Mon Jan 12, 2015 9:53 am

LÖVE-Android • Re: IAP(In App Purchase)

2015-01-12T09:47:48+00:00

Not sure whether someone else is planning it I personally do not plan to add it. I also do not think that there will be a IAP-API on the LÖVE side itself and adding for each provider a custom API would be too cumbersome.

The most feasible route I see is by implementing some communication layer with the Java side of the app. I.e. that one could send key-value pairs to Java, do some processing there, and send them back to LÖVE. That way you would implement the IAP code for the provider of your liking in Java as any other Android app and would have to figure out what to communicate between Java and LÖVE to make it happen or to confirm it.

Any progress in the direction of Java-LÖVE-communication will be reported here: https://bitbucket.org/MartinFelis/love- ... st-android. Would love to accept some patches for this!

Statistics: Posted by fysx — Mon Jan 12, 2015 9:47 am

LÖVE-Android • Re: "LÖVE FOR ANDROID has stopped working"

2015-01-09T05:43:49+00:00

Hello, clofresh, thank you for your answer.

I should have closed the topic because I finally got it working by downgrading to r9.

Statistics: Posted by Ulydev — Fri Jan 09, 2015 5:43 am

LÖVE-Android • Re: "LÖVE FOR ANDROID has stopped working"

2015-01-08T01:40:36+00:00

Are there any errors in logcat? Does it work when installing the apk onto an actual device?

Statistics: Posted by clofresh — Thu Jan 08, 2015 1:40 am

LÖVE-Android • Re: LÖVE 0.9.1 released

2015-01-04T00:33:46+00:00

Thanks! It works now.

Statistics: Posted by Gold_Car — Sun Jan 04, 2015 12:33 am

LÖVE-Android • Re: LÖVE 0.9.1 released

2015-01-03T22:53:44+00:00

Replace

Code:: require "entities.lua"

with

Code:: require "entities"

The string that is passed to require is a module name, not a file name. A module called "foo.bar" can generally be found in "foo/bar.lua" or "foo/bar/init.lua", so your code is looking for "entities/lua.lua" and "entities/lua/init.lua" etc.

Statistics: Posted by Robin — Sat Jan 03, 2015 10:53 pm

LÖVE-Android • Re: LÖVE 0.9.1 released

2015-01-03T21:54:13+00:00

Alright, here's what I've got. I'm trying to make the entities.lua load with the main.lua, and I get that cheeky old bluescreen.

Statistics: Posted by Gold_Car — Sat Jan 03, 2015 9:54 pm

LÖVE-Android • Re: LÖVE 0.9.1 released

2015-01-01T23:48:00+00:00

Will do.

Statistics: Posted by Gold_Car — Thu Jan 01, 2015 11:48 pm

LÖVE-Android • Re: LÖVE 0.9.1 released

2015-01-01T21:13:21+00:00

Put them in a .zip, and then rename the .zip to .love, as seen on the wiki page Game_Distribution. If you prefer, you could just upload a zip file of your game, it's just more convenient for us if it's a .love.

Statistics: Posted by Robin — Thu Jan 01, 2015 9:13 pm

LÖVE-Android • Re: LÖVE 0.9.1 released

2015-01-01T21:09:04+00:00

Robin wrote:
You could try uploading a .love of your game so we can take a look at it.

How do I turn my files into .love?

Statistics: Posted by Gold_Car — Thu Jan 01, 2015 9:09 pm

LÖVE-Android • Re: LÖVE 0.9.1 released

2015-01-01T13:37:45+00:00

Gold_Car wrote:
I've been trying to use the require() thingy for quite some time now and haven't made any progress. But I need it - or something equivalent to it - to finish a small project that I've been trying to figure out (I.E. following Goature's tutorial). Should I just downgrade my LOVE?

You could try uploading a .love of your game so we can take a look at it.

Statistics: Posted by Robin — Thu Jan 01, 2015 1:37 pm

LÖVE-Android • Re: LÖVE 0.9.1 released

2015-01-01T02:23:49+00:00

slime wrote:
osuf oboys wrote:However, it is no longer possible to 'require "bit"' (works fine in lua) - would it be possible to add back this library?

There is no bit operations library in Lua 5.1 (which LÖVE used to use until 0.9). LuaJIT (which LÖVE uses by default in 0.9.0 and 0.9.1) includes a bit library which you can use like so:
Code:
local bit = require("bit")

I've been trying to use the require() thingy for quite some time now and haven't made any progress. But I need it - or something equivalent to it - to finish a small project that I've been trying to figure out (I.E. following Goature's tutorial). Should I just downgrade my LOVE?

Statistics: Posted by Gold_Car — Thu Jan 01, 2015 2:23 am

LÖVE-Android • "LÖVE FOR ANDROID has stopped working"

2014-12-29T20:12:58+00:00

Hello everyone, I'm running into (hopefully) the last issue before actually releasing my first two Löve2D games to iOS and Android.

I've searched on the internet and on the forums for answers but it seems like this problem has not been solved. Please tell me if an answer has already been posted.

I followed the instructions to build Löve for Android, as specified in the bitbucket documentation.
I first ran into an issue and had to downgrade the NDK to r10. Then building worked fine and "ant debug" resulted in a test .apk. The problem I'm getting is that whenever I try to install the .apk I built on an Android emulator, it crashes and tells me that "LÖVE FOR ANDROID has stopped working".
At first I thought there was a problem with the emulator. So, I tried to install the pre-built .apk version of Löve available in the bitbucket repo, and... surprisingly, it worked fine. Now that I need to package my game for releasing, I do need to build my own .apk.

I must add that I'm using OSX 10.9.5.

Thank you in advance for your answers, I really need to get this working ASAP as my games need to be released in less than a week.

Statistics: Posted by Ulydev — Mon Dec 29, 2014 8:12 pm

LÖVE-Android • Re: Installing .apk files?

2014-12-20T16:25:26+00:00

Germanunkol wrote:
Settings for the emulator: Android 3.1 (API level 12)

I believe newer versions of the emulator support OpenGL ES 2, but it still might be buggy enough to not work properly.

Statistics: Posted by slime — Sat Dec 20, 2014 4:25 pm

LÖVE-Android • Re: Installing .apk files?

2014-12-20T14:21:19+00:00

Maybe it does support GLESv1.1 but not GLESv2.

Statistics: Posted by bartbes — Sat Dec 20, 2014 2:21 pm

LÖVE-Android • Re: Installing .apk files?

2014-12-20T13:43:57+00:00

Right... weird though, there was a folder with "API Samples/GLES" or similar, and those worked.

Anyway, then I'll have to get my hands on a real phone one of these days...

Statistics: Posted by Germanunkol — Sat Dec 20, 2014 1:43 pm