Re: [SailfishDevel] App rejected...
Thanks Martin, your trick works actually really well. I had to create another timer for the Cover but that is no issue. // Peter Pykäläinen On 29 April 2014 07:23, peter.pykalai...@gmail.com wrote: Thank you. Will have a look at that. martin.gri...@gmail.com kirjoitti Tue Apr 29 2014 07:12:45 GMT+0300 (EEST): Hi, Am Mon Apr 28 2014 23:11:58 GMT+0200 (CEST) schrieb Peter Pykäläinen: Thank you for you response. Unfortunately no, since I need to show info on the cover. I think, for just showing info on the cover, giving the CPU sleep deprivation is overkill. You can make the timer's running property depend on Qt.application.active (app is not minimized and screen is not locked) and the Cover.Active signal of the CoverBackground element (Cover is visible and screen is not locked). I'm watching these two properties in Tidings, for example, to keep the elapsed time labels up to date. Martin -- Gesendet von meinem Jolla ___ SailfishOS.org Devel mailing lis -- // Peter Pykäläinen Lähetetty Jollastani ___ SailfishOS.org Devel mailing list
[SailfishDevel] App rejected...
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 here: https://together.jolla.com/question/13243/my-app-got-rejected-to-store-because-of-high-power-consumption-how-to-debug-problems/ https://together.jolla.com/question/13243/my-app-got-rejected-to-store-because-of-high-power-consumption-how-to-debug-problems/ Thank you for understanding.* I have a QML Timer to monitor some activity in 1 second interval. I have been strugeling to find a way to get Qt5SystemInfo to expose me when the device is locked so I could stop the timer and then start it again when the device is unlocked. Good ideas to overcome this issue are mostly welcome. // Peter Pykäläinen ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] App rejected...
well, just stopping timer when app minimized is not enough? 29.04.2014 03:08, Peter Pykäläinen ?: 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 here: https://together.jolla.com/question/13243/my-app-got-rejected-to-store-because-of-high-power-consumption-how-to-debug-problems/ Thank you for understanding./ I have a QML Timer to monitor some activity in 1 second interval. I have been strugeling to find a way to get Qt5SystemInfo to expose me when the device is locked so I could stop the timer and then start it again when the device is unlocked. Good ideas to overcome this issue are mostly welcome. // Peter Pykäläinen ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] App rejected...
Thank you for you response. Unfortunately no, since I need to show info on the cover. // Peter Pykäläinen On 29 April 2014 00:10, Andrey Kozhevnikov coderusin...@gmail.com wrote: well, just stopping timer when app minimized is not enough? 29.04.2014 03:08, Peter Pykäläinen пишет: 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 here: https://together.jolla.com/question/13243/my-app-got-rejected-to-store-because-of-high-power-consumption-how-to-debug-problems/ https://together.jolla.com/question/13243/my-app-got-rejected-to-store-because-of-high-power-consumption-how-to-debug-problems/ Thank you for understanding.* I have a QML Timer to monitor some activity in 1 second interval. I have been strugeling to find a way to get Qt5SystemInfo to expose me when the device is locked so I could stop the timer and then start it again when the device is unlocked. Good ideas to overcome this issue are mostly welcome. // Peter Pykäläinen ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] App rejected...
I have been strugeling to find a way to get Qt5SystemInfo to expose me when the device is locked so I could stop the timer and then start it again when the device is unlocked. nemo-keepalive (https://github.com/nemomobile/nemo-keepalive) exposes a DisplayBlanking.status property with which you can detect when the device is locked. If you're interested, I've written a custom qmake project file to make it possible to install the plugin to a custom location without having to make any changes to the actual nemo-keepalive project. You can find it here: https://gist.github.com/BeholdMyGlory/9662866. If you want to use it, make sure that you've checked out the nemo-keepalive repository as well as libiphb (https://github.com/nemomobile/libiphb), and place the project file in the directory directly above the two repositories. Then set your main project file to use the subdirs template and add nemo- keepalive.pro to the SUBDIRS variable. Don't forget to substitute PROJECT_NAME_HERE with your own project's name (sans 'harbour-') at lines 8 and 14 in nemo-keepalive.pro as well as the first line in the qmldir file. You may need to install libiphb separately to your build environment in order for some header files to be found properly. Regards, Arvid ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] App rejected...
Thanks Arvid, Will an app using that still pass harbour QA? I just can't believe howcome basic stuff like checking wheter the screen is locked is not available. Arvid Fahlström Myrman kirjoitti Tue Apr 29 2014 00:41:47 GMT+0300 (EEST): I have been strugeling to find a way to get Qt5SystemInfo to expose me when the device is locked so I could stop the timer and then start it again when the device is unlocked. nemo-keepalive (https://github.com/nemomobile/nemo-keepalive) exposes a DisplayBlanking.status property with which you can detect when the device is locked. If you're interested, I've written a custom qmake project file to make it possible to install the plugin to a custom location without having to make any changes to the actual nemo-keepalive project. You can find it here: https://gist.github.com/BeholdMyGlory/9662866. If you want to use it, make sure that you've checked out the nemo-keepalive repository as well as libiphb (https://github.com/nemomobile/libiphb), and place the project file in the directory directly above the two repositories. Then set your main project file to use the subdirs template and add nemo- keepalive.pro to the SUBDIRS variable. Don't forget to substitute PROJECT_NAME_HERE with your own project's name (sans 'harbour-') at lines 8 and 14 in nemo-keepalive.pro as well as the first line in the qmldir file. You may need to install libiphb separately to your build environment in order for some header files to be found properly. Regards, Arvid ___ SailfishOS.org Devel mailing list -- // Peter Pykäläinen Lähetetty Jollastani ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] App rejected...
I haven't tried actually submitting an app using nemo-keepalive to Harbour, but I did pass the RPM validator built into the SDK. As long as the plugin isn't linking to any disallowed libraries and is placed in /usr/share/harbour- projectname/harbour/projectname it shouldn't be breaking any Harbour rules AFAIK. On Monday 28 April 2014 21:47:36 peter.pykalai...@gmail.com wrote: Thanks Arvid, Will an app using that still pass harbour QA? I just can't believe howcome basic stuff like checking wheter the screen is locked is not available. Arvid Fahlström Myrman kirjoitti Tue Apr 29 2014 00:41:47 GMT+0300 (EEST): I have been strugeling to find a way to get Qt5SystemInfo to expose me when the device is locked so I could stop the timer and then start it again when the device is unlocked. nemo-keepalive (https://github.com/nemomobile/nemo-keepalive) exposes a DisplayBlanking.status property with which you can detect when the device is locked. If you're interested, I've written a custom qmake project file to make it possible to install the plugin to a custom location without having to make any changes to the actual nemo-keepalive project. You can find it here: https://gist.github.com/BeholdMyGlory/9662866. If you want to use it, make sure that you've checked out the nemo-keepalive repository as well as libiphb (https://github.com/nemomobile/libiphb), and place the project file in the directory directly above the two repositories. Then set your main project file to use the subdirs template and add nemo- keepalive.pro to the SUBDIRS variable. Don't forget to substitute PROJECT_NAME_HERE with your own project's name (sans 'harbour-') at lines 8 and 14 in nemo-keepalive.pro as well as the first line in the qmldir file. You may need to install libiphb separately to your build environment in order for some header files to be found properly. Regards, Arvid ___ SailfishOS.org Devel mailing list -- // Peter Pykäläinen Lähetetty Jollastani ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] App rejected...
Last time I tried linking to libiphb wasn't allowed, so I made a qml plugin including it instead: https://github.com/tanghus/kitchen-timer-qml/tree/master/src/insomniac Not sure if the harbour rules have changed since that. On Monday 28 April 2014 23:41:47 Arvid Fahlström Myrman wrote: I have been strugeling to find a way to get Qt5SystemInfo to expose me when the device is locked so I could stop the timer and then start it again when the device is unlocked. nemo-keepalive (https://github.com/nemomobile/nemo-keepalive) exposes a DisplayBlanking.status property with which you can detect when the device is locked. If you're interested, I've written a custom qmake project file to make it possible to install the plugin to a custom location without having to make any changes to the actual nemo-keepalive project. You can find it here: https://gist.github.com/BeholdMyGlory/9662866. If you want to use it, make sure that you've checked out the nemo-keepalive repository as well as libiphb (https://github.com/nemomobile/libiphb), and place the project file in the directory directly above the two repositories. Then set your main project file to use the subdirs template and add nemo- keepalive.pro to the SUBDIRS variable. Don't forget to substitute PROJECT_NAME_HERE with your own project's name (sans 'harbour-') at lines 8 and 14 in nemo-keepalive.pro as well as the first line in the qmldir file. You may need to install libiphb separately to your build environment in order for some header files to be found properly. Regards, Arvid ___ SailfishOS.org Devel mailing list -- Best regards / Med venlig hilsen Thomas Tanghus ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] App rejected...
That's why my project file includes libiphb statically when compiling instead of linking to it dynamically. (And also why you have to fetch libiphb in order to build it.) Last time I tried linking to libiphb wasn't allowed, so I made a qml plugin including it instead: https://github.com/tanghus/kitchen-timer-qml/tree/master/src/insomniac Not sure if the harbour rules have changed since that. On Monday 28 April 2014 23:41:47 Arvid Fahlström Myrman wrote: I have been strugeling to find a way to get Qt5SystemInfo to expose me when the device is locked so I could stop the timer and then start it again when the device is unlocked. nemo-keepalive (https://github.com/nemomobile/nemo-keepalive) exposes a DisplayBlanking.status property with which you can detect when the device is locked. If you're interested, I've written a custom qmake project file to make it possible to install the plugin to a custom location without having to make any changes to the actual nemo-keepalive project. You can find it here: https://gist.github.com/BeholdMyGlory/9662866. If you want to use it, make sure that you've checked out the nemo-keepalive repository as well as libiphb (https://github.com/nemomobile/libiphb), and place the project file in the directory directly above the two repositories. Then set your main project file to use the subdirs template and add nemo- keepalive.pro to the SUBDIRS variable. Don't forget to substitute PROJECT_NAME_HERE with your own project's name (sans 'harbour-') at lines 8 and 14 in nemo-keepalive.pro as well as the first line in the qmldir file. You may need to install libiphb separately to your build environment in order for some header files to be found properly. Regards, Arvid ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] App rejected...
On 29 Apr 2014, at 7:08 am, Peter Pykäläinen peter.pykalai...@gmail.com 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 here: https://together.jolla.com/question/13243/my-app-got-rejected-to-store-because-of-high-power-consumption-how-to-debug-problems/ Thank you for understanding. I have a QML Timer to monitor some activity in 1 second interval. I have been strugeling to find a way to get Qt5SystemInfo to expose me when the device is locked so I could stop the timer and then start it again when the device is unlocked. Good ideas to overcome this issue are mostly welcome. Might try using QtDBus to mce like this: https://github.com/nemomobile/connectionagent/blob/master/connd/wakeupwatcher.cpp https://github.com/nemomobile/connectionagent/blob/master/connd/wakeupwatcher.cpp ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] App rejected...
Hi, Am Mon Apr 28 2014 23:11:58 GMT+0200 (CEST) schrieb Peter Pykäläinen: Thank you for you response. Unfortunately no, since I need to show info on the cover. I think, for just showing info on the cover, giving the CPU sleep deprivation is overkill. You can make the timer's running property depend on Qt.application.active (app is not minimized and screen is not locked) and the Cover.Active signal of the CoverBackground element (Cover is visible and screen is not locked). I'm watching these two properties in Tidings, for example, to keep the elapsed time labels up to date. Martin -- Gesendet von meinem Jolla ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] App rejected...
Thank you. Will have a look at that. martin.gri...@gmail.com kirjoitti Tue Apr 29 2014 07:12:45 GMT+0300 (EEST): Hi, Am Mon Apr 28 2014 23:11:58 GMT+0200 (CEST) schrieb Peter Pykäläinen: Thank you for you response. Unfortunately no, since I need to show info on the cover. I think, for just showing info on the cover, giving the CPU sleep deprivation is overkill. You can make the timer's running property depend on Qt.application.active (app is not minimized and screen is not locked) and the Cover.Active signal of the CoverBackground element (Cover is visible and screen is not locked). I'm watching these two properties in Tidings, for example, to keep the elapsed time labels up to date. Martin -- Gesendet von meinem Jolla ___ SailfishOS.org Devel mailing lis -- // Peter Pykäläinen Lähetetty Jollastani ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] App rejected, missing libc.so.6
Hi, thanks for testing! So I don't have to worry about libc anymore and I'll define my next tasks as- correct icon path- load Views dynamically to increase startup time- think about reducing the fields in the game area to make them larger on small devices Thanks!Martin From: jonni.raini...@jolla.com To: devel@lists.sailfishos.org Date: Wed, 13 Nov 2013 06:18:20 + Subject: Re: [SailfishDevel] App rejected, missing libc.so.6 Hi, Few pointers, application installs and starts. desktop file Icon path is wrong so app icon is empty on grid. If you change Icon line to: Icon=/usr/share/icons/hicolor/90x90/apps/morzyn.png Then icon would show up in the grid too. Your startup time is pretty slow so you might want to optimizehunt down bottlenecks in startuptime by using qml debugger. (Or maybe add some splashscreen while application is starting). Its pretty hard to choose player in game area, you might want to think about increasing the size in there, or maybe even add some zooming possibility to game field. re, Jonni From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] on behalf of Martin Windolph [mar...@yoktobit.de] Sent: Tuesday, November 12, 2013 11:13 PM To: Sailfish OS Developers Subject: [SailfishDevel] App rejected, missing libc.so.6 Hi, my game, submitted to Jolla Harbour yesterday, just got rejected for the following reasons: The Installation brought up: error: Failed dependencies: libc.so.6(GLIBC_2.0) is needed by morzyn-0.7.14-1.armv7hl libm.so.6(GLIBC_2.0) is needed by morzyn-0.7.14-1.armv7hl I never had these missing dependencies in the emulator. What am I missing here? The only “non-predefined” Qt things I use (in my opinion) are QT += xml #include time.h Do I have to include some more PkgConfigBR-Entries? I now cleaned up my qmake-File to be as lightweight as in the new template and I found a non-used #include cstdlib in my code, which is now removed. Maybe that was the libc.so-guy? Morzyn is now repackaged, but before resubmitting, I’d like to know if it works now. Could someone with a real device please test if it is installable now? - or just send me a device, then I do it on my own The emulator never had any problems with libc.so.6, so testing there is pointless. The new RPM is located here: http://yoktobit.de/morzyn/downloads/morzyn-0.7.14-1.armv7hl.rpm Thanks! Martin ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
