Showing posts with label Tips And Tricks. Show all posts
Showing posts with label Tips And Tricks. Show all posts

Saturday, 19 October 2013

Custom ROMs For Android Explained - Here Is Why You Want Them

Introduction

Ever wondered what the whole Android custom ROM scene was about?
What is all this talk of installing "aftermarket", custom upgrades on your phone?
Who needs it? Why do it? Is it safe?
Don't fret - I'm here to explain - the AndroidPolice Academy is now in session.
By the way, the word ROM means Read OnlyMemory, but has migrated in the modding community to mean an actual custom OS image that you install into the ROM area of your phone.
Also, the word kernel essentially means the heart of the OS - it's the barebones operating system components.

Custom ROMs

A stock ROM is the version of the phone's operating system that comes with your phone when you buy it.
A custom ROM is a fully standalone version of the OS, including the kernel (which makes everything run), apps, services, etc - everything you need to operate the device, except it's customized by someone in some way.
So what does the "customized" part mean? Since Android is open source, developers are free to take stock ROMs, modify them, strip them of garbage, optimize them, add things, and pretty much do whatever their imagination and skills allow.

Why You Want Custom ROMs

Update Frequency

Using a custom ROM usually results in more frequent updates that fix bugs and introduce new features because the developer behind the ROM doesn't have the same procedures and red tape that the manufacturer+carrier combo does.
  • A quality update can be churned faster because it doesn't involve the bureaucracy of 30 different project managers, 15 vice presidents, and 5 dozen marketing departments.
  • A ROM developer usually gains a loyal community which beta tests his updates in real life situations and provide feedback, or even fixes bugs - that's the beauty of open source software.
  • Oh and did I mention that ROMs are usually free and supported by optional donations? If you can't afford to pay for it, you don't have to.
  • Finally, most custom ROMs out there are updateable over the air (OTA) and without reinstalling anything.
Who doesn't love open source after this?

Better Performance And Efficiency

Custom ROMs are oftentimes faster, more efficient, and use less memory because
  • the developer ripped out useless garbage, such as carrier installed apps or
  • the developer optimized the kernel. For example, an undervolted kernel can provide a much better battery life than the stock one.

Upgrading To A Better/Later Version Of Android

You can upgrade to a version of the OS that has not yet been released for your device, or never will be. This is possible in 2 situations:
  • A leaked version of the new ROM showed up online, and the developer got on it like the fat kid chasing an ice cream truck. This was exactly the case with Hero and Android 2.1, allowing me to upgrade from 1.5 weeks (months) before the official version was available and ditch the bogged down and slow stock OS.
  • A ROM from another phone was ported by the developer to work on yours. For example, G1 and MyTouch 3G users may never see Android 2.1 officially released on their phones, but Cyanogen, one of the most respected Android developers, was recently able to create a custom ROM running 2.1 for those devices. Oh, what a happy day it was for MT3G and G1 owners.

Ability To Install Apps To The SD Card

Most custom ROMs nowadays come with the ability to install applications to the SD card, calledApps2SD (or A2SD).
This is currently not possible on stock ROMs, even in Android 2.1 and is supposedly on Google's TODO list.
If you have run out of space on your phone (which I have repeatedly on my Hero), Apps2SD is a killer feature to have.

About That Rooting Business…

Don't confuse custom ROMs with rooting - they're completely different.
We have explained rooting and its benefits in an article called Rooting Explained + Top 5 Benefits Of Rooting Your Android Phone.

The Downsides Of Custom ROMs

Of course, there are dangers of using custom ROMs which you should be aware of.

Something Could Go Wrong

First of all, something may go wrong with the flashing process (that's the process of installing the ROM) and leave your phone in a bricked state. The chances of this are pretty low nowadays, and most of the time you can restore it back to normal.
Try to go for the ROM that has been tested by time and has lots of positive feedback.

Clean Wipe

In order to install a custom ROM, you need to perform a clean wipe.
This means you will lose all existing data, so you have to back everything up first. Of course, just for this, we have a straightforward tutorial that shows how to back up and restore your entire phone: [Complete Guide] How To Fully Back Up And Restore Your Android Phone Using Nandroid Backup.

Potential Problems

Custom ROMs could have bugs… but then so do the stock ones.
However, in case you do find a bug, you actually have a 2-way channel of reporting it - post in the ROM forum and you will more than likely get an answer back and your bug acknowledged.
Try doing this to your phone manufacturer and see if you can get past the first level of outsourced monkeys, let alone actual developers.

You May Void Your Warranty

It's possible that custom rooting will void your warranty because you will "break the seal" on the boot loader by installing a custom one which on some phones apparently can't be undone (this includes the Nexus One). Because of that, the manufacturer might be able to tell that the phone has had a custom ROM installed and not honor the warranty, in case you need to use it.
Now, in most cases, the benefits of the custom ROM outweigh the possibility of your warranty being denied. I recommend getting a warranty from your carrier and using that in case anything bad happens (that warranty is usually unconditional and covers things like losses and physical damage).

Getting The Right Custom ROM

New phones and ROMs come out all the time, and the scope of this article doesn't cover individual ROMs - but the general approach to finding one is Googling for "YOUR_PHONE_MODEL ROM" or something similar, optionally including the wanted Android version. Try it out - you'll find what you want.

Conclusion

And there you have it - another tutorial is in the can, as Ijaz likes to say.

Have you found it useful or got anything to add? Please share in the comments.

How To: Install Sony's New PlayStation Mobile For Android On Any Rooted Device

Sony's PlayStation Mobile for Android just went live for certified devices last night. But what if you don't have a certified device, which so far includes only a number of Sony phones and tablets as well as the HTC One series? Heck, I have a One series device - the EVO LTE - but turns out it's not certified. That's just silly.
Not a problem - if you have root on your phone or tablet, getting the PSM (PlayStation Mobile) apk to work is a matter of pushing a few files it relies on to your /system directory and rebooting. Original credit goes to XxXPachaXxX - I used his work from a few months ago, took out some extra unnecessary Bravia engine stuff, and repacked it into a flashable zip for use with the PSM.
Here is PS Mobile running on my Nexus 7:
wm_IMG_1738
wm_Screenshot_2012-10-03-16-00-06 wm_Screenshot_2012-10-03-16-00-38
On the Nexus 7, I was able to play the free game and successfully tested a paid game called Fuel Tiracas. They both worked wonderfully. I also bought Samurai Beatdown, but for some reason it didn't install right (I tried 3 times but the download just said installation unsuccessful, hmmm).
Unfortunately, PSM crashes upon loading the store front on my EVO LTE. If you're not using a certified device, don't be surprised if it crashes on yours too - after all, it wasn't certified and, therefore, not tested.

Screenshots

wm_Screenshot_2012-10-03-16-00-06 wm_Screenshot_2012-10-03-16-00-26 wm_Screenshot_2012-10-03-16-00-38
wm_Screenshot_2012-10-03-16-02-07 wm_Screenshot_2012-10-03-16-05-27 wm_Screenshot_2012-10-03-16-12-32
wm_Screenshot_2012-10-03-16-13-59 wm_Screenshot_2012-10-03-16-36-28 wm_Screenshot_2012-10-03-16-37-14
wm_Screenshot_2012-10-03-16-37-25 wm_Screenshot_2012-10-03-16-37-40 wm_Screenshot_2012-10-03-16-39-41

Installation

Disclaimer: Android Stuff isn't responsible for any harm to your device - proceed at your own risk.
Step 1.
Download and install the latest PSM apk from Sony. I mirrored the current version, 1.0, here:
If you try to run the PSM app now, you'll likely get this:
wm_Screenshot_2012-10-03-14-59-54
Step 2.
Download the flashable zip I packed from one of these mirrors:
Step 3.
Note: Just to be clear once again, you have to be rooted to install the helper filescom.playstation.playstationcertified.jar and com.playstation.playstationcertified.xml. If you're not rooted yet, first figure out how to do so to your device and then come back.
Flash the zip from custom recovery, like ClockworkMod or TWRP. This relies on having busybox, which if you're rooted, you likely already do.
Alternatively, if you don't want to flash from recovery or just like to know what you're doing, you can perform the steps manually while booted into Android:
  1. Unzip the zip file downloaded in step 2.
  2. Copy playcertetcpermissionscom.playstation.playstationcertified.xml to /system/etc/permissions/ on your device.
  3. Copy playcertframeworkcom.playstation.playstationcertified.jar to /system/framework/ on your device.
  4. Set the permissions on com.playstation.playstationcertified.jar to 644 (read/write, read, read) using your favorite file manager or command line.
  5. Reboot.
Step 4.
At this point, PSM should work just fine and you should no longer see the error from Step 1. Goregister for a Sony Entertainment Network account if you haven't yet and try playing some games.

Please report your successes and failures in the comments.

How To: Manually Update Your Nexus 7 To Android 4.1.2 (JZO54K) With Stock Or Custom Recovery

If you want to update your Nexus 7 to official Android 4.1.2 that started rolling out earlier todaybut your turn hasn't come yet, you have two options: wait (possibly for a while) or flash it manually. The latter is absolutely safe and lets you bypass the line without any risk whatsoever. Even better - you don't even need to be rooted or running a custom recovery - updating with Jelly Bean and full stock recovery is easier than ever before.
Let's get to it.
Prerequisite: Your Nexus 7 should be running Android 4.1.1 build JRO03D.
Step 1.
Download the JZO54K Android 4.1.2 update zip from Google's servers (32,862,193 bytes, MD5: 1a68f499129ae2ee373806a9cad13174).
If you have a custom recovery, you can just copy it to the device, reboot to recovery, and flash directly as you would any other zip. You're done.
If you have the stock recovery, carry on.
Step 2.
Reboot your Nexus 7 and hold the VolDn button while it's booting up. Once you see the fastbootmenu and the word Start, press VolUp a few times until you see Recovery and then press the Power button to enter recovery.
You will see an Android with a red exclamation point. Now press VolUp+Power together, and you should see the menu below.
Select the 2nd option called apply update from adb.
wm_IMG_20121009_124737
Step 3.
Connect the Nexus 7 to your computer with a USB cable.
Make sure you have a recent version of adb that supports the sideload command (if you don't, download the latest Android SDK to ensure your adb is up-to-date).
Keep the file you just downloaded on your computer and open up a command prompt (cmd in Windows, regular shell in Linux and Mac) in the same directory as the zip file.
Type in:
adb sideload 03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip
You should see the progress bar go up to 100%, like so:
sending: 'sideload'  100%
At this point, the device should have started installing the update. See the screenshots below:
wm_IMG_20121009_124956 wm_IMG_20121009_125353 
Step 4.
Reboot - you're done! Enjoy the new landscape support in the launcher.
wm_Screenshot_2012-10-09-13-11-23 wm_Screenshot_2012-10-09-13-11-11
wm_Screenshot_2012-10-09-13-11-05
wm_Screenshot_2012-10-09-13-37-48
P.S. adb sideload kicks ass, doesn't it?
Thanks for the link, rusty++!

[Download And Manual Update Instructions] Install The Android 4.1 Jelly Bean Update For The AT&T HTC One X

Update: It seems these instructions aren't working for most people. Until another method is found, you'll have to wait for the OTA update to be pushed to your device.
Still waiting for that Android 4.1 OTA on your AT&T HTC One X? Well, wait no more: you can manually flash the update to your stock AT&T HTC One X running the latest firmware using the following instructions (your data will not be wiped).
What you'll need:
Warning: Proceed at your own risk - we aren't responsible for any lost data or damage that occurs to your phone while using the information in this post. If you've never flashed an update manually before, please - do yourself a favor and read up on how to recover your phone if something goes wrong during the flashing process before trying this.
Step 1: Download the update.
Step 2: Place the update file on the root of the phone's storage (aka /sdcard/)
Step 3: Boot your phone into recovery. To do this:
  • Power off your phone.
  • Hold down volume down, and then while doing that, press and hold the power button (this may take a while - up to 10 seconds) until you see the fastboot screen (white background with three skateboarding Androids).
  • Use the volume keys to navigate to the "Recovery" option, then press the power button. You'll see the HTC logo, then the screen will go blank, followed by an image of a phone lying flat with an exclamation point and a triangle.
  • Now, press and hold down on both volume up and down, and then while holding them, press and release the power button. Release the volume rocker. You should get a blue menu with a set of options - you are now in recovery mode.
Step 4: Flash the update file from recovery. To do this:
  • Navigate with the volume rocker to the "Apply update from internal storage" option.
  • Hit the power button.
  • You should see the update file you placed on the root of the phone storage, select it and hit the power button to begin the flashing process (if it does not begin automatically).
Step 5: Wait for the update to install, after which, the phone should reboot on its own.
And you're done! You're now running Android 4.1 Jelly Bean. Easy, right?
Thanks to DvineLord for the OTA file link!

Tip: Facebook Messenger For Android Has Hidden Sticker Support, Here's How To Enable It

Facebook has been making numerous changes to its Android apps as of late, thanks to the arrival of Facebook Home. Sometimes, new features also bring "hidden" options – things that may not be quite ready for prime time but can be accessed within the app. Facebook Messenger has one such "feature" tucked away in its emoticon menu: stickers. Big ol' images with goofy faces and cats and other stuff. I'm not entirely sure why this is a thing that anyone wants, but it's there, and you can use these oversized emoticons now. Fun.
Screenshot_2013-04-22-10-30-02 Screenshot_2013-04-22-10-37-12 Screenshot_2013-04-22-10-34-09
That's right, Internet – I don't really like cats. What you gonna do about it?
Here's how to find 'em:
  1. Enable Chat Heads. (This only works in a popped out Chat Head, it doesn't work in the regular Facebook chat.)
  2. Press the tiny invisible area to the left of the "+" button on the bottom left.
  3. Bam - stickers.
I had some issues getting stickers to load properly while testing this – a force close/re-open seems to do the trick.
Update: Some users are having a hard time finding the invisible area that needs to be tapped. Here's a shot with the area highlighted:
Screenshot_2013-04-22-11-13-30
And that's pretty much it. Enjoy your new fat heads and fat cats. Share them with all your friends.

PSA: Your Gmail's "Delete" Button Is Not Gone In The New App, It's Just Hiding - Here's How To Re-Enable It

Do you have this (look down) problem after installing the new version of Gmail? That is, when you open a message, all you see are options for archive, mark unread, and add to folder? You're not alone! If you downloaded the new version of Gmail (v4.5) from the Play Store today, it's likely that your "Archive & delete actions" were reset when the app was installed. We're not sure why Google did this (well maybe Google doesn't really want you deleting your email, that would make sense from a business standpoint), but here's how to fix it.
Screenshot_2013-06-05-12-25-00
Hit the menu button, and go to settings. Then, go to general settings. You should see the option below at the top of the list - Archive & delete actions. Right now, it's set to "Show archive only" - and at this point you probably don't need much more of my help, but I'll explain anyway.
Screenshot_2013-06-05-12-24-02
Tap it, and you get three options - archive only, delete only, and archive & delete. The third option gets rid of the 'move to folder' action. Choose the one you want (probably the second or third), and you're set to go - your little trash icon will return.
Screenshot_2013-06-05-12-24-12
Here's how it looks with archive & delete selected, for example. Do note, however, that selecting archive only or archive & delete will make it such that your swipe action will only be able to archive.If you still want to swipe to delete, you must select 'delete only' from the actions menu above.
Screenshot_2013-06-05-12-27-22
Yep, that's kind of annoying, right? It certainly had me scratching my head for a couple of minutes. If you haven't update to Gmail v4.5 yet, it's on the Play Store now.
By the way, if you're having trouble with multi-select in the new Gmail, fret not - it still works. Check out this article.

 

Copyright @ 2013 Android Zone.

Designed by Ijaz Hussain | Apk Apps