I have a background service for getting the gps coordinates, from 2 seconds to 2 seconds, this works until I've tryed on Android 8.0 (Oreo). I have research for information on how to do this and I found a lot of people saying to use JobScheduler. But in this situation that I need the service too being executed from 2 seconds in 2 seconds, and long running(until user log out), I have read that the Job scheduler is not the best option.
So, in resume, has anyone got a way/clue of how I can do this to work in Android 8?
Thanks any help.
Related
I have a Google Pro + account and facing problem with working in Google colab. The processing time of my ipynb file normally is 8 hours.
But now, from yesterday it is taking too much time in processing. its more than 25 hours and my process is still not completed.
Runtime is also disconnecting again and again.
My display starts to flicker heavily after / while using eclipse. First i thought this is the common "surface problem", but everything is fine if i don't use eclipse (tested for 3 days.) Just after opening eclipse and using it for 5 mins, the whole screen starts to flicker, making it unable to work with. It flickers in every programm and also on the task manager, even after closing eclipse. It stops if i put the monitor on standby for a couple minutes, then comes back randomly.
Things i work with:
Surface Pro 4,
Windows 10 (current version),
Eclipse Version: 2020-03 (4.15.0)
Things i tried:
Using windows compatibility tool,
checking my current drivers (no update found)
Note: I just started programming and digging into IT stuff. So im far from an experienced user and haven't tried any stuff i cant unterstand (yet).
Please help me out, thanks a lot in advance.
I use gnome shell in Fedora 18 x86_64 on an emachines E725 notebook. For the last month, every 60 seconds the display locks up for 25 seconds. Sometimes it does this for 10 minutes, and sometimes all day. The mouse cursor still moves, and sound still plays without skipping. Also, progress bars jump forward when it unfreezes as they never froze. I have stopped all cron tasks and restarted many times. The exact second the clock stops on varies each time I restart the system. I have also noticed a small increase in network use right before it freezes. It sometimes starts freezing before I open any apps, and it still freezes after I close all apps. Please let me know if there is any additional information I should post. I have done many convoluted google and stackoverflow searches over a long period of time and have found no similar problems posted. Thank you for any help or advice.
Probably off topic, but I'd suggest trying a CD/USB linux distribution (i.e. one that runs off the CD rather than having to install it).
If that has problems, you are probably looking at a hardware issue.
If a CD distribution works, then yep, it's something wrong with your installation.
I just read that while Windows Phone 7.5 background tasks can poll for a location, they don't actually poll real-time from the GPS but rather the location API calls return a system-cached position that's only updated once every fifteen minutes.
That limitation of course completely invalidates any attempt at having navigation run in the background as you can get pretty damn far off-track in fifteen minutes, let alone that a background task can only run once every thirty minutes or so!
That said, Nokia's navigation app and reportedly Runtastic's app do continue tracking when in the background (i.e. not just under the lock screen) and both are in the marketplace meaning they have been approved, so does anyone know how they managed to do what the SDK supposedly doesn't support?
For reference, we don't actually need real-time tracking... maybe once a minuted or so, and we don't need that much accuracy... maybe 100 feet or so... but we do need more than we have been given. We just don't know how they're doing it in approved apps.
You'll only be able to retrieve the location when your PeriodicTask executes (Approximately every ~30 minutes, depending on OS scheduling). The location data it fetches from GeoCoordinateWatcher will be from the OS's cache rather than directly from the GPS hardware. If nothing is running the OS will update this with coarse-grained data approximately every 15 minutes. However if an application has executed and retrieved fine-grained GPS hardware data than this will be the data you'll retrieve in your PeriodicTask. You can see examples of this by accessing the GPS in your foreground app and force-scheduling your PeriodicTask with ScheduledActionService.LaunchForTest.
Based on my experience with background tasks, you will not be able to achieve what you want with either Periodic or ResourceIntensive background tasks.
Despite documentation claiming that they run every 30 minutes, my experience is that they run sporadically and unpredictably. Over the last 14 hours, my app's periodic task has run a total of 6 times, and this is pretty consistent every day - it runs about once every two hours. For resource intensive tasks, I find they usually run about twice a night. I guess the OS has to balance all the processes on the phone and all the other apps clamoring to run their background tasks, so sometimes yours doesn't make the cut. Obviously, your mileage may vary based on your phone (lumia 800 in my case) and the apps you have installed.
If you want to write an app that tracks your location once a minute, my advice would be to enable it to run under the lock screen by disabling idle detection and make sure it has a low memory footprint to conserve battery life.
In other words, Windows starts up, and my application xyz.exe, is started at exactly 5 minutes after boot up. Is this possible to guarantee, within a margin of error of say 10-15 seconds?
It will probably be easier just to launch your app at windows startup and then sleep for 5 minutes before doing anything.
You can programtical modify a scedlued task after bootup or login to start your program.