Re: [SailfishDevel] QGeoSatelliteInfoSource in Sailfish

2014-02-02 Thread Aaron McCarthy
Hi,

On Sat, 1 Feb 2014 10:37:59 christopher.l...@thurweb.ch wrote:
 A slight correction to my previous post
 
 I think that the high number of Sats in View shown on the Jolla means
 that it is showing both GPS and Glonass Satellites, and thus gives a
 figure almost double of that I was used to from the Nokia N9 and
 classic GPS devices.
 
 Comparing various devices I get the following readings:
 
 Sats in use / Sats in View / Device / Technology
 
 6 / 9 / Nokia N9 / GPS only
 
 5 / 20 / Jolla / GPS and Glonass
 
 15 / 21 / Samusung Galaxy Note 3 / GPS and Glonass
 
 9 / Garmin GPSmap 60CSx / GPS only
 
 So the Sats in View figure of the Jolla is plausible.
 
 Interestingly the Jolla's Sats In Use figure - at least in the tests
 on my terrace this morning - is consistently lower than that displayed
 by the other devices. I show 15 for the Galaxy above, but have seen
 readings of 18 and 19.

What are the satellite identification numbers for these satellites. Satellites 
65 to 88 are GLONASS. Others are GPS. Does this match your hypothesis?

Cheers,

-- 
Aaron McCarthy
___
SailfishOS.org Devel mailing list


Re: [SailfishDevel] QGeoSatelliteInfoSource in Sailfish

2014-02-02 Thread christopher . lamb

Hi Aaron

Adding that information proved easier than I had expected: it just  
took a few minutes during breakfast!



void SatInfoSource::onSatsInViewUpdated(const QListQGeoSatelliteInfo  
list) {

int newInView = list.count();
if (newInView != _satsInView) {
qDebug()  satInfoSource.cpp: onSatsinViewUpdated:
QString::number(newInView, 'g', 2);

for (int i = 0; i  newInView; i++ ) {
qDebug()  satsInView: id: 
list[i].satelliteIdentifier()  , system:
list[i].satelliteSystem()  , strength:  + list[i].signalStrength();

}
_satsInView = newInView;
emit satellitesInViewChanged(newInView);
}
}

The for loop is new, and gives the following output.

[D] SatInfoSource::onSatsInViewUpdated:59 - satInfoSource.cpp:  
onSatsinViewUpdated:  23
[D] SatInfoSource::onSatsInViewUpdated:61 - satsInView: id:  1 ,  
system:  0 , strength:
[D] SatInfoSource::onSatsInViewUpdated:61 - satsInView: id:  3 ,  
system:  0 , strength:
[D] SatInfoSource::onSatsInViewUpdated:61 - satsInView: id:  6 ,  
system:  0 , strength:
[D] SatInfoSource::onSatsInViewUpdated:61 - satsInView: id:  11 ,  
system:  0 , strength:
[D] SatInfoSource::onSatsInViewUpdated:61 - satsInView: id:  14 ,  
system:  0 , strength:
[D] SatInfoSource::onSatsInViewUpdated:61 - satsInView: id:  17 ,  
system:  0 , strength:
[D] SatInfoSource::onSatsInViewUpdated:61 - satsInView: id:  19 ,  
system:  0 , strength:
[D] SatInfoSource::onSatsInViewUpdated:61 - satsInView: id:  20 ,  
system:  0 , strength:
[D] SatInfoSource::onSatsInViewUpdated:61 - satsInView: id:  22 ,  
system:  0 , strength:
[D] SatInfoSource::onSatsInViewUpdated:61 - satsInView: id:  27 ,  
system:  0 , strength:
[D] SatInfoSource::onSatsInViewUpdated:61 - satsInView: id:  28 ,  
system:  0 , strength:
[D] SatInfoSource::onSatsInViewUpdated:61 - satsInView: id:  32 ,  
system:  0 , strength:
[D] SatInfoSource::onSatsInViewUpdated:61 - satsInView: id:  74 ,  
system:  0 , strength:
[D] SatInfoSource::onSatsInViewUpdated:61 - satsInView: id:  66 ,  
system:  0 , strength:
[D] SatInfoSource::onSatsInViewUpdated:61 - satsInView: id:  82 ,  
system:  0 , strength:
[D] SatInfoSource::onSatsInViewUpdated:61 - satsInView: id:  73 ,  
system:  0 , strength:
[D] SatInfoSource::onSatsInViewUpdated:61 - satsInView: id:  80 ,  
system:  0 , strength:
[D] SatInfoSource::onSatsInViewUpdated:61 - satsInView: id:  65 ,  
system:  0 , strength:
[D] SatInfoSource::onSatsInViewUpdated:61 - satsInView: id:  88 ,  
system:  0 , strength:
[D] SatInfoSource::onSatsInViewUpdated:61 - satsInView: id:  87 ,  
system:  0 , strength:
[D] SatInfoSource::onSatsInViewUpdated:61 - satsInView: id:  81 ,  
system:  0 , strength:
[D] SatInfoSource::onSatsInViewUpdated:61 - satsInView: id:  67 ,  
system:  0 , strength:
[D] SatInfoSource::onSatsInViewUpdated:61 - satsInView: id:  72 ,  
system:  0 , strength:


Interestingly neither system nor strength give expected output.

Sometimes I get garbled output like:

[D] SatInfoSource::onSatsInViewUpdated:59 - satInfoSource.cpp:  
onSatsinViewUpdated:  21

[D] SatInfoSource::onSatsInViewUpdated:61 - satsInView: id:  1 , system:  0
[D] SatInfoSource::onSatsInViewUpdated:61 - satsInView: id:  3 ,  
system:  0 Updates requested, but no satellite info source available
[D] SatInfoSource::onSatsInViewUpdated:61 - satsInView: id:  6 ,  
system:  0 ates requested, but no satellite info source available
[D] SatInfoSource::onSatsInViewUpdated:61 - satsInView: id:  11 ,  
system:  0 Stop Updates requested, but no satellite info source  
available
[D] SatInfoSource::onSatsInViewUpdated:61 - satsInView: id:  14 ,  
system:  0  Updates requested, but no satellite info source available

[D] SatInfoSource::onSatsInViewUpdated:61 - satsInView: id:  19 , system:  0
[D] SatInfoSource::onSatsInViewUpdated:61 - satsInView: id:  22 ,  
system:  0  requested, but no satellite info source available
[D] SatInfoSource::onSatsInViewUpdated:61 - satsInView: id:  27 ,  
system:  0 ates requested, but no satellite info source available
[D] SatInfoSource::onSatsInViewUpdated:61 - satsInView: id:  28 ,  
system:  0 Stop Updates requested, but no satellite info source  
available



Grüsse

Chris



Zitat von christopher.l...@thurweb.ch:


Aaron

I will have to write some more code to spit out the sat ids to the  
debug console. At the moment my SatInfoSource declarative plugin is  
ultra-simple, it just exposes the numbers of Sats InView and InUse,  
nothing more.


At the moment my hypothesis is based on the circumstantial evidence  
that new newer devices (Jolla and Galaxy) show roughly double the  
number of older GPS only devices (N9, Garmin).


Cheers

Chris

Zitat von Aaron McCarthy aaron.mccar...@jolla.com:


Hi,

On Sat, 1 Feb 2014 10:37:59 christopher.l...@thurweb.ch wrote:

A slight correction to my previous post

I think that the high number of Sats in View shown on the Jolla means
that it is showing both GPS and Glonass Satellites, 

Re: [SailfishDevel] QGeoSatelliteInfoSource in Sailfish

2014-02-01 Thread christopher . lamb

Hi all

A slight correction to my previous post

I think that the high number of Sats in View shown on the Jolla means  
that it is showing both GPS and Glonass Satellites, and thus gives a  
figure almost double of that I was used to from the Nokia N9 and  
classic GPS devices.


Comparing various devices I get the following readings:

Sats in use / Sats in View / Device / Technology

6 / 9 / Nokia N9 / GPS only

5 / 20 / Jolla / GPS and Glonass

15 / 21 / Samusung Galaxy Note 3 / GPS and Glonass

9 / Garmin GPSmap 60CSx / GPS only

So the Sats in View figure of the Jolla is plausible.

Interestingly the Jolla's Sats In Use figure - at least in the tests  
on my terrace this morning - is consistently lower than that displayed  
by the other devices. I show 15 for the Galaxy above, but have seen  
readings of 18 and 19.


Chris




Zitat von christopher.l...@thurweb.ch:


But SatsInView jumps straight to 17 and stays at 17. This figure  
seems less plausible to me.





___
SailfishOS.org Devel mailing list


Re: [SailfishDevel] QGeoSatelliteInfoSource in Sailfish

2014-01-31 Thread Marcel
Hi,

just a small note if everyone else is waiting for this: 
QGeoSatelliteInfoSource is working since Sailfish 1.0.3.8

The only problem here is what the system (GPS/GLONASS) is not set, it is 
QGeoSatelliteInfo::Undefined. But this shouldn't be a real problem to nearly 
all apps.

Greetings,
Marcel

Am Sonntag, 12. Januar 2014 schrieb Marcel mar...@aliquis.de:
 Hi,
 
 I'm trying to get satellite information using QGeoSatelliteInfoSource, but I 
 cannot create a default source. Is it not implemented in Sailfish? I know 
that 
 Sailfish is using Geoclue, and there is a commit in Qt for supporting the 
 Geoclue Satellite interface:
 
 
https://qt.gitorious.org/qt/qtlocation/commit/e09d297894a8b4ff9b06317169b5a9eb97aa7162
 
 Is this missing in the Sailfish-Qt-packages? Is the satellite interface 
 missing in the Sailfish-Geoclue? Is it another problem? Can I access the 
 satellite information in another way?
 
 Another small partly related problem I found then using the GPS is the 
 following: If you use QGeoPositionInfoSource the VerticalAccuracy and the 
 HorizontalAccuracy are always the same, is this normal behaviour?
 
 Greetings,
 Marcel
 ___
 SailfishOS.org Devel mailing list
___
SailfishOS.org Devel mailing list


Re: [SailfishDevel] QGeoSatelliteInfoSource in Sailfish

2014-01-31 Thread christopher . lamb

Hi Marcel

I can confirm that I am getting QGeoSatelliteInfoSource info too.

SatsInUse is changing, before levelling out at 4, which is plausible  
as I am sitting inside.


But SatsInView jumps straight to 17 and stays at 17. This figure seems  
less plausible to me. It maybe down to a bug in my code, but if so I  
have yet to find it. (Tomorrow I will test outside, to see if that  
makes a difference).


mfg

Chris


Zitat von Marcel mar...@aliquis.de:


Hi,

just a small note if everyone else is waiting for this:
QGeoSatelliteInfoSource is working since Sailfish 1.0.3.8

The only problem here is what the system (GPS/GLONASS) is not set, it is
QGeoSatelliteInfo::Undefined. But this shouldn't be a real problem to nearly
all apps.

Greetings,
Marcel

Am Sonntag, 12. Januar 2014 schrieb Marcel mar...@aliquis.de:

Hi,

I'm trying to get satellite information using QGeoSatelliteInfoSource, but I
cannot create a default source. Is it not implemented in Sailfish? I know

that

Sailfish is using Geoclue, and there is a commit in Qt for supporting the
Geoclue Satellite interface:



https://qt.gitorious.org/qt/qtlocation/commit/e09d297894a8b4ff9b06317169b5a9eb97aa7162


Is this missing in the Sailfish-Qt-packages? Is the satellite interface
missing in the Sailfish-Geoclue? Is it another problem? Can I access the
satellite information in another way?

Another small partly related problem I found then using the GPS is the
following: If you use QGeoPositionInfoSource the VerticalAccuracy and the
HorizontalAccuracy are always the same, is this normal behaviour?

Greetings,
Marcel
___
SailfishOS.org Devel mailing list

___
SailfishOS.org Devel mailing list





___
SailfishOS.org Devel mailing list


Re: [SailfishDevel] QGeoSatelliteInfoSource in Sailfish

2014-01-12 Thread Marcel
Hi Chris,

Thanks for the quick response on a sunday... I've already seen that there is 
no GPS in the Emulator, but since Friday I have my own Jolla device :)

As first project I'm trying to create a simple app showing the GPS infos 
similiar to GPS Info Qt on Symbian.

QML PositionSource (and in C++ QGeoPositionInfoSource) is working without 
problems on my real device (besides the accuracies are the same as stated in 
my first mail), so I can access the hardware, but there seems to be something 
missing for the SatelliteInfoSource.

Greetings,
Marcel

Am Sonntag, 12. Januar 2014 schrieb christopher.l...@thurweb.ch:
 Hoi Marcel
 
 Good to see a fellow Sailfish GPS hacker at work.
 
 I am fighting with PositionSource (in QML), but have not got as far as  
 SatelliteInfoSource on a real device - but I hope to soon, as the app  
 I am porting has a C++ plugin to expose SatelliteInfoSource to QML.
 
 You don't state what target you are using.
 
 If your target is the Emulator, then I don't think you will be able to  
 get SatelliteInfoSource working. Evidently the Emulator has no real  
 GPS hardware, and as far as I know there is not (yet) a working  
 simulator plugin that would provide SatelliteInfoSource.
 
 You should find a thread on this topic in this mailing-list from  
 around Christmas time.
 
 Grüsse
 
 Chris
 
 
 Zitat von Marcel mar...@aliquis.de:
 
  Hi,
 
  I'm trying to get satellite information using QGeoSatelliteInfoSource, but 
I
  cannot create a default source. Is it not implemented in Sailfish? I  
  know that
  Sailfish is using Geoclue, and there is a commit in Qt for supporting the
  Geoclue Satellite interface:
 
  
https://qt.gitorious.org/qt/qtlocation/commit/e09d297894a8b4ff9b06317169b5a9eb97aa7162
 
  Is this missing in the Sailfish-Qt-packages? Is the satellite interface
  missing in the Sailfish-Geoclue? Is it another problem? Can I access the
  satellite information in another way?
 
  Another small partly related problem I found then using the GPS is the
  following: If you use QGeoPositionInfoSource the VerticalAccuracy and the
  HorizontalAccuracy are always the same, is this normal behaviour?
 
  Greetings,
  Marcel
  ___
  SailfishOS.org Devel mailing list
 
 
 
 
___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] QGeoSatelliteInfoSource in Sailfish

2014-01-12 Thread Aaron McCarthy
Hi,

On Sun, 12 Jan 2014 15:15:13 Marcel wrote:
 I'm trying to get satellite information using QGeoSatelliteInfoSource, but I
 cannot create a default source. Is it not implemented in Sailfish? I know
 that Sailfish is using Geoclue, and there is a commit in Qt for supporting
 the Geoclue Satellite interface:
 
 https://qt.gitorious.org/qt/qtlocation/commit/e09d297894a8b4ff9b06317169b5a9
 eb97aa7162

 Is this missing in the Sailfish-Qt-packages? Is the satellite interface
 missing in the Sailfish-Geoclue? Is it another problem? Can I access the
 satellite information in another way?

Unfortunately, due to a build configuration issue, the satellite interface is 
not available in the current released version. The issue has already been 
fixed and will be released with a future update.
 
 Another small partly related problem I found then using the GPS is the
 following: If you use QGeoPositionInfoSource the VerticalAccuracy and the
 HorizontalAccuracy are always the same, is this normal behaviour?

This is expected behaviour. Only a single accuracy figure is given by the 
hardware and is used as both the vertical and horizontal accuracy.

Cheers,

-- 
Aaron McCarthy
___
SailfishOS.org Devel mailing list


Re: [SailfishDevel] QGeoSatelliteInfoSource in Sailfish

2014-01-12 Thread christopher . lamb

Hi Aaron

Zitat von Aaron McCarthy aaron.mccar...@jolla.com:


Hi,

Unfortunately, due to a build configuration issue, the satellite interface is
not available in the current released version. The issue has already been
fixed and will be released with a future update.



Thanks for the confirmation that this is not yet working and that a  
fix is in the works. Just out of interest of how thinks work, could  
you provide a more detailed explanation of what is missing / broken? I  
am guessing a geoclue provider, but may be way-off.


Cheers

Chris




___
SailfishOS.org Devel mailing list


Re: [SailfishDevel] QGeoSatelliteInfoSource in Sailfish

2014-01-12 Thread Aaron McCarthy
Hi,

On Mon, 13 Jan 2014 08:01:43 christopher.l...@thurweb.ch wrote:
 Zitat von Aaron McCarthy aaron.mccar...@jolla.com:
  Hi,
  
  Unfortunately, due to a build configuration issue, the satellite interface
  is not available in the current released version. The issue has already
  been fixed and will be released with a future update.
 
 Thanks for the confirmation that this is not yet working and that a
 fix is in the works. Just out of interest of how thinks work, could
 you provide a more detailed explanation of what is missing / broken? I
 am guessing a geoclue provider, but may be way-off.

Just a missing BuildRequires in the rpm spec file for Qt Location.

Cheers,

-- 
Aaron McCarthy
___
SailfishOS.org Devel mailing list