Slashdot Mirror
Firefox OS 1.3 Arrives: Dual SIM Support, Continuous Autofocus, Graphics Boost
An anonymous reader writes "Mozilla today released Firefox OS version 1.3 to its partners for implementing in their smartphones. There are many new features for both users and developers, and the first phone to feature them is the ZTE Open C, which is available for sale as of today on eBay. First and foremost, Firefox OS users can expect dual-SIM dual-standby (DSDS) support, which gives you two lines on compatible phones, a popular feature in emerging markets. DSDS lets dual-SIM devices individually manage two different SIMs for calling, texting, or data through the 'SIM Manager' interface."
company phone & personal phone?
Mod parent up
Having lived in an emerging market (Romania) for six years, I knew several people who would carry around multiple feature phones, or a smartphone and a feature phone, just so they could use prepaid SIM cards from two different networks, so they could call all of their friends and family "in network".
I was using a prepaid SIM from Orange, and for 5 Euros/month, I had 3000 minutes/month to other Orange numbers and 100 minutes/month to other networks/landlines. As it happens, everyone I wanted to call was on Orange, so I was fine. However, I knew people who would pay 5 Euros/month to Orange, and another 5 Euros/month to Cosmote. For 10 Euros/month, they had effectively unlimited calling to everyone they wanted to call, but needed to carry a second phone (or swap SIMs to call on the correct network).
Today we have quad core multi-ghz CPUs with gigabytes of memory and 1080 displays. Having installed Linux from floppies on hardware orders of magnitude less capable is it now really too much to ask to have UI execute from a real non-nerf'd operating system?
Why can't I compile and run whatever software that will run on desktop on my phone?
The real performance bottlenecks have to do with RAM, and just-in-time compilations (though that is often cached). Even number-crunching apps can use asm.js to approach native performance, and even if the gap isn't fully closed there just aren't many apps that require that much performance for a simple smartphone. If you wanted the best possible performance you'd be wasting much time, because it's not JS that's causing most of the performance issues on something like FirefoxOS, but simply the RAM usage and the graphics stack being a bit slipshod in places (though both aspects are being actively improved a lot in FirefoxOS).