Are android permissions fixed on unity 5 latest version?

Are android permissions fixed on unity 5?
On unity 4 the runtime permissions of android api 23+ especially android 6.0 do not work and we have to find out a way to do that with some plugin or else permissions that my app need to work aren't even asked at anytime, is it still that way on unity 5 or its implemented already on unity code?
Actual version of unity is Unity 5.6.5

I can't release a version of my app on play store using unity 5 just to test that because my project is 4 and when upgrading assets that use physics like cars lead to strange behaviours and will have to be redone.

 

Unity 4 to 5 had a physics update as well as some other things.

As far as permissions go as of Android 6.0 (Marshmallow) you have to ask for permissions at* run-time because Google PlayStore no longer has the user accept all permissions before downloading the app. This means, that before you do something that is considered "dangerous" by Google see here, you must check if your application has the permission see here. So you have to build a plug-in yourself.

 

Thank you for the answer
So unity 5 will display automatically the window on the start of the app and if anything that needs permision at any point of the game it will already be authorized (if user said alow) on all android versions?

I can't test it because i don't have an android 6.0 device, i have a motorola with android 7.0 that on unity 4 at the start of the app permission is corretcly asked after installation first launch.

For testing with users and several android versions i would need to upgrade my project to 5 wich i'm already doing, i'm having to redo the car physics and lightmaps but getting all sorted out eventually.

 

My app is currently using unity 4.7.2 f1 and its on play store, the following tests we're run on that version.

My game needs 2 permissions, telephone id/status and files.
Recently i found out that device unique identifier of unity was identifiying more than 3 thousand of 9 thousand users of my game in my database with the same following hash:
cd9e459ea708a948d5c2f5a6ca8838cf wich decrypted is 00000000000000000000000000000000
The rest 6thousand+ was working properlly with unique hashes to identify them.

I managed to reproduce this problem by denying permission to telephone id/status at startup after the installation of the app on my motorola android 7.0.

So i made my system not allow that cd9e... hash anymore, so some users came and said that only files permission was being asked and the telephone id was not, they sent me a screenshot of permission configurations of the app and only files permission was avaliable to change to allow or disalow and others permissions we're not listed at all.
Users that sent me the screenshoot we're using samsung android 6.0 marshmellow, i could not keep it that way so i could not identify if there's more issues with another android versions/brands.

Also the changelog says 'Android: Added support for Marshmallow OS runtime permissions.' it doesn't say marshmallow and above, maybe it's a especific problem of android marshmallow

 

When i ran into this problem i started to collecting android id, imei, mac and video memory manually via script.
I found out that users that had the cd9... hash would not give any of the above information only 00000000 zero's, in other words, it seems like even to get the android id permission is needed on those also, at least on unity 4.7.2 f1, users with normal hashes would give out those info normally.
I'm maybe wondering if android 6 of samsung it's configured not to give any personal information about the device by default or something...

(Their values changing is not a problem because they are prompted to update their info when that happen and it should not happen often, it's a system that i'm using for my game that's working fine for a year.)

And i think unity should keep using the imei as first resource of identification just its because its not good for the user changing it with root apps i believe changing their android id doesn't affect anything, changing their imei is illegal and dangerous for warranty, theft recovery etc. and for us developers that need it for security is no good. (I know we should not trust it but it's my only resource)


*UPDATE*
I think i MAY have solved the problem by adding this to the manifest:
<meta-data android:name="unityplayer.SkipPermissionsDialog" android:value="false" />
(It was not present at all before saying true or false, i fully added to the builded by unity manifest it some days ago)
When i uploaded the app with that line google prompted me for the first time saying i was asking dangerous permissions, privacy policy info etc. (I was not asking before??)
Notice that this line below we're always present since unity add's it automatically and i haven't changed anything the manifest before i discovered the cd9 problem and 60% of the users we're already giving me their hashed android info correctly.
<uses-permission android:name="android.permission.READ_PHONE_STATE" />

Yesterday i blocked cd9... again and today no complaining on the support, if it stays like that i'll come back and update below if that solved the problem or not.

 

Adding to the manifest
<meta-data android:name="unityplayer.SkipPermissionsDialog" android:value="false" />
Solved the problem that was happening only on android 6.0.

Sorry for my english because i'm from brazil and sorry if i didn't explained more since the beggining because this topic https://forum.unity.com/threads/systeminfo-deviceuniqueidentifier-android-6-0.367028/ led me to believe that unity was not implementing the runtime permissions.

Thank you for the support JuliusM.