VLC crashes on Nextbook NX006HD8G

[gronceski]

VLC dies very early in the startup process and no "vlc_logcat*" files are created. To follow up I uninstalled VLC rebooted my NX006HD8G and then installed VLC-debug-20130827-0108.apk cleaned the android logcat and executed with the same results. When I dump logcat after the screen flash and immediate exit all that is contained in the dump is:

W/IInputConnectorWrapper(17129): showStatusIcon on inactive InputConnection

Any other suggestions for determining why VLC won't even start on this device?

[edwardw]

You have tried to follow https://wiki.videolan.org/Android_Report_bugs?

[gronceski]

Other than there was nothing to paste into the "Pastebin.com" site then the one line message I'm including again below and I did not see a form for fileing a bug report from that web page I thought I did what was asked. I know I'm missing something NOOB to your forum but I cannot figure out how to file a proper bug report but I have logged equivalent entries in http://goo.gl/zZ8O4 from earlier in the forum.

I tried using several VLC versions, Google Play hat says VLC is not compatible with my device (Nextbook NX0008HD8G which uses an AML8726-MX dual core Cortex A9 processor, 1GB ram, running JB 4.1.1 JRO03C.v009 3.0.8-g4b66125 kernel) through the .../android-armv7/VLC-debug-20130825-0106.apk and .../android-armv7/VLC-debug-20130827-0108.apk versions from the nightly builds on the videolan web site with zero success. The application flashes the screen and exits immediately, I cannot find debug or logcat files to upload in Astro File manager nor via Terminal program and the only message I get following the steps on https://wiki.videolan.org/Android_Report_bugs is:

W/IInputConnectorWrapper(17129): showStatusIcon on inactive InputConnection

I know I'm being stupid by asking again but I need help filing a proper bug report.

I know this is not a main stream reference table but since it is selling for $99 USD at Walmart there are thousands of these devices being sold every week. My family owns two tablets and other than video player that can play my 4TB of video files over the years without transcoding everything works on this table even Netflix, Hlu and Amazon Prime Instant Video. The only 3rd party player I have tried that runs on this table is BSPlayer and its hit or miss on my video library. VLC, MXPLAYER and VPLAYER do not run, I'd prefer VLC like I use on my PC as it plays everything I have ever tried.

Please help or direct me to better instructons for filing a proper bug report.

[edwardw]

Other than there was nothing to paste into the "Pastebin.com" site then the one line message I'm including again below and I did not see a form for fileing a bug report from that web page I thought I did what was asked. I know I'm missing something NOOB to your forum but I cannot figure out how to file a proper bug report but I have logged equivalent entries in http://goo.gl/zZ8O4 from earlier in the forum.

I tried using several VLC versions, Google Play hat says VLC is not compatible with my device (Nextbook NX0008HD8G which uses an AML8726-MX dual core Cortex A9 processor, 1GB ram, running JB 4.1.1 JRO03C.v009 3.0.8-g4b66125 kernel) through the .../android-armv7/VLC-debug-20130825-0106.apk and .../android-armv7/VLC-debug-20130827-0108.apk versions from the nightly builds on the videolan web site with zero success. The application flashes the screen and exits immediately, I cannot find debug or logcat files to upload in Astro File manager nor via Terminal program and the only message I get following the steps on https://wiki.videolan.org/Android_Report_bugs is:

W/IInputConnectorWrapper(17129): showStatusIcon on inactive InputConnection

I know I'm being stupid by asking again but I need help filing a proper bug report.

I know this is not a main stream reference table but since it is selling for $99 USD at Walmart there are thousands of these devices being sold every week. My family owns two tablets and other than video player that can play my 4TB of video files over the years without transcoding everything works on this table even Netflix, Hlu and Amazon Prime Instant Video. The only 3rd party player I have tried that runs on this table is BSPlayer and its hit or miss on my video library. VLC, MXPLAYER and VPLAYER do not run, I'd prefer VLC like I use on my PC as it plays everything I have ever tried.

Please help or direct me to better instructons for filing a proper bug report.

Can you root your tablet?

[gronceski]

Took a few hours last night as I couldn't find ADB USB drivers but yes, I have rooted the tablet.

Combination of (http://forum.xda-developers.com/showthr ... ?t=2366829 and http://www.freaktab.com/showthread.php? ... ashable-Ro) Anyway, I now have a Nextbook 8 (NX008HD8G) tablet available from Walmart with JB 4.1.1 with root access.

I poked around a bit and see the Linux kernel does detect and boot as ARMv7 processor "Amlogic: Meson6" and confirmed the tablet is using AMLogic AML8726-MX SoC (1.5Ghz dualcore Cortex-A9 w/400mhz dualcore Malli400 GPU) has 1 Gb of DDR3 RAM, 8" display, and 8Gb internal storage.

Anyway with root access I captured more data with the logcat and uploaded as:

http://pastebin.com/AZ5Vx9Hj

[edwardw]

Hello,

Could you please install Term.apk and pastebin the output of

Code: Select all

cat /proc/cpuinfo

?

Thanks.

[gronceski]

Posted as http://pastebin.com/JQqGLgiQ

Thank You for taking the time to look.

[edwardw]

So it looks like a standard ARMv7 NEON processor.

Please try this build http://nightlies.videolan.org/build/and ... 0-0105.apk and what happens?

[gronceski]

I have tried several versions of android-armv7 VLC from nightlies VLC-debug-20130825-0106.apk, VLC-debug-20130827-0108.apk and now VLC-debug-20130830-0105.apk with the same results. When the application starts the screen briefly flashes and the application has exited, nothing starts. After rooting tablet I was able to get a decent logcat which I previously posted but still not able to get the normal VLC debug files. However I updated with the logcat results using this slightly new version for your reference as http://pastebin.com/0affjPcH.

[edwardw]

Please post the logcat of this special debug build: https://my.owndrive.com/public.php?serv ... 4&download

Edit: updated

[gronceski]

Wow, thanks the old version (VLC-debug-ARMv6-20120822.apk) you provided starts as expected logcat (http://pastebin.com/qVt6WkYc) however it failed to play a simple mp4 video file logcat (http://pastebin.com/SfsPNBJ2) so we only made progress to see the VLC GUI.

Thanks again,
Dave Gronceski

[edwardw]

Wow, thanks the old version (VLC-debug-ARMv6-20120822.apk) you provided starts as expected logcat (http://pastebin.com/qVt6WkYc) however it failed to play a simple mp4 video file logcat (http://pastebin.com/SfsPNBJ2) so we only made progress to see the VLC GUI.

Thanks again,
Dave Gronceski

Sorry, that is the wrong build. Please try the updated one above.

And you should never use such an old build.

[gronceski]

Thought it was strange that you would provide such an old build in your special link, but didn't question too much as figured that may be the old software had debugging statements or something not in the current generation of software.

Anyway, now I am trying (VLC-debug-20130902-hasCompatibleCPU.apk) from your same link and like magic it works and I used it to play a sample mp4 file. Need to double check some other files as had intermittent screen artifacts & minor studdering, incase you would like to see here is logacat (http://pastebin.com/FtETvKxD)

Code: Select all

# begin build properties # autogenerated by buildinfo.sh ro.build.id=JRO03C ro.build.display.id=JRO03C.v009 ro.build.version.incremental=eng.root.20130402.204838 ro.build.version.sdk=16 ro.build.version.codename=JellyBean ro.build.version.release=4.1.1 ro.build.date=Tue Apr 2 20:49:15 CST 2013 ro.build.date.utc=1364906955 ro.build.type=user ro.build.user=root ro.build.host=midcs-desktop ro.build.tags=release-keys ro.product.board=NXM8000ND_WM ro.product.model=NX008HD8G ro.product.brand=Nextbook ro.product.name=NX008HD8G ro.product.device=NX008HD8G ro.product.cpu.abi2=armeabi ro.product.cpu.abi2=armeabi-v7a ro.product.manufacturer=YIFANG ro.wifi.channels=14 ro.board.platform=meson6 # ro.build.product is obsolete; use ro.product.device ro.build.product=NXM8000ND_WM # Do not try to parse ro.build.description or .fingerprint ro.build.description=NXM8000ND_WM-user 4.1.1 JRO03C eng.root.20130402.204838 release-keys ro.build.fingerprint=Nextbook/M8000ND/M8000ND:4.1.1/JRO03C/v009:user/release-keys ro.build.characteristics=tablet

[edwardw]

Cool. So VLC nightlies should work fine for you then

[gronceski]

Starting with which release?

"http://nightlies.videolan.org/build/and ... 3-1725.apk" does not work where your special build "VLC-debug-20130902-hasCompatibleCPU.apk" does work. Failure logcat (http://pastebin.com/Whyea3e3)

[gronceski]

I opened up your "VLC-debug-20130902-hasCompatibleCPU.apk" and looked at the contents including the env.txt file and it showed NO_FP=1 build option and the only nightly ARM build without FPU in the standard nightly builds I could find was "armv6-android-nofpu" so I tried:

http://nightlies.videolan.org/build/arm ... 3-1730.apk

and this version works. I suspect in backwards compatibility mode as indicated by your test build "VLC-debug-20130902-hasCompatibleCPU.apk" despite the Cortex A9 having an FPU, so I wonder if this is it the correct version to use for the NX008HD8G long term?

Thanks,
Dave

[edwardw]

Hmm.

Try installing sysinfo and tell me what the contents of CPU_ABI and CPU_ABI2 are.

[gronceski]

CPU ABI unknown
CPU ABI2 armeabi
Manufacturer YIFANG
Hardware amlogic
Finger Print Nextbook/M8000ND/M8000ND:4.1.1/JRO03C/v009:user/release-keys
SDK Version 16

I thought you might need the contents of /system/build.prop since these are almost useless:
http://pastebin.com/g0EBTnFY


Thanks for continuing to look at this budget tablet.

[gronceski]

Based on http://forum.xda-developers.com/showthr ... ?t=2056266

Shouldn't we have these values in build.prop
ro.product.cpu.abi2=armeabi
ro.product.cpu.abi=armeabi-v7a
not
ro.product.cpu.abi2=armeabi
ro.product.cpu.abi2=armeabi-v7a

which leaves ro.product.cpu.abi as an unknown value and the second of ro.product.cpu.abi2 is ignored during the boot process?

If so should I modify build.prop file so it makes sense?

[edwardw]

It looks like the manufacturer was completely careless and made a stupid typo in the build.prop.

While it would work if you modified it, it wouldn't be reasonable to expect all tablet owners to modify it either

I'll look into some workaround in the code.

[edwardw]

Hello,

You can use the ARMv6-fpu builds for now.