When I open my app on a device build and go then go back to the main menu and then I wish to return to my app, the whole screen (minus the textfields) appear black for roughly 5 seconds before it properly loads. Am I supposed to code something to memory? I’ve never worked with memory so I don’t really know what I should do. Any help is greatly appreciated! [import]uid: 35535 topic_id: 33160 reply_id: 333160[/import]
Are there any errors poping up in the terminal? [import]uid: 130035 topic_id: 33160 reply_id: 131690[/import]
Looking for a little more info too…
iOS, Android? Any specifics about the Device, OS version, and Corona version? (The D.O.C. info please 
)
Do you have a default.png graphic to show while the app loads? Or is this not from a coldstart, but from a suspend/resume (or both)?
Are you saying just your textfields appear (and immediately, or with a delay)? Are they native textfields, or regular corona text objects (display.newText)?
[import]uid: 79933 topic_id: 33160 reply_id: 131696[/import]
And also, are you using director? [import]uid: 130035 topic_id: 33160 reply_id: 131698[/import]
Okay I’ll try my best to answer all the questions but I’m new at this and there are some terms I don’t fully understand.
-
In the corona terminal no errors were reported
-
The device is an android nexus 7
-
Corona version is giving me this “Version 2012.840 (2012.06.19)”. I got that from clicking the “about corona simulator”
-
I have these files included in the folder: Icon-ldpi.png (36x36 image), Icon-mdpi.png (48x48 image),
Icon-hdpi.png (64x64 image), Icon-xhdpi.png (96x96 image) and an Icon.png and Default.png (both 100x100) -
On the initial start-up, my default.png file shows while the app loads and now everything everything loads perfectly and is indistinguishable from corona’s simulator. When I leave the app (not closing out of the app though) to go to say google chrome and then I click it’s icon to reopen my app, this is when it happens. Everything except the multiple textfields (native textfields) becomes a black screen and the textfields show up with their perspective text that was either provided upon initial startup of the app or altered by the user before changing screens (ex going to google chrome app)
-
I am not using director class. I currently have no different screens to transition to so I’m not using anything besides my main.lua file. I will eventually need to include a director class though to include a “how to” manual.
-As a side note. I’m having trouble replicating this error but from what I remember sometimes in addition the the screen temporarily going black for roughly 5 seconds. The text within the textfield would become little squares and vertical rectangles. For instance “text” would become “[][][][]” but with the rectangles colored black. Letters like “a” will be more of a square shape while longer letters like “g” were more similar to a rectangle
When I have time I’ll try to replicate that last problem but I think I just transitioned out of my screen differently and it gave me a different problem. To be more clear, the nexus has a button on the right that shows apps running int he background and then a backwards arrow that takes you back to where you came from. Also I might also add that it’s a free build. I’ve considered that may also contribute to the problem?
Thanks again for your help guys, I appreciate your help.
[import]uid: 35535 topic_id: 33160 reply_id: 131705[/import]
Ahh, it’s a nexus 7, and you’re using build 840, the last release version it sounds like.
I think that release was before that android version came out, not sure though… So maybe that corona SDK version isn’t compatible with the newer android version… I’m running a more recent version (971 I think), and my app runs fine / wakes up etc ok from suspend on the nexus 7…
Maybe someone else knows specifically about that version of corona with your android version (what android version is on your nexus?)
The good news is… CoronaLabs is about to release a new / updated version of the Corona SDK, for the latest iOS, Android, Nook versions. You should be able to update to that very soon… [import]uid: 79933 topic_id: 33160 reply_id: 131706[/import]
Update is already out, New daily build is #971 [import]uid: 62706 topic_id: 33160 reply_id: 131723[/import]
Yes, pick up the latest public build and see if things get better.
Build 840 came out before the Nexus 7 and there were several things that didn’t play well with Android 4.1 that have been fixed since.
If you’re still having problems, perhaps seeing your code could let us have a better insite. Also make sure you have the Android Debug Bridge tools (adb) installed. You can do the command:
adb logcat
from your command line and see what messages the device is spewing.
[import]uid: 19626 topic_id: 33160 reply_id: 131765[/import]
Are there any errors poping up in the terminal? [import]uid: 130035 topic_id: 33160 reply_id: 131690[/import]
Looking for a little more info too…
iOS, Android? Any specifics about the Device, OS version, and Corona version? (The D.O.C. info please )
Do you have a default.png graphic to show while the app loads? Or is this not from a coldstart, but from a suspend/resume (or both)?
Are you saying just your textfields appear (and immediately, or with a delay)? Are they native textfields, or regular corona text objects (display.newText)?
[import]uid: 79933 topic_id: 33160 reply_id: 131696[/import]
And also, are you using director? [import]uid: 130035 topic_id: 33160 reply_id: 131698[/import]
Okay thanks, I’ll update and give it a try. Can you give me some info about the Android Debug Bridge tools please? When I was reading about it it seemed like a program you install on a pc that connects to whichever device you’re testing on but I don’t know if that’s right. [import]uid: 35535 topic_id: 33160 reply_id: 131786[/import]
Okay I’ll try my best to answer all the questions but I’m new at this and there are some terms I don’t fully understand.
-
In the corona terminal no errors were reported
-
The device is an android nexus 7
-
Corona version is giving me this “Version 2012.840 (2012.06.19)”. I got that from clicking the “about corona simulator”
-
I have these files included in the folder: Icon-ldpi.png (36x36 image), Icon-mdpi.png (48x48 image),
Icon-hdpi.png (64x64 image), Icon-xhdpi.png (96x96 image) and an Icon.png and Default.png (both 100x100) -
On the initial start-up, my default.png file shows while the app loads and now everything everything loads perfectly and is indistinguishable from corona’s simulator. When I leave the app (not closing out of the app though) to go to say google chrome and then I click it’s icon to reopen my app, this is when it happens. Everything except the multiple textfields (native textfields) becomes a black screen and the textfields show up with their perspective text that was either provided upon initial startup of the app or altered by the user before changing screens (ex going to google chrome app)
-
I am not using director class. I currently have no different screens to transition to so I’m not using anything besides my main.lua file. I will eventually need to include a director class though to include a “how to” manual.
-As a side note. I’m having trouble replicating this error but from what I remember sometimes in addition the the screen temporarily going black for roughly 5 seconds. The text within the textfield would become little squares and vertical rectangles. For instance “text” would become “[][][][]” but with the rectangles colored black. Letters like “a” will be more of a square shape while longer letters like “g” were more similar to a rectangle
When I have time I’ll try to replicate that last problem but I think I just transitioned out of my screen differently and it gave me a different problem. To be more clear, the nexus has a button on the right that shows apps running int he background and then a backwards arrow that takes you back to where you came from. Also I might also add that it’s a free build. I’ve considered that may also contribute to the problem?
Thanks again for your help guys, I appreciate your help.
[import]uid: 35535 topic_id: 33160 reply_id: 131705[/import]
Ahh, it’s a nexus 7, and you’re using build 840, the last release version it sounds like.
I think that release was before that android version came out, not sure though… So maybe that corona SDK version isn’t compatible with the newer android version… I’m running a more recent version (971 I think), and my app runs fine / wakes up etc ok from suspend on the nexus 7…
Maybe someone else knows specifically about that version of corona with your android version (what android version is on your nexus?)
The good news is… CoronaLabs is about to release a new / updated version of the Corona SDK, for the latest iOS, Android, Nook versions. You should be able to update to that very soon… [import]uid: 79933 topic_id: 33160 reply_id: 131706[/import]
This was a known Android hardware acceleration bug that we had to work-around. This issue was fixed in the newest release build, which you can download here…
http://developer.coronalabs.com/downloads/corona-sdk
[import]uid: 32256 topic_id: 33160 reply_id: 131794[/import]
Update is already out, New daily build is #971 [import]uid: 62706 topic_id: 33160 reply_id: 131723[/import]
Android Debug Bridge is a series of programs you can run from the command line and do things with an android device that is plugged into that computer via a USB cable (tethered). You get commands iike:
adb install /path/to/your/app.apk
to install an app you just built with Corona or likewise
adb uninstall com.yoursite.yourapp
(where com.yoursite.yourapp is your app identifer) and the all important:
adb logcat
which dumps out the console log of the device to your terminal screen. You also get a program called ddms (I think) which is a GUI based app, but it can capture screen shots from your device.
Google “install adb for mac” or “install adb for windows” depending on your OS to find instructions on setting it up. [import]uid: 19626 topic_id: 33160 reply_id: 131826[/import]
Thanks robmircale! And by the way, once I updated the problem was fixed! [import]uid: 35535 topic_id: 33160 reply_id: 131843[/import]
Yes, pick up the latest public build and see if things get better.
Build 840 came out before the Nexus 7 and there were several things that didn’t play well with Android 4.1 that have been fixed since.
If you’re still having problems, perhaps seeing your code could let us have a better insite. Also make sure you have the Android Debug Bridge tools (adb) installed. You can do the command:
adb logcat
from your command line and see what messages the device is spewing.
[import]uid: 19626 topic_id: 33160 reply_id: 131765[/import]
Okay thanks, I’ll update and give it a try. Can you give me some info about the Android Debug Bridge tools please? When I was reading about it it seemed like a program you install on a pc that connects to whichever device you’re testing on but I don’t know if that’s right. [import]uid: 35535 topic_id: 33160 reply_id: 131786[/import]