I am using Android-x86 6.0 on VirtualBox. Since I have changed the screen resolution using the method described here: https://stackoverflow.com/a/8273560/6110243 Android restarts whenever an open app is exited through the home or back button. This happens for every application, system apps and user apps. I can still use the back button to navigate within an application, but once the back button closes the app it instantly shows the "android" logo and boots back up.
I suspect it might be because my battery level always shows "0%" (and charging) and it somehow triggers a shutdown when an app is closed? But that wouldn't explain why it only started happening after I changed the resolution from the standard resolustion to 600x800x32. I have tried to set the Battery level to something higher, but couldn't find any Information on how to do so.
Related
I created a Background Application for Windows IoT Core on a Raspberry Pi 3. It is to become a hub application for a "smart home remote" (Nuimo) which uses BLE GATT to communicate.
The odd thing is that after a short time of running, the application simply stops responding and also drags Visual Studio along. VS then responds very slowly, has trouble detaching from the debugging process, shows "waiting for a background task to complete" dialog. However, no exceptions seem to be thrown (I enabled breaking on all exceptions). This makes it very difficult to find the cause of the problem.
I tried:
removing parts of the application
enabling breaking on all exceptions
combining multiple events coming from the BLE device to prevent flooding the application with events.
Unfortunately none of this helped.
Relevant documentation I read:
https://developer.microsoft.com/en-us/windows/iot/docs/backgroundapplications
https://learn.microsoft.com/en-us/windows/uwp/devices-sensors/bluetooth-dev-faq
https://learn.microsoft.com/en-us/windows/uwp/devices-sensors/gatt-client
https://learn.microsoft.com/en-us/windows/uwp/launch-resume/access-sensors-and-devices-from-a-background-task
Therefore I'm wondering whether anybody could share experience and hints where to look for the issue.
The code is at https://github.com/wind-rider/nuimo-hub and https://github.com/wind-rider/nuimo-windows (too much to post here since I don't know what part the issue is in)
Update: in the process explorer (via Windows Device Portal) I see that suddenly the memory used by the app drops when it stops responding, but its process (backgroundTaskHost.exe) is not immediately gone. It seems that somehow the Background App is unloaded, and that Visual Studio doesn't notice it since the host process is not shut down?
Now - how to know why the task is unloaded?
I assume that a Windows IoT Core background app is a special kind of background task that is not limited by the resource constraints applying to background tasks for "normal UWP apps"? Quote: "Background Applications are applications that have no direct UI. Once deployed and configured, these applications launch at machine startup and run continuously without any process lifetime management resource use limitations." (from https://developer.microsoft.com/en-us/windows/iot/docs/backgroundapplications)
Im using this guide "automating the testing of windows 8 apps" to test my windows store app
http://blogs.msdn.com/b/windowsappdev/archive/2012/09/04/automating-the-testing-of-windows-8-apps.aspx
Unfortunaltely Ive run into a problem, I need to know when my app closes (crashes) or when it goes into suspended mode, to log that info, and I want the launcher to be able to know the application has stopped , unfortunately iApplicationActionManager, does not have that method. And IPackageDebugSettings which is used to change the application suspend and resume states does not have a readable current state property (afaik)
Is there any way to do this?
So I've got my live card working with the v12 GDK. It responds to a voice trigger and then sits there until the user stops it.
However, I can't determine how to create an always present live card which always remains on the left side of the timeline. Some apps already do this, the Settings app and Weather app, for instance. But I've been unable to make the same happen for my app; I can't find any hook on Glass start like the GlobalAlarmReceiver for normal Android apps.
Am I missing something?
To make a live card that will remain in the timeline even if the user reboots the device, you may want to try the techniques described here to register a broadcast receiver that detects when the system is booted and you can start your service from there.
Your users will still need to use a voice trigger to start it once after installing it, though (either that, or reboot their device, which is even less desirable). This is because on Android, the ACTION_PACKAGE_ADDED broadcast that gets sent when an application is installed doesn't get sent to the application that was just installed.
I have created an addin(Extension) for enterprise architect. The addin basically popup's a dialog(using tkinter of python to show this popup) where i allow the user to select the directory path. now if the user takes more than say 3 seconds, there appears an server busy window, which the user has to click switch to to return to the previous control. Is there any way to avoid this or increase the server busy timeout in EA?. The dialog popup and server busy window appears like below
Well i found the solution, Since EA is an 32bit application, even if you are using 64bit windows. You are expected to install python 32bit.
I have a Windows service written in CPP that I start manually. The service starts up just fine and works ok. However we have recently noticed in the Windows Services GUI that the service shows in the Starting state. Upon examining the Event Viewer it clearly shows that the service has entered the Running state.
Anyone got any nuggets of gold on this one?
Thanks.
The problem turned out to be an unaccounted for call to the SCM to start the service. Deleted the line and the problem went away.