[TouchPad Development] nevertells2:
Please satisfy my curiousity. What it the file size of the uImage.evervolv in the /boot folder? I have Milaq's CM11 3.0 kernel dated 02/24 installed and Root Explorer reports /boot folder at 18mb and change. With that much room, I have J.C. Sullins CWM DM and TWRP DM both installed which increases the size of /boot to just over 25mb and I still have about 5.5mb space left. With Flintman's Rom installed, what is the reported size of the /boot folder? I haven't installed my Moboot background file yet, but it's not like I don't have plenty of room.

When I was running J.C.'s CM10.1 Bluetooth snapshot build with my moboot background installed, I only had around 1.7mb left in /boot. So something in DM builds, at least Milaq's, is leaving a whole lot of extra space.

---------- Post added at 05:57 PM ---------- Previous post was at 05:51 PM ----------

Wish one of the knowledgeable developers would at least explain why a resize zip (or include it in ACMEInstaller) could not be created that would borrow like 5 or 10mb from the media partition(old WebOS SD card/USB drive) for /boot. I'm not a coder or developer, but we seem to be able to resize every other partition on the TouchPad, why not /boot?

---------- Post added at 05:59 PM ---------- Previous post was at 05:57 PM ----------

Please don't think I'm being whinny on this, but why. Do you know of anyone that has tried and failed? Just trying to understand. Thanks

---------- Post added at 06:01 PM ---------- Previous post was at 05:59 PM ----------

Looks like this needs a little J.C. Sullin's TLC. :)

---------- Post added at 06:18 PM ---------- Previous post was at 06:01 PM ----------

@Flintman,

Being that Evervolv is what would be considered a plain vanilla ASOP build of Android, have you ever considered playing around with Exposed and the Gravity Box module? I've messed around with it on another device to add back in a lot of the options that are missing on ASOP builds. I had never heard of it until I mentioned to the developer on that device about some of the features that were missing that I was used to on CM builds. Gravity Box is just one of dozens of modules available once Exposed is installed. A few of the modules are device specific, but most appear compatible with any device running a non-customized Rom like ASOP. Customized Roms like CM not recommended.

The developer also uses the Aroma Installer to install his Roms. As long a the device is unlocked and has a custom recovery, in this case TWRP, the options to have the choice of multiple kernels, optional programs, a variety of tweaks and many other features is really cool. Aroma is kind of like a wrapper with the Rom, tweaks, kernel and other stuff all neatly packaged inside. One starts off Flashing the zip from TWRP and then Aroma takes over and offers you all the options. When you are done with the selections, the install is performed with the features you have selected.

---------- Post added at 06:24 PM ---------- Previous post was at 06:18 PM ----------

One last question. The OP says that the mic is fixed as of 02/20 and you have a specific link for that. But when I look on your website I see a 03/10 build. I'm prepared to be punished here for this question, but I got to ask. :fingers-crossed: Better to ask and not know for sure than not ask not know the answer. Does the 03/10 build have the mic fix. Thanks