When I was developing my Chrome extension I used the alarms API, and it worked without any issues. After uploading it to the Chrome Web Store, it doesn't trigger at the scheduled times (I am settings timers greater than one minute). I tested with a 5 minute timer, and it took 5 minutes and 47 seconds to trigger. I am considering switching to setting a timeout for the timers, but would prefer to use the alarms API. Below is a screenshot of the scheduled time going over the actual time.
Any ideas on how to fix this?
Related
I keep on typing in the google Colaboratory but it has happened three times now I left for like 2 minutes to check of some other things onto a web browser, at the same time 90 minutes finished and the runtime disconnected, which mean it wasn't idle for 90 minutes, it just disconnects me after 90 minutes anyways. Does it have to do with where I live maybe? India
I had this issue many times due to bad internet, if that's not case switch to GPU runtime and try.
We are using a headless Chrome to take screenshots of our websites. Because on startup there are some animations we set a timeout of 10 seconds before we take the screenshot. We are running all of this on an AWS lambda. It sucks though that we actually have to wait 10 real life seconds. Is there a way to tell (headless) Chrome to fast forward (or "fake") 10 seconds?
This is a Windows Phone 8.1 app. I want to be able to trigger a task to execute at a specific time. My main concerns are accuracy, resource and user experience.
I have tried a TimeTrigger with an IBackgroundTask but found that, aside from the minimum 15 minutes constraint, the execution time is far from accurate - sometime the task triggers 8 minutes later, some times 20 so no use for a scheduled trigger.
I have looked at toast but I need the task to run without user input and, as far as I can see, the toast notifications have no capability to trigger code execution without the user interacting.
I have looked at the alarm clock approach but, firstly it uses toast notifications and, secondly, I understand you can only have one alarm app that the user must declare so that's a bit intrusive.
I have looked at using a Task.Delay approach using async and await to avoid blocking the UI thread but this is hardly a background-centric approach.
Has anyone managed to find a way to create resource-friendly, scheduled background tasks (i.e. an alarm and sleep function) for Windows Phone 8.1?
I'm going to make a simple toast notification using periodic task of background agent, what I'm asking is how can I show deep toast notification in specific time (ex:5 mins). Note: We have used this method ScheduledActionService.LaunchForTest(string name, TimeSpan delay) to check in Emulator.
Is this will work in Device with customized time interval?
Please help me.
Periodic agents typically run every 30 minutes. To optimize battery
life, periodic agents may be run in alignment with other background
processes and therefore the execution time may drift by up to 10
minutes.
http://msdn.microsoft.com/en-us/library/windowsphone/develop/hh202942%28v=vs.105%29.aspx#BKMK_ConstraintsforPeriodicAgents
You can however send a toast via push notification service. You can do that whenever you want.
I'm using Adobe's Google Analytics SWC library for flex. What I'm trying to achieve is to simply be able to utilize the realtime features of Google Analytics to know when users have my AIR desktop application open.
Making it detect an open application was easy enough. I can visually see the count on Google Analytics getting updated in a matter of seconds whenever I open up my application. However, the problem occurs when I close my app. Google Analytics doesn't seem to detect a closed app and still detects it as open on the realtime view. How would I go with making Google Analytics know that the application has stopped?
So far, it seems the realtime counter only reverts back to 0 after some 30 or so minutes that I have already closed the app. This leads me to believe that it was considered to be idle by Google and so decided to update the statistics. That might be good and all but I really want to utilize the realtime capability so I need it to reflect when an app closes with only a few seconds of offset.
Any thoughts?
Not sure if this one will work (don't know that Android will kill the process and restart it each time) but if it does it's an answer:
http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/desktop/NativeApplication.html#event:exiting
Also check out the Deactivate event as it seems to be relevant, more on mobile app life cycle here:
http://help.adobe.com/en_US/air/build/WSfffb011ac560372f82c4ee412b1275403b-8000.html
From the Google Analytics documentation.
setSessionTimeout () method public function
setSessionTimeout(newTimeout:int):void
Sets the new session timeout in seconds. By default, session timeout
is set to 30 minutes (1800 seconds).
Session timeout is used to compute visits, since a visit ends after 30
minutes of browser inactivity or upon browser exit.
If you want to change the definition of a "session" for your
particular needs, you can pass in the number of seconds to define a
new value.
This will impact the Visits reports in every section where the number
of visits are calculated, and where visits are used in computing other
values.
For example, the number of visits will increase if you shorten the
session timeout, and will decrease if you increase the session
timeout.