Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: Android - Skobbler doesn't support 64 bits processor

  1. #1
    Neuer skobbler
    Join Date
    16.11.2015
    Posts
    2

    Android - Skobbler doesn't support 64 bits processor

    Hi,

    Can I know when you will share :
    - jniLibs/arm64-v8a/libngnative.so
    - jniLibs/x86_64/libngnative.so

    Because today, Skobbler is not working on Android 64bits devices.

    Thx

  2. #2
    Oberskobbler
    Join Date
    22.07.2014
    Posts
    399
    Indeed for the moment we don’t have a build for arm64. It’s on our roadmap for the next releases.

    We are working on the feature's list for the next release, but we can't guarantee that will be included on the first release
    Last edited by Adela_Silvia; 16.11.2015 at 16:42.

  3. #3
    Neuer skobbler
    Join Date
    16.11.2015
    Posts
    2
    Hi,

    Is it possible to fix the 32 bits libraries to work on 64 bits device ?

    --------- beginning of crash
    11-17 10:20:52.035 2317 3784 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 3784 (GLThread 65)
    11-17 10:20:52.155 1012 1012 I SELinux : SELinux: Loaded file_contexts contexts from /file_contexts.
    11-17 10:20:52.165 1012 1012 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
    11-17 10:20:52.165 1012 1012 F DEBUG : Build fingerprint: 'generic_x86_64/sdk_phone_x86_64/generic_x86_64:6.0/MRA44C/2166767:eng/test-keys'
    11-17 10:20:52.165 1012 1012 F DEBUG : Revision: '0'
    11-17 10:20:52.165 1012 1012 F DEBUG : ABI: 'x86'
    11-17 10:20:52.165 1012 1012 F DEBUG : pid: 2317, tid: 3784, name: GLThread 65 >>> fr.apila.apila <<<
    11-17 10:20:52.165 1012 1012 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
    11-17 10:20:52.175 1012 1012 F DEBUG : eax 00000000 ebx e00acb10 ecx d598c990 edx e00f5124
    11-17 10:20:52.175 1012 1012 F DEBUG : esi 00000003 edi e00f5124
    11-17 10:20:52.175 1012 1012 F DEBUG : xcs 00000023 xds 0000002b xes 0000002b xfs 000000ef xss 0000002b
    11-17 10:20:52.175 1012 1012 F DEBUG : eip dfa2ef80 ebp d52753f8 esp d5275330 flags 00210297
    11-17 10:20:52.175 1012 1012 F DEBUG :
    11-17 10:20:52.175 1012 1012 F DEBUG : backtrace:
    11-17 10:20:52.175 1012 1012 F DEBUG : #00 pc 0014af80 /data/app/fr.apila.apila-1/lib/x86/libngnative.so (MapRenderer::setupDraw()+3296)
    11-17 10:20:52.175 1012 1012 F DEBUG : #01 pc 00149ddf /data/app/fr.apila.apila-1/lib/x86/libngnative.so (MapRenderer:raw(bool)+399)
    11-17 10:20:52.175 1012 1012 F DEBUG : #02 pc 0014959d /data/app/fr.apila.apila-1/lib/x86/libngnative.so (MapRenderer:rawWrapper(bool)+141)
    11-17 10:20:52.175 1012 1012 F DEBUG : #03 pc 0011b69d /data/app/fr.apila.apila-1/lib/x86/libngnative.so (NG_Render+61)
    11-17 10:20:52.175 1012 1012 F DEBUG : #04 pc 000f3fe4 /data/app/fr.apila.apila-1/lib/x86/libngnative.so (Java_com_skobbler_ngx_map_MapRenderer_render+36)
    11-17 10:20:52.175 1012 1012 F DEBUG : #05 pc 01b2c420 /data/app/fr.apila.apila-1/oat/x86/base.odex (boolean com.skobbler.ngx.map.MapRenderer.render(boolean)+1 16)
    11-17 10:20:52.175 1012 1012 F DEBUG : #06 pc 01b34fd2 /data/app/fr.apila.apila-1/oat/x86/base.odex (void com.skobbler.ngx.map.MapRenderer.onSurfaceChanged( javax.microedition.khronos.opengles.GL10, int, int)+790)
    11-17 10:20:52.175 1012 1012 F DEBUG : #07 pc 743f80b7 /data/dalvik-cache/x86/system@framework@boot.oat
    11-17 10:20:52.175 1012 1012 F DEBUG : #08 pc 000f6cb7
    11-17 10:20:52.305 1012 1012 F DEBUG :

    Thx

  4. #4
    Neuer skobbler
    Join Date
    02.12.2015
    Posts
    3
    Hi,

    I have the same problem.

    How I can disable build for 64 bit?

    I think if the whole application will build only for 32 bits, then it will work on 64 bit processors too.

  5. #5
    Oberskobbler
    Join Date
    22.07.2014
    Posts
    399
    For the moment we don't support 64 bits processor.

  6. #6
    Neuer skobbler
    Join Date
    02.12.2015
    Posts
    3
    May I know when You are planning your next release.

    I'm using Skobbler's map in my application and I will decide continue using it or not.

    Thanks!

  7. #7
    Oberskobbler
    Join Date
    22.07.2014
    Posts
    399
    The next release is scheduled for January 2016

  8. #8
    Neuer skobbler
    Join Date
    09.04.2016
    Posts
    3
    Any news on this? Looks like the release didn't make it on time :-)

  9. #9
    Oberskobbler
    Join Date
    22.07.2014
    Posts
    399
    The date of the release has changed in the meantime due to the high volume of the enterprise requests, we have the beta builds are ready (if you want to test them please send us an email at dev@telenav.com) and the public SDK is scheduled to be released soon. An important notice is that this feature request didn't get in the next SDK, so the remaining workaround is to run as a 32 bit app on a 64 bit architecture.

  10. #10
    Neuer skobbler
    Join Date
    27.06.2016
    Posts
    2

    How to use the map on 64 bit architecture (Galaxy S6 for example)

    Quote Originally Posted by Adela_Silvia View Post
    The date of the release has changed in the meantime due to the high volume of the enterprise requests, we have the beta builds are ready (if you want to test them please send us an email at dev@telenav.com) and the public SDK is scheduled to be released soon. An important notice is that this feature request didn't get in the next SDK, so the remaining workaround is to run as a 32 bit app on a 64 bit architecture.
    @Adela_Silvia
    Please specify detail steps to run the application as a 32 bit app on a 64 bit architecture?
    Currently our app which integrated your map does not work on Galaxy S6, just keep crashing every time we load the map.
    Last edited by hoang06kx1; 27.06.2016 at 10:07.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •