Re: [MeeGo-dev] How to build meego corss compile environment for arm
Hi, I use Ubuntu to build the arm linux kernel and rootfs. Now I need to build my own application. I am just wandering about how to use the cross-compiler and the meego libraries. Meego SDK for Intel is just fine, and I can build my own app, but as for meego for arm, I don’t know the way. Best Regards Wang Qiang From: carsten.m...@gmail.com [mailto:carsten.m...@gmail.com] On Behalf Of Carsten Munk Sent: Wednesday, April 06, 2011 3:50 PM To: Wang Qiang Cc: meego-dev@meego.com Subject: Re: [MeeGo-dev] How to build meego corss compile environment for arm 2011/4/6 Wang Qiang Hello, I tried to google this problem, but hard to find answer. I will create the application on beagleboard for meego. Hope someone can help me. Thank you very much. MeeGo SDK comes with a proper environment for developing MeeGo apps for both Intel architecture and ARM architecture. /Carsten Best Regards Wang Qiang エラー! ファイル名が指定されていません。 ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] How to build meego corss compile environment for arm
2011/4/6 Wang Qiang > Hello, > >I tried to google this problem, but hard to find answer. > >I will create the application on beagleboard for meego. > >Hope someone can help me. > > > >Thank you very much. > MeeGo SDK comes with a proper environment for developing MeeGo apps for both Intel architecture and ARM architecture. /Carsten > > > Best Regards > > Wang Qiang > > ___ > MeeGo-dev mailing list > MeeGo-dev@meego.com > http://lists.meego.com/listinfo/meego-dev > http://wiki.meego.com/Mailing_list_guidelines > ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] How to build meego corss compile environment for arm
Hello, I tried to google this problem, but hard to find answer. I will create the application on beagleboard for meego. Hope someone can help me. Thank you very much. Best Regards Wang Qiang ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Qt with OpenGL (ES)
I don't think Dave is trying to build an image. He said he is trying to rebuild a QT bases demo app that works on MeeGo 1.0.1 IVI on a MeeGo 1.2 IVI image Regards Joel On Apr 5, 2011, at 5:27 PM, "Tracy Graydon" wrote: > The IVI Russellville image also uses the EMGD driver, by the way. > > If you are trying to generate your own image from a kickstart, you may need > explicitly remove the libGL package. The libGL package is still referenced > in the package-group patterns in the current 1.2 repos. Since the libGL > package is non-existent, your image creation will fail on it and throw an > error message about not being able to find the package. You can add "- > libGL" to your kickstart in the packages section and that should get you > past the error. > > I was able to use the kickstart from > http://repo.meego.com/MeeGo/builds/trunk/1.1.99.0.20110330.3/images/meego-iv > i-ia32-conx/meego-ivi-ia32-conx-1.1.99.0.20110330.3.ks, add the "- libGL" > line, and include qt-mobility and successfully spin an image with it. > > Tracy > > p.s. Top-post brought to you by Outlook. Sorry. :| > > > > -Original Message- > From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On > Behalf Of Matt Roper > Sent: Tuesday, April 05, 2011 9:45 AM > To: O'carroll, David T > Cc: meego-dev@meego.com > Subject: Re: [MeeGo-dev] Qt with OpenGL (ES) > > On Tue, Apr 05, 2011 at 06:36:35AM -0600, fathi.bou...@nokia.com wrote: >> >> A package should provides libGLESv2. If the platform (IVI conx) >> doesn't provide OpenGL ES driver, you're using software rendering. >> > > For the IVI conx images, EGL and GLES should be provided by the EMGD > driver in the package emgd-bin: > >[meego@localhost ~]$ rpm -ql emgd-bin | grep GL >/usr/lib/libEGL.so >/usr/lib/libEGL.so.1 >/usr/lib/libEGL.so.1.1.15.3226 >/usr/lib/libEMGDOGL.so >/usr/lib/libEMGDOGL.so.1.1.15.3226 >/usr/lib/libGLES_CM.so >/usr/lib/libGLES_CM.so.1.1.15.3226 >/usr/lib/libGLESv2.so >/usr/lib/libGLESv2.so.1.1.15.3226 >/usr/lib/libGLESv2.so.2 >/usr/lib/libemgdPVR2D_DRIWSEGL.so >/usr/lib/libemgdPVR2D_DRIWSEGL.so.1.1.15.3226 > > EMGD's implementation of GLES is not based on the Mesa framework, so you > won't see the Mesa EGL and GLES packages installed when EMGD is present. > > I'm a little bit confused by this part of David's original email: > >> The demo uses qt-mobility which has a dependency on libGL. However, >> libGL is not located in the repo. > ... >> That is fine except that the version of Qt that is in the >> repository is not built to use OpenGL ES, > > As others have noted, I don't think this should be true for the QT > present in the Meego 1.2-based images. When I run > >ldd /usr/lib/libQt* | grep libGL | grep -v libGLES > > to see if any of the /usr/lib/libQt* libraries have a libGL (not > libGLES) dependency, I don't get any results. Can you identify which QT > library on your system you're finding to have the libGL dependency? > > Thanks. > > > Matt > > > -- > Matt Roper > Intel Corporation > Embedded Media & Graphics Driver Group > ___ > MeeGo-dev mailing list > MeeGo-dev@meego.com > http://lists.meego.com/listinfo/meego-dev > http://wiki.meego.com/Mailing_list_guidelines > > ___ > MeeGo-dev mailing list > MeeGo-dev@meego.com > http://lists.meego.com/listinfo/meego-dev > http://wiki.meego.com/Mailing_list_guidelines ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] [Meego-qa] Bugzilla changes for tablet user experience open sourcing
Okay. This component was added. Regards Shuang -Original Message- From: Lynch, Rusty Sent: Tuesday, April 05, 2011 9:19 AM To: meego...@lists.meego.com Cc: Wan, Shuang; meego-dev@meego.com Subject: Re: [MeeGo-dev] [Meego-qa] Bugzilla changes for tablet user experience open sourcing We still need a component for meego-app-browser. --rusty ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] [Meego-qa] Bugzilla changes for tablet user experience open sourcing
Hi Shane, MeeGo Bugzilla was upgraded into 3.6.2 during PRC holiday (3.3~3.5). I have no more details on this since I didn't involve this transition. Eric may share with you more details on this. >From my investigation, most of issues are existing customizations for 3.4 >Bugzilla not integrated into bugzilla 3.6 and patches for known issues on 3.6 >upgrading not integrated. Anyway, we are trying to fix these issues ASAP and >document the changes on MeeGo wiki page. Thanks Shuang -Original Message- From: Shane Bryan [mailto:shane.br...@linux.intel.com] Sent: Tuesday, April 05, 2011 2:46 AM To: Wan, Shuang Cc: meego-dev@meego.com; meego...@lists.meego.com Subject: Re: [Meego-qa] Bugzilla changes for tablet user experience open sourcing On Fri, 1 Apr 2011 10:06:51 +0800 "Wan, Shuang" wrote: > 2. Old "Platform" is renamed to Profile. This is to make the > field name more meaningful to reflect the value list Handset, Tablet > etc belong to; I thought I saw this on Friday... seems to be gone again? > 3. New field "Platform" is created to record hardware platform > information in bug report. Seems there are some missing key values still needed. None of the Handset platforms exist. Moreover, there seems to be a mixing of "platform" and "product" names in the list, which will be confusing for many, since, for example, multiple products can be built from/on the *same* platform. See BMC# 15148 that I opened for this: https://bugs.meego.com/show_bug.cgi?id=15148 > Welcome your feedbacks and suggestions! Other things I noticed this morning that are new and as yet unannounced or explained on any ML I've found yet... On any BMC detail view: - Risk Level: * What is the purpose and definitions of "Red", "Yellow" and "Green". * Under what conditions do they apply and what factors into determining if the current Risk Level is "Yellow" vs. "Red". * Who has rights to change it? * When is it set and reviewed? * Who owns keeping up to date? - UX Status: * Pretty much the same questions as above - Architecture: * Seems to have disappeared, or it is now combined with "Platform" (or is that what is supposed to read "Profile"?)? - Some explanation of the newly added work effort metrics is probably needed, esp for those new to them. * When do these need to be used, and when is it optional? On the search form (https://bugs.meego.com/query.cgi) - Missing "Profile" - Missing "Platform" - Missing "Architecture" (Seems to be "OS", but that's not accurate really) - Missing "Risk Level" - Missing "UX Status" - "Hardware" needs to be renamed "Profile" (I'm guessing)? - "OS" needs to be renamed "Architecture" (I'm guessing)? New bug entry form does not reflect any of the above changes or new/redefined fields yet either. (https://bugs.meego.com/enter_bug.cgi) I general, the changes being seen right now seem to either be incompletely rolled out, or not completely thought out. Even worse, it seems there has been no discussion of these changes *before* they happened, providing the rational, justification, use cases, and impact to developers and QA in their day to day activities. Regards, Shane... ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] FW: [MeeGo-SDK] About Meego Handset for armv7l
Can you tell me which repos are you using? The following is mine: http://repo.meego.com/MeeGo/builds/1.1/1.1.3.2.20110401.1/core/repos/armv7l/ packages/ By the way, the rootfs is make by this file: http://bug10738.openaos.org/images/beagleboard/handset-armv7l-beagle.ks -Original Message- From: Till Harbaum / Lists [mailto:li...@harbaum.org] Sent: Tuesday, April 05, 2011 11:40 PM To: fathi.bou...@nokia.com Cc: meego-dev@meego.com; k...@isb.co.jp Subject: Re: FW: [MeeGo-SDK] About Meego Handset for armv7l hI, Am Dienstag 05 April 2011 schrieb fathi.bou...@nokia.com: > > So can anybody successes to run these application on the arm architecture Yes, i do. Till ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] how to run meego-ux's meego-app-camera on MeeGo 1.2 Netbook?
re: hint to do $ mv /usr/lib/gstreamer-0.10/libgstcamerabin.so /usr/lib/gstreamer-0.10/libgstcamerabin.so.bak WORKSFORME!! Thanks! ... meegolem-120-.../Pictures/Camera> td -rw-r--r-- 1 npm npm 230556 2011-04-05 17:39 Tue-Apr-5-17:39:58-2011.jpg -rw-r--r-- 1 npm npm 234552 2011-04-05 17:39 Tue-Apr-5-17:39:54-2011.jpg -rw-r--r-- 1 npm npm 231908 2011-04-05 17:39 Tue-Apr-5-17:39:53-2011.jpg -rw-r--r-- 1 npm npm 221608 2011-04-05 17:39 Tue-Apr-5-17:39:44-2011.jpg ... ## NB: recorded video is pretty lurchy/jerky but at least it's ## recognizable ## as video. Does the lurching happen each ## time the app checks for free space (see log below) which ## might be a bad idea on a uniprocessor/ht like this n455 meegolem-134-.../Videos/Camera> ffmpeg -i Tue-Apr-5-17:40:04-2011.ogg FFmpeg version SVN-r24044, Copyright (c) 2000-2010 the FFmpeg developers built on Jul 21 2010 15:07:15 with gcc 4.5.0 20100716 (Red Hat 4.5.0-3) [...] libavutil 50.20. 0 / 50.20. 0 libavcodec52.79. 1 / 52.79. 1 libavformat 52.73. 0 / 52.73. 0 libavdevice 52. 2. 0 / 52. 2. 0 libavfilter1.20. 1 / 1.20. 1 libswscale 0.11. 0 / 0.11. 0 libpostproc 51. 2. 0 / 51. 2. 0 [theora @ 0x96d4d00] 7 bits left in packet 82 Input #0, ogg, from 'Tue-Apr-5-17:40:04-2011.ogg': Duration: 00:00:35.60, start: 0.00, bitrate: 418 kb/s Stream #0.0: Video: theora, yuv420p, 1280x1024, 5 tbr, 5 tbn, 5 tbc Stream #0.1: Audio: vorbis, 44100 Hz, mono, s16, 120 kb/s ... meegolem-103-~> meego-qml-launcher --opengl --fullscreen --app meego-app-camera Adding Master Pointer: Virtual core pointer ( 2 ) Skipping non-Touch device: Virtual core XTEST pointer ( 4 ) Adding ATTACHED touch device: Cando Corporation Cando 10.1 Multi Touch Panel with Controller ( 11 ) Skipping non-Touch device: SynPS/2 Synaptics TouchPad ( 14 ) loaded the Generic plugin Loaded the MeeGo sensor plugin Request for interface not granted... Request for interface not granted... Warning: Object::connect: No such signal QXIMInputContext::inputMethodAreaChanged(QRect) Warning: Object::connect: No such signal LauncherApp::localeSettingsChanged() Warning: Object::connect: (sender name: 'meego-qml-launcher') Warning: Object::connect: No such signal LauncherApp::windowListUpdated(QList) Warning: Object::connect: (sender name: 'meego-qml-launcher') Debug: Instantiating VolumeControlPrivate Debug: Settings* Debug: Flash Mode: 2 Debug: Capture Mode: 1 Debug: "/dev/video0" "Lenovo EasyCamera" Debug: "/dev/video0" "Lenovo EasyCamera" Debug: Setting camera to "/dev/video0" Debug: Supported maximum optical zoom 1 Debug: Supported maximum digital zoom 1 Debug: Metadata is not available Debug: Audio input: "alsa:null" - "Discard all samples (playback) or generate zero samples (capture)" Debug: Audio input: "alsa:pulse" - "PulseAudio Sound Server" Debug: Audio input: "alsa:default" - "Default" Debug: Audio input: "alsa:front:CARD=Intel,DEV=0" - "HDA Intel, CONEXANT Analog Front speakers" Debug: Audio input: "alsa:surround40:CARD=Intel,DEV=0" - "HDA Intel, CONEXANT Analog 4.0 Surround output to Front and Rear speakers" Debug: Audio input: "alsa:surround41:CARD=Intel,DEV=0" - "HDA Intel, CONEXANT Analog 4.1 Surround output to Front, Rear and Subwoofer speakers" Debug: Audio input: "alsa:surround50:CARD=Intel,DEV=0" - "HDA Intel, CONEXANT Analog 5.0 Surround output to Front, Center and Rear speakers" Debug: Audio input: "alsa:surround51:CARD=Intel,DEV=0" - "HDA Intel, CONEXANT Analog 5.1 Surround output to Front, Center, Rear and Subwoofer speakers" Debug: Audio input: "alsa:surround71:CARD=Intel,DEV=0" - "HDA Intel, CONEXANT Analog 7.1 Surround output to Front, Center, Side, Rear and Woofer speakers" Debug: Audio input: "pulseaudio:" - "PulseAudio device." Debug: Default source: "alsa:null" Debug: Using default resolution Debug: Frame rate: 5 Debug: Frame rate: 10 Debug: Frame rate: 15 Debug: Using default FPS Debug: Video resolution: 160 x 120 Debug: Video resolution: 320 x 240 Debug: Video resolution: 640 x 400 Debug: Video resolution: 640 x 480 Debug: Video resolution: 1280 x 720 Debug: Video resolution: 1280 x 800 Debug: Video resolution: 1280 x 1024 Debug: Codec: "video/h264" Debug: Codec: "video/xvid" Debug: Codec: "video/mpeg4" Debug: Codec: "video/mpeg1" Debug: Codec: "video/mpeg2" Debug: Codec: "video/theora" Debug: Container: "qtmux" Debug: Container: "matroska" Debug: Container: "ogg" Debug: Container: "mp4" Debug: Container: "wav" Debug: Container: "quicktime" Debug: Container: "avi" Debug: Container: "3gpp" Debug: Container: "flv" Debug: Container: "amr" Debug: Container: "asf" Debug: Container: "dv" Debug: Container: "mpeg" Debug: Container: "vob" Debug: Container: "mpegts" Debug: Container: "3g2" Debug: Container: "3gp" Debug: Container: "raw" Debug: Selected container: "ogg" Debug: Sorted resolution: 1280 x 1024 Debug: So
Re: [MeeGo-dev] Qt with OpenGL (ES)
The IVI Russellville image also uses the EMGD driver, by the way. If you are trying to generate your own image from a kickstart, you may need explicitly remove the libGL package. The libGL package is still referenced in the package-group patterns in the current 1.2 repos. Since the libGL package is non-existent, your image creation will fail on it and throw an error message about not being able to find the package. You can add "- libGL" to your kickstart in the packages section and that should get you past the error. I was able to use the kickstart from http://repo.meego.com/MeeGo/builds/trunk/1.1.99.0.20110330.3/images/meego-iv i-ia32-conx/meego-ivi-ia32-conx-1.1.99.0.20110330.3.ks, add the "- libGL" line, and include qt-mobility and successfully spin an image with it. Tracy p.s. Top-post brought to you by Outlook. Sorry. :| -Original Message- From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On Behalf Of Matt Roper Sent: Tuesday, April 05, 2011 9:45 AM To: O'carroll, David T Cc: meego-dev@meego.com Subject: Re: [MeeGo-dev] Qt with OpenGL (ES) On Tue, Apr 05, 2011 at 06:36:35AM -0600, fathi.bou...@nokia.com wrote: > > A package should provides libGLESv2. If the platform (IVI conx) > doesn't provide OpenGL ES driver, you're using software rendering. > For the IVI conx images, EGL and GLES should be provided by the EMGD driver in the package emgd-bin: [meego@localhost ~]$ rpm -ql emgd-bin | grep GL /usr/lib/libEGL.so /usr/lib/libEGL.so.1 /usr/lib/libEGL.so.1.1.15.3226 /usr/lib/libEMGDOGL.so /usr/lib/libEMGDOGL.so.1.1.15.3226 /usr/lib/libGLES_CM.so /usr/lib/libGLES_CM.so.1.1.15.3226 /usr/lib/libGLESv2.so /usr/lib/libGLESv2.so.1.1.15.3226 /usr/lib/libGLESv2.so.2 /usr/lib/libemgdPVR2D_DRIWSEGL.so /usr/lib/libemgdPVR2D_DRIWSEGL.so.1.1.15.3226 EMGD's implementation of GLES is not based on the Mesa framework, so you won't see the Mesa EGL and GLES packages installed when EMGD is present. I'm a little bit confused by this part of David's original email: > The demo uses qt-mobility which has a dependency on libGL. However, > libGL is not located in the repo. ... > That is fine except that the version of Qt that is in the > repository is not built to use OpenGL ES, As others have noted, I don't think this should be true for the QT present in the Meego 1.2-based images. When I run ldd /usr/lib/libQt* | grep libGL | grep -v libGLES to see if any of the /usr/lib/libQt* libraries have a libGL (not libGLES) dependency, I don't get any results. Can you identify which QT library on your system you're finding to have the libGL dependency? Thanks. Matt -- Matt Roper Intel Corporation Embedded Media & Graphics Driver Group ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] how to run meego-ux's meego-app-camera on MeeGo 1.2 Netbook?
On 04/05/2011 01:31 PM, Niels Mayer wrote: I got a little farther with bringing up meego-ux camera on Netbook 1.2 "alpha". After seeing various warnings regarding missing gstreamer components and failures in meego-app-music and meego-app-video related to dbus message parse failures, I decided to upgrade this highly updated 2/22/11 image to the latest "base" packages from Trunk: Just realized we are still using a work around in the image creation process. There is a bug for Qt Mobility bug for this, but I don't recall the number so cc'ing Iain for the answer. But... the gst camera bin doesn't play nicely with the Qt Mobility Video widget. In the ks file we: rm /usr/lib/gstreamer-0.10/libgstcamerabin.so ... which means on each update the file comes back (which is how i remembered since i just did a massive Trunk:Testing update and the camera app stopped working.) --rusty ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] how to run meego-ux's meego-app-camera on MeeGo 1.2 Netbook?
On Sun, Apr 3, 2011 at 4:33 PM, Arjan van de Ven wrote: > h wonder why you don't run the tablet/etc UX entirely The tablet-UX probably makes good sense on a compatible tablet, with larger surface, better edge-of-screen & button ergonomics, more memory, higher resolution, faster processors, etc. e.g., something like http://www.amazon.com/dp/B004HKIIFI/ (ASUS EEE Slate 12.1" tablet PC). A platform like that would be good incentive to use the tablet UX. (Now accepting all donations :-) ). A better reason is the latest 1.2 Netbook UX worksforme, whereas the Tablet-UX still has some issues that need to be worked out, e.g., http://lists.meego.com/pipermail/meego-dev/2011-April/482477.html where Costas Stylianou wrote: .. You are correct, the problem is once you boot to the MeeGo Tablet UX image you lose touch clicks, I believe that the touch driver has been tuned for the ExoPC only which probably has a different touch controller to your device. If you switch to the netbook build touch works very well. [...] ... My goal with the camera app is a codebase with portability to all MeeGo platforms (doesn't IVI need a touch-based QML camera app too?). Given the reprioritization of the handset, I still hope to work on some variant of http://code.google.com/p/ytd-meego/wiki/CitizenJournalismWithYoutubeDirectForMeego but want it to run on all platforms that its Qt-based infrastructure would target, not just the handset. Plus, it's a lot easier to develop on the netbook, snarfling up whatever tools and devel libs using http://wiki.meego.com/MeeGo-Lem , with the promise that eventually I'll be able to run the same code on multiple MeeGo targets. and more than just ia32 processors. I'm seeking to evaluate meego-app-camera versus http://code.google.com/p/ytd-meego/wiki/CitizenJournalismWithYoutubeDirectForMeego#Reusing_QtMobility_1.2%27s_%22declarative_camera%22_Exa ... the first step of which is getting meego-app-camera running on a generic MeeGo platform such as the Lenovo s10-3t. The second would be getting it running on the n900 when all the codecs and camera functionality support video recording. If that includes taking all the pieces apart and putting them back together again to understand the dependencies, then so be it... -- Niels http://nielsmayer.com ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Another architecture direction mail
Hi, >-Original Message- >From: jeremias bosch [snip] >> If so, then perhaps you want to check out >> https://meego.gitorious.org/meegotouch/meegotouch-feedback >> https://meego.gitorious.org/meegotouch/meegotouch-feedbackreactionmaps >> >> The main feature is its very low latency, and we actively use it in >the >> virtual keyboard parts of the MeeGo Input Methods. It's also actively >> developed. >> >Hello >Just for curiosity, is that in anyway releated to qt mobility haptic? >I.e. a backend lib or such? Or is qt mobility haptic a complete own >implementation? [snip] There is a backend plugin (meegotouch) in Qt Mobility which uses MFeedback::play() to provide instantaneous feedback (called theme effects in the Qt Mobility API), but there are a couple of issues with that backend plugin: 1) The MFeedback::play function in the library appeared to support only three effects (press, release, cancel) and our implementation only used Press. 2) Calling MFeedback::play sometimes crashed if we didn't explicitly initialise an MComponentData instance in our wrapper implementation prior to calling ::play(). We hacked around this issue by simply initialising one if required, prior to calling ::play(), but I'm fairly certain that's the wrong solution. For custom effects (and periodic effects, as well as file effects) we did not develop a backend based on meegotouch-feedback. The main backend plugin in Qt Mobility for tactile feedback is the "immersion" plugin, but obviously that won't be available on all devices. In short, I believe the "meegotouch" backend could (from my understanding) be improved to support the full variety of effects supported in the Qt Mobility Feedback API (with the possible exception of file effects?). Depending on the recent development of the MFeedback libraries, the instantaneous effect playback supported by the "meegotouch" Qt Mobility Feedback backend could also be improved substantially. If any member of the community would like to spend some time and effort to do so, please send me an email and I'll point you to the relevant documentation and some example plugins (it's all in the mobility gitorious repo anyway) to get you started. Cheers, Chris. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Another architecture direction mail
Am 05.04.2011 21:01, schrieb Michael Hasselmann: On Tue, 2011-04-05 at 14:39 -0400, Anderson Lizardo wrote: Non-Graphics-Feedback (NGF), Profiles, and Qt style APIs (QmSystem) Where's the source repository of NGF, btw? The specs of libngf and ngfd do not have URL: and meego.gitorious.org does not seem to include them either. I suppose it is: http://meego.gitorious.org/maemo-multimedia/ngfd What are the features of NGF? The README is apparently empty. Is it perhaps about playing haptic and tactile feedback, e.g., on touchscreen interaction (guessing from the Architecture wiki page that NGF is some form of general purpose notification system as well, so am not sure). If so, then perhaps you want to check out https://meego.gitorious.org/meegotouch/meegotouch-feedback https://meego.gitorious.org/meegotouch/meegotouch-feedbackreactionmaps The main feature is its very low latency, and we actively use it in the virtual keyboard parts of the MeeGo Input Methods. It's also actively developed. Hello Just for curiosity, is that in anyway releated to qt mobility haptic? I.e. a backend lib or such? Or is qt mobility haptic a complete own implementation? BR, Jeremias regards, Michael ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] how to run meego-ux's meego-app-camera on MeeGo 1.2 Netbook?
I got a little farther with bringing up meego-ux camera on Netbook 1.2
"alpha". After seeing various warnings regarding missing gstreamer
components and failures in meego-app-music and meego-app-video related
to dbus message parse failures, I decided to upgrade this highly
updated 2/22/11 image to the latest "base" packages from Trunk:
$ zypper ar http://download.meego.com/live/devel:/base/Trunk/devel:base.repo
$ zypper clean --all ; zypper --gpg-auto-import-keys refresh
## removed dangerous-to-upgrade packages via hand-edited from list
output by "zypper up"
$ zypper update -acl alsa-lib alsa-lib-devel alsa-plugins-pulseaudio
alsa-utils aspell atk atk-devel augeas-libs autoconf automake avahi
avahi-glib avahi-gobject avahi-ui basesystem bash binutils btrfs-progs
bzip2 bzip2-libs cairo cairo-devel chkconfig cmake connman
connman-test ConsoleKit ConsoleKit-libs ConsoleKit-x11 coreutils cpio
cpp cups cups-libs curl cvs db4 db4-utils deltarpm desktop-file-utils
device-mapper device-mapper-libs diffutils docbook-dtds
docbook-style-dsssl docbook-style-xsl docbook-utils dosfstools ed
elfutils-libelf expat fastinit file file-libs findutils flac
flac-devel fontconfig fontconfig-devel fontpackages-filesystem
foomatic freetype freetype-devel fuse fuse-libs gamin gawk gcc gcc-c++
gdb gdb-gdbserver gdbm geoclue geoclue-devel gettext-devel
gettext-libs ghostscript-fonts giflib glib2 glib2-devel gmp
gnome-doc-utils gnome-doc-utils-stylesheets gnome-mime-data gnupg2
grep groff grubby gzip hicolor-icon-theme hwdata icu info iproute
iptables iputils jasper jasper-libs kbd keyutils keyutils-libs lcms
lcms-libs less libacl libarchive libasyncns libattr libblkid libcap
libcroco libcurl libdaemon libdrm libexif libexif-devel libffi
libfontenc libgcc libgcrypt libglade2 libgnome-keyring
libgnome-keyring-devel libgomp libgpg-error libgudev1 libical
libical-devel libICE libICE-devel libicu libidn libjpeg libjpeg-devel
libksba liblua libmng libnl libnotify libpciaccess libpng libpng-devel
libpthread-stubs libsamplerate libsamplerate-devel libSM libSM-devel
libsndfile libsoup libsoup-devel libstdc++ libstdc++-devel libtasn1
libtasn1-devel libtheora libtheora-devel libtiff libtool libtool-ltdl
libudev libusb libuser libuser-python libutempter libuuid
libuuid-devel libva libvisual libxml2-python libxslt libzypp
linux-firmware logrotate m4 mailcap make MAKEDEV meego-app-music
meego-app-video meego-ux-components meego-ux-components-devel
mesa-dri-i915-driver mesa-dri-i965-driver mesa-dri-swrast-driver
mesa-libEGL mesa-libEGL-devel mesa-libGL mesa-libGL-devel
mesa-libGLESv2 mesa-libGLESv2-devel mesa-libGLU mesa-libGLU-devel
mesa-libOpenVG mesa-libOpenVG-devel mesa-libOSMesa
mesa-libOSMesa-devel mingetty minizip mkinitrd mtools ncurses
ncurses-base ncurses-libs net-tools nspr nss nss-mdns
nss-softokn-freebl nss-sysinit openjade opensp openssh openssh-clients
openssh-server pam pango pango-devel parted passwd patch pciutils
pixman pixman-devel pkgconfig pm-utils polkit popt prelink procps
psmisc pth pycairo pycairo-devel pygobject2 pygobject2-codegen
pygobject2-devel pygobject2-doc pyparted rarian rarian-compat rhpl
rootfiles rpm-python satsolver-tools sed sgml-common shadow-utils
shared-mime-info speex speex-devel sqlite sqlite-devel sreadahead
ssmtp startup-notification strace sudo swig sysklogd tar time tzdata
udev unzip upower urw-fonts usbutils usleep util-linux-ng uxlaunch
vim-minimal wget wireless-tools wpa_supplicant xcb-util xdg-utils
xkeyboard-config xml-common xorg-x11-drv-intel xorg-x11-server
xorg-x11-server-common xorg-x11-server-Xorg
xorg-x11-server-Xorg-setuid xterm xz xz-libs xz-lzma-compat yasm zip
zlib zlib-devel zypper linux-firmware sysvinit sysvinit-tools
## in case you want a working GUI after reboot.
$ zypper remove mce qmsystem
## ("your mileage may vary")
$ reboot
~300 package updates later ... now various things work better than
they did before, and nothing seems to work worse, although sreadahead
complains of 15 errors instead of 1 or 2 (?). More importantly, now
the wired network stays stable for up to 12 hours at a time --
amazing! And connman isn't constantly connecting and disconnecting on
the wireless.
Do I need to upgrade to the latest kernel in order to get the camera
to actually capture a photo or video? Does installing
http://download.meego.com/live/devel:/kernel/Trunk/i586/kernel-2.6.37.2-256.2.i586.rpm
via zypper actually do all the right stuff w/r/t updating the boot
information for the new kernel? I also skipped
updating syslinux-extlinux (& syslinux dependency) as it messes with
/boot ...If I want to avoid a reinstall, what's the right way to
upgrade a "live" meego system to the latest "trunk" kernel?
...
Unlike my previous attempt, now the camera application launches its
GUI; but, the video preview/viewfinder is "blank", and it cannot
capture any photos or videos.
The main problem now is:
"g_object_set_valist: object class `GstMcSrc' has no property named `device'"
Note I have the follow
Re: [MeeGo-dev] [PATCH] [PATCH] Fixed BMC#8485 - People crashes when...
+1 I've tested this patch with and without hfdialer installed. Looks good - thanks for tracking this down! I applied this patch; I also updated the meego-handset-people package in OBS and updated bug 8485. Thanks! -Kaitlin On 04/05/2011 04:13 AM, Jukka Selesniemi wrote: There was an uninitialised boolean variable which was set to true by default by compiler. Invalid default value generated an unwanted call of callNumberToActiveService() method just after the Dialer application had been registered to D-Bus. This caused a crash in the People application. Signed-off-by: Jukka Selesniemi --- src/peopleapp.cpp |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/src/peopleapp.cpp b/src/peopleapp.cpp index db05fbc..d6df030 100644 --- a/src/peopleapp.cpp +++ b/src/peopleapp.cpp @@ -67,6 +67,7 @@ PeopleApplication::PeopleApplication(int&argc, char**argv): m_currentPerson = NULL; m_editModel = NULL; m_editModelModified = NULL; +m_callPending = false; //m_AccountPath = NULL; ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Another architecture direction mail
On Tue, 2011-04-05 at 14:39 -0400, Anderson Lizardo wrote: > Hi, > > 2011/4/5 Antti Kaijanmäki : > > On Fri, 2011-04-01 at 09:07 -0700, Arjan van de Ven wrote: > >> Late last year, in the Architecture meeting, we had agreed to include > >> timed, MCE, Sharing Framework, > >> Non-Graphics-Feedback (NGF), Profiles, and Qt style APIs (QmSystem) > > > > Where's the source repository of NGF, btw? > > The specs of libngf and ngfd do not have URL: and meego.gitorious.org > > does not seem to include them either. > > I suppose it is: http://meego.gitorious.org/maemo-multimedia/ngfd Thanks! I actually tried the search box, but it didn't find these :) http://meego.gitorious.org/maemo-multimedia/ngfd http://meego.gitorious.org/maemo-multimedia/libngf -- Antti ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Another architecture direction mail
On Tue, 2011-04-05 at 14:39 -0400, Anderson Lizardo wrote: > >> Non-Graphics-Feedback (NGF), Profiles, and Qt style APIs (QmSystem) > > > > Where's the source repository of NGF, btw? > > The specs of libngf and ngfd do not have URL: and meego.gitorious.org > > does not seem to include them either. > > I suppose it is: http://meego.gitorious.org/maemo-multimedia/ngfd What are the features of NGF? The README is apparently empty. Is it perhaps about playing haptic and tactile feedback, e.g., on touchscreen interaction (guessing from the Architecture wiki page that NGF is some form of general purpose notification system as well, so am not sure). If so, then perhaps you want to check out https://meego.gitorious.org/meegotouch/meegotouch-feedback https://meego.gitorious.org/meegotouch/meegotouch-feedbackreactionmaps The main feature is its very low latency, and we actively use it in the virtual keyboard parts of the MeeGo Input Methods. It's also actively developed. regards, Michael ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Another architecture direction mail
Hi, 2011/4/5 Antti Kaijanmäki : > On Fri, 2011-04-01 at 09:07 -0700, Arjan van de Ven wrote: >> Late last year, in the Architecture meeting, we had agreed to include >> timed, MCE, Sharing Framework, >> Non-Graphics-Feedback (NGF), Profiles, and Qt style APIs (QmSystem) > > Where's the source repository of NGF, btw? > The specs of libngf and ngfd do not have URL: and meego.gitorious.org > does not seem to include them either. I suppose it is: http://meego.gitorious.org/maemo-multimedia/ngfd Regards, -- Anderson Lizardo Instituto Nokia de Tecnologia - INdT Manaus - Brazil ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] meego tablet on viewpad 10
On Wed, 6 Apr 2011, 陈鲍孜 wrote: Here is the device info: Bus 005 Device 002: ID 20b3:0a18 Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize032 idVendor 0x20b3 idProduct 0x0a18 bcdDevice 38.93 iManufacturer 1 Hanvon iProduct2 10.1 iSerial 0 See BMC # 10887 https://bugs.meego.com/show_bug.cgi?id=10887 kernel driver has been submitted to meego-kernel ML, but so far has not been commented on. -gabriel___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] MeeGo Community device program update
Greetings all, It's been a while since I updated everyone on this list with what's going on around the MeeGo Community device program [1], so here you go: - several of us have been shaping up a database model and application framework for an online device request system. �I'm still not clear on who will be implementing this, but I believe the proposal that Ferenc and I have put together is a good one. �More on this as details solidify. - I am still trying to get more providers in. �I heard from the AAVA rep again today but no actual progress yet-- he hopes to free time up this week to talk with me. �I also reached out to GENIVI to see about including the dev device they expect to have out in September for automotive use. �Cross your fingers, IVI fans! �In addition, I have added a new table to the wiki for tracking proposals/requests for provider participation [2]. �Feel free to help out there! �Also propose devices [3]. - I was just down in Austin for the Texas Linux fest this last Saturday [4] and got to talk with Jayabharath Goluguri from TI about Pandaboards there. �TI is eager to get some into the hands of MeeGo members with big ideas! �So pending the introduction of our online solution, email myself, Dawn Foster and Brian Warner (included on this email) with your proposals, based on the form requirements [5]. �We'll pass the approved requests on to TI! Special thanks to Nathan Willis and Till Harbaum for agreeing to be device champions (IVI and Beagleboard, respectively). �We are looking for more volunteers, and there are many ways to help! �See the forum thread [6] for more details. * Note: the meego-dev list was added as an FYI only. �All general replies need to go to meego-community. Thanks all! Randall (Randy) Arnold Forum Nokia Champion blog: http://tabulacrypticum.wordpress.com cell: +18177396806 irc: Texrat @ irc.freenode.net twitter: http://twitter.com/texrat linkedin: http://www.linkedin.com/in/tabletman� [1]�http://wiki.meego.com/Community_Office/Community_device_program [2]�http://wiki.meego.com/Community_Office/Community_device_program/Contact_Table [3]�http://wiki.meego.com/Community_Office/Community_device_program#Device_Possibilities [4]�http://tabulacrypticum.wordpress.com/2011/04/04/texas-linux-fest-2011/ [5]�http://wiki.meego.com/Community_Office/Community_device_program#Form_Requirements [6]�http://forum.meego.com/showthread.php?t=2901 -- Ovi Mail: Making email access easy http://mail.ovi.com ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] meego tablet on viewpad 10
Here is the device info: Bus 005 Device 002: ID 20b3:0a18 Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize032 idVendor 0x20b3 idProduct 0x0a18 bcdDevice 38.93 iManufacturer 1 Hanvon iProduct2 10.1 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 0 No Subclass bInterfaceProtocol 0 None iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.11 bCountryCode0 Not supported bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 177 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0020 1x 32 bytes bInterval 5 Device Status: 0x0001 Self Powered > -Original Message- > From: meego-dev-boun...@meego.com > [mailto:meego-dev-boun...@meego.com] On Behalf Of Gabriel M. > Beddingfield > Sent: Tuesday, April 05, 2011 11:54 PM > To: Foster, Dawn M > Cc: meego-dev@meego.com > Subject: Re: [MeeGo-dev] meego tablet on viewpad 10 > > > > On Tue, 5 Apr 2011, Foster, Dawn M wrote: > > > So, to support my touch screen, does the work relate to device driver > > or userspace library outside kernel. I’d like to help if possible. > > > > You need a fix for the device driver... specifically the driver needs > > to support XInput2 > > > > > > So, the best way to contribute a fix for this is to submit a patch for the > > driver? > > What is the touch device? (Typically found by `sudo lsusb > -v`) Sometimes it works to simply add a file in /etc/xorg.conf.d > > -gabriel ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Qt with OpenGL (ES)
On Tue, Apr 05, 2011 at 06:36:35AM -0600, fathi.bou...@nokia.com wrote: > > A package should provides libGLESv2. If the platform (IVI conx) > doesn't provide OpenGL ES driver, you're using software rendering. > For the IVI conx images, EGL and GLES should be provided by the EMGD driver in the package emgd-bin: [meego@localhost ~]$ rpm -ql emgd-bin | grep GL /usr/lib/libEGL.so /usr/lib/libEGL.so.1 /usr/lib/libEGL.so.1.1.15.3226 /usr/lib/libEMGDOGL.so /usr/lib/libEMGDOGL.so.1.1.15.3226 /usr/lib/libGLES_CM.so /usr/lib/libGLES_CM.so.1.1.15.3226 /usr/lib/libGLESv2.so /usr/lib/libGLESv2.so.1.1.15.3226 /usr/lib/libGLESv2.so.2 /usr/lib/libemgdPVR2D_DRIWSEGL.so /usr/lib/libemgdPVR2D_DRIWSEGL.so.1.1.15.3226 EMGD's implementation of GLES is not based on the Mesa framework, so you won't see the Mesa EGL and GLES packages installed when EMGD is present. I'm a little bit confused by this part of David's original email: > The demo uses qt-mobility which has a dependency on libGL. However, > libGL is not located in the repo. ... > That is fine except that the version of Qt that is in the > repository is not built to use OpenGL ES, As others have noted, I don't think this should be true for the QT present in the Meego 1.2-based images. When I run ldd /usr/lib/libQt* | grep libGL | grep -v libGLES to see if any of the /usr/lib/libQt* libraries have a libGL (not libGLES) dependency, I don't get any results. Can you identify which QT library on your system you're finding to have the libGL dependency? Thanks. Matt -- Matt Roper Intel Corporation Embedded Media & Graphics Driver Group ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] Dialer Project meeting minutes for Tuesday 4/5
== #meego-meeting: Dialer Project meeting == Meeting started by sabotage at 15:00:05 UTC. Online minutes: http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-05-15.00.html Full IRC meeting log: http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-05-15.00.log.html Meeting summary --- * Meeting info at http://wiki.meego.com/Project/Dialer/Meetings (sabotage, 15:00:46) * sabotage is author maintainer of meego-handset-dialer (sabotage, 15:01:58) * crevetor is Antoine Reversat, helping hand, wants to work on the QML version of the dialer (sabotage, 15:02:06) * introductions (sabotage, 15:02:38) * More about who's who in the project is at http://wiki.meego.com/Project/Dialer/Meetings#Preface (sabotage, 15:04:17) * aruravi part of N900 hardware adaptation and DE Voice/SMS team (sabotage, 15:04:26) * jukkaeklund, N900 DE product manager and very interested in the topic :) (sabotage, 15:05:17) * essi is the Team lead for VoiceSMS project on the N900 Developer Edition (sabotage, 15:06:43) * zolkis: I am architect for RTCom in Harmattan, including a dialer too, so naturally interested on the MeeGo dialer (sabotage, 15:07:33) * kallam has provided a bunck of Resource Policy Manager additions to Dialer (sabotage, 15:08:40) * kallam: Kalle Lampila member of N900 hardware adatation team (sabotage, 15:08:56) * Two Meetings (Dialer and VoiceSMS) (sabotage, 15:09:17) * GCF == Global Certification Forum (sabotage, 15:18:53) * LINK: http://www.globalcertificationforum.org/WebSite/public/home_public.aspx (sabotage, 15:18:56) * ACTION: sabotage to discuss project goals and meeting combination with essi (sabotage, 15:19:26) * AGREED: (sabotage, 15:19:34) * Wire frames (sabotage, 15:21:12) * Dialer wireframes to be released any day now (sabotage, 15:30:50) * ACTION: sabotage to find out more detail and make it available ASAP (sabotage, 15:31:12) * bugs and features (sabotage, 15:32:20) * LINK: https://bugs.meego.com/buglist.cgi?query_format=advanced&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=MeeGo_N900DE_Release_Blocker%2B&component=Dialer&product=Handset%20User%20Experience&classification=MeeGo%20Platform (sabotage, 15:34:05) * Dialer history is not changing right now until the tracker vs. EDS issues have settled out (sabotage, 15:42:46) * Bug owner volunteers (sabotage, 15:46:19) * LINK: Open dialer bugs https://bugs.meego.com/buglist.cgi?cmdtype=runnamed&namedcmd=Open%20Dialer%20Bugs (sabotage, 15:48:09) * LINK: Open dialer bugs http://wiki.meego.com/Project/Dialer#Bugs (sabotage, 15:49:38) * LINK: Open dialer bugs alternate link (sabotage, 15:50:28) * LINK: https://bugs.meego.com/buglist.cgi?query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&columnlist=bug_severity%2Cpriority%2Cassigned_to%2Ccomponent%2Cbug_status%2Cresolution%2Cshort_desc&component=Dialer&classification=MeeGo%20Platform&known_name=Open%20Dialer%20Bugs&query_based_on=Open%20Diale (sabotage, 15:50:30) * LINK:(sabotage, 15:50:42) * LINK: https://bugs.meego.com/buglist.cgi?query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&columnlist=bug_severity%2Cpriority%2Cassigned_to%2Ccomponent%2Cbug_status%2Cresolution%2Cshort_desc&component=Dialer&classification=MeeGo%20Platform&known_name=Open%20Dialer%20Bugs&query_based_on=Open%20Diale (sabotage, 15:50:44) * ACTION: anyone who wants to own a bug, please set the assigned to to yourself (sabotage, 15:53:14) * Headless Dialer (sabotage, 15:53:54) * assuming highlander and aruravi agree that it's working, and I can test it successfully, I want to move headless branch to master ASAP (sabotage, 15:56:35) * QML dialer (sabotage, 15:57:09) * ACTION: alterego please provide URL to your QML dialer source (sabotage, 16:00:16) * LINK: http://gitorious.org/qml-meego-dialer (alterego, 16:00:31) * sabotage set up a Wiki page to start tracking this http://wiki.meego.com/Project/Dialer/QMLMigration (sabotage, 16:00:51) * LINK: http://wiki.meego.com/Project/Dialer/QMLMigration (sabotage, 16:00:54) Meeting ended at 16:01:12 UTC. Action Items * sabotage to discuss project goals and meeting combination with essi * sabotage to find out more details [wireframe release] and make it available ASAP * anyone who wants to own a bug, please set the assigned to to yourself * alterego please provide URL to your QML dialer source Action Items, by person --- * alterego * alterego please provide URL to your QML dialer source * sabotage * sabotage t
Re: [MeeGo-dev] meego tablet on viewpad 10
On Tue, 5 Apr 2011, Foster, Dawn M wrote: So, to support my touch screen, does the work relate to device driver or userspace library outside kernel. I’d like to help if possible. You need a fix for the device driver... specifically the driver needs to support XInput2 So, the best way to contribute a fix for this is to submit a patch for the driver? What is the touch device? (Typically found by `sudo lsusb -v`) Sometimes it works to simply add a file in /etc/xorg.conf.d -gabriel ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] meego tablet on viewpad 10
On Apr 5, 2011, at 7:36 AM, "Rusty Lynch" mailto:rusty.ly...@intel.com>> wrote: On 04/05/2011 01:40 AM, 陈鲍孜 wrote: Aha, the mouse can work even though there is no cursor. So, to support my touch screen, does the work relate to device driver or userspace library outside kernel. I’d like to help if possible. You need a fix for the device driver... specifically the driver needs to support XInput2 So, the best way to contribute a fix for this is to submit a patch for the driver? Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] somebody knows how to unsubscribe this list
On Tue, 2011-04-05 at 22:01 +0800, manbu hust wrote: > i try and try, but it didn't work See the link at the bottom of every message: > http://lists.meego.com/listinfo/meego-dev If I didn't work: Elaborate. andre -- Andre Klapper (maemo.org bugmaster) http://www.openismus.com ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] meego tablet on viewpad 10
On 04/05/2011 01:40 AM, 陈鲍孜 wrote: > > Aha, the mouse can work even though there is no cursor. > > So, to support my touch screen, does the work relate to device driver > or userspace library outside kernel. I’d like to help if possible. > > You need a fix for the device driver... specifically the driver needs to support XInput2 ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] FW: [MeeGo-SDK] About Meego Handset for armv7l
hI, Am Dienstag 05 April 2011 schrieb fathi.bou...@nokia.com: > > So can anybody successes to run these application on the arm architecture Yes, i do. Till ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] somebody knows how to unsubscribe this list
i try and try, but it didn't work ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] Dialer Project meeting - Agenda for Tuesday 4/5
Agenda for the Dialer Project meeting - Tuesday, April 5th, 2011 * General information/business (Shane) - Introductions (arun, alterego, crevetor, essi, others...) - Two meetings (Dialer and DE VoiceSMS)? What are they for, and should they be merged? - Wire frames * Bug, patch and merge-request status (??) Features: - 2809 [FEA] Dialer application mute incoming call ringtone - 8148 [FEA] Emergency Calls without dedicated number - 6092 [FEA] Provive Alternate Line Service Support - 9270 [FEA] [L10N] Dialer shall be translated into the POR languages as listed in Core Master #5068. - 2805 [FEA] Dialer application support for Unstructured Supplementary Services Data (USSD) Bugs: - Too many to list and we're not going to triage - We'll review what folks want to review - Would like volunteers willing to own some * New features discussion - Headless branch work/status/next steps - HFP branch work/status/next steps - QML UI status and next steps * Any Other Business ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Qt with OpenGL (ES)
> Is this image built to use OpenGL? This image contains a Qt GL ES enabled: $ rpm -qp --requires libqtopengl4-4.7.2-2.3.i586.rpm /sbin/ldconfig /sbin/ldconfig libEGL.so.1 libGLESv2.so.2 libQtCore.so.4 libQtGui.so.4 libQtMeeGoGraphicsSystemHelper.so.4 libQtOpenGL.so.4 libX11.so.6 libc.so.6 libc.so.6(GLIBC_2.0) libc.so.6(GLIBC_2.1.3) libc.so.6(GLIBC_2.4) libgcc_s.so.1 libgcc_s.so.1(GCC_3.0) libgcc_s.so.1(GLIBC_2.0) libm.so.6 libm.so.6(GLIBC_2.0) libm.so.6(GLIBC_2.1) libstdc++.so.6 libstdc++.so.6(CXXABI_1.3) libstdc++.so.6(GLIBCXX_3.4) rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 A package should provides libGLESv2. If the platform (IVI conx) doesn't provide OpenGL ES driver, you're using software rendering. From: ext Stylianou, Costas [costas.stylia...@intel.com] Sent: Tuesday, April 05, 2011 3:21 PM To: O'carroll, David T; Boudra Fathi (Nokia-SD/Helsinki); meego-dev@meego.com Subject: RE: Qt with OpenGL (ES) > > It means you aren't using Qt from trunk/1.2 (OpenGL ES) but Qt from > 1.1 (OpenGL). > > I got the image from > http://repo.meego.com/MeeGo/builds/trunk/latest/images/meego-ivi-ia32- > conx/ > The image in there at the time was meego-ivi-ia32-conx- > 1.1.90.8.20110322.2.ks > > Is this image built to use OpenGL? It looks like the IVI build does not contain the OpenGL ES drivers (mesa-libGLESv2.i586 7.9.1-6.2) that are included in latest MeeGo v1.2 pre-releases and used by the Handset UX. Regards Costas - Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47 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. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Qt with OpenGL (ES)
> > It means you aren't using Qt from trunk/1.2 (OpenGL ES) but Qt from > 1.1 (OpenGL). > > I got the image from > http://repo.meego.com/MeeGo/builds/trunk/latest/images/meego-ivi-ia32- > conx/ > The image in there at the time was meego-ivi-ia32-conx- > 1.1.90.8.20110322.2.ks > > Is this image built to use OpenGL? It looks like the IVI build does not contain the OpenGL ES drivers (mesa-libGLESv2.i586 7.9.1-6.2) that are included in latest MeeGo v1.2 pre-releases and used by the Handset UX. Regards Costas - Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47 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. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] meego tablet on viewpad 10
Hi, I’m wondering if I can help to make MeeGo support ViewPad 10, for I may get its hardware manual from its manufacturer. The Question is where I could start the adaption work and how I summit to the community. Thanks. Baozi From: Stylianou, Costas [mailto:costas.stylia...@intel.com] Sent: Tuesday, April 05, 2011 5:00 PM To: 陈鲍孜 Cc: meego-dev@meego.com Subject: RE: [MeeGo-dev] meego tablet on viewpad 10 Hi, You are correct, the problem is once you boot to the MeeGo Tablet UX image you lose touch clicks, I believe that the touch driver has been tuned for the ExoPC only which probably has a different touch controller to your device. If you switch to the netbook build touch works very well. I need to work out how to bring back the mouse cursor but for now if you have you tablet in landscape and move the mouse to the right then left click mouse and move to the left you will be able to unlock the screen. Once you get to the panel you can use the touch screen to point to where you want to go and left click on the mouse to invoke. Regards Costas From: 陈鲍孜 [mailto:chenba...@gmail.com] Sent: Tuesday, April 05, 2011 9:33 AM To: Stylianou, Costas Cc: meego-dev@meego.com Subject: RE: [MeeGo-dev] meego tablet on viewpad 10 Thanks for your reply. It seems that is has the basic support. Because during the installation I use the touch screen as the mouse very well. And when it turns to black screen saver during power on, the click on the screen can wake the screen up. The only problem is that I cannot unlock the screen. If I have to use mouse for now, where is the cursor? It seems that I cannot find it on the locked screen. L Cheers. Baozi From: Stylianou, Costas [mailto:costas.stylia...@intel.com] Sent: Tuesday, April 05, 2011 4:09 PM To: 陈鲍孜; meego-dev@meego.com Subject: RE: [MeeGo-dev] meego tablet on viewpad 10 That’s because touch click on that device is not supported on the Tablet UX build, use a mouse for now. From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On Behalf Of ??? Sent: Tuesday, April 05, 2011 8:55 AM To: meego-dev@meego.com Subject: [MeeGo-dev] meego tablet on viewpad 10 Hello, I’ve installed MeeGo Tablet version on my new ViewPad 10. It seems everything is going well except I can’t find ways to unlock the screen. Does anyone know the problem? I guess there maybe two possible reason. The first one which I think would be the most possible is due to lack of unlock key mapping. If so where can I modify the mapping? Second, it is also possible that there is still work to do with the device support. But it seems when I install the image, it recognize the touchscreen to be used as a mouse. I’m also willing to make contribute to support ViewPad 10 if MeeGo hasn’t supported just now. Is there anyone who can tell me where to start? I mean how and where to checkout codes and submit patches? Baozi - Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47 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. - Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47 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. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Qt with OpenGL (ES)
> It means you aren't using Qt from trunk/1.2 (OpenGL ES) but Qt from 1.1 > (OpenGL). I got the image from http://repo.meego.com/MeeGo/builds/trunk/latest/images/meego-ivi-ia32-conx/ The image in there at the time was meego-ivi-ia32-conx-1.1.90.8.20110322.2.ks Is this image built to use OpenGL? -Original Message- From: fathi.bou...@nokia.com [mailto:fathi.bou...@nokia.com] Sent: Tuesday, April 05, 2011 12:04 PM To: O'carroll, David T; meego-dev@meego.com Subject: RE: Qt with OpenGL (ES) Hi, > I am developing a demo IVI system for Intel and came across the following > while > attempting to port the demo to Meego 1.2. The demo uses qt-mobility which has > a dependency on libGL. However, libGL is not located in the repo. In MeeGo 1.2, Qt/Qt Mobility doesn't depends on libGL but on libGLESv2. > When I initially enquired about this I was told that MeeGo is moving away from > OpenGL in favor of OpenGL ES. That is fine except that the version of Qt that > is in the repository is not built to use OpenGL ES, so in order to use it > I would have to rebuild Qt and specify OpenGL ES as the dependency. It means you aren't using Qt from trunk/1.2 (OpenGL ES) but Qt from 1.1 (OpenGL). > To me this doesn't make much sense as every Qt developer that wishes to use a > module with a dependency on OpenGL (such as qt-mobility) will need to rebuild > Qt instead of using the files in the repo. I think the Qt files in the repo > should be changed to use OpenGL ES natively to avoid this (especially if this > is the direction MeeGo is headed). That's the current situation in 1.2: we depends on GL ES and you don't need to rebuild anything. Your setup seems incorrect. Cheers, Fathi -- Intel Shannon Limited Registered in Ireland Registered Office: Collinstown Industrial Park, Leixlip, County Kildare Registered Number: 308263 Business address: Dromore House, East Park, Shannon, Co. Clare 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. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] [PATCH] [PATCH] Fixed BMC#8485 - People crashes when...
There was an uninitialised boolean variable which was set to true by default by compiler. Invalid default value generated an unwanted call of callNumberToActiveService() method just after the Dialer application had been registered to D-Bus. This caused a crash in the People application. Signed-off-by: Jukka Selesniemi --- src/peopleapp.cpp |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/src/peopleapp.cpp b/src/peopleapp.cpp index db05fbc..d6df030 100644 --- a/src/peopleapp.cpp +++ b/src/peopleapp.cpp @@ -67,6 +67,7 @@ PeopleApplication::PeopleApplication(int &argc, char**argv): m_currentPerson = NULL; m_editModel = NULL; m_editModelModified = NULL; +m_callPending = false; //m_AccountPath = NULL; -- 1.7.0.4 ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] [PATCH] Fixed BMC#8485 - People crashes when launching dialer
Hello, This is a fix for BMC#8485 (https://bugs.meego.com/show_bug.cgi?id=8485). Please review. BR, Jukka Selesniemi ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Qt with OpenGL (ES)
Hi, > I am developing a demo IVI system for Intel and came across the following > while > attempting to port the demo to Meego 1.2. The demo uses qt-mobility which has > a dependency on libGL. However, libGL is not located in the repo. In MeeGo 1.2, Qt/Qt Mobility doesn't depends on libGL but on libGLESv2. > When I initially enquired about this I was told that MeeGo is moving away from > OpenGL in favor of OpenGL ES. That is fine except that the version of Qt that > is in the repository is not built to use OpenGL ES, so in order to use it > I would have to rebuild Qt and specify OpenGL ES as the dependency. It means you aren't using Qt from trunk/1.2 (OpenGL ES) but Qt from 1.1 (OpenGL). > To me this doesn’t make much sense as every Qt developer that wishes to use a > module with a dependency on OpenGL (such as qt-mobility) will need to rebuild > Qt instead of using the files in the repo. I think the Qt files in the repo > should be changed to use OpenGL ES natively to avoid this (especially if this > is the direction MeeGo is headed). That's the current situation in 1.2: we depends on GL ES and you don't need to rebuild anything. Your setup seems incorrect. Cheers, Fathi ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] Qt with OpenGL (ES)
Hi all, I am developing a demo IVI system for Intel and came across the following while attempting to port the demo to Meego 1.2. The demo uses qt-mobility which has a dependency on libGL. However, libGL is not located in the repo. When I initially enquired about this I was told that MeeGo is moving away from OpenGL in favor of OpenGL ES. That is fine except that the version of Qt that is in the repository is not built to use OpenGL ES, so in order to use it I would have to rebuild Qt and specify OpenGL ES as the dependency. To me this doesn't make much sense as every Qt developer that wishes to use a module with a dependency on OpenGL (such as qt-mobility) will need to rebuild Qt instead of using the files in the repo. I think the Qt files in the repo should be changed to use OpenGL ES natively to avoid this (especially if this is the direction MeeGo is headed). Has anyone encountered a problem like this? Should I submit a bug report on it? Regards, Dave -- Intel Shannon Limited Registered in Ireland Registered Office: Collinstown Industrial Park, Leixlip, County Kildare Registered Number: 308263 Business address: Dromore House, East Park, Shannon, Co. Clare 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. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] [MeeGo-SDK] About Meego Handset for armv7l
Hi, On Tue, Apr 5, 2011 at 8:32 AM, Wang Qiang wrote: > Hello All, > > > > I am making meego handset for armv7l work on BeagleTouch board. > > > > I have finished porting the kernel and building the rootfs. > > > > I just followed the instruction in > http://wiki.meego.com/ARM/Meego_on_Beagleboard_from_scratch. > > > > But I found that some application can not work properly. > > > > Such as music, video and photo. > > > > So can anybody successes to run these application on the arm architecture? > Can you describe which specifica applications are not working? Or if you get error messages, can you put them in your email? Regards, Jeremiah ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] meego tablet on viewpad 10
Hi, You are correct, the problem is once you boot to the MeeGo Tablet UX image you lose touch clicks, I believe that the touch driver has been tuned for the ExoPC only which probably has a different touch controller to your device. If you switch to the netbook build touch works very well. I need to work out how to bring back the mouse cursor but for now if you have you tablet in landscape and move the mouse to the right then left click mouse and move to the left you will be able to unlock the screen. Once you get to the panel you can use the touch screen to point to where you want to go and left click on the mouse to invoke. Regards Costas From: 陈鲍孜 [mailto:chenba...@gmail.com] Sent: Tuesday, April 05, 2011 9:33 AM To: Stylianou, Costas Cc: meego-dev@meego.com Subject: RE: [MeeGo-dev] meego tablet on viewpad 10 Thanks for your reply. It seems that is has the basic support. Because during the installation I use the touch screen as the mouse very well. And when it turns to black screen saver during power on, the click on the screen can wake the screen up. The only problem is that I cannot unlock the screen. If I have to use mouse for now, where is the cursor? It seems that I cannot find it on the locked screen. :( Cheers. Baozi From: Stylianou, Costas [mailto:costas.stylia...@intel.com] Sent: Tuesday, April 05, 2011 4:09 PM To: 陈鲍孜; meego-dev@meego.com Subject: RE: [MeeGo-dev] meego tablet on viewpad 10 That’s because touch click on that device is not supported on the Tablet UX build, use a mouse for now. From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On Behalf Of ??? Sent: Tuesday, April 05, 2011 8:55 AM To: meego-dev@meego.com Subject: [MeeGo-dev] meego tablet on viewpad 10 Hello, I’ve installed MeeGo Tablet version on my new ViewPad 10. It seems everything is going well except I can’t find ways to unlock the screen. Does anyone know the problem? I guess there maybe two possible reason. The first one which I think would be the most possible is due to lack of unlock key mapping. If so where can I modify the mapping? Second, it is also possible that there is still work to do with the device support. But it seems when I install the image, it recognize the touchscreen to be used as a mouse. I’m also willing to make contribute to support ViewPad 10 if MeeGo hasn’t supported just now. Is there anyone who can tell me where to start? I mean how and where to checkout codes and submit patches? Baozi - Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47 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. - Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47 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. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] meego tablet on viewpad 10
Aha, the mouse can work even though there is no cursor. So, to support my touch screen, does the work relate to device driver or userspace library outside kernel. I’d like to help if possible. Thanks Baozi From: Stylianou, Costas [mailto:costas.stylia...@intel.com] Sent: Tuesday, April 05, 2011 4:09 PM To: 陈鲍孜; meego-dev@meego.com Subject: RE: [MeeGo-dev] meego tablet on viewpad 10 That’s because touch click on that device is not supported on the Tablet UX build, use a mouse for now. From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On Behalf Of ??? Sent: Tuesday, April 05, 2011 8:55 AM To: meego-dev@meego.com Subject: [MeeGo-dev] meego tablet on viewpad 10 Hello, I’ve installed MeeGo Tablet version on my new ViewPad 10. It seems everything is going well except I can’t find ways to unlock the screen. Does anyone know the problem? I guess there maybe two possible reason. The first one which I think would be the most possible is due to lack of unlock key mapping. If so where can I modify the mapping? Second, it is also possible that there is still work to do with the device support. But it seems when I install the image, it recognize the touchscreen to be used as a mouse. I’m also willing to make contribute to support ViewPad 10 if MeeGo hasn’t supported just now. Is there anyone who can tell me where to start? I mean how and where to checkout codes and submit patches? Baozi - Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47 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. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] meego tablet on viewpad 10
Thanks for your reply. It seems that is has the basic support. Because during the installation I use the touch screen as the mouse very well. And when it turns to black screen saver during power on, the click on the screen can wake the screen up. The only problem is that I cannot unlock the screen. If I have to use mouse for now, where is the cursor? It seems that I cannot find it on the locked screen. L Cheers. Baozi From: Stylianou, Costas [mailto:costas.stylia...@intel.com] Sent: Tuesday, April 05, 2011 4:09 PM To: 陈鲍孜; meego-dev@meego.com Subject: RE: [MeeGo-dev] meego tablet on viewpad 10 That’s because touch click on that device is not supported on the Tablet UX build, use a mouse for now. From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On Behalf Of ??? Sent: Tuesday, April 05, 2011 8:55 AM To: meego-dev@meego.com Subject: [MeeGo-dev] meego tablet on viewpad 10 Hello, I’ve installed MeeGo Tablet version on my new ViewPad 10. It seems everything is going well except I can’t find ways to unlock the screen. Does anyone know the problem? I guess there maybe two possible reason. The first one which I think would be the most possible is due to lack of unlock key mapping. If so where can I modify the mapping? Second, it is also possible that there is still work to do with the device support. But it seems when I install the image, it recognize the touchscreen to be used as a mouse. I’m also willing to make contribute to support ViewPad 10 if MeeGo hasn’t supported just now. Is there anyone who can tell me where to start? I mean how and where to checkout codes and submit patches? Baozi - Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47 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. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] FW: meego tablet on viewpad 10
It seems that device support has no problem, because I could wake the screen up (from black screen saver) by touching. Baozi From: 陈鲍孜 [mailto:chenba...@gmail.com] Sent: Tuesday, April 05, 2011 3:55 PM To: 'meego-dev@meego.com' Subject: meego tablet on viewpad 10 Hello, I’ve installed MeeGo Tablet version on my new ViewPad 10. It seems everything is going well except I can’t find ways to unlock the screen. Does anyone know the problem? I guess there maybe two possible reason. The first one which I think would be the most possible is due to lack of unlock key mapping. If so where can I modify the mapping? Second, it is also possible that there is still work to do with the device support. But it seems when I install the image, it recognize the touchscreen to be used as a mouse. I’m also willing to make contribute to support ViewPad 10 if MeeGo hasn’t supported just now. Is there anyone who can tell me where to start? I mean how and where to checkout codes and submit patches? Baozi ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] meego tablet on viewpad 10
That’s because touch click on that device is not supported on the Tablet UX build, use a mouse for now. From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On Behalf Of ??? Sent: Tuesday, April 05, 2011 8:55 AM To: meego-dev@meego.com Subject: [MeeGo-dev] meego tablet on viewpad 10 Hello, I’ve installed MeeGo Tablet version on my new ViewPad 10. It seems everything is going well except I can’t find ways to unlock the screen. Does anyone know the problem? I guess there maybe two possible reason. The first one which I think would be the most possible is due to lack of unlock key mapping. If so where can I modify the mapping? Second, it is also possible that there is still work to do with the device support. But it seems when I install the image, it recognize the touchscreen to be used as a mouse. I’m also willing to make contribute to support ViewPad 10 if MeeGo hasn’t supported just now. Is there anyone who can tell me where to start? I mean how and where to checkout codes and submit patches? Baozi - Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47 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. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] [Meego-architecture] Another architecture direction mail
On Fri, 2011-04-01 at 09:07 -0700, Arjan van de Ven wrote: > Late last year, in the Architecture meeting, we had agreed to include > timed, MCE, Sharing Framework, > Non-Graphics-Feedback (NGF), Profiles, and Qt style APIs (QmSystem) > identified on the > http://wiki.meego.com/Architecture as new technologies into MeeGo. We > had hoped that all the > documentation and source code would end up well integrated into the 1.2 > release of MeeGo. By "Profiles" you mean the device category profiles defined in compliance specification? -- Antti Kaijanmäki Software Architect Team Manager m. +358 41 440 4187 linkedin.com/in/anttikaijanmaki www.nomovok.com Nomovok Ltd. Keilasatama 3 FI-02150 Espoo Finland ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] meego tablet on viewpad 10
Hello, I’ve installed MeeGo Tablet version on my new ViewPad 10. It seems everything is going well except I can’t find ways to unlock the screen. Does anyone know the problem? I guess there maybe two possible reason. The first one which I think would be the most possible is due to lack of unlock key mapping. If so where can I modify the mapping? Second, it is also possible that there is still work to do with the device support. But it seems when I install the image, it recognize the touchscreen to be used as a mouse. I’m also willing to make contribute to support ViewPad 10 if MeeGo hasn’t supported just now. Is there anyone who can tell me where to start? I mean how and where to checkout codes and submit patches? Baozi ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Another architecture direction mail
On Fri, 2011-04-01 at 09:07 -0700, Arjan van de Ven wrote: > Late last year, in the Architecture meeting, we had agreed to include > timed, MCE, Sharing Framework, > Non-Graphics-Feedback (NGF), Profiles, and Qt style APIs (QmSystem) Where's the source repository of NGF, btw? The specs of libngf and ngfd do not have URL: and meego.gitorious.org does not seem to include them either. -- Antti Kaijanmäki Software Architect Team Manager m. +358 41 440 4187 linkedin.com/in/anttikaijanmaki www.nomovok.com Nomovok Ltd. Keilasatama 3 FI-02150 Espoo Finland ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
