Hi together,
developing quite a few weeks with very good progress on my new game. After some time I tried Android deployment, but it no longer works for any kind of project. None of the sample projects are working (they did before, I am pretty certain). I tried the button example using IntellijIDEA and getting the following message with seems quite usual:
.....
Launching application: de.blabla.button/com.giderosmobile.android.ButtonActivity.
DEVICE SHELL COMMAND: am start -n "de.blabla.button/com.giderosmobile.android.ButtonActivity"
Starting: Intent { cmp=de.blabla.button/com.giderosmobile.android.ButtonActivity }
.....
But screen remains black, no guiders splash screen shping up. So I started DDMS to give some additional info and it shows:
10-21 15:55:06.228: W/ActivityManager(85): Activity idle timeout for HistoryRecord{44eaece0 de.blabla.button/com.giderosmobile.android.ButtonActivity}
The funny thing is, the generated .apk file is working on a real device, so it seems to be a emulator issue? However emulator is working fine with a project not using gideros. I tried thousands of different SDK settings (SDK 4.1.2, 4.0.03, 2.2,...) but with no solutions.
Any help? Best regards
Radiesel
PS: It's always the same, on Mac OS/X and Windows 7, no difference....
Comments
I actually didn't know that Gideros could work with emulators at all. After switching to Gideros (and using Gideros Android player) I forgot what an emulator was. And thanks god, my PC could not handle it, it was loading too long and working so slow.
Did the Gideros apps on emulator ran fast enough for you? Because really in B.G. (Before Gideros) Android emulator gave me such a pain. It was never working normally.
Likes: gorkem, atilim
1. OpenGL support is not complete.
2. It's too slow.
regards
Radiesel
To test different resolutions/devices, you can use the predefined set of resolutions in Gideros Desktop Player.
could this be a problem with your Android Virtual Device itself? Try opening AVD manager and see if the AVD are listed as valid (green tick), repairable or failed to load. There is an option to repair which might help...
I've got one AVD installed like this:
AVD Name=Test
Target Name= Android 4.1
Platform=4.1
API Level=16
CPU/ABI = ARM (armeabi-v7a)
You could add an AVD just like this and see if it works...
https://github.com/gideros/gideros
https://www.youtube.com/c/JohnBlackburn1975
Main reason for using an AVD was that I wanted to try new Amazon Kindle Fire HD device. I know it has resolution which is available in the player, but since gideros does not support In-App-Billing, I was thinking about writing my own module. As far as I understand, Kindle Fire uses Android, so gideros projects should work without problems, except the billing features...
Looks like I will have to buy one - not that expensive ;-))
Thank you very much!
Radiesel
I realized that and I am very happy that it's included now. Great work, thanks!
Radiesel
https://github.com/gideros/gideros
https://www.youtube.com/c/JohnBlackburn1975
yes, I tried that, but it's not working. The strange thing is, I got emulator working, but only android Api level 8,10 (armeabi). As soon as I add I device using Api 15 or 16 (with armeabi-v7a), it is not selectable as a valid device in the project settings. I have setup Android 4.1.2 as external library and also have
uses-sdk android:minSdkVersion="8"
So my understanding is, it should work for any device using Android 2.2 and above. But for any reason I don't know it does not work for device above android 2.3
regards
Radiesel
I guess the reason was, that I setup google Api 4.1.2 instead of Android 4.1.2. (shame...)
However starting the Kinde Fire emulator on my MacBook Air 13 took forever (3-4 minutes). So basically it's working, although useless.
Guys, thanks for all your help!
Radiesel