This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
I have a UK milestone, but am in Slovenia. I've got used to not having access to paid apps in the market. What bothers me is that some of the free apps are missing from the market. Is there any solution for that? + Where could I find a version of the google maps with buzz?
I have a UK milestone, but am in Slovenia. I've got used to not having access to paid apps in the market. What bothers me is that some of the free apps are missing from the market. Is there any solution for that? + Where could I find a version of the google maps with buzz?
The problem is that paid apps are not your problem - protected apps are your problem. Many free apps are protected.
I don't know that anyone has bothered to pull the APK for Google Maps 4.0 for Android. Here is the file directly lifted from /data/app on my phone. I do not know if it is installable like this - try it.
By the way, if you root your phone, you can install Market Enabler (I don't need it, but if you search, you'll find it...), which enables protected and paid apps for anyone. Apparently it works perfectly.
The UK 2.0.1 is a 1.14 version, and it still had the hackable recovery - meaning it does not verify the signature on an encapsulating zip file around the stock update. So any update.zip can be used, as long as it has been properly modified to just copy and set rights on su and SuperUser.apk.
Maybe the version that you downloaded was corrupted? Try unzipping it on your PC/Mac/Linux system to see if it is a viable file.
The simple answer is that you do not overclock it.
To get a bit more detailed, even though we have root on the Milestone, we cn't change the kernel, and without a changed kernel, we can't overclock.
If you want to know why, Motorola implemented a signature checking feature in the chipset for the bootloader and for recovery - if the bootloader is not properly signed, the chipset won't start it. They then have the bootloader refuse to load unsigned kernels. We COULD change either, but then the phone would not boot. So far, nobody has found a way around this limitation.