[sossy]

Have the same issues here, but running the stock Samsung firmware 3.4.5

Hi,
Strange thing, mine was working fine for the first few days I had my device, then i rooted it, and all of a sudden, no icons in xbmc, just text and a black screen. So tonight i went back to stock firmware and everything is good again. Not sure why rooting it would break that, but maybe someone smarter than me can figure that out. The only thing i had added after rooting was adaway, not sure if that had anything to do with it or not either. I am wondering how many other people that are having problems have rooted devices? anyways, I will let you know if the problem comes back on the stock firmware or not in a few days or so.

[sheepybach]

Not sure if I've asked this silly question or not but you are all using builds from the link below for your Tab 3 10.1 yes??

http://mirrors.xbmc.org/nightlies/android/x86/

The reason I'm asking is that not matter what I try I can't repeat your problems with any of these builds.

[Martijn]

Not sure if I've asked this silly question or not but you are all using builds from the link below for your Tab 3 10.1 yes??

http://mirrors.xbmc.org/nightlies/android/x86/

The reason I'm asking is that not matter what I try I can't repeat your problems with any of these builds.

sossy has this in the log

00:18:41 T:1593154168 NOTICE: Starting XBMC (13.0-ALPHA11 Git:20131231-8eb49b3). Platform: ARM Android 32-bit
00:18:41 T:1593154168 NOTICE: Using Debug XBMC x32 build, compiled Jan 1 2014 by GCC 4.8.0 for ARM Android 32-bit API level 14
00:18:41 T:1593154168 NOTICE: Running on Linux 32-bit (Android, 3.4.5-1256430-user armv7l)
00:18:41 T:1593154168 NOTICE: Host CPU: ARMv7 Processor rev 0 (v7l), 2 cores available

so you say the Galaxy Tab 3 is a X86 processor? There are different version iirc with different processor specs
Looking at the debug message it's not really clear as well.

[sheepybach]

Not sure if I've asked this silly question or not but you are all using builds from the link below for your Tab 3 10.1 yes??

http://mirrors.xbmc.org/nightlies/android/x86/

The reason I'm asking is that not matter what I try I can't repeat your problems with any of these builds.

sossy has this in the log

00:18:41 T:1593154168 NOTICE: Starting XBMC (13.0-ALPHA11 Git:20131231-8eb49b3). Platform: ARM Android 32-bit
00:18:41 T:1593154168 NOTICE: Using Debug XBMC x32 build, compiled Jan 1 2014 by GCC 4.8.0 for ARM Android 32-bit API level 14
00:18:41 T:1593154168 NOTICE: Running on Linux 32-bit (Android, 3.4.5-1256430-user armv7l)
00:18:41 T:1593154168 NOTICE: Host CPU: ARMv7 Processor rev 0 (v7l), 2 cores available

so you say the Galaxy Tab 3 is a X86 processor? There are different version iirc with different processor specs
Looking at the debug message it's not really clear as well.

Martijn,
All SG Tab 3's come with Intel Atom Z2560 chipset's and if I'm reading his log right then he's using an arm build and not a x86 one
I've tried to do a log of my tab3 but I can't find the bloody thing ok found out put wrong email addy in and can't seem to change it.

[sossy]

Thanks for replying Sheepybach and Martijn.

The Samsung Galaxy tab 3 range has three different variants. The 7.0, 8.0 and 10.1. The 7.0 and 8.0 have Arm processors, and the 10.1 has an x86.
The Samsung Galaxy tab 3 7.0 (which is the version we are having the issue with) uses a Marvell PXA986 processor

Hope this helps. If there is any particular testing I can do to help pinpoint the issue, let me know

glen

[sossy]

As there seems to be a little confusion, I thought I would consolidate the description of the problem, and attempts at solutions so far:

This relates to the gui display when running XBMC on the Samsung Galaxy Tab 3 7.0. Below is the link to the tech specs:
http://www.samsung.com/au/consumer/mobil...WAXSA-spec

It doesnt appear to affect the Tab 3 8.0 nor the Tab 3 10.1. (I have tried this on the 8.0 and it works fine)

The issue is that on the gui, only text appears to be being displayed, none of the textures, backgrounds, buttons etc are shown. Below are some screenshots of the gui and while a video is being played:

http://i953.photobucket.com/albums/ae14/...f72736.png
http://i953.photobucket.com/albums/ae14/...6983c8.png

Apart from this issue, xbmc runs as smooth as butter, the gui is snappy, and HD videos appear to play without issue. The buttons work, but unfortunately you cant see them, so you have to keep touching where you think the button should be until you find it

Below are some hardware info screenshots of this particular tablet, it is running the stock Samsung firmware, unrooted:

http://i953.photobucket.com/albums/ae14/...173421.png
http://i953.photobucket.com/albums/ae14/...fa15fc.png
http://i953.photobucket.com/albums/ae14/...924f70.png

I have tried the following versions of xbmc with the same results:
XBMC current version 12.3
XBMC Gotham Alpha 8
XBMC Gotham Alpha 11
XAF XBMC for Neon enable touch device

Below are the debug logs for the Gotham Alpha 11
xbmc.old.log - http://xbmclogs.com/show.php?id=104697
xbmc.log - http://xbmclogs.com/show.php?id=104696

I have tried copying the skin folder over from a raspberry pi, but that didnt make any difference either

I am happy to dig into this issue, as it would seem to be something simple (hoping its just some setting somewhere) but just not sure where to start looking

Glen

[Koying]

Thanks for the summary, sossy.

That probably hints to an opengl ES issue with the Vivante GC1000 GPU used in the Tab 3 7.0
The XBMC logs shows nothing.
Maybe a logcat might bring some more light, but it is anyway unlikely we'd be able to fix the issue, as I don't think any of the devs have such a device.

[sheepybach]

sossy,
OK sorry my bad I was certain you was talking about SG Tab3 10.1. From your screen shots you've seemed to have lost your background setup or it's not enabled, having said that I've failed again to repeat this on any of my tabs

[CastNoShadow]

sossy,
I just checked and my current firmware is also 3.4.5 on the tab 3 7.0. XBMC is still humming away nicely. One thing you might want to try, is to reflash the stock firmware, not sure why that worked for me, but after the flash I opened xbmc and it was good as new. I didn't even have to reinstall it.

[sossy]

Hi Koying, thanks for the response. It looks like to get a logcat I need to root the tablet. I havent quite got that far yet. I will post one if I can build up the nerve to root


Castnoshadow: your post gives me hope. you mentioned earlier that you had rooted your tablet and then went back to stock firmware, does this mean you have root access with the stock firmware, or are you back to factory?
if you can, can you point me in the direction of how you re-flashed the stock firmware, and which country firmware you used, so I can re-produce what you did

Glen

[CastNoShadow]

sossy,
when I went back to stock firmware I lost root access. No big deal really, as there were very few things i needed it for, and I can live without them for now. You will need a few things, first the firmware, I used SM-T210R "Cellular South" as the device and region. but you should probably use the same one you currently are to avoid any problems. Second, you will need the drivers for your device, Samsung Kies is the best way to go. Third, you will need Odin 3.07. Lastly and most importantly, a good understanding of what you are about to do. It is possible to brick your tablet if something goes wrong. Oh, and the warranty issues, but with all that being said, it is fairly easy to do. I will PM you the links to the firmware and files needed.

[sossy]

Hi Koying

I managed to get the device rooted, so I could provide a logcat. This is for Gotham Alpha 11.

The logcat should be for XBMC starting up for the first time, and then navigating a couple of menu items.

Hope you are able to shed some light on the issue from the log

http://xbmclogs.com/show.php?id=106639

glen

[Memphiz]

Seems to be an issue with the gl driver of this particular GC1000 GPU in this device. See this QT bug entry which describes something similar:

https://bugreports.qt-project.org/browse/QTBUG-34984

No solution from them. Maybe Koying can make some more sense out of the log.

[Koying]

Thanks sossy

Key error is certainly:

Code:

gl2mERROR: result=0x0500 @ glTexImage2D

But google is not helpful on this one...

[jonny109]

Im having the same problem on my galaxy tab 3 7.0.
At first xbmc was working perfectly using the official install. Then I decided to root my tablet and now its black screen in xbmc. I used the prerooted tar file listed on this page to root my tablet.
http://www.ibtimes.co.uk/galaxy-tab370-r...210-501118