On 01/05/17 19:16, Slava Monich wrote:
> Basically, QNetworkAccessManager is sometimes stuck in NotAccessible
> state after switching from mobile data to wifi.
> My theory was that
> configurationChanged, onlineStateChanged and networkSessionStateChanged
> (queued) signals from the past were get
On Monday, May 1, 2017 7:16:34 PM AEST Slava Monich wrote:
> but that didn't quite fix it. It does eliminate one scenario (described in
> the merge request) but there must be something else there. The whole
> connman bearer plugin thing looks generally prone to race conditions, I
> would've done it
s is on topic here. So let's EOD. If there's any change you'll
> see it in the TJC item.
SIP is still on the Jolla roadmap, although I am not aware of the
current status. I think it's a matter of priorities.
--
Lorn Potter
Sensors / Connectivity
Jolla / llornkcor technologi
> On 12 Nov 2015, at 9:50 am, Aaron McCarthy wrote:
>
> Hi,
>
> On Wed, 11 Nov 2015 16:20:11 Alexander Ladygin wrote:
>> I probably didn't make myself clear =(
>> 1) wifi is turned on
>> 2) app is launched, i can download files with QNAM
>> 3) app is still launched, i turn off the wifi (mobile
> On 11 Nov 2015, at 8:09 pm, Lorn Potter wrote:
>
> Hi Alex,
>
> Having tested this, it does seem to be a bug in that when connecting to wlan
I should have specified here when already connected to mobile data and then
connecting to wlan without first disconnecting mobile dat
Hi Alex,
Having tested this, it does seem to be a bug in that when connecting to wlan,
QNAM’s networkAccessibility sometimes will go to NotAccessible, but then go to
Accessible when wlan connects. or sometimes it won’t even go to NotAccessible
then Accessible when wlan is connected.
You should
On 19/06/15 05:07, Fab wrote:
> Hello everybody !
>
> This is my first post (and first SailfishOS app), so be indulgent :)
>
> I try to use SensorGesture within an app for the Jolla. I particularly
> want to use the shake gesture. I import for this QtSensors 5.x.
>
> But "onDetected" signal is neve
Hi Artem,
It depends on if this is for a harbour app or not, as some of the
middleware connectivity stack API is not yet available for harbour apps.
You could (not harbour app) use libconnman-qt, which comes with a qml
API. This is my first choice.
You could use the qml dbus plugin (not sure if
On 5 Dec 2014, at 2:38 am, Alejandro Exojo wrote:
>
> Then I searched a bit in the branch of the mer-qt/qtbase repo. I see you
> don't
> use any mkspec for SailfishOS or Jolla, right? That's where I thought you
> might have it, and where I think it could be. Blackberry sets there the
> QMAK
On 28 Apr 2014, at 11:10 am, Neel wrote:
> Hi,
>
> What do you people think about adding sensors like temperature, humidity,
> pressure etc.? I heard that iOS is doing so already with the next version of
> the mobile devices.
>
> I joined the group just a couple of days back so don't know if
On 29 Apr 2014, at 5:09 am, Peter Pykäläinen wrote:
> Hi,
>
> any idea on how to use QML DeviceInfo on Sailfish?
> I have been searching for a solution to get the event when device screen is
> locked (onLockStatusChanged), but apparently the imports are not working /
> not allowed.
DeviceInfo
On 29 Apr 2014, at 7:08 am, Peter Pykäläinen wrote:
> Just got my app rejected due to:
>
> "sorry for rejecting your update, but it causes too high power consumption.
> It seems that app doesn't go to idle state when device does. How to measure
> power consumption by yourself you can find her
Hi Robin,
I just tested the mag sensor on 1.0.4.20 using a show_magneticflux
example app, which uses QMagnetometer and it seems to be working.
There were some eariler version of sailfish that did not have a working
compass/mag, but these were fixed. Odd that compass works but mag does not.
W
itor(QObject *parent) :
>QObject(parent)
> {
> }
>
> void WifiMonitor::propertyChanged(const QDBusObjectPath &in)
> {
>qDebug() << "DBus signal received";
>qDebug() << "PropertyChanged, ObjectPath: " << in.path();
> }
>
>
> Thanks
> Julius
>
> --
>
> [ Julius Loman ][ l...@kyberia.net ][ http://lomo.kyberia.net ][ icq:35732873
> ]
> ___
> SailfishOS.org Devel mailing list
Lorn Potter
QtSensors/ Connectivity
llornkcor technologies / Jolla Mobile
___
SailfishOS.org Devel mailing list
?
>>
>> The emulator doesn't simulate accelerometer sensors, for this sort of
>> thing your only option is to test on device.
>>
>> Cheers,
>> Mike.
>>
>> ___
>> SailfishOS.org Devel mailing list
>>
>
> ___
> SailfishOS.org Devel mailing list
Lorn Potter
QtSensors/ Connectivity
llornkcor technologies / Jolla Mobile
___
SailfishOS.org Devel mailing list
on to get that kind of information.
>
> Regards,
> Jukka
> ___
> SailfishOS.org Devel mailing list
Lorn Potter
QtSensors/ Connectivity
llornkcor technologies / Jolla Mobile
___
SailfishOS.org Devel mailing list
On 26/11/2013, at 10:26 AM, Matt Austin wrote:
> Hi,
>
> Just a small pedantic question - when referring to Sailfish, should I be
> using:
> 1) "Sailfish"
> 2) "Sailfish OS"
> 3) "SailfishOS"
>
>
> Is there any versioning scheme I should also use when I want to say that my
> app works on "S
On 21/11/13 10:50 PM, Robin Burchell wrote:
Hi Artem,
On Thu, Nov 21, 2013 at 1:41 PM, Artem Marchenko
wrote:
Thanks for the update, Lekku
I, not L :-)
Will the apps violating these rules, but currently approved or submitted and
under QA still work fine for the launch? And will users get pr
I believe the goal for QtLocation to be included with Qt is 5.2
On 04/08/2013, at 2:32 AM, Mario Bob Jelica wrote:
> Hi all,
>
> Seeing how the QTLocation is being (heavily) refactored right now, and not
> part of QT5 at this time, what are all of us who are doing location-aware
> apps to do
19 matches
Mail list logo
