Android 4.3 update

[erico]

Hello chaps.

I have the glbasic-debug.apk file of my game on my fone and it always worked perfectly on note II (android 4.2).
So, while I´m off home, I´m constantly testing the game.

There was a recent android update to 4.3, which I did a couple days ago.
First, it is a strange update, full of the usual shovelware. It does very little good things (like the arrow for moving the cursor while typing actually works perfect now) but it brings some bad stuff, like I´m noticing a considerable hit on battery life (argh!).

If you are fine running 4.2, I´m not sure it is worth updating, but I did it so to test the game on a newer android version.
So the game installs fine but when I run it, it has a 50% chance of crashing before launch.
I can´t see a pattern, if I re run it a few times, it will eventually work.

I´m off my main computer till 13/01, so I can´t investigate it further, but it is really strange.
It does feel like it is related to the on_sleep or on_pause things but I can´t be sure.

So just out of curiosity, is anyone running your own game on android 4.3 or even 4.4?
Does it go perfecly for you?

I´m not using extras, just standard GLB compilled apk

Also, you may know about it, but developer options on 4.3 is hidden under:
settings>more>about device and press BUILD NUMBER 7 times to enable it.
This is really stupid.

[spacefractal]

Sounds like its a low memory issue if you ask me with this kind of crash. I'm can only tell if you post in the logcat here.

Also it's can been a back button issue, if you hit on that, then it's might close without androidextras.

[fuzzy70]

My phone was nearly bricked by an update (not 4.3 btw) from my service provider in that it would boot up to the Sony logo then reboot & it would do this constantly. After a call to Sony support, as my provider couldn't help, I used the Sony software to basically download & reflash my phone back to default & when it was all finished my phone was now 4.3.

Once it finished downloading all my purchases & downloads from the playstore (which it done automatically after the 1st boot) I tried them & all was fine. The only GLB related item I had was Spacefractals Greedy Mouse which runs with no problems at all.

One thing I noticed was Opengl-ES is now version 3 rather than 2 under 4.2 but cant see that causing a problem. Also I know Sony's versions of Android are pretty much close to stock with additions like Camera/Walkman app etc whereas Samsung do modify their Android quite a bit so not sure if that is whats causing your problems.

I have to admit I am liking 4.3 more than 4.2 & while I would say my phone was good before it seems just a bit more "complete" for want of a better word lol.

Lee

[erico]

my update to 4.3 was a provider thing.
It is like one every 10 attempts will run the debug.apk
It does not look like a memory thing as I keep it really clean.

Anyways, thanks for the feed, will look into it deeper when I´m back home.
It is just I wanted to take vacation time to test it but it is now a bit harder, but it works once in a very while.

4.3 is taking almost twice battery juice as 4.2 on my end...it is stock from the provider+store. that is really bad.
Oh heck, soon it is out of warranty and cyanogen here me goes just to check.

[spacefractal]

the default attest copy might have fails once, and hence need to clean up data to get the App working (etc closed Down while ... Screen). Androidextras fix that issue by manually copy it by a function and the very important orientation issue. Greedy Mouse uses arround 25-30mb ram.

But my Best get is still a out of memory (like a app drain your battery and hence memory?) issue but can only been checked where its crashed with logcat. It's tell very much.

Happy new year too and still a good vacation to you.

Edit: your Phone have 2gb ram, so I'm guess it's more a assest issue. Thanks to let me know greedy mouse did ran fine (which of course uses androidextras and sdk upgrade).

[erico]

How alien!! It is now working as it always were. I did nothing but reinstalled the same apk more than 10x, also rebooted fone a few times too. Couple days later and it is now working. This is really strange, but good it is working. Thanks for the help.

[spacefractal]

strange, its more look like few assets files was missing and then fails to find them and quit. This happens if you quit the app under ... screen section, then its wont recopy it again, until you delete the data from it. Property Gernot should add a dummy file after copy to makre sure the app dod copy to the end or not to detecting.

Howover this was the directly reason why im looked how to communicate with Java, so that could been fixed (etc if you quit the app under assest copy, its just countinue where you left on on the next start uneffected, and when you update, only updated files got copied). Im did have similar issues in the starting with crashes in the start due this reason.

Im happy im did all loading thing in a function rather than uses the glbasic commands directly.

[erico]

It is really strange Space, it happened again a few hours ago. But in a lesa intensity than before, now it is working again. It is a very strange behaviour. I'm starting to think it is related to the back button. I have no proper exit in game yet and am not sure it could be related to the on pause or on quit things i'm yet to imlement. Thing is, that whatever that is, it is going on the android 4.3, cause that never happened on 4.2 before.

[spacefractal]

Also many devices have limits how much memory each app can been used, which is often around 32-64mb on many devices. The app could have crash due that.

Alteernative its could been that damn Back button, or a failed assests copy thing (which quit glbasic directly, which can been disabled with AndroidExtas).

So hence im want to see the crash logcat came with, which would tell more.

If the heapsize is a reason, you could try to add that to the manifest:
android:largeHeap="true"

under the <application tag (http://developer.android.com/guide/topics/manifest/application-element.html).

[spacefractal]

Just now, im have found a important NullPointer crash (another one), which happens when doing any keypresses outside the game. That is now being fixed and do a quick release when done.

[spacefractal]

im have nearly fixed the pause/resume issue and the eventuelly ouya nulpointer issue when ouya is not used.

when EnableBackButton(TRUE) is set, its will quit at is will normally, but when you do that with EnableBackButton(FALSE), its will instead launch the main launcher (so the app is sent to background), without it quit. Music etc is still been played, but it up to you to eventuelly stop it.

Im update to android v1.6.1 for the small file now, and to been included with the sdk tomorrow.

[erico]

I will have to check this all when I´m back home again (I should be home on 13/january).
Thanks for all the efforts Space!