Starling Forum

1. 

   gp
   

   Novice Bird
   Joined: Mar '12
   Posts: 6

   Are there any specific hardware requirements for Starling/Stage3D mobile? I cannot get my AIR 3.2 app that uses Starling to run on an OEM tablet with 1 GHz ARM Cortex-A8 processor and 800x480 screen. I get the wrong wmode error message at startup. Tried different combinations of swf-version(13,14,15) and rendermode(direct/gpu) but no luck so far. Runs fine on desktop and device emulator.

   Appreciate any inputs/suggestions.

   Posted 1 year ago #
2. 

   Daniel
   

   Primary Feather
   Joined: Jan '10
   Posts: 2,461

   Hm, sorry, I don't know of any list containing supported hardware. I'll ask someone from Adobe if there is such a list somewhere!

   Posted 1 year ago #
3. 

   gp
   

   Novice Bird
   Joined: Mar '12
   Posts: 6

   Hi Daniel,

   Thanks for your response. Wondering if you heard back from Adobe regarding this. I am still stuck with this issue.

   Thanks again.

   Posted 1 year ago #
4. 

   Daniel
   

   Primary Feather
   Joined: Jan '10
   Posts: 2,461

   No response yet, sorry!

   Posted 1 year ago #
5. 

   tfartek
   

   Hatchling
   Joined: Feb '12
   Posts: 2

   The wrong wmode error can be solved by going into your project's XML file and finding this: <!-- <renderMode></renderMode> -->

   and replacing it with this: <renderMode>direct</renderMode>

   Posted 1 year ago #
6. 

   fabiobiondi
   

   Senior Bird
   Joined: Mar '12
   Posts: 66

   Hi GP,
   it's weird.

   Here the device I'm using and works fine with Starling:
   - HTC Nexus One (2.3.x), <-- this is an old device with 800x480 resolution, just like yours
   - Samsung Galaxy(4.0.3),
   - Tablet ASUS TF101 (Android 4.0.3)
   - Samsung Galaxy Tab 7'' (2.3.x)

   Fabio

   Posted 1 year ago #
7. 

   lokhy
   

   Senior Bird
   Joined: Sep '11
   Posts: 68

   I have the same problem with ARNOVA 9G2 (A8 cortex cpu) :<

   Posted 1 year ago #
8. 

   gp
   

   Novice Bird
   Joined: Mar '12
   Posts: 6

   Finally, nailed it!!

   Adding this line to the application.xml under the android section solves the
   issue.

   <colorDepth>16bit</colorDepth>

   Documentation says the default is 32bit from AIR 3.0 onwards. Apparently, this causes Stage3D to fail on some devices.

   Thanks to this apk that worked on the same problem device, I was able to narrow it down to this manifest change.

   I would really appreciate thoughts from the experts here on how exactly the color depth could have caused the issue and if this fix would cover all the second-class android devices out there.

   Posted 1 year ago #
9. 

   Jeff
   

   Moderating Owl
   Joined: Nov '11
   Posts: 1,302

   I assume in both cases the apks you built were captive runtimes that bundled the AIR version?

   So would developers build both a 16bit and 32bit version and sell both on Android stores if they didn't want all android devices forced into 16bit mode? Seems there is no way to control this on startup or runtime right?

   Posted 1 year ago #
10. 

    famicomboy
    

    Senior Bird
    Joined: Jan '12
    Posts: 75

    This might be old but I found a devices list here:

    http://www.adobe.com/flashplatform/certified_devices/

    Posted 1 year ago #
11. 

    danieldourado_2
    

    Moderating Bird
    Joined: Feb '12
    Posts: 207

    I don't think this list is relevant, as it shows compatible devices with Adobe Flash Player, no Adobe Air... You can see Apple devices are not there...

    Posted 1 year ago #
12. 

    gp
    

    Novice Bird
    Joined: Mar '12
    Posts: 6

    Jeff, they both were normal apks, not bundles.

    Having the app store pick the right version would be nice, so would be the ability to specify the color depth at runtime, perhaps based on the device's memory size. I don't know of any way yet to do this.

    Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.