Tag Archives: gingerbread
Updated: Controlling your root settings is very important, especially as it opens your Android device up to the threat of malware. if you are familiar with rooting you will know that you can tweak and modify the way your Android software and hardware behaves. Granting apps root allows you to have vastly more control of your device and apps than without.
You should though be very aware that allowing your Android device to have root access does come with an element of security and privacy risk. Given the risk, SuperSU is often used by modders to control Android root settings on a per app basis.
What is SuperSU? SuperSU allows for advanced management of Superuser access rights for all the apps on your device that need root. It’s that simple!
I’m going to assume you already have a rooted device and that you have an intermediary knowledge of device rooting using SuperSU developed by ChainfireXDA. SuperSU allows for advanced management of Superuser access rights for all the apps on your device that need root.
Here is a quick guide using SuperSU v2.78 SR1, on how to control your Android smartphone root settings:
Updated: If you use an Android device and regularly download and install apps from the Google Play Store, you may have noticed that some apps require device admin rights to be disabled before you can “Force stop” or “uninstall” an app. Device admin allows developers to create security-aware apps that are mainly useful for enterprise settings. These settings (or policies as they are referred too) may stop a user from installing or uninstalling an app for example.
I’ve started noticing quite a few Android mobile security apps are employing device admin rights to their consumer apps. The main reason for doing this is that the AV vendors want to lock down their app in the event some malware looks to disable or remove their security app, but it is also to with defining a generic security standard for mobile security app development.
Glancing through developer forums it’s clear to see (and I’m one of these) that not being able to kill an app because it is using up large amounts of CPU or RAM time, isn’t that useful to us end -users. Apps and operating systems do have memory leakage and probably always will from time to time. So, how do you disable device admin rights for a particular app so that you can enable ‘Force stop’; ‘Uninstall’; ‘Clear data’; ‘Clear cache’; and ‘Clear defaults’ from within App Manager? It’s actually very simple folks:
Have you ever wanted to download an app from Google Play to be told that your device is incompatible? Not all apps are available in every country. You might want to install an app that is only compatible for the US.
Read on to find out how you can trick Google Play into thinking your device is compatible. You can edit a file called ‘build.prop’, but you will also need access to another Android device that doesn’t have incompatibility issues with Google Play. Accessing ‘build.prop’ can only be done on a rooted device and comes with the obvious warnings.
‘build.prop’ (it’s like config.sys file in Windows) is an editable text file (referred to as ‘strings’) that identifies your build id i.e. KTU84P; model, sensors; network info; stack tracing data and more. Follow the steps below very carefully:
- Make sure your device is rooted and you have the ‘build.prop’ file for the device you want to imitate*
- Backup your device data with a Nandroid full ROM backup in recovery
- Using a root file explorer (ES File Explorer is my favourite) app search for ‘build.prop’
- Backup ‘build.prop’ to your SD card, so you can revert to this if you encounter problems
Mobile phones are stolen daily. Most are never recovered. Locating your lost mobile can be challenging. Apple has the Find My iPhone app and BlackBerry has BlackBerry Protect. Both location finding software work well, but when the device is wiped and another SIM is used, it will be impossible to track your device. Note: BlackBerry devices can also be tracked using the PIN (the one you use for BlackBerry Messenger), but I don’t have evidence to confirm this.
If you have lost or had your device stolen (this includes Android and Windows Phone), you will in most instances call your mobile carrier, who will ask you whether you have insurance and or whether you want to pay for a new device. What you pay depends on whether you have insurance or not. The Police will normally track your phone number and IMEI number, but this will not help you if someone replaces your SIM. Okay, you say – what should you do?
All mobile devices have unique identifier called an IMEI – you can call it a serial number. Using your dialler type *#06# 9 (called a USSD code) if you don’t have the original box that you device was packaged in. The IMEI number is also tied to the ICCID (Integrated Circuit Card ID) – you can find this on most devices in Settings > About.
I’ve been frequently asked how you can manage Google Settings content (this includes data requests from Google apps) and privacy. Most people I speak with didn’t even know there was an icon (app) on the home screen that allowed you to access a Google Settings app (it actually isn’t an app) which allows you to proactively manage your data privacy.
It’s actually a powerful tool that every Android device should have on the home screen by default. One theory I have why this isn’t the case is that Google doesn’t want you to know what it’s collecting. If there is public concern, Google can turn around and say we provide an app that allows users to manage the data flowing out of your device.
If you wish to manage you Google Settings more closely (and I suggest you take some time to look at these features), I recommend you click on the Google Settings icon, which can be found on your home screen.
Tap > Google Settings icon and this will present you with the following list:
- Connected apps – these are apps that are connected to your Google account