Quick Links: Download Gideros Studio | Gideros Documentation | Gideros community chat | DONATE
V2014.01, Android and Landscape mode — Gideros Forum

V2014.01, Android and Landscape mode

Jeff_KanaziJeff_Kanazi Member
edited March 2014 in Bugs and issues
Hi,

There appears to be some issue with the 2014.01 release and orientation when building Android apps. In Gideros Studio the project is defined with orientation Landscape Left. In the AppManifest.xml file it is defined as Landscape as well (android:screenOrientation="Landscape"). When started the application does start in Landscape mode but it looks like the Gideros activity does not see that and rotates it at 90 degrees and the screen is all messed up.

With earlier versions the same setup worked just fine.

Workaround is to set android:screenOrientation="portrait" in the manifest - that makes the app show in ;landscape mode and it is usable but this does look crappy especially on tablets with soft Android screen buttons. One would expect those buttons to be under the screen and not on the side. Same with notifications etc.

Is there something we can do to address this? Basically have the app start in Landscape mode and work properly? We have tried some things in the Lua code but without success.

Thanks!

Comments

  • Another interesting thing - so in order to test other things we have changed screenOrientation to Portrait but the app crashes every time after the screen locked with the following error:

    03-25 13:51:45.553: W/WindowManager(518): Window freeze timeout expired.
    03-25 13:51:45.553: W/WindowManager(518): Force clearing orientation change: Window{42f738a8 u0 com.ijs.phyzzlets/com.ijs.phyzzlets.PhyzzletsActivity}
    03-25 13:51:45.553: W/WindowManager(518): Force clearing orientation change: Window{422873c8 u0 SurfaceView}
    03-25 13:51:45.553: W/WindowManager(518): Force clearing orientation change: Window{427be220 u0 com.android.systemui.ImageWallpaper}
    03-25 13:51:46.253: E/dalvikvm(16286): JNI ERROR: env->self != thread-self (0x66f22008 vs. 0x41afa3c8); auto-correcting
    03-25 13:51:46.253: E/dalvikvm(16286): JNI ERROR: env->self != thread-self (0x66f22008 vs. 0x41afa3c8); auto-correcting
    03-25 13:51:46.293: A/libc(16286): Fatal signal 11 (SIGSEGV) at 0x00000008 (code=1), thread 18407 (Thread-945)
    03-25 13:51:46.353: I/DEBUG(121): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
    03-25 13:51:46.353: I/DEBUG(121): Build fingerprint: 'google/nakasi/grouper:4.4.2/KOT49H/937116:user/release-keys'
    03-25 13:51:46.353: I/DEBUG(121): Revision: '0'
    03-25 13:51:46.353: I/DEBUG(121): pid: 16286, tid: 18407, name: Thread-945 >>> com.ijs.phyzzlets <<<
    03-25 13:51:46.353: I/DEBUG(121): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000008
    03-25 13:51:46.543: I/DEBUG(121): r0 00000000 r1 42283128 r2 66f77ee0 r3 6ac4f0f0
    03-25 13:51:46.543: I/DEBUG(121): r4 00000000 r5 66f22008 r6 00000000 r7 66f77e90
    03-25 13:51:46.543: I/DEBUG(121): r8 6afe3b10 r9 66f77e88 sl 66f22018 fp 6afe3b24
    03-25 13:51:46.543: I/DEBUG(121): ip 6ad45a29 sp 6afe3b00 lr 414f6bd0 pc 6ad458e4 cpsr a00d0030
    03-25 13:51:46.543: I/DEBUG(121): d0 0000002200000010 d1 0000000000000000
    03-25 13:51:46.543: I/DEBUG(121): d2 0000000000000000 d3 0000000000000000
    03-25 13:51:46.543: I/DEBUG(121): d4 0000000000000000 d5 00000000bf800000
    03-25 13:51:46.543: I/DEBUG(121): d6 3f8000003f800000 d7 3f8000003f800000
    03-25 13:51:46.543: I/DEBUG(121): d8 0000000000000000 d9 0000000000000000
    03-25 13:51:46.543: I/DEBUG(121): d10 0000000000000000 d11 0000000000000000
    03-25 13:51:46.543: I/DEBUG(121): d12 0000000000000000 d13 0000000000000000
    03-25 13:51:46.543: I/DEBUG(121): d14 0000000000000000 d15 0000000000000000
    03-25 13:51:46.543: I/DEBUG(121): d16 000012e63a661e4b d17 3f80deb527f7ca4b
    03-25 13:51:46.543: I/DEBUG(121): d18 bfe491b7523c161c d19 be5ad09a65948130
    03-25 13:51:46.543: I/DEBUG(121): d20 bf29d48edf86a0c3 d21 0000000000000000
    03-25 13:51:46.543: I/DEBUG(121): d22 3ec71de357b1fe7d d23 3fe7f910d768cfb0
    03-25 13:51:46.543: I/DEBUG(121): d24 bfe491b7523c161c d25 3ff0000000000000
    03-25 13:51:46.543: I/DEBUG(121): d26 be7d5c7abc800000 d27 3fd00dde512e60a0
    03-25 13:51:46.543: I/DEBUG(121): d28 bfa370216fbbd292 d29 3fb66140cd77471f
    03-25 13:51:46.543: I/DEBUG(121): d30 be7d5c7abc62e63d d31 3f114d2e4f9303d2
    03-25 13:51:46.543: I/DEBUG(121): scr 60000011
    03-25 13:51:46.543: I/DEBUG(121): backtrace:
    03-25 13:51:46.543: I/DEBUG(121): #00 pc 000628e4 /data/app-lib/com.ijs.phyzzlets-2/libgideros.so (ApplicationManager::drawFrame()+3)
    03-25 13:51:46.543: I/DEBUG(121): #01 pc 0001dbcc /system/lib/libdvm.so (dvmPlatformInvoke+112)
    03-25 13:51:46.543: I/DEBUG(121): stack:
    03-25 13:51:46.543: I/DEBUG(121): 6afe3ac0 41583c74 /system/lib/libdvm.so
    03-25 13:51:46.543: I/DEBUG(121): 6afe3ac4 4152ba69 /system/lib/libdvm.so
    03-25 13:51:46.543: I/DEBUG(121): 6afe3ac8 42414104 /dev/ashmem/dalvik-heap (deleted)
    03-25 13:51:46.543: I/DEBUG(121): 6afe3acc 42414100 /dev/ashmem/dalvik-heap (deleted)
    03-25 13:51:46.543: I/DEBUG(121): 6afe3ad0 00000000
    03-25 13:51:46.543: I/DEBUG(121): 6afe3ad4 42414104 /dev/ashmem/dalvik-heap (deleted)
    03-25 13:51:46.543: I/DEBUG(121): 6afe3ad8 42414100 /dev/ashmem/dalvik-heap (deleted)
    03-25 13:51:46.543: I/DEBUG(121): 6afe3adc 4152bacd /system/lib/libdvm.so
    03-25 13:51:46.543: I/DEBUG(121): 6afe3ae0 00000000
    03-25 13:51:46.543: I/DEBUG(121): 6afe3ae4 41afa390 [heap]
    03-25 13:51:46.543: I/DEBUG(121): 6afe3ae8 00000000
    03-25 13:51:46.543: I/DEBUG(121): 6afe3aec 415881f0 /system/lib/libdvm.so
    03-25 13:51:46.543: I/DEBUG(121): 6afe3af0 423ceef0 /dev/ashmem/dalvik-heap (deleted)
    03-25 13:51:46.543: I/DEBUG(121): 6afe3af4 4006a384
    03-25 13:51:46.543: I/DEBUG(121): 6afe3af8 42283128 /dev/ashmem/dalvik-heap (deleted)
    03-25 13:51:46.543: I/DEBUG(121): 6afe3afc 66f22008
    03-25 13:51:46.543: I/DEBUG(121): #00 6afe3b00 62b6a798 /dev/ashmem/dalvik-LinearAlloc (deleted)
    03-25 13:51:46.543: I/DEBUG(121): 6afe3b04 66f22008
    03-25 13:51:46.543: I/DEBUG(121): 6afe3b08 00000000
    03-25 13:51:46.543: I/DEBUG(121): 6afe3b0c 414f6bd0 /system/lib/libdvm.so (dvmPlatformInvoke+116)
    03-25 13:51:46.543: I/DEBUG(121): 6afe3b10 66f77e88
    03-25 13:51:46.543: I/DEBUG(121): 6afe3b14 00000001
    03-25 13:51:46.543: I/DEBUG(121): 6afe3b18 00000008
    03-25 13:51:46.543: I/DEBUG(121): 6afe3b1c 42283128 /dev/ashmem/dalvik-heap (deleted)
    03-25 13:51:46.543: I/DEBUG(121): 6afe3b20 00000000
    03-25 13:51:46.543: I/DEBUG(121): 6afe3b24 41527127 /system/lib/libdvm.so (dvmCallJNIMethod(unsigned int const*, JValue*, Method const*, Thread*)+402)
    03-25 13:51:46.543: I/DEBUG(121): 6afe3b28 66f77e88
    03-25 13:51:46.543: I/DEBUG(121): 6afe3b2c 6ac8cefc /data/dalvik-cache/data@app@com.ijs.phyzzlets-2.apk@classes.dex
    03-25 13:51:46.543: I/DEBUG(121): 6afe3b30 6ad45a29 /data/app-lib/com.ijs.phyzzlets-2/libgideros.so (Java_com_giderosmobile_android_player_GiderosApplication_nativeDrawFrame)
    03-25 13:51:46.543: I/DEBUG(121): 6afe3b34 66f22018
    03-25 13:51:46.543: I/DEBUG(121): 6afe3b38 00000000
    03-25 13:51:46.543: I/DEBUG(121): 6afe3b3c 00000000

    What might this be?
  • ar2rsawseenar2rsawseen Maintainer
    Interesting, just released a landscape app:
    https://play.google.com/store/apps/details?id=com.jenots.x2048

    do you have same problems with it?

    And I don't if that make any changes, but I define: android:screenOrientation="landscape" in manifest (lowercased)
  • Interesting. There must be something going on when a project is exported for the first time from a new Gideros Studio version but I could not figure what exactly.

    So Exporting the project again to a new folder (not the same folder I have been using with the previous release of Gideros) and literary moving over folder by folder assets, libs, src, and AndroidManifest somehow fixed the problem in the new folder. Then I copied the new project folder back over the original project folder and that one started working too.

    Perhaps a file that Eclipse creates when not there (the new folder) but does not know to re-create when the source files are touched by the complete Gideros export? It is obviously not related to assets, libraries or java source files.

    Anyway, problem solved. ... It is really painful to upgrade to the next Gideros release for apps with multiple plugins... BTW the weird crash is gone too.

    Thanks
Sign In or Register to comment.