Nexus 4 gran descuento

El LG Nexus 4 de Google ahora cuesta 100€ menos!!!
Impresionante e insuperable relación calidad/precio.

https://play.google.com/store/devices/details?id=nexus_4_8gb

Linux Mint Debian, Google Chrome, libnss

Linux Mint Debian runs under Debian Testing, but the updates come in a form of compilation packages from Linux Mint. Not directly from Debian Testing.

With the latest update of Google Chrome beta on Linux, i was unable to launch the browser. I had to run it from terminal to see what was happening.

The problem was the library libnss, it was too old for the new version of Google Chrome browser. So i decided to add the Debian Testing repository to apt. And then update and upgrade the system.

Add "deb http://ftp.debian.org/debian testing main contrib non-free" to the file /etc/apt/sources.list
Exec apt-get update and finally apt-get upgrade.
A reboot is recommended.

At the moment i don't have any problem, as it is a modded Debian Testing.

How to delete apps from /system/app

First of all, this is for rooted devices only.

If you try to delete some apk files from /system/app, you will get an "Read-only file system" error. This is why /system is mounted as read-only.

To be allowed to delete data from /system/app, we need to remount it as read-write. How can i do that? Well it is very simple, we only need a Terminal application and execute a few commands.

1. Open our Terminal application and exec the command "su" (super user, root) to request root privileges.
2. Exec the remount command: "mount -rw -o remount /system".
3. Then we can delete the desired files with the command: "rm /system/app/file_name". Proceed with caution! And don't delete files if you don't know what are you deleting!
4. Reboot. At the next start /system will be read-only as it should be.

This is very useful for removing app's that are included with our rom's by partners or manufacturers, and can't be uninstalled with the app manager.

Android 4.3 Restricted Profiles

With the new version of Android, Jelly Bean 4.3, we got a new profiles system. Now we have the option to create content restricted profiles.

App developers can limit the content inside their apps, if it's running on a restricted profile. With the new restricted profile system we can also limit which app's can be used in such profiles.

However, a lot of apps have to be fixed, because if we are using an app, and that app wants to start a not permitted activity on a restricted profile, then the app will crash.

The fix is simple, we have to check if the activity we want to launch exists, and if it exists we proceed to launch it. If the activity exists, it means that we hace access to it, so it's permitted.

developer.android.com example:

Intent intent = new Intent(Intent.ACTION_SEND);
...
if (intent.resolveActivity(getPackageManager()) != null) {
    startActivity(intent);
} else {
    Toast.makeText(context, R.string.app_not_available, Toast.LENGTH_LONG).show();
}