Quote:
Originally Posted by arrrghhh
1. I wouldn't worry about specific numbers - I seriously doubt he was looking at his free memory correctly.
2. I don't know, but I assume if you look at the WinMo threads on increasing volume, they involve mucking with those CSV's. Look at what they change, and try tinkering. Let us know what works.
3. It's fine here, I see the mic no problemo... Do you have voice search installed?
Also, why the heck would you muck with the rootfs just to resize your data.img? lol.
[APP] Windows: Create Your Own Data.img Maker Application, +/- From Existing data.img - xda-developers |
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.