Now you should understand what the meaning of "open". The G1 phone doesn't give the "root" permission. You won't be able to run most of the commands under /bin. It is like you buy a PC, but you are merely a guest trying to browse the system.
Simply, the software I developed on Windows Mobile, won't be able to be ported to Android. But I would say, I will be able to port to a linux PC, which is real open. On Oct 17, 8:30 am, Mark Murphy <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > Google will release the source code soon. Can we build the source code > > and load the image into the phone? > > That is a question for the device manufacturers. HTC, makers of the > T-Mobile G1, have a good track record in this area. We will see how the > G1 pans out, just as we will see how other devices pan out over time. > > > I guess not... otherwise, how > > > google and wireless carriers can control the phone? > > And your proof of this assertion is...what, exactly? > > > Just read the news > > > that google have a backdoor in the phone so they can uninstall an app > > if they don't like it. > > For apps installed by the Android Market, as far as we know. If you > don't like the "backdoor", don't buy off the Android Market. Use one of > the alternative markets (SlideME, AndAppStore, Handango, etc.). > > > But as a developer, I do want to do anything which is possible. For > > example: communicate with the Qualcomm cellar chip to provide better > > phone experince, or capture the screen image..., or develop a video > > telephony stack etc. All these need to access to the native system, or > > even modify the driver... > > Since others have been successful in getting Android running on other > equipment, there is no particular reason you won't be able to do this > yourself...to any phones you own, make, or sell. > > Or, if theopensource Android project accepts contributions or patches, > submit your changes for review and possible inclusion in future editions > of the OS. > > > At this point, I would say Windows Mobile is a moreopensystem, since > > I can make native app or even create a new device driver... > > >??? > > It's not like with Windows Mobile you can: > > -- get the source code for free > -- deploy modifications of that source code on any device you have > access to for free > -- have a shot of getting your changes put back in the core OS to the > benefit of all > > There are two tiers to Android development. Work with the raw source > code and firmware images, and you should be able do pretty much whatever > you want, but distribution in the form of firmware and hardware is up to > you. Or, work within the confines of the SDK, and your apps will run on > all sorts of devices with a wide range of distribution options, but you > need to work within a set of constraints designed to maximize stability > and security. And none of this requires any cash outlay, other than your > time and the equipment you want to use. > > -- > Mark Murphy (a Commons Guy)http://commonsware.com > _The Busy Coder's Guide to Android Development_ Version 1.3 Published! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
