Thanks, following your instructions, I re-partitioned using Tailor in WebOS and did a clean installation with cwm 22.214.171.124. And now everything works perfect except with one instance of auto shutdown because of low battery, which was not the case. And after that, it simply runs smooth. Now one function that I desperately would like to have is a working BT so that I can do some simple programming on my touchpad.Simply flashing a CM11 4.4 ROM (clean or dirty flash) means you will end up with a completely messed up storage sd card partition layout and actually a system which isn't really usable in the long run, forget it. However, with patience there is a way around this though, as Milaq rightly states in his original post and that is to re-partition the drive (sd card) so the maximum amount is given over to data as opposed to media storage, this means that when the 4.4 rom is flashed it sees the whole of the sd card and treats it as a single drive which is the way its all going using new datamedia builds. This however is not straightforward and takes some thinking about, but it can be done and is well worth it in the long run. I sugget that RolandDeschain79 really needs to update this and other posts as it is extremely misleading to let people think they can simply flash 4.4 - CM11 following his guides - as you really should not, especially as the newer kernels are being used. The video tutorials created by RolandDeschain79 are absolutely magnificent and have helped me a lot but I would like to suggest that a whole new video is created (the existing one is good but could be improved) to fully explain re-partitioning with 'Tailor' (this is the only way to do it forget all other ways using Apes flashable fixes and the like as they do not work properly). Sideload the ROM and Gapps using ADB from recovery using the feature in CWM 126.96.36.199, is really the only proper way to install CM11 KitKat on the Touchpad and make use of its storage capability in one simple easy to navigate installation. I will help others where I can as I just spent the whole of yesterday figuring this all out and now have a 32GB Touchpad that runs Milaq's CM11 the way it should be, its fantastic and well worth the effort.
Camera still not working.<jcsullins> yasin: bluetooth, vpn, fix USB connect failure, multi-charger detection, a6 read/write retry (avoid spontaneous batt=0% when it's not), a6 reflash support, sesnors fixes, sleep power drain improvement, fix recents not working until first sleep
If you wish to remove Android completly and start over you will need to run iMarck90's ACMEUninstaller2.I am new to ROMs on Touchpad and I am learning a great deal from the FAQs. I have had problems like no gapps and I was able to ascertain how to locate the correct gapps to use. I have found the method to install and deinstall. I have t say I am stumped on thie one though. My system is coming up with what looks like a cell phone interface and I cannot get it back to an earlier working version android. Is there a process to WIPE, like really WIPE this thing clean? And start over?
Thank you for posted the detailed information about the build, I will add it to the OP of this thread. I wonder what A6 reflash support means. Does that mean it will work when we run it or is there some sort of built in reflash option for it. I'm thrilled to see the progress Jcsullins has made with CM10.1 and 3.0 kernel :grin:New build with kernel 3.x from jcsullins http://goo.im/devs/jcsullins/cmtouchpad/testing/cm-10.1-20140125-EXPERIMENTAL-3KERN_TEST-tenderloin.zip
This is the changelog
<jcsullins> yasin: bluetooth, vpn, fix USB connect failure, multi-charger detection, a6 read/write retry (avoid spontaneous batt=0% when it's not), a6 reflash support, sesnors fixes, sleep power drain improvement, fix recents not working until first sleep
Camera still not working.
Tested with ACMEInstaller4
I was getting an average of around -8 to -20 during deep sleep but I had to charge it shortly after. This is a good low to medium battery drain.How's the battery drain?
Been running JCS Jan 25/14-3.x build for about 24 hoursHow's the battery drain?
New 3.4 jcsullins 10.1 experience:Wonderful! I flashed a few hours ago. I'll see how battery drain is for me as well as overall experience. (coming from JCS vpn build)
Thanks for the change log reference iMarck90!I have insurance...lol! Thunderbolt has a 100 dollar deductible, so by the time I find a case I like that fits the extended battery, I could drop that much in the process I may as well save it for the deductible...
sent via rooted THUNDERBOLT with Tapatalk
Did you see my "The future of Android" post. I wouldn't get your hopes up of changing Google's intentions to lock down Android.- And if you hate gMaps 7.x like I do:
[APP]install Google Maps 6 and 7 and use them together[Root/NoRoot][14.01.2014]
And feel free to slam gMaps by review in the PlayStore, its the only way we might be able to get some of these features back.
I can confirm that Jc's CM10.1_1/25/14 3.x kernel build apparently has the "Fast charge" (AC Charge) implemented ("multi charger detection" as mentioned in the change log on IRC iMarck90 shared) and is charging fine on "apple" and android ports (all but the Samsung Tab port) like it did on the earlier VPN 2.x kernel build.Small update on JC's 1/5/14 CM10.1 with 3.x kernel build, my minor charge glitch hasn't resurfaced on the HP Charger, but on a related note I do not think that the same previous "charging" features are present in the build.
I say this because I recently purchased an Anker 5 Port/5A charger (see my review for details and spreadsheet here) which on the prior VPN build would "Fast charge" (AC Charge) on all the ports except the Samsung Tab port (not sure yet why it's different). On this latest 3.x Kern build, it won't charge on anything but the one "Android" port (AC Charge) which indicates to me that "Fast Charge" isn't enabled within the 3.x kernel as it was on the 2.x kernel in prior builds...yet. (Still charges normally on the HP barrel charger).