Archives for

How To

How to wipe cache partition on Samsung Galaxy S9 and what are its benefits?

Your Samsung Galaxy S9 has sophisticated technical specifications–that translate into an impressive hardware–and a feature-packed firmware. Unfortunately, these are not a guarantee that your device could no longer encounter problems either with its hardware or firmware. When it comes to issues with the operating system, you can always use the Factory Reset to address them. But what if you already have installed a lot of apps and saved tons of files into your phone’s internal storage? To do the reset should be the last thing you should do and this is where the wiping of the cache partition enters.

To wipe the cache partition means to delete all system caches stored in the directory but there’s more to it than just deleting those files. After wiping the partition, the phone would then boot up and deleted caches will be replaced with new ones. So, if you have issues with your phone that are caused by some corrupt caches, they will surely be fixed and your phone will work perfectly again.

Below, I will enumerate the benefits of wiping the cache partition. But before going further, if you found this post because you were trying to find a solution to your problem, then try to visit our Galaxy S9 troubleshooting page as we’ve already addressed most of the commonly reported issues with the phone. We’ve already provided solutions to some of the problems reported by our readers so try to find issues that are similar with yours and use the solutions we suggested. If they don’t work for you and if you need further assistance, fill up our Android issues questionnaire and hit submit.

Benefits of wiping the cache partition in your Samsung Galaxy S9

This method is often done when a user has some issues with his / her phone but we suggest you do it from time to time to make sure all caches in your phone are new and up-to-date. Why? It’s because of the following benefits.

Wiping the cache partition will make your Galaxy S9…

  • Run smoother
  • Open apps quicker
  • Avoid glitches in either the firmware or hardware
  • Fix minor problems that may occur every now and then
  • Refresh your phone’s memory
  • Boot successfully when it gets stuck on the logo
  • Improve performance especially after firmware updates

Now that you know the common benefits of wiping the cache partition in your Galaxy S9, you’re ready to do it in your phone.

How to wipe cache partition in your Samsung Galaxy S9

Just like doing the master reset, you also have to reboot your Galaxy S9 to Recovery Mode to access the option to wipe the cache partition. Follow these steps…

  1. Turn off the device.
  2. Press and hold the Volume Up key and the Bixby key, then press and hold the Power key.
  3. When the Android logo displays, release all three keys.
  4. An ‘Installing system update’ message will show for 30 – 60 seconds before the Android system recovery menu options appear.
  5. Press the Volume down key several times to highlight wipe cache partition.
  6. Press Power key to select.
  7. Press the Volume down key to highlight yes, them and press the Power key to select.
  8. When the wipe cache partition is complete, Reboot system now is highlighted.
  9. Press the Power key to restart the device.

Your phone will take a little time booting up after the cache partition is wiped off of its contents as it will rebuild or recreate those caches. Don’t be alarmed if the phone gets stuck on the logo for a minute or two after this just don’t turn it off so that what were deleted will be replaced successfully. So, wait for your Galaxy S9 to become active. Don’t worry, this procedure is very easy and safe to do. You won’t damage your phone just by wiping the cache partition.

I hope that this post can help you one way or another. If there’s something you want to share with us, you may contact us or leave a comment below.

Connect with us

We are always open to your problems, questions and suggestions, so feel free to contact us by filling up this form. This is a free service we offer and we won’t charge you a penny for it. But please note that we receive hundreds of emails every day and it’s impossible for us to respond to every single one of them. But rest assured we read every message we receive. For those whom we’ve helped, please spread the word by sharing our posts to your friends or by simply liking our Facebook and Google+ page or follow us on Twitter.

Posts you may also like to check out:

How To Get Started Programming Android (Part 2): Free Resources

Android for Beginners

There are a plethora of free resources out on the world wide web all willing to teach you the Android mobile programming language for free. Google has a wealth of information available to interested users at a simple search of a word. Keep in mind that while there is a wealth of free knowledge out there, there is also a plethora of scams. Most of these scams are, of course, not free. To name one scam right off the bat that most of you will run into during your searches is edumobile.

As I mentioned above, the first thing that you are going to want to do is do a few Google searches. Again, there is a gold mine of information there. A simple search for “beginner android tutorials” pulls up nearly 3 million results  Those three million of results can’t fit in a single blog post, so you may want to sift through Google to find a good resource for yourself if none of the below resources help you out.

The second free resource you are going to want to look at is free e-books. As I said in the first installment in this tutorial series, books are your friend for a multitude of reasons. To summarize that, there is wealth of knowledge that you could easily find on the internet, but in a book it is often all congregated in one place with projects at the end of each chapter to help you retain the knowledge the book taught the reader.

Another great option is to get involved with an Android Google Group. I use them quite often and I swear they have all of the answers to any question you would ever ask. If they don’t, they are ambitious enough over there to figure it out themselves. Granted, these groups are massive– 25,000 members on [android-developers]. While you are guaranteed to get an answer from someone, it’s a tad chaotic. If you can handle the chaos though, getting involved in android-developers or android-beginners could be one of your best choices.

Lastly, for your general questions you are going to want to look at developer.android.com. That website is Google’s own Android website, which answers a lot of general questions people have. Not only that, but it’ll get you started programming Android in no time. Granted, I wouldn’t say that it is a great source to learn the entire Android language, as there aren’t a whole lot of tutorials on there (there is a whole heck of a lot of documentation though!). As I said, it’s essentially general knowledge to any Android programmer. You could say it is the “Hello World” of any other programming language.

In the next tutorial, I’ll be listing off resources to learn Android that will cost you a bit o’ cash. I personally think considering paid resources is essential in learning Android because both parties (the consumer and the seller) are happy. The consumer purchases a lengthy book that looks likes it worth learning from while the seller gets some revenue for essentially teaching the consumer how to do something like Android programming. You don’t need paid resources to learn Android, but they are more often that not very helpful.

Galaxy Tab 10.1 P7510 CyanogenMod 10.1 Android 4.2.1 Jelly Bean ROM now available [Tutorial]

galaxy tab 10.1 cm 10.1

Samsung Galaxy Tab 10.1 with model number P7510 is among the few Android tablets that recently received good treatment from CyanogenMod team of developers. The CyanogenMod 10.1 Android 4.2.1 Jelly Bean ROM has been made available for download a few days ago for people who want to take the risk of flashing unofficial ROMs and mods into their device to take advantage of features that stock ROMs never offer, or at least, be one of the few to enjoy the goodness of v4.2.1 version of Android. Here is our step-by-step guide on how to install CM 10.1 Android 4.2.1 JellyBean ROM into your Galaxy Tab 10.1 P7510.

Pre-requisites/Reminders

  1. To be safe, there should be, at least 80 percent of battery left in your device but it is advisable to fully-charge it before flashing this ROM. Probability is your device will be bricked if it powers out during the installation.
  2. Your device’s bootloader should have been unlocked. Also make sure your device is rooted. Here is our guide on how to root your Android device.
  3. Clockworkmod Recovery should be installed in your device as you will be using it to flash this custom ROM. Here’s how you install CWM Recovery.
  4. Make sure you have made a backup of all your data in your device’s internal memory. Backing up data is easier than you think, here’s our guide.
  5. Enable USB Debugging in your device.

Disclaimer: You cannot blame The Droid Guy or XDA Developers for possible damages caused by this tutorial. All ROMs and mods used in this guide are credited to their developers.

Files to Download

  1. CyanogenMod 10.1 Android 4.2.1 Jelly Bean ROM [LINK HERE]
  2. Google Apps for this build [LINK HERE]

Step-by-step Tutorial

Step 1: Download all packages specified above and save both in your computer. Don’t extract them, just save them in a directory you can easily remember and access.

Step 2: Connect your Samsung Galaxy Tab 10.1 P7510 to your computer using the USB data cable.

Step 3: Copy both packages into your device’s internal memory but make sure you save them in the root directory and NOT in any folder. This is to make them detectable by ClockworkMod Recovery.

Step 4: After copying those files, you may now disconnect your device from your computer and turn it off.

Step 5: Boot your Galaxy Tab 10.1 into recovery mode. You can do so by pressing and holding both Volume Up and Power buttons simultaneously. Continue doing this until you see Tab 10.1 logo on screen then release the Power button but keep holding the Volume Up button.

Step 6: Once inside the recovery mode, it is imperative you make a Nandroid backup of your current ROM so you can always revert to it if things don’t work as expected or if you don’t like the custom ROM. Choose Backup and Restore => Backup. After doing so, go back to main recovery menu.

Step 7: You need to do a full data wipe, select Wipe Data/Factory Reset => Yes. This process may take a few minutes so you need to wait a bit before it’s completed.

Step 8: You may now install CM 10.1 Android 4.2.1 Jelly Bean ROM: choose Install zip from SD Card => Choose zip from SD Card and browse through your internal memory’s root directory and select the CM 10.1 package. Wait until the installation is complete.

Step 9: Choose Install zip from SD Card => Choose zip from SD Card again but this time choose Google Apps package to install necessary Google applications.

Step 10: You may now reboot your device and wait until it’s fully active before you use it. Go back to main menu and select Reboot System Now.

Your device is now running CyanogenMod 10.1 based on Android 4.2.1 Jelly Bean ROM. Do let us know if this works for you.

[source: XDA Developers]

How to Install Official CyanogenMod 10.1 AOSP 4.2.1 JellyBean on Nexus 7 3G

google-nexus-7

The official CyanogenMod 10.1 AOSP 4.2.1 Jelly Bean custom ROM for Nexus 7 has finally been released after weeks and weeks of development. We have seen all efforts done by developers to release a much stable version so, all credits go to them. Of course, together with the release of this ROM is a rough guide that Android enthusiasts can follow to install it successfully into their devices. However, the developer disclosed there are still some things that don’t work after the installation of the ROM including the following:

  • Bluetooth (& bt-tethering)
  • Wifi tethering (use an external app, e.g. WiFi
  • Tether for Root Users)
  • USB-tethering (use an external app)
  • FM radio

Rest assured the development continues and a more stable build may be released a few days from now. If you think you live without the abovementioned functionality and wishes to try what CM10.1 has in store for Nexus 7 3G, here’s a guide to walk you through the installation process.

Pre-requisites

  1. Your device must be rooted. Here’s our guide on how to rood Android devices.
  2. Make a backup of all your important data including your SMS, contacts and files. [Guide]
  3. Download CM10.1 AOSP JB package from here. [Link]
  4. Download Google Apps from here. [Link]
  5. Make sure you have sufficient battery left; at least, 50% is advisable.

Disclaimer: You cannot blame The Droid Guy or XDA Developers if something goes wrong with your device after the process. It is advised only owners who have vast knowledge on how to flash custom ROMs to their devices should continue with this process. At the end of the day, the decision is yours whether to flash this ROM or not.

Important Note: Make sure you install Tilapia Recovery first to avoid “Status 7” errors. XDA Developers have a better way to do this. Just follow this link.

Quick Step-by-step Tutorial

Assuming you have installed necessary drivers for Nexus 7 on your computer, it is just a quick process. Otherwise, take a little time installing them before you do the first step.

Step 1: Connect your Nexus 7 to your computer using the USB data cable and wait until it is fully detected. Copy the packages into your internal memory.

Step 2: Boot your Nexus 7 into recovery mode by pressing and holding Power, Volume Up and Volume Down buttons until you can see Android robot lying on its back. Once in recovery mode, use volume keys to navigate and Power button to select.

Step 3: Now flash the CM10.1 JellyBean package by navigating to the directory inside your device’s internal memory and choosing the zip package.

Step 4: Do step 3 once again but this time choose Google Apps package.

Step 5: Reboot your device and wait until it becomes fully active before using it.

Now, enjoy the new custom ROM. The development is still ongoing and updates will be posted here as soon as developers release new updates.

[credits to: XDA Developers]