Thank you very much for your insightful comments. You echo my own sentiments exactly. I've personally been extremely frustrated as I have realized how "closed" my G1 actually is. I bought it with the expectation that, as a device running an open source software stack, it would be possible for me to modify it as I desire. It's pathetic that, even as many bug fixes and enhancements have been merged to the Android trunk, I'm unable to apply them to my own phone but am instead left at the mercy of Tmobile, waiting for them push their own build out to me.
If I understand correctly, it is possible for me to run the latest Android build on my phone, but I would first need to hack it to get root access (and likely void the phone's warranty in so doing), and in the end I would loose the proprietary apps included in Tmobile's (or HTC's) _closed_ build. Where is the open collaboration and open development? I suppose open source doesn't necessarily mean open collaboration as well... but without it the whole point of open source is kind of lost. And there's my 2c. Sam On Jan 18, 4:48 pm, MyLinuxSupport <[email protected]> wrote: > You know the problem is not toolkits, developer tools, or operating > systems. The real problem is non-published drivers,locked down > booters, locked down channels and the telecom mindset. > > Symbian is much more feature rich then android but comes with lot's of > legacy baggage. The problem with Android is folks seemed enamored > with copying the Symbian legacy baggage before they get the base > functionality running (Windows95 supported a richer telephony feature > set then android does (TAPI and .WAV). > > The problem is access to the construction site, any screw driver and > hammer will do... > > Hopefully the following industry changes happen > > #1) Everyone recognizes the phone is owned by the person who purchases > it, not the manufacturer, not the carrier, and definitely not the > service provider. The phone should be built so it act's like a pc > shipped with an integrated modem. It's fine to pre-install and > configure software but it's not ok to lock it down so the user can't > modify it or replace it. > > #2) Purchasers should exert their power as the consumer and never > purchase a device with any of the following: > > 1) A locked down booter (booters should alway be open sourced) > 2) Base software (drivers and OS) that is not open sourced > 3) A device where the user is not the sole owner of the ROOT account > and password. > > #3) Open source software licensing needs stronger wording to insure > that modification or replacement of open source software by the device > owner is is never prevented by any means (hardware or software). > > Just my 2 cents... > > On Jan 17, 9:43 pm, aayush <[email protected]> wrote: > > > Some strategic inputs are welcome.... > > > 1. In the opinion of the community, will Android be able to completely > > replace Symbian? > > 2. What are the pros and cons of both operating systems. > > 3. From a long term perspetive, what do you think will be the major > > differentiating factor that will contribute to their success? (android > > or symbian) > > 4. What are the factors that might lead to the downfall of Android/ > > Symbian? What needs to be done ? > > 5. With the advent of Android, will the average mobile phone finally > > be as feature rich as a PC? Can android realize that dream? > > > aayush. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
