[Norin_Radd]

@Norin_Radd any testing and feedback is highly welcome. Let me know if you need an Android build because jenkins should be able to deliver that as well.
If you're Emby server cannot be auto-detected you can use the "Add provider..." entry in the "Media provider" tree. There you should be able to choose what kind of media provider to add (Emby) and then enter the base URL of your Emby server installation (e.g. "http://localhost:8096" but with the proper hostname / IP address and port). Kodi will then try to find and identify your Emby server and a dialog will appear informing you about whether that worked or not. If it worked there should be a new media provider in the list view and you should be able to configure it with your access credentials.

@LongMan thanks for the logs. It looks like in your case Kodi is trying to execute the settings callback twice simultaneously which does not end well. I'll try to figure out where this is coming from. Just to be sure does Kodi crash after you

1. opened the list of detected users
   
2. selected a specific user (not manual) from the list of detected users
   

Reading the logs I would say the latter (option 2).

I've made a few changes to the settings dialog which should avoid more unnecessary calls to the settings callback and hope I didn't break any existing functionality... The test build has been triggered at https://jenkins.kodi.tv/job/WIN-64/11310/, see http://mirrors.kodi.tv/test-builds/windo...03-x64.exe. It does NOT solve the problem of the crash when two UI-based settings callbacks are passed to python add-ons but it's hard to fix it if I can't reproduce it myself.  

Thanks for the reply, nothing shows up on the media provider tree on my windows 10 pc. 

https://prnt.sc/q92rib

And yeah i would like to test it on my android tv.