Why are mobile OS'es still tied to vendors? [closed] - operating-system

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 12 years ago.
Modern mobile phones have come far since their beginnings over 30 years ago. Especially smartphones, which are essentially miniature PC's, capable of all the same things, if at a bit slower pace. So if cellphones have followed in the footsteps of PCs, why hasn't their software? Why can't I take my mobile phone and install the latest edition of Android on it, like I install the latest edition of Windows or Ubuntu on my PC? Is this solely a marketing decision (market segregation, forcing to buy a new phone if you want a different OS, etc.), or is there some fundamental problem preventing the good old OS+driver model?

Probably because there was no need for it. A cellphone is like a toaster. Nearly nobody want’s to change the firmware of a toaster (except for Cylons). Most people simply want to use it.
Interchangeable firmwares mean additional work for the vendor which can’t be justified if nobody will use this feature.

You can do that, by rooting your phone. In fact, it is possible to put Android onto iPhone (and theoretically possible to do the opposite). It's not more widespread because the phone and software are tied together very tightly, that's why you never have to worry about drivers. For you to change the operating system and perform other tasks that require similar levels of access and modification, it requires manufacturers to update all those specific details, hence it is rare. In the past there have been phones (such as the Omnia) where the manufacturer provides these updates for owners.

Related

How to get started writing SIP / VoIP based software [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I need to add some SIP based functionality to my company's Windows based software, allowing the user to call extensions and receive calls from extensions registered with a SIP server. Essentially I'll be creating a simple soft-phone. The software might be running on separate networks, so NAT, firewalls and STUN servers are considerations.
I'm wondering if others have done this sort of thing and if so do you have any recommendations on how to get started.
Should I write my own SIP stack from scratch?
Should I consider using OPAL? It looks ideal, but they only list a single company that they know of using their library, which concerns me.
Should I consider other 3rd party libraries?
You should avoid to write your own implementation because this voip is a huge and complex topic. I would also not recommend OPAL (that is already outdated).
Just search for "SIP SDK" and you will see a lot of ready to use working solutions then just choose whichever seems better for your needs.
Opal has been around for years - and the code has been provided to various commercial users.
The code has been tested in many harsh environments.
Good software is like wine - it matures with age. Opal has matured well.
The library is extreme C++ - I hope you know C++ well.
Use Opal - cause when they ask for h.323, it will be easy.
The code has been tested on many compilers - (win, gcc, mac) and each compiler can be regarded
as a new pair of eyes, or another CPP quality check system.
http://www.opensips.org/ is a good choice in working for a server side implementation.
If you are to make a SIP client, try searching for webphones.Things with javascripts are cool.
here is a list:
http://www.voip-info.org/wiki/view/Open+Source+VOIP+Software

Which is the best OS for web application development? [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
Which is the best Operation System suited for web application development in various platforms like JAVAEE, PHP, Ruby-On-Rails, Perl, Python, if I have missed out anything then that too etc. including testing front end and business logics, version control system like svn/git etc, planning, reporting, life cycle management etc etc? In short, need to cover all aspects for web application engineering.
I have used both Windows and Linux and have felt Linux is better for its great command line capability. I have no idea about development in Mac. My experience in web application development is limited to 3 years and I just need expert opinion.
Linux is great option because of the following:
Software/Tools availability
Relatively easy troubleshooting
Easy to find answers on any question/error code you get
Great package management (Debian/Ubuntu and derivatives)
Friendly community
and many more
About the machine configuration more RAM, more HDD space, better CPU, ... :). In the company I work, every in-house developed piece of software is developed and hosted on Linux. I really can not remember of any issues we've had, except minor hardware related ones.
Linux is always a best bet on development, but of course you'll want available testing platforms with Windows and Macintosh, as well as other Unix bases for testing to make sure that your product functions appropriately under all configurations.

IPhone over Android and vice versa [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
I develop applications on both IPhone and Android. As a part of my organization's Technical Session program I have myself delivering the next session on iPhone or Android. Getting the session made me start comparing both technologies, which believe me, is really a tough job. As a programmer in both technologies I often think how will the Application seem to be if I used the other one. Which further makes me list out pros and cons of both.
Android ahead of iPhone:
There are couple of factors where Android steps ahead of iPhone.
Multiple apps at same time
Information visible on home screen
Better notifications
Hardware flexibility
iPhone ahead of Android:
Following are the factors:
UI Smoothness and Consistency
Language support
Accessibility options
Battery life
Resource efficiency
Hardware quality
Better App Store
However, as a programmer, I want my session to be more of technical rather than a being a general overview of both technologies. For which I need some help. For instance Android's memory management is way ahead of that of iPhone's. On the other hand IPhone's UI has no comparison at all.
What more (technical) points can I include in my session? Also, kindly correct me if I am wrong somewhere above.
As far as the UI goes. I'm interested (as a programmer) to understand why exactly you consider iOS to be superior because in android the layouts that can be used are ever expanding and can be customized from the ground up where as in iPhone if you step outside of Apples box you get booted from the app store.

How often do you Upgrade your Bug Tracking System / Software [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I am using Fogbugz as my Bug tracking software, and was thinking on a schedule so that I can upgrade my Bug tracking software once in a while according to that schedule.
I was just curious on how others are doing their upgrades, and how often.
It would also be nice If you share on what basis you schedule the frequency of your Bug tracking software's upgradation.
Thanks.
I check for the changes implemented in any software and see if the new feature set and/or fixes provide benefit to our development team. In the case of FogBugz, I have not had a single problem caused by the upgrades. Fog Creek has done a remarkable job at testing their product before it hits our system.
I am not saying FogBugz is perfect, but it is close. I cannot say this about every software vendor. I really dislike when software installs screw up the workstations or the server. I use to be a jump on the new release as soon as it ships kinda guy. But too much blood loss being on the bleeding edge these days so I now wait a little bit and see who else has success or failure.
By the way, this is a business decision, not a technical decision. And I make it on a case-by-case basis depending on the reliability of the vendor and the level of importance the software makes to my company.
Rick Schummer
Whenever we need to. If running an older version still works, then thats what we'll do. If a new version has features that would aid development, then we'd upgrade after the next release of our product.
If we were to upgrade just because one became available, the response is usually that the bug tracking software is not as important as fixing the bugs themselves, and that it could wait.
There is no software free of bugs, even the bug tracking softwares.

I want to learn all the internals and structure of the iPhone [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
Does anyone know of a website or resource to learn about important files / directory structures or data within the iPhone?
Soon i'll be learning to develop iPhone applications and I want to know everything about its internals, if anyone knows a resourse that would be great.
What I want to do is.
How to access the database.
Where system settings are stored.
How to gain access to the Mobile Comm Server
etc...
All the information you'll need is available from Apple in their developer site.
File structure and other internals matter less than you'd think, as your app won't be able to get outside its sandboxed resources (unless you're writing jailbroken apps).
Begining IPhone Development by Jeff LaMarche and David Mark
You keep mentioning database. What database are you talking about? In your last question about gaining access to a database, I assumed it was a database that you had as part of your app. The iPhone OS probably has many databases, including the Contacts database, the songs database, the album photos database, etc. There are some limited ways to access this data, but they're on Apple's terms and I have to emphasize the word "limited".
As a previous respondent said, the best place to start is at Apple's iPhone Dev Center, but you won't find anything on jailbroken phones, accessing any of the cell or communication systems, nor the system settings, among many other things.