I used to have some SDKs and even a WDK for Windows 10 (Including Windows 10 Mobile). After recently installing Visual Studio 2015/2017 and building up libraries tools etc. one install after another I was able to acquire SDKs, ADKs and WDKs for Windows Phone 7, WP 8.0 and WP 8.1....but when I got started on installing or trying to install Windows 10 (Including Win10m) I realized none of the downloads on M$'s servers/webpages contain the Windows 10 Mobile portion of the installations, after doing a quick google search it appears Microsoft removed Win10m development feaures from their product downloads as far back as 2017?? Has it really been that long...? Wow.... I know I can't have been the only one to download these dev kits while they were available, can anybody provide a backup link or archive link to a cloud based service to share for those of us that still wish to continue to build Win10m source files and mess around with creating our own (UWP or not) Win10m software??
Thanks very much guys
Related
Hello
I've been trying to figure out (by googling a *lot*) what the limitations are for non-Windows developers with the GT-I9000. Samsung's SDK is Windows only, but maybe it's not the end of the road?
Some concrete questions:
* Do you need Windows to get an adb session?
* Do you need Windows to root the device?
* Do you need Windows to cross compile native code?
* Does the stock Android SDK from Google work?
* What do you actually loose without Samsung's SDK? E.g. the BONDI API's?
I really want to buy this shiny monster, but I also *never* again want to suffer Windows, and especially not for development.
Best regards / Klas
AFAIK there is no "Samsung SDK"
check this http://developer.android.com/sdk/index.html
the sdk is available for windows, osx & linux
hope this helps
My mistake, it's called "Bada SDK". And at least for the GT-I9000 it's for Windows only. Apparently the Bada Linux platform includes support for some novelty API's such as BONDI (to access e.g. device file system from web apps) and these have no support in the regular Android SDK.
I can live without these device specific API's, I just don't want to have to use the Bada SDK to do anything *else*.
Google's SDK is eclipse based and is available for windows, linux and osx like stated above. I'm running it in 64 bit ubuntu (lucid lynx) and have little problems doing so.
Sent from my GT-I9000 using XDA App
How about just running Windows in VirtualBox for the neccessary parts.
Darkstriker said:
How about just running Windows in VirtualBox for the neccessary parts.
Click to expand...
Click to collapse
I had much problems with trying this under mac os x.
VMware and VirtualBox dont show the i9000 as USB-Device...
My experiences with connecting USB devices to virtualized environments are also poor. Not that it matters much: I am curious what development capabilities you *loose* if you can't/won't use Windows -- not how to run the Bada SDK in a virtualized environment. No one seems to be overly concerned about this (a good sign so I'll go ahead and order the phone.
Klasa said:
My mistake, it's called "Bada SDK". And at least for the GT-I9000 it's for Windows only. Apparently the Bada Linux platform includes support for some novelty API's such as BONDI (to access e.g. device file system from web apps) and these have no support in the regular Android SDK.
I can live without these device specific API's, I just don't want to have to use the Bada SDK to do anything *else*.
Click to expand...
Click to collapse
You don't need the Bada SDK at all, because Bada is a different platform used on other Samsung phones like the Samsung Wave S8500. It's not Android or related to Android, other than both (potentially, in Bada's case) being based on Linux.
the galaxy is running android os from google - the wave is running the bada os from samsung.
as such i think the OP has confused the above fact and thinks the galaxy is running bada hence referring to a "samsung sdk". galaxy s GT-I9000 runs google android, for which google has released a multi platform SDK
The poster may need to be aware that the descriptor for usb detection is broken for it currently, and has been for a little while. It's not really plug and go.
You'll need to follow the usual instructions to setup your android dev, then possibly compile a adb with support for the galaxy s. I hope I can be proven wrong for that though.
Superroach said:
The poster may need to be aware that the descriptor for usb detection is broken for it currently, and has been for a little while. It's not really plug and go.
You'll need to follow the usual instructions to setup your android dev, then possibly compile a adb with support for the galaxy s. I hope I can be proven wrong for that though.
Click to expand...
Click to collapse
Compile abd, why? The old sdk does not see galaxy S but the latest one does. And if you have problems on linux with adb not seeing your phone try running adb with root user.
Thank you guys.
I havn't checked again, but I was under the impression that Bada is the underpinning of Android on I9000.
The only thing left to understand about the vendor's platforms underneath Android is why Google didn't set it all up with Debian packages. A common repo could keep vendor specific variants of components neatly isolated; Isolated and distributable without the fuss of trying to figure out what is compatible with what. I just want to run something like
Code:
apt-get install android-gti9000-dev android-sdk --rootdir=$MY_CHOICE
on my workstation and have the SDK, device sources, other host tools, and IDE plugins installed to some working directory of my choice. That would be great
Hello everybody!
I have FW4, VS2010 Ult, XNA Game Studio 4, ExpressionBlend 4. I want to start development for WP7 and found MS' toolchain (467Mb ISO!), but it's huge! (and no separate components is available). What else do I need to develop for WP7? Guessed I need phone emulator and some libraries/SDK, but cannot find appropriate packages. Can somebody help me, please?
Also, do I need unlocked image? What exactly is locked in emulator?
Thanks in advance.
The only basics you really need Visual Studio, and this download which is the Developer Tools Package, it contains all the files, the emulators, etc
http://www.microsoft.com/downloads/...cf-a63a-4f97-952c-8b51b34b00ce&displaylang=en
One thing you should certainly take a look at is the Silverlight for Windows Phone Toolkit, which you can get here:
http://silverlight.codeplex.com/releases/view/55034
It's stuff that really should be in the main SDK download, but it simply isn't.
Hi all,
has someone tried to get privileged access to wp7 via calls to conmanclient3? The RemoteAgent settings are all there (C:\ProgramData\Microsoft\Phone Tools\CoreCon\10.0).
Visual Studio 2010 does use the new CoreCon 10 files if it deploys to a real wp7 device. If it deploys to the emulator it does use the 5.1 files instead.
It looks like the settings for the 10.0 files differ from prevoius versions as the SmartDevice Tools of VS2008 (Plattformbuilder 6 based) won't work with the new files.
But in theory it should be possible to get access via a RemoteAgent (h__p://msdn.microsoft.com/en-us/library/microsoft.smartdevice.connectivity.remoteagent(v=VS.90).aspx), shouldn't it?
As cormanclient3, CMAccess and friends are all signed by microsoft and consist of native code it would be interesting to talk to someone who has already created a RemoteAgent based connection to a smartdevice. Is there someone out there?
Best regards,
-tobias
From the WP7 Developer Tools Application Deployment Tool, I'm pretty sure it's only using the CoreCon 10.0 files.
My RemoteExecute program here is using the Device classes (though I might have rewritten it a bit to get the Device.ConManServer), I'll now try the sample you linked too, and see if I can get it to work. File manipulation using the ConManServerseems to give lots of "Access Denied" errors, which I'm trying to work out why, and there's some stuff to be done with registry access as well, but this is the only way I've yet found of controlling the device from a desktop, without extra on device apps.
I check it with procmon, if you deploy to the emulator is loads the 5.01 files.
The MSDN Sample from above won't work as the service ids are from an older ce version. You need to use the ids from the file in corecon 10 addon folder.
do you get "access denied" or "not implemented" errors? Would be interesting if there is another set of files in the platform builder 7 which do implement additional functionality. I'd seen your remote execute program but I think the trick is to get a remoteagent running (looks like that's what visual studio does to get the debugger working).
regards,
- tobias
kuerbis2 said:
I check it with procmon, if you deploy to the emulator is loads the 5.01 files.
The MSDN Sample from above won't work as the service ids are from an older ce version. You need to use the ids from the file in corecon 10 addon folder.
do you get "access denied" or "not implemented" errors? Would be interesting if there is another set of files in the platform builder 7 which do implement additional functionality. I'd seen your remote execute program but I think the trick is to get a remoteagent running (looks like that's what visual studio does to get the debugger working).
regards,
- tobias
Click to expand...
Click to collapse
Ah, I'm just checking the Application Deployment tools, rather than the debugger, which would be a lot more useful... I think the emulator isn't really emulating, it's running using x86 code, and just acting like a WP7 environment (unlike the older emulators that emulated the entire hardware).
Will find the IDs for corecon 10 then, as that might make things work! (I've got device connections working, device name is "Windows Phone 7 Device".
I get Access Denied with most of them, though there is at least one function that's not implemented somewhere (I can't remember which one it is though!). The file manipulation APIs are quite different in the latest version of Microsoft.SmartDevice.Connectivity, with things like ProvisionDevice() not exisiting at all.
Will look at getting a RemoteAgent running, the functions are all there, and implemented, I just need the right IDs.
I can upload my code somewhere if you want (it's a little messy though!)
Hi,
With the new Windows 8.1 Update 1 Microsoft integrated a new ability to reduce the size of the space for the Windows Installation.
Since there is a leaked Windows RT 8.1 ISO in the internet is it theoretically possible to modify the ISO to install with the new WIMBoot function? 28GB free space instead of 10GB on a 32GB Surface sounds good and the Microsoft site also mentions ARM processors.
Because I'm a new user I can't post links so please Google for: "What is Windows Image Boot (WIMBoot)?" and "Deploy WIMBoot Images"
I was going to try this myself (I have the 8.0 wim file), but apparently you need the RT 8.1 with Update 1 to do it. Unfortunately, recimg.exe doesn't exist on RT, so you can't create your own. I'm going to try to find that leaked ISO you're talking about, though. This would be a boon for people with 32GB of memory.
Hey, everyone! If any of you are still looking around, I have some pretty good news. I have found 2 out of the 4 unlocked ROM files, and I have managed to get them both to work. I will be packing them into folders with all the necessary files to run them! All you need is a system that has WDDM video drivers, Windows 7, and 64bit support. The two working ROMs I have are build 6176, and 7003. They both run flawlessly and I'm very happy to have them running. This is all great news, but I need your help. Everyone that has your old computer, please, look through it to try and find the other two bin files. One should be called "WM70Full.bin" (This is the unlocked BIN file for build 6007), and the other one should be called "WM70C1-6414-Unlocked.bin" (this is the bin file for the unlocked build 6414 ROM). They could have different names, but I think these were the original names. I will be sharing the packed emulators shortly, once I get everything finished up. They will be hosted on a MODERN website (I'm not gonna use dead sites like MultiUpload, rapidshare, etc). I will host them on OneDrive, in a private shared folder. I will also be uploading all of this to archive.org to preserve the history as much as possible. Thank you for reading, and I hope you all have a great day.
Edit as of 10/8/2022, 6:33PM:
The packed emulators are now ready, and they should run on any 64bit Windows 7 system with WDDM support! Here is the download link to the emulators: https://1drv.ms/u/s!Ai5FoHSKYucjhaw4FTwlPPZ5vjdHHw?e=C4DLbH