Pandora + Pebble = Music Control (and hopefully more)


@ptitSeb: I'll try finding a way to compile libQt5contacts first.

From what I can tell, manager.h assigns QtContacts as it's namespace. I feel like that might make it difficult to identify and stub out any function calls that are being made to that lib. I could be on the complete wrong track about that though.

Interesting that libQt5contacts doesn't seem to get used anywhere else.
 
@ptitSeb: It hasn't gone well so far. I'll keep working on it, but you may be right about just trying to move ahead without it. I downloaded the source for qtpim and tried to compile, but the .pro had been deactivated. After removing "requires(fail)" from the .pro. then make started playing nicer.

For some reason, the headers all have their includes pointing to other header files using a path that doesn't exist (e.g. "#include <QtContacts/qcontactdetail.h>") so g++ couldn't locate the headers. Copying all the header files to "/usr/include/QtContacts" got me past that one.

However, now I have an output that I don't understand at all:
/home/edgex004/Downloads/qtpim2/qtpim-dev$ qmake5 qtpim.proInfo: creating cache file /home/edgex004/Downloads/qtpim2/qtpim-dev/.qmake.cache
/home/edgex004/Downloads/qtpim2/qtpim-dev$ make
cd src/ && ( test -e Makefile || /mnt/utmp/codeblocks/qt5/bin/qmake5 /home/edgex004/Downloads/qtpim2/qtpim-dev/src/src.pro -o Makefile ) && make -f Makefile
make[1]: Entering directory '/home/edgex004/Downloads/qtpim2/qtpim-dev/src'
cd contacts/ && ( test -e Makefile || /mnt/utmp/codeblocks/qt5/bin/qmake5 /home/edgex004/Downloads/qtpim2/qtpim-dev/src/contacts/contacts.pro -o Makefile ) && make -f Makefile
make[2]: Entering directory '/home/edgex004/Downloads/qtpim2/qtpim-dev/src/contacts'
g++ -O3 -mcpu=cortex-a8 -mfpu=neon -ftree-vectorize -mfloat-abi=softfp -mno-unaligned-access -fuse-ld=gold -fuse-linker-plugin -fdiagnostics-color=auto -fsigned-char -mneon-for-64bits -mthumb-interwork -fpermissive -O2 -fvisibility=hidden -fvisibility-inlines-hidden -std=c++0x -fno-exceptions -Wall -W -D_REENTRANT -fPIC -DQT_NO_MTDEV -DQT_BUILD_CONTACTS_LIB -DQT_BUILDING_QT -DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS -DQT_MOC_COMPAT -DQT_USE_QSTRINGBUILDER -DQT_DEPRECATED_WARNINGS -DQT_DISABLE_DEPRECATED_BEFORE=0x050000 -DQT_NO_EXCEPTIONS -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -DQT_NO_DEBUG -DQT_CORE_LIB -I/mnt/utmp/codeblocks/qt5/mkspecs/linux-pandora-g++ -I. -Idetails -I. -Iengines -Ifilters -Irequests -I../../include -I../../include/QtContacts -I/home/edgex004/Downloads/qtpim2/qtpim-dev/include/QtContacts/0.0.0 -I/home/edgex004/Downloads/qtpim2/qtpim-dev/include/QtContacts/0.0.0/QtContacts -I/mnt/utmp/codeblocks/qt5/include/QtCore/5.4.0 -I/mnt/utmp/codeblocks/qt5/include/QtCore/5.4.0/QtCore -I/mnt/utmp/codeblocks/qt5/include -I/mnt/utmp/codeblocks/qt5/include/QtCore -I.moc -x c++-header -c ../../include/QtContacts/QtContactsDepends -o .pch/Qt5Contacts.gch/c++
g++ -c -include .pch/Qt5Contacts -O3 -mcpu=cortex-a8 -mfpu=neon -ftree-vectorize -mfloat-abi=softfp -mno-unaligned-access -fuse-ld=gold -fuse-linker-plugin -fdiagnostics-color=auto -fsigned-char -mneon-for-64bits -mthumb-interwork -fpermissive -O2 -fvisibility=hidden -fvisibility-inlines-hidden -std=c++0x -fno-exceptions -Wall -W -D_REENTRANT -fPIC -DQT_NO_MTDEV -DQT_BUILD_CONTACTS_LIB -DQT_BUILDING_QT -DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS -DQT_MOC_COMPAT -DQT_USE_QSTRINGBUILDER -DQT_DEPRECATED_WARNINGS -DQT_DISABLE_DEPRECATED_BEFORE=0x050000 -DQT_NO_EXCEPTIONS -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -DQT_NO_DEBUG -DQT_CORE_LIB -I/mnt/utmp/codeblocks/qt5/mkspecs/linux-pandora-g++ -I. -Idetails -I. -Iengines -Ifilters -Irequests -I../../include -I../../include/QtContacts -I/home/edgex004/Downloads/qtpim2/qtpim-dev/include/QtContacts/0.0.0 -I/home/edgex004/Downloads/qtpim2/qtpim-dev/include/QtContacts/0.0.0/QtContacts -I/mnt/utmp/codeblocks/qt5/include/QtCore/5.4.0 -I/mnt/utmp/codeblocks/qt5/include/QtCore/5.4.0/QtCore -I/mnt/utmp/codeblocks/qt5/include -I/mnt/utmp/codeblocks/qt5/include/QtCore -I.moc -o .obj/qcontactdetails.o details/qcontactdetails.cpp
details/qcontactdetails.cpp:68:1: error: ���QT_WARNING_PUSH��� does not name a type
QT_WARNING_PUSH
^
details/qcontactdetails.cpp:115:77: error: ���QContactSyncTargetPrivate��� was not declared in this scope
const QContactDetailBuiltinPrivateBase::Member QContactDetailBuiltinPrivate<QContactSyncTargetPrivate>::s_members[] = {
^
details/qcontactdetails.cpp:115:102: error: template argument 1 is invalid
const QContactDetailBuiltinPrivateBase::Member QContactDetailBuiltinPrivate<QContactSyncTargetPrivate>::s_members[] = {
^
In file included from /mnt/utmp/codeblocks/usr/include/_G_config.h:15:0,
from /mnt/utmp/codeblocks/usr/include/libio.h:32,
from /mnt/utmp/codeblocks/usr/include/stdio.h:75,
from /mnt/utmp/codeblocks/qt5/include/QtCore/qtextstream.h:43,
from /mnt/utmp/codeblocks/qt5/include/QtCore/qdebug.h:42,
from /mnt/utmp/codeblocks/qt5/include/QtCore/QtCore:28,
from ../../include/QtContacts/QtContactsDepends:3:
details/qcontactdetails.cpp:116:58: error: ���QContactSyncTargetPrivate��� does not name a type
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactSyncTargetPrivate, m_syncTarget) },
^
details/qcontactdetails.cpp:115:48: warning: ���QtContacts::s_members��� is not a static data member of a class template [-fpermissive]
const QContactDetailBuiltinPrivateBase::Member QContactDetailBuiltinPrivate<QContactSyncTargetPrivate>::s_members[] = {
^
details/qcontactdetails.cpp:115:48: warning: unused variable ���QtContacts::s_members��� [-Wunused-variable]
details/qcontactdetails.cpp: In member function ���QString QtContacts::QContactSyncTarget::syncTarget() const���:
details/qcontactdetails.cpp:140:35: warning: ISO C++ forbids declaration of ���type name��� with no type [-fpermissive]
return reinterpret_cast<const QContactSyncTargetPrivate*>(d.constData())->memberValue<QString>(QContactSyncTarget::FieldSyncTarget);
^
details/qcontactdetails.cpp:140:35: error: expected ���>��� before ���QContactSyncTargetPrivate���
details/qcontactdetails.cpp:140:35: error: expected ���(��� before ���QContactSyncTargetPrivate���
details/qcontactdetails.cpp:140:35: error: ���QContactSyncTargetPrivate��� was not declared in this scope
details/qcontactdetails.cpp:140:61: error: expected primary-expression before ���>��� token
return reinterpret_cast<const QContactSyncTargetPrivate*>(d.constData())->memberValue<QString>(QContactSyncTarget::FieldSyncTarget);
^
details/qcontactdetails.cpp:140:79: error: ���const class QtContacts::QContactDetailPrivate��� has no member named ���memberValue���
return reinterpret_cast<const QContactSyncTargetPrivate*>(d.constData())->memberValue<QString>(QContactSyncTarget::FieldSyncTarget);
^
details/qcontactdetails.cpp:140:98: error: expected primary-expression before ���>��� token
return reinterpret_cast<const QContactSyncTargetPrivate*>(d.constData())->memberValue<QString>(QContactSyncTarget::FieldSyncTarget);
^
details/qcontactdetails.cpp:140:136: error: expected ���)��� before ���;��� token
return reinterpret_cast<const QContactSyncTargetPrivate*>(d.constData())->memberValue<QString>(QContactSyncTarget::FieldSyncTarget);
^
details/qcontactdetails.cpp: In member function ���void QtContacts::QContactSyncTarget::setSyncTarget(const QString&)���:
details/qcontactdetails.cpp:151:22: error: ���QContactSyncTargetPrivate��� does not name a type
reinterpret_cast<QContactSyncTargetPrivate*>(d.data())->setMemberValue<QString>(QContactSyncTarget::FieldSyncTarget, _value);
^
details/qcontactdetails.cpp:151:47: error: expected ���>��� before ���*��� token
reinterpret_cast<QContactSyncTargetPrivate*>(d.data())->setMemberValue<QString>(QContactSyncTarget::FieldSyncTarget, _value);
^
details/qcontactdetails.cpp:151:47: error: expected ���(��� before ���*��� token
details/qcontactdetails.cpp:151:48: error: expected primary-expression before ���>��� token
reinterpret_cast<QContactSyncTargetPrivate*>(d.data())->setMemberValue<QString>(QContactSyncTarget::FieldSyncTarget, _value);
^
details/qcontactdetails.cpp:151:61: error: ���class QtContacts::QContactDetailPrivate��� has no member named ���setMemberValue���
reinterpret_cast<QContactSyncTargetPrivate*>(d.data())->setMemberValue<QString>(QContactSyncTarget::FieldSyncTarget, _value);
^
details/qcontactdetails.cpp:151:83: error: expected primary-expression before ���>��� token
reinterpret_cast<QContactSyncTargetPrivate*>(d.data())->setMemberValue<QString>(QContactSyncTarget::FieldSyncTarget, _value);
^
details/qcontactdetails.cpp:151:122: warning: left operand of comma operator has no effect [-Wunused-value]
reinterpret_cast<QContactSyncTargetPrivate*>(d.data())->setMemberValue<QString>(QContactSyncTarget::FieldSyncTarget, _value);
^
details/qcontactdetails.cpp:151:129: error: expected ���)��� before ���;��� token
reinterpret_cast<QContactSyncTargetPrivate*>(d.data())->setMemberValue<QString>(QContactSyncTarget::FieldSyncTarget, _value);
^
In file included from /mnt/utmp/codeblocks/usr/include/_G_config.h:15:0,
from /mnt/utmp/codeblocks/usr/include/libio.h:32,
from /mnt/utmp/codeblocks/usr/include/stdio.h:75,
from /mnt/utmp/codeblocks/qt5/include/QtCore/qtextstream.h:43,
from /mnt/utmp/codeblocks/qt5/include/QtCore/qdebug.h:42,
from /mnt/utmp/codeblocks/qt5/include/QtCore/QtCore:28,
from ../../include/QtContacts/QtContactsDepends:3:
details/qcontactdetails.cpp: At global scope:
details/qcontactdetails.cpp:178:87: warning: invalid access to non-static data member ���QtContacts::QContactEmailAddressPrivate::m_emailAddress��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactEmailAddressPrivate, m_emailAddress) },
^
details/qcontactdetails.cpp:178:87: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:235:81: warning: invalid access to non-static data member ���QtContacts::QContactFamilyPrivate::m_spouse��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactFamilyPrivate, m_spouse) },
^
details/qcontactdetails.cpp:235:81: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:236:85: warning: invalid access to non-static data member ���QtContacts::QContactFamilyPrivate::m_children��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::StringList, offsetof(QContactFamilyPrivate, m_children) },
^
details/qcontactdetails.cpp:236:85: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:313:81: warning: invalid access to non-static data member ���QtContacts::QContactFavoritePrivate::m_favorite��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::Bool, offsetof(QContactFavoritePrivate, m_favorite) },
^
details/qcontactdetails.cpp:313:81: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:314:80: warning: invalid access to non-static data member ���QtContacts::QContactFavoritePrivate::m_index��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::Int, offsetof(QContactFavoritePrivate, m_index) },
^
details/qcontactdetails.cpp:314:80: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:407:86: warning: invalid access to non-static data member ���QtContacts::QContactAnniversaryPrivate::m_calendarId��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactAnniversaryPrivate, m_calendarId) },
^
details/qcontactdetails.cpp:407:86: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:408:88: warning: invalid access to non-static data member ���QtContacts::QContactAnniversaryPrivate::m_originalDate��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::DateTime, offsetof(QContactAnniversaryPrivate, m_originalDate) },
^
details/qcontactdetails.cpp:408:88: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:409:86: warning: invalid access to non-static data member ���QtContacts::QContactAnniversaryPrivate::m_event��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactAnniversaryPrivate, m_event) },
^
details/qcontactdetails.cpp:409:86: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:410:83: warning: invalid access to non-static data member ���QtContacts::QContactAnniversaryPrivate::m_subType��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::Int, offsetof(QContactAnniversaryPrivate, m_subType) },
^
details/qcontactdetails.cpp:410:83: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:577:78: warning: invalid access to non-static data member ���QtContacts::QContactAvatarPrivate::m_imageUrl��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::Url, offsetof(QContactAvatarPrivate, m_imageUrl) },
^
details/qcontactdetails.cpp:577:78: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:578:78: warning: invalid access to non-static data member ���QtContacts::QContactAvatarPrivate::m_videoUrl��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::Url, offsetof(QContactAvatarPrivate, m_videoUrl) },
^
details/qcontactdetails.cpp:578:78: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:579:81: warning: invalid access to non-static data member ���QtContacts::QContactAvatarPrivate::m_metaData��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactAvatarPrivate, m_metaData) },
^
details/qcontactdetails.cpp:579:81: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:684:82: warning: invalid access to non-static data member ���QtContacts::QContactAddressPrivate::m_street��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactAddressPrivate, m_street) },
^
details/qcontactdetails.cpp:684:82: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:685:82: warning: invalid access to non-static data member ���QtContacts::QContactAddressPrivate::m_locality��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactAddressPrivate, m_locality) },
^
details/qcontactdetails.cpp:685:82: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:686:82: warning: invalid access to non-static data member ���QtContacts::QContactAddressPrivate::m_region��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactAddressPrivate, m_region) },
^
details/qcontactdetails.cpp:686:82: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:687:82: warning: invalid access to non-static data member ���QtContacts::QContactAddressPrivate::m_postcode��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactAddressPrivate, m_postcode) },
^
details/qcontactdetails.cpp:687:82: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:688:82: warning: invalid access to non-static data member ���QtContacts::QContactAddressPrivate::m_country��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactAddressPrivate, m_country) },
^
details/qcontactdetails.cpp:688:82: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:689:83: warning: invalid access to non-static data member ���QtContacts::QContactAddressPrivate::m_subTypes��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::IntList, offsetof(QContactAddressPrivate, m_subTypes) },
^
details/qcontactdetails.cpp:689:83: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:690:82: warning: invalid access to non-static data member ���QtContacts::QContactAddressPrivate::m_pobox��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactAddressPrivate, m_pobox) },
^
details/qcontactdetails.cpp:690:82: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:924:78: warning: invalid access to non-static data member ���QtContacts::QContactUrlPrivate::m_url��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactUrlPrivate, m_url) },
^
details/qcontactdetails.cpp:924:78: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:925:75: warning: invalid access to non-static data member ���QtContacts::QContactUrlPrivate::m_subType��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::Int, offsetof(QContactUrlPrivate, m_subType) },
^
details/qcontactdetails.cpp:925:75: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:1025:86: warning: invalid access to non-static data member ���QtContacts::QContactPhoneNumberPrivate::m_number��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactPhoneNumberPrivate, m_number) },
^
details/qcontactdetails.cpp:1025:86: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:1026:86: warning: invalid access to non-static data member ���QtContacts::QContactPhoneNumberPrivate::m_normalizedNumber��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactPhoneNumberPrivate, m_normalizedNumber) },
^
details/qcontactdetails.cpp:1026:86: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:1027:87: warning: invalid access to non-static data member ���QtContacts::QContactPhoneNumberPrivate::m_subTypes��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::IntList, offsetof(QContactPhoneNumberPrivate, m_subTypes) },
^
details/qcontactdetails.cpp:1027:87: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:1144:85: warning: invalid access to non-static data member ���QtContacts::QContactBirthdayPrivate::m_birthday��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::DateTime, offsetof(QContactBirthdayPrivate, m_birthday) },
^
details/qcontactdetails.cpp:1144:85: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:1145:83: warning: invalid access to non-static data member ���QtContacts::QContactBirthdayPrivate::m_calendarId��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactBirthdayPrivate, m_calendarId) },
^
details/qcontactdetails.cpp:1145:83: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:1246:87: warning: invalid access to non-static data member ���QtContacts::QContactDisplayLabelPrivate::m_label��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactDisplayLabelPrivate, m_label) },
^
details/qcontactdetails.cpp:1246:87: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:1303:78: warning: invalid access to non-static data member ���QtContacts::QContactGenderPrivate::m_gender��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::Int, offsetof(QContactGenderPrivate, m_gender) },
^
details/qcontactdetails.cpp:1303:78: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:1383:86: warning: invalid access to non-static data member ���QtContacts::QContactGeoLocationPrivate::m_label��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactGeoLocationPrivate, m_label) },
^
details/qcontactdetails.cpp:1383:86: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:1384:86: warning: invalid access to non-static data member ���QtContacts::QContactGeoLocationPrivate::m_latitude��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::Double, offsetof(QContactGeoLocationPrivate, m_latitude) },
^
details/qcontactdetails.cpp:1384:86: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:1385:86: warning: invalid access to non-static data member ���QtContacts::QContactGeoLocationPrivate::m_longitude��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::Double, offsetof(QContactGeoLocationPrivate, m_longitude) },
^
details/qcontactdetails.cpp:1385:86: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:1386:86: warning: invalid access to non-static data member ���QtContacts::QContactGeoLocationPrivate::m_accuracy��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::Double, offsetof(QContactGeoLocationPrivate, m_accuracy) },
^
details/qcontactdetails.cpp:1386:86: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:1387:86: warning: invalid access to non-static data member ���QtContacts::QContactGeoLocationPrivate::m_altitude��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::Double, offsetof(QContactGeoLocationPrivate, m_altitude) },
^
details/qcontactdetails.cpp:1387:86: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:1388:86: warning: invalid access to non-static data member ���QtContacts::QContactGeoLocationPrivate::m_altitudeAccuracy��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::Double, offsetof(QContactGeoLocationPrivate, m_altitudeAccuracy) },
^
details/qcontactdetails.cpp:1388:86: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:1389:86: warning: invalid access to non-static data member ���QtContacts::QContactGeoLocationPrivate::m_heading��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::Double, offsetof(QContactGeoLocationPrivate, m_heading) },
^
details/qcontactdetails.cpp:1389:86: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:1390:86: warning: invalid access to non-static data member ���QtContacts::QContactGeoLocationPrivate::m_speed��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::Double, offsetof(QContactGeoLocationPrivate, m_speed) },
^
details/qcontactdetails.cpp:1390:86: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:1391:88: warning: invalid access to non-static data member ���QtContacts::QContactGeoLocationPrivate::m_timestamp��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::DateTime, offsetof(QContactGeoLocationPrivate, m_timestamp) },
^
details/qcontactdetails.cpp:1391:88: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:1640:79: warning: invalid access to non-static data member ���QtContacts::QContactGuidPrivate::m_guid��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactGuidPrivate, m_guid) },
^
details/qcontactdetails.cpp:1640:79: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:1700:80: warning: invalid access to non-static data member ���QtContacts::QContactHobbyPrivate::m_hobby��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactHobbyPrivate, m_hobby) },
^
details/qcontactdetails.cpp:1700:80: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:1761:79: warning: invalid access to non-static data member ���QtContacts::QContactNamePrivate::m_prefix��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactNamePrivate, m_prefix) },
^
details/qcontactdetails.cpp:1761:79: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:1762:79: warning: invalid access to non-static data member ���QtContacts::QContactNamePrivate::m_firstName��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactNamePrivate, m_firstName) },
^
details/qcontactdetails.cpp:1762:79: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:1763:79: warning: invalid access to non-static data member ���QtContacts::QContactNamePrivate::m_middleName��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactNamePrivate, m_middleName) },
^
details/qcontactdetails.cpp:1763:79: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:1764:79: warning: invalid access to non-static data member ���QtContacts::QContactNamePrivate::m_lastName��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactNamePrivate, m_lastName) },
^
details/qcontactdetails.cpp:1764:79: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:1765:79: warning: invalid access to non-static data member ���QtContacts::QContactNamePrivate::m_suffix��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactNamePrivate, m_suffix) },
^
details/qcontactdetails.cpp:1765:79: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:1766:79: warning: invalid access to non-static data member ���QtContacts::QContactNamePrivate::m_customLabel��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactNamePrivate, m_customLabel) },
^
details/qcontactdetails.cpp:1766:79: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:1923:83: warning: invalid access to non-static data member ���QtContacts::QContactNicknamePrivate::m_nickname��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactNicknamePrivate, m_nickname) },
^
details/qcontactdetails.cpp:1923:83: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:1979:79: warning: invalid access to non-static data member ���QtContacts::QContactNotePrivate::m_note��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactNotePrivate, m_note) },
^
details/qcontactdetails.cpp:1979:79: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:2045:78: warning: invalid access to non-static data member ���QtContacts::QContactTagPrivate::m_tag��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactTagPrivate, m_tag) },
^
details/qcontactdetails.cpp:2045:78: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:2117:86: warning: invalid access to non-static data member ���QtContacts::QContactTimestampPrivate::m_modificationTimestamp��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::DateTime, offsetof(QContactTimestampPrivate, m_modificationTimestamp) },
^
details/qcontactdetails.cpp:2117:86: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:2118:86: warning: invalid access to non-static data member ���QtContacts::QContactTimestampPrivate::m_creationTimestamp��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::DateTime, offsetof(QContactTimestampPrivate, m_creationTimestamp) },
^
details/qcontactdetails.cpp:2118:86: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:2119:86: warning: invalid access to non-static data member ���QtContacts::QContactTimestampPrivate::m_deletionTimestamp��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::DateTime, offsetof(QContactTimestampPrivate, m_deletionTimestamp) },
^
details/qcontactdetails.cpp:2119:86: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:2213:76: warning: invalid access to non-static data member ���QtContacts::QContactTypePrivate::m_contactType��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::Int, offsetof(QContactTypePrivate, m_contactType) },
^
details/qcontactdetails.cpp:2213:76: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:2321:88: warning: invalid access to non-static data member ���QtContacts::QContactOnlineAccountPrivate::m_accountUri��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactOnlineAccountPrivate, m_accountUri) },
^
details/qcontactdetails.cpp:2321:88: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:2322:88: warning: invalid access to non-static data member ���QtContacts::QContactOnlineAccountPrivate::m_serviceProvider��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactOnlineAccountPrivate, m_serviceProvider) },
^
details/qcontactdetails.cpp:2322:88: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:2323:85: warning: invalid access to non-static data member ���QtContacts::QContactOnlineAccountPrivate::m_protocol��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::Int, offsetof(QContactOnlineAccountPrivate, m_protocol) },
^
details/qcontactdetails.cpp:2323:85: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:2324:92: warning: invalid access to non-static data member ���QtContacts::QContactOnlineAccountPrivate::m_capabilities��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::StringList, offsetof(QContactOnlineAccountPrivate, m_capabilities) },
^
details/qcontactdetails.cpp:2324:92: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:2325:89: warning: invalid access to non-static data member ���QtContacts::QContactOnlineAccountPrivate::m_subTypes��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::IntList, offsetof(QContactOnlineAccountPrivate, m_subTypes) },
^
details/qcontactdetails.cpp:2325:89: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:2510:87: warning: invalid access to non-static data member ���QtContacts::QContactOrganizationPrivate::m_name��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactOrganizationPrivate, m_name) },
^
details/qcontactdetails.cpp:2510:87: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:2511:84: warning: invalid access to non-static data member ���QtContacts::QContactOrganizationPrivate::m_logoUrl��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::Url, offsetof(QContactOrganizationPrivate, m_logoUrl) },
^
details/qcontactdetails.cpp:2511:84: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:2512:91: warning: invalid access to non-static data member ���QtContacts::QContactOrganizationPrivate::m_department��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::StringList, offsetof(QContactOrganizationPrivate, m_department) },
^
details/qcontactdetails.cpp:2512:91: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:2513:87: warning: invalid access to non-static data member ���QtContacts::QContactOrganizationPrivate::m_location��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactOrganizationPrivate, m_location) },
^
details/qcontactdetails.cpp:2513:87: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:2514:87: warning: invalid access to non-static data member ���QtContacts::QContactOrganizationPrivate::m_role��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactOrganizationPrivate, m_role) },
^
details/qcontactdetails.cpp:2514:87: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:2515:87: warning: invalid access to non-static data member ���QtContacts::QContactOrganizationPrivate::m_title��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactOrganizationPrivate, m_title) },
^
details/qcontactdetails.cpp:2515:87: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:2516:87: warning: invalid access to non-static data member ���QtContacts::QContactOrganizationPrivate::m_assistantName��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactOrganizationPrivate, m_assistantName) },
^
details/qcontactdetails.cpp:2516:87: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:2707:80: warning: invalid access to non-static data member ���QtContacts::QContactRingtonePrivate::m_audioRingtoneUrl��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::Url, offsetof(QContactRingtonePrivate, m_audioRingtoneUrl) },
^
details/qcontactdetails.cpp:2707:80: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:2708:80: warning: invalid access to non-static data member ���QtContacts::QContactRingtonePrivate::m_videoRingtoneUrl��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::Url, offsetof(QContactRingtonePrivate, m_videoRingtoneUrl) },
^
details/qcontactdetails.cpp:2708:80: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:2709:80: warning: invalid access to non-static data member ���QtContacts::QContactRingtonePrivate::m_vibrationRingtoneUrl��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::Url, offsetof(QContactRingtonePrivate, m_vibrationRingtoneUrl) },
^
details/qcontactdetails.cpp:2709:80: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:2831:85: warning: invalid access to non-static data member ���QtContacts::QContactPresencePrivate::m_timestamp��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::DateTime, offsetof(QContactPresencePrivate, m_timestamp) },
^
details/qcontactdetails.cpp:2831:85: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:2832:83: warning: invalid access to non-static data member ���QtContacts::QContactPresencePrivate::m_nickname��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactPresencePrivate, m_nickname) },
^
details/qcontactdetails.cpp:2832:83: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:2833:80: warning: invalid access to non-static data member ���QtContacts::QContactPresencePrivate::m_presenceState��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::Int, offsetof(QContactPresencePrivate, m_presenceState) },
^
details/qcontactdetails.cpp:2833:80: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:2834:83: warning: invalid access to non-static data member ���QtContacts::QContactPresencePrivate::m_presenceStateText��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactPresencePrivate, m_presenceStateText) },
^
details/qcontactdetails.cpp:2834:83: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:2835:80: warning: invalid access to non-static data member ���QtContacts::QContactPresencePrivate::m_presenceStateImageUrl��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::Url, offsetof(QContactPresencePrivate, m_presenceStateImageUrl) },
^
details/qcontactdetails.cpp:2835:80: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:2836:83: warning: invalid access to non-static data member ���QtContacts::QContactPresencePrivate::m_customMessage��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactPresencePrivate, m_customMessage) },
^
details/qcontactdetails.cpp:2836:83: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:3038:91: warning: invalid access to non-static data member ���QtContacts::QContactGlobalPresencePrivate::m_timestamp��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::DateTime, offsetof(QContactGlobalPresencePrivate, m_timestamp) },
^
details/qcontactdetails.cpp:3038:91: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:3039:89: warning: invalid access to non-static data member ���QtContacts::QContactGlobalPresencePrivate::m_nickname��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactGlobalPresencePrivate, m_nickname) },
^
details/qcontactdetails.cpp:3039:89: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:3040:86: warning: invalid access to non-static data member ���QtContacts::QContactGlobalPresencePrivate::m_presenceState��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::Int, offsetof(QContactGlobalPresencePrivate, m_presenceState) },
^
details/qcontactdetails.cpp:3040:86: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:3041:89: warning: invalid access to non-static data member ���QtContacts::QContactGlobalPresencePrivate::m_presenceStateText��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactGlobalPresencePrivate, m_presenceStateText) },
^
details/qcontactdetails.cpp:3041:89: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:3042:86: warning: invalid access to non-static data member ���QtContacts::QContactGlobalPresencePrivate::m_presenceStateImageUrl��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::Url, offsetof(QContactGlobalPresencePrivate, m_presenceStateImageUrl) },
^
details/qcontactdetails.cpp:3042:86: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:3043:89: warning: invalid access to non-static data member ���QtContacts::QContactGlobalPresencePrivate::m_customMessage��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactGlobalPresencePrivate, m_customMessage) },
^
details/qcontactdetails.cpp:3043:89: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:3243:89: warning: invalid access to non-static data member ���QtContacts::QContactExtendedDetailPrivate::m_name��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::String, offsetof(QContactExtendedDetailPrivate, m_name) },
^
details/qcontactdetails.cpp:3243:89: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:3244:90: warning: invalid access to non-static data member ���QtContacts::QContactExtendedDetailPrivate::m_data��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::Variant, offsetof(QContactExtendedDetailPrivate, m_data) },
^
details/qcontactdetails.cpp:3244:90: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:3323:79: warning: invalid access to non-static data member ���QtContacts::QContactVersionPrivate::m_sequenceNumber��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::Int, offsetof(QContactVersionPrivate, m_sequenceNumber) },
^
details/qcontactdetails.cpp:3323:79: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp:3324:85: warning: invalid access to non-static data member ���QtContacts::QContactVersionPrivate::m_extendedVersion��� of NULL object [-Winvalid-offsetof]
{ QContactDetailBuiltinPrivateBase::ByteArray, offsetof(QContactVersionPrivate, m_extendedVersion) },
^
details/qcontactdetails.cpp:3324:85: warning: (perhaps the ���offsetof��� macro was used incorrectly) [-Winvalid-offsetof]
details/qcontactdetails.cpp: In static member function ���static QtContacts::QContactDetailPrivate* QtContacts::QContactDetailPrivate::construct(QtContacts::QContactDetail::DetailType)���:
details/qcontactdetails.cpp:3524:60: error: ���QContactSyncTargetPrivate��� does not name a type
case QContactDetail::TypeSyncTarget: return new QContactSyncTargetPrivate;
^
details/qcontactdetails.cpp: At global scope:
details/qcontactdetails.cpp:3581:1: error: ���QT_WARNING_POP��� does not name a type
QT_WARNING_POP /* -Winvalid-offsetof */
^
details/qcontactdetails.cpp: In member function ���QString QtContacts::QContactSyncTarget::syncTarget() const���:
details/qcontactdetails.cpp:141:1: warning: control reaches end of non-void function [-Wreturn-type]
}
^
Makefile:2323: recipe for target '.obj/qcontactdetails.o' failed
make[2]: *** [.obj/qcontactdetails.o] Error 1
make[2]: Leaving directory '/home/edgex004/Downloads/qtpim2/qtpim-dev/src/contacts'
Makefile:47: recipe for target 'sub-contacts-make_first-ordered' failed
make[1]: *** [sub-contacts-make_first-ordered] Error 2
make[1]: Leaving directory '/home/edgex004/Downloads/qtpim2/qtpim-dev/src'
Makefile:44: recipe for target 'sub-src-make_first' failed
make: *** [sub-src-make_first] Error 2

I'll keep trying to figure that one out.

Would the easiest course of action for removing that dependancy be to remove it from the .pro and comment out the include and namespace lines? Then basically try to compile and comment out any lines the compiler complains about?

EDIT: Slowly working my way through the output of compiling qtpim. Looks like the offsetof warnings can be explained by the following comment from qcontactdetails.cpp:

/* We use offsetof to determine the offset to member fields
* in each builtin detail type private class.
* This is technically undefined behavior according to the
* CPP98 spec, as the classes in question are non-POD.
* However, they do not have any virtual functions, nor any
* private or protected non-static data, nor do they use
* multiple inheritance or virtual inheritance otherwise.
* As such, all modern compilers do implement the class
* layouts as if they were POD, and the offsetof macro
* does indeed work in our case. */
Click to expand...

Moving on to the first error:
details/qcontactdetails.cpp:68:1: error: ���QT_WARNING_PUSH��� does not name a type
QT_WARNING_PUSH
^
Click to expand...

At first I thought QT_WARNING_PUSH wasn't defined, but a google search showed that QT_WARNING_PUSH and QT_WARNING_DISABLE_GCC("-Winvalid-offsetof") are probably defined together in qcompilerdetection.h. If that is the case, then on would think that line 69 should get the same error as well.
 
Last edited:
edgex, not directly on the topic but do you find a pebble watch useful in general ? What do you usually use it for yourself ?
This is coming from someone who has dropped wrist watches for like... 15 years or so. I'm genuinely curious.
 
edgex004 said:
I still want to try to figure out how to pair with the new firmware anyway though.
Click to expand...
This may be a lost cause. Pebble Time has a BT4.0 chip, the newer firmwares may have started using it that way. I don't know if the Pandora's old Bluetooth would try and fail in such a case, as you're seeing, or if it just wouldn't work at all.
 
@ekianjo: I actually stopped using it for a year or two because the battery kept draining and there were not many useful apps. Recently I realized it was draining because I was using the "shake backlight on" feature and it was lighting up over and over as I was biking. Turning this off greatly extended battery life.

I picked it up again after my wife and I started wearing fitbits that were given to us as a gift. I realized I like having steps/time on my wrist but really missed the music control/notifications features of the pebble, so I looked into all the apps that have come out over the years and decided to try the pebble out again.

So here's my uses at the moment:

1. I'm a bike commuter in Minnesota. One winter morning can be 10F and the next -15F. I always have to check the weather when I wake up to know how many layers to wear. Having it on my wrist is convenient and helps me focus on something as I'm trying to wake up. This goes well with gentle wake apps for me.
2. I replaced the Fitbit with my pebble. Sleep tracking, pedometer, etc. wrist pedometers will never be 100% accurate, but I've noticed that they tend to give consistent results when averaged across the day or longer activity.
3. Gentle wake apps are nice.
4. Music control while biking. Especially handy when playing music through a Bluetooth speaker. Some speakers don't have control buttons on them, and neither do most wired headphones. Even if they do, it's nicer to have the buttons on my handlebars.
5. Notifications, email, sms, call answering from watch. Useful for me on or off the bike.
6. Gps notification pushing for directions while biking. Some of the apps have pictures of the turn, which i like a lot. Without this I have to resort to listening for the audio notifications, which can be confusing as the bike directions are still pretty immature. They'll tell you "turn right" when they really mean "turn right then quickly left in order to hop on this bike friendly sidewalk." I hope to get something working for this for Pyra.

There is probably more I'm not listing, but these are at least my favorite features at the moment.

@WizardStan: I think you are probably right. However I believe pairing and some form of communication could still be possible. When pairing with your phone, the pebble app first performs a normal pair and then asks if you'd like to perform a low-energy pair. I think some features are forced to go through the LE connection though, such as notifications. Also I communicated with someone who was pairing their raspberry pi to the pebble, and they mentioned that they were able to normally pair to the new firmware through Bluez4, but that they couldn't do a LE pair until they upgraded to Bluez5.
 
Last edited:
Interesting.
Well, as a Pebble Time owner I'll be closely watching this. I plan to replace my phone with a Pyra and hope it'll work as well.
I can't guarantee I'll be of much help but I can try, if there's anything specific you'd like me to try.
 
WizardStan said:
Interesting.
Well, as a Pebble Time owner I'll be closely watching this. I plan to replace my phone with a Pyra and hope it'll work as well.
I can't guarantee I'll be of much help but I can try, if there's anything specific you'd like me to try.
Click to expand...

Well, if you wouldn't mind trying the following, I'd love to know what happens on the Pebble Time:
1. Turn off bluetooth on any devices your Pebble is already paired with.
2. Make Pebble discoverable.
3. Turn on bluetooth on Pandora and use the bluetooth applet to "Set up new device".
4. Select Pebble and try to pair using default settings.

I especially would like to know if a paring request shows up on the Pebble, even if paring fails.

I don't expect pairing will work, but I'm hoping there is a chance. On 2.x firmware, it can sometimes be difficult to pair ( pressing the response button quickly seems to work), but I at least get a pairing notification on the Pebble. On the 3.x firmware I wasn't even getting a notification prior to the Pandora telling me it failed.

If you could send me your dmesg so I can compare it to what my output looks like after a successful pair, that may help too.

Honestly I need to try upgrading to 3.x firmware and do some more testing myself too. I just don't want to have to borrow an Android phone if I end up needing to downgrade back again.
 
So I tried upgrading to the 3.X pebble firmware and investigating the pairing issue. dmesg did not seem to output anything relevant on the failed pairings. Running the bluetooth-wizard from a terminal also gave no additional information.

I downloaded the source for our version of Bluez (4.99) and tried some of the command line tools that aren't provided by opkg (such as simple-agent) and this also gave nothing helpful. Every time I try to pair, the Pandora immediately exits with a "pairing failed" or "authentication failed" type message.

I went back to the conversation I had with another Pebble user who said they were able to pair with 3.X firmware and noticed they were using Bluez version 4.101, which is the most up to date version of Bluez4. I looked into compiling/installing, but this required that our D-Bus version be greater than 1.4.

So I compiled and installed D-Bus version 1.4.20, and after that was able to install Bluez 4.101.

Unfortunately, after rebooting the system, nub/touchscreen/keyboard input no longer work. Oddly, the Pandora button brings up the XFCE menu, but that's about all I can get.

I did receive a warning during the D-Bus "make install" that I thought might be important, but forgot to write it down. The warning concerned permissions to a certain file or folder and it mentioned that if I wanted certain permissions set for the file, I would need to do it manually. (I think it said I might want to set permissions to "root 4702" or something along those lines)

@notaz: I hate to ask, but do you have any idea what I may have broken? Or maybe advice on if it is even possible to safely install D-Bus version 1.4.x?

I'm thinking that maybe the Pandora key is being mapped at a hardware or system wide level, and the other inputs are set at a user level. Therefore, I should have set up some form of user level bus creation permissions when I upgraded D-Bus.

Luckily I only broke a version of SZ installed to an SD card that I use specifically for testing out this sort of thing. I can easily reinstall it to fix everything and maybe try upgrading D-Bus again and posting the specific warning I encountered.

EDIT: This site suggests that when installing D-Bus, you should not only perform "make install", but also "
make install DESTDIR=/home/export/rootfs". Not sure if this is only for cross compiling, or if I should have done this even when compiling/installing natively.

EDIT2: Maybe I could try this... Hmm though I'm not sure this is relevant since we don't use GDM.

EDIT3: Looks like I no longer have a /var/run/dbus/ folder either.
 
Last edited:
edgex004 said:
@notaz: I hate to ask, but do you have any idea what I may have broken? Or maybe advice on if it is even possible to safely install D-Bus version 1.4.x?
Click to expand...
No idea, sorry. It's exactly the reason I updated bluez to 4.99 instead of 4.101 - to avoid touching dbus, which I felt was very risky.

Try looking at /var/log/slim.log if you haven't already - sometimes messages go there for some reason. Maybe syslog `logread` will output something too.
 
notaz said:
Maybe syslog `logread` will output something too.
Click to expand...


Any idea how I can get this? Since I have no form of input, is there a way I can start SSH or something at boot time?

EDIT: Also I found out what that permissions warning was about from this site:

If you are using a DESTDIR install, dbus-daemon-launch-helper needs to be fixed afterwards. Issue, as root user:

chown -v root:messagebus /usr/libexec/dbus-daemon-launch-helper &&
chmod -v 4750 /usr/libexec/dbus-daemon-launch-helper
Click to expand...
 
Last edited:
edgex004 said:
Any idea how I can get this? Since I have no form of input, is there a way I can start SSH or something at boot time?
Click to expand...
There is a dropbear option in ED's startup options somewhere in Settings, but I guess it's too late to use that. If you can edit your rootfs, you could try making a symlink to /etc/init.d/dropbear from /etc/rc5.d/ .
 
Hi!

I'm also using a Pebble Time (which replaced my classic). My smartphone is there only as support for the pebble... and I would gladly replace most of my use of the smartphone with my Pandora if it were able to talk to the Pebble. I also commute by cycling and being able to control my music is one of the main uses of the Pebble.

My Pandora, however, is running Debian.

Next week I should have some time and I will try to see how far I get using all of the above.

Thank you.
 
@eric: Feel free to try pairing the Pandora to your Pebble. I'm interested to see how the Time responds to pairing attempts. Have you been able to get bluetooth working in Debian? I hadn't seen that happen yet.

I'm trying to figure out how to set up ssh through mini-USB and dropbear in order to investigate my DBus problems. So I think I need two things:

1. @notaz, do you happen to know the startup script I need to symlink to in order to start OTG port at boot?

2. Using my working NAND install of SZ, I am trying to figure out how to SSH to the pandora over the OTG port. I seem to be getting "No DHCPOFFERS received" when I try to run "sudo dhclient usb0". This seems to be the same problem @ZXDunny was having in this thread: https://pyra-handheld.com/boards/threads/usb-networking.59842/#entry20440

I was able to follow @WizardStan's instructions from the thread just fine, but get that error nonetheless.

Did you ever figure out your issue ZXDunny?
 
I just use static usb0 network config in /etc/network/interfaces , the kernel module is g_cdc which is autoloaded by the kernel (I think?).
 
edgex004 said:
@eric: Feel free to try pairing the Pandora to your Pebble. I'm interested to see how the Time responds to pairing attempts. Have you been able to get bluetooth working in Debian? I hadn't seen that happen yet.
Click to expand...

I will try this week hopefully. But to warn you, I've never successfully used bluetooth in Debian... so I'm not particularly optimistic. :(
 
notaz said:
I just use static usb0 network config in /etc/network/interfaces , the kernel module is g_cdc which is autoloaded by the kernel (I think?).
Click to expand...

This is killing me. I had a glimmer of hope a few moments ago. I somehow got ssh running using the 'sudo dhclient usb0' along with what I understand to be an auto assigned IP.

However, upon restarting to see if I could get it to work automatically at startup, I seem to have destroyed my routing table.

The static method is currently not working for me from what I can tell. The static IP is being set at startup now that I uncommented the static usb0 section of /etc/network/interfaces and use the deault IP of 10.0.1.3, but now when I attempt to ping, I get "connect: Network is unreachable" until I run "sudo /sbin/route add default gw 10.0.1.3".

Also, now 'sudo dhclient usb0' no longer seems to work. It exits with 'No DHCPOFFERS received' and removes the static IP from usb0 on the Pandora. Then ping attempts once again error out with "connect: Network is unreachable" because the default gateway is set to the static IP which no longer is assigned.

I might need to install another clean OS to an SD card and try again from there if I can't figure out what I broke here...

I did run "sudo iptables -A INPUT -p tcp --dport ssh -j ACCEPT" in an attempt to open port 22 to ssh. Maybe that is what broke everything.

EDIT: Well I figured out my problem with 'sudo dhclient usb0'. I was not manually initiating a connection request from the desktop. While the Pandora was waiting for a DCHPOFFER, I used network manager on the desktop to connect to usb0, and the connection went through. So now I can create a connection with auto IPs, however this won't let me SSH into my broken development OS until I can figure out how to do this at start up and define a static IP that my desktop can use for SSH.

Is there a way I can spawn a terminal at startup that will first run 'sudo dhclient usb0' so I can attempt to connect from the desktop, and then have it run ifconfig so I can view the IP address and us that to SSH?
[doublepost=1459706393,1459703265][/doublepost]Okay I am a dummy. Got static to work with my NAND OS. I just needed to enter in a manual IP on the desktop in network manager instead of using the "shared to other computers" option. After that, initiating the connection from network manager in the desktop works perfectly fine. I think I was just trying to mix methods.

Next step will be seeing if I can do all this with the borked OS.

There are a couple of patches that angstrom applies to their version of dbus. Maybe I shoul have applied those before compiling the new version of dbus from source.
[doublepost=1459713224][/doublepost]Haha and now of course it is not working again. No idea why. I am not very good at figuring out SSH apparently.

EDIT:
Okay, so I figured out that I need to run "sudo /sbin/route add default gw 10.0.1.3" at startup on the Pandora. Without this, but depending on connection method, I was able to ping from the Pandora to the desktop and get a response, and a ping could be sent from the desktop to the Pandora, but the packets were dropped and no response was received.

Trying this now:
http://raspberrypi.stackexchange.co...to-make-a-change-to-the-routing-table-persist

Okay I finally got SSH working over USB. I put a spoiler around all my confused posts where I could not figure out what was going on. If anyone else borks their system and needs to SSH in, I've broken down how I did it with instructions even an idiot like me could follow.

1. You need access to the root file system. My broken OS is installed to an SD, and my root file system is installed to a partition called "ROOT" on the card. My root filesystem therefore gets mounted to "/media/ROOT/" when I put the SD into the Pandora. The stuff that needs to be modified lives in /etc/ of the root file system, so when I mount my SD, I need to be able to navigate to "/media/ROOT/etc/".

2. If you do not already have dropbear set to start on boot, add a symlink that will run the dropbear start script at boot. A symlink to "../init.d/dropbear" has to be created in <root_file_system>/etc/rc5.d. This is the symlink I created:
Code: 
sudo ln -s "../init.d/dropbear" /media/ROOT/etc/rc5.d/S10dropbear
From what I understand, the "S10" at the start of the symlink helps determine boot order.

3. Uncomment the auto usb0 section of <root_file_system>/etc/network/interfaces.

For me:
Code: 
sudo mousepad /media/ROOT/etc/network/interfaces
and then removing the pound signs for the following lines:
Code: 
#auto usb0
#    address 10.0.1.3
#    netmask 255.255.255.0
Also add an additional line that will set the usb0 interface as our default gateway, making the section look like:
Code: 
auto usb0
    address 10.0.1.3
    netmask 255.255.255.0
    up route add -net 0.0.0.0 netmask 0.0.0.0 gw 10.0.1.3 dev usb0

4. Boot to the borked OS. I do that by inserting the SD with the OS on it into the left slot on the Pandora.
5. Connect the Pandora's mini USB to your desktop. On my desktop, it appears as a "Wired Connection". If a new connection does not show up when you plug in your Pandora, something is wrong, so go back over the first few steps if possible.
6. On the desktop, set a static IP for the connection that shows up when you connect your Pandora. I select "Edit" > "IPv4 settings" > select "Manual" > "Add" Address. I used the following for my connection:
Address: 10.42.0.1
Netmask: 255.255.255.0
Gateway: 10.42.0.1
6. After you have saved this manual setting, select the connection in your network manager applet (if you use one) in order for it to restart the connection attempt. It should use the manual settings now and connect momentarily.
7. You should now have a connection to the Pandora and can ping between the Pandora and desktop. You can then SSH as normal. Using the default usb0 IP from above works for me:
Code: 
ssh edgex004@10.0.1.3
[doublepost=1459723764][/doublepost]@notaz: I have the contents of /var/log/slim.log:

/usr/bin/xauth: creating new authority file /var/run/slim.auth


slim: waiting for X server to begin accepting connections
X.Org X Server 1.7.7
Release Date: 2010-05-04
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.2.0-4-amd64 x86_64
Current Operating System: Linux edgex004-openpandora 3.2.78 #1162 Sun Feb 28 04:00:39 EET 2016 armv7l
Kernel command line: root=/dev/mmcblk0p3 rw rootwait vram=6272K omapfb.vram=0:3000K mmc_core.removable=0
Build Date: 24 July 2014 12:50:34AM

Current version of pixman: 0.32.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sun Apr 3 15:50:53 2016
(==) Using config file: "/etc/X11/xorg.conf"
.
/usr/bin/xauth: creating new authority file /home/edgex004/.Xauthority
stdin: is not a tty
/usr/bin/startxfce4: X server already running on display :0.0
xrdb: "Xft.hinting" on line 9 overrides entry on line 6
xrdb: "Xft.hintstyle" on line 11 overrides entry on line 7
_IceTransmkdir: ERROR: euid != 0,directory /tmp/.ICE-unix will not be created.
Should load Toggle WIFI
Should load TV-Out settings
Should load Toggle Bluetooth™
Should load Toggle USB-host
Should load USB Mass storage
Should load CPU speed
xfdesktop[2007]: starting up
Found plugin 'USB Mass storage'

(Thunar:2005): thunar-vfs-WARNING **: Failed to connect to the HAL daemon: Failed to connect to socket /usr/var/run/dbus/system_bus_socket: No such file or directory
Found plugin 'Toggle Bluetooth™'
Found plugin 'CPU speed'
Connecting to system bus failed: Failed to connect to socket /usr/var/run/dbus/system_bus_socket: No such file or directory
Found plugin 'TV-Out settings'

** (bluetooth-applet:2021): CRITICAL **: dbus_g_proxy_new_for_name: assertion 'connection != NULL' failed

** (bluetooth-applet:2021): CRITICAL **: dbus_g_proxy_add_signal: assertion 'DBUS_IS_G_PROXY (proxy)' failed

** (bluetooth-applet:2021): CRITICAL **: dbus_g_proxy_connect_signal: assertion 'DBUS_IS_G_PROXY (proxy)' failed

** (bluetooth-applet:2021): CRITICAL **: dbus_g_proxy_new_for_name: assertion 'connection != NULL' failed

** (bluetooth-applet:2021): CRITICAL **: dbus_g_proxy_add_signal: assertion 'DBUS_IS_G_PROXY (proxy)' failed

** (bluetooth-applet:2021): CRITICAL **: dbus_g_proxy_connect_signal: assertion 'DBUS_IS_G_PROXY (proxy)' failed

** (bluetooth-applet:2021): CRITICAL **: dbus_g_proxy_add_signal: assertion 'DBUS_IS_G_PROXY (proxy)' failed

** (bluetooth-applet:2021): CRITICAL **: dbus_g_proxy_connect_signal: assertion 'DBUS_IS_G_PROXY (proxy)' failed

** (bluetooth-applet:2021): CRITICAL **: dbus_g_proxy_add_signal: assertion 'DBUS_IS_G_PROXY (proxy)' failed

** (bluetooth-applet:2021): CRITICAL **: dbus_g_proxy_connect_signal: assertion 'DBUS_IS_G_PROXY (proxy)' failed

** (bluetooth-applet:2021): CRITICAL **: dbus_g_proxy_call: assertion 'DBUS_IS_G_PROXY (proxy)' failed

** (bluetooth-applet:2021): CRITICAL **: dbus_g_proxy_call: assertion 'DBUS_IS_G_PROXY (proxy)' failed
Found plugin 'Toggle USB-host'
Found plugin 'Toggle WIFI'
Texas module LMP version : 0x03
Texas module LMP sub-version : 0x1126
internal version freeze: 38
software version: 2
chip: brf6300 (4)
Could not open firmware file /etc/firmware/brf6300.bin: No such file or directory (2).

** (nm-applet:2017): WARNING **: <WARN> bus_init(): Could not get the system bus. Make sure the message bus daemon is running! Message: Failed to connect to socket /usr/var/run/dbus/system_bus_socket: No such file or directory


** (nm-applet:2017): CRITICAL **: nm_remote_settings_system_new: assertion 'bus != NULL' failed

** (nm-applet:2017): CRITICAL **: nm_settings_service_export: assertion 'priv->bus != NULL' failed

** (nm-applet:2017): CRITICAL **: dbus_g_proxy_call: assertion 'DBUS_IS_G_PROXY (proxy)' failed

** (nm-applet:2017): WARNING **: <WARN> request_name(): Could not acquire the NetworkManagerUserSettings service.
Error: (-1) (unknown)


(nm-applet:2017): GLib-GObject-CRITICAL **: object NMApplet 0x7e040 finalized while still in-construction

(nm-applet:2017): GLib-GObject-CRITICAL **: Custom constructor for class NMApplet returned NULL (which is invalid). Please use GInitable instead.

(xfdesktop:2007): thunar-vfs-WARNING **: Failed to connect to the HAL daemon: Failed to connect to socket /usr/var/run/dbus/system_bus_socket: No such file or directory
Opening firmware file: /etc/firmware/brf6300.bin
Device setup complete
Can't init device hci0: Connection timed out (110)

EDIT: So it seems like the upgraded version of dbus does not want to start. So I thought I'd try to stop/start dbus (logged in as root):

Code: 
edgex004-openpandora:~# /etc/init.d/dbus-1 start
Failed to open "/etc/machine-id": No such file or directory
edgex004-openpandora:~# dbus-uuidgen > /etc/machine-id         
edgex004-openpandora:~# /etc/init.d/dbus-1 start
Starting system message bus: dbus.
Starting Hardware abstraction layer hald
run-parts: /etc/dbus-1/event.d/20hal exited with code 1

So at first it was maybe a machine-id issue. I created the machine id and at this point hald doesn't want to start. Maybe I need to upgrade hald? We will see. I will maybe next try to start/stop hald, then after that I will see if there is a way to get more explicit output from the dbus-1 script. I have not yet gotten the syslog command to work. Probably need to opkg install that.
 
Last edited:
I don't own a Pebble but a friend (a really good friend of mine) have created a nice app for android that use the Pebble microphone (so not for Pebble classic sorry) to dictate events to a previously selected smartphone calendar.
It's called Colloquium and is available ONLY IN ITALIAN (for now) but a french and english versions should follow (if there is some interest).

More info here http://rbnet.it/blog/colloquium/


Here is a video for instructions to use (in italian)



sorry for the little derailing..but i think Pebble users maybe like it
 
Last edited:
I would be up for this! I don't have a pebble, but I've wanted one since the kickstarter.
 
You must log in or register to reply here.

Similar threads

Wrath Of Khan
What software/emulators are in development for the Pyra?
2 3
Replies
54
Views
13K
bzar
bzar
ible
e-ink sheet music thingamabob
Replies
7
Views
5K
sm0kew0n
S
M
OpenPandora and smartwatches
Replies
8
Views
3K
mstn
M
klapse
Using the Pandora as my Primary Music Player
Replies
13
Views
4K
sebt3
sebt3
L
Control pandora with android-phone for music-playback. Possible?
Replies
11
Views
5K
lomaxx
L
Back
Top