September 12, 2012 By: Haroon Q. Raja
Many Galaxy S II and III owners who do a lot of heavy gaming on their phones have run out of space for game data in internal storage. While both of these devices support external SD cards, there is no official method available to use that instead for the storage. Fortunately, there is an easy solution for this problem now with free tool DirectoryBind.
Originally built for the SGS II by XDA Forum Member slig, DirectoryBind has been confirmed to work on SGS III and Galaxy Tab 2 by many, and may work for more devices too, as long as they are rooted and have a similar partition structure. As the name suggests, DirectoryBind binds a directory in one location on your device to another. While the concept behind it is similar to symlinking, it uses the bind command instead that makes it work across file systems. This is particularly important, as the file system used on the external SD Card is usually FAT or FAT32, and the internal one is Ext 3/4, making symlinking impossible.
The app has a decent GUI that makes it easy to create new directory pairs, manage the existing ones, mount or unmount them manually, choose to automatically mount them at system startup, and even set them to automatically unmount when USB storage mode is activated and remount when it is deactivated.
You can download the app and learn more in the application thread.
If you peruse XDA, you’ve likely installed custom ROMs on your phone. Often we find the perfect ROM when it comes to the features, but would prefer it to have a different look. Many times that can be changed with themes, but those can often vary from ROM to ROM, and not everyone may want to apply all the aspects of a theme.
XDA Senior Member rehpyc has come up with a way of customizing the look of your ROM installation right from recovery. The mod is built on the AROMA Installer, and it puts you into the driver seat—letting you choose your own modifications right from a touch-based GUI in recovery. Currently, you can choose the following styles:
The mod is currently only available for the Galaxy S III, and being an initial release, it has its limitations. However, given the active development, and the possibility to integrate this into ROMs directly, there is a good amount of future potential.
To learn more and get started, head over to the original thread.
September 5, 2012 By: Joseph Hindy
Around here, many users enjoy various AOSP-derived ROMs. There are quite a few options, including such well known ROMs as CyanogenMod, AOKP, and ParanoidAndroid. There are many more options as well, which is great because the more the merrier.
Now, the Android Developer Alliance development team has released the AffinitySERIES ROM to various devices. Their missions statement is pretty simple, as explained by ADA member, and XDA Recognized Developer, blueHarford:
One of our biggest things is No Drama, no secrets, BIG on communication which i think alot of other teams lack. We are not the best we will not boast ourselves or ever use the word kang. We feel like one of the first teams to start AOSP project to where it truley is part of the open source community. Were not out for recognition were out to make good products.
Fast, Responsive, Intuitive & Professional UI
GLaDOS v2.1 Power Kernel Built In
First of its kind Customized Toggle Icons
Custom Awesome Popup SMS Features
Facebook Contacts Support
Custom Power Widget
4 Way Reboot Menu
Exclusive ADA Wallpapers
5 Way Lock Screen Targets
Beautiful Weather Lock Screen
Voice & Data (SVDO)
Customized Navbar Settings
Modified Navigation Bar Options
Clock Modifications – Left, Center, and Right Clock AM/PM Weekday Abbreviation
Battery Options 6 Styles to Choose
Many, many more…!
Users are reporting that the ROM works well and has very few issues. Most are reporting no issues at all, which is great for a Jelly Bean ROM. Now that the initial release is out of the way, the team is looking forward to the host of other devices they plan on supporting in their second round of releeases. The official list includes:
Asus Transformer TF101
Asus Transformer Infinity TF700
Samsung Galaxy Tab2
Droid RAZR/RAZR MAXX
Samsung Galaxy Nexus (toroplus)
Samsung Galaxy Note
Samsung Galaxy SII and SIII
September 4, 2012 By: Joseph Hindy
The Samsung Galaxy S III has been widely touted as one of the best Android devices currently available. As such, we here at the XDA Portal have been reporting on it extensively for quite some time. However, there are still some kinks to be worked out, even on this massively successful device, and one of those kinks just got fixed. Now, users can monitor their CPU temperatures in real time.
It seems like such a trivial thing, and no one can really explain why Samsung didn’t enable this in the first place, but that doesn’t matter anymore. XDA Recognized Contributor bala_gamer has posted a thread where users can enable CPU temp monitoring. The original method was discovered by XDA Senior Member viking37.
Initially it was thought that you had to have a stock kernel to get real time CPU monitoring, but after further research it appears as though all kernels support it. From there, you install System Tuner Pro with the Notifications Package. For more info, check out the original thread.
The CyanogenMod crew has added four new devices to their officially supported lineup. This is exciting news, considering the popularity of the devices in question. These four flagship-status devices are some of the most widely-used phones on the market today. The list of devices and maintainers is as follows:
This is great news for owners of these devices, since the aforementioned HTC and Samsung devices natively run HTC Sense and Samsung TouchWiz, respectively. Many users prefer a fully functional AOSP-based build to these bloated default ROMs, and CyanogenMod 10 fits the bill as an Android 4.1 ROM with some discrete, yet highly functional modifications. Keep your eye on the device forums to catch the latest release candidates, and try not to ask for ETAs!
August 27, 2012 By: Joseph Hindy
While they don’t offer any additional functionality over capacitive buttons, the software buttons that first appeared in Honeycomb and continued to Jelly Bean have become rather popular. They’re not only a modifiable novelty, but with screens as large as they are, giving up a little screen real estate for the software buttons isn’t exactly a big deal. Now, the Samsung Galaxy S III and its US variants running CM10 can have their software buttons enabled with a single mod.
The original thread was started by XDA Recognized Developer graffixnyc to bring the software buttons to the international Galaxy S III. However, XDA Forum Member NemesisRE took it a step further and developed a mod that brings the soft keys to all Galaxy S III devices.
There are five mods that users can use, all of which are flashable through custom recovery software. They are as follows:
NAV_Only: none of the hardware keys are enabled (except Volume and Power)
NAV_HomeWake: Home button wakes device but has no other function
NAV_HomeCamera: Long press Home button opens Camera and takes Pictures but has no other function
NAV_StockKeys: Functions as normal but with on Screen Navbar
NAV_Remove: Removes the mod
Not only does it work on any Samsung Galaxy S III devices, but it also may work with any device that uses the same key binding as the Galaxy S III. As NemesisRE explains:
This should work on any device with the same keybindings:
key 172 HOME
key 158 BACK
key 139 MENU
In the this files:
For more info, check out the thread above or the single post for more details.
August 27, 2012 By: Jimmy McGee
This has been another great weekend on the XDA Portal. XDA Developer TV Producer Jordan covers all the news you need to know to keep you updated. Jordan talks about controlling your appliances with your Android Device and overclocking your Samsung Galaxy S III. Jordan mentions the Samsung Galaxy Note 10.1 receiving its first custom ROMs.
August 26, 2012 By: Joseph Hindy
Overclocking your CPU can be a lot of fun. When successful, one can experience anything from increased performance to less game lag. Despite the hit to battery life, overclocking is a pretty popular activity among electronics owners. Something that not so many people know, though, is that overclocking a mobile device can involve more than just changing the processor clock. Many kernels also allow one to change the processor voltage and sometimes even overclock the GPU as well. For Samsung Galaxy S III owners, you now have a guide to help you make sense of it all.
The guide covers pretty much all of the basics including the advantages and disadvantages of overclocking and underclocking, the advantages and disadvantages of undervolting, and a list of commonly stable overclock and underclock values along with their stock voltages, though one must keep in mind the highly variable nature of individual pieces of silicon. Of course, most are aware of the advantages of overclocking. Usually it means a faster GUI, faster application load and response time, and just all around improved performance. However with that comes some risk, such as blowing out your hardware entirely. Written by XDA Recognized Contributor bala_gamer, the guide covers pretty much everything and includes everything you need to get started, such as an overclocking-compatible kernel and all the necessary tools.
For more info, check the original thread.
Having your SIM locked doesn’t usually cause a lot of problems. Sure, it means you’re stuck on whatever carrier you’re currently on, but otherwise it doesn’t really hinder things like root, flashing ROMs, etc. That isn’t to say that unlocking the SIM isn’t useful. Those who travel or simply want to remove carrier restrictions can benefit from SIM unlocking a device. Now, Samsung Galaxy S III owners can have their SIMs unlocked so that they may do as they please.
The method comes in the form of a zip that contains a few files that must be moved to the Galaxy S III EFS folder. Released by XDA Recognized Developer zohawkish, the method is very easy to do. As zohawkish explains:
- First you need to backup your “EFS FILE” in safe place.
- you must be in unlocked stock firmware like BLG8 (using voodoo app + libsec-ril.so (mike1986 fix))
- unzip the attached zip “efs.zip”
- copy the files (.nv_core.bak, .nv_core.bak.md5) to your EFS file
- reboot and enjoy !!!
Of course, there are some potential complications. As stated, you’ll want to backup your EFS file in case something goes wrong. Additionally, you’ll have to restore your backed up EFS if you ever want to update to a future Jelly Bean release. Aside from that, users have reported that the mod works perfectly.
Note from the editor: the actual thread is no longer being supported by the OP and as such it has been closed.
August 20, 2012 By: Joseph Hindy
When flashing an AOSP ROM on a CDMA phone, it’s a win-some lose-some affair. You gain the functionality that comes with a pure Android experience. However, you traditionally lose USB Modem and Diagnosis Mode on your device. For those who are unaware, USB Mode and Diagnosis Mode are accessed via codes you enter into the dialer. This is not only required to activate the phone on some networks, but also helpful in alleviating some problems like restoring your IMEI using QPST. However, for many Samsung devices, that is no longer a problem. Now, you can get all this functionality back without flashing back to a stock ROM.
XDA Senior Member autoprime has put a thread that not only gives a profound amount of information but also provides a script to make it all easier. The suggested way is to use a script manager application to apply the script. As autoprime explains:
Open script manager, browse to script files on SD card, select script, set to run as SU and hit save. Do this with both scripts. Now you can use the script manager in the Widgets section to create shortcuts on the desktop for easy access. Hopefully these scripts get built into CM10 so this method is no longer needed. You may or may not have to unplug/plugin the usb cable after new mode is set.
Also provided is a plethora of instructions. This is a huge step for the supported devices, which include:
The Epic 4G Touch was having some troubles with the script, but autoprime managed to fix it in short order. Additionally, this method will soon support other devices. So if you’ve had to flash back and forth between AOSP and stock just to use these codes and your phone is supported, it’s time for some celebration.
To learn more, head over to the original thread.
Update: Given the abuse, the link to the thread has been removed. We apologize for any inconvenience.
August 19, 2012 By: Joseph Hindy
It’s been a big week for the Samsung Galaxy S III and its US variants. Not only has the Verizon Samsung Galaxy S III had its bootloader unlocked, but the International version got a Jelly Bean leak. This gives credence to the rumor that Samsung is releasing the update soon. However, many don’t want to wait that long. Now, there’s another way to get the leaked build.
XDA Senior Member Jack Barrett has re-released the leak in a useful manner for those wishing to flash without Odin or Heimdall. Instead, Jack Barrett has released the Jelly Bean leak via a Nandroid backup. In short, Jack Barrett got the Jelly Bean leak on the device, wiped everything, and made a backup. To install it is actually pretty easy:
How to install:
Extract the zip in SDCard –> clockworkmod –> folder (for example JB) –> files here
Go to CWM –> Backup & Restore –> Restore from internal storage
The ROM is NOT rooted.
You should root it yourself.
Those interested can visit the original thread.
That last thing you want to hear when submitting your device for a warranty repair is, “You rooted your device and broke the warranty so I can’t help you. Enjoy your bricked device!” The tech in the store or at the repair center rarely knows exactly what was done, but they tend to pay attention to the status of your bootloader and if you have a rooted device and/or custom firmware. In the case of newer Samsung devices, after flashing a custom kernel, the screen displays a nice yellow triangle on boot signifying you’ve done something that the manufacturer didn’t want you to.
XDA Elite Recognized Developer Chainfire recently created an app called Triangle Away, which clears the system flag on select Samsung devices so that the annoying triangle goes away. Today, he updated the app to version 1.80, which adds support for the US Cellular Samsung Galaxy S III, along with the entire Samsung Galaxy Tab 2 series. Recently added devices:
Samsung Galaxy S2 GT-I9100 **
Samsung Galaxy Note GT-N7000 **
Samsung Galaxy Note GT-I9220 **
Samsung Galaxy S3 GT-I9300 **
Samsung Galaxy S3 GT-I9300T **
Samsung Galaxy S3 AT&T
Samsung Galaxy S3 Sprint
Samsung Galaxy S3 T-Mobile
Samsung Galaxy S3 Verizon
Samsung Galaxy S3 Canadia
Samsung Galaxy S3 US Cellular
Samsung Galaxy Tab 2 GT-P310x 7″ 3G
Samsung Galaxy Tab 2 GT-P311x 7″ Wi-Fi
Samsung Galaxy Tab 2 GT-P510x 10″ 3G
Samsung Galaxy Tab 2 GT-P511x 10″ Wi-Fi
** Various related models are supported depending on firmware, but only the exact model numbers listed are supported regardless of firmware version.
Head on over to the original thread to get more information and to download the application.
August 16, 2012 By: Haroon Q. Raja
Just yesterday we posted about Android 4.1 Jelly Bean potentially making its way to the Samsung Galaxy S III by the 29th of this month and how it was strange that no test builds have yet leaked. As luck would have it, a leaked build of Jelly Bean for the device has now appeared for the device, which is great news for anyone looking forward to Google’s latest tasty treat.
Brought to us by SamMobile (the same guys who predicted the 29th as the OTA release date) and posted to XDA by Recognized Developer Faryaab, this is test build XXDLG4 targeted at the international version of the device. While it may not be a final build, it brings the I9300 all the latest Jelly Bean features including the revamped notification bar and Google Now.
You can download and flash the build by following the instructions in the original thread. However, as mentioned in the thread, be sure to verify that you are on a stock Samsung ROM before flashing it. Otherwise, you risk bricking your device.
[Thanks to XDA Recognized Developer Faryaab for the tip]