Kodi Community Forum

Full Version: xbmc-android cannot run on hisilicon arm platform
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
hi folks,
I can successfully install xbmc-android on hisilicon arm platform(hi3716C), but can not run.
Has anyone encountered this error?
Thanks in avdance!

the cpuinfo of this chip is:
[email protected]:/ # cat /proc/cpuinfo
Processor : ARMv7 Processor rev 2 (v7l)
BogoMIPS : 2007.04
Features : swp half thumb fastmult vfp edsp vfpv3 vfpv3d16
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x2
CPU part : 0xc09
CPU revision : 2

Hardware : godbox
Revision : 0000
Serial : 0000000000000000

and the logcat output is:
V/AudioPolicyManagerBase( 899): startOutput() output 1, stream 1, session 11
V/AudioPolicyManagerBase( 899): changeRefCount() stream 1, count 1
I/AudioPolicyManagerBase( 899): MEDIA fromCache 1
V/AudioPolicyManagerBase( 899): getDeviceForStrategy() from cache strategy 0, device 2
V/AudioPolicyManagerBase( 899): getNewDevice() selected device 2
V/AudioPolicyManagerBase( 899): setOutputDevice() output 1 device 2 delayMs 0
V/AudioPolicyManagerBase( 899): setOutputDevice() setting same device 2 or null device for output 1
V/AudioPolicyManagerBase( 899): VOLUME vol index=[20 46 60], dB=[-34.0 -19.0 -11.0] ampl=0.11156
V/AudioPolicyManagerBase( 899): releaseOutput() 1
I/AudioResampler( 899): Mono: mInSampleRate&mSampleRate:4410048000
I/AudioHardwareALSA( 899): recover
I/AudioHardwareALSA( 899): recover n 0
I/AudioResampler( 899): Mono: mInSampleRate&mSampleRate:4410048000
I/AudioResampler( 899): Mono: mInSampleRate&mSampleRate:4410048000
I/ActivityManager( 1213): START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=org.xbmc.xbmc/android.app.NativeActivity} from pid 1339
I/AudioResampler( 899): Mono: mInSampleRate&mSampleRate:4410048000
V/AudioPolicyManagerBase( 899): stopOutput() output 1, stream 1, session 11
V/AudioPolicyManagerBase( 899): changeRefCount() stream 1, count 0
V/AudioPolicyManagerBase( 899): getNewDevice() selected device 0
V/AudioPolicyManagerBase( 899): setOutputDevice() output 1 device 0 delayMs 86
V/AudioPolicyManagerBase( 899): setOutputDevice() setting same device 0 or null device for output 1
D/dalvikvm( 1213): GC_FOR_ALLOC freed 3122K, 27% free 10993K/14983K, paused 56ms
D/dalvikvm( 1803): Late-enabling CheckJNI
I/ActivityManager( 1213): Start proc org.xbmc.xbmc for activity org.xbmc.xbmc/android.app.NativeActivity: pid=1803 uid=10034 gids={1015, 3003}
V/AudioPolicyManagerBase( 899): startOutput() output 1, stream 1, session 12
V/AudioPolicyManagerBase( 899): changeRefCount() stream 1, count 1
I/AudioPolicyManagerBase( 899): MEDIA fromCache 1
V/AudioPolicyManagerBase( 899): getDeviceForStrategy() from cache strategy 0, device 2
V/AudioPolicyManagerBase( 899): getNewDevice() selected device 2
V/AudioPolicyManagerBase( 899): setOutputDevice() output 1 device 2 delayMs 0
V/AudioPolicyManagerBase( 899): setOutputDevice() setting same device 2 or null device for output 1
V/AudioPolicyManagerBase( 899): VOLUME vol index=[20 46 60], dB=[-34.0 -19.0 -11.0] ampl=0.11156
V/AudioPolicyManagerBase( 899): releaseOutput() 1
I/dalvikvm( 1803): Turning on JNI app bug workarounds for target SDK version 10...
I/AudioResampler( 899): Mono: mInSampleRate&mSampleRate:4410048000
W/NetworkManagementSocketTagger( 1213): setKernelCountSet(10034, 1) failed with errno -2
D/OpenGLRenderer( 1339): Flushing caches (mode 1)
I/AudioResampler( 899): Mono: mInSampleRate&mSampleRate:4410048000
D/OpenGLRenderer( 1339): GL error from OpenGLRenderer: 0x501
I/AudioResampler( 899): Mono: mInSampleRate&mSampleRate:4410048000
D/dalvikvm( 1045): GC_EXPLICIT freed 37K, 4% free 9057K/9347K, paused 2ms+5ms
D/OpenGLRenderer( 1339): Flushing caches (mode 0)
I/ActivityManager( 1213): START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=org.xbmc.xbmc/android.app.NativeActivity} from pid 1339
I/AudioResampler( 899): Mono: mInSampleRate&mSampleRate:4410048000
V/AudioPolicyManagerBase( 899): stopOutput() output 1, stream 1, session 12
V/AudioPolicyManagerBase( 899): changeRefCount() stream 1, count 0
V/AudioPolicyManagerBase( 899): getNewDevice() selected device 0
V/AudioPolicyManagerBase( 899): setOutputDevice() output 1 device 0 delayMs 86
V/AudioPolicyManagerBase( 899): setOutputDevice() setting same device 0 or null device for output 1
D/dalvikvm( 1045): GC_EXPLICIT freed <1K, 4% free 9057K/9347K, paused 2ms+10ms
D/dalvikvm( 1045): GC_EXPLICIT freed <1K, 4% free 9057K/9347K, paused 4ms+3ms
D/dalvikvm( 1803): GC_CONCURRENT freed 164K, 3% free 9398K/9607K, paused 2ms+5ms
D/dalvikvm( 1803): GC_CONCURRENT freed 128K, 3% free 9758K/9991K, paused 3ms+3ms
F/libc ( 1803): Fatal signal 4 (SIGILL) at 0x5b4a8e5c (code=1)
I/DEBUG ( 894): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 894): Build fingerprint: 'HiAndroid/full_godbox/godbox:4.0.3/IML74K/eng.huanzq.20121009.173517:eng/test-keys'
I/DEBUG ( 894): pid: 1803, tid: 1803 >>> org.xbmc.xbmc <<<
I/DEBUG ( 894): signal 4 (SIGILL), code 1 (ILL_ILLOPC), fault addr 5b4a8e5c
I/DEBUG ( 894): r0 49ef6f00 r1 fffffffd r2 00000000 r3 00000000
I/DEBUG ( 894): r4 5c53b88c r5 00000000 r6 5c538f40 r7 00000641
I/DEBUG ( 894): r8 00000000 r9 5c53a000 10 00000000 fp 5b1bf000
I/DEBUG ( 894): ip 00989680 sp be845250 lr 49ef6f00 pc 5b4a8e5c cpsr 00000010
I/DEBUG ( 894): d0 3f7aaaab3f800000 d1 3ff0000042c80000
I/DEBUG ( 894): d2 437e8000000000fe d3 000000003f000000
I/DEBUG ( 894): d4 000001fd00000000 d5 3fe999999999999a
I/DEBUG ( 894): d6 3fe8000000000000 d7 408000003f800000
I/DEBUG ( 894): d8 0000000000000000 d9 0000000000000000
I/DEBUG ( 894): d10 0000000000000000 d11 0000000000000000
I/DEBUG ( 894): d12 0000000000000000 d13 0000000000000000
I/DEBUG ( 894): d14 0000000000000000 d15 0000000000000000
I/DEBUG ( 894): scr 20000012
I/DEBUG ( 894):
I/DEBUG ( 894): #00 pc 002e9e5c /data/data/org.xbmc.xbmc/lib/libxbmc.so (_Z20SystemTimeToFileTimePK11_SYSTEMTIMEP9_FILETIME)
I/DEBUG ( 894): #01 pc 00774f70 /data/data/org.xbmc.xbmc/lib/libxbmc.so (_ZNK9CDateTime10ToFileTimeERK11_SYSTEMTIMER9_FILETIME)
I/DEBUG ( 894): #02 pc 0077579c /data/data/org.xbmc.xbmc/lib/libxbmc.so (_ZN9CDateTime11SetDateTimeEiiiiii)
I/DEBUG ( 894): #03 pc 007757d4 /data/data/org.xbmc.xbmc/lib/libxbmc.so (_ZN9CDateTime5ResetEv)
I/DEBUG ( 894):
I/DEBUG ( 894): code around pc:
I/DEBUG ( 894): 5b4a8e3c 0a000002 e358003a c2888001 c58d8020 ....:.X..... ...
I/DEBUG ( 894): 5b4a8e4c e28d0004 ebffdd5b e59fc048 e1d550be ....[...H....P..
I/DEBUG ( 894): 5b4a8e5c eddf0b0b e0832c90 e023319c e3021710 .....,...1#.....
I/DEBUG ( 894): 5b4a8e6c e0a32591 ec510b30 e0922000 e3a00001 .%..0.Q.. ......
I/DEBUG ( 894): 5b4a8e7c e0a33001 e884000c e28dd030 e8bd81f0 .0......0.......
I/DEBUG ( 894):
I/DEBUG ( 894): code around lr:
I/DEBUG ( 894): 49ef6ee0 00000000 00000000 00000000 00000000 ................
I/DEBUG ( 894): 49ef6ef0 00000000 00000000 00000000 00000000 ................
I/DEBUG ( 894): 49ef6f00 00000000 00000000 00000000 00000000 ................
I/DEBUG ( 894): 49ef6f10 00000000 00000000 00000000 00000000 ................
I/DEBUG ( 894): 49ef6f20 00000000 00000000 00000000 00000000 ................
I/DEBUG ( 894):
I/DEBUG ( 894): memory map around addr 5b4a8e5c:
I/DEBUG ( 894): 5b0c0000-5b1bf000
I/DEBUG ( 894): 5b1bf000-5c40d000 /data/data/org.xbmc.xbmc/lib/libxbmc.so
I/DEBUG ( 894): 5c40d000-5c53a000 /data/data/org.xbmc.xbmc/lib/libxbmc.so
I/DEBUG ( 894):
I/DEBUG ( 894): stack:
I/DEBUG ( 894): be845210 be845218 [stack]
I/DEBUG ( 894): be845214 400ab17f /system/lib/libc.so
I/DEBUG ( 894): be845218 00000001
I/DEBUG ( 894): be84521c 00000000
I/DEBUG ( 894): be845220 be845254 [stack]
I/DEBUG ( 894): be845224 00000000
I/DEBUG ( 894): be845228 00000000
I/DEBUG ( 894): be84522c 5c53b88c
I/DEBUG ( 894): be845230 be8452a0 [stack]
I/DEBUG ( 894): be845234 5c538f40 /data/data/org.xbmc.xbmc/lib/libxbmc.so
I/DEBUG ( 894): be845238 00000641
I/DEBUG ( 894): be84523c 00000000
I/DEBUG ( 894): be845240 5c53a000
I/DEBUG ( 894): be845244 00000000
I/DEBUG ( 894): be845248 df0027ad
I/DEBUG ( 894): be84524c 00000000
I/DEBUG ( 894): #00 be845250 5c53a27c
I/DEBUG ( 894): be845254 00000000
I/DEBUG ( 894): be845258 00000000
I/DEBUG ( 894): be84525c 00000000
I/DEBUG ( 894): be845260 00000001
I/DEBUG ( 894): be845264 00000000
I/DEBUG ( 894): be845268 fffffed5
I/DEBUG ( 894): be84526c 00000000
I/DEBUG ( 894): be845270 00000000
I/DEBUG ( 894): be845274 00000000
I/DEBUG ( 894): be845278 00000000
I/DEBUG ( 894): be84527c 00000000
I/DEBUG ( 894): be845280 5c53b88c
I/DEBUG ( 894): be845284 00000001
I/DEBUG ( 894): be845288 00000641
I/DEBUG ( 894): be84528c 00000001
I/DEBUG ( 894): be845290 5c4f1ab0 /data/data/org.xbmc.xbmc/lib/libxbmc.so
I/DEBUG ( 894): be845294 5b933f74 /data/data/org.xbmc.xbmc/lib/libxbmc.so
I/DEBUG ( 894): #01 be845298 5c53b888
I/DEBUG ( 894): be84529c 5b9347a0 /data/data/org.xbmc.xbmc/lib/libxbmc.so
I/InputDispatcher( 1213): Dropping event because there is no touched window or focused application.
W/NetworkManagementSocketTagger( 1213): setKernelCountSet(10034, 0) failed with errno -2
D/Zygote ( 1045): Process 1803 terminated by signal (4)
I/ActivityManager( 1213): Process org.xbmc.xbmc (pid 1803) has died.


Not all Android devices are supported and to tell the truth we have no clue where you got the XBMC.apk from. You might even be running one built for NEON and since your armv7 does not have it, there you go Smile
@sonach : a little off topic, but what hardware are you running ? I have a AC Ryan Veolo myself, which is identified as "godbox" hardware platform also, but you seem to be running ICS.

Thx for your answer, because I really would like to see ICS on the Veolo, as it could then possibly run XBMC.
(2012-10-10, 05:45)davilla Wrote: [ -> ]Not all Android devices are supported and to tell the truth we have no clue where you got the XBMC.apk from. You might even be running one built for NEON and since your armv7 does not have it, there you go Smile
davilla, thank you very much for the reply!
1. the xbmc.apk was built myself following android.README. and the same apk can be run on Samsung Nexus S handset.
2. yes, the hardware doesn't support NENO. so it there any instructions for disabling NENO while build xbmc-android(or Have anyone done the same thing / or Is it possible to disable NEON for xbmc-android build)?



(2012-10-11, 00:10)jefke Wrote: [ -> ]@sonach : a little off topic, but what hardware are you running ? I have a AC Ryan Veolo myself, which is identified as "godbox" hardware platform also, but you seem to be running ICS.

Thx for your answer, because I really would like to see ICS on the Veolo, as it could then possibly run XBMC.

@jefke: you can see the detail cpuinfo in the post. and the hardware is produced by hilision, codename is "hi3716C", the target market is STB.
BTW, I am running ICS.
you would be much better off getting a XDA non-neon build, they run a nightly build. The custom ndk needs to be fixed for non-neon.
(2012-10-11, 02:54)sonach Wrote: [ -> ]
(2012-10-11, 00:10)jefke Wrote: [ -> ]@sonach : a little off topic, but what hardware are you running ? I have a AC Ryan Veolo myself, which is identified as "godbox" hardware platform also, but you seem to be running ICS.

Thx for your answer, because I really would like to see ICS on the Veolo, as it could then possibly run XBMC.

@jefke: you can see the detail cpuinfo in the post. and the hardware is produced by hilision, codename is "hi3716C", the target market is STB.
BTW, I am running ICS.

Thanks for your reply. I know the CPU is a Hi3716C and the GPU is a Vivante Corp. GC800, it's the same as in the AC Ryan Veolo (and all similar devices are identified as "godbox" platform), difference is that the firmware published for the Veolo is only 2.2 (Froyo). This is why I wanted to know what hardware you have, maybe some ICS firmware is available to play around with...
(2012-10-11, 03:59)davilla Wrote: [ -> ]you would be much better off getting a XDA non-neon build, they run a nightly build. The custom ndk needs to be fixed for non-neon.
Awesome!

I tried XDA non-neon build and it runs good on the hardware, with 25 fps for 1280x720 screen.
and the xda non-neon link is http://forum.xda-developers.com/showthre...?t=1813089

thank you very much!
(2012-10-11, 08:20)jefke Wrote: [ -> ]
(2012-10-11, 02:54)sonach Wrote: [ -> ]
(2012-10-11, 00:10)jefke Wrote: [ -> ]@sonach : a little off topic, but what hardware are you running ? I have a AC Ryan Veolo myself, which is identified as "godbox" hardware platform also, but you seem to be running ICS.

Thx for your answer, because I really would like to see ICS on the Veolo, as it could then possibly run XBMC.

@jefke: you can see the detail cpuinfo in the post. and the hardware is produced by hilision, codename is "hi3716C", the target market is STB.
BTW, I am running ICS.

Thanks for your reply. I know the CPU is a Hi3716C and the GPU is a Vivante Corp. GC800, it's the same as in the AC Ryan Veolo (and all similar devices are identified as "godbox" platform), difference is that the firmware published for the Veolo is only 2.2 (Froyo). This is why I wanted to know what hardware you have, maybe some ICS firmware is available to play around with...

@jefke: I don't quite sure what does "know what hardware you have" mean. Do you mean the NAND(mine is 1GB) and RAM(mine is 1GB) size or other?
If you are interested, you can test my prebuilt ICS image Smile
(2012-10-13, 08:24)sonach Wrote: [ -> ]
(2012-10-11, 08:20)jefke Wrote: [ -> ]
(2012-10-11, 02:54)sonach Wrote: [ -> ]@jefke: you can see the detail cpuinfo in the post. and the hardware is produced by hilision, codename is "hi3716C", the target market is STB.
BTW, I am running ICS.

Thanks for your reply. I know the CPU is a Hi3716C and the GPU is a Vivante Corp. GC800, it's the same as in the AC Ryan Veolo (and all similar devices are identified as "godbox" platform), difference is that the firmware published for the Veolo is only 2.2 (Froyo). This is why I wanted to know what hardware you have, maybe some ICS firmware is available to play around with...

@jefke: I don't quite sure what does "know what hardware you have" mean. Do you mean the NAND(mine is 1GB) and RAM(mine is 1GB) size or other?
If you are interested, you can test my prebuilt ICS image Smile

@sonach : I have a AC Ryan Veolo. It has 4 GB NAND and 512 MB RAM. Sadly, it only has Android 2.2 ... What mediaplayer do you have ? Or is it some kind of development board ? If you have a ICS image, I would gladly help test it, as long as it can be flashed on to the AC Ryan Smile
The XBMC, non-neon, nightly .apk file build from 10/23/12 DOES work on a Droid3.

However, playback of H.264 encoded video operates at about 1/2 the frame rate it should be playing.

Note the Droid 3 specs:

1GHz OMAP4430 CPU
PowerVR SGX540 GPU
512MB RAM
Running gingerbread (No ICS available, locked bootloader because motorola hates their customers.)

So unless there is a way to take advantage of the the PowerVR SGX540 for video playback, XBMC won't be too useful for H.264 encoded videos on these type of phones.


I was hoping to post this in a new thread but I'm not able to make new threads for some reason.

I did not yet try out regular MPEG2 recordings.

(2012-10-25, 15:18)NewJerseyNinja Wrote: [ -> ]The XBMC, non-neon, nightly .apk file build from 10/23/12 DOES work on a Droid3.

However, playback of H.264 encoded video operates at about 1/2 the frame rate it should be playing.

Note the Droid 3 specs:

1GHz OMAP4430 CPU
PowerVR SGX540 GPU
512MB RAM
Running gingerbread (No ICS available, locked bootloader because motorola hates their customers.)

So unless there is a way to take advantage of the the PowerVR SGX540 for video playback, XBMC won't be too useful for H.264 encoded videos on these type of phones.


I was hoping to post this in a new thread but I'm not able to make new threads for some reason.

I did not yet try out regular MPEG2 recordings.

(1) Since you device is OMAP4430, maybe you should try the NEON version of xbmc-android? then xbmc can make use of NEON to accelerate the H264 decoding.

(2) Since official xbmc-android doesn't support hardware decoding except PiVOS, you can try diceplayer as the external player for the testing purpose Smile
Since I want to add hardware decoding to xbmc-android, I am trying to build non-neon xbmc-android myself and I have posted a thread on xbmcandroid forum:
http://www.xbmcandroid.com/forums/xbmc-a...ty/139.htm

I wish with the help of xbmc and xbmcandroid guys, I can make this job done Smile
Hi, you have any sucess with this?