Original Asus Transformer Gets Experimental 3G/GSM on Jelly Bean

Android devices typically never get the kind of manufacturer support that we all want, and that’s the case with the original Transformer. The TF101 and its close cousin, the TF101G (which includes radios for 3G connectivity) have gotten ports of multiple, fully functional Jelly Bean ROMs. Unfortunately for the TF101G, the 3G radios aren’t functional in the ROMs developed for the TF101, and so anyone using those newer ROMs lose 3G functionality. And of course it’s not fair to give users the choice between losing features they paid for or staying on older software.

XDA, like always, to the rescue. One dev has figured out a way to get those 3G radios working on the TF101G. It’s still only an experimental build of Cyanogenmod 10, and it’s appropriately labeled a WIP, but if you’re the owner of a Transformer and you’re really missing 3G functionality on Jelly Bean, this is a great breakthrough for you. The dev is also planning on releasing source later for anyone to help out.

So if you’re feeling adventurous today, give the build a shot. The dev is asking for feedback, since it is still an experimental build that may have some bugs. But sometimes that’s the fun part of flashing, isn’t it?

Source: XDA

HTC One X starts getting some Jelly Bean love

HTC has made good on its promise to bring Jelly Bean and Sense 4+ to the One X this month. XDA users are reporting the roll out has begun in HTC’s home country of Taiwan. The hefty 352.87MB update (software number 3.14.709.16) will bring the One X to Android 4.1 and Sense 4+.  No news on the One S or One XL, but we remain hopeful this One X roll out is the beginning.

Of course, if you’re not willing to wait for the update to make it to your region there are other ways to get Jelly Bean early on the One X.

Source: XDA

Via: Gotta Be Mobile

[For Rooted Users Only] Trinity Kernel and TKT App Review

If you’re familiar with rooting and custom ROM’s, then I’m sure you’ve had your fair share of trying to find the right kernel to flash that coincides best with your phone and current ROM. Keep in mind that the best kernel is always up for grabs and I feel is just too subjective to definitively determine who makes the best kernel. Every phone is different, and every ROM (stock or not) is different. For me, the best that has worked for quite some time now on my Samsung Galaxy Nexus has been Trinity kernel created by XDA user Morfic. Trinity is currently available for the Nexus S, Nexus 7, (AT&T/TMO) Samsung Galaxy S III and the Galaxy Nexus.

If you’re not familiar with Trinity kernel, or if you’ve never used it, Trinity offers a kernel that’s optimized and enhanced for performance all while maintaining a great battery life. Morfic also offers several versions of his kernel all dependent to your liking, whether you want an overclocked CPU version or even an overclocked GPU version. Trinity also offers great colors for my Nexus’ SAMOLED screen. Upon first flash, you may notice a slight blu-ish hue to your Galaxy Nexus’ screen, but trust me, after a couple days you’ll get used to it and will never want to go back to stock colors. Here’s a full list of what Trinity offers:

• Offering lowered voltages
• Build optimizations
• Performance through research
• Removed wasteful debugging
• Optimized ext4 mount options
• VM, Filesystem, governor tweaks
• Color Control
• Contrast Control
• Sound Control
• Vibration Control
• 307MHz to 512MHz GPU as indicated in filename
• 1344 to 1728MHz as indicated in filename or any in between or above

With so much power and so many features/options from one kernel, there should be something else with it that gives you complete control, right? Morfic was great enough to create his own Trinity Kernel Toolbox (TKT) application that gives the user absolute control of the kernel so that he/she can change several aspects such as CPU overclock, voltages, colors and even vibration just to name a few.

Upon opening up the TKT app, you’re greeted with the “CPU” tab, in this section of the app you can set your minimum and maximum CPU frequency and choose your desired governor and I/O scheduler. This is an easy and quick way to overclock or underclock your device depending on your current needs or desires.

In this next part of the app, one can set and change the voltages of your CPU. To be honest, I’ve never touched this part of the app, mostly due to my lack of understanding when it comes to undervolting your CPU. Trinity is already undervolted by default and this just allows you to control it even further if you wish to raise the voltages or lower it even more for supposed better battery (if your phone ca handle it). One thing to keep note of: If you decide to change the default Trinity voltages, to my understanding you also have to turn off  ”Smart Reflex” which can be found in the next tab. If you’re familiar with undervolting then this is a great section of the app for you, if you’re not then I would highly suggest to just stay clear from this section until you familiarize yourself with it a bit more.

The “Tunables” section of the TKT app is what I use the most. In this section you’re able to change the vibration strength of your device and enable awesome features such as “USB Fast Charge” (this enables you to charge your device via your computer and USB cable just like it were hooked up to the standard wall charger). An advantage of owning a device with a SAMOLED screen is that you’re allowed to change many aspects of it such as gamma collors, color multipliers and the overall contrast of your screen. The TKT app allows you to change the colors of your screen to your liking. By default it’s on “Trinity Colors,” but if you wish to tinker it a little bit that best fits you, then this is an easy took for you to do so. At the very bottom you’ll see other switches: Smart Reflex, FSync and Thermal Throttling. XDA use GideonX provided a great explanation of these three: 

Smart Reflex is used to scale your voltages. Voltage will be increased or decreased when required. If you are overclocking, disable SR to have access to higher clock speeds.

FSync is a system call that can be toggled on to write buffers to disk (slow) or toggled off (fast) for performance. FSync defaults to on in the linux kernels, the option to disable it exists but it is advised to use this with caution. COMPLETE data corruption could occur if the phone crashes with fsync disabled.

Thermal throttling protects your CPU from overheating. If you are benchmarking, turn this option off to prevent throttling of the CPU that can cause lower scores. Just remember to re-enable it afterwards. Bear in mind that at 110C, the CPU will shut down no matter what. It is not advised to disable thermal throttling, however the option exists for those enthusiasts who are aware of the risk of permanent hardware damage. Please take the necessary precautions!

The very last page is the download section and gives you an easy way to download the latest versions of Trinity. The main ones I use are either the stables releases or experimental ones. To know which version you want, you first have to know a quick understanding of how Morfic labels his releases: TUV is Trinity undervolt, a kernel released with battery saving in mind. TNP is Trinity Nexus Prime, which includes options to overclock. The first number after the kernel designation indicates highest CPU slot. The next number indicates the GPU clock speed.

And that’s it folks! Trinity is a powerful, but yet battery saving kernel. Trinity is available for all Nexus devices and the Samsung Galaxy S III (AT&T/TMO). Trinity should be compatible on any AOSP based ROM such as CyanogenMod 10 and AOKP. I believe it even works on MIUI ROM’s! If you haven’t given Trinity a shot on your Nexus, I would highly recommend it. Trinity gives my “aging” Galaxy Nexus the wings it truly deserves. If Trinity interests you, you obviously have to have a rooted device along with a custom recovery such as Clockwork Mod. Here’s some benchmark scores of Trinity on a Google Nexus 7 provided by XDA user Simms22:

I’d like to thank Morfic (Twitter) and Simms22 (Twitter) for graciously helping me with the information needed to write up this post. If any of you guys have any questions, they’re always happy to help you out, whether it’s through Twitter or through their XDA thread. Below will be links to Trinity downloads, a QR code and download link for the TKT app and a link to the Trinity XDA thread. Enjoy!

Play Store Download Link

Trinity Kernel

Trinity XDA Thread

Motorola DROID RAZR M, RAZR i, RAZR HD and Atrix HD all recieve root method

As with any other Android device, root is eventually achieved. The Motorola DROID RAZR M, RAZR i, RAZR HD and Atrix HD have all received root thanks to XDA user djrbliss. The process that exploits root in these devices is called Motofail2Go and is a virtual one-click root process.

You’ll need a Windows PC, Motorola’s latest USB drivers and the program itself. If you’re brave and willing to give this a shot then head on over to the source link for instructions and more information regarding this rooting process.

source: XDA

How to install leaked Ice Cream Sandwich build on the Motorola Atrix 4G

Motorola recently announced that the Atrix 4G will not get Ice Cream Sandwich, but it appears they at least gave it a shot. A leaked build has appeared in the XDA forums, and it can be installed relatively painlessly. Now obviously this build is going to have issues since Motorola decided not to continue development on it. They may have stopped it because they felt ICS wasn’t going to jive with the Atrix 4G, or possibly it was budget constraints. We will never know, but if you own an Atrix 4G and want to give it a shot, hit the break for the instructions.

Instructions posted by XDA member drmspidi:

Files needed: Leaked Zip / MOTO-FASTBOOT app / Motorola Drivers

1)  Enter on CWM and do a wipe data/factory and cache

2)  Then reboot on your fastboot (make sure to have all motorola drivers installed on your PC)

3)  On windows CMD go to the folder you put the LEAKED Zip (ex. c:/Atrix) and the MOTO-FASTBOOT app

4)  Open the CMD, go to this directory and enter the these commands.

moto-fastboot.exe flash boot boot.img
moto-fastboot.exe flash preinstall preinstall.img
moto-fastboot.exe flash radio radio.img
moto-fastboot.exe flash system system.img
moto-fastboot.exe flash webtop vendor.img
moto-fastboot.exe reboot

5)  Now wait… It will look like its stucked on AT&T logo, but it is not, Just wait…

You should now be enjoying ICS on your Atrix 4G, and best of all MOTOBLUR will be gone!! Like I mentioned, this release probably wasn’t ready for primetime. so make sure to hit up the source link to get in on the conversation.

source: xda

Newest LG Nexus leaked pictures reveal more of its design

It sure has been an exciting, leak filled week for those following all of the newest LG Nexus news. From the first signs of the device in the FCC filings to that strange shot of a bowl of spaghetti, the leaks seem to be coming on a daily basis. This latest set of shots comes courtesy of a generous poster over at the XDA forums. As mentioned before, the LG Nexus looks very similar to the Samsung Galaxy Nexus, save for a little shine around the bezel. As far as the innards, here is what the poster reveals:

• CPU: quad core ARMv7 1.5GHz
• RAM: 2 GB
• Memory: 8GB (no SD slot)
• GPU: Adreno 320
• Android version: JellyBeanMR1
• Kernel 3.4.0
• Screen: 768×1184 (320 dpi)
• Camera: 8 MP

Although it may look the same as the Galaxy Nexus, it’s obviously packing a much bigger punch, and with that resolution and DPI, we can deduce that it’ll rock close to a 4.7-inch display. All of these specs fall directly in line with the FCC filing that we ran across last week which revealed a GSM device that’ll lack LTE capabilities which eliminates early thoughts of this device possibly being the Optimus G, but it will still hold its own. At this rate we should hopefully see an official announcement soon. Hit the break for an additional shot of the back of the device, and hit the source link for a pretty good read from other posters asking the original poster questions about the device.  

source:  XDA Forums

Sprint Samsung Galaxy S III Jelly Bean update leaked

Over the weekend XDA forum member freeza posted information about a leaked build of Sprint’s pending Android 4.1.1 Jelly Bean update for Samsung Galaxy S III devices. The leaked ROM includes Samsung’s custom TouchWiz interface. Unfortunately, it also includes a few items not quite working right like the stock browser, Google Now and some issues with the device’s gyroscope sensor. Nevertheless, it is clear that build JRO03L is close to complete, which means we may see it rolling out to users soon.

If you are not willing to wait for Sprint to make it available and you can live with the issues, you can hit the source link to pull down the leaked file or one of the custom ROMs the XDA community has already generated. Trying out any of these is subject to the usual warnings about messing up your device.

For those content to wait for the update via Sprint, hopefully this leak may help create some pressure for Samsung and Sprint to accelerate their schedule a bit.

source: XDA Developer Forum

Kindle Fire HD 7 root method

As consumers start to get their hands on a new Amazon Kindle Fire HD 7 device, some will certainly want to stretch the capabilities of their new tablet. They will be met with frustration if they decide to pursue a new bootloader as it appears Amazon has locked down the devices extra tight. XDA forum member kinfauns did some digging only to discover Amazon has employed some high security device techniques similar to Barnes & Noble’s Nook Tablet devices. Unlike a Nook, the Kindle Fire HD 7 does not have an SD card slot that can be used as an alternate boot device. Developers are exploring workarounds for this situation.

There is good news though on the root front. RootzWiki contributor jcase(OP) has determined Amazon failed to secure a known method for gaining root access on Ice Cream Sandwich devices. Using the Android SDK, it is only a matter of minutes to root the device. Just hit the source link for the instructions if you want to give it a try. Just remember though, you are responsible for what happens to your device if you root it and something goes wrong.

source: RootzWiki

Tegra 3 powered HTC One X+ device shows up at FCC, includes LTE

A new HTC device going by the model number PM63100 has shown up in the FCC database. According the documents available, this new smartphone will have LTE capability, just as we suspected based on information slowly leaking out about the device over the past month. The model number corresponds to an HTC device that appeared on the GLBenchmark site back in July that was powered by a quad-core Tegra 3 processor running at 1.7GHz. Many think this new device will be the HTC One X+, a revision of their current flagship device the HTC One X. According to some specs that were released last week by an XDA forum member, the HTC One X+ will carry 1GB of RAM, 32GB of internal storage and will come with Android 4.1 Jelly Bean installed. Based on the LTE bands identified in the FCC documents, it appears the device may be headed to AT&T, though we have also reported it should show up in T-Mobile’s lineup as well.

source: FCC
via: Engadget

Tegra 3 powered HTC One X+ device shows up at FCC, includes LTE

A new HTC device going by the model number PM63100 has shown up in the FCC database. According the documents available, this new smartphone will have LTE capability, just as we suspected based on information slowly leaking out about the device over the past month. The model number corresponds to an HTC device that appeared on the GLBenchmark site back in July that was powered by a quad-core Tegra 3 processor running at 1.7GHz. Many think this new device will be the HTC One X+, a revision of their current flagship device the HTC One X. According to some specs that were released last week by an XDA forum member, the HTC One X+ will carry 1GB of RAM, 32GB of internal storage and will come with Android 4.1 Jelly Bean installed. Based on the LTE bands identified in the FCC documents, it appears the device may be headed to AT&T, though we have also reported it should show up in T-Mobile’s lineup as well.

source: FCC
via: Engadget