Quote:
Originally Posted by auburnham
Thanks for the feedback arrrghhh.
1) I'd still like to understand why I've seen little effect of changing minfrees after the 9/30/11 rootfs.img. If anyone has a suggested way to investigate, I would be interested in hearing it. Perhaps I could compare every file in this rootfs.img to the 9/20/11 rootfs.img for changes? Also, what are others' typical free memory just after boot and after a reasonable uptime?
2) I'm experimenting with badboy8813's AudioPara3.csv, and it seems to work quite well at boosting the volume. I'll post if I run into any problems with it. If that doesn't work, I'll try rete's Volume+ rec (thanks, rete).
3) Voice Search wasn't included with the GBX0B bundle like it was with FRX07.1, so I didn't know I needed to install it. It is now installed and mic button is present.
The rootfs.img change isn't indented to resize the data.img, it is intended to create the data.img with a larger size. Much cleaner, IMO. Plus, I often have to recreate my data.img because of SD card issues, and the rootfs.img change saves time in the long run. Looking forward to a NAND build with as many working features as GBX0B. |
1) Minfree settings from the SuperCharger script or from manual intervention should still work fine. Why do you feel they're not being set properly? Keep in mind, it gets to a point where you just can't free up any more memory - I don't know how Android behaves if you set the numbers to something insane, I would think it would kill applications very quickly, perhaps even when you're using them lol.
3) Hum, I didn't do anything special to include it in FRX, that I know of... I'll look into it, but IMHO this is trivial - does AOSP include it?
Also, you can generate a blank data.img file to always replace yours... but do what you gotta do, I just would not recommend everyone hack the rootfs. There's much easier ways to get a bigger data.img file, lol.
Also, for me - NAND seems to work really damned well. I rarely have WinMo flashed on the device at all anymore...