February 9, 2013 By: Will Verduzco
By now, you’ve no doubt heard of Paranoid Android. In fact, there’s a good chance that if you own the Galaxy Nexus, Nexus 4, Nexus 7, or Nexus 10; you’re either running the ROM yourself or you’ve given it a try in the past.
For the few unfamiliar, Paranoid Android’s defining characteristic is what they call Hybrid Engine. Contrary to what many believe, this is not “tablet mode,” though that is one of many things that can be accomplished using Hybrid Engine. Rather, Hybrid Engine allows you to select both dpi and layout on a per-app basis. Rather than being forced to modify the look of your entire device, you can optimize your applications to what works best for each and every one.
A new and important feature that has come to light in the recent beta builds, and now sees light in the official release of PA3 is the PIE control system. What this allows one to do is to disable onscreen buttons and use a swipe gesture to access various common functions, thereby freeing up valuable screen real estate. The menu can be seen in the header image above, as well as the video below.
Per-app color, another significant feature in PA3 and recent pre-release builds, allows you set system UI colors on a per-app basis. Want a black system bar for your launcher, but a blue one for Facebook? No problem. Have more eccentric choices in mind? That’s fine too.
The most recent (and most specific) addition is screen calibration for the Google Nexus 4. While the vast majority of third-party reviews have praised the device for its screen, build quality, responsiveness, and overall value; some have been quick to point out that the screen seems under-saturated, especially to those coming from overly saturated S-AMOLED devices. Rather than trying to offer a simple band-aid solution with RGB calibration, PA3 also corrects for the device’s gamma issues to give it the punch the IPS panel deserves. While you’ll be hard-pressed to find anyone who says that the Nexus 4 screen looks “bad,” the calibration has been met with much praise thus far, and the team only hopes that these changes are incorporated upstream.
Are you salivating yet? Those eager to get started should visit the threads below. Naturally, there will also be a plethora of unofficial ports for various unsupported devices. So if you’re looking for a build for your device, be sure to check in your device forum to see if someone’s already attempted porting the ROM. Even better, you could always try porting and building the ROM from source yourself.
January 19, 2013 By: jerdog
At the end of last year, we started selling XDA cases with our friends at CruzerLite, and we’ve seen some phenomenal interest. Our current lineup is the Samsung Galaxy Note 2, Samsung Galaxy S III, Samsung Galaxy Nexus, and the Google Nexus 4—but we want to add more. So we have decided to hold a poll and let the users choose which device(s) to add to our current lineup.
Below you will find some of the top devices at XDA. Please choose one from the list that you would like to see offered, and we will pick from the top 3 devices. The voting ends on February 15, so make sure you place your vote for the devices you love!
EDIT: The results are in, and displayed below. We’ll keep you updated as to the final options when they become available.
January 14, 2013 By: Haroon Q. Raja
Whenever there is mention of custom ROMs for Android, AOKP is one of the first to come to mind. Over the past year, the popularity of this source-built ROM has skyrocketed to make it one of the most recognizable third party development projects. Though over the past few months, several AOKP users (including myself) decided to jump ship to other ROMs because of the delay in a release based on Android 4.2. There is good news: The wait is over, as Team Kang has officially released Android 4.2.1-based AOKP JB-MR1 Build 1, starting with the Nexus line of devices.
As with the changes in Android 4.2 from 4.1, the changes in this AOKP release from the previous one aren’t as many as we’ve seen in previous major releases. However, they are still substantial enough to improve the overall user experience. Apart from all the AOKP features of the previous Jelly Bean builds, you’ll get:
The Nexus line of devices was the primary focus of AOKP since its very inception, and they are the first ones to get this release as well. However, that doesn’t mean other devices will be left out. The team is working on Galaxy S II, S III, Note, and Note II support for the next build, with builds for many other devices to follow. Until then, you can grab the ROM for Nexus devices from the following links:
The team is also planning a return to its (bi)weekly release schedule once builds for more of the officially supported devices are ready. More information can be found at the AOKP website.
January 8, 2013 By: jerdog
Bootloaders are like locks on a cookie jar: They’re just begging to be unlocked. When users on XDA see a locked bootloader, they immediately start looking for the accomplished developer who is working on hacking the device. It is for this reason that we like to hold Google Nexus devices as the gold standard for how manufacturers (and carriers) should approach their bootloaders, as well as firmware openness.
Nexus devices are easy to unlock: You go into fastboot mode, type ‘fastboot oem unlock’, and you’re done. Easy peasy. Of course, Google’s method involves an automatic wipe of your data, which functions as a pseudo-security measure. There of course is a way to get that data back after the wipe on the Galaxy Nexus, but what most users fail to think about is locking their bootloader again once they’ve gotten their ROM to where they want it to be. This opens up their device to all sorts of potential problems, especially those of the malicious kind.
Recently there has been talk about the Samsung Exynos 4 memory exploit, which leaves Exynos 4-based devices open to malicious attackers. With the fact that Samsung has never fixed the eMMC Brick Bug issue, which affects stock and non-stock Exynos 4 devices, you have the perfect storm of malicious attacker meets manufacturer negligence. Users can have their devices bricked and/or wiped in a matter of moments, and they would be none the wiser.
XDA Senior Member segv11 came across something in the Nexus bootloader, which is cause for concern for the Galaxy Nexus, Google Nexus 4 and Google Nexus 10. segv11 created a bootloader unlock, which does not follow the normal convention. Instead, it falls back on a process where you can keep your bootloader locked, and still keep a sense of security. He does this by simply changing a couple of bits in the /param partition, while keeping the bootloader locked for security reasons. XDA Elite Recognized Developer AdamOutler also released a similar process for the Galaxy Nexus back in April of 2012 which utilizes a brute-force method to unlock the bootloader by replacing the entire /param partition instead of just adjusting the bits.
This app highlights an issue with the way Google has chosen to lock the bootloader, especially when it’s easy to just change the aforementioned bit. What else is contained in there that can be hacked? What else is there that a malicious app, with root privileges, could potentially render your device a pricey brick? It’s for this very reason that we encourage users to be very careful before they mess around with their devices, and to make sure they read all of the instructions the developers put together beforehand.
The morning started off with an LG press conference. They talked at length about “Touch[ing] the Smart Life.” They then talked about their “smart” products. This included everything from refrigerators and washing machines to televisions with more pixels than people in New York.
They spoke briefly about connected devices. They talked about a washing machine that you can start with your smartphone using NFC. You can control their robotic vacuum with your smartphone. They also covered standard device mirroring, or showing your mobile devices screen on your television. The talk included simplifying the setup for this, using a “one touch connection.”
They spoke about their advanced touch interface on their mobile devices. However, only three features of this UI were shown. One was the live zoom feature, which allows you to zoom in and out in a playing video, and another was called “Vu: Talk,” which from gather allows you to write on the screen while talking to someone.
Finally, they talked about their mobile device releases, but most of these devices are not new. They talked about the LG Intuition and its “genius” 4:3 aspect ratio, because that’s the aspect ratio of documents that you view on your phone. Also, they talked about the LG Optimus G—which they went on to call not just a smartphone, but a superphone—and the Google Nexus 4.
All in all, it doesn’t appear that there are currently any breakthrough devices coming from LG. Surprising, right? So developers need not salivate over anything on the LG mobile line up for a while. Judging from their presentation, they instead seem to be focusing on making televisions with more and more pixels at this time.
The Google Nexus 4 has had its ups and downs since its release. The lack and subsequent gain of (limited) LTE functionality, shipping/stock issues, and of course the great development occurring on the device. Another issue that some users have reported is that there is excessive noise in their video recording. Now, there may be a fix for that.
XDA Recognized Contributor mohit1234 released a mod that increases the bitrate of the Nexus 4 from 12 Mbps to 20 Mbps. This should help fix the noise problem and give you better quality videos. So far, users have reported that this has, in fact, helped a great deal and testing seems to show that this will help the noise issue. Of course, increasing the bitrate will inherently require more storage space for your recorded videos, so choose wisely.
To apply the mod, users will have to make a few edits in media_profiles.xml. This is not too different from the 720p mod for the Nexus 7. While this does fix the issues, there is more potential fun that modders can have with the media_profiles.xml file. The next steps will be seeing how high the bitrate can go, and altering the audio and channel values to see if Nexus 4 users can get better audio along with video.
To learn more, check out the original thread.
December 5, 2012 By: Joseph Hindy
Over the last couple of weeks, we’ve been bringing you news of mskip’s toolkits making it to the Nexus 4 and the Nexus 10. It’s a popular and well known toolkit with extensive features. There is a second toolkit making its way around to Nexus devices, known as Wug’s Nexus Root Toolkit. We brought you news that it was released for the Nexus 7. Now, it’s available for the Samsung Nexus S and Nexus S 4G, the Nexus 4, and the Nexus 10.
XDA Recognized Developer WugFresh has been busy this month. The toolkit has made to five different Nexus devices in just a few weeks. The core features of the toolkit are the same for all releases, and include:
This program will automatically bring together all the files you need to unlock and root your device in a few clicks, or flash it back to stock and re-lock it. You can also use this program to backup/restore all your important data, flash zips, set file permissions, push and pull files, install apps, and much more! With the included file association options, you can perform tasks like flashing zips, installing apps, restoring android backup files, and flashing/booting img files with just a double click! The program includes a full featured interface for automating tasks in TWRP, enhanced restore features, an in-built auto-updater/notification system, ‘any build’ mode, and quick tools utilities. All the latest Android builds and Nexus devices are now officially supported, including the new Nexus 10, Nexus 4, and 3G Nexus 7 (with full 4.2.0 support).
The premise of this toolkit is to make rooting easy and provide a few extra features like installing applications and pushing files. For those looking for a root-bringing toolkit, you should give them a shot.
Unless you’ve been hiding under a rock somewhere, you know that Google has released a few new devices (Nexus 4 and Nexus 10), as well as a refresh to the Nexus 7. What makes this different from previous Nexus releases is that there are two new manufacturers added to the mix with Asus (Nexus 7) and LG (Nexus 4) joining Samsung (Nexus 10 as well as Nexus S and Galaxy Nexus) and HTC (Nexus One).
We recently told you about XDA Elite Recognized Developer Chainfire’s new project to automatically root devices and keep them as stock as possible, and we now have an important update to share with you, as Chainfire has added CF-Auto-Root support for the new Nexus devices. What makes this update different from previous versions is that fastboot support has been enabled, as well as an updated version of SuperSU (v0.99).
Follow the links below to learn more and to obtain the downloads.
December 2, 2012 By: Joseph Hindy
Earlier, we brought you news that the universal naked driver received a well deserved update. For those who are unaware of the universal naked driver, it is a project that fits as many drivers as possible into a single driver install to save new users hassle. It’s been updated once again, and this time for the newer Nexus devices.
The new update supports the Nexus 4, Nexus 10, Nexus Q, and—even though it’s a little late—the Nexus S. XDA Senior Member 1wayjonny posted the update in the Nexus 4 forums. The drivers are supported on Windows XP, Vista, 7, and 8.
For most Windows machines, it’s a matter of installing the drivers like any other driver, which is install and go. Windows 8 users may have a more complicated time installing it, but it’s still pretty easy. 1wayjonny posted a tutorial for Windows 8 users to disable driver signature enforcement, so that the drivers can be installed correctly. Once installed, all your devices should be supported under a single driver. For anyone who has a number of devices or plans on adding a member of the Nexus family to their device list, this is definitely something to check out.
To learn more, check out the original thread.
While one-click tools have been a subject of much debate, developers are still developing them and users are still using them. They often come in the form of one-click methods and all-in-one toolkits. They can be helpful with a variety of things. Now, the Nexus 4, which recently achieved root, has its own.
* Install correct adb/fastboot drivers automatically on Windows xp/vista/7/8 32bit+64bit
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your /data/media (virtual SD Card) to your PC for a Full Safe backup of data
* Unlock/Re-Lock your Bootloader
* Root Stock Jelly Bean builds (upto 4.2.0 JOP40C)
* 1-Click For All to Unlock, Root, Rename the Restore File
* Perform a FULL NANDROID Backup of your system (Boot, Cache, Data, Recovery and System) via adb and save in Custom Recovery format on your PC which can be Restored via CWM Recovery
* Pull /data and /system folders, compress to a .tar file and save to your PC
* Dump selected Phone Partitions, compress to a .zip file with md5 and save to your PC
* Install BusyBox on your phone
* Extras, Tips and Tricks section available to all ToolKit Donators
* Mods section to automatically perform certain tasks on your phone
* Download Google Stock Image directly to correct ToolKit folder for extracting and flashing (no need to move it manually anymore)
* Flash Custom Recovery or Google Stock Image to phone
* Rename the Recovery Restore File present on some Stock Roms
* Boot into CWM Touch Recovery without Flashing it
* Boot or Flash .img Files directly from your PC
* Install a single apk or multiple apk’s to your phone
* Push Files from your PC to your phone
* Pull Files from your phone to your PC
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Set Files Permissions on your phone
* Open new Command Prompt for manual input
* Reboot Phone to Fastboot Mode or Android from fastboot mode
* Reboot Phone to Fastboot Mode, Recovery, Android or Download Mode from adb mode
So if you have the Nexus 4 and you need pretty much anything, this is the toolkit to get. The highlights include root, recovery, busybox, and bootloader unlock. However, there are some tools available that could be very handy. Backing up the virtual SD card, for instance. Also, dumping various logs can help users help developers. We all know how much developers love logcats.
For more details, check out the original thread.
November 23, 2012 By: Conan Troutman
Nov 23 Update: It appears that the modem does indeed work on band 4 (1700 MHz / 2100 MHz)! Instructions on how to enable the functionality can be found here! Essentially, you need to enter *#*#4636#*#* into the dialer, select Phone Information, and set Preferred Network Type to one of the LTE options. Depending on your carrier, you may also need to modify your APN settings. Work is now being done to try and enable bands 1 and 2. READ ON »
The Nexus 4 was just recently released, and naturally it didn’t take long for developers to achieve root and start releasing development work. With all Nexus devices, unlocking the bootloader is fairly simple. You need the Android SDK for Fastboot support, and you simply enter fastboot OEM unlock.
First came ClockworkMod Recovery for the Google Nexus 4 thanks to Koush. The update was posted to the forums by XDA Forum Member fkrone. The recovery is the official version of ClockworkMod Touch, and it seems to be highly functional.
For those who prefer more eye candy and an even greater number of additional features, XDA Recognized Developer Dees_Troy has ported his famous Team Win Recovery Project 2.3 to the device. As usual, the TWRP 2.3 port includes all of the previously covered goodies such as a fancy themable GUI, ORS support, and much more.
November 19, 2012 By: Jimmy McGee
Jelly Bean Leak, Nexus device rooted, Windows 8 and wireless device manufacturers’ agreements—all this and more covered on today’s episode of XDA Developer TV. Android News specialist Jordan talks about the Jelly Bean leak for the international variant of the Samsung Galaxy S II. Also mentioned is the article talking about more and more Windows 8 apps being released.
In rooting news, Jordan mentions the rooting guide for the Droid DNA device. Also, to the surprise of no one, the Nexus 4 has been rooted. Finally, Jordan mentions the agreement between HTC and Apple and Samsung’s demands to see the particulars of this agreement. Pull up a chair and check out this video.