Re: Building Tizen IVI 3.0 locally with gbs

[venkat]

  
  
Hi Paul,

With the "latest" version also, I am getting the same errors. Can
anyone help me out to fix this?

Regards,
Venkat
 
On Tuesday 03 September 2013 06:54 AM,
  Hanchett, Paul wrote:


  
Hi Venkat--


From the
  errors you're seeing, I'd wonder if somehow the sources are
  not in sync with the build process.  It looks to me like
  you've gotten a bit farther than we have so far... I'm away
  from the company computer, but I think that we've fallen back
  to using 'latest' vs 'snapshot' branches for our builds.  


Steve Maurer
  could tell you more, he's in the thick of it.

  

Sorry that I
  don't have an answer for you.  :-(



  Paul


  
  

  
Paul Hanchett
---
Infotainment Engineer
MSX on behalf of Jaguar Land Rover
One World Trade Center, 121 Southwest Salmon Street, 11th
Floor, Portland, Oregon, 97204 

Email: phanc...@jaguarlandrover.com
---

Business Details:
Jaguar Land Rover Limited
Registered Office: Abbey Road, Whitley, Coventry CV3 4LF 
Registered in England No: 1672070
  



On Mon, Sep 2, 2013 at 6:20 AM, venkat
  
  wrote:
  
 Hi Geoffroy,
  
  While building 3.0 M2 packages,  we are able to build most
  of the upstream packages except some. I have attached logs
  for libcap and smack packages. Can you please let me know
  what is the issue?
  
  We are using Ubuntu 12.04.
  
  Regards,
  Venkat
  

  
  On Thursday 29 August 2013 03:07 PM, VanCutsem,
Geoffroy wrote:
  
  

  Hi

  Venkat,
   
  libtapi - 
  Can I use the same tag (that exists in the
  manifest?
  [Geoffroy]
  Yes
  wrt - What should be the tag to be used?
  [Geoffroy]
  Replace the ‘revision’ tag by this one: submit/tizen/20130716.222709-0-ga8cd04578ff0ff57ef5e1a8ad3c1c261df9a1d43
   
  I’ve

  also attached that very manifest file with the
  modifications in for your convenience.
   
  Thanks,
  Geoffroy
   
  

  
From:
venkat [mailto:patn...@allgosystems.com]

Sent: Thursday, August 29, 2013
11:31 AM
To: VanCutsem, Geoffroy
Cc: ivi@lists.tizen.org
Subject: Re: Building Tizen IVI
3.0 locally with gbs
  

 
Hi Geoffroy,
  
  I am using this manifest.xml
  http://download.tizen.org/releases/milestone/tizen/ivi/tizen_20130729.2/images/ivi-release-mbr-i586/tizen_20130729.2-ivi-release-mbr-i586.manifest.xml

libtapi -  Can I use the same tag (that
exists in the manifest?
wrt - What should be the tag to be used?

  On Thursday 29 August
2013 02:44 PM, VanCutsem, Geoffroy wrote:


  Hi

  Venkat,
   
  These

  are known issues which I have reported to
  our team already:
  -
  libslp-tapi: this package was recently
  renamed to libtapi but the manifest file
  has not yet been updated. I expect this to
  be done shortly and in the meantime you
 

Re: IVI Qt RPMs preview

[Tomasz Olszak]

2013/9/6 Prabhuram Murugan 

> Hi,
>
> I have to try it on TIZEN IVI 2.0... can it work with X, any suggestions ?
>
>>
>>
>
Yeah it's for IVI 3.0 M2 image I mentioned (
http://download.tizen.org/releases/daily/tizen/ivi/tizen_20130829.9/))

-- 
regards / pozdrawiam, Tomasz Olszak
Qt for Tizen | http://qt-project.org/wiki/Tizen
Qt Certified Developer | http://qt-project.org
http://linkedin.com/in/tolszak
___
IVI mailing list
IVI@lists.tizen.org
https://lists.tizen.org/listinfo/ivi

RE: egalax touch screen not detected by X

[Chang, Esmond]

Did you try to use the mtev driver? As I know, touch device should use mtev 
driver instead of evdev.

Regards,
Esmond

From: ivi-boun...@lists.tizen.org [mailto:ivi-boun...@lists.tizen.org] On 
Behalf Of Prabhuram Murugan
Sent: Friday, September 06, 2013 10:39 AM
To: Clark, Joel
Cc: IVI Tizen
Subject: Re: egalax touch screen not detected by X


I extracted the binary file from TIZEN 1.0 rpm,

xinput_calibrator --list
No calibratable devices found.
it is not able find any touch device. I think this is because it is detected as 
a mouse device .

And the Xorg log file in /var/log/Xorg.0.log shows the below log,

[10.434] (II) config/udev: Adding input device eGalax Inc. USB 
TouchController (/dev/input/mouse1)
[10.434] (II) No input driver specified, ignoring this device.
[10.434] (II) This device may have been added with another device file.
I am wondering if the values in my Xorg configuration file is proper ?

Section "InputClass"
Identifier "eGalax Inc. USB TouchController"
MatchIsPointer "on"
MatchDevicePath "/dev/input/event*"
Option "Calibration" "17 1000 27 1000"
Driver "evdev"
EndSection
Jeol,
it may sound stupid,
Actually I launched a application and touched across the entire touch screen ...
Screen was filled with buttons, but non of them received any click event...

Regards,
Prabhuram M


On Fri, Sep 6, 2013 at 9:53 AM, Clark, Joel 
mailto:joel.cl...@intel.com>> wrote:
I’ll question my on assertion, Should evdev recognize a “single point, 
resistive touch screen device”, as a USB Mouse or as some other device? For 
multi-touch we know mouse did not work. But I think it also did not work for 
single touch, where when it was treated as a mouse, we could swipe (“drag” like 
a mouse), but could not tap (“click” like a mouse).

Regards
Joel


From: Clark, Joel
Sent: Thursday, September 05, 2013 5:46 PM
To: Rees, Kevron M; Prabhuram Murugan
Cc: IVI Tizen
Subject: RE: egalax touch screen not detected by X

It sounds like the same bug as in Wayland.  It is being recognized as a USB 
device, but not as a touchscreen, so it defaults to being a mouse, which it is 
not.

When you say “touch input is not working with this board”, what specifically is 
the failure mode? Does it respond to taps at all?  Does it respond to “drag” at 
all?

Regards
Joel


From: ivi-boun...@lists.tizen.org 
[mailto:ivi-boun...@lists.tizen.org] On Behalf Of Rees, Kevron

Sent: Thursday, September 05, 2013 5:41 PM
To: Prabhuram Murugan
Cc: IVI Tizen
Subject: Re: egalax touch screen not detected by X

it sounds like it is being recognized.  perhaps it just needs calibration?  I 
recall there is an xinput_calibrator tool that you might be able to use to 
calibrate it.  I don't remember if that tool was included in Tizen 2.0 though.
-Kevron

On Thu, Sep 5, 2013 at 5:03 PM, Prabhuram Murugan 
mailto:prabhuram.muru...@gmail.com>> wrote:
Hi All,
I am using TIZEN 2.0 ...
Jeol,

I gone through the changes, https://review.tizen.org/gerrit/#/c/6047/ , but it 
is for Weston and TIZEN 3.0

however to fix this issues in TIZEN 2.0, I am looking in to 
adaptation/xorg/driver/xserver-xorg-input-evdev

can you advice, if this is the right point to start ,

Rusty,
Yes, we are using a single point, resistive touch screen device.
and from the mount point /dev/input/mouse1 looks it is detected as the mouse 
device.
TIZEN 2.0 doesnt support single touch device ?


On Fri, Sep 6, 2013 at 2:52 AM, Abramski, Adam M 
mailto:adam.m.abram...@intel.com>> wrote:
I believe he mentions below that he's running 2.0, NOT 3.0.
Adam

-Original Message-
From: ivi-boun...@lists.tizen.org 
[mailto:ivi-boun...@lists.tizen.org] On 
Behalf Of Rusty Lynch
Sent: Thursday, September 05, 2013 8:58 AM
To: Clark, Joel
Cc: IVI Tizen
Subject: Re: egalax touch screen not detected by X

Actually... that fix only applies when you are using wayland.

I'm not sure if you were using a touchscreen with the same issue, but we hit an 
issue when a vendor wired up an old style single point resistive screen on top 
of an egalax touchscreen controller, where weston didn't recognize the device 
as touch (since it didn't support the modern multipoint protocol), and treated 
it as a mouse, but then the device would emit TOUCH_BTN instead of a left or 
right mouse button.

So... it actually worked, but no software is listening for this little known 
button value so kind of pointless.

--rusty

On Thu, 2013-09-05 at 14:21 +, Clark, Joel wrote:
> This has been fixed in Tizen IVI 3.0
>  https://bugs.tizen.org/jira/i#browse/TIVI-1086
>
>
>
> You might want to look at these patches:
>
> https://bugs.freedesktop.org/show_bug.cgi?id=54428
>
>
>
> https://review.tizen.org/gerrit/#/c/6047/
>
>
>
> with the fix the touchscreen is no longer recognized as a mouse
> device.
>
>
>
> Regards
>
> Joel
>
>
>
>
>
> From: ivi-boun...@lists.tiz

Re: egalax touch screen not detected by X

[Prabhuram Murugan]

I extracted the binary file from TIZEN 1.0 rpm,

xinput_calibrator --list
No calibratable devices found.

it is not able find any touch device. I think this is because it is
detected as a mouse device .

And the Xorg log file in /var/log/Xorg.0.log shows the below log,

[10.434] (II) config/udev: Adding input device eGalax Inc. USB
TouchController (/dev/input/mouse1)
[10.434] (II) No input driver specified, ignoring this device.
[10.434] (II) This device may have been added with another device file.

I am wondering if the values in my Xorg configuration file is proper ?

Section "InputClass"
Identifier "eGalax Inc. USB TouchController"
MatchIsPointer "on"
MatchDevicePath "/dev/input/event*"
Option "Calibration" "17 1000 27 1000"
Driver "evdev"
EndSection

Jeol,
it may sound stupid,
Actually I launched a application and touched across the entire touch
screen ...
Screen was filled with buttons, but non of them received any click event...

Regards,
Prabhuram M




On Fri, Sep 6, 2013 at 9:53 AM, Clark, Joel  wrote:

>  I’ll question my on assertion, Should evdev recognize a “single point,
> resistive touch screen device”, as a USB Mouse or as some other device?
> For multi-touch we know mouse did not work. But I think it also did not
> work for single touch, where when it was treated as a mouse, we could swipe
> (“drag” like a mouse), but could not tap (“click” like a mouse).
>
> ** **
>
> Regards
>
> Joel
>
> ** **
>
> ** **
>
> *From:* Clark, Joel
> *Sent:* Thursday, September 05, 2013 5:46 PM
> *To:* Rees, Kevron M; Prabhuram Murugan
> *Cc:* IVI Tizen
> *Subject:* RE: egalax touch screen not detected by X
>
> ** **
>
> It sounds like the same bug as in Wayland.  It is being recognized as a
> USB device, but not as a touchscreen, so it defaults to being a mouse,
> which it is not. 
>
> ** **
>
> When you say “touch input is not working with this board”, what
> specifically is the failure mode? Does it respond to taps at all?  Does it
> respond to “drag” at all?
>
> ** **
>
> Regards
>
> Joel
>
> ** **
>
> ** **
>
> *From:* ivi-boun...@lists.tizen.org 
> [mailto:ivi-boun...@lists.tizen.org]
> *On Behalf Of *Rees, Kevron
>
> *Sent:* Thursday, September 05, 2013 5:41 PM
> *To:* Prabhuram Murugan
> *Cc:* IVI Tizen
> *Subject:* Re: egalax touch screen not detected by X
>
> ** **
>
> it sounds like it is being recognized.  perhaps it just needs
> calibration?  I recall there is an xinput_calibrator tool that you might be
> able to use to calibrate it.  I don't remember if that tool was included in
> Tizen 2.0 though.
>
> -Kevron
>
> ** **
>
> On Thu, Sep 5, 2013 at 5:03 PM, Prabhuram Murugan <
> prabhuram.muru...@gmail.com> wrote:
>
> Hi All,
>
> I am using TIZEN 2.0 ...
>
> Jeol,
>
> ** **
>
> I gone through the changes, https://review.tizen.org/gerrit/#/c/6047/ ,
> but it is for Weston and TIZEN 3.0
>
> however to fix this issues in TIZEN 2.0, I am looking in to
> adaptation/xorg/driver/xserver-xorg-input-evdev
>
> can you advice, if this is the right point to start ,
>
> Rusty,
>
> Yes, we are using a single point, resistive touch screen device.
>
> and from the mount point */dev/input/mouse1* looks it is detected as the
> mouse device.
>
> TIZEN 2.0 doesnt support single touch device ? 
>
> ** **
>
> ** **
>
> On Fri, Sep 6, 2013 at 2:52 AM, Abramski, Adam M <
> adam.m.abram...@intel.com> wrote:
>
> I believe he mentions below that he's running 2.0, NOT 3.0.
> Adam
>
>
> -Original Message-
> From: ivi-boun...@lists.tizen.org [mailto:ivi-boun...@lists.tizen.org] On
> Behalf Of Rusty Lynch
> Sent: Thursday, September 05, 2013 8:58 AM
> To: Clark, Joel
> Cc: IVI Tizen
> Subject: Re: egalax touch screen not detected by X
>
> Actually... that fix only applies when you are using wayland.
>
> I'm not sure if you were using a touchscreen with the same issue, but we
> hit an issue when a vendor wired up an old style single point resistive
> screen on top of an egalax touchscreen controller, where weston didn't
> recognize the device as touch (since it didn't support the modern
> multipoint protocol), and treated it as a mouse, but then the device would
> emit TOUCH_BTN instead of a left or right mouse button.
>
> So... it actually worked, but no software is listening for this little
> known button value so kind of pointless.
>
> --rusty
>
> On Thu, 2013-09-05 at 14:21 +, Clark, Joel wrote:
> > This has been fixed in Tizen IVI 3.0
> >  https://bugs.tizen.org/jira/i#browse/TIVI-1086
> >
> >
> >
> > You might want to look at these patches:
> >
> > https://bugs.freedesktop.org/show_bug.cgi?id=54428
> >
> >
> >
> > https://review.tizen.org/gerrit/#/c/6047/
> >
> >
> >
> > with the fix the touchscreen is no longer recognized as a mouse
> > device.
> >
> >
> >
> > Regards
> >
> > Joel
> >
> >
> >
> >
> >
> > From: ivi-boun...@lists.tizen.org [mailto:ivi-boun...@lists.tizen.or

RE: egalax touch screen not detected by X

[Clark, Joel]

I’ll question my on assertion, Should evdev recognize a “single point, 
resistive touch screen device”, as a USB Mouse or as some other device? For 
multi-touch we know mouse did not work. But I think it also did not work for 
single touch, where when it was treated as a mouse, we could swipe (“drag” like 
a mouse), but could not tap (“click” like a mouse).

Regards
Joel


From: Clark, Joel
Sent: Thursday, September 05, 2013 5:46 PM
To: Rees, Kevron M; Prabhuram Murugan
Cc: IVI Tizen
Subject: RE: egalax touch screen not detected by X

It sounds like the same bug as in Wayland.  It is being recognized as a USB 
device, but not as a touchscreen, so it defaults to being a mouse, which it is 
not.

When you say “touch input is not working with this board”, what specifically is 
the failure mode? Does it respond to taps at all?  Does it respond to “drag” at 
all?

Regards
Joel


From: ivi-boun...@lists.tizen.org 
[mailto:ivi-boun...@lists.tizen.org] On Behalf Of Rees, Kevron
Sent: Thursday, September 05, 2013 5:41 PM
To: Prabhuram Murugan
Cc: IVI Tizen
Subject: Re: egalax touch screen not detected by X

it sounds like it is being recognized.  perhaps it just needs calibration?  I 
recall there is an xinput_calibrator tool that you might be able to use to 
calibrate it.  I don't remember if that tool was included in Tizen 2.0 though.
-Kevron

On Thu, Sep 5, 2013 at 5:03 PM, Prabhuram Murugan 
mailto:prabhuram.muru...@gmail.com>> wrote:
Hi All,
I am using TIZEN 2.0 ...
Jeol,

I gone through the changes, https://review.tizen.org/gerrit/#/c/6047/ , but it 
is for Weston and TIZEN 3.0

however to fix this issues in TIZEN 2.0, I am looking in to 
adaptation/xorg/driver/xserver-xorg-input-evdev

can you advice, if this is the right point to start ,

Rusty,
Yes, we are using a single point, resistive touch screen device.
and from the mount point /dev/input/mouse1 looks it is detected as the mouse 
device.
TIZEN 2.0 doesnt support single touch device ?


On Fri, Sep 6, 2013 at 2:52 AM, Abramski, Adam M 
mailto:adam.m.abram...@intel.com>> wrote:
I believe he mentions below that he's running 2.0, NOT 3.0.
Adam

-Original Message-
From: ivi-boun...@lists.tizen.org 
[mailto:ivi-boun...@lists.tizen.org] On 
Behalf Of Rusty Lynch
Sent: Thursday, September 05, 2013 8:58 AM
To: Clark, Joel
Cc: IVI Tizen
Subject: Re: egalax touch screen not detected by X

Actually... that fix only applies when you are using wayland.

I'm not sure if you were using a touchscreen with the same issue, but we hit an 
issue when a vendor wired up an old style single point resistive screen on top 
of an egalax touchscreen controller, where weston didn't recognize the device 
as touch (since it didn't support the modern multipoint protocol), and treated 
it as a mouse, but then the device would emit TOUCH_BTN instead of a left or 
right mouse button.

So... it actually worked, but no software is listening for this little known 
button value so kind of pointless.

--rusty

On Thu, 2013-09-05 at 14:21 +, Clark, Joel wrote:
> This has been fixed in Tizen IVI 3.0
>  https://bugs.tizen.org/jira/i#browse/TIVI-1086
>
>
>
> You might want to look at these patches:
>
> https://bugs.freedesktop.org/show_bug.cgi?id=54428
>
>
>
> https://review.tizen.org/gerrit/#/c/6047/
>
>
>
> with the fix the touchscreen is no longer recognized as a mouse
> device.
>
>
>
> Regards
>
> Joel
>
>
>
>
>
> From: ivi-boun...@lists.tizen.org 
> [mailto:ivi-boun...@lists.tizen.org]
> On Behalf Of Prabhuram Murugan
> Sent: Thursday, September 05, 2013 5:38 AM
> To: IVI Tizen
> Subject: egalax touch screen not detected by X
>
>
>
> Hi ,
>
>
> I am using a USB based touch screen LCD for TIZEN on NDiS 166 board.
>
>
> But the touch input is not working with this board.
> I came across many bugs raised in TIZEN bug site, but they are mostly
> for touch calibration.
>
>
> In my case the touch screen is detected by the kernel but "xinput
> list" doesnt list my touch screen device at all. Below are dmesg and
> xinput list logs 
>
>
> I am using TIZEN 2.0 release.
>
>
>
>
>
> DMESG
>
>
> [   12.703678] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
> [   21.528514] composite sync not supported
> [  884.484925] usb 2-1.1: USB disconnect, device number 3 [
> 885.940235] usb 2-1.1: new low-speed USB device number 7 using
> ehci-pci [  886.020179] usb 2-1.1: New USB device found,
> idVendor=0eef,
> idProduct=0001
> [  886.020184] usb 2-1.1: New USB device strings: Mfr=1, Product=2,
> SerialNumber=0
> [  886.020188] usb 2-1.1: Product: USB TouchController [  886.020191]
> usb 2-1.1: Manufacturer: eGalax Inc.
> [  886.022735] input: eGalax Inc. USB TouchController as
> /devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/input/input9
>
> -sh-4.1# xinput list
> ⎡ Virtual core pointer

RE: egalax touch screen not detected by X

[Clark, Joel]

It sounds like the same bug as in Wayland.  It is being recognized as a USB 
device, but not as a touchscreen, so it defaults to being a mouse, which it is 
not.

When you say “touch input is not working with this board”, what specifically is 
the failure mode? Does it respond to taps at all?  Does it respond to “drag” at 
all?

Regards
Joel


From: ivi-boun...@lists.tizen.org [mailto:ivi-boun...@lists.tizen.org] On 
Behalf Of Rees, Kevron
Sent: Thursday, September 05, 2013 5:41 PM
To: Prabhuram Murugan
Cc: IVI Tizen
Subject: Re: egalax touch screen not detected by X

it sounds like it is being recognized.  perhaps it just needs calibration?  I 
recall there is an xinput_calibrator tool that you might be able to use to 
calibrate it.  I don't remember if that tool was included in Tizen 2.0 though.
-Kevron

On Thu, Sep 5, 2013 at 5:03 PM, Prabhuram Murugan 
mailto:prabhuram.muru...@gmail.com>> wrote:
Hi All,
I am using TIZEN 2.0 ...
Jeol,

I gone through the changes, https://review.tizen.org/gerrit/#/c/6047/ , but it 
is for Weston and TIZEN 3.0

however to fix this issues in TIZEN 2.0, I am looking in to 
adaptation/xorg/driver/xserver-xorg-input-evdev

can you advice, if this is the right point to start ,

Rusty,
Yes, we are using a single point, resistive touch screen device.
and from the mount point /dev/input/mouse1 looks it is detected as the mouse 
device.
TIZEN 2.0 doesnt support single touch device ?


On Fri, Sep 6, 2013 at 2:52 AM, Abramski, Adam M 
mailto:adam.m.abram...@intel.com>> wrote:
I believe he mentions below that he's running 2.0, NOT 3.0.
Adam

-Original Message-
From: ivi-boun...@lists.tizen.org 
[mailto:ivi-boun...@lists.tizen.org] On 
Behalf Of Rusty Lynch
Sent: Thursday, September 05, 2013 8:58 AM
To: Clark, Joel
Cc: IVI Tizen
Subject: Re: egalax touch screen not detected by X

Actually... that fix only applies when you are using wayland.

I'm not sure if you were using a touchscreen with the same issue, but we hit an 
issue when a vendor wired up an old style single point resistive screen on top 
of an egalax touchscreen controller, where weston didn't recognize the device 
as touch (since it didn't support the modern multipoint protocol), and treated 
it as a mouse, but then the device would emit TOUCH_BTN instead of a left or 
right mouse button.

So... it actually worked, but no software is listening for this little known 
button value so kind of pointless.

--rusty

On Thu, 2013-09-05 at 14:21 +, Clark, Joel wrote:
> This has been fixed in Tizen IVI 3.0
>  https://bugs.tizen.org/jira/i#browse/TIVI-1086
>
>
>
> You might want to look at these patches:
>
> https://bugs.freedesktop.org/show_bug.cgi?id=54428
>
>
>
> https://review.tizen.org/gerrit/#/c/6047/
>
>
>
> with the fix the touchscreen is no longer recognized as a mouse
> device.
>
>
>
> Regards
>
> Joel
>
>
>
>
>
> From: ivi-boun...@lists.tizen.org 
> [mailto:ivi-boun...@lists.tizen.org]
> On Behalf Of Prabhuram Murugan
> Sent: Thursday, September 05, 2013 5:38 AM
> To: IVI Tizen
> Subject: egalax touch screen not detected by X
>
>
>
> Hi ,
>
>
> I am using a USB based touch screen LCD for TIZEN on NDiS 166 board.
>
>
> But the touch input is not working with this board.
> I came across many bugs raised in TIZEN bug site, but they are mostly
> for touch calibration.
>
>
> In my case the touch screen is detected by the kernel but "xinput
> list" doesnt list my touch screen device at all. Below are dmesg and
> xinput list logs 
>
>
> I am using TIZEN 2.0 release.
>
>
>
>
>
> DMESG
>
>
> [   12.703678] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
> [   21.528514] composite sync not supported
> [  884.484925] usb 2-1.1: USB disconnect, device number 3 [
> 885.940235] usb 2-1.1: new low-speed USB device number 7 using
> ehci-pci [  886.020179] usb 2-1.1: New USB device found,
> idVendor=0eef,
> idProduct=0001
> [  886.020184] usb 2-1.1: New USB device strings: Mfr=1, Product=2,
> SerialNumber=0
> [  886.020188] usb 2-1.1: Product: USB TouchController [  886.020191]
> usb 2-1.1: Manufacturer: eGalax Inc.
> [  886.022735] input: eGalax Inc. USB TouchController as
> /devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/input/input9
>
> -sh-4.1# xinput list
> ⎡ Virtual core pointerid=2[master pointer
> (3)]
> ⎜   ↳ Virtual core XTEST pointer  id=4[slave
> pointer  (2)]
> ⎜   ↳ SEJIN SEJIN USB Mini Trackball Keyboard id=11[slave
> pointer  (2)]
> ⎣ Virtual core keyboard   id=3[master keyboard
> (2)]
> ↳ Virtual core XTEST keyboard id=5[slave
> keyboard (3)]
> ↳ SEJIN SEJIN USB Mini Trackball Keyboard id=10[slave
> keyboard (3)]
> ∼ Power Buttonid=6[floating slave]
> ∼ Video Bus  

Re: egalax touch screen not detected by X

[Rees, Kevron]

it sounds like it is being recognized.  perhaps it just needs calibration?
I recall there is an xinput_calibrator tool that you might be able to use
to calibrate it.  I don't remember if that tool was included in Tizen 2.0
though.

-Kevron


On Thu, Sep 5, 2013 at 5:03 PM, Prabhuram Murugan <
prabhuram.muru...@gmail.com> wrote:

> Hi All,
>
> I am using TIZEN 2.0 ...
>
> Jeol,
>
> I gone through the changes, https://review.tizen.org/gerrit/#/c/6047/ ,
> but it is for Weston and TIZEN 3.0
>
> however to fix this issues in TIZEN 2.0, I am looking in to
> adaptation/xorg/driver/xserver-xorg-input-evdev
>
> can you advice, if this is the right point to start ,
>
> Rusty,
> Yes, we are using a single point, resistive touch screen device.
> and from the mount point */dev/input/mouse1* looks it is detected as the
> mouse device.
>
> TIZEN 2.0 doesnt support single touch device ?
>
>
>
>
> On Fri, Sep 6, 2013 at 2:52 AM, Abramski, Adam M <
> adam.m.abram...@intel.com> wrote:
>
>> I believe he mentions below that he's running 2.0, NOT 3.0.
>> Adam
>>
>> -Original Message-
>> From: ivi-boun...@lists.tizen.org [mailto:ivi-boun...@lists.tizen.org]
>> On Behalf Of Rusty Lynch
>> Sent: Thursday, September 05, 2013 8:58 AM
>> To: Clark, Joel
>> Cc: IVI Tizen
>> Subject: Re: egalax touch screen not detected by X
>>
>> Actually... that fix only applies when you are using wayland.
>>
>> I'm not sure if you were using a touchscreen with the same issue, but we
>> hit an issue when a vendor wired up an old style single point resistive
>> screen on top of an egalax touchscreen controller, where weston didn't
>> recognize the device as touch (since it didn't support the modern
>> multipoint protocol), and treated it as a mouse, but then the device would
>> emit TOUCH_BTN instead of a left or right mouse button.
>>
>> So... it actually worked, but no software is listening for this little
>> known button value so kind of pointless.
>>
>> --rusty
>>
>> On Thu, 2013-09-05 at 14:21 +, Clark, Joel wrote:
>> > This has been fixed in Tizen IVI 3.0
>> >  https://bugs.tizen.org/jira/i#browse/TIVI-1086
>> >
>> >
>> >
>> > You might want to look at these patches:
>> >
>> > https://bugs.freedesktop.org/show_bug.cgi?id=54428
>> >
>> >
>> >
>> > https://review.tizen.org/gerrit/#/c/6047/
>> >
>> >
>> >
>> > with the fix the touchscreen is no longer recognized as a mouse
>> > device.
>> >
>> >
>> >
>> > Regards
>> >
>> > Joel
>> >
>> >
>> >
>> >
>> >
>> > From: ivi-boun...@lists.tizen.org [mailto:ivi-boun...@lists.tizen.org]
>> > On Behalf Of Prabhuram Murugan
>> > Sent: Thursday, September 05, 2013 5:38 AM
>> > To: IVI Tizen
>> > Subject: egalax touch screen not detected by X
>> >
>> >
>> >
>> > Hi ,
>> >
>> >
>> > I am using a USB based touch screen LCD for TIZEN on NDiS 166 board.
>> >
>> >
>> > But the touch input is not working with this board.
>> > I came across many bugs raised in TIZEN bug site, but they are mostly
>> > for touch calibration.
>> >
>> >
>> > In my case the touch screen is detected by the kernel but "xinput
>> > list" doesnt list my touch screen device at all. Below are dmesg and
>> > xinput list logs 
>> >
>> >
>> > I am using TIZEN 2.0 release.
>> >
>> >
>> >
>> >
>> >
>> > DMESG
>> >
>> >
>> > [   12.703678] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
>> > [   21.528514] composite sync not supported
>> > [  884.484925] usb 2-1.1: USB disconnect, device number 3 [
>> > 885.940235] usb 2-1.1: new low-speed USB device number 7 using
>> > ehci-pci [  886.020179] usb 2-1.1: New USB device found,
>> > idVendor=0eef,
>> > idProduct=0001
>> > [  886.020184] usb 2-1.1: New USB device strings: Mfr=1, Product=2,
>> > SerialNumber=0
>> > [  886.020188] usb 2-1.1: Product: USB TouchController [  886.020191]
>> > usb 2-1.1: Manufacturer: eGalax Inc.
>> > [  886.022735] input: eGalax Inc. USB TouchController as
>> > /devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/input/input9
>> >
>> > -sh-4.1# xinput list
>> > ⎡ Virtual core pointerid=2[master pointer
>> > (3)]
>> > ⎜   ↳ Virtual core XTEST pointer  id=4[slave
>> > pointer  (2)]
>> > ⎜   ↳ SEJIN SEJIN USB Mini Trackball Keyboard id=11[slave
>> > pointer  (2)]
>> > ⎣ Virtual core keyboard   id=3[master keyboard
>> > (2)]
>> > ↳ Virtual core XTEST keyboard id=5[slave
>> > keyboard (3)]
>> > ↳ SEJIN SEJIN USB Mini Trackball Keyboard id=10[slave
>> > keyboard (3)]
>> > ∼ Power Buttonid=6[floating slave]
>> > ∼ Video Bus   id=7[floating slave]
>> > ∼ Power Buttonid=8[floating slave]
>> > ∼ Microsoft LifeCam VX-800id=9[floating slave]
>> >
>> > #cat /dev/input/mouse1
>> >
>> > )9
>> >
>> >
>> >
>> >
>> > Thanks and Regards,
>> > Prabhuram M
>> >
>> >
>> > ___
>>

Re: IVI Qt RPMs preview

[Prabhuram Murugan]

Hi,

I have to try it on TIZEN IVI 2.0... can it work with X, any suggestions ?

On Fri, Sep 6, 2013 at 6:17 AM, Rees, Kevron wrote:

> That's awesome!  Looking forward to trying them out.
>
>
> On Thu, Sep 5, 2013 at 2:14 PM, Tomasz Olszak wrote:
>
>> Some people asked about possibility of trying out Qt on IVI.
>>
>> I have prepared some RPMs. You should consider them as *alpha *but
>> working. They contain the newest Qt features:
>> * new SceneGraph
>> * Qml optimized v4
>> They will be released with incoming 5.2 version.
>>
>> I also created temporary repository for you:
>> http://oliamaru.mydevil.net/IVI_REPOS_NODEBUG_TEMPORARY/
>>
>> These packages will stay there for a week or two until I prepare
>> repositories on qt-project.org
>>
>> What's inside:
>> main Qt libraries, QtQuick, QtQml, graphicall effects, sensors, Qt Quick
>> Controls and QtQuick Controls Tizen (mobile look & feel based on OSP). Also
>> Qt development tools are available(qmake and so on)
>>
>> It is configured with wayland platform plugins so you don't need to add
>> -platform wayland argument to you app.
>>
>> I tested it only on the latest image (
>> http://download.tizen.org/releases/daily/tizen/ivi/tizen_20130829.9/)
>> in vmware. Let me know if it work on device.
>>
>> Installation steps:
>> as root on IVI:
>> zypper ar http://oliamaru.mydevil.net/IVI_REPOS_NODEBUG_TEMPORARY/
>>  QtRepos
>> zypper refresh (choose yes because i didn't signed the repo)
>> zypper in qt*
>>
>>
>> You can test some examples from here:
>> http://oliamaru.mydevil.net/additional_examples.tar.gz
>> run it wilth qmlscene.
>> However they are not adjusted for resolution.
>>
>> I know that keyboard doesn't work.
>>
>> I would like to mention once again that many things may not work.
>> "Stable" packages can be expected when Qt 5.2 will go to beta - within a
>> month or two, Until then we will continue our works on integration with
>> Mobile and IVI profiles.
>>
>> --
>> regards / pozdrawiam, Tomasz Olszak
>> Qt for Tizen | http://qt-project.org/wiki/Tizen
>> Qt Certified Developer | http://qt-project.org
>> http://linkedin.com/in/tolszak
>>
>> ___
>> IVI mailing list
>> IVI@lists.tizen.org
>> https://lists.tizen.org/listinfo/ivi
>>
>>
>
> ___
> IVI mailing list
> IVI@lists.tizen.org
> https://lists.tizen.org/listinfo/ivi
>
>
___
IVI mailing list
IVI@lists.tizen.org
https://lists.tizen.org/listinfo/ivi

Re: egalax touch screen not detected by X

[Prabhuram Murugan]

Hi All,

I am using TIZEN 2.0 ...

Jeol,

I gone through the changes, https://review.tizen.org/gerrit/#/c/6047/ , but
it is for Weston and TIZEN 3.0

however to fix this issues in TIZEN 2.0, I am looking in to
adaptation/xorg/driver/xserver-xorg-input-evdev

can you advice, if this is the right point to start ,

Rusty,
Yes, we are using a single point, resistive touch screen device.
and from the mount point */dev/input/mouse1* looks it is detected as the
mouse device.

TIZEN 2.0 doesnt support single touch device ?




On Fri, Sep 6, 2013 at 2:52 AM, Abramski, Adam M
wrote:

> I believe he mentions below that he's running 2.0, NOT 3.0.
> Adam
>
> -Original Message-
> From: ivi-boun...@lists.tizen.org [mailto:ivi-boun...@lists.tizen.org] On
> Behalf Of Rusty Lynch
> Sent: Thursday, September 05, 2013 8:58 AM
> To: Clark, Joel
> Cc: IVI Tizen
> Subject: Re: egalax touch screen not detected by X
>
> Actually... that fix only applies when you are using wayland.
>
> I'm not sure if you were using a touchscreen with the same issue, but we
> hit an issue when a vendor wired up an old style single point resistive
> screen on top of an egalax touchscreen controller, where weston didn't
> recognize the device as touch (since it didn't support the modern
> multipoint protocol), and treated it as a mouse, but then the device would
> emit TOUCH_BTN instead of a left or right mouse button.
>
> So... it actually worked, but no software is listening for this little
> known button value so kind of pointless.
>
> --rusty
>
> On Thu, 2013-09-05 at 14:21 +, Clark, Joel wrote:
> > This has been fixed in Tizen IVI 3.0
> >  https://bugs.tizen.org/jira/i#browse/TIVI-1086
> >
> >
> >
> > You might want to look at these patches:
> >
> > https://bugs.freedesktop.org/show_bug.cgi?id=54428
> >
> >
> >
> > https://review.tizen.org/gerrit/#/c/6047/
> >
> >
> >
> > with the fix the touchscreen is no longer recognized as a mouse
> > device.
> >
> >
> >
> > Regards
> >
> > Joel
> >
> >
> >
> >
> >
> > From: ivi-boun...@lists.tizen.org [mailto:ivi-boun...@lists.tizen.org]
> > On Behalf Of Prabhuram Murugan
> > Sent: Thursday, September 05, 2013 5:38 AM
> > To: IVI Tizen
> > Subject: egalax touch screen not detected by X
> >
> >
> >
> > Hi ,
> >
> >
> > I am using a USB based touch screen LCD for TIZEN on NDiS 166 board.
> >
> >
> > But the touch input is not working with this board.
> > I came across many bugs raised in TIZEN bug site, but they are mostly
> > for touch calibration.
> >
> >
> > In my case the touch screen is detected by the kernel but "xinput
> > list" doesnt list my touch screen device at all. Below are dmesg and
> > xinput list logs 
> >
> >
> > I am using TIZEN 2.0 release.
> >
> >
> >
> >
> >
> > DMESG
> >
> >
> > [   12.703678] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
> > [   21.528514] composite sync not supported
> > [  884.484925] usb 2-1.1: USB disconnect, device number 3 [
> > 885.940235] usb 2-1.1: new low-speed USB device number 7 using
> > ehci-pci [  886.020179] usb 2-1.1: New USB device found,
> > idVendor=0eef,
> > idProduct=0001
> > [  886.020184] usb 2-1.1: New USB device strings: Mfr=1, Product=2,
> > SerialNumber=0
> > [  886.020188] usb 2-1.1: Product: USB TouchController [  886.020191]
> > usb 2-1.1: Manufacturer: eGalax Inc.
> > [  886.022735] input: eGalax Inc. USB TouchController as
> > /devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/input/input9
> >
> > -sh-4.1# xinput list
> > ⎡ Virtual core pointerid=2[master pointer
> > (3)]
> > ⎜   ↳ Virtual core XTEST pointer  id=4[slave
> > pointer  (2)]
> > ⎜   ↳ SEJIN SEJIN USB Mini Trackball Keyboard id=11[slave
> > pointer  (2)]
> > ⎣ Virtual core keyboard   id=3[master keyboard
> > (2)]
> > ↳ Virtual core XTEST keyboard id=5[slave
> > keyboard (3)]
> > ↳ SEJIN SEJIN USB Mini Trackball Keyboard id=10[slave
> > keyboard (3)]
> > ∼ Power Buttonid=6[floating slave]
> > ∼ Video Bus   id=7[floating slave]
> > ∼ Power Buttonid=8[floating slave]
> > ∼ Microsoft LifeCam VX-800id=9[floating slave]
> >
> > #cat /dev/input/mouse1
> >
> > )9
> >
> >
> >
> >
> > Thanks and Regards,
> > Prabhuram M
> >
> >
> > ___
> > IVI mailing list
> > IVI@lists.tizen.org
> > https://lists.tizen.org/listinfo/ivi
>
>
> ___
> IVI mailing list
> IVI@lists.tizen.org
> https://lists.tizen.org/listinfo/ivi
> ___
> IVI mailing list
> IVI@lists.tizen.org
> https://lists.tizen.org/listinfo/ivi
>
___
IVI mailing list
IVI@lists.tizen.org
https://lists.tizen.org/listinfo/ivi

IVI Qt RPMs preview

[Tomasz Olszak]

Some people asked about possibility of trying out Qt on IVI.

I have prepared some RPMs. You should consider them as *alpha *but working.
They contain the newest Qt features:
* new SceneGraph
* Qml optimized v4
They will be released with incoming 5.2 version.

I also created temporary repository for you:
http://oliamaru.mydevil.net/IVI_REPOS_NODEBUG_TEMPORARY/

These packages will stay there for a week or two until I prepare
repositories on qt-project.org

What's inside:
main Qt libraries, QtQuick, QtQml, graphicall effects, sensors, Qt Quick
Controls and QtQuick Controls Tizen (mobile look & feel based on OSP). Also
Qt development tools are available(qmake and so on)

It is configured with wayland platform plugins so you don't need to add
-platform wayland argument to you app.

I tested it only on the latest image (
http://download.tizen.org/releases/daily/tizen/ivi/tizen_20130829.9/)
in vmware. Let me know if it work on device.

Installation steps:
as root on IVI:
zypper ar http://oliamaru.mydevil.net/IVI_REPOS_NODEBUG_TEMPORARY/ QtRepos
zypper refresh (choose yes because i didn't signed the repo)
zypper in qt*


You can test some examples from here:
http://oliamaru.mydevil.net/additional_examples.tar.gz
run it wilth qmlscene.
However they are not adjusted for resolution.

I know that keyboard doesn't work.

I would like to mention once again that many things may not work. "Stable"
packages can be expected when Qt 5.2 will go to beta - within a month or
two, Until then we will continue our works on integration with Mobile and
IVI profiles.

-- 
regards / pozdrawiam, Tomasz Olszak
Qt for Tizen | http://qt-project.org/wiki/Tizen
Qt Certified Developer | http://qt-project.org
http://linkedin.com/in/tolszak
___
IVI mailing list
IVI@lists.tizen.org
https://lists.tizen.org/listinfo/ivi

Re: IVI Qt RPMs preview

[Rees, Kevron]

That's awesome!  Looking forward to trying them out.


On Thu, Sep 5, 2013 at 2:14 PM, Tomasz Olszak wrote:

> Some people asked about possibility of trying out Qt on IVI.
>
> I have prepared some RPMs. You should consider them as *alpha *but
> working. They contain the newest Qt features:
> * new SceneGraph
> * Qml optimized v4
> They will be released with incoming 5.2 version.
>
> I also created temporary repository for you:
> http://oliamaru.mydevil.net/IVI_REPOS_NODEBUG_TEMPORARY/
>
> These packages will stay there for a week or two until I prepare
> repositories on qt-project.org
>
> What's inside:
> main Qt libraries, QtQuick, QtQml, graphicall effects, sensors, Qt Quick
> Controls and QtQuick Controls Tizen (mobile look & feel based on OSP). Also
> Qt development tools are available(qmake and so on)
>
> It is configured with wayland platform plugins so you don't need to add
> -platform wayland argument to you app.
>
> I tested it only on the latest image (
> http://download.tizen.org/releases/daily/tizen/ivi/tizen_20130829.9/)
> in vmware. Let me know if it work on device.
>
> Installation steps:
> as root on IVI:
> zypper ar http://oliamaru.mydevil.net/IVI_REPOS_NODEBUG_TEMPORARY/ QtRepos
> zypper refresh (choose yes because i didn't signed the repo)
> zypper in qt*
>
>
> You can test some examples from here:
> http://oliamaru.mydevil.net/additional_examples.tar.gz
> run it wilth qmlscene.
> However they are not adjusted for resolution.
>
> I know that keyboard doesn't work.
>
> I would like to mention once again that many things may not work. "Stable"
> packages can be expected when Qt 5.2 will go to beta - within a month or
> two, Until then we will continue our works on integration with Mobile and
> IVI profiles.
>
> --
> regards / pozdrawiam, Tomasz Olszak
> Qt for Tizen | http://qt-project.org/wiki/Tizen
> Qt Certified Developer | http://qt-project.org
> http://linkedin.com/in/tolszak
>
> ___
> IVI mailing list
> IVI@lists.tizen.org
> https://lists.tizen.org/listinfo/ivi
>
>
___
IVI mailing list
IVI@lists.tizen.org
https://lists.tizen.org/listinfo/ivi

Re: Errors installing Tizen 3.0 M2 Aug HomeScreen

[Rusty Lynch]

This is in a VM?  I totally missed that.

Running an image in a virtual machine is not supported yet.  Various
people have various workarounds, but don't expect it to work out of the
box.

--rusty

On Thu, 2013-09-05 at 09:06 -0700, Hanchett, Paul wrote:
> I'm sorry to say that "launch_app org.tizen.ico.homescreen" does not
> seem to fix my problem.   It says the app has been launched (or is
> running or some such),  but nothing on the VM screen.
> 
> 
> I'm going to try setting the environment variables mentioned elsewhere
> here to see if that makes any difference...
> 
> 
> Clearly there are a lot of people who think this is working. I'm
> perplexed that it apparently does not for me.  I'm using a VM built on
> the Aug M2 released image.  
>  1. Has anyone actually got HomeScreen running with the released
> (BIOS) image?  In a VMware VM?
>  2. When there are known issues and workarounds that need to be
> applied to get the image to work, aren't they part of the
> release notes?
>  3. I can't find these issues listed in Jira-- have they been
> reported there?  If not, how can anyone track the quality of
> the current build, or know whether or not to report a bug?
> I've had it called to my attention that changes/bug fixes are being
> committed to git/Jenkins that do not appear to be driven by bug
> reports or feature requests.  Without an explicit connection between
> commits and features/bugs, how do the QA people know what to focus on
> when they QA the build?
> 
> 
> I apologize in advance for asking these challenging questions--I'm
> just trying to understand how or if I should be reporting what I'm
> finding.  So far, when I report issues here I get the response "Yes,
> we know about that," but I can't find where to know that for myself.
> 
> 
> I really want to get into self-help mode.   :-)
> 
> 
> Thanks for your responses!
> 
> 
> Paul
> 
> 
> 
> 
> Paul Hanchett
> ---
> Infotainment Engineer
> MSX on behalf of Jaguar Land Rover
> One World Trade Center, 121 Southwest Salmon Street, 11th Floor,
> Portland, Oregon, 97204 
> 
> Email: phanc...@jaguarlandrover.com
> ---
> 
> Business Details:
> Jaguar Land Rover Limited
> Registered Office: Abbey Road, Whitley, Coventry CV3 4LF 
> Registered in England No: 1672070
> 
> 
> On Thu, Sep 5, 2013 at 12:10 AM, Ylinen, Mikko
>  wrote:
> On Thu, Sep 5, 2013 at 7:57 AM, Ylinen, Mikko
>  wrote:
> > Paul,
> >
> > On Thu, Sep 5, 2013 at 12:40 AM, Hanchett, Paul
> >  wrote:
> >> Rusty--
> >>
> >> When Tizen reboots, all I get is an empty black screen.  I
> can switch to
> >> other terminals but the wayland screen seems dead.
> >>
> >> Are you saying that with the "dead" screen, if I go to one
> of the alternate
> >> consoles and "launch_app org.tizen.ico.homescreen" that I
> should see
> >> something happening in the blank display?
> >
> > Correct. The workaround I shared last Friday on this list
> helps:
> 
> 
> Forgot to mention the bug:
> https://bugs.tizen.org/jira/browse/TIVI-1724
> 
> -- Mikko
> 
> 


___
IVI mailing list
IVI@lists.tizen.org
https://lists.tizen.org/listinfo/ivi

Re: Errors installing Tizen 3.0 M2 Aug HomeScreen

[Hanchett, Paul]

I'm sorry to say that "launch_app org.tizen.ico.homescreen" does not seem
to fix my problem.   It says the app has been launched (or is running or
some such),  but nothing on the VM screen.

I'm going to try setting the environment variables mentioned elsewhere here
to see if that makes any difference...

Clearly there are a lot of people who think this is working. I'm perplexed
that it apparently does not for me.  I'm using a VM built on the Aug M2
released image.

   1. Has anyone actually got HomeScreen running with the released (BIOS)
   image?  In a VMware VM?
   2. When there are known issues and workarounds that need to be applied
   to get the image to work, aren't they part of the release notes?
   3. I can't find these issues listed in Jira-- have they been reported
   there?  If not, how can anyone track the quality of the current build, or
   know whether or not to report a bug?

I've had it called to my attention that changes/bug fixes are being
committed to git/Jenkins that do not appear to be driven by bug reports or
feature requests.  Without an explicit connection between commits and
features/bugs, how do the QA people know what to focus on when they QA the
build?

I apologize in advance for asking these challenging questions--I'm just
trying to understand how or if I should be reporting what I'm finding.  So
far, when I report issues here I get the response "Yes, we know about
that," but I can't find where to know that for myself.

I really want to get into self-help mode.   :-)

Thanks for your responses!

Paul



Paul Hanchett
---
Infotainment Engineer
MSX on behalf of Jaguar Land Rover
One World Trade Center, 121 Southwest Salmon Street, 11th Floor, Portland,
Oregon, 97204

Email: phanc...@jaguarlandrover.com
---

Business Details:
Jaguar Land Rover Limited
Registered Office: Abbey Road, Whitley, Coventry CV3 4LF
Registered in England No: 1672070


On Thu, Sep 5, 2013 at 12:10 AM, Ylinen, Mikko wrote:

> On Thu, Sep 5, 2013 at 7:57 AM, Ylinen, Mikko 
> wrote:
> > Paul,
> >
> > On Thu, Sep 5, 2013 at 12:40 AM, Hanchett, Paul
> >  wrote:
> >> Rusty--
> >>
> >> When Tizen reboots, all I get is an empty black screen.  I can switch to
> >> other terminals but the wayland screen seems dead.
> >>
> >> Are you saying that with the "dead" screen, if I go to one of the
> alternate
> >> consoles and "launch_app org.tizen.ico.homescreen" that I should see
> >> something happening in the blank display?
> >
> > Correct. The workaround I shared last Friday on this list helps:
>
> Forgot to mention the bug:
> https://bugs.tizen.org/jira/browse/TIVI-1724
>
> -- Mikko
>
___
IVI mailing list
IVI@lists.tizen.org
https://lists.tizen.org/listinfo/ivi

RE: egalax touch screen not detected by X

[Abramski, Adam M]

I believe he mentions below that he's running 2.0, NOT 3.0.
Adam

-Original Message-
From: ivi-boun...@lists.tizen.org [mailto:ivi-boun...@lists.tizen.org] On 
Behalf Of Rusty Lynch
Sent: Thursday, September 05, 2013 8:58 AM
To: Clark, Joel
Cc: IVI Tizen
Subject: Re: egalax touch screen not detected by X

Actually... that fix only applies when you are using wayland.

I'm not sure if you were using a touchscreen with the same issue, but we hit an 
issue when a vendor wired up an old style single point resistive screen on top 
of an egalax touchscreen controller, where weston didn't recognize the device 
as touch (since it didn't support the modern multipoint protocol), and treated 
it as a mouse, but then the device would emit TOUCH_BTN instead of a left or 
right mouse button.

So... it actually worked, but no software is listening for this little known 
button value so kind of pointless.

--rusty

On Thu, 2013-09-05 at 14:21 +, Clark, Joel wrote:
> This has been fixed in Tizen IVI 3.0
>  https://bugs.tizen.org/jira/i#browse/TIVI-1086
> 
>  
> 
> You might want to look at these patches:
> 
> https://bugs.freedesktop.org/show_bug.cgi?id=54428
> 
>  
> 
> https://review.tizen.org/gerrit/#/c/6047/
> 
>  
> 
> with the fix the touchscreen is no longer recognized as a mouse 
> device.
> 
>  
> 
> Regards
> 
> Joel
> 
>  
> 
>  
> 
> From: ivi-boun...@lists.tizen.org [mailto:ivi-boun...@lists.tizen.org]
> On Behalf Of Prabhuram Murugan
> Sent: Thursday, September 05, 2013 5:38 AM
> To: IVI Tizen
> Subject: egalax touch screen not detected by X
> 
>  
> 
> Hi ,
> 
> 
> I am using a USB based touch screen LCD for TIZEN on NDiS 166 board.
> 
> 
> But the touch input is not working with this board.
> I came across many bugs raised in TIZEN bug site, but they are mostly 
> for touch calibration.
> 
> 
> In my case the touch screen is detected by the kernel but "xinput 
> list" doesnt list my touch screen device at all. Below are dmesg and 
> xinput list logs 
> 
> 
> I am using TIZEN 2.0 release.
> 
> 
>  
> 
> 
> DMESG
> 
> 
> [   12.703678] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
> [   21.528514] composite sync not supported
> [  884.484925] usb 2-1.1: USB disconnect, device number 3 [  
> 885.940235] usb 2-1.1: new low-speed USB device number 7 using 
> ehci-pci [  886.020179] usb 2-1.1: New USB device found, 
> idVendor=0eef,
> idProduct=0001
> [  886.020184] usb 2-1.1: New USB device strings: Mfr=1, Product=2,
> SerialNumber=0
> [  886.020188] usb 2-1.1: Product: USB TouchController [  886.020191] 
> usb 2-1.1: Manufacturer: eGalax Inc.
> [  886.022735] input: eGalax Inc. USB TouchController as 
> /devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/input/input9
> 
> -sh-4.1# xinput list
> ⎡ Virtual core pointerid=2[master pointer
> (3)]
> ⎜   ↳ Virtual core XTEST pointer  id=4[slave
> pointer  (2)]
> ⎜   ↳ SEJIN SEJIN USB Mini Trackball Keyboard id=11[slave
> pointer  (2)]
> ⎣ Virtual core keyboard   id=3[master keyboard
> (2)]
> ↳ Virtual core XTEST keyboard id=5[slave
> keyboard (3)]
> ↳ SEJIN SEJIN USB Mini Trackball Keyboard id=10[slave
> keyboard (3)]
> ∼ Power Buttonid=6[floating slave]
> ∼ Video Bus   id=7[floating slave]
> ∼ Power Buttonid=8[floating slave]
> ∼ Microsoft LifeCam VX-800id=9[floating slave]
> 
> #cat /dev/input/mouse1
> 
> )9   
> 
> 
> 
> 
> Thanks and Regards,
> Prabhuram M
> 
> 
> ___
> IVI mailing list
> IVI@lists.tizen.org
> https://lists.tizen.org/listinfo/ivi


___
IVI mailing list
IVI@lists.tizen.org
https://lists.tizen.org/listinfo/ivi
___
IVI mailing list
IVI@lists.tizen.org
https://lists.tizen.org/listinfo/ivi

RE: Errors installing Tizen 3.0 M2 Aug HomeScreen

[VanCutsem, Geoffroy]

Hi Paul,

From: ivi-boun...@lists.tizen.org [mailto:ivi-boun...@lists.tizen.org] On 
Behalf Of Hanchett, Paul
Sent: Thursday, September 05, 2013 6:07 PM
To: Ylinen, Mikko
Cc: ivi@lists.tizen.org; Kenneth Smith
Subject: Re: Errors installing Tizen 3.0 M2 Aug HomeScreen

I'm sorry to say that "launch_app org.tizen.ico.homescreen" does not seem to 
fix my problem.   It says the app has been launched (or is running or some 
such),  but nothing on the VM screen.

I'm going to try setting the environment variables mentioned elsewhere here to 
see if that makes any difference...

Clearly there are a lot of people who think this is working. I'm perplexed that 
it apparently does not for me.  I'm using a VM built on the Aug M2 released 
image.

  1.  Has anyone actually got HomeScreen running with the released (BIOS) 
image?  In a VMware VM?
[Geoffroy] It worked for me at some stage but not anymore... I guess it may 
come back at some stage given it's a race condition (but that's by no means a 
solution :)). I tried the fix that Mikko suggested earlier on the mailing list 
but it did not work for me. He has proposed a patch for 
https://bugs.tizen.org/jira/browse/TIVI-1724 that's under review 
https://review.tizen.org/gerrit/#/c/9809/1 but I noticed that this later patch 
is different than what I tried so my intention is to wait for it to land and 
then test it. By the way, I'm not 100% sure this is purely related to the 
HomeScreen... I've seen a similar issue where the weston desktop shell does not 
come up. It seems to be triggered much more easily with some screens than with 
others. I have one in particular here which triggers that problem nearly all 
the time.

  1.  When there are known issues and workarounds that need to be applied to 
get the image to work, aren't they part of the release notes?
[Geoffroy] I try to include the top known issues and most 'tips & tricks' in 
the release notes, so respectively:
- https://wiki.tizen.org/wiki/IVI/IVI_August_29,_3.0-M2-Aug#Top_Known_Issues
- 
https://wiki.tizen.org/wiki/IVI/IVI_August_29,_3.0-M2-Aug#Tips.2C_tricks_and_other_workarounds
I may be missing some though... in my case, I never hit that bug on my platform 
before.

  1.  I can't find these issues listed in Jira-- have they been reported there? 
 If not, how can anyone track the quality of the current build, or know whether 
or not to report a bug?
[Geoffroy] There are some filters in JIRA that have been set-up by various 
folks (from PM, Q&A, etc.): 
https://bugs.tizen.org/jira/secure/ManageFilters.jspa#filterView=popular. You 
can use some of them or do a general search. My rule of thumb is that if I 
don't find a particular issue then I do some debug and file a JIRA issue. If it 
turns out to be a duplicate, then we can later mark it as such and close it but 
at least we can track it through resolution.
I've had it called to my attention that changes/bug fixes are being committed 
to git/Jenkins that do not appear to be driven by bug reports or feature 
requests.  Without an explicit connection between commits and features/bugs, 
how do the QA people know what to focus on when they QA the build?

I apologize in advance for asking these challenging questions--I'm just trying 
to understand how or if I should be reporting what I'm finding.  So far, when I 
report issues here I get the response "Yes, we know about that," but I can't 
find where to know that for myself.

I really want to get into self-help mode.   :-)

Thanks for your responses!

Paul



Paul Hanchett
---
Infotainment Engineer
MSX on behalf of Jaguar Land Rover
One World Trade Center, 121 Southwest Salmon Street, 11th Floor, Portland, 
Oregon, 97204

Email: phanc...@jaguarlandrover.com
---

Business Details:
Jaguar Land Rover Limited
Registered Office: Abbey Road, Whitley, Coventry CV3 4LF
Registered in England No: 1672070

On Thu, Sep 5, 2013 at 12:10 AM, Ylinen, Mikko 
mailto:mikko.yli...@intel.com>> wrote:
On Thu, Sep 5, 2013 at 7:57 AM, Ylinen, Mikko 
mailto:mikko.yli...@intel.com>> wrote:
> Paul,
>
> On Thu, Sep 5, 2013 at 12:40 AM, Hanchett, Paul
> mailto:phanc...@jaguarlandrover.com>> wrote:
>> Rusty--
>>
>> When Tizen reboots, all I get is an empty black screen.  I can switch to
>> other terminals but the wayland screen seems dead.
>>
>> Are you saying that with the "dead" screen, if I go to one of the alternate
>> consoles and "launch_app org.tizen.ico.homescreen" that I should see
>> something happening in the blank display?
>
> Correct. The workaround I shared last Friday on this list helps:
Forgot to mention the bug:
https://bugs.tizen.org/jira/browse/TIVI-1724

-- Mikko

Intel Corporation NV/SA
Kings Square, Veldkant 31
2550 Kontich
RPM (Bruxelles) 0415.497.718. 
Citibank, Brussels, account 570/1031255/09

This e-mail and any attachments may contain confidential material for the sole 
use of the intended recipient(s). Any review or distribution by others is 

Re: egalax touch screen not detected by X

[Rusty Lynch]

Actually... that fix only applies when you are using wayland.

I'm not sure if you were using a touchscreen with the same issue, but we
hit an issue when a vendor wired up an old style single point resistive
screen on top of an egalax touchscreen controller, where weston didn't
recognize the device as touch (since it didn't support the modern
multipoint protocol), and treated it as a mouse, but then the device
would emit TOUCH_BTN instead of a left or right mouse button.

So... it actually worked, but no software is listening for this little
known button value so kind of pointless.

--rusty

On Thu, 2013-09-05 at 14:21 +, Clark, Joel wrote:
> This has been fixed in Tizen IVI 3.0
>  https://bugs.tizen.org/jira/i#browse/TIVI-1086
> 
>  
> 
> You might want to look at these patches:
> 
> https://bugs.freedesktop.org/show_bug.cgi?id=54428
> 
>  
> 
> https://review.tizen.org/gerrit/#/c/6047/
> 
>  
> 
> with the fix the touchscreen is no longer recognized as a mouse
> device.
> 
>  
> 
> Regards
> 
> Joel
> 
>  
> 
>  
> 
> From: ivi-boun...@lists.tizen.org [mailto:ivi-boun...@lists.tizen.org]
> On Behalf Of Prabhuram Murugan
> Sent: Thursday, September 05, 2013 5:38 AM
> To: IVI Tizen
> Subject: egalax touch screen not detected by X
> 
>  
> 
> Hi ,
> 
> 
> I am using a USB based touch screen LCD for TIZEN on NDiS 166 board.
> 
> 
> But the touch input is not working with this board.
> I came across many bugs raised in TIZEN bug site, but they are mostly
> for touch calibration.
> 
> 
> In my case the touch screen is detected by the kernel but "xinput
> list" doesnt list my touch screen device at all. Below are dmesg and
> xinput list logs 
> 
> 
> I am using TIZEN 2.0 release.
> 
> 
>  
> 
> 
> DMESG 
> 
> 
> [   12.703678] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
> [   21.528514] composite sync not supported
> [  884.484925] usb 2-1.1: USB disconnect, device number 3
> [  885.940235] usb 2-1.1: new low-speed USB device number 7 using
> ehci-pci
> [  886.020179] usb 2-1.1: New USB device found, idVendor=0eef,
> idProduct=0001
> [  886.020184] usb 2-1.1: New USB device strings: Mfr=1, Product=2,
> SerialNumber=0
> [  886.020188] usb 2-1.1: Product: USB TouchController
> [  886.020191] usb 2-1.1: Manufacturer: eGalax Inc.
> [  886.022735] input: eGalax Inc. USB TouchController
> as /devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/input/input9
> 
> -sh-4.1# xinput list
> ⎡ Virtual core pointerid=2[master pointer
> (3)]
> ⎜   ↳ Virtual core XTEST pointer  id=4[slave
> pointer  (2)]
> ⎜   ↳ SEJIN SEJIN USB Mini Trackball Keyboard id=11[slave
> pointer  (2)]
> ⎣ Virtual core keyboard   id=3[master keyboard
> (2)]
> ↳ Virtual core XTEST keyboard id=5[slave
> keyboard (3)]
> ↳ SEJIN SEJIN USB Mini Trackball Keyboard id=10[slave
> keyboard (3)]
> ∼ Power Buttonid=6[floating slave]
> ∼ Video Bus   id=7[floating slave]
> ∼ Power Buttonid=8[floating slave]
> ∼ Microsoft LifeCam VX-800id=9[floating slave]
> 
> #cat /dev/input/mouse1
> 
> )9� �� �� �� 
> 
> 
> 
> 
> Thanks and Regards,
> Prabhuram M
> 
> 
> ___
> IVI mailing list
> IVI@lists.tizen.org
> https://lists.tizen.org/listinfo/ivi


___
IVI mailing list
IVI@lists.tizen.org
https://lists.tizen.org/listinfo/ivi

RE: egalax touch screen not detected by X

[Clark, Joel]

This has been fixed in Tizen IVI 3.0  
https://bugs.tizen.org/jira/i#browse/TIVI-1086

You might want to look at these patches:

https://bugs.freedesktop.org/show_bug.cgi?id=54428


https://review.tizen.org/gerrit/#/c/6047/

with the fix the touchscreen is no longer recognized as a mouse device.

Regards
Joel


From: ivi-boun...@lists.tizen.org [mailto:ivi-boun...@lists.tizen.org] On 
Behalf Of Prabhuram Murugan
Sent: Thursday, September 05, 2013 5:38 AM
To: IVI Tizen
Subject: egalax touch screen not detected by X

Hi ,
I am using a USB based touch screen LCD for TIZEN on NDiS 166 board.
But the touch input is not working with this board.
I came across many bugs raised in TIZEN bug site, but they are mostly for touch 
calibration.
In my case the touch screen is detected by the kernel but "xinput list" doesnt 
list my touch screen device at all. Below are dmesg and xinput list logs 
I am using TIZEN 2.0 release.

DMESG

[   12.703678] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[   21.528514] composite sync not supported
[  884.484925] usb 2-1.1: USB disconnect, device number 3
[  885.940235] usb 2-1.1: new low-speed USB device number 7 using ehci-pci
[  886.020179] usb 2-1.1: New USB device found, idVendor=0eef, idProduct=0001
[  886.020184] usb 2-1.1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[  886.020188] usb 2-1.1: Product: USB TouchController
[  886.020191] usb 2-1.1: Manufacturer: eGalax Inc.
[  886.022735] input: eGalax Inc. USB TouchController as 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/input/input9

-sh-4.1# xinput list
⎡ Virtual core pointerid=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer  (2)]
⎜   ↳ SEJIN SEJIN USB Mini Trackball Keyboard id=11[slave  pointer  (2)]
⎣ Virtual core keyboard   id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard id=5[slave  keyboard (3)]
↳ SEJIN SEJIN USB Mini Trackball Keyboard id=10[slave  keyboard (3)]
∼ Power Buttonid=6[floating slave]
∼ Video Bus   id=7[floating slave]
∼ Power Buttonid=8[floating slave]
∼ Microsoft LifeCam VX-800id=9[floating slave]

#cat /dev/input/mouse1

)9� � � � � � �

Thanks and Regards,
Prabhuram M
___
IVI mailing list
IVI@lists.tizen.org
https://lists.tizen.org/listinfo/ivi

egalax touch screen not detected by X

[Prabhuram Murugan]

Hi ,
I am using a USB based touch screen LCD for TIZEN on NDiS 166 board.

But the touch input is not working with this board.
I came across many bugs raised in TIZEN bug site, but they are mostly for
touch calibration.

In my case the touch screen is detected by the kernel but "xinput list"
doesnt list my touch screen device at all. Below are dmesg and xinput list
logs 

I am using TIZEN 2.0 release.

*DMESG*

[   12.703678] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[   21.528514] composite sync not supported
[  884.484925] usb 2-1.1: USB disconnect, device number 3
[  885.940235] usb 2-1.1: new low-speed USB device number 7 using ehci-pci
[  886.020179] usb 2-1.1: New USB device found, idVendor=0eef,
idProduct=0001
[  886.020184] usb 2-1.1: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[  886.020188] usb 2-1.1: Product: USB TouchController
[  886.020191] usb 2-1.1: Manufacturer: eGalax Inc.
[  886.022735] input: eGalax Inc. USB TouchController as
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/input/input9

*-sh-4.1# xinput list*
⎡ Virtual core pointerid=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer
(2)]
⎜   ↳ SEJIN SEJIN USB Mini Trackball Keyboard id=11[slave  pointer
(2)]
⎣ Virtual core keyboard   id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard id=5[slave  keyboard
(3)]
↳ SEJIN SEJIN USB Mini Trackball Keyboard id=10[slave  keyboard
(3)]
∼ Power Buttonid=6[floating slave]
∼ Video Bus   id=7[floating slave]
∼ Power Buttonid=8[floating slave]
∼ Microsoft LifeCam VX-800id=9[floating slave]

*#cat /dev/input/mouse1

)9� � � � � � � *


Thanks and Regards,
Prabhuram M
___
IVI mailing list
IVI@lists.tizen.org
https://lists.tizen.org/listinfo/ivi

RE: Applications don't display properly on Tizen 3.0 M2 August (image)

[VanCutsem, Geoffroy]

Hi Jacky,

You don't need to adjust the /etc/sysconfig/wrt file on real hardware, this is 
only required when running in a VMware environment.

I have been unable to reproduce your problem below... could it be that you 
mistyped something by error which pulled in all these extra packages? I have 
re-installed my Nexcom system twice with a fresh Tizen IVI 3.0-M2-Aug image and 
re-installed the ico-uxf-homescreen and ico-uxf-weston-setting but it's never 
installed all these packages for me so I'm a bit at a loss.

Thanks,
Geoffroy

From: ivi-boun...@lists.tizen.org [mailto:ivi-boun...@lists.tizen.org] On 
Behalf Of Jacky (ZhiJun) Ni
Sent: Thursday, September 05, 2013 3:26 AM
To: Wang, Ning W; Hanchett, Paul; ivi@lists.tizen.org; Steven Maurer; Charles 
Hanchett; Matt Jones
Subject: RE: Applications don't display properly on Tizen 3.0 M2 August (image)

Hi All,
 I wanna tell you another phenomenon happened to me yesterday.
I have two environment: vmware and VTC720-BK, they are both installed 
with IVI-TIZEN3.0-20130829,  their default screens are both Weston shell.
   After that, I use the same way both on these two environment,
Firstly,I correct the  /etc/sysconfig/wrt:
 ELM_ENGINE=wayland_shm
ECORE_EVAS_ENGINE=wayland_shm
then root the system,
When the systems powered on, I use zypper install ico-uxf-weston-plugin 
ico-uxf-homescreen,
Here was the big difference, I got 118 rpms to install on VTC, but only  3 rpms 
on vmware, then reboot again.
Finally, I can see the home screen on VTC,  and the screen was blank on vmware.

I can't tell the true reason, but maybe it cause by the imperfect rpms 
installing.


  For example, in my VTC device,
root:~> ls /etc/smack/accesses.d/
aillibX11-datalibgio libwayland-server
app-checkerlibX11-xcb libgliblibwebsockets
app-checker-server libXau libgmodule libxcb
app-core-commonlibXcomposite  libgmp libxcb-dri2
app-core-efl   libXcursor libgnutls  libxcb-glx
app2sd libXdamage libgobject libxcb-render
aullibXextlibgpg-error   libxcb-shape
bash   libXfixes  libhogweed libxcb-shm
bundle libXi  libidn libxcb-xfixes
coreutils  libXineramalibjpeglibxml2
dbus   libXrandr  libjson-glib   mesa-libEGL
dbus-glib  libXrender libkmodmesa-libGL
ecore  libXss liblua mesa-libGLESv2
edje   libXv  liblzmamesa-libglapi
eetlibXxf86vm libmtdev   pixman
efreet libacl libnettle  pkg-config
eina   libattrlibp11-kit pkgmgr
elementary libblkid   libpng pkgmgr-client
embryo libcairo   librua pkgmgr-info
filesystem libcap libslp-db-util pkgmgr-info-parser
fontconfig libcares   libslp-utilx   pkgmgr-installer
gawk   libcurllibsmack   pwdutils
gio-branding-upstream  libdbuslibsqlite  setup
grep   libdloglibsystemd systemd
hwdata libdri2libtasn1   vconf
ico-uxf-homescreen libdrm libtasn1-tools weston
ico-uxf-utilities  libexpat   libtbm xdgmime
ico-uxf-weston-plugin  libfreetypelibwayland-client  zlib
iniparser  libgbm libwayland-cursor
libX11 libgcrypt  libwayland-egl


in my vmware:
root:~> ls /etc/smack/accesses.d/
ico-uxf-homescreen  ico-uxf-utilities  ico-uxf-weston-plugin

Maybe someone can figure out the bug.







CONFIDENTIALITY NOTICE: The information contained in this message may be 
privileged and/or confidential. If you are not the intended recipient, or 
responsible for delivering this message to the intended recipient, any review, 
forwarding, dissemination, distribution or copying of this communication or any 
attachment(s) is strictly prohibited. If you have received this message in 
error, please notify the sender immediately, and delete it and all attachments 
from your computer and network.
Intel Corporation NV/SA
Kings Square, Veldkant 31
2550 Kontich
RPM (Bruxelles) 0415.497.718. 
Citibank, Brussels, account 570/1031255/09

This e-mail and any attachments may contain confidential material for the sole 
use of the intended recipient(s). Any review or distribution by others is 
strictly prohibited. If you are not the intended recipient, please contact the 
sender and delete all copies.
___
IVI mailing list
IVI@lists.tizen.org
https://lists.tizen.org/listinfo/ivi

RE: Help~,how to enable qt applications run on IVI-tizen-3.0

[VanCutsem, Geoffroy]

I will upgrade VMware Player to version 6.0 and see if it works too. I'll 
update the list later on that.

I was able to bring up Tizen IVI 3.0-M2-Aug under VMware Player 6.0 (Ubuntu 
13.04 64b host) and start all web apps (using wrt-launcher).

The homescreen still does not work for me and I've noticed Mikko has submitted 
a patch for review but it's slightly different than the workaround mentionned 
previously [1] (which does not work for me).

Geoffroy

[1] Workaround for the homescreen

1) add a new file:



root:/usr/lib/systemd/user> cat launcher.path [Unit] Description=Path 
activation for AUL



[Path]

PathExists=/tmp/amd_ready

Unit=ico_homescreen.service



2) fix symlinks



# cd /usr/lib/systemd/user/weston.target.wants

# rm ico_homescreen.service

# ln -s ../launcher.path



3) reboot


Intel Corporation NV/SA
Kings Square, Veldkant 31
2550 Kontich
RPM (Bruxelles) 0415.497.718. 
Citibank, Brussels, account 570/1031255/09

This e-mail and any attachments may contain confidential material for the sole 
use of the intended recipient(s). Any review or distribution by others is 
strictly prohibited. If you are not the intended recipient, please contact the 
sender and delete all copies.
___
IVI mailing list
IVI@lists.tizen.org
https://lists.tizen.org/listinfo/ivi

RE: Help~,how to enable qt applications run on IVI-tizen-3.0

[VanCutsem, Geoffroy]

From: Tomasz Olszak [mailto:olszak.tom...@gmail.com]
Sent: Wednesday, September 04, 2013 9:37 PM
To: Hanchett, Paul
Cc: VanCutsem, Geoffroy; ivi@lists.tizen.org
Subject: Re: Help~,how to enable qt applications run on IVI-tizen-3.0

2013/9/4 Hanchett, Paul 
mailto:phanc...@jaguarlandrover.com>>
Yes, it comes up!  Huzzah!  I'm using VMware 9.0.
[Geoffroy] Nice. By the way, I had tested the Tizen IVI 3.0-M2-Aug release on 
VMware Player 5.0 with the couple of tricks required (i.e. enable Blacklisted 
driver in *.vmx file and use driconf to enable S3TC on Linux host). It worked 
for me. There are more places where I've seen the EVAS_ECORE_ENGINE and 
ELM_ENGINE variables are set and have updated that info on the wiki 
(https://wiki.tizen.org/wiki/IVI/IVI_3.0_VMware#Changing_the_Wayland_backend)

I will upgrade VMware Player to version 6.0 and see if it works too. I'll 
update the list later on that.

The one thing is that I declined to update the vmdk format when I was asked.  
Don't know if that might have impacted you in some way (wouldn't expect it, but 
there have been a lot of things I didn't expect on this project so far.   )
[Geoffroy] I never do it either and have never noticed any side-effect.

Intel Corporation NV/SA
Kings Square, Veldkant 31
2550 Kontich
RPM (Bruxelles) 0415.497.718. 
Citibank, Brussels, account 570/1031255/09

This e-mail and any attachments may contain confidential material for the sole 
use of the intended recipient(s). Any review or distribution by others is 
strictly prohibited. If you are not the intended recipient, please contact the 
sender and delete all copies.
___
IVI mailing list
IVI@lists.tizen.org
https://lists.tizen.org/listinfo/ivi

RE: Help~,how to enable qt applications run on IVI-tizen-3.0

[VanCutsem, Geoffroy]

PS: AFAIK VMWare workstation won't work if it is trial version.
[Geoffroy] That did work for me (at least for the 30 days that it lasted of 
course :))

Geoffroy

Intel Corporation NV/SA
Kings Square, Veldkant 31
2550 Kontich
RPM (Bruxelles) 0415.497.718. 
Citibank, Brussels, account 570/1031255/09

This e-mail and any attachments may contain confidential material for the sole 
use of the intended recipient(s). Any review or distribution by others is 
strictly prohibited. If you are not the intended recipient, please contact the 
sender and delete all copies.
___
IVI mailing list
IVI@lists.tizen.org
https://lists.tizen.org/listinfo/ivi

RE: Errors installing Tizen 3.0 M2 Aug HomeScreen

[VanCutsem, Geoffroy]

> -Original Message-
> From: ivi-boun...@lists.tizen.org [mailto:ivi-boun...@lists.tizen.org] On
> Behalf Of Rusty Lynch
> Sent: Thursday, September 05, 2013 12:40 AM
> To: Hanchett, Paul
> Cc: ivi@lists.tizen.org; Kenneth Smith
> Subject: Re: Errors installing Tizen 3.0 M2 Aug HomeScreen
> 
> The systemd log garbage is a red herring.

As mentionned by Rusty, this is a different issue. It's tracked in 
https://bugs.tizen.org/jira/browse/TIVI-1710

> > > >   * From the weston terminal, you don't have
> > enough
> > > privilege to
> > > > complete the install.  If you try to sudo,
> > you get
> > > asked for
> > > > the app password.

I've added the fact you need to be root to install new packages to that wiki 
section.
https://wiki.tizen.org/wiki/IVI/IVI_August_29,_3.0-M2-Aug#New_HomeScreen_not_installed_by_default

Geoffroy
Intel Corporation NV/SA
Kings Square, Veldkant 31
2550 Kontich
RPM (Bruxelles) 0415.497.718. 
Citibank, Brussels, account 570/1031255/09

This e-mail and any attachments may contain confidential material for the sole 
use of the intended recipient(s). Any review or distribution by others is 
strictly prohibited. If you are not the intended recipient, please contact the 
sender and delete all copies.

___
IVI mailing list
IVI@lists.tizen.org
https://lists.tizen.org/listinfo/ivi

Re: Errors installing Tizen 3.0 M2 Aug HomeScreen

[Ylinen, Mikko]

On Thu, Sep 5, 2013 at 7:57 AM, Ylinen, Mikko  wrote:
> Paul,
>
> On Thu, Sep 5, 2013 at 12:40 AM, Hanchett, Paul
>  wrote:
>> Rusty--
>>
>> When Tizen reboots, all I get is an empty black screen.  I can switch to
>> other terminals but the wayland screen seems dead.
>>
>> Are you saying that with the "dead" screen, if I go to one of the alternate
>> consoles and "launch_app org.tizen.ico.homescreen" that I should see
>> something happening in the blank display?
>
> Correct. The workaround I shared last Friday on this list helps:

Forgot to mention the bug:
https://bugs.tizen.org/jira/browse/TIVI-1724

-- Mikko
___
IVI mailing list
IVI@lists.tizen.org
https://lists.tizen.org/listinfo/ivi