Love-native-android - Development

A project to port LÖVE to Android handhelds
User avatar
kalle2990
Party member
Posts: 245
Joined: Sat Sep 12, 2009 1:17 pm
Location: Sweden

Re: Love-native-android - Development

Post by kalle2990 »

T-Bone wrote:
Moe wrote:The same settings as for deploying from Eclipse should be fine.
I have never done that. So far, what I've done is merely exporting apk files and sending them to my phone. I will try to get logcat running and see if it works.

Totally works. Here's my logcat

Code: Select all

I/ActivityManager(  166): Start proc net.schattenkind.nativelove for activity net.schattenkind.nativelove/.LoveLauncher: pid=8538 uid=10071 gids={3003, 1015}
D/szipinf ( 8538): Initializing inflate state
D/dalvikvm( 8538): GC_EXTERNAL_ALLOC freed 42K, 51% free 2688K/5379K, external 0K/0K, paused 46ms
D/dalvikvm( 8538): GC_EXTERNAL_ALLOC freed 10K, 50% free 2712K/5379K, external 498K/513K, paused 38ms
I/ActivityManager(  166): Displayed net.schattenkind.nativelove/.LoveLauncher: +367ms
D/dalvikvm( 8511): GC_EXPLICIT freed 380K, 46% free 3484K/6343K, external 6967K/7816K, paused 67ms
I/ActivityManager(  166): Starting: Intent { dat=file:///mnt/sdcard/Android/data/com.dropbox.android/files/scratch/lua/loopbox/loopbox.love cmp=net.schattenkind.nativelove/.LoveNative } from pid 8538
D/libEGL  ( 8538): loaded /system/lib/egl/libGLES_android.so
D/libEGL  ( 8538): loaded /system/lib/egl/libEGL_adreno200.so
D/libEGL  ( 8538): loaded /system/lib/egl/libGLESv1_CM_adreno200.so
D/libEGL  ( 8538): loaded /system/lib/egl/libGLESv2_adreno200.so
I/System.out( 8538): java: init
W/dalvikvm( 8538): Exception Ljava/lang/UnsatisfiedLinkError; thrown while initializing Lnet/schattenkind/nativelove/LoveJNI;
W/dalvikvm( 8538): threadid=9: thread exiting with uncaught exception (group=0x4018d560)
E/AndroidRuntime( 8538): FATAL EXCEPTION: GLThread 10
E/AndroidRuntime( 8538): java.lang.ExceptionInInitializerError
E/AndroidRuntime( 8538): 	at net.schattenkind.nativelove.LoveRenderView$1.onSurfaceChanged(LoveRenderView.java:31)
E/AndroidRuntime( 8538): 	at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1356)
E/AndroidRuntime( 8538): 	at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1118)
E/AndroidRuntime( 8538): Caused by: java.lang.UnsatisfiedLinkError: Couldn't load ogg: findLibrary returned null
E/AndroidRuntime( 8538): 	at java.lang.Runtime.loadLibrary(Runtime.java:429)
E/AndroidRuntime( 8538): 	at java.lang.System.loadLibrary(System.java:554)
E/AndroidRuntime( 8538): 	at net.schattenkind.nativelove.LoveJNI.<clinit>(LoveJNI.java:7)
E/AndroidRuntime( 8538): 	... 3 more
W/ActivityManager(  166):   Force finishing activity net.schattenkind.nativelove/.LoveNative
W/ActivityManager(  166):   Force finishing activity net.schattenkind.nativelove/.LoveLauncher
I/ActivityManager(  166): No longer want com.koushikdutta.rommanager (pid 8031): hidden #16
I/dalvikvm( 8538): Rejecting re-init on previously-failed class Lnet/schattenkind/nativelove/LoveJNI; v=0x0
D/AndroidRuntime( 8538): Shutting down VM
W/dalvikvm( 8538): threadid=1: thread exiting with uncaught exception (group=0x4018d560)
I/Process ( 8538): Sending signal. PID: 8538 SIG: 9
I/ActivityManager(  166): Process net.schattenkind.nativelove (pid 8538) has died.
I/WindowManager(  166): WIN DEATH: Window{409e82e8 net.schattenkind.nativelove/net.schattenkind.nativelove.LoveNative paused=false}
I/WindowManager(  166): WIN DEATH: Window{409f9030 SurfaceView paused=false}
W/InputManagerService(  166): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@40ac1788
I/power   (  166): *** set_screen_state 0
I/gllauncher( 8511): onReceive() android.intent.action.SCREEN_OFF
D/gllauncher( 8511): screenOff - null
W/ActivityManager(  166): finishReceiver called but active receiver is different
W/ActivityManager(  166): finishReceiver called but no pending broadcasts
D/SurfaceFlinger(  166): About to give-up screen, flinger = 0x95008
D/WifiService(  166): acquireWifiLockLocked: WifiLock{NetworkLocationLocator type=2 binder=android.os.BinderProxy@40b3c928}
D/WifiService(  166): releaseWifiLockLocked: WifiLock{NetworkLocationLocator type=2 binder=android.os.BinderProxy@40b3c928}
D/dalvikvm( 1482): GC_FOR_MALLOC freed 334K, 44% free 3987K/7047K, external 0K/0K, paused 27ms
D/szipinf (  166): Initializing inflate state
D/dalvikvm(  166): GC_EXTERNAL_ALLOC freed 277K, 49% free 7323K/14151K, external 5808K/5985K, paused 84ms
D/dalvikvm(  166): GC_EXTERNAL_ALLOC freed 92K, 49% free 7334K/14151K, external 7494K/7712K, paused 96ms

Seems like the C/C++ code failed to compile, and is not included in your apk. Try fixing the ndk and jni path in build properties, we made some changes to how those paths are found quite recently ;)
User avatar
T-Bone
Inner party member
Posts: 1492
Joined: Thu Jun 09, 2011 9:03 am

Re: Love-native-android - Development

Post by T-Bone »

kalle2990 wrote:
T-Bone wrote:
Moe wrote:The same settings as for deploying from Eclipse should be fine.
I have never done that. So far, what I've done is merely exporting apk files and sending them to my phone. I will try to get logcat running and see if it works.

Totally works. Here's my logcat

Code: Select all

I/ActivityManager(  166): Start proc net.schattenkind.nativelove for activity net.schattenkind.nativelove/.LoveLauncher: pid=8538 uid=10071 gids={3003, 1015}
D/szipinf ( 8538): Initializing inflate state
D/dalvikvm( 8538): GC_EXTERNAL_ALLOC freed 42K, 51% free 2688K/5379K, external 0K/0K, paused 46ms
D/dalvikvm( 8538): GC_EXTERNAL_ALLOC freed 10K, 50% free 2712K/5379K, external 498K/513K, paused 38ms
I/ActivityManager(  166): Displayed net.schattenkind.nativelove/.LoveLauncher: +367ms
D/dalvikvm( 8511): GC_EXPLICIT freed 380K, 46% free 3484K/6343K, external 6967K/7816K, paused 67ms
I/ActivityManager(  166): Starting: Intent { dat=file:///mnt/sdcard/Android/data/com.dropbox.android/files/scratch/lua/loopbox/loopbox.love cmp=net.schattenkind.nativelove/.LoveNative } from pid 8538
D/libEGL  ( 8538): loaded /system/lib/egl/libGLES_android.so
D/libEGL  ( 8538): loaded /system/lib/egl/libEGL_adreno200.so
D/libEGL  ( 8538): loaded /system/lib/egl/libGLESv1_CM_adreno200.so
D/libEGL  ( 8538): loaded /system/lib/egl/libGLESv2_adreno200.so
I/System.out( 8538): java: init
W/dalvikvm( 8538): Exception Ljava/lang/UnsatisfiedLinkError; thrown while initializing Lnet/schattenkind/nativelove/LoveJNI;
W/dalvikvm( 8538): threadid=9: thread exiting with uncaught exception (group=0x4018d560)
E/AndroidRuntime( 8538): FATAL EXCEPTION: GLThread 10
E/AndroidRuntime( 8538): java.lang.ExceptionInInitializerError
E/AndroidRuntime( 8538): 	at net.schattenkind.nativelove.LoveRenderView$1.onSurfaceChanged(LoveRenderView.java:31)
E/AndroidRuntime( 8538): 	at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1356)
E/AndroidRuntime( 8538): 	at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1118)
E/AndroidRuntime( 8538): Caused by: java.lang.UnsatisfiedLinkError: Couldn't load ogg: findLibrary returned null
E/AndroidRuntime( 8538): 	at java.lang.Runtime.loadLibrary(Runtime.java:429)
E/AndroidRuntime( 8538): 	at java.lang.System.loadLibrary(System.java:554)
E/AndroidRuntime( 8538): 	at net.schattenkind.nativelove.LoveJNI.<clinit>(LoveJNI.java:7)
E/AndroidRuntime( 8538): 	... 3 more
W/ActivityManager(  166):   Force finishing activity net.schattenkind.nativelove/.LoveNative
W/ActivityManager(  166):   Force finishing activity net.schattenkind.nativelove/.LoveLauncher
I/ActivityManager(  166): No longer want com.koushikdutta.rommanager (pid 8031): hidden #16
I/dalvikvm( 8538): Rejecting re-init on previously-failed class Lnet/schattenkind/nativelove/LoveJNI; v=0x0
D/AndroidRuntime( 8538): Shutting down VM
W/dalvikvm( 8538): threadid=1: thread exiting with uncaught exception (group=0x4018d560)
I/Process ( 8538): Sending signal. PID: 8538 SIG: 9
I/ActivityManager(  166): Process net.schattenkind.nativelove (pid 8538) has died.
I/WindowManager(  166): WIN DEATH: Window{409e82e8 net.schattenkind.nativelove/net.schattenkind.nativelove.LoveNative paused=false}
I/WindowManager(  166): WIN DEATH: Window{409f9030 SurfaceView paused=false}
W/InputManagerService(  166): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@40ac1788
I/power   (  166): *** set_screen_state 0
I/gllauncher( 8511): onReceive() android.intent.action.SCREEN_OFF
D/gllauncher( 8511): screenOff - null
W/ActivityManager(  166): finishReceiver called but active receiver is different
W/ActivityManager(  166): finishReceiver called but no pending broadcasts
D/SurfaceFlinger(  166): About to give-up screen, flinger = 0x95008
D/WifiService(  166): acquireWifiLockLocked: WifiLock{NetworkLocationLocator type=2 binder=android.os.BinderProxy@40b3c928}
D/WifiService(  166): releaseWifiLockLocked: WifiLock{NetworkLocationLocator type=2 binder=android.os.BinderProxy@40b3c928}
D/dalvikvm( 1482): GC_FOR_MALLOC freed 334K, 44% free 3987K/7047K, external 0K/0K, paused 27ms
D/szipinf (  166): Initializing inflate state
D/dalvikvm(  166): GC_EXTERNAL_ALLOC freed 277K, 49% free 7323K/14151K, external 5808K/5985K, paused 84ms
D/dalvikvm(  166): GC_EXTERNAL_ALLOC freed 92K, 49% free 7334K/14151K, external 7494K/7712K, paused 96ms

Seems like the C/C++ code failed to compile, and is not included in your apk. Try fixing the ndk and jni path in build properties, we made some changes to how those paths are found quite recently ;)
They looked just fine, but I recompiled everything and it seems to work now. However, when I back out from my game and try to launch it again, it crashes. Here's the logcat from that:

Code: Select all

D/com.dropbox.android.util.FileWatcher( 8982): loopbox.love Open for /mnt/sdcard/Android/data/com.dropbox.android/files/scratch/lua/loopbox/
D/com.dropbox.android.util.FileWatcher( 8982): loopbox.love Close NoWrite for /mnt/sdcard/Android/data/com.dropbox.android/files/scratch/lua/loopbox/
I/com.dropbox.android.util.FileWatcher( 8982): File not modified: /mnt/sdcard/Android/data/com.dropbox.android/files/scratch/lua/loopbox/loopbox.love
D/com.dropbox.android.util.FileWatcher( 8982): loopbox.love Open for /mnt/sdcard/Android/data/com.dropbox.android/files/scratch/lua/loopbox/
D/com.dropbox.android.util.FileWatcher( 8982): loopbox.love Close NoWrite for /mnt/sdcard/Android/data/com.dropbox.android/files/scratch/lua/loopbox/
I/com.dropbox.android.util.FileWatcher( 8982): File not modified: /mnt/sdcard/Android/data/com.dropbox.android/files/scratch/lua/loopbox/loopbox.love
D/com.dropbox.android.util.FileWatcher( 8982): loopbox.love Open for /mnt/sdcard/Android/data/com.dropbox.android/files/scratch/lua/loopbox/
D/com.dropbox.android.util.FileWatcher( 8982): loopbox.love Close NoWrite for /mnt/sdcard/Android/data/com.dropbox.android/files/scratch/lua/loopbox/
I/com.dropbox.android.util.FileWatcher( 8982): File not modified: /mnt/sdcard/Android/data/com.dropbox.android/files/scratch/lua/loopbox/loopbox.love
D/com.dropbox.android.util.FileWatcher( 8982): loopbox.love Open for /mnt/sdcard/Android/data/com.dropbox.android/files/scratch/lua/loopbox/
D/com.dropbox.android.util.FileWatcher( 8982): loopbox.love Close NoWrite for /mnt/sdcard/Android/data/com.dropbox.android/files/scratch/lua/loopbox/
I/com.dropbox.android.util.FileWatcher( 8982): File not modified: /mnt/sdcard/Android/data/com.dropbox.android/files/scratch/lua/loopbox/loopbox.love
D/com.dropbox.android.util.FileWatcher( 8982): loopbox.love Open for /mnt/sdcard/Android/data/com.dropbox.android/files/scratch/lua/loopbox/
D/com.dropbox.android.util.FileWatcher( 8982): loopbox.love Close NoWrite for /mnt/sdcard/Android/data/com.dropbox.android/files/scratch/lua/loopbox/
I/com.dropbox.android.util.FileWatcher( 8982): File not modified: /mnt/sdcard/Android/data/com.dropbox.android/files/scratch/lua/loopbox/loopbox.love
D/PhoneListener( 8511): Signal type: GSM
I/liblove ( 9211): deinit
E/libEGL  ( 9211): call to OpenGL ES API with no current context (logged once per thread)
D/com.dropbox.android.util.FileWatcher( 8982): loopbox.love Close NoWrite for /mnt/sdcard/Android/data/com.dropbox.android/files/scratch/lua/loopbox/
I/com.dropbox.android.util.FileWatcher( 8982): File not modified: /mnt/sdcard/Android/data/com.dropbox.android/files/scratch/lua/loopbox/loopbox.love
I/ActivityManager(  166): Starting: Intent { dat=file:///mnt/sdcard/Android/data/com.dropbox.android/files/scratch/lua/loopbox/loopbox.love cmp=net.schattenkind.nativelove/.LoveNative } from pid 9211
I/System.out( 9211): java: init
I/liblove ( 9211): init
I/ActivityManager(  166): Displayed net.schattenkind.nativelove/.LoveNative: +270ms
D/WifiService(  166): acquireWifiLockLocked: WifiLock{NetworkLocationLocator type=2 binder=android.os.BinderProxy@40ddbe30}
D/WifiService(  166): releaseWifiLockLocked: WifiLock{NetworkLocationLocator type=2 binder=android.os.BinderProxy@40ddbe30}
D/dalvikvm( 1482): GC_CONCURRENT freed 339K, 44% free 4007K/7047K, external 0K/0K, paused 2ms+3ms
W/InputConnectionWrapper.ICC(  272): Timed out waiting on IInputContextCallback
W/InputConnectionWrapper.ICC(  272): Timed out waiting on IInputContextCallback
W/InputConnectionWrapper.ICC(  272): Timed out waiting on IInputContextCallback
I/InputDispatcher(  166): Application is not responding: Window{40de8900 net.schattenkind.nativelove/net.schattenkind.nativelove.LoveLauncher paused=false}.  5012.1ms since event, 5005.8ms since wait started
I/WindowManager(  166): Input event dispatching timed out sending to net.schattenkind.nativelove/net.schattenkind.nativelove.LoveLauncher
I/Process (  166): Sending signal. PID: 9211 SIG: 3
I/dalvikvm( 9211): threadid=4: reacting to signal 3
I/dalvikvm( 9211): Wrote stack traces to '/data/anr/traces.txt'
I/Process (  166): Sending signal. PID: 166 SIG: 3
I/dalvikvm(  166): threadid=4: reacting to signal 3
I/dalvikvm(  166): Wrote stack traces to '/data/anr/traces.txt'
I/Process (  166): Sending signal. PID: 281 SIG: 3
I/dalvikvm(  281): threadid=4: reacting to signal 3
I/dalvikvm(  281): Wrote stack traces to '/data/anr/traces.txt'
I/Process (  166): Sending signal. PID: 243 SIG: 3
I/dalvikvm(  243): threadid=4: reacting to signal 3
I/dalvikvm(  243): Wrote stack traces to '/data/anr/traces.txt'
D/dalvikvm(  166): GC_CONCURRENT freed 1686K, 47% free 7547K/14151K, external 5572K/6867K, paused 3ms+7ms
D/dalvikvm(  166): GC_EXPLICIT freed 244K, 47% free 7544K/14151K, external 4765K/5950K, paused 88ms
E/ActivityManager(  166): ANR in net.schattenkind.nativelove (net.schattenkind.nativelove/.LoveLauncher)
E/ActivityManager(  166): Reason: keyDispatchingTimedOut
E/ActivityManager(  166): Load: 2.64 / 2.78 / 3.5
E/ActivityManager(  166): CPU usage from 11418ms to 1925ms ago with 99% awake:
E/ActivityManager(  166):   3.6% 166/system_server: 2% user + 1.6% kernel / faults: 73 minor
E/ActivityManager(  166):   1.5% 122/akmd: 0% user + 1.5% kernel
E/ActivityManager(  166):   0.5% 243/com.android.systemui: 0.5% user + 0% kernel
E/ActivityManager(  166):   0.5% 9211/net.schattenkind.nativelove: 0.4% user + 0.1% kernel / faults: 432 minor
E/ActivityManager(  166):   0.4% 8607/kworker/0:3: 0% user + 0.4% kernel
E/ActivityManager(  166):   0.3% 1482/com.google.android.apps.maps:LocationFriendService: 0.3% user + 0% kernel
E/ActivityManager(  166):   0% 6/rcu_kthread: 0% user + 0% kernel
E/ActivityManager(  166):   0% 50/file-storage: 0% user + 0% kernel
E/ActivityManager(  166):   0% 272/com.touchtype.swiftkey: 0% user + 0% kernel / faults: 1 minor
E/ActivityManager(  166):   0% 281/com.android.phone: 0% user + 0% kernel / faults: 1 minor
E/ActivityManager(  166):   0.1% 8261/kworker/u:2: 0% user + 0.1% kernel
E/ActivityManager(  166): 6.1% TOTAL: 3% user + 3% kernel
E/ActivityManager(  166): CPU usage from 575ms to 1098ms later:
E/ActivityManager(  166):   7.4% 166/system_server: 0% user + 7.4% kernel / faults: 2 minor
E/ActivityManager(  166):     7.4% 202/InputDispatcher: 0% user + 7.4% kernel
E/ActivityManager(  166):     1.8% 174/SurfaceFlinger: 0% user + 1.8% kernel
E/ActivityManager(  166):     1.8% 178/GL updater: 0% user + 1.8% kernel
E/ActivityManager(  166):   1.8% 122/akmd: 0% user + 1.8% kernel
E/ActivityManager(  166):     1.8% 9182/akmd: 0% user + 1.8% kernel
E/ActivityManager(  166): 5.7% TOTAL: 1.9% user + 3.8% kernel
I/InputDispatcher(  166): Dropping event because the pointer is not down.
I/InputDispatcher(  166): Dropping event because the pointer is not down.
I/InputDispatcher(  166): Dropping event because the pointer is not down.
W/ActivityManager(  166): Launch timeout has expired, giving up wake lock!
W/ActivityManager(  166): Activity idle timeout for HistoryRecord{4085cd70 net.schattenkind.nativelove/.LoveLauncher}
W/ActivityManager(  166):   Force finishing activity net.schattenkind.nativelove/.LoveLauncher
I/Process (  166): Sending signal. PID: 9211 SIG: 9
I/ActivityManager(  166): Killing net.schattenkind.nativelove (pid=9211): user's request
I/WindowManager(  166): WIN DEATH: Window{40de8900 net.schattenkind.nativelove/net.schattenkind.nativelove.LoveLauncher paused=true}
E/InputDispatcher(  166): channel '409c5eb8 net.schattenkind.nativelove/net.schattenkind.nativelove.LoveNative (server)' ~ Consumer closed input channel or an error occurred.  events=0x8
E/InputDispatcher(  166): channel '409c5eb8 net.schattenkind.nativelove/net.schattenkind.nativelove.LoveNative (server)' ~ Channel is unrecoverably broken and will be disposed!
I/ActivityManager(  166): Process net.schattenkind.nativelove (pid 9211) has died.
I/WindowManager(  166): WIN DEATH: Window{409c5eb8 net.schattenkind.nativelove/net.schattenkind.nativelove.LoveNative paused=false}
I/WindowManager(  166): WIN DEATH: Window{40a48750 SurfaceView paused=false}
W/InputManagerService(  166): Got RemoteException sending setActive(false) notification to pid 9211 uid 10071
^C

Moe
Party member
Posts: 115
Joined: Thu Dec 22, 2011 10:20 pm

Re: Love-native-android - Development

Post by Moe »

miko wrote:- the fonts are unreadable - I get only white blocks
also known, but I moved that issues after fixing the most annoying chrashes :D. I am not sure, if it is a power of two texture problem, because my Acer Iconia Tab is able to handle them but has the bug also, or if we have some issues with our freetype configuration.
- the volume button does not work - in iyfct.love I could not lower the music volume - had to exit the application (the music was still playing!), then the volume botton worked. However, to stop the music, I had to kill love
Seems like Android does not like our way to play every sound/music directly without using the Java/Android API. I will debug this.
- in order to compile the project succesfully, I had to comment out 3 lines with @Override decorators in LoveRenderView.java (as advised by Eclipse)
I am always unsure if this is caused by a too new or old Java version. Removing @Override has no impact anyhow, it is only a helper during development - the compiler will throw an error if there is no class to override.
T-Bone wrote:However, when I back out from my game and try to launch it again, it crashes.
[/quote]
I am working on that point at the moment.

[EDIT]Fixed some quoting ugliness[/EDIT]
Last edited by Moe on Thu Mar 22, 2012 6:44 pm, edited 1 time in total.
User avatar
T-Bone
Inner party member
Posts: 1492
Joined: Thu Jun 09, 2011 9:03 am

Re: Love-native-android - Development

Post by T-Bone »

Moe wrote:
miko wrote:
Moe wrote:- the fonts are unreadable - I get only white blocks
also known, but I moved that issues after fixing the most annoying chrashes :D. I am not sure, if it is a power of two texture problem, because my Acer Iconia Tab is able to handle them but has the bug also, or if we have some issues with our freetype configuration.
- the volume button does not work - in iyfct.love I could not lower the music volume - had to exit the application (the music was still playing!), then the volume botton worked. However, to stop the music, I had to kill love
Seems like Android does not like our way to play every sound/music directly without using the Java/Android API. I will debug this.
- in order to compile the project succesfully, I had to comment out 3 lines with @Override decorators in LoveRenderView.java (as advised by Eclipse)
I am always unsure if this is caused by a too new or old Java version. Removing @Override has no impact anyhow, it is only a helper during development - the compiler will throw an error if there is no class to override.
T-Bone wrote:However, when I back out from my game and try to launch it again, it crashes.
I am working on that point at the moment.
Oh, right. I forgot what it was I was supposed to confirm in the first place :P
User avatar
miko
Party member
Posts: 410
Joined: Fri Nov 26, 2010 2:25 pm
Location: PL

Re: Love-native-android - Development

Post by miko »

miko wrote: Works for me both on emulator and on HTC Desire. I have orderer a HP TouchPad tablet (yes, the only reason being love-native-android), will install Android 4 on it, so there will be another device to test.
So I have got the HP TouchPad today, installed ICS on it (Android 4.0.3), and run love-native-android. It basically runs as on HTC Desire, except:
- in IYFCT I get only welcome screen (green buildings), then there are only white strips: no trains, no buildings, black boxes instead letters (PO2 issue?) - but on HTC those are OK (at least music plays right)
- as the screen size is 1024x720, many games (and even nogame) are too small

Other than that, a tablet like this one feels great, so I hope to develop some apps in love for it.

Edit: I have installed love-android (java version) on TouchPad, and the iyfct works great there (I get images/letters) until the screen lock comes in - then after unlocking, the letters are black boxes and there are no images.
My lovely code lives at GitHub: http://github.com/miko/Love2d-samples
User avatar
T-Bone
Inner party member
Posts: 1492
Joined: Thu Jun 09, 2011 9:03 am

Re: Love-native-android - Development

Post by T-Bone »

No news or progress? :neko: Not even any april fools jokes?
Moe
Party member
Posts: 115
Joined: Thu Dec 22, 2011 10:20 pm

Re: Love-native-android - Development

Post by Moe »

We had the same discussion yesterday night, but none of use had something cool ready to commit.
You wouldn't believe me that we switched from open source to beer2code development style, so that we only add new features while you send us beer... so no jokes today.
User avatar
T-Bone
Inner party member
Posts: 1492
Joined: Thu Jun 09, 2011 9:03 am

Re: Love-native-android - Development

Post by T-Bone »

Moe wrote:We had the same discussion yesterday night, but none of use had something cool ready to commit.
You wouldn't believe me that we switched from open source to beer2code development style, so that we only add new features while you send us beer... so no jokes today.
That wouldn't be too bad if it were true, I actually brew beer in my spare time. If you guys don't live too far away, I wouldn't minding sending some. Of course, I expect love-native-android to be usable by this summer in return. :neko:
User avatar
T-Bone
Inner party member
Posts: 1492
Joined: Thu Jun 09, 2011 9:03 am

Re: Love-native-android - Development

Post by T-Bone »

No news? :crazy:

I've been thinking recently that, since development here seems rather slow, perhaps I should get involved somehow. I really care about this project, so perhaps it would only be fair if I contributed some. However, I have hardly any knowledge of C++ (although I have used Java quite a bit a few years ago) and I have never worked with anything like this. Do you think that if one of you guys gave me a "guided tour" around the source code, that I could be helpful to you? Or is it too complicated for someone with limited experience?
Moe
Party member
Posts: 115
Joined: Thu Dec 22, 2011 10:20 pm

Re: Love-native-android - Development

Post by Moe »

Sorry, I haven't been a lot at home the last two weeks. I think that I will have more time in the next weeks.
Anyway, if you want to join and help you will need to be familiar with C/C++. You need to understand the original Löve code if some changes are necessary. E.g. we will need to store the (complete) Löve state when the application moves into the background and restore it when it comes to the foreground again. So first thing would be that you get known to C/C++ very well. I don't think that we will have time to teach you this.
Locked

Who is online

Users browsing this forum: No registered users and 3 guests