v17 After 9.93.2016 is installed but the interface is not launched
#31
(2016-03-27, 01:37)shomari Wrote: ... still crashes, same result - splash screen, then down it goes. Still can't even access GUI

Log: http://goo.gl/zuQ4Gj

Error is gone. The problem is not obvious at all. We need a logcat to continue.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#32
Here is a logcat, using version 2d05a88, this logcat isn't from the first run:
http://pastebin.com/Wx2QAzbb
Crash dump is created at first run in Kodi profile temp directory, here it is:
https://mega.nz/#!oRkkTBKK!aKtAOV05XyHDK...DObf5N_sNY
Reply
#33
Quote:03-28 10:19:45.729 V/Kodi (4166): Debug Print: CSettings: error loading settings definition from special://xbmc/system/settings/settings.xml, Line 0
03-28 10:19:45.729 V/Kodi (4166): Failed to open file
03-28 10:19:45.729 V/Kodi (4166): Debug Print: Unable to load settings definitions
03-28 10:19:45.729 V/Kodi (4166): => XBMC_Run finished with -1

That says that the installation is borked.
Which apk did you use?
Reply
#34
This nightly, kodi-20160327-2d05a88-master-armeabi-v7a.apk:
http://mirrors.kodi.tv/nightlies/android...bi-v7a.apk
Reply
#35
The apk is ok.
Could uninstall/reinstall and retake a debug log + logcat, please.
Reply
#36
Debug log:
http://pastebin.com/UHajgvTa
Logcat:
http://pastebin.com/sEFPdZbh
Reply
#37
Anything attached to USB? If so, try without it...

P.S. Oh, and try SPMC (http://spmc.semperpax.com) side-by-side with kodi to see if the result is the same...
Reply
#38
Tried without devices attached to usb port, same thing happens(splash screen the exit to home menu).
SPMC is working fine.
I think kodi-20160311-11912ea-master-armeabi-v7a.apk was the last one working.
Why is there a Windows crash minidump file being created in Kodi profile temp directory?
I've uploaded the crashdump to an online analyzer here is a part of the output:
http://pastebin.com/dMBRtt9F
Reply
#39
99% chance it's due to the joystick refactoring merge...
It will need a dev running Android 17 to fix...

P.S. Works for me, though
Reply
#40
Hi.

After disabling: "m_busses.push_back(std::make_shared<CPeripheralBusAndroid>(this))" on "xbmc/peripherals/Peripherals.cpp", kodi starts normally.
So there is definitively error with a new code for peripherals on android platform.
Reply
#41
That piece of code is added from this commit:
https://github.com/xbmc/xbmc/commit/9e1f...3c2eee923c
That commit was made on Mar 11, 2016.
Reply
#42
(2016-03-29, 19:19)csgabe Wrote: That piece of code is added from this commit:
https://github.com/xbmc/xbmc/commit/9e1f...3c2eee923c
That commit was made on Mar 11, 2016.

I know, that commit is crashing kodi on older android platform / or on some specific android devices. When I will have more time I will debug further.
Reply
#43
@Montellese wrote the android joystick code, so he will probably have a better idea of why this is crashing. When CPeripheralBusAndroid is created, it looks like it does an initial scan. my guess is that the JNI code that does the scan relies on something that isn't initialized yet. Peripherals is one of the first systems initialized, so this is likely. Performing the scan after CPeripheralBusAndroid is created might fix the problem.
Reply
#44
I made some changes on peripheral scan function so if anyone want to try apk on problematic device. I'm not at home so I can't try it on my own device.

APK Link: Kodi test APK

Remember to uninstall current kodi app before installing this one. (Different apk signature).
Reply
#45
Still crashes, kodi log:
http://goo.gl/g02ygV
Reply

Logout Mark Read Team Forum Stats Members Help
After 9.93.2016 is installed but the interface is not launched1