[Android General] fuser-invent:
@ vpandey - Try deleting them and then installing them again. Apps on your smaller internal partition space should not be effected. The memory swappers change the larger internal partition with the external sd card. If deleting and re-installing doesn't work then you could have internal memory curruption or you could just need a good old fashioned factory reset.

@ sudersanmurthy - Complicated question, if you really want to know you should google it. If you just want a brief answer, the internal battery stats are crappy and inaccurate, if you want a more accurate idea of what your battery is doing try betterbatterystats and/or Battery Monitory Widget. If its stuck at 100% in TabletUI, I have no idea, other people will have to report back and let me know if its working for them in TabletUI. Could be a different dpi and its only reading the old battery percentages, which were only 0, 15, 28, 43, 57, 71, 85 and 100, with nothing in between.

@ kartikeyadhh - Thanks for reporting back, I'll try a different method at some point and delete those two zips off the mediafire account.

@ KSKHH - No it's not possible to provide mod packs. You are now caught up with my other ROMs. It's hard enough maintaining all those and all the files associated with them, breaking things down into mod packs would be impossible for me.

@ Ozadroid - You should really download one to see for yourself but here is the general breakdown of something like CM10 for Cortex A9 tablets:

CM10 ROM package - Most of the ROM is universal to all devices with Cortex A9 devices. This package does not contain a boot.img or anything else that can break your device beyond soft bricking it because it doesn't yet have the drivers specific to your device.

Compatibility Zip/Patch - Each Cortex A9 tablet that is supported will have one of these. They add functionality for hardware specific changes between Cortex A9 tablets. They also almost always contain a boot.img specific to that device with slight changes in the kernel for CM10 support. Here is an example of some of the files that could be in a comp zip:

META-INF folder - I'm assuming you know what this is.

Boot.img - I think that all the changes necessary can be made in the init.rc file but I'm not totally sure about that.

addition - This file contains build.prop changes, such as the build.prop lines for specific g-sensor positions or if the device has 2 cameras instead of one.

System Folder

Bin Folder - Usually just a wpa_supplicant here but could also need other wifi/bluetooth/radio related files.

Etc Folder - Init.d folder with CM10 specific scripts, sometimes bluetooth files

Lib Folder - egl (graphics), hw(sensors/camera/g-sensory), modules (usually additional cm10 ones) folders. There are also several lib files directly in the lib folder which control hardware and boot properties.

There could definitely be more necessary, like the set_display_mode.sh in the bin file maybe. You'd have to look at other comp zips and try to make one that you think would cover all the bases. Then you'd have to boot the device with adb logcat and watch to see if anything breaks. If it does, track down what you need to make it work from the stock ROM and add it to the comp zip.