Version number 2.0.011044_11 now available to update
I'm trying to use this version with an SGS2 on Windows XP and it can't find a driver for the "CDC Serial" interface.
Anyone know where I need to go looking for it ?
Related
http://windowsteamblog.com/blogs/wp...indows-phone-developer-tools-ctp-refresh.aspx
This version works with the final version of Visual Studio 2010 (RTM) AND it includes an updated image of Windows Phone 7 for the emulator, so there should be some new goodies to dig into!
There's no actual download link that appears to be update/working atm though. Any luck finding one?
Yeah
http://www.microsoft.com/downloads/...FamilyID=cabcd5ed-7dfc-4731-9d7e-3220603cad14
Strangely enough though, it doesn't seem to work if you open in a new tab or window - but if you open the link directly it works fine.
Weird...
Casey
Thanks!
Now, how do I unlock the full image?
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
Google says android 4.4 kitkat is available for everyone. So is it means we can flash it directly to our galaxy w?
Now our smartphones become a mini computers.
in dekstop computers we can install a new os(linux or windows) directly. The OS recognize the drivers then install them directly or from the web. Maybe some of hardwares drivers cant find but its very rare issue.
So why android doesnt like this. Thats everybody install new version of android and its install the phones drivers directly or from the internet.
The smartphones hardware manufacturers less than dekstop computers hardware manufacturers but dekstop computers OS can do it well and avaliable for every kind of computer.
Why Android OS install like dekstop computers OS.
pharatlil said:
Google says android 4.4 kitkat is available for everyone. So is it means we can flash it directly to our galaxy w?
Click to expand...
Click to collapse
No, it needs to be ported.
pharatlil said:
in dekstop computers we can install a new os(linux or windows) directly. The OS recognize the drivers then install them directly or from the web. Maybe some of hardwares drivers cant find but its very rare issue.
So why android doesnt like this. Thats everybody install new version of android and its install the phones drivers directly or from the internet.
The smartphones hardware manufacturers less than dekstop computers hardware manufacturers but dekstop computers OS can do it well and avaliable for every kind of computer.
Why Android OS install like dekstop computers OS.
Click to expand...
Click to collapse
This is just partially true. Windows and Linux for desktop PCs already come with most of the drivers directly on the CD or DVD or at least with hardware IDs for the drivers they can download and install via internet.
Your ROM simply isn´t about the same size like a Linux or Windows DVD It also doesn´t have a 100GB HD, a DVD drive and at least 4GB RAM installed.
So if you want an Android that is about as easy to install on all devices, you would have to make it about that big in size like a Linux or a Windows installation DVD which most of the devices couldn´t handle.
That´s why it needs to be ported with just the drivers for your specific device. And this is also the advantage to keep it as small and slick as possible.
Most of linux os about 1gb.
Windows is about 1-2 gn. Not about 100gb.
İ ha ve a galaxy s3 and stock rom about 900mb.
İf google want to give latest firmwares every device They can make a pc program and it finds devices specs automatically.
Samsung, htc, lg...etc.. maybe dont want to give newest firmwares to older devices for selling new devices.
But why google dont make roms for every device. Android is a linux based os and linuxs difference is its avaliable for everyone. So i think googles s strategy about android isnt true. İt must be same way with linux.
pharatlil said:
Most of linux os about 1gb.
Windows is about 1-2 gn. Not about 100gb.
İ ha ve a galaxy s3 and stock rom about 900mb.
İf google want to give latest firmwares every device They can make a pc program and it finds devices specs automatically.
Samsung, htc, lg...etc.. maybe dont want to give newest firmwares to older devices for selling new devices.
But why google dont make roms for every device. Android is a linux based os and linuxs difference is its avaliable for everyone. So i think googles s strategy about android isnt true. İt must be same way with linux.
Click to expand...
Click to collapse
A totally fresh installed Windows 7 already is taking about 4GB on your HD and needs a way bigger partition to get installed at all.
Android is not a linux based rom. It´s a Java based ROM. Only the kernel is linux and this needs to be compiled first and match your hardware to make it able for the rom to work at.
Google only offers the basic code for a ROM but the rest must be added by the manufacturers. Beside this linux also wasn´t that userfriendly like it is now. The very first releases even didn´t use an UI. All had to be done on command line. Was meant to be used on servers but not for end users and though it was open source it took about 20 years from this stage to become an userfirendly OS for endusers like Windows.
So this is like comparing apples with pears. Best you ask Google and see what they will answer you.
İm disagree with you. or i couldnt explain well.
There in not more hardware manufacterers than PCs. But dekstop computers OS can handle it. For example i have got a hp compaq nx8220 notebook. its very old pc but i intalled windows 8 and its running very well. There is no drivers for windows 8 but windows have a feature for it. İ install many drivers in compatibility mode. ( Yes HP didnt publish a driver for it but windows's this compatibility feature solve the problem.)
Im not a developer but i know programming dialectic (i wrote programs in q basic and gw basic but i stay away from programming because of my job.) im interested about java and c++ and im learning. im seeing that developers main problem to porting Android to a device is hardware drivers. İf manufacterer give codes they port it easier.
İ want to say my hp compaq nx8220 is very old device but its runs with windows 8 very stable.
But my old phone and and my wifes phone galaxy w isnt a old device but they r saying your device cant runs properly with android's newest OS. It has 512 mb ram and 1,4ghz processor.??? (my notebook worst but runs w8)
Maybe one day some developers agree with my opinion and work with hardware drivers than making alot of custom roms. So maybe one day we enter a web page (for example cyanogenmod web page)and flash newest rom like installing a newest OS to a PC.
You may agree or disagree. No problem with that. It´s just you are comparing apples with pears. An Android Phone isn´t the same like a PC. Doesn´t have a HD or something equial to this in its capacity and so on. Neither Android, Firefox OS or Ubuntu Touch do have such an installer included that will install the Operating System on all devices. They all need to be ported. The same even for Windows Phone. So rather than arguing with me, go out and ask all the big players like Google, Ubuntu, Firefox or Microsoft why this isn´t the same like fo a PC.
Hello!
I own a Asus VivoTab TF600T and have Windows RT 8.1 Preview installed from a few months back.
Now I try to find a way to get the official 8.1 update but can't really get it to work.
What I did is using the Modern UI to find updates, no luck.
Then I tried the windows classic UI Windows Updates, activating "Search for other product drivers". No luck here aswel.
I also tried to find the update KB 2871389, but doesn't appear in my Installed Updates list, and the device has no more updates to install.
I did the "run/wsreset.exe" and that did not show any results.
I need to have this update in order to get the tablet back in Italian, as I sold it to an Italian friend.
Thanks!
PS: I asked the same question on the Windows Forum, but I really never see any good answers on there, so I ask the awesome XDA members who are WAY better then "wana b MS devs"
I had the exact same issue:
Follow the directions from the following link under the section marked
"I installed the preview from the Windows Store or I installed the preview using media while Windows 8 was running"
http://windows.microsoft.com/en-us/w...e-from-preview
In fact, I've released Win10 Mobile Offline Update Package V5 in China, but I've never released it in xda before.
Well... I tested OTC Updater provided by Microsoft, it will get a secret update to Windows 10 Mobile 10586.107 which is already used for my Offline Update Packages.
To download OTC Updater:
http://www.microsoft.com/en-us/download/details.aspx?id=56120
Click to expand...
Click to collapse
Here's the partial output log:
Code:
...
(ID): Found update: Windows Phone 8.1 Production Bundle - OS 10.0.13080.107 update for Nokia RM-1010_1003 CMC-CN based devices
(ID): 196 installable packages found
(ID): 1/196: Downloading Microsoft.MainOS.Production_Lang_sk-SK.spkg.20093217.cab
(ID): 2/196: Downloading Microsoft.MainOS.Production_Lang_ru-RU.spkg.20093216.cab
...
I was using Nokia Lumia 638 when testing.
I presume it will get a hidden update called "Windows Phone 8.1 Production Bundle - OS 10.0.13080.107 update for (PhoneManufacturer) (PhoneManufacturerModelName) (PhoneMobileOperatorName) based devices" to identify if the device is eligable to W10M, and the update itself provided all of the packages with extension name spkg/spku/spkr instead of cbs/cbsu/cbsr.
Right now, I collected 361 spkg/spkr/spku for the project, but far from perfect. List of packages is attached below.
What I'm going to request is:
Try to get all of the packages links of "Windows Phone 8.1 Production Bundle - OS 10.0.13080.107 update for (PhoneManufacturer) (PhoneManufacturerModelName) (PhoneMobileOperatorName) based devices".
And here's how I'm going to use a new tool with these packages as my new offline update package V6:
1. Use getdulogs command to get the device info, including it's model, codename (For example, the codename of Lumia 830 is Tesla) and packages structure.
2. Check if the phone is a cancelled prototype device, or the current OS version is supported.
3. Check if the phone is confirmed unsupported like HTC 8X, and Win 10 Mobile preinstalled device like Lumia 950.
4. Prepare required update packages according to packages structure included in the phone by copying them to a temporary directory. Remove PIN lock will no longer required, but recommended.
5. If the phone doesn't have the language you're using on PC (For example, HTC One M8 for Windows AT&T and T-Mobile don't have Chinese included), it will ask you if you want to add extra languages.
6. Push the packages in the temporary directory to your phone to execute the update procedure. Since it analyzed your phone, you needn't to worry about your default keyboard and speech if you're not using English (United States).
7. After the update procedure finished, the tool will ask you if you want to use OTC Updater to get further updates if the phone is eligable to later OS.
After V6 release, only confirmed unsupported models will get listed, which will heavily reduce the length of guide.