Kodi Community Forum - Raspberry PI3 - Jessie - Waveshare TouchScreen LCD 7 inch

Pages: 1 2

Hi all.

I have a PI3 running Raspbian OS with Pixel. I've made an update and upgrade of the OS.
After that, I've installed kodi using the ppa of pipplware.
For setup I was using a big monitor and everything went fine. Run kodi and done the proper setup.

Disconnected everything and connect an 7 inch LCD from Wave share; I ssh into PI, change the config.txt by adding the lines below:

Code:
max_usb_current=1

hdmi_group=2

hdmi_mode=1

hdmi_mode=87

hdmi_cvt 1024 600 60 6 0 0 0

I open PI, image on the Waveshare LCD looking fine; touch is working if I connect mouse is working also. The LCD is connected to USB port of PI.
Then, I start kodi and all I get is a black screen. I ssh into it, reboot - everything looks fine, I start kodi again - black screen.
After some research on the net I find this post "http://forum.kodi.tv/showthread.php?tid=241622&page=2" where an idea about powering the LCD screen directly - not via PI USB is given. So, I power the LCD directly, reboot, desktop shows fine . . ..but I have no touch working;
I start kodi, and everything is OK, I can make setup, go check the menus, play moovie, everything OK - but only with the mouse attached to USB of PI, so I have no touch in kodi and no touch also in the OS. The only possible access to menu and stuff is via mouse connected.

Next, I shut down, connect USB of Pi to USB of LCD screen, HDMI to HDMI, start . . . .and now the touch function is back; I start kodi, program is running, I manage to use the touch for 2-3 seconds but after that the screen goes blinking and showing different lines like in this post " http://forum.kodi.tv/showthread.php?tid=241622&page=3" - user DaniiSahne; exactly like this, after 20-30 seconds the kodi menu shows back again, able to use the touch for a while and then again a lined screen - and the story goes forever.

So is anyone able to tell me what is wrong and how to fix it?
reason is I want to test PI3+LCD as a carputer in the near future, so having touch available when using kodi is mandatory . . .

Hello again;
At least in part It seems that kodi is making such troubles when the mouse is also connected to the PI unit;
As soon as I restarted the PI, without having the mouse attached, the touch screen worked without problems.
Today, I started the system again, connected to 7'' LCD screen, started kodi and received the same behavior.

Still waiting for ideas . . . .

Do you have any kind of gamepad also connected? If yes try without it. Also try to disable the gamepad support in kodi -> peripherals. Its possible that your mouse is making conflict with the unoficial gamepad support in this version of kodi.

Hello,

I've tried changing also resolution in kodi to the specific value of the LCD screen 1024x600. No change in behavior.
I've tried booting without having the mouse connected; I'll try also without keyboard . . just for the heck of it.
I do not have a gamepad connected to the Pi.
I think is related with the resolution that kodi is changing when switching between different panels (? could be); it is for sure when trying to play the movie - at that point the screen goes crazy in full and nothing is able to display.

I've tested the LCD in raspbian only, playing a sample .mkv with omxplayer, the image is very nice and shows no problem;

One other thing . . . at some points, in the right upper side of the screen a red thermometer is shown; does anyone knows what this stands for ?

Does "hdmi_force_mode=1" added to config.txt help?

Hi popcornmix;

I will try that too; found out that info in another post but the user instructed to add this line to config.txt reported no change.
I will try that myself, I am a bit concerned about the fact that last time, editing the config.txt with several options leaded into boot problems, unable to access the PI via ssh and in the end I had to reinstall the OS.

I will try to mitigate this issue in the future by having separate SD cards for : "kodi based OD" - just for playing media and another SD card for a test system; I hope the PI will resist to several changes/replace of the SD card per day.

I do have another idea to spin; could I try to purge kodi install, or better a re-install of raspbian, after that a setup of the touch LCD screen, and after that an install of kodi ? I am thinking into the direction that the first install of kodi having only the touch LCD attached will adapt the resolution change and so on . . ; if this is not working I may try to install the drivers provided by the Waveshare - but if I've got this correct, they only affect the v1.1 firmware - and I have the 2.1 - which basically do not need the manufacturer's drivers . . . .

nope, no improvement when
hdmi_force_mode=1
is added to the config.txt

Any other ideas ?

With hdmi_force_mode=1 present, report output of

Code:
vcgencmd get_throttled

tvservice -s

before and after launching kodi. Also post a debug log (wiki).

Code:
pi@raspberrypi:~ $ vcgencmd get_throttled

throttled=0x0

pi@raspberrypi:~ $ tvservice -s

state 0x120006 [DVI DMT (87) RGB full 15:9], 1024x600 @ 60.00Hz, progressive

AFTER KODI START

pi@raspberrypi:~ $ vcgencmd get_throttled

throttled=0x20002

pi@raspberrypi:~ $ tvservice -s

state 0x12000a [HDMI DMT (87) RGB full 15:9], 1024x600 @ 59.94Hz, progressive

How do I post the log files ? I have kodi.log which is 6 MB and kodi.old.log which is around 600 kb.

Enable debug logging. Reboot. Post ~/.kodi/temp/kodi.log to a paste site like pastebin.com.
It won't be very large after rebooting.

http://pastebin.com/1VbvH0Fq

Actually I have rebooted but the file doesn't change; so I've copied the last information what I guess it stands for the activity last time - around midnight (11PM-00AM). I hope it will show something.

(2016-11-02, 23:50)need4help Wrote: [ -> ]http://pastebin.com/1VbvH0Fq

Doesn't have debug logging enabled and seems to stop prematurely so doesn't really tell me anything.

Hi popcornmix, I am not sure why is this happening . . . please see picture where log is checked inside kodi.
(http://imgur.com/a/BWYfl)

watch gallery

http://pastebin.com/tsdStPvn
http://pastebin.com/i0GPZbCn
http://pastebin.com/EHpSLZSA

Those are from the .log file this morning; the kodi.log has now 41 Mb so I cannot post everything; should I place the entire file into a file transfer server ?

The log file file won't be 41M after just rebooting and grabbing the log.

Code:
08:42:30 170.926804 T:1944121344  NOTICE: ARM mem: 944MB GPU mem: 64MB MPG2:0 WVC1:0

That will never work. We recommend gpu_mem=256 (in config.txt) for Pi2/Pi3.

pfoaaa man, you may save the day with this one . . . .I had it in 256, and than the OS got broken and I've re-installed the raspbian.
By chance I forgot to rechange this value due to the fact that once connected to the TV, even if it's a little bit slower the software is working.
I'll get it fixed.
Any other issues that might trigger your attention beside that ?

Pages: 1 2