We are just wondering about the messages.
We have written just a adopter plug-in (as attached in previous mail)
and we have debug messages in als adopter but none seems to be coming..
Is there a way to test it in client API test(like alsadopter and alssensor are
working properly)?
By default code is this one...
void ClientApiTest::testALSSensor()
{
QString sensorName("alssensor");
SensorManagerInterface& sm = SensorManagerInterface::instance();
QVERIFY( sm.isValid() );
// Attempt to get another control session
ALSSensorChannelInterface* failIfc =
ALSSensorChannelInterface::controlInterface(sensorName);
QVERIFY2(!failIfc, "Got another control session");
}
This is what we understand for MeeGO
Qt mobility:
Application-->(Qsensor. QAmbientLightReading)-->(sensor backend/our case it may
falling to mameo6)
Sensor Framework:(Sensor backend)
Plug-in interface-->(alssensor and alsadopter)
-----Original Message-----
From: Rongas Timo [mailto:[email protected]]
Sent: Wednesday, December 01, 2010 1:26 PM
To: Preetham-rao K; [email protected]
Subject: RE: [MeeGo-dev] Sensor Framework: Show_als application not working on
QT mobility level
>-----Original Message-----
>From: [email protected]
>[mailto:[email protected]] On Behalf Of Preetham-rao K
>Sent: Tuesday, November 30, 2010 12:42 PM
>To: [email protected]
>Subject: [MeeGo-dev] Sensor Framework: Show_als application
>not working on QT mobility level
>
>Hi Timo & Markus,
>
>
>
>We want to test qt mobility test application given for sensors
>like show_als
>
>We have written adopter for BH1780 ALS using sysfs adopter
>class in meego sensor framework(0.6.19)
>
>Please see the code attached (based on BH1780 driver in linux kernel)
>
>
>
>But when we run the test we are getting following log.
>
>Have we done something wrong?
>
>
>
>"[r...@localhost bin]# ./show_als
>
>loaded the Generic plugin
>
>loaded the grue plugin
>
>Loaded the Maemo 6 sensor plugin
>
>Request for control interface not granted...
>
>New listen sensor "alssensor" interface created with session id 3 ...
>
>Data rate in don't care mode (interval 0 ms) for "alssensor""
The log seems to be fine. It just shows that sensord did not grant you "control
session" for ALS, and as a fallback you got a "listen session". There is no
practical difference between control/listen anymore, and the whole concept
could get deprecated.
You might want to define a default interval for your adaptor with
setDefaultInterval(), as it runs in busypoll mode. You will still see '0' as
the value via QtMobility to notify 'I don't care', but the adaptor behaves
reasonably. If there's no default, it defaults to zero, which means it will
keep reading as fast as the system allows it to.
setDefaultInterval() is available from sensord-0.6.28. If you need things to
run nicely with 0.6.19, you need to handle the interval setting directly with
the interval property.
Do you have trouble seeing ALS values, or were you just wondering about the
messages?
// Timo
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
