I just wanted to thank you for making a p4tmo version. I have one (but I use it in Canada on WIND; same bands as T-Mobile) and finally decided to bite the bullet and try this bad boy out a couple of days ago. I love this ROM!
I have been running into one issue since using it though, and after trying many things, I suspect that you're the only one that can help me out.
First off, I used to run CM 10.1 on this tablet, but when I switched to use your rom, I wiped cleanly and installed everything from scratch.
Now, I typically run a lot of apps on my device, and I'm finding that after a certain number are installed on this rom, no more apps will install either manually, through Google Play, Titanium Backup, etc. Throughout the weekend I've been trying different things such as factory resets, wiping various caches, etc but eventually, I get to the same problem where no apk will install after a certain point. I had never encountered anything like it before (and I own multiple Android devices running everything from stock to various custom roms).
In frustration, I finally decided to peek at logcat while trying to install an apk when it failed to see if that would give any clues. Not sure why I didn't try that first, but the reason why it was failing according to the logcat was that the device was out of space when the installer tried to extract the contents of the apk.
That was weird to me since I still had 2.6GB free on /data, but then I took a closer look at the various partitions using df and saw that /cache only had 140k free (it was the only partition that was close to being full; /system still has about 220MB free).
So what I wanted to try was moving dalvik-cache *back* to /data to see if that would solve this problem and allow me to install a few more programs. Unfortunately, it looks like the old vold.fstab way of doing things doesn't work anymore, and from what I can tell by Googling is that with Android 4.3 and above, boot.img has to be modified with the new mount points instead?
Unfortunately, while I'm good with Linux, making boot.img changes is where my skills end. So here is my ask of you: Would it be possible to make a flashable zip that I could install that changes the dalvik-cache mount point back to /data, just to see if that will fix this problem? Or would a whole new rom need to be compiled in order to change the dalvik-cache mount point back to the old way of doing things? Sorry if that's a dumb question; I'm not sure how the Android build system works.
Or if you have any other ideas on what I can do that's quick while I'm troubleshooting, that'd be great too! While I don't know much about how to build Android roms, I at least know my way around a linux shell.
Thanks again for the wonderful rom!