FollowMee Forums   Home    Forums    Active Topics    Search
    Login
FollowMee Forums >> Phone Specific Discussion >> Windows Phone >> Time Interval setting Page of 3
Time Interval setting
Author Topic
wunwinglow


Newbie

Join Date: 2013-05-22
Posts: 1

Posted: 2013-05-26 05:53:56 PM

My Windows Phone only shows interval options from 30 minutes up to 12 hours. How doI set the interval to a shorter interval, say 3 minutes? Thanks in advance! Very useful app, by the way!

wunwinglow

Administrator


Best of the Best


Join Date: 2010-01-27
Posts: 1323

Posted: 2013-05-30 08:20:33 AM

This is not possible. This is the limitation of the windows phone 8 platform. This OS only allows the app to wake up every 30 minutes to obtain location.

flyninja68


Newbie

Join Date: 2013-06-19
Posts: 1

Posted: 2013-06-20 02:41:46 PM

If I were to pay for the upgrade, would this allow me to change the time interval on my Windows 8 Phone or are these limitations very specific to Windows Phones as I believe you suggested? I just wanted to be sure because I really like the app.

Thanks
chris12


Forum Regular


Join Date: 2010-01-27
Posts: 491

Posted: 2013-06-20 06:45:25 PM

The upgrade does not help. This is limited by the WP8 platform.

Gerardo86


Newbie

Join Date: 2013-06-15
Posts: 1

Posted: 2013-06-25 10:15:36 PM

no fix near?
mizuoh


Newbie

Join Date: 2013-07-13
Posts: 5

Posted: 2013-07-13 09:49:44 PM

on Windows Phone 8, it is possible to have a location tracking app run in the background. This should enable updating user's location more frequently.

http://msdn.microsoft.com/en-us/library/windowsphone/develop/jj681691(v=vs.105).aspx

http://msdn.microsoft.com/en-us/library/windowsphone/develop/jj662935(v=vs.105).aspx


" On Windows Phone 8, a location-tracking app can continue to run in the background after the user navigates away, as long as the app continues to actively track location. This feature enables scenarios such as an app that provides turn-by-turn directions."
mizuoh


Newbie

Join Date: 2013-07-13
Posts: 5

Posted: 2013-07-21 05:01:57 PM

Does the information help?
skinnymuch


Newbie

Join Date: 2013-08-09
Posts: 2

Posted: 2013-08-09 07:57:42 PM

mizuoh, i believe that would destroy the battery as it would require continuous location tracking, like it says, "turn-by-turn directions". Also, I'm not sure an app like this using those features would be allowed in the app store.
skinnymuch


Newbie

Join Date: 2013-08-09
Posts: 2

Posted: 2013-08-09 07:59:11 PM

Windows Phone 8 allows background tasks updating location like this app every 20 minutes now right? A number of other location or background task apps I've checked out in the app store do seem to run their task every 20 minutes.

Any chance for an update?
chris12


Forum Regular


Join Date: 2010-01-27
Posts: 491

Posted: 2013-08-10 08:13:59 AM

It is 30 minutes, not 20 minutes. It is in Microsoft's document.

mizuoh


Newbie

Join Date: 2013-07-13
Posts: 5

Posted: 2013-08-30 01:36:12 PM

If you keep location tracking turned on for real time tracking like a turn-by-turn app, then of course you would drain the battery. But, as far as I can tell, with this new feature in Windows Phone 8, you should be able to at least shorten the refresh time to more frequently then 30 minutes. You would need to manage when and how often to get a location lock instead of the 30-minute limit enforced by the OS.

http://msdn.microsoft.com/en-us/library/windowsphone/develop/jj681691(v=vs.105).aspx

http://msdn.microsoft.com/en-us/library/windowsphone/develop/jj662935(v=vs.105).aspx
chris12


Forum Regular


Join Date: 2010-01-27
Posts: 491

Posted: 2013-08-31 12:37:26 PM

This method is completely no use. Though it allows the app to run in the background, it has a time limit of 2 hours. After 2 hours, the user has to open the app, otherwise, the app is killed. This will create a maintenance nightmare for us because users will not understand why the app stops after 4 hours.

Another limitation, this OS allow one background app running at one time. If FollowMee is running and the user wants to listen to music, he cannot do it because the music player app runs in the background.

Another limitation, the app runs in the background but the phone is not completely sleeping. The battery is draining fast and will lead to negative user experience.

Welcome to the WP8 world, a land of limitation!

digital_realms


Newbie

Join Date: 2013-07-21
Posts: 3

Posted: 2013-09-01 08:04:53 AM

Just reading this thread made me think, if any given app on the phone can only wake itself once every 30 minutes, then could it be conceivable that a single app could have the ability to effectively have two parts/processes to it. So for example FollowMee-A and FollowMee-B, one would trigger the other after a given time and both of these parts having the ability to lookup the last update timestamp in order to keep themselves equally offset in time from each other by say 15 minutes. I hope that makes sense, it's little hard to describe-by-type a hypothetical scenario. I don't reckon there would be any real detriment to battery life, if logic dictates.
chris12


Forum Regular


Join Date: 2010-01-27
Posts: 491

Posted: 2013-09-02 11:01:36 PM

This is an interesting theory and I have thought about it some time back. This is called hacking and it is not always working. First, you have to make two identical apps with different times. Will Microsoft approve it? Second, this make the operation of the app more complicated. Most users will not understand the situation and this create a nightmare for the supports.

akkoev


Newbie

Join Date: 2013-08-26
Posts: 3

Posted: 2013-09-09 12:31:09 AM

The interval of 30 minutes is on average. WP8 Will try to sychronize this scheduled task with other tasks. The deviation is up to +/- 10 min I believe. In the end both tasks (A & B) will be synchronized...

chris12


Forum Regular


Join Date: 2010-01-27
Posts: 491

Posted: 2013-09-10 11:07:30 PM

akkoev:

Thank you very much for your clever reasoning. This makes more sense.

   Page of 3 Next »    Last »


  FollowMee.com DMG Forums 3.2