Graphics 2.0 compatibility mode: no display on Android device

Solar2D General Questions/Discussion
#1

So my app is currently working great with 1202.  I decided to try moving to build 2100 and use the graphicsCompatibility = 1 setting in the config.lua file and see how it would go.  Developing on Windows, just installing the new SDK and running the app in the Simulator worked great.  No problems other than my use of a scrollView was positioned wrong.  I had seen that in the notes, so I made adjustments to fix that, and had that working in short time.

Did a build and copied it to my Android test device - a Samsung Galaxy Tab 10.1 - and the app launched, but nothing displayed.  Audio played, and it went from the opening company logo to the menu (which I know because the audio changed), but nothing displayed on the screen.  I was using adb logcat Corona:v *:s to see what happened, but no errors of any kind were reported.

Thinking that maybe one of the changes I had made to do the custom scroll bar in the scrollView (and get the scrollView positioning corrected) had broken something, I went back to the version that built and worked fine on the device in build 1202, and tried that with 2100.  Same thing.  No audio, no errors.

I then tried commenting out the scrollView code to see if it was the issue.  But it wasn’t.  Finally, I removed everything from my main.lua file other than the function that displays the opening logo.  Built and copied that to the device and same thing.  No errors, but no display on the Android device.

Anyone else run into something like this?

One other thing that I noticed that was weird was that when I went to uninstall the app in Settings | Applications, the app size was listed as 6.01 MB in all cases, yet on build 1202 (which worked), the app size would be around 47.2 MB.  Not sure why that would be since I wasn’t getting errors about images not being found.

I went back to build 1202 and built again, and indeed, the app built and ran fine on the device.

Searched but no one else seemed to be having this issue.

I would like to move to 2100, but can’t move to Graphics 2.0 natively at the moment since I have a lot of setReferencePoint calls.  Was hoping that the graphics compatibility mode would actually work and be quick to implement, but doesn’t appear to work for me.
 

Would appreciate any pointers or suggestions on what might be happening.

#2

I just checked your device processor (nvidia tegra 2).  As I thought from your title.

I started a topic on this issue on the 21st December here:

http://forums.coronalabs.com/topic/42581-black-screen-loading-hello-world-sample-app-on-android-20132099/

Please can you post your device and issues in here, as the more people showing the same issues with the same processor, the quicker we can get this fixed.

Something went wrong for nvidia tegra 2 devices on the update from 2013.2099 to 2013.2100

Thanks

PS All is fine up to and including daily build 2013.2099.  That’s what I’m running in the mean time.

Try building Hello World, it’s black screen too.  There’s nothing you can do to make it work if you use 2013.2100 and above.

#3

Icy, thanks for alerting me to that thread.  I did a search and nothing came up, so glad to know about it.

I posted a comment in the thread.

That seems like a really ugly bug to make it into a public release!  And one that really should have been caught by QA.

#4

I have a similar issue. I had an update fail on Samsung’s market due to some of the graphics not showing up. It seemed to be in all of the scrollviews on a Samsung Galaxy 3 tablet. This also occured with a customer using this same device. Is this a bug? Or, is there a hack for using the scrollview on certain devices. It’s been working just fine on other device and is currently working on other android devices.

Thanks,

#5

Can’t say, Bead.  The issues that we were seeing was no display at all and seemed to be limited to Tegra 2-based devices.  Don’t think the Galaxy 3 has one of those, or a Tegra chipset at all.

Maybe it is something different?

#6

It does sound different. It’s interesting how it is to specific devices. My issue seems to be happening inside of scrollView, but only on certain devices.

Thanks and hope you figure yours out soon!

Kiffin

#7

Thanks, Bead Pond.  I am just happy that it wasn’t my code that was the problem.  :slight_smile:

Definitely hoping that the Corona team can get it fixed soon.  Seems very odd that the chipset that powered the first group of popular Android tablets would have to get left out.

Hope you figure out what yours is as well.

#8

Brent (from Corona) said that the latest build addressed some container, alpha and potentially related issues. See how that might help you. I’ll let you know how mine turns out, and I’ll share anything that provides a fix to the issue. It’s a popular device and it’s not very new in device terms.

#9

Oh, good to know.  I think I decided to hold off on moving to 2.0 (even with compatibility mode) until I get the app update out the door.  Done too much testing already to go back and do it all again.  But glad that they are making progress, so can hopefully move to it for an update.

#10

These issues were fixed in 2130, but another bug with text crept in, so if you need output from display.newText, wait until 2131 or later since it’s been fixed as well. 

Rob

#11

Thanks Rob! Brent asked me to check out a problem the problem I was having, and I encountered the newText issue. Thank you for the confirmation! So good!

#12

I just checked your device processor (nvidia tegra 2).  As I thought from your title.

I started a topic on this issue on the 21st December here:

http://forums.coronalabs.com/topic/42581-black-screen-loading-hello-world-sample-app-on-android-20132099/

Please can you post your device and issues in here, as the more people showing the same issues with the same processor, the quicker we can get this fixed.

Something went wrong for nvidia tegra 2 devices on the update from 2013.2099 to 2013.2100

Thanks

PS All is fine up to and including daily build 2013.2099.  That’s what I’m running in the mean time.

Try building Hello World, it’s black screen too.  There’s nothing you can do to make it work if you use 2013.2100 and above.

#13

Icy, thanks for alerting me to that thread.  I did a search and nothing came up, so glad to know about it.

I posted a comment in the thread.

That seems like a really ugly bug to make it into a public release!  And one that really should have been caught by QA.

#14

I have a similar issue. I had an update fail on Samsung’s market due to some of the graphics not showing up. It seemed to be in all of the scrollviews on a Samsung Galaxy 3 tablet. This also occured with a customer using this same device. Is this a bug? Or, is there a hack for using the scrollview on certain devices. It’s been working just fine on other device and is currently working on other android devices.

Thanks,

#15

Can’t say, Bead.  The issues that we were seeing was no display at all and seemed to be limited to Tegra 2-based devices.  Don’t think the Galaxy 3 has one of those, or a Tegra chipset at all.

Maybe it is something different?

#16

It does sound different. It’s interesting how it is to specific devices. My issue seems to be happening inside of scrollView, but only on certain devices.

Thanks and hope you figure yours out soon!

Kiffin

#17

Thanks, Bead Pond.  I am just happy that it wasn’t my code that was the problem.  :slight_smile:

Definitely hoping that the Corona team can get it fixed soon.  Seems very odd that the chipset that powered the first group of popular Android tablets would have to get left out.

Hope you figure out what yours is as well.

#18

Brent (from Corona) said that the latest build addressed some container, alpha and potentially related issues. See how that might help you. I’ll let you know how mine turns out, and I’ll share anything that provides a fix to the issue. It’s a popular device and it’s not very new in device terms.

#19

Oh, good to know.  I think I decided to hold off on moving to 2.0 (even with compatibility mode) until I get the app update out the door.  Done too much testing already to go back and do it all again.  But glad that they are making progress, so can hopefully move to it for an update.

#20

These issues were fixed in 2130, but another bug with text crept in, so if you need output from display.newText, wait until 2131 or later since it’s been fixed as well. 

Rob