[MeeGo-dev] conflicting screen dimensions on netbook
Hi all, On MeeGo 'xdpyinfo | grep dim' gives as output 1024x600 pixels and 214 mm x 127 mm. On Ubuntu we get 1024x600 pixels and 270 mm x 158 mm. Due to this many windows overshoot the screen in MeeGo running on netbooks. Is there a way to change screen geometry size in MeeGo? We have been trying to change screen geometry using Xorg. 'xorg.conf' has an entry 'DisplaySize' in 'Monitor' section where screen size can be set. But whenever the system is run with 'xorg.conf' the keyboard and mouse freeze. Tried changing the device names and drivers but to no effect. Why is there no xorg.conf by default in '/etc/X11' ? Is there any other way to set proper screen size? Regards, Saurabh ___ 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] Compilation issues of Meego touch
Hello, That issue solved. When compiling m-keyboard project ,@ final stage getting error gen_mvirtualkeyboardstyledata.cpp:177:1: error: 'dummyNeverToBeUsedPtr' in class 'MVirtualKeyboardStyleContainer' does not name a type Thanks Yuvaraj R From: Chen, Zhang Z [mailto:zhang.z.c...@intel.com] Sent: Monday, February 21, 2011 1:22 PM To: Ragupathi Yuvaraj; meego-dev@meego.com Subject: RE: Compilation issues of Meego touch Are you using MeeGo SDK to compile? If so, please refer to https://bugs.meego.com/show_bug.cgi?id=13540 for detail descript of the bug. There's also a workaround as specified in the bug comments: you can edit PATH variable in Projects->Build Environment->Using System Environment->Details of QtCreator so that/targets//bin is prior to /madbin From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On Behalf Of yuvaraj.ragupa...@tieto.com Sent: Monday, February 21, 2011 2:41 PM To: meego-dev@meego.com Subject: Re: [MeeGo-dev] Compilation issues of Meego touch Hello, I solved my previous errors. When compiling meego im framework , I am getting is error. i586-meego-linux-gnu-g++: .moc/moc_mabstractinputmethod.cpp: No such file or directory. I think, these error occurring because of "moc: not supported in this target" What I need to do to solve these issues Thanks Yuvaraj R From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On Behalf Of yuvaraj.ragupa...@tieto.com Sent: Monday, February 21, 2011 10:17 AM To: meego-dev@meego.com Subject: [MeeGo-dev] Compilation issues of Meego touch Hello, I am compiling meego touch framework. Getting issue with adding header files (/usr/include*). My virtual machine box is not taking /usr/include path automatically. This is happening only with meego touch framework. If I give absolute path mean ( instead of ), its working fine. Thanks Yuvaraj R ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] the dependent relationship problem when build src.rpm
Hi All, The following error appears when I use rpmbuild to build src.rpm packages on ubuntu 10.10. error: Failed build dependencies: module-init-tools is needed by kernel-netbook-2.6.35.3-12.1.i386 bash >= 2.03 is needed by kernel-netbook-2.6.35.3-12.1.i386 sh-utils is needed by kernel-netbook-2.6.35.3-12.1.i386 findutils is needed by kernel-netbook-2.6.35.3-12.1.i386 make >= 3.78 is needed by kernel-netbook-2.6.35.3-12.1.i386 linux-firmware is needed by kernel-netbook-2.6.35.3-12.1.i386 elfutils-libelf-devel is needed by kernel-netbook-2.6.35.3-12.1.i386 binutils-devel is needed by kernel-netbook-2.6.35.3-12.1.i386 newt-devel is needed by kernel-netbook-2.6.35.3-12.1.i386 But I am sure that the Make Version is 3.8. How to resolve the dependent relationship problem on ubuntu? I am looking forward to your feedback. Thank you very much! Regards, Steven ,Zhang 张凌鹤 PRC DRD Atom Platform Enabling Team Tel: 86-755-25830868 - 1116 INET: 8754 - 1116 Cell Phone: 13798361680 ___ 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] Fail to run the Phoronix "qgears2" test suit for 3D benchmark.
On 2/21/2011 6:05 PM, jms yang wrote: hi There Just verified that the Phoronix test suit "qgears" with OpenGL rendering is capable to test on Acer AspireOne with pinetrail image(e.g. MeeGo release 1.1.90 (MeeGo) BUILD: meego-tablet-ia32-pinetrail-1.1.90.2.20110207.22) smoothly. Is there any one successfully test openGL OKAY on MRST/Medfield/Octrail platform? sounds like you need to file a (serious) bug ___ 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] Fail to run the Phoronix "qgears2" test suit for 3D benchmark.
hi There Just verified that the Phoronix test suit "qgears" with OpenGL rendering is capable to test on Acer AspireOne with pinetrail image(e.g. MeeGo release 1.1.90 (MeeGo) BUILD: meego-tablet-ia32-pinetrail-1.1.90.2.20110207.22) smoothly. Is there any one successfully test openGL OKAY on MRST/Medfield/Octrail platform? 2011/2/15 Wichmann, Mats D > > > -- > *From:* meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] *On > Behalf Of *maceo_y...@acer.com.tw > *Sent:* Monday, February 14, 2011 8:14 PM > *To:* meego-dev@meego.com > *Subject:* [MeeGo-dev] Fail to run the Phoronix "qgears2" test suit for 3D > benchmark. > > > Hi There > I've been try to run part of the PTS(Phoronix Test Suit) tests for system > benchmark of my Meego device. > I manually zypper installed some packages(php-cli, libX11-devel, > libXrender-devel, libqtopengl-develand its dependencies ) in order to > make qgears2 to run correctly. > (Attached file record the manual installed packages in order to run the PTS > test.) > > I met a fatal error as below and return right away without a result comes > out when I runs the qgears2 sub-item OpenGL->Gears. > > *"PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried > to allocate 192771641 bytes) in > /usr/share/phoronix-test-suite/pts-core/library/pts-includes-run.php on line > 624"* > > I did check the free memory and storage left after error return, I think > they are all enough for the test at the moment. > Do I have to run-time check it ? > > the message in red is php's limit, you can up the size in /etc/php.ini, > look for memory_limit > > > > ___ > 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 http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] kernel_panic on on mrst-mtf image
I've seen this on my system, and issue is gone after updating to the latest FW (SCU). --Tommy From: praveen pandey [mailto:praveen.pan...@gmail.com] Sent: Monday, February 21, 2011 9:06 PM To: meego-dev@meego.com Subject: [MeeGo-dev] kernel_panic on on mrst-mtf image Hi, I am using http://repo.meego.com/MeeGo/builds/1.1.90/1.1.90.2.20110208.4/handset/images/meego-handset-ia32-mrst-mtf/ image on moorsetown Hardware but I am not able to boot. I have attached the logs here. somewhere in the call trace it points to intel_sst. Any idea on this. BR, Praveen Pandey ___ 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] By the way audio actually works in MeeGo "1.2" netbook
> - Original message - > From: "Niels Mayer" > To: meego-dev@meego.com > Subject: [MeeGo-dev] By the way audio actually works in MeeGo "1.2" netbook > Date: Mon, 21 Feb 2011 13:07:38 -0800 > > > Now I have audio working on the internal card -- I have absolutely no > reasons to upgrade beyond the hybrid release I've created... BTW, that's some really cool work you're doing Niels. So... what does it take to make your hybrid release more-or-less official? :D Randy -- 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
[MeeGo-dev] By the way audio actually works in MeeGo "1.2" netbook
http://qa-reports.meego.com/1.2/Netbook/Acceptance/Pinetrail/ indicates that audio is not working in ( https://bugs.meego.com/show_bug.cgi?id=13436 ). Worksforme :-) Seeing pulseaudio churning away like it does whenever audio is output, and events going into the audio device had me look at something a little simpler... You just have to remember to turn up "Master" volume at the ALSA level! This has nothing to do with pulseaudio per say, other than gettting in the way and hiding important device information ... The GUI volume control only changes "PCM" ; by default it seems "Master" is set to 0 and hidden. In KDE/phonon's 'kmix' this is handled more elegantly, IMHO -- you can choose which device the GUI and keyboard volume control actually changes -- e.g. PCM/Master/Headphone/etc -- or route your "media" audio to an external SPDIF or HDMI digital output, leaving the computer speakers for system sounds and other low-fi. On the MeeGo 1.2 netbook, running on Lenovo s10-3t reference platform, running "alsamixer -c 0" in a terminal will let you see what's going on and adjust the "Master" volume using the cursor keys. Here's how I got it adjusted currently: meegolem-156-~> amixer -c 0 Simple mixer control 'Master',0 Capabilities: pvolume pswitch pswitch-joined penum Playback channels: Front Left - Front Right Limits: Playback 0 - 74 Mono: Front Left: Playback 74 [100%] [0.00dB] [on] Front Right: Playback 74 [100%] [0.00dB] [on] Simple mixer control 'PCM',0 Capabilities: pvolume penum Playback channels: Front Left - Front Right Limits: Playback 0 - 255 Mono: Front Left: Playback 255 [100%] [0.00dB] Front Right: Playback 255 [100%] [0.00dB] Simple mixer control 'Capture',0 Capabilities: cvolume cswitch penum Capture channels: Front Left - Front Right Limits: Capture 0 - 80 Front Left: Capture 80 [100%] [6.00dB] [on] Front Right: Capture 80 [100%] [6.00dB] [on] Simple mixer control 'Analog Mic Boost',0 Capabilities: cenum Items: '0dB' '10dB' '20dB' '30dB' '40dB' Item0: '0dB' .. Now I have audio working on the internal card -- I have absolutely no reasons to upgrade beyond the hybrid release I've created... especially now that I've got Fedora 14/RPMFusion/PlanetCCRMA/Google repositories integrated :-). Oh wait the video isn't working yet. But then again how could it be given that v4l modules aren't installed? meegolem-162-~> lsmod Module Size Used by snd_usb_audio 81305 0 snd_usbmidi_lib15341 1 snd_usb_audio snd_rawmidi16190 1 snd_usbmidi_lib ath9k 65616 0 ath9k_common1977 1 ath9k ideapad_laptop 3517 0 joydev 8181 0 ath9k_hw 243231 2 ath9k,ath9k_common serio_raw 3797 0 battery 8850 0 So which of these do I 'modprobe' to get the Lenovo s10-3t camera working?? meegolem-160-~> modprobe -l | grep vid kernel/drivers/video/backlight/adp8860_bl.ko kernel/drivers/video/vgastate.ko kernel/drivers/video/sysfillrect.ko kernel/drivers/video/syscopyarea.ko kernel/drivers/video/sysimgblt.ko kernel/drivers/video/fb_sys_fops.ko kernel/drivers/media/video/tuner.ko kernel/drivers/media/video/tda9840.ko kernel/drivers/media/video/tea6415c.ko kernel/drivers/media/video/tea6420.ko kernel/drivers/media/video/saa7115.ko kernel/drivers/media/video/tveeprom.ko kernel/drivers/media/video/sr030pc30.ko kernel/drivers/media/video/cpia2/cpia2.ko kernel/drivers/media/video/mxb.ko kernel/drivers/media/video/videobuf-core.ko kernel/drivers/media/video/videobuf-dma-sg.ko kernel/drivers/media/video/videobuf-dma-contig.ko kernel/drivers/media/video/videobuf-vmalloc.ko kernel/drivers/media/video/videobuf-dvb.ko kernel/drivers/media/video/zr364xx.ko kernel/drivers/media/video/stkwebcam.ko kernel/drivers/media/video/sn9c102/sn9c102.ko kernel/drivers/media/video/et61x251/et61x251.ko kernel/drivers/media/video/pwc/pwc.ko kernel/drivers/media/video/gspca/gspca_main.ko kernel/drivers/media/video/gspca/gspca_jeilinj.ko kernel/drivers/media/video/gspca/gspca_konica.ko kernel/drivers/media/video/gspca/gspca_mr97310a.ko kernel/drivers/media/video/gspca/gspca_sn9c20x.ko kernel/drivers/media/video/gspca/gspca_spca1528.ko kernel/drivers/media/video/gspca/gspca_sq905.ko kernel/drivers/media/video/gspca/gspca_sq905c.ko kernel/drivers/media/video/gspca/gspca_sq930x.ko kernel/drivers/media/video/gspca/gspca_xirlink_cit.ko kernel/drivers/media/video/gspca/gl860/gspca_gl860.ko kernel/drivers/media/video/s2255drv.ko kernel/drivers/media/video/uvc/uvcvideo.ko kernel/drivers/media/video/saa7164/saa7164.ko kernel/drivers/video/i810/i810fb.ko Niels http://nielsmayer.com PS: (*) FYI snd_usbmidi_libsnd_usb_audio snd_rawmidi snd_usbmidi_lib all got loaded up because I was testing out the packages I'd just installed on this "1.2 MeeGolem" http://jackaudio.org and http://qjackctl.sourceforge.net and http://www.hydrogen-music.org/ I'd loaded up with a little install: ROO
Re: [MeeGo-dev] kernel_panic on on mrst-mtf image
On 2/21/2011 5:05 AM, praveen pandey wrote: Hi, I am using http://repo.meego.com/MeeGo/builds/1.1.90/1.1.90.2.20110208.4/handset/images/meego-handset-ia32-mrst-mtf/ image on moorsetown Hardware but I am not able to boot. I have attached the logs here. somewhere in the call trace it points to intel_sst. you're going to need to provide a lot more detail for us to be able to help you. Also, our mrst kernel is for a very specific mrst device, and likely not yours... what kind of device are you using ___ 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 play a video is h.264 in meego-handset-video player
Hi, >___ >From: meego-dev-boun...@meego.com [meego-dev-boun...@meego.com] On Behalf Of >stefan.k...@nokia.com [stefan.k...@nokia.com] >Sent: Monday, February 21, 2011 4:54 PM >To: cars...@maemo.org; ssukh...@gmail.com >Cc: meego-dev@meego.com >Subject: Re: [MeeGo-dev] how to play a video is h.264 in >meego-handset-video player > >Hi, > >>-Original Message- >>From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] >>On Behalf Of ext Carsten Munk >>Sent: 17 February, 2011 11:35 >>To: ssuk hyun kim >>Cc: meego-dev@meego.com >>Subject: Re: [MeeGo-dev] how to play a video is h.264 in meego-handset- >>video player >> >>2011/2/17 ssuk hyun kim : >>> Hi All, >>> I am trying to play a video which is h.264 via meego-handset-video >>player on >>> N900. But it doesn't play. ogg plays well. >>> N900 is installed MeeGo handset 1.1 image. >>> Please let me know how to video can play mp4 and h.264. >>> Regards, >>> SH >>MP4 and H264 aren't supported in MeeGo out of the box because of >>royalty/patent issues. It's possible to install codecs manually >>though. For anybody interested in MeeGo N900 & DSP codecs: http://wiki.meego.com/ARM/N900/Tips_and_Tricks/DSP BR, Topi > >Mp4 as a container format is supported via the qtdemux plugin from >gst-plugins-good :) > >Stefan >> >> >>/Carsten >> >>> ___ >>> 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 ___ 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 play a video is h.264 inmeego-handset-video player
In Moblin, GStreamer plugins for H.264 works in Intel Atom reference board. Does it not work in MeeGo? What about WMA? Regards Vijayendra -Original Message- From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On Behalf Of stefan.k...@nokia.com Sent: Monday, 21 February, 2011 8:24 PM To: cars...@maemo.org; ssukh...@gmail.com Cc: meego-dev@meego.com Subject: Re: [MeeGo-dev] how to play a video is h.264 inmeego-handset-video player Hi, >-Original Message- >From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] >On Behalf Of ext Carsten Munk >Sent: 17 February, 2011 11:35 >To: ssuk hyun kim >Cc: meego-dev@meego.com >Subject: Re: [MeeGo-dev] how to play a video is h.264 in meego-handset- >video player > >2011/2/17 ssuk hyun kim : >> Hi All, >> I am trying to play a video which is h.264 via meego-handset-video >player on >> N900. But it doesn't play. ogg plays well. >> N900 is installed MeeGo handset 1.1 image. >> Please let me know how to video can play mp4 and h.264. >> Regards, >> SH >MP4 and H264 aren't supported in MeeGo out of the box because of >royalty/patent issues. It's possible to install codecs manually though. Mp4 as a container format is supported via the qtdemux plugin from gst-plugins-good :) Stefan > >/Carsten > >> ___ >> 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 ___ 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 play a video is h.264 in meego-handset-video player
Hi, >-Original Message- >From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] >On Behalf Of ext Carsten Munk >Sent: 17 February, 2011 11:35 >To: ssuk hyun kim >Cc: meego-dev@meego.com >Subject: Re: [MeeGo-dev] how to play a video is h.264 in meego-handset- >video player > >2011/2/17 ssuk hyun kim : >> Hi All, >> I am trying to play a video which is h.264 via meego-handset-video >player on >> N900. But it doesn't play. ogg plays well. >> N900 is installed MeeGo handset 1.1 image. >> Please let me know how to video can play mp4 and h.264. >> Regards, >> SH >MP4 and H264 aren't supported in MeeGo out of the box because of >royalty/patent issues. It's possible to install codecs manually >though. Mp4 as a container format is supported via the qtdemux plugin from gst-plugins-good :) Stefan > >/Carsten > >> ___ >> 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] how to log message from screen orientation to sensorfw?
>-Original Message- >From: Jia-Chi Lai [mailto:jackie09050...@gmail.com] >Sent: Monday, February 21, 2011 10:07 AM >To: Rongas Timo >Cc: meego-dev@meego.com >Subject: Re: [MeeGo-dev] how to log message from screen orientation to >sensorfw? > > > >2011/2/16 Rongas Timo > > > >From: meego-dev-boun...@meego.com [mailto:meego-dev- > >boun...@meego.com] On Behalf Of Jia-Chi Lai > >Sent: Wednesday, February 16, 2011 11:47 AM > >To: meego-dev@meego.com > >Subject: [MeeGo-dev] how to log message from screen orientation >to > >sensorfw? > > > > >hi~ > > > >I open a setting application and change the orientation of device.The >screen > >will change the orientation. > > > >I would like to log message from application screen orientation to >sensorfw to > >see what happen when I install a qt-mobility rpm. > >the rpm which I build with qt-mobility-1.2.0~beta0+git922- >2.11.src.rpm and > >after I install it, then the screen can not change the orientation when >I change > >device orientation. > > > >anyone know how to log the message from application screen >orientation to > >sensorfw?? > >Or any idea about this question?? > > > If I understood correctly, you wish to get log entries whenever >sensord detect a change in orientation, right? > > You can adjust sensord logging level by sending it SIGUSR1. The >modes are test, debug, warning, critical. Each received signal notches the >level >up by one. By default the level is 'warning', so send it two signals to get >'test' >level messages. Look for line saying "new orientation value". Expect a lot of >noise to the log. > > You can also start sensord manually and give it the logging level and >target file as parameters. By default syslog is used. See sensord --help > > > > >yes, I use --log-level=debug --log-target=1 and the log message is shown in >the console, but the last message show: Dbus abort. This is because only one Sensorfw daemon can be connected to DBus at a time. >So, I kill the sensord and manually start the sensord and the log of sensord >are >shown on console. >But I would like to get more log message, from qt-mobility to sensorfw. >Do you know how to get the log message of "orientation-contextkit- >sensor" ,"sensorfw" , "qt-mobility sensor" when the screen orientation is >started at the same time? Depends on what you are after, but how about just having 3 consoles open, each monitoring the output of one of those components? Manually started sensord pushing out logs in the first, context-listen showing context info in the next, and some example client from QtMobility (e.g. show_orientation) in the third. Or write a nifty script that does all of that and hands you the output in a nice format? :) // Timo ___ 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] Are there any methods to setContentType for the QML component(TextInput or ...).
On Fri, 2011-02-18 at 16:16 +0800, ext danny wrote:
> Hi all,
>
> In the MTF , we could set the content type for MTextEdit by:
>
> MTextEdit *edit = new MTextEdit();
> edit->setContentType(M::NumberContentType);
>
> I try to find it in the QML related documents, but failed at the end.
> So I come here to ask are there any methods to set the content type
> for the TextInput component in QML?
TextInput {
inputMethodHints: Qt.ImhDigitsOnly
}
should do it.
___
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 log message from screen orientation to sensorfw?
2011/2/16 Rongas Timo > >From: meego-dev-boun...@meego.com [mailto:meego-dev- > >boun...@meego.com] On Behalf Of Jia-Chi Lai > >Sent: Wednesday, February 16, 2011 11:47 AM > >To: meego-dev@meego.com > >Subject: [MeeGo-dev] how to log message from screen orientation to > >sensorfw? > > > >hi~ > > > >I open a setting application and change the orientation of device.The > screen > >will change the orientation. > > > >I would like to log message from application screen orientation to > sensorfw to > >see what happen when I install a qt-mobility rpm. > >the rpm which I build with qt-mobility-1.2.0~beta0+git922-2.11.src.rpm and > >after I install it, then the screen can not change the orientation when I > change > >device orientation. > > > >anyone know how to log the message from application screen orientation to > >sensorfw?? > >Or any idea about this question?? > > If I understood correctly, you wish to get log entries whenever sensord > detect a change in orientation, right? > > You can adjust sensord logging level by sending it SIGUSR1. The modes are > test, debug, warning, critical. Each received signal notches the level up by > one. By default the level is 'warning', so send it two signals to get 'test' > level messages. Look for line saying "new orientation value". Expect a lot > of noise to the log. > > You can also start sensord manually and give it the logging level and > target file as parameters. By default syslog is used. See sensord --help > > yes, I use --log-level=debug --log-target=1 and the log message is shown in the console, but the last message show: Dbus abort. So, I kill the sensord and manually start the sensord and the log of sensord are shown on console. But I would like to get more log message, from qt-mobility to sensorfw. Do you know how to get the log message of "orientation-contextkit-sensor" ,"sensorfw" , "qt-mobility sensor" when the screen orientation is started at the same time? thanks. > Depends on what you really are after, you can also try looking at > Screen.TopEdge context property. (context-listen Screen.TopEdge). > > // Timo > > ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
