How can I set default application on pepper robot tablet? - pepper

I have created a simple web application to render on pepper tablet and I want to set the application as default startup app. how can I do that?

You can set the "Launch trigger condition" to "1".
These can be set in the manifest of the Choregrahe behavior of the activity.
Check the documentation here:
More about trigger conditions can be found here:

Related

AWS Device Farm - Disable tutorials on devices

I am doing automated tests [Android / Appium Java JUnit] with the AWS Device Farm service, but they are interrupted by the use tutorials that appear on the devices, for example, the tutorial of how to use the camera. I want to know if there is a way to disable the tutorials of the use of the device. Thanks.
I work for the AWS Device Farm team.
We detected and root caused this issue where a one-time tutorial popup appears on some phone's camera apps. We've corrected it, so feel free to try again and let us know if this problem is still affecting you.
Looks like there is also a script you can run from this AWS forum post
https://forums.aws.amazon.com/thread.jspa?threadID=294719
Hi,
I'm so sorry this keeps happening to you. We do currently only have the dismissal running on some devices like the Samsung S9, and are going to be enabling it for other devices soon, in the coming weeks. What I can do now is provide you a script to verify that theyre dismissed yourself at the beginning of your test. If you're using "custom environment mode", add the following 2 lines to the pre-test section of your test spec file:
curl https://s3-us-west-2.amazonaws.com/aws-devicefarm-support/chrome_initialization_and_popup_detection.py -o chrome_initialization_and_popup_detection.py
- python chrome_initialization_and_popup_detection.py -v --retries 2 --output-dir $DEVICEFARM_TEST_PACKAGE_PATH/popup_dismissal
This will run our popup dismissal script in your own code to verify that any device you run on gets all popups dismissed. It shouldn't be necessary for some devices like the S9, but just in case any do happen to creep up, this will dismiss them for you. I'll also double-check on our end why some popups like the S9 popup aren't getting dismissed properly.

Can't connect to Diagnostic Events while debugging Service Fabric app

I just created a fresh Service Fabric app with a stateless ASP.NET Core Web API service as an admin with a 5-machine debug cluster running locally. When I debug it (or any other Service Fabric app), it launches and runs successfully (e.g. I can see the expected output when I navigate to the endpoint with my browser or with Postman), I can see it running fine in the Service Fabric Explorer and I can see output in the Debug window within Visual Studio 2017, but I cannot see any events in the Diagnostic Events (note, not Diagnostic Tools) panel.
When I start debugging, the Diagnostic Events panel shows up as expected, but remains empty. I have no filter applied (no change if I click "Clear Filter" for the heck of it) and it shows at the bottom that it's Disconnected with 0 of 0 events shown. However, if I click on the green Start button, nothing happens and it continues to stay in a state of being disconnected.
Why is this and how can I get it to connect so I can see the output of ServiceEventSource calls?
Make sure that the name of the EventSource is set in the ETW Providers window:

Windows store app automating testing, run and detect when the application is stopped (suspended) c++

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?

Windows Service for launching and restarting a user process (with GUI)

I need a certain process to be constantly running in every user’s computer. If that .exe is killed, I must be able to restart it and send an alert.
I immediately thought of building a Windows Service as the ideal solution, but I am facing a problem:
The process started by that service needs to be able to interact with the user, e.g. be able to show him a GUI.
my application also sets a keyboard hook in order to monitor the user's typing rhythms, and when I start the .exe from a service, that information is not accessible.
From the service I am able to launch the process "as the user" (using the LogonUser and CreateProcessAsUser functions), but still can’t see the GUI.
Is this possible? If not, what can I use to achieve the desired functionality?
tia
By default the GUI .exe will be run in the service session, which is separate from the interactive session of the user. You need to look into techniques for building an interactive service.

Windows Service with GUI monitor?

I have a C++ Win32 application that was written as a Windows GUI project, and now I'm trying to figure out to make it into a Service / GUI hybrid. I understand that a Windows Service cannot / should not have a user interface. But allow me to explain what I have so far and what I'm shooting for.
WHAT I HAVE NOW is a windows application. When it is run it places an icon in the system tray that you can double-click on to open up the GUI. The purpose of this application is to process files located in a specified directory on a nightly schedule. The GUI consists of the following:
A button to start an unscheduled scan/process manually.
A button to open a dialog for modifying settings.
A List Box for displaying status messages sent from the processing thread.
A custom drawn window for displaying image data (the file processing includes the creation and saving of images).
A status bar - while a process is not running, it shows a countdown to the next scheduled scan. During a scan it also provides some status feedback, including a progress bar.
WHAT I'M SHOOTING FOR is a service that will run on boot-up and not require a user to login. This would consist of the scheduled file processing. However, when a user logs in I would still like the tray icon to be loaded and allow them to open up a GUI as I described above to monitor the current state of the service, change settings, start a scan manually, and monitor the progress of a scan.
I'm sure that I have seen applications like this - that function as a service even when I'm not logged in, but still give me a user interface to work with once I do log in.
I'm thinking that instead of having a single multi-threaded application that sends messages to the GUI thread from the processing thread, I need two applications - a Service to perform the processing and a GUI application to provide visual feedback from the Service and also send messages to the Service (for example, to start a scan manually). But I am new to Windows Services and have no idea how this is done.
It is also possible that I'm completely off base and a Service is not what I'm looking for at all.
Any help / ideas / suggestions would be greatly appreciated! Thank you.
You can't do this as a service.
You'll need to make your Windows Service as a normal service application. This will startup on system startup, and run the entire time the system is up.
You'd then make a completely separate GUI application, which "talks" to the service. This can be set to run when a user logs in, in the user's account.
In order to make them "talk" to each other, you'll need to use some form of IPC. Since these run on the same system (but in different accounts, typically), named pipes or sockets both work quite well.
There is a simple way of doing it.
You can’t have the service access any user’s session (session 1,2,3..) since services are isolated and can access session 0 only. This is a change from 2011.
You should write a win32 program to be launched by your service per each user who logs in using https://msdn.microsoft.com/en-us/library/windows/desktop/ms682429(v=vs.85).aspx
The service can continue performing any task that isn’t user specific.