We cannot enrol a Wishtel IRA Tablet device in device owner mode using the Android Management API. The enrollment process stops before launching our companion app during setup (through the setupActions profile setting).
The enrollment process is detailed below:
Tap 7 times on the welcome screen
Configure the WiFi network
Checking for updates
Installing QR reader
Flash the QR code
Set up your device screen
Setting up work device screen
Just a sec... screen
Android home screen is displayed
The device information is:
Model & hardware: IRAI1705
Android version: 8.1.0
Android security patch level: 5 September 2018
Build number: Wishtel_IRA_20181018
Thanks a lot in advance for your help.
Related
I'm trying to see why our DJI-enabled app isn't working correctly with the Mavic Air 2 on iOS or Android. Here I'm debugging with iOS but I've seen the same failures when briefly testing on our Android app.
When calling setMode:completion: on the single camera belonging to the Mavic Air 2, I consistently get "Current product does not support this feature.(code:-1013)"
isMediaDownloadModeSupported returns true for the camera, and yet I can't set the camera mode to media download mode at all (or any other mode).
I've found that setFlatMode:completion: seems to work ok to set photo and video modes as a sort of alternative, however this is only for photo/video modes, and won't help me with downloading media from the SD card. (right?)
Any help out there?
From my DJI Developer Support ticket for the same issue:
For the Mavic Air 2 drone, should use the setFlatMode to switch the photo, video mode, and use the enterPlayback, exitPlayback to enter/ exit the download mode.
Is there any way in wear app, to redirect a user to a "Connectivity" screen which is added below,
Notes: able to open only Bluetooth or Wi-Fi or Airplane mode using the setting intent given in this link
https://developer.android.com/reference/android/provider/Settings.html
Issue is solved using Settings.ACTION_WIRELESS_SETTINGS intent
I enabled debugging over bluetooth on my Moto 360
and enabled Android Wear app on my Nexus4.
Status displays target : disconnected
Forwarding the port from my computer shows the status host will be changed to connected, but the target status remains disconnected.
I toggled debug via the bluetooth switch which had no effect.
My phone is a Nexus 4. Is there a problem with my phone or the Moto 360?
I eventually managed to get it working. The issue seems to be related to having paired your device with an emulator first. Take a look at this post to see how I fixed it: http://melix.github.io/blog/2014/10/android-moto360.html
open the applications settings, search for the Android Wear application, then force stop it
clear its data and cache
Search for Google Play Services
Click on Manage space. Delete all data.
reboot your phone
reset your Moto 360
Pair watch with phone
Following the instructions from android.com https://developer.android.com/training/wearables/apps/bt-debugging.html to setup debugging and it should work now.
Done.
I tried it on a Sony z1.
It succeeded without any problems.
So, maybe it's not supported perfectly in Nexus 4.
If you have the same problem, I suggest using another device.
I fixed without factory reset with these steps
-Force stop android wear application and clear cache
-Disconnect emulator on android wear app
-Forget emulator on android wear app
-Connect your real device via bluetooth
-Open debugging over bluetooth
Make sure that debugging options are also active in android wear device
Run this commands in command window:
adb forward tcp:4444 localabstract:/adb-hub
adb connect localhost:4444
It's great that I can develop Blackberry software on OS X. I need to run the desktop software to gain access to the device from the JDE. When I start a debug session I can't set breakpoints, but I can see System.out on the JDE console. Problem is that the phone can't see file:///store/... (error 10003) Research shows that as long as desktop is connected the phone then the running application doesn't have access to the file system. Disconnecting phone from finder doesn't help. Disconnecting blackberry desktop terminates the debug session.
So, the question: how can I keep the JDE debugger connected with an application that reads and writes files on the phone?
plug in the blackberry via USB
Blackberry desktop will pop up
Run JDE
Send mac to sleep
Leave blackberry plugged in
Wake up Mac again
No drives reconnect
Blackberry desktop running but shows ejected
JDE can still see BlackBerry
Debugging works while application can see Blackberry file-system
I've started yesterday afternoon studying WP7, so be patient.
I've just created my first test app, registered as developer on AppHub, connected my phone with Zune, registered my phone in my AppHub profile (I can see it in my devices section) and compiled my app.
When I try to transfer my app into phone (using Application Deployment Tool as described here) I get an error that can be traslated as
Unable to connect to device because it's locked by pin
But my device has not any pin (or I don't know to have one) and it doesn't show anything on screen.
What could/should I do?
UPDATE:
Zune is running: if I try I get the error
I close Zune and run WPConnect: my device is connected but the error is the same
When deploying the app, make sure the phone screen is unlocked.
Additinal info: If you are developing from Desktop PC, sometimes connecting from front USB panel wont work.
You can't deploy while the screen lock is active, so try swiping up the lock screen before deploying.