- Based on CM10.1 source
- Built with Linaro GCC 4.7 with optis
- Ramdisk tweaked (init.d support, unsecure)
- OC up to 1.8Ghz
- GPU OC to 480Mhz
- Undervolted
- Trinity colors
- Defaults to tweaked ondemand governor and deadline scheduler
- USB Fast Charge (credit to imoseyon and chad)
- Removal of mpdecision, uses tweaked auto_hotplug driver (credit to thalamus)
- Removal of thermald
- fix_permissions added to zip

To do:

- Voltage control

To install (no need to wipe anything):

- Download .zip below and place on your internal or external sdcard
- Reboot into CWM or the recommended TWRP 2.3.3.0
- Flash .zip
- Reboot

Download latest 2013-02-02 – BMS #24

Here’s another update of my BMS AOSP 4.1.x Jellybean kernel for the Verizon Samsung Galaxy S III.

Features:

• Overclocking up to 1.8Ghz
• Undervolted on all frequencies for battery savings
• USB Fast Charge (ex: gain max mAh on a laptop usb port)
• Lazy governor added
• *new* abyssplug governor added
• *new* row scheduler added

Requirements:

• Rooted and Unlocked bootloader (guide)

Since this is an initial release, not many features are added just yet. Once a general stable build has been achieved, more tweaks and additions will be included.

This is flashable zip so you may flash it with either Clockworkmod or TWRP recovery. Remember, this is for AOSP based (CM, AOKP, Slimrom, etc.) roms. You can try flashing it on a Touchwiz rom, but you’re on your own with that

Download the latest release here.

Since getting my Nexus 7, I’ve been using it daily for just about everything. I’ve gotten to the point where I stopped opening my laptop after getting home from work. It really is that useful of a device at this point.

Although the size and performance is great, there are some glaring quality control issues that Asus has let slip thru their factories. Aside from the very prominent speaker crackling issue that plagues both the 8GB and 16GB models, there’s also the dreaded screen lifting problem. This lifting problem is pretty much what it sounds like — the screen is lifted slightly above the bezel. This usually occurs on the left side of the screen, so the glass will be just that slightly higher than the other side.

There have been homebrew fixes all over the net, but the best I’ve seen is the removal of two screws. The reason I say it’s one of the best is because Asus may have adopted this as their fix. Small hardware spiel to follow.

To get the tablet together in one piece, many small screws are used to keep the PCB attached to the bezel. Due to the design of a tablet, the glass is always on the other side. So when the PCB is screwed down and the distances are not calculated correctly, it pushes onto the other side thus raising the glass. This is entirely not scientific and no testing has concluded this is the case, but that’s my best guess as to what’s happening.

So earlier, I said Asus may have adopted this as their “fix” as well. There are currently (as of this writing) three hardware versions of the Nexus 7. You have the C6O, C7O, and the C80 models. They are all pretty much identical, except for the fact that the C8O is missing two screws that are present in the previous two models. You can check the version you have from the SSN listed on the bar code sticker on your box. It’s also plastered on a sticker on the inside of the back cover. So let’s say you have the two older models and you want to remove the two screws, well, keep on reading.

Power down your Nexus 7 first. Then using a guitar pick (or something similar), pry the back cover off your Nexus 7. Work very slowly and you’ll prevent any locking tabs from snapping off. Next, using a small precision screwdriver, remove the third and fifth screw on the right side. In the pic attached to this gallery, I have my screwdrivers pointing to the screws you need to focus on.

Once you are done removing the screws, snap the back cover back into place. And just like that, you have a C8O “version”. Hopefully this helps, the jury is still out on this one as to whether this will keep this issue fixed.

My latest gaming addiction has been the NBA Jam release on Android. It was recently on sale for 99 cents so I couldn’t resist. The updated graphics and zany gameplay makes it just as fun as the original.

There are just two quirks that I really wish this game didn’t have. The first small annoyance is that it always checks for updates on start. So if you are not connected to a cell tower or on wifi, it pretty much stops.

The second more serious issue is the inability for it to function at anything but the default 48dpi navigation bar icon sizes on the Ice Cream Sandwich and Jelly Bean OS releases. So if you have a custom rom and you plan to make or flash edits that shrink or modify the size of the navbar, NBA Jam will crash back to your homescreen or give you an ambiguous 5002 error code.

As always, make a nandroid before you do any kind of editing. You may never know what app your mods will break until it’s too late.

If you tend to crackflash often, then you probably use Titanium Backup and you’d want to know the easiest way to back up your SMS/MMS as well as your call log. These items are not retained when you go from rom to rom nor are they backed up when doing a user data backup in Titanium Backup. Here’s how you can do it on a set schedule so you never forget.

1. Open app drawer
2. Open Titanium Backup
3. Press the menu radio button
4. Select “Filters”
5. At the bottom press the “Create label” button
6. Name your label whatever you want
7. Press the “Add/Remove elements” button
8. Check the “[SMS/MMS/APN] Dialer Storage x.x” checkbox (version x.x numbers may vary)
9. Check the “[CONTACTS/CALLS] Contacts Storage x.x” checkbox (version x.x numbers may vary)
10. Press the “OK” button
11. Press the “Save” button
12. Press the back radio button
13. Select the “Schedules” tab
14. Press the “Add new schedule” button located at the bottom
15. On the schedule that just appeared press the “Edit” button
16. On the top combo box select the arrow to pull down the menu. Select the “Backup all system data” option
17. On the next combo box that says “No filtering”, click the arrow to pull down a menu. You should see your label you created. Select your label.
18. Select the time you want your backup to take place
19. Select the days you want your backup to take place
20. Press the “Save” button
21. Check the “Enabled” check box to enable your schedule
22. Now Titanium Backup will automatically backup your messages at the specified time and day or days.

When you are ready to restore on your new rom, just search for Dialer Storage and Contacts Storage and restore the data only. Perform a reboot and you should have everything back. Just be careful when going from major OS version updates (ex: Gingerbread to Ice Cream Sandwich). You may encounter some weirdness, so be prepared to restore a nandroid or reflash if something doesn’t take right.

[via XDA]

The wait is over, Temple Run is finally available for your Android phone! Head over to the Google Play store and start downloading.

Although the Nexus S has been available on the market now for over a year, it’s actually a bit confusing for first time users to unlock and root the device. Give it a try, do a search and try and find the right adb and fastboot drivers for Windows 7 64-bit. I’m willing to bet it’s not as easy as everyone claims it to be. For some reason, fastboot drivers give 64-bit users a world of trouble in terms of acquiring and installing.

Since I went back to using my Nexus S on T-Mobile, I decided to post a quick how-to on getting this done.

Download the following zips before beginning:

Since I have the I-9020T model for T-Mobile, this guide will support only that version. This most likely will not work for the I-9023 LCD version or the D720 (Sprint 4g version), however, it should work for the I-9020A (ATT version).

Let’s begin…

Extract the zips to your Desktop, or anywhere else you feel comfortable with.

ADB Drivers

Connect your Nexus S (NS) via USB to your computer, it should trigger your Windows 7 to prompt for drivers. Point the installation to look in the ADB drivers directory that you extracted earlier. You may get a warning about driver signatures, just accept it and let it install. To check if ADB drivers have been successfully installed, open a command prompt and navigate to the ADB_Fastboot directory that contains the adb and fastboot executables. Issue the command “adb devices” and it should show your connected device. Keep this command prompt open, we’ll need it again in the next step.

Fastboot Drivers

Unplug the USB cable and power down your NS and then power it up again by holding Volume + and Power. This should bring you to a black screen with some information about your NS. You’ll also be greeted by the familiar Android mascot.

Plug the USB cable back into your NS and it should now prompt for another set of drivers, this time for fastboot. Navigate on your computer to the fastboot drivers you extracted earlier from the zip you downloaded. Again, you may be prompted with warnings about driver signatures, accept them and let the drivers install.

Once the installation is done, go back to the command prompt you had open and type ”fastboot devices”. If your drivers were installed correctly, your device should now be listed in a similar fashion as the previous adb devices screen. Keep this command prompt open, we’ll need it again.

Unlock Bootloader

Before we go ahead and unlock our bootloader, make a backup of everything you deem important. This next step will wipe your device clean. Please make a BACKUP!

With an unlocked bootloader, you’ll be free to install and flash just about any recovery, radio, and rom you wish. There is now no need to wait for Google to push any updates to you, just head out and grab the latest update and flash it yourself.

To unlock the bootloader, go back to fastboot mode (Volume + and Power) and then use the command prompt to type “fastboot oem unlock”. You’ll be prompted on your NS with a warning and confirmation to unlocking the bootloader. Acknowledge it and it should wipe and unlock your device in a matter of minutes. When it reboots, you should see an lock symbol below the Google splash screen. This will let you know you have unlocked the device. Again, keep the command prompt window open, we’ll need it for the next step.

Flash a Custom Recovery

A custom recovery will allow you to flash a custom rom or kernel on your NS. It also has the VERY useful nandroid option to make an exact backup of your device. This is useful in case you flash an update that causes problems on your NS. A simple nandroid restore and you’re back to where you were prior to the bad flash.

Find the recovery image in the recovery directory that you extracted from the zip earlier. Move that image to the adb_fastboot directory where you opened up the command prompt. Now in the command prompt, type “fastboot flash recovery recovery-clockwork-touch-5.8.0.2-crespo.img”. This will flash the latest Clockwork Mod Touch Recovery. You should see some bytes flashed to your NS and it should be done in about five seconds. Congratulations, you’ve successfully made your NS that much better.

Custom Roms

It is highly recommended before you do anything to make a nandroid backup in the custom recovery. You can then download any roms or kernels and try them out on your NS. I highly recommend Android Open Kang Project (AOKP). It has more options and customizations than any other ROM out there. Enjoy!

I’m sure you’ve come to wonder what all these kernel governors are and what their differences to your performance and battery can be. Here is an excellent thread describing some of the more popular ones. My current running combo is the SIO scheduler with Intellidemand on Speedy-7 on my Nexus S.

Here’s a quick tip on how to look up a saved wifi password on your Android handset. Let’s say you need to flash a new rom but you don’t have a password written down for a wifi access point you frequently use. Use any file explorer on your Android handset and navigate to the /data/wifi directory and view the bcm_supp.conf file. This is just a basic text file that contains all your wifi access points and passwords that you’ve used previously.

Make a backup of it or simply write down the password you need, enjoy!

This year the Galaxy Nexus was released a day earlier than the Nexus S. As you know, the phone was released exclusively on Verizon Wireless after much delay. All evidence points to the fact that the Galaxy Nexus was ready to launch by the end of November, but Verizon waited to give the Rezoud and the RAZR more time to sell. To make matters worse, the Galaxy Nexus is the first Nexus device to have a carrier’s software preinstalled. Speaking of software, the Galaxy Nexus doesn’t have Google Wallet installed on it. Sure, it can be side-loaded, but it’s just more evidence that Google is not in control of this device. Unlike every other Nexus, the Galaxy Nexus does not have Google branding on the back; instead Verizon’s logo rests above their 4G LTE logo. If there was any doubt about whether or not this was Google’s phone, that should put the debate to rest.

Yup, the Galaxy Nexus isn’t a true Nexus in this writer’s eyes because, well, it has carrier software preinstalled and it doesn’t say Google on the back cover. I’m usually on the same wavelength with the dudes over at DL when it comes to opinions on handsets, but this piece is awful. Seriously? Your main gripe is that it has a few carrier apps and it doesn’t have the Google logo on the back? It’s a Galaxy Nexus, load a new rom, instant carrier-free app experience. Buy a case and cover your phone, who cares what it says on the back cover. Are people complaining just to complain? The Verizon users should be happy they got a totally unlockable phone on their network.

This opinion piece just sounds like it’s there to fill space on a slow pre-New Years day.