Is the Nabi Tablet supported?

Hi, we’ve been approached by this company:
http://www.nabitablet.com/tech/

They want us to add our apps to their market.
I personally heard of them but we do not have a device to test with.
Has anyone tried running Corona apps on this kind of Android? [import]uid: 80469 topic_id: 22563 reply_id: 322563[/import]

if you were approached by them, have them give you a test unit and install corona apps and see if they work.

it is like when B&N and Amazon approached us. We needed the tablets here in order to test.

Is is stock android? custom android? like amazon and nook, they are *not* stock android that’s why we have special builds for nook and fire.

c
[import]uid: 24 topic_id: 22563 reply_id: 89932[/import]

I’m not sure actually what kind of android it is I don’t think they have branched out like amazon and BN but who knows…

I will try to get a test unit from them. [import]uid: 80469 topic_id: 22563 reply_id: 89936[/import]

From the page you linked to, it appears it runs android 2.2 and uses a armv7 processor. So it sounds like it will probably work with Corona. Just a assumption, I haven’t heard of that device until you mentioned it. [import]uid: 84637 topic_id: 22563 reply_id: 90040[/import]

Nabi uses stock Android without Google Mobile Services.
As long as your applications don’t use GMS, they should be able to run on Nabi.
[import]uid: 131073 topic_id: 22563 reply_id: 90319[/import]

Submitted 4 apps to them for their launch.

Built for generic android using Build 840. Tested on a moto triumph, and a dell streak 7.

They sent me the following crashdump.
Any thoughts anyone?

I also have requested a demo unit, or a vm - initially they said no to the demo unit,
Hopefully this changes their mind. BTW - their site says they are using ics (4.0).

Thanks!


I’ve gotten the responses from our tech team, and they are showing that the app easily crashes. I’ve attached the error log below. Can you take a look and see if your team will be able to fix the issue?

E/AndroidRuntime(20572): FATAL EXCEPTION: GLThread 336

E/AndroidRuntime(20572): java.lang.IllegalArgumentException: Make sure the Surfa

ceView or associated SurfaceHolder has a valid Surface

E/AndroidRuntime(20572): at com.google.android.gles_jni.EGLImpl._eglCreat

eWindowSurface(Native Method)

E/AndroidRuntime(20572): at com.google.android.gles_jni.EGLImpl.eglCreate

WindowSurface(EGLImpl.java:90)

E/AndroidRuntime(20572): at android.opengl.derived.SwapGLSurfaceView$Defa

ultWindowSurfaceFactory.createWindowSurface(SwapGLSurfaceView.java:473)

E/AndroidRuntime(20572): at android.opengl.derived.SwapGLSurfaceView$EglH

elper.createSurface(SwapGLSurfaceView.java:689)

E/AndroidRuntime(20572): at android.opengl.derived.SwapGLSurfaceView$GLTh

read.guardedRun(SwapGLSurfaceView.java:936)

E/AndroidRuntime(20572): at android.opengl.derived.SwapGLSurfaceView$GLTh

read.run(SwapGLSurfaceView.java:809)

W/InputManagerService( 193): Starting input on non-focused client com.android.i

nternal.view.IInputMethodClient$Stub$Proxy@411c0778 (uid=10117 pid=20572)

W/IInputConnectionWrapper(20572): showStatusIcon on inactive InputConnection

D/ImageWallpaper( 320): onOffsetsChanged: xOffset=0.0, yOffset=0.0, xOffsetStep

=0.0, yOffsetStep=0.0, xPixels=0, yPixels=0

D/ImageWallpaper( 320): Suppressed drawFrame since wallpaper is not visible.

D/ImageWallpaper( 320): onVisibilityChanged: visible=true

D/ImageWallpaper( 320): Visibility changed to visible=true

D/ImageWallpaper( 320): Suppressed drawFrame since redraw is not needed and off

sets have not changed.

I/Sign (19381): Validate session Finish.

D/dalvikvm( 193): GC_EXPLICIT freed 250K, 32% free 47209K/69255K, paused 2ms+7m

s [import]uid: 9070 topic_id: 22563 reply_id: 117238[/import]

We submitted 3 apps to them last week and just got a similar report back from them. They said our apps sometimes crash when you press the Home button. They didn’t know if it was something on their tablet causing it, something in Corona, or something we’re doing in our code. We’re using code to save the state of the app (saving a tiny text file) and I wonder if something there is causing the problem. We’re also using build 840. I tested it on a NOOK and Kindle Fire, but I don’t have a generic Android tablet.

The crash report they sent us is:

E/AndroidRuntime(21288): FATAL EXCEPTION: GLThread 354  
E/AndroidRuntime(21288): java.lang.IllegalArgumentException: Make sure the SurfaceView or associated SurfaceHolder has a valid Surface  
E/AndroidRuntime(21288): at com.google.android.gles\_jni.EGLImpl.\_eglCreateWindowSurface(Native Method)  
E/AndroidRuntime(21288): at com.google.android.gles\_jni.EGLImpl.eglCreateWindowSurface(EGLImpl.java:90)  
E/AndroidRuntime(21288): at android.opengl.derived.SwapGLSurfaceView$DefaultWindowSurfaceFactory.createWindowSurface(SwapGLSurfaceView.java:473)  
E/AndroidRuntime(21288): at android.opengl.derived.SwapGLSurfaceView$EglHelper.createSurface(SwapGLSurfaceView.java:689)  
E/AndroidRuntime(21288): at android.opengl.derived.SwapGLSurfaceView$GLThread.guardedRun(SwapGLSurfaceView.java:936)  
E/AndroidRuntime(21288): at android.opengl.derived.SwapGLSurfaceView$GLThread.run(SwapGLSurfaceView.java:809)  
W/InputManagerService( 193): Starting input on non-focused client com.android.internal.view.IInputMethodClient$Stub$Proxy@41200988 (uid=10116 pid=21288)  
W/IInputConnectionWrapper(21288): showStatusIcon on inactive InputConnection  
D/dalvikvm(20947): GC\_CONCURRENT freed 4558K, 13% free 34077K/38727K, paused 3ms+10ms  
I/Sign (20947): Validate session Finish.  
D/dalvikvm( 193): GC\_EXPLICIT freed 214K, 33% free 46994K/69255K, paused 3ms+5ms  

Anyone have any ideas? Is this something we should submit as a bug? I don’t know a lot about Android development… [import]uid: 9905 topic_id: 22563 reply_id: 117244[/import]

Right after I put my message on the corona forum, I got approval notices on all of the apps I submitted.

When I let them know I was confused - this reply came in…


We discussed with our tech team and decided it’s not a huge issue that would impair the user experience too much. Ideally, we can figure out to resolve the issue eventually, but it’s okay to be approved. In terms of our Android build, we are operating on Ice Cream Sandwich.


So - I guess a chair dance is in order… :wink:
4 more corona generated apps - on a new market place.

I guess I’ll do a logcat on one of my generic android devices to see if it is us or them…
So until then - Cant answer the question - should we submit a bug or not… [import]uid: 9070 topic_id: 22563 reply_id: 117248[/import]

Hey guys. We are looking into getting one of these devices, although we don’t have one now. But we won’t really be able to treat it as a bug until we somehow see confirmation that this is Corona related and a pared-down test case that crashes. Keep us in the loop on what you hear/see…

David [import]uid: 10668 topic_id: 22563 reply_id: 117249[/import]

I have 2 Nabi Tablets, but still working on my first game. will let you know how i getting on. [import]uid: 225288 topic_id: 22563 reply_id: 142579[/import]

I have 2 Nabi Tablets, but still working on my first game. will let you know how i getting on. [import]uid: 225288 topic_id: 22563 reply_id: 142579[/import]

I’m having the same issue with Nabi - they are saying when they tap the “back” button that some games of ours have trouble reopening the first few times - it’s not until the first time that they reopen.

Do you guys have a Nabi tablet now, and are you aware of this bug, or have you been able to locate the cause of the issues above? Thank you!

I’m having the same issue with Nabi - they are saying when they tap the “back” button that some games of ours have trouble reopening the first few times - it’s not until the first time that they reopen.

Do you guys have a Nabi tablet now, and are you aware of this bug, or have you been able to locate the cause of the issues above? Thank you!