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.
If you’re an avid Android “rooter” and “ROM flasher,” then I’m sure the Nandroid backup feature that custom recoveries offer has been your best friend. It’s essential to perform a Nandroid backup before you wipe and flash your newly desired ROM in case something goes wrong and you need to restore your phone into a previously working state.
If you’re not familiar with how a traditional Nandroid backup works, you are required to turn the phone off and boot into the recovery to perform the procedure. A typical Nandroid backup takes about 4-6 minutes, thus your phone would be nonoperational for that period of time. An XDA developer by the name of ameer1234567890 found that troublesome as he would constantly miss important calls and texts from his family and took it upon himself in creating away to perform a Nandroid backup without having to boot into recovery. Online Nandroid Backup allows the user to perform a Nandroid backup without the need to turn your phone off, thus you won’t miss important calls or texts.
Using the program is actually fairly simple and easy to follow:
A few days ago we told you about how Android already has some built in functionality for multiple user accounts, but just not complete. If you’re not familiar with what this concept is, it allows you to have separate log ins for your tablet or smartphone. For example, you could set up your tablet the way you want as far as home screens and whatever apps you use, but other family members could log in under a different account, and they would get their own set up of apps and home screens.
This is something that is within the AOSP, but not something that is ready for prime time. It only means that it’s something we will probably see in a later version of Android like 4.2 or 5.0. None of this will stop the amazing Android development community as XDA member zanderman112 was able to setup multiple accounts using Terminal Emulator. Unfortunately there isn’t too much functionality, but this is a major start. Check out the video after the break.
The credit card sized Raspberry Pi computer that sells for $25 now has a working version of Android 4.0 Ice Cream Sandwich thanks to a port. The development community has been working towards getting Android on the Raspberry Pi with CyanogenMod 7.2 and CyanogenMod 9, but this is by far the most usable. This port even supports hardware-accelerated graphics, but unfortunately sound isn’t yet available.
This device is quite limited so this is pretty impressive. The Raspberry Pi sports a 700MHz single-core processor and only 256MB of RAM. Hit the break for a video showcasing it in action.
In a Google+ post yesterday, the CyanogenMod team announced that Ice Cream Sandwich (CM9) and Jelly Bean (CM10) won’t be supported for Snapdragon S1 devices. One such phone is the Nexus One and they stated that it would require a custom hboot to repartition the internal memory. The fact that there is only 512MB of RAM certainly doesn’t help the matter. On top of that, compromises to the CyanogenMod code would be necessary because of the proprietary libs available from 2.3.
They went on to say that “with enough time, effort, and hacks” it could be made to work, but they don’t feel the experience is worth all of that. Other main attraction phones that have the Snapdragon S1 are the HTC EVO 4G and the HTC Desire.
Multi-user accounts on an Android device is something that users have been longing for. Having multiple user support is something that personal computers have had for quite some time now, thus it only makes sense for it to finally be implemented into Android phones, and most importantly, Android tablets. Thanks to some digging by one of CyanogenMod’s finest developers ciwrl, it seems as if Google has left some “bits and crumbs” of code within Android AOSP (Android Open Source Project) suggesting that multi-user accounts will eventually make its way into Android.
Next to the locked bootloader, the absence of Google Wallet in Verizon’s flavor of the Samsung Galaxy S III smartphone is a major buzzkill to owners of the device. Fortunately, the Android world is graced with fine individuals who strive to correct unjust actions by big brands. And with that, crafty developers Mike Beauchamp and Dustin Evans developed a special hack, which allows the NFC-capable smartphone to now utilize the famed mobile payment function. Naturally you’ll need your Galaxy S III to be rooted and it wouldn’t hurt to have some working knowledge of how to tweak and tinker, but it’s all worth it once you’ll have that sweet, sweet ability to tap your smartphone against any and all of those Google Wallet payment terminals.
Interested Verizon Galaxy S III owners can hit the source link for full details.