Enrolling Android 5.1 device fails without reasonCosu app development through Android Management Api or device owner locktaskHow does designing custom android DPC app relate to Android management API?Management API and app distribution inside enterpriseHow to get list of devices with Management API (beta)?Is it possible to enroll a non-play-certified device into the Android management API?Android Management API change Policy for deviceAndroid EMM: Enable the System apps for the owner userAndroid Management API not working in KoreaHow to distribute private Android app testing tracks using the Android Management API + Organisations?Android Kiosk mode not working when using Android Management API Policy
Category-theoretic treatment of diffs, patches and merging?
What was the significance of Spider-Man: Far From Home being an MCU Phase 3 film instead of a Phase 4 film?
KenKen solver - Python
Can you create a free-floating MASYU puzzle?
Why am I getting unevenly-spread results when using $RANDOM?
Are "confidant" and "confident" homophones?
How to factor a fourth degree polynomial
Are host configurations in the SSH config merged?
Why did the frequency of the word "черт" (devil) in books increase by a few times since the October Revolution?
Why does the Misal rico de Cisneros uses the word "Qiſſa", and what is it supposed to mean? Why not "Miſſa" (Missa)?
What do you call a situation where you have choices but no good choice?
Attach a visible light telescope to the outside of the ISS
Array or vector? Two dimensional array or matrix?
Taking advantage when HR forgets to communicate the rules
My professor has told me he will be the corresponding author. Will it hurt my future career?
How do I explain that I don't want to maintain old projects?
Interpretation of non-significant results as "trends"
How to say "is going" in Russian in "this game is going to perish"
The flying colours
Any way to meet code with 40.7% or 40.44% conduit fill?
When moving a unique_ptr into a lambda, why is it not possible to call reset?
Passwordless authentication - how invalidate login code
What does "spinning upon the shoals" mean?
Why is there paternal, for fatherly, fraternal, for brotherly, but no similar word for sons?
Enrolling Android 5.1 device fails without reason
Cosu app development through Android Management Api or device owner locktaskHow does designing custom android DPC app relate to Android management API?Management API and app distribution inside enterpriseHow to get list of devices with Management API (beta)?Is it possible to enroll a non-play-certified device into the Android management API?Android Management API change Policy for deviceAndroid EMM: Enable the System apps for the owner userAndroid Management API not working in KoreaHow to distribute private Android app testing tracks using the Android Management API + Organisations?Android Kiosk mode not working when using Android Management API Policy
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I am trying to enroll a fleet of Android 5.1 devices which did never receive a newer version of Android and are not working with any third party ROM. So we're stuck on 5.1.
As the Google Play Services in the ROM was so old, that I couldn't even install the Android Device Policy DPC, I updated the Play Services in the ROM using an update.zip, wiped the device and then enrolled the device using a NFC tag.
Unfortunately, enrollment is not working, and I'm not even getting an error message. The DPC seems to set itself as the device owner, but no enrollment is taking place - the device does not show up on the API, and upon launching the DPC from the application drawer and clicking on the "Get started"-button, we always are presented with "Your system cannot be managed by this app. Please contact your administrator".
Well, I am the administrator and I have no clue, why this is failing.
Has anyone an idea, what the DPC is looking for before deciding that the device cannot be managed? Or how to get a more meaningful message out of the DPC?
android-management-api
asked Mar 25 at 21:16
MartinMartin
3322 silver badges12 bronze badges
add a comment |
I am trying to enroll a fleet of Android 5.1 devices which did never receive a newer version of Android and are not working with any third party ROM. So we're stuck on 5.1.
As the Google Play Services in the ROM was so old, that I couldn't even install the Android Device Policy DPC, I updated the Play Services in the ROM using an update.zip, wiped the device and then enrolled the device using a NFC tag.
Unfortunately, enrollment is not working, and I'm not even getting an error message. The DPC seems to set itself as the device owner, but no enrollment is taking place - the device does not show up on the API, and upon launching the DPC from the application drawer and clicking on the "Get started"-button, we always are presented with "Your system cannot be managed by this app. Please contact your administrator".
Well, I am the administrator and I have no clue, why this is failing.
Has anyone an idea, what the DPC is looking for before deciding that the device cannot be managed? Or how to get a more meaningful message out of the DPC?
android-management-api
asked Mar 25 at 21:16
MartinMartin
3322 silver badges12 bronze badges
add a comment |
I am trying to enroll a fleet of Android 5.1 devices which did never receive a newer version of Android and are not working with any third party ROM. So we're stuck on 5.1.
As the Google Play Services in the ROM was so old, that I couldn't even install the Android Device Policy DPC, I updated the Play Services in the ROM using an update.zip, wiped the device and then enrolled the device using a NFC tag.
Unfortunately, enrollment is not working, and I'm not even getting an error message. The DPC seems to set itself as the device owner, but no enrollment is taking place - the device does not show up on the API, and upon launching the DPC from the application drawer and clicking on the "Get started"-button, we always are presented with "Your system cannot be managed by this app. Please contact your administrator".
Well, I am the administrator and I have no clue, why this is failing.
Has anyone an idea, what the DPC is looking for before deciding that the device cannot be managed? Or how to get a more meaningful message out of the DPC?
android-management-api
asked Mar 25 at 21:16
MartinMartin
3322 silver badges12 bronze badges
I am trying to enroll a fleet of Android 5.1 devices which did never receive a newer version of Android and are not working with any third party ROM. So we're stuck on 5.1.
As the Google Play Services in the ROM was so old, that I couldn't even install the Android Device Policy DPC, I updated the Play Services in the ROM using an update.zip, wiped the device and then enrolled the device using a NFC tag.
Unfortunately, enrollment is not working, and I'm not even getting an error message. The DPC seems to set itself as the device owner, but no enrollment is taking place - the device does not show up on the API, and upon launching the DPC from the application drawer and clicking on the "Get started"-button, we always are presented with "Your system cannot be managed by this app. Please contact your administrator".
Well, I am the administrator and I have no clue, why this is failing.
Has anyone an idea, what the DPC is looking for before deciding that the device cannot be managed? Or how to get a more meaningful message out of the DPC?
android-management-api
android-management-api
asked Mar 25 at 21:16
MartinMartin
3322 silver badges12 bronze badges
asked Mar 25 at 21:16
MartinMartin
3322 silver badges12 bronze badges
asked Mar 25 at 21:16
MartinMartin
3322 silver badges12 bronze badges
asked Mar 25 at 21:16
MartinMartin
3322 silver badges12 bronze badges
asked Mar 25 at 21:16
MartinMartin
3322 silver badges12 bronze badges
3322 silver badges12 bronze badges
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The Android Management API doesn't support NFC provisioning on Android 5.1. It is only supported on Android 6.0 and above.
The documentation previously mentioned that 5.1 is supported, that was an error and we have now updated it.
answered Mar 27 at 11:35
FredFred
1,4865 silver badges11 bronze badges
So how do you enroll a COSU 5.1 Android device then? If I understand correctly, there is no way to enroll a 5.1 device to be a COSU device?
– Martin
Mar 27 at 15:17
That's correct. Fully managed mode (and therefore COSU) is only supported on 6.0+. Work profile however is supported on 5.1+.
– Fred
Mar 27 at 19:03
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55346521%2fenrolling-android-5-1-device-fails-without-reason%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The Android Management API doesn't support NFC provisioning on Android 5.1. It is only supported on Android 6.0 and above.
The documentation previously mentioned that 5.1 is supported, that was an error and we have now updated it.
answered Mar 27 at 11:35
FredFred
1,4865 silver badges11 bronze badges
So how do you enroll a COSU 5.1 Android device then? If I understand correctly, there is no way to enroll a 5.1 device to be a COSU device?
– Martin
Mar 27 at 15:17
That's correct. Fully managed mode (and therefore COSU) is only supported on 6.0+. Work profile however is supported on 5.1+.
– Fred
Mar 27 at 19:03
add a comment |
The Android Management API doesn't support NFC provisioning on Android 5.1. It is only supported on Android 6.0 and above.
The documentation previously mentioned that 5.1 is supported, that was an error and we have now updated it.
answered Mar 27 at 11:35
FredFred
1,4865 silver badges11 bronze badges
So how do you enroll a COSU 5.1 Android device then? If I understand correctly, there is no way to enroll a 5.1 device to be a COSU device?
– Martin
Mar 27 at 15:17
That's correct. Fully managed mode (and therefore COSU) is only supported on 6.0+. Work profile however is supported on 5.1+.
– Fred
Mar 27 at 19:03
add a comment |
The Android Management API doesn't support NFC provisioning on Android 5.1. It is only supported on Android 6.0 and above.
The documentation previously mentioned that 5.1 is supported, that was an error and we have now updated it.
answered Mar 27 at 11:35
FredFred
1,4865 silver badges11 bronze badges
The Android Management API doesn't support NFC provisioning on Android 5.1. It is only supported on Android 6.0 and above.
The documentation previously mentioned that 5.1 is supported, that was an error and we have now updated it.
answered Mar 27 at 11:35
FredFred
1,4865 silver badges11 bronze badges
edited Mar 27 at 19:04
answered Mar 27 at 11:35
FredFred
1,4865 silver badges11 bronze badges
answered Mar 27 at 11:35
FredFred
1,4865 silver badges11 bronze badges
answered Mar 27 at 11:35
FredFred
1,4865 silver badges11 bronze badges
1,4865 silver badges11 bronze badges
So how do you enroll a COSU 5.1 Android device then? If I understand correctly, there is no way to enroll a 5.1 device to be a COSU device?
– Martin
Mar 27 at 15:17
That's correct. Fully managed mode (and therefore COSU) is only supported on 6.0+. Work profile however is supported on 5.1+.
– Fred
Mar 27 at 19:03
add a comment |
So how do you enroll a COSU 5.1 Android device then? If I understand correctly, there is no way to enroll a 5.1 device to be a COSU device?
– Martin
Mar 27 at 15:17
That's correct. Fully managed mode (and therefore COSU) is only supported on 6.0+. Work profile however is supported on 5.1+.
– Fred
Mar 27 at 19:03
So how do you enroll a COSU 5.1 Android device then? If I understand correctly, there is no way to enroll a 5.1 device to be a COSU device?
– Martin
Mar 27 at 15:17
So how do you enroll a COSU 5.1 Android device then? If I understand correctly, there is no way to enroll a 5.1 device to be a COSU device?
– Martin
Mar 27 at 15:17
That's correct. Fully managed mode (and therefore COSU) is only supported on 6.0+. Work profile however is supported on 5.1+.
– Fred
Mar 27 at 19:03
That's correct. Fully managed mode (and therefore COSU) is only supported on 6.0+. Work profile however is supported on 5.1+.
– Fred
Mar 27 at 19:03
add a comment |
Got a question that you can’t ask on public Stack Overflow? Learn more about sharing private information with Stack Overflow for Teams.
Got a question that you can’t ask on public Stack Overflow? Learn more about sharing private information with Stack Overflow for Teams.
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55346521%2fenrolling-android-5-1-device-fails-without-reason%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
