I am using the Genymotion emulator and am unable to lock the screen by using the power button, or any of the other suggestions provided here: How to lock genymotion?
On the device go to Settings > Security > Screen Security and check that Screen Lock isn't set to None
Hope that helps!
Related
I am using Android management API. I have applied policy to device and turned it to kiosk mode. After a while when I turn on the device, it is not connected to wifi anymore and is still in kiosk mode. Therefore I cannot connect it manually or update its policy. Is there a way to solve it ?
Unfortunately, as you cannot open the wifi dialog and devices cannot update the policy without a connection, the only way to workaround this is to hard reset the device per OEM instruction.
In the future, you can use KioskCustomization to have access to the status bar and navigation buttons so there would be no need to hard reset the device again if there is no connection as you can open the wifi dialog with this.
For people wondering how to escape the kiosk mode. There should be a way for your device to reboot to recovery mode. I my case - samsung tablet - I hold power button and volume down button for a while and when samsung logo appeared a released the power button, but still hold the volume down button. In recovery mode I were able to connect to wifi manually.
I following this link to enable developer mode on xbox.
https://learn.microsoft.com/en-us/windows/uwp/xbox-apps/devkit-activation
Everything is fine except that after activating xbox with code, It is showing this message
If anybody can assist how to fix this? It's been two days and still showing this message. Thanks!
Update
The newest app called 'Xbox Dev Mode', with Xbox Series S and X logo, which can work as before. But their docs haven't changed yet.
=========================================================
This may be a production bug of MS. But you can enable dev mode with some hidden skills.
Settings > System > Console Info > Press LB RB LT RT quickly > Developer Settings > Developer Mode.
Check it, your console will restart to dev mode.
Thanks.
I downloaded the agora.io video sdk asset from the asset store, imported it to a new project. On the demo "SceneHome" scene, I entered the api id. Clicked play, and as soon as I click the "join" button Unity crashes. As far as I can tell the crash happens on the
app.join(field.text);
line in the TestHome.cs script (line #86).
I tested it in 2019.3.2f1 and 2020.1.0b5. The result was the same.
The OS is Catalina 10.15.4.
The demo works on Windows.
I followed this tutorial: https://medium.com/#jake_agora.io/mac-run-video-chat-within-your-unity-application-e001091db62f but used x86_64 dlls instead of x86
Does anyone know what this is about? Or where should I begin to look?
Another tutorial, this one from Agora:
https://www.agora.io/en/blog/run-video-chat-within-your-unity-application-mac
It can be caused by missing the Camera and Microphone usage in the Unity Editor project setting. Please let us know if that's the case. (I saw you are also on the Slack channel, let's continue the conversation there.).
For the people who didn't know, Agora Developer Community - Unity Chat channel is here :)
As herve nau pointed out the problem was that the Unity did not had the permission to use camera or microphone. And the solution should work. Alternatively, here is another way to add the permission as described by launzone:
1) Disable SIP: Go into recovery mode (hold CMD+R when you
restart your Mac) Don't be afraid, we are not doing anything crazy.
2) After that open Terminal (it should be accessible from one of the
Menus at the Top) Type in "csrutil disable" and hit enter. Then reboot
your Mac normally.
3) Open Terminal and type in: "sqlite3 ~/Library/Application\
Support/com.apple.TCC/TCC.db" and hit enter
4) For microphone access, type in: "INSERT INTO access
VALUES('kTCCServiceMicrophone','com.unity3d.unityhub',0,1,1,NULL,NULL,NULL,'UNUSED',NULL,0,1541440109);"
and hit enter
For camera, type in: "INSERT INTO access
VALUES('kTCCServiceCamera','com.unity3d.unityhub',0,1,1,NULL,NULL,NULL,'UNUSED',NULL,0,1541440109);"
and hit enter
6) check in your SystemPreferences/Security&Privacy > unity hub should
now show up in both mic and cam
7) reboot in recovery mode again (CMD+R), open terminal again, type
in: "csrutil enable" and hit enter, to enable SIP again
8) reboot normally and enjoy!
Here is the full thread. I hope it helps someone :)
check if not related to the webcam registration issue on macOs with the Unity Hub running. Fix for the camera, not sure if related to your problem: Remove the Unity Hub app, then open the project directly from Unity App. May also be useful to relocate the Unity app in another folder to force the webcam usage security registration.
Made the test here, Unity 2019.3.11.f1, using the demo app, with Hub active -> crash on press of Join Button, did the Hub removal described above, rerun the same demo and no more crash at this level. Running on Catalina 10.15.2.
I developed a simple application on Kony and while launching the application it shows the message "Waiting for device". How can I solve it?
Just "wake" your device by unlocking it, touching its screen or going to home screen.
This message is shown when there are no devices/emulators connected to install the application.
You can check if any device/emulator connected by using the below command in Windows command prompt.
adb devices
If the above command lists any device/emulator then you wont see the error.
If the physical device is already connect via USB, the you can check whether the developer option and USB debugging is enabled in you android device.
How to enable developer option?
Hope this helps!
The application could not be launched for debugging. Ensure that the
target device screen is unlocked and that the application is installed.
How to get rid of this annoying message which appears every time I try to debug or run project from Visual Studio on Windows Phone 7 after 5 minutes of not-using phone (5 minutes is maximum time of sreen time-out I can set in phone settings).
I am missing something? Is it possible to avoid phone form locking/time-outing screen either from VS at start of debugging or in special application that I would manually start first before debugging so that app will be back on screen when debugging is finished and stopping phone from locking screen? But how to stop phone from locking screen? :-)
UPDATE: I have Omnia 7 which is AMOLED and doesn't have "never" setting. According to J. Loomis said in comment below, this is because "they can get severe burn in if left sitting on for extended periods" so best would be to unlock screen programmatically on start of debugging. I think this should work this way in VS.
In "Settings" select "lock & wallpaper" turn the password off and set "Screen time-out" to never.
It is important to note that the "never" option will only show if the password switch is set to off.
you can set UserIdleDetectionMode = Disabled to prevent the lockscreen from coming down on your app while debugging/developing/testing. Use it with caution in your released app. See MSDN for details:
http://msdn.microsoft.com/en-us/library/microsoft.phone.shell.phoneapplicationservice.useridledetectionmode(VS.92).aspx
My phone (Lumia 800) does not have a setting for "Never" in lock+wallpaper settings, even with the password turned off. The only way I could get the phone to stop locking between debugging sessions is to have another app running in the background behind the app you are debugging that has UserIdleDetectionMode set to disabled. There is an app in the marketplace whose sole purpose is this call Phone! Dont Sleep! (note: I did not make this app nor do I know who made it, I am just sharing because I found it helpful)