[MeeGo-dev] State of multi-touch in MeeGo 1.1.80?

[Eugene Seah]

Hi,

Does anyone know the current state of multi-touch on MeeGo 1.1.80 builds?
I noticed in this slide 15 of this presentation - 
(http://conference2010.meego.com/sites/all/files/sessions/meego-conference-2010-multi-point-touch.odp), 
the stack is presumably different for MeeGo 1.2 than MeeGo 1.1's scheme 
of Qt reinterpreting multiple single-touch input devices as a 
multi-touch event. Stack looks like (from slides)


Qt (needs to support multi-touch valuators from mtev/ Xinput 2.0)
   |
multipointtouchplugin
   |
xf86-input-mtev
   |
kernel driver support (multi-touch-protocol)
   |
touch hardware

My specific question is whether all these pieces are in place today, and 
if any adaptation/porting steps are required to make this work. I'm 
assuming this stack should support MT_ touch events from the kernel 
touch driver.


Thanks!
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

[MeeGo-dev] MIC-image-creator failure on Ubuntu, latest weekly N900 KS

[Eugene Seah]

Hi,

We're getting a new failure on Ubuntu mic-image-creator 0.22.2 with the 
latest N900 KS, that did not occur before... errors look like this:



  Installing: filesystem   # [  2/551]
error: unpacking of archive failed on file /boot: cpio: chown
...
  Installing: meegotouch-feedback  # [154/551]
/var/tmp/rpm-tmp.rp53VK: line 4: ln: command not found
warning: %post(meegotouch-feedback-0.10.4-2.29.armv7l) scriptlet failed, 
exit status 127


then stalling at

   Installing: libasyncns   # 
[222/551]


Has anyone else seen these symptoms and does anyone know how to work 
around these? Thanks.

___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

[MeeGo-dev] Fwd: [MeeGo-touch-dev] Target specification in meegotouch reference UX gconf

[Eugene Seah]

Since this goes into some gconf setting in meego... trying meego-dev as 
well, does anyone know how the target "device profile" gets specified 
post 1.1?


Thanks.

===

Hi all,

On MeeGo 1.1, we used to modify the gconf setting of
"/meegotouch/theme/target" to point the UX to use different device
settings... e.g. device profile for N900, aava, etc.

Since updating to a recent MeeGo 1.1.80 build, it seems this gconf
setting is no longer valid, and the UX seems to be using device settings
from
/usr/share/meegotouch/targets/Default.conf.

Does anyone know what the reference UX is using for selecting target
device settings now on 1.1.80?

Thanks.
___
MeeGo-touch-dev mailing list
meego-touch-...@meego.com
http://lists.meego.com/listinfo/meego-touch-dev

___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] Has the new kernel process been established?

[Eugene Seah]

On 10/28/10 15:05, Carsten Munk wrote:

http://wiki.meego.com/MeeGo_kernel_documentation_for_contributors
seems up to date, as well as subscribe to meego-kernel mailing list,
it's very active.

General contribution guidelines at
http://meego.com/about/contribution-guidelines

BR
Carsten Munk

   

Thanks!

2010/10/28 Eugene Seah:
   

Bumping this question, would be interested in whether the new kernel process
has been finalized/documented.

From: http://wiki.meego.com/Kernel_Process_Obsolete

"UPDATE: 2010-05-27 - Per discussion on the meego-dev mailing list, Arjan
van de Ven has indicated that he's the Intel employee responsible for the
kernel, and that procedures Intel said would be put into place are being
finalized/documented right now."

On 08/03/10 20:19, Liu, Haibo wrote:

Hi MeeGoers,

According to MeeGo Wiki, a new kernel process is being finalized now. Just
wonder if there is still any general process I should follow if I want to
make the newest kernel version work on my netbook? And where should I find
the news about this new kernel process, will it be posted on Wiki page?

P.S. I’ve checked out the newest version of kernel source and followed the
obsolete process to compile it and failed. The scripts failed to mkdir for
linux-2.6.33-{tags}.orig. I’m trying to make this work now. Hope anybody
tells me it’s unnecessary.

Best  Regards,

Liu Haibo  (Lewis)
Technical Marketing Engineer, ATPS/SMG
E-mail:  haibo@intel.com
Office:  8610-8507-1310
iNet:8751-1310
Cell:138-103-20201




___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev


___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev


 


___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] Has the new kernel process been established?

[Eugene Seah]

Bumping this question, would be interested in whether the new kernel 
process has been finalized/documented.


From: http://wiki.meego.com/Kernel_Process_Obsolete

"UPDATE: 2010-05-27 - /Per discussion on the meego-dev 
 
mailing list, Arjan van de Ven has indicated that he's the Intel 
employee responsible for the kernel, and that procedures Intel said 
would be put into place are being finalized/documented right now."


/On 08/03/10 20:19, Liu, Haibo wrote:

Hi MeeGoers,
According to MeeGo Wiki, a new kernel process is being finalized now. 
Just wonder if there is still any general process I should follow if I 
want to make the newest kernel version work on my netbook? And where 
should I find the news about this new kernel process, will it be 
posted on Wiki page?
P.S. I've checked out the newest version of kernel source and followed 
the obsolete process to compile it and failed. The scripts failed to 
mkdir for linux-2.6.33-{tags}.orig. I'm trying to make this work now. 
Hope anybody tells me it's unnecessary.

Best  Regards,
Liu Haibo  (Lewis)
Technical Marketing Engineer, ATPS/SMG
E-mail:  haibo@intel.com
Office:  8610-8507-1310
iNet:8751-1310
Cell:138-103-20201


___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
   


___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

[MeeGo-dev] fennec/network interface permissions as meego user?

[Eugene Seah]

Hi,

I'm unable to get fennec to connect to any internet site through the 
Handset UX launched by uxlaunch as the "meego" user.

Executing fennec from the command line as "root" user gets me connected.

Suspect that it's not just fennec, but all network applications, e.g. 
tried ping and got a  "socket: Permission denied", does anyone know what 
kind of setup/configuration is needed to allow "meego" user to use the 
network interfaces. Would this issue be related to some configuration in 
connman?


Thanks!
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

[MeeGo-dev] MeeGo UX libmeegotouch release schedule

[Eugene Seah]

Hi,

Is there some way to find out the release schedule of more recent 
versions of libmeegotouch (or any other package for that matter) on the 
meego.com repos? When will MeeGo pick up something beyond version 0.20.25?


On a related note, has anyone tried picking up a more recent 
libmeegotouch off gitorious, building and running on N900? Are there 
dependencies on other packages?


Thanks.


___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] MeeGo 1.1 Development Release 1.0.90.1.20100907.1 is available

[Eugene Seah]

Alexander Kanevskiy wrote:


Handset, N900:

 * Image not buildable currently due to the absence of the latest Qt
fixes in this release.

  


Is there any further information about these Qt fixes required for 
building the handset image?
I'm trying to rebuild libmeegotouch and running into build issues in 
/usr/include/qt4/QtCore/qdebug.h, does anyone know if these are related 
issues?


make[2]: Entering directory 
`/root/rpmbuild/BUILD/libmeegotouch-0.20.25/demos/widgetsgallery'
g++ -c -pipe -g -O2 -D_REENTRANT -Wall -W 
-DM_APPLICATION_NAME=\"widgetsgallery\" -DBUILD_M -DHAVE_ICU 
-DHAVE_CONTEXTSUBSCRIBER -DHAVE_GCONF -DHAVE_GSTREAMER -DHAVE_DBUS 
-DIS_ARMEL -DTHEMEDIR=\""/usr/share/themes"\" 
-DAPPLET_LIBS=\""/usr/lib/meegotouch/applets"\" 
-DAPPLET_INSTALLATION_SOURCES=\""/usr/lib/meegotouch/appletinstallationsources"\" 
-DAPPLET_DATA=\""/usr/share/meegotouch/applets"\" 
-DAPPLET_SETTINGS_DIR=\""/usr/share/meegotouch/applets/settings"\" 
-DAPPLICATION_EXTENSION_LIBS=\""/usr/lib/meegotouch/applicationextensions"\" 
-DAPPLICATION_EXTENSION_DATA_DIR=\""/usr/share/meegotouch/applicationextensions"\" 
-DTRANSLATION_DIR=\""/usr/share/l10n/meegotouch"\" 
-DM_ICUEXTRADATA_DIR=\""/usr/share/meegotouch/icu"\" 
-DM_THEME_PRELOAD_DIR=\""/var/lib/meegotouch/theme/preload.d"\" 
-DM_THEME_POST_PRELOAD_DIR=\""/var/lib/meegotouch/theme/preload.post"\" 
-DM_DBUS_SERVICES_DIR=\""/usr/share/dbus-1/services"\" 
-DM_XDG_DIR=\""/etc/xdg"\" -DM_INSTALL_SYSCONFDIR=\""/etc"\" 
-DM_SHADER_SOURCE_DIR=\""/usr/share/meegotouch/shaders"\" 
-DM_SHADER_BINARY_DIR=\""/var/cache/meegotouch/shaders"\" 
-DCACHEDIR=\""/var/cache/meegotouch/"\" 
-DCONTACTS_DIR="\"/usr/share/themes/devel/meegotouch/widgetsgallery/images/contacts/\"" 
-DIMAGES_DIR="\"/usr/share/themes/devel/meegotouch/widgetsgallery/images/\"" 
-DMEDIA_DIR="\"/usr/share/widgetsgallery/media\"" -DQT_NO_DEBUG 
-DQT_DBUS_LIB -DQT_SVG_LIB -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED 
-I/usr/share/qt4/mkspecs/linux-g++ -I. -I/usr/include/qt4/QtCore 
-I/usr/include/qt4/QtGui -I/usr/include/qt4/QtSvg 
-I/usr/include/qt4/QtDBus -I/usr/include/qt4 -I. -I../../src/include 
-I../../src/corelib -I.moc -o .obj/panningbenchmark.o panningbenchmark.cpp

In file included from /usr/include/qt4/QtCore/qdebug.h:50:0,
from panningbenchmark.cpp:10:
/usr/include/qt4/QtCore/qtextstream.h:60:2: error: #error qtextstream.h 
must be included before any header file that defines Status
/usr/include/qt4/QtCore/qtextstream.h:89:10: error: expected identifier 
before 'int'
/usr/include/qt4/QtCore/qtextstream.h:89:17: error: expected 
unqualified-id before '{' token

make[2]: *** [.obj/panningbenchmark.o] Error 1

Thanks.
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] Meego Multitouch support vs. New Ubuntu Multitouch API

[Eugene Seah]

Thiago Macieira wrote:

On Wednesday 18. August 2010 22.20.23 Sivan Greenberg wrote:
  

On Wed, Aug 18, 2010 at 7:18 PM, Thiago Macieira  wrote:


On Wednesday 18 August 2010 13:10:23 Cláudio Sampaio wrote:
  

Hi.

I've search through meego's site for "multitouch" and couldn't find
anything relating to its multitouch support.

How multitouch support in Meego relates to that new Multitouch stack to
be released by Canonical? http://lwn.net/Articles/400455/rss  Is it
done differently? Can Meego actually use Canonical's framework?


It's done completely differently. It uses the Qt multitouch and gesture
support only. It's built-in.
  
So MTF is wrappers around Qt's multi touch and gesture api? 



Yes.

  

What does built-in here means?



It's inside of Qt. It's not provided by an external library.

  
Follow-on questions: Does Qt's multitouch functionality already work 
currently on MeeGo? Even though Xorg evdev driver isn't yet capable of 
detecting multitouch-capable devices (at least from my understanding)?


If multitouch on Qt does already work, how do we tell Qt about our 
multitouch device, is there some non-default setting that needs to be 
configured?


Thanks.
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

[MeeGo-dev] Portrait mode on Handset UX for ARM?

[Eugene Seah]

Trying again: I see there's a bug on N900 for screen rotation, and the 
UX seems to assume landscape mode.


Is there a way to start the duihome executable to make it start in
portrait mode (for a 480x800 screen, instead of 800x480).

Thanks.

___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

[MeeGo-dev] Portrait mode on Meegotouch-duihome working for ARM?

[Eugene Seah]

Is there a way to start the duihome executable to make it start in 
portrait mode instead of the default landscape mode?


Thanks.
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] MeeGo Touch Framework memory benchmarks

[Eugene Seah]

Seconded as something that would be very useful.

Jackson, Thomas (Tom) wrote:

Hi,
 
Curious if there are any official MeeGo Touch Framework memory 
benchmark documents available for developers?  We have conducted some 
initial tests by installing packages and gathering the minimum and 
average memory footprint via /proc for many of the subsystems of the 
MeeGo Touch Framework, but would like to determine if there any 
performance metrics already. 
 
Thanks!
Tom Jackson  
 



___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
  


___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] State of ARM N900 kickstart-generated image?

[Eugene Seah]

Thanks Jose,

That helps a lot, examining the builds, it seems like the 1.0.80.11 
builds are the first to pick up gcc 4.5.0 where the problem lies.
Looks like gcc 4.5.1 (which should have the fix, according to 
http://bugs.meego.com/show_bug.cgi?id=3936 and 
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43698) is publicly available 
on the gcc website, so when it gets picked up for the build system, that 
should fix these issues?


Also, this type of image status information would be really nice to have 
on the ARM/N900 wiki...



José Luís wrote:

Hi Eugene,

Looks like that the issue related to gcc version change is not fixed 
yet (http://wiki.meego.com/Release_Engineering/Plans/1.1). Since then, 
I'm not able to generate a MeeGo image for N900 (armv7l) capable of 
boot correctly. Using then, the system boot is very slow and freezes 
in ssh key generation. The last successful image that boot and 
start-up the UI that I have created was generated with the 
repositories below:
repo --name=handset   
--baseurl=http://repo.meego.com/MeeGo/builds/trunk/1.0.80.9.20100706.1/core/repos/armv7l/packages/ 
--save
repo --name=MeeGo-Trunk   
--baseurl=http://repo.meego.com/MeeGo/builds/trunk/1.0.80.9.20100706.1/handset/repos/armv7l/packages/  
--save


The last repositories that I have tried and the N900 boot don't work 
was this http://repo.meego.com/MeeGo/builds/trunk/1.0.80.12.20100727.1/.


[]'s

2010/8/2 Eugene Seah mailto:es...@codeaurora.org>>

Hi,

I've tried to regenerate the latest N900 handset UX image via the
closed kickstart file and run that on the N900.

Of late the image does not get to the UX, it fails while running
the rc5.d scripts... the last thing I can see is the
nokia-usb-networking script being run before the phone just
suddenly resets.  Anyone know what's broken?

Thanks.
___
MeeGo-dev mailing list
MeeGo-dev@meego.com <mailto:MeeGo-dev@meego.com>
http://lists.meego.com/listinfo/meego-dev




--
José Luís do Nascimento
Signove - Enjoy Innovation
Home page: http://www.signove.com


___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
  


___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

[MeeGo-dev] State of ARM N900 kickstart-generated image?

[Eugene Seah]

Hi,

I've tried to regenerate the latest N900 handset UX image via the closed 
kickstart file and run that on the N900.


Of late the image does not get to the UX, it fails while running the 
rc5.d scripts... the last thing I can see is the nokia-usb-networking 
script being run before the phone just suddenly resets.  Anyone know 
what's broken?


Thanks.
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] mcompositor X11 requirements/limitations

[Eugene Seah]

Hey Robin,

Thanks for the reply, questions below:

Robin Burchell wrote:

Hi Eugene,

Excerpts from Eugene Seah's message of Tue Jul 13 23:33:25 +0100 2010:
  

Hi there,

I'm trying to get the UX working on another ARM device that does not 
have the same SGX graphics chip that the N900/Beagleboard have. What's 
limiting the UX/mcompositor from working with non-hw accelerated X11?



MCompositor requires a GLX/EGL backend to do rendering. I briefly (<5 mins)
looked into whether a software backend would be possible, as GLX/EGL
backends are thankfully fairly seperated from everything else, but I didn't
really reach a conclusion. It may be possible (if slow).

MCompositor works this way as it composites thumbnails of running applications
or something along these lines. I haven't worked out precisely what it does as I
haven't had the time to sit down and actually get it running. ;)

The rest of the UX is usable without GL, as libmeegotouch does not require it -
with newest libmeegotouch from master (I'm not sure if it's updated in MeeGo
yet), you have a patch by me which looks for the environment variable
M_USE_SOFTWARE_RENDERING to use software rendering, or alternatively, you can
run applications and pass -software as a parameter.

  
I guess I don't understand the UX framework well enough to get that. How 
do I use "the rest of the UX" without running mcompositor? My impression 
was that MCompositor was the window manager that and was critical for 
anything else running on the UX? Any diagrams/docs you could point me to 
would be helpful.


Thanks.

Thanks.



Hope this helps,

--
Robin Burchell
http://rburchell.com
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
  


___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

[MeeGo-dev] mcompositor X11 requirements/limitations

[Eugene Seah]

Hi there,

I'd like to get a better understanding of the Handset UX mcompositor 
requirements for X11, I saw this on one of the IRC chats ( 
http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-30-18.59.log.html): 



19:22:15  dnaumov: as far as i know the UX won't start on a 
nonaccelerated vm


I'm trying to get the UX working on another ARM device that does not 
have the same SGX graphics chip that the N900/Beagleboard have. What's 
limiting the UX/mcompositor from working with non-hw accelerated X11?


Thanks.
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev