I'm happy with T-Mobile...but not with this price increase, especially since my contract is going from £11 to £12 i.e. a 9% increase. They say they can do this because I'm on a £31 plan with a £20 discount, but they didn't say anything about it being structured like that when I signed up, they just said they'd do me a deal for £11/month. Anyway, there are more important things in life than £1/month, that doesn't stop it being annoying! Why can't they just increase prices when contracts expire?
Some applications that are supplied in /system can be updated with newer versions from the Market. This only works if the apk in /system/app and the new version of the app in the Market are signed with the same keys, so if you resign all the APKs then you'll break updates of system apps.
I didn't know that, are any of those devices made by well-known manufacturers or are they cheapo ones?
http://source.android.com/porting/release_keys.html tells you not to do it:
That's what got me thinking about it, although I had to work out why it was a bad idea for myself. It would be nice if that page told you why you shouldn't use the testkeys, although I expect that some manufacturers would still ignore (or not read) it.
I think that this may introduce a security risk, albeit one that may be worth it. Because the AOSP test cert is available to anyone then couldn't anyone sign a malicious APK with the AOSP test certs and therefore be able to have their APK run as the system user?
I re-sign framework-res and other APKs that are signed with manufacturer certs with my own certificate (whose private key I keep secret) to avoid this security problem. That does have the disadvantage that themers can't just sign things with the AOSP cert - they'd have to re-sign all the "system" APKs with their own cert even if they just wanted to mod one of them.
It would probably be quite difficult for an attacker to get a malicious APK signed with the AOSP test cert onto a victim's phone because I expect that the Market wouldn't allow an app to be uploaded if it had been signed with that certificate so the attacker would have to get the victim to install the malicious APK using adb or similar.
There's an O2-branded Froyo RUU at http://shipped-roms.com/download.php?categ...4166_signed.exe which you could install before you return it if you've currently got unbranded software on there. AFAIK all Froyo ROMs support SLCD but you may want to check that before installing the RUU.
Can you share any information about how the MCR build process shrinks the ROM? I'm working on a Desire custom ROM at the moment and have run out of space on /system so any tips on what I can do to save space without removing apks etc would be very welcome!
"adb shell dmesg" should let you see printk messaged as long as your kernel doesn't crash before adbd is started. I think you might need to install busybox on your phone to get dmesg. "adb shell cat /proc/last_kmsg" and "adb shell cat /proc/kmsg" may also be useful.
AnyKernel is useful when doing kernel development, it lets you make an update zip with your new kernel without having to unpack/repack boot.img
Yes, one would expect readahead to have much less impact when using flash media than when using rotating media, but this change definitely improves SD performance. Perhaps reading from SD is faster when the data is read in larger chunks?
BTW, the readahead constants are 16K to 128K in all of the kernel versions I've looked at except HTC's 220.127.116.11 where they are 4K to 4K. Don't know why they changed them - I wish I could see their git repo so that I could look at the commit comments...
Interestingly, although readahead is 4K in the Bravo and Supersonic kernels it is back up to 16 to 128K in the Vision kernel. Perhaps HTC realised the downside of reducing it to 4K? OTOH the Vision kernel source might not be a 'descendant' of the Bravo or Supersonic kernel source.