The Oppo N1 went on sale last week, but not the very anticipated CyanogenMod version. Well good news for those of you waiting to get your hands on one because it will be available starting December 24.
They didn’t want to release the phone until is passed Google’s CTS and CDD certification programs, which it did. This means that it has access to Google’s official apps as well as the Play Store.
Oppo didn’t tell us the price, but we are assuming it will cost the same as the regular model, which is $599.
sources: @Oppo / CyanogenMod
Cyanogen’s future is looking pretty good at the moment. It was three months ago when the company formed with $7 million in funding, but it wasn’t nearly enough for their plans. They just secured another $23 million from Andreessen Horowitz, which could help them bring CyanogenMod to TVs, wearables, and cars.
However, there is still a lot of work regarding mobile phones and tablets. Their ultimate goal is to give mainstream consumers the power and freedom to customize their device easily. This will most likely happen in late 2014 or early 2015.
Today the CyanogenMod team announced their secure messaging system that is being integrated into their CM 10.2 nightlies (will soon follow into their CM 11 branch). Dubbed as WhisperPush, the system-wide secure messaging system is powered by TextSecure. This basically encrypts your SMS messages both locally and over- the-air when sending to other TextSecure users.
The source is of course made available to the public. Check out the link below for CM’s official word on the matter and for further information.
A couple days ago CM11 M1 was released to most Nexus devices, but we didn’t see nightly releases enabled for others. Well CyanogenMod has now enabled nightly releases of CM11 for every device that supports it!
Android 4.4.1 has also been merged into the code stream of CyanogenMod 11, so CM updates are up to date. Device maintainers for CM will perform these updates for their respective devices. You can find a full list of devices supported by hitting the source link.
Cyanogen has already made available the first Milestone release of CyanogenMod 11, which is based on KitKat. It’s only available for Nexus devices, but only the ones that are “actively AOSP supported”, which means the Nexus 5, Nexus 4, Nexus 7 (all variants), and Nexus 10.
This is a new method for the Cyanogen team as they usually release Nightlies at this point, but not allow bug reports. While, M1 will only be available to these select devices, users will be able issue bug reports, although they do feel things are pretty stable at this point.
Other devices such as the Galaxy Nexus and non-Nexus devices will be part of the Nightlies, which should be available in the near future.
source: CyanogenMod / Downloads
When Google announced KitKat, they confirmed that the Samsung Galaxy Nexus had officially reached the end of its support life and that it would not see the update from 4.3 to 4.4. Of course, the entire reason many people buy these Nexus devices is so they don’t have to settle for “official” updates and can take care of it themselves, and the Galaxy Nexus is no different. Thanks to developer PlayfulGod on XDA, the Gnex finally has a fully functional KitKat ROM available so it can join the Nexus 4 and Nexus 5 with up-to-date software.
The ROM is built off of Cyanogenmod 11 source, and every major thing works, including data, phone calls, camera, etc. There are a handful of bugs left to iron out, including panorama being broken and a graphical glitch when taking screenshots (although the screenshots turn out fine) but neither of those things are going to affect the ROM in a major way.
If you’re interested, you can find the ROM below. Remember, unlocking your device and flashing custom software can void your warranty, so flash at your own risk.
Upon the official release of CM 10.2, the CM team has announced that they will cease development of CM 10.2 and mainly focus on CM 11 (KitKat). They will still provide nightlies and updates for 10.2, but will mainly just be bug fixes rather than new feature implementations.
While Jelly Bean is still alive in the CM world, the ICS branch will officially be retired and no longer continued.
One of Google’s selling points on KitKat was that it could run on low-power devices and phones with as low as 512 MB of RAM, but no one realistically expected extremely old devices to get official KitKat support. Of course, that’s never stopped Android’s developer community, and as of today both the Nexus One and Nexus S (yeah, remember those?) have unofficial KitKat ROMs. Best of all? They actually run pretty well.
Previously (as in, before today), your warranty on your Motorola device would be voided if you requested the Bootloader to be unlocked. It was an evil, but perhaps a necessary one.
But today, it seems that change is in the air. If you request an unlock bootloader code for your Moto device you can keep your warranty. Not only that, but Moto will be posting the return-to-factory software images. Awesome, right?
This news serves as even more proof that Motorola has become more and more “Google-fied” since it was purchased by the search giant.
Moto will also be reinstating all warranties to Developer edition devices that were purchased from 2012-2013.
Remember, this information is only for Developer edition devices, and it’s definitely not expected that they’ll do the same for other devices. Still, great news.
Source: Moto Blog
Frustrated at the lack of Galaxy Gear device compatibility? You might be interested in a new ROM that’s popped up on XDA for the Gear that not only allows it to connect to any Android device via Bluetooth, but also adds in the Play Store as well as a ton of other features.
The ROM throws in CM 10.2′s web browser so you can freely browse the internet on the device, Bluetooth tethering for internet access for the smartwatch, a native email client, and it’s completely rooted. It’s definitely a huge step up from what Samsung was offering in the device, so if you’re interested, you can find the files and instructions at the link below.