CyanogenMod (CM) and the Android Open Kang Project (AOKP) are the two most feature filled ROM’s that you can find in the custom ROM world. With CM10 Nightlies having been released just a couple of days ago, it was only natural for the AOKP team to follow suit and release their first official build of Jelly Bean AOKP. There’s far too many features that AOKP provides to list them all, but here’s the popular ones that you can expect:
- Notification Toggles
- Lockscreen tweaks (no custom targets yet)
- Navigation bar modifications
- Custom kernel performance options
- LED colors
- Notification wallpapers
- Phone ringer modifications (Flip call to silent, silent/vibrate when headphones are in)
- Plus more!
You can head on over to the source link for a download link, the device maintainer list and their Gerrit page. Let us know if you’ve given AOKP a shot and tell us your experience with the ROM!
source: AOKP Google+
Earlier this week, Jean-Baptiste Queru, Google’s Technical Lead on the Android Open Source Project (AOSP), announced a new experiment he was starting up. Up to now, the AOSP has focused on Nexus class devices. As Queru explains, AOSP was setup so that in theory it would be possible to plug in files for additional hardware targets. Thus far though, the theory has not translated into practice. Queru hopes this new experiment may change that and help identify and eliminate hurdles present in the theory as it moves to practice.
The target of the experiment is Sony’s Xperia S model. Queru selected the LT26 as it is a fairly powerful device currently on the market, has an unlockable bootloader, and a manufacturer that is friendly toward open source projects and philosophy.
If you are interested in helping out with the effort, check out the source link. Otherwise, keep an eye on this experiment as it may yield positive results not only for the Xperia S, but for other devices as well.
source: Google Groups
via: The Verge
The CyanogenMod team has formally announced that official CM10 nightlies will be available starting tonight. For rooted users, this is Christmas time as CM ROM’s are the current king when it comes to the Android modding community. The devices receiving the CM10 nightly treatment will include, but are not limited to:
- The US SGS3 variants
- The Galaxy Nexus variants
- The Nexus S varaints
- The Nexus 7
- The Transformer and Transformer Prime
- The SGS1 variants (Vibrant, Captivate, International, and i9000b)
- The SGS2 i9100g
- P3 and P5 tablets
According to the CM team, “Other devices will join the roster as they become ready and gain their maintainers blessing for nightlies.”
Just keep in mind that you, and you only, are responsible for anything that were to happen to your device if you decide to delve into flashing custom ROM’s. With that said, enjoy and let us know your experience with the CM10 nightlies once they become available later tonight!
source: CM’s Google+ Page
One of the biggest advantages of owning an Android device is having the ability to customize not only the interface, but the system settings itself. Part of that includes flashing a custom kernel, which can bring all sorts of enhancements to a variety of levels. Such settings include specifying voltages, underclock or overclock speeds of the CPU, custom color settings. You get the idea.
XDA Senior member clemsyn has created a modified kernel for the Nexus 7 called the Elite Kernel, which is a modified version of the Motley kernel originally created by XDA Senior Member _motley. Hit the break for the list of tweaks this customized kernel brings.
Hey modders, devs, and hackers! You know how you keep that “USB Debugging” option checked in settings? Sure, it’s useful when you need to root a device or test an app you’re developing, but you might want to consider unchecking it when not using it.
XDA developer M.Sabra says that anyone with a little ADB knowledge can easily hack Android’s pattern unlock, essentially getting access to your entire device. Apparently it’s not that difficult to do either. Root isn’t even required.
We won’t go into detail here on how to do it, but hit the source link to find out how easily your phone can get hacked if you lose it. Don’t believe your pattern gives you total protection.
The second I saw this story on the XDA thread, I envisioned many Verizon Samsung Galaxy S III users giving Verizon the proverbial middle finger. This locked bootloader issue with Verizon’s Samsung Galaxy S III has certainly made a full circle. It started off with many angry customers when Verizon formally announced that the bootloader will be locked on their Galaxy S III, but soon after there was hope as a couple of miss-informed Verizon and Samsung reps told various people that an update for the S III would be out soon that would unlock the bootloader. Verizon quickly denied that rumor and left us all with the hopes of XDA soon finding a way to crack Verizon’s lock on the bootloader.
Well folks, that day has come as the XDA developer by the name of AdamOutler has released instructions on how to unlock your Verizon Galaxy S III’s bootloader. Before I give you all the instructions, it’s important to first read AdamOutler’s precautionary statement first:
Let me make this clear. If Samsung updates your device’s bootloaders, using this tool could potentially brick your device. Once you apply this, never accept a factory update without first flashing the Odin Packages in the Original Post of this thread. As a general rule, you want to be the last guy to apply any Samsung update. Run custom.
As of the date of this posting, this works great on Linux and it should work wonderfully on Mac too. If you’re using Windows, I recommend downloading Windows Ubuntu Installer(WUBI) to install Ubuntu from within Windows.
First you’ll need to download the file needed for this:
XDA member bongostl has posted a step-by-step guide for modifying your Nexus 7, or any tablet for that matter, to enable outgoing and incoming calls through Google Voice. This requires the editing of system files, so your tablet needs to be rooted. What this method does is make the tablet think it’s voice capable, which allows dialer app voice+ to connect through Google Voice and place a call.
Incoming calls will be handled by any SIP app, such as CSipSimple, which requires you to also set up a call number and routing using other online services such as callcentric and ipkall. Couple all that with Google Voice, an edited and recompiled framework-res.apk file, and the flashing of an update.zip, and you’ve got yourself a really large tablet-phone in 16 quick and easy steps.
Or you can download GrooVe IP from the Play Store and skip all the rest.
Ok, that was snarky. To be fair, bongostl’s method has the advantage that you can still receive calls in your Gmail on your computer, whereas with GrooVe IP, it’s one or the other. But seriously, to me this all seems like way too much of a hassle with too many potential points of failure to really be worth it for most people.
Bottom line: Hackers and tweakers only. Everyone else just get GrooVe IP.
The CyanogenMod team has started the process of releasing stable builds of CM9. The first device to be released is the Google Galaxy Nexus (Maguro) which was released earlier today. Indications are that release was a bit premature and a very minor update will be rolling out later this evening. Builds for other devices are also anticipated to start appearing on the download page.
CM9 is based on Android 4.0 Ice Cream Sandwich. The stable builds represent the end of development on CM9 as the CyanogenMod team transitions to work on CM10 based on Jelly Bean. Hit the source link if you are interested in grabbling CM9 for your Galaxy Nexus or to keep an eye open for a release for your device.
source: cyanogenmod downloads
While the Android platform tries to be the best OS in the game, there are minor problems that plague it such as rampant piracy issues—- specifically with developers of various apps in the Play Store. While Google has addressed piracy issues with each new OS release such as with Jelly Bean’s App Encryption, its solution has ended up being worse for developers. Apparently developers are claiming encryption (the location of installed and encrypted apps from the Play Store) makes their apps completely unusable because account information is removed after a device reboot. Because of this— Google has disabled the security feature for the Play Store on Jelly Bean smartphones and tablets.