Meego and Nokia

Nokia's third-quarter Annual Report showed that Nokia would discard Symbian, bet meego, and adopt QT across the board (now Nokia announced that it would abandon WRT and use Qt as the only application development platform, in the future, all official programs and system user interfaces will be developed using QT. The existing OVI program will also be rewritten with QT .).

The problem with meego is that the thunder is loud and the rain is low. The meego mobile phone used by the first Taiwanese businessman is very important and can understand the prudent attitude. However, moblin + maemo = meego has been counted for more than seven months, enough OEM to produce an andriod mobile phone.

Unlike iOS and andriod, meego has two bosses, Nokia and Intel. Therefore, any technical route requires double check, which slows down the process. Open source is a feature of meego. However, history has proved that not open source is also an outstanding product, and meego, which wants to keep up with iOS and andriod, will spend extra time on open source. Time is efficiency, and time is money. Start with innovation, keep up with leading, and slow with everyone else. The advantage of open source is that everyone can understand the underlying layer, modify, rewrite, and contribute. But what is the purpose? If andriod has already done a good job at the bottom layer, you don't need to worry about it. You can concentrate on your design, develop your applications, push them to the market as soon as possible, and release them as soon as possible, what's wrong. Until now, we have targeted the underlying layer, including chip manufacturers and software companies, which have truly joined the meego camp. Meego can attract the following people:

• This is a natural law for enthusiasts of embedded operating systems.
• The platform needs to be controlled, and the operating system needs to be mastered for some purpose. These parts can benefit from the contribution of MeeGo to Linux, without the need
• Box devices, such as home gateways and set-top boxes, are obviously different from Nokia's targets.

It is unclear how MeeGo coordinates the LPIA between ARM and Intel. Intel's LPIA has to sacrifice some computing power for low power consumption and other problems. The difference in chip processing power is not important. After all, we didn't edit offic and ppt on mobile phones, the size also determines the user's usage. For video, it can be solved through an auxiliary graphics processing chip. Mobile phones are the portable products of life, rather than office computers. However, Intel's LPIA x86 mobile phone has never seen it. It's just a flicker, And it's impatiently waiting. It's already suspected that there are flaws in the hardware design. After all, Intel hasn't involved such consumer electronics before, the only xscale is also available. When Intel handles all these problems and the new medfield chip is available, is it still x86? In principle, the moorestown chip is already available for smartphones, but no real products are available. In linux, we use QEMU as the VT and find that the netbook version can be loaded, but the handset version (mrst) cannot be loaded ), it seems that mrst is already significantly different from traditional x86, so that QEMU cannot simulate it.

In any case, MeeGo needs to prove its position in the smartphone market as soon as possible.

Google is accelerating. In 2010, they shortened the release cycle of many products and posed new challenges to companies that want to lead the competition and be competitive in the market. Google has released 5 to 6 system upgrades in a year. It seems that Google is too fast on Android. This is true without a doubt, but Google and Android are also slow in some ways. If you look at the mobile device battlefield, Google will never wait for anyone. Mobile phone manufacturers cannot keep up with a large number of versions. Sony Ericsson released the Android August 2010 Xperia X10 in 1.6. Dell's Dell Aero launched in August 2010 runs Android 1.5. Some previously released devices are equipped with Android 2.1, such as Motorola Droid X released in July 2010 and htc evo released in June 2010. At the same time, Google has to face the impact of API changes by different manufacturers on developers. They handled the issue through the CTS (compatibility test) project. The differences between Android versions are not just some additional functions-some changes are structural changes, affecting developers and undermining the compatibility of different versions. For example, the addition of Stagefright is a new media architecture released with OpenCore of Android 2.2. Will Google continue to develop OpenCore or give up in future versions? Http://www.ifanr.com/23934

)

Apart from version splitting, different models are the second layer of Android splitting. There are three layers: (functional and API) to achieve split, user experience split and code split. If Google wants to regain control over Android, they need to solve the five layers of Android split. Http://www.ifanr.com/23934

)