message slot problems--QMessageManager::messageAdded

[zuo3diao]

My devices is N900 PR1.2 and i follow the http://wiki.forum.nokia.com/index.ph...g_an_SMS_in_Qt direct to do ,but it is not realize like it discribe.

I use windows 7 and Nokia qt SDK 1.0 release, very common , I search some place about QMessageManager::messageAdded and Qt Mobility ,some people looks like in the same trouble.

Who explain this ? How get the signal when the sms incoming?

[zuo3diao]

It looks like TpSession have some bugs. TpSession can print some infomation but qt mobilty not emit out.

ModestEngine::ModestEngine Starting to initialize 
ModestEngine::ModestEngine Connecting to Modest DBus Interface 
ModestEngine::ModestEngine Connected to Modest DBus Interface 
ModestEngine::ModestEngine Connecting to Qt Mobility Modest Plugin DBus Interface 

ModestEngine::ModestEngine Connected to Qt Mobility Modest Plugin DBus Interface 
ModestEngine::ModestEngine Initialized successfully 

TpSessionAccount::onNewChannels 
 channelType: "org.freedesktop.Telepathy.Channel.Type.Text"  requested  : false  targetId "18924704680" 

TpSessionAccount::onNewChannels path= path  "/org/freedesktop/Telepathy/Connection/ring/tel/ring/text29" 
TpSessionChannel::TpSessionChannel path  "/org/freedesktop/Telepathy/Connection/ring/tel/ring/text29" 

TpSessionChannel::onChannelReady type= "org.freedesktop.Telepathy.Channel.Type.Text" path  "/org/freedesktop/Telepathy/Connection/ring/tel/ring/text29" initiatorContact= "18924704680" 
received  "123" 
TpSessionAccount::onMessageReceived  "123" 
TestProg::onMessageReceived  "123" from  "18924704680"

[divanov]

There is nothing in the debug output indicating a bug. Do you trigger SMS in Qt Simulator?

[zuo3diao]

qt simulator I use it only for designer.. it is not suiltable for the maemo5 dev. The menu for maemo5 cann't be show in the simulator.
I got the problem, that wiki page may test the

QMessageManager::NotificationFilterId m_notificationFilterId = m_manager->registerNotificationFilter( QMessageFilter());

not test

// Create 2 filers set for filtering messages
// - SMS filter
// - InboxFolder filter
// m_notifFilterSet.insert( m_manager->registerNotificationFilter(
// QMessageFilter::byType(QMessage::AnyType) &
// QMessageFilter::byStandardFolder(QMessage::InboxFolder)
// ));
}

So the QMessageManager::NotificationFilterIdSet may have a bug, the QMessageManager::NotificationFilterId section work well , but the other that wiki told do not work.

[divanov]

So are you testing on the N900 device?

[zuo3diao]

Yeah, I tested in N900 at PR1.2.

[divanov]

I've compiled example from http://wiki.forum.nokia.com/index.ph...g_an_SMS_in_Qt
and it works as expected in 19-1 image.

[zuo3diao]

I comfirm that

m_notifFilterSet.insert( m_manager->registerNotificationFilter(
QMessageFilter::byType(QMessage::Sms) &
QMessageFilter::byStandardFolder(QMessage::InboxFolder)
));

not work in 19-1 image (PR1.2), but change it to

QMessageManager::NotificationFilterId m_notificationFilterId = m_manager->registerNotificationFilter( QMessageFilter());

work fine. I restart the devices before test.

[divanov]

There is no need to restart the device. Is your version of Qt Mobility 1:1.0.0-maemo1+0m5?

[zuo3diao]

hi ，how to check the qt mobility 's version ? and how to update it ?

[zuo3diao]

apt-cache show libqtm-messaging


./libqtm-messaging_1.0.0-maemo1+0m5_armel.deb

version is correct?

[divanov]

apt-cache is good, but it shows information about packages available in the repository, not on the device, if you can see a tiny, but crucial difference.
Use

dpkg -l libqtm-messaging

instead.

[zuo3diao]

hi ， I execute the command of your support. The snap screen image is below .
http://picasaweb.google.fi/lh/photo/...eat=directlink
These infomation are right?

[divanov]

Yes, it seems that you have the latest Qt Mobility Messaging library.

[pingiori]

I comfirm that not work in 19-1 image (PR1.2), but change it to work fine. I restart the devices before test.

hello zuo3diao,
I experienced your same troubles and modified the source code the way you suggest. My program is now able to "see" an incoming SMS; however it can read neither the textContent() property of the message, nor the address (from().addressee() property) of the sender. It seems like the QMessageId& passed by the signal messageAdded is not valid.
Did you find any solution to these problems?
Thanks for now
pingiori