yashsingh1/xdaforums huggingface dataset:
[TouchPad Development] googlephone:
All you apps are installed to data partition. You can do move to sdcard to move apps from data to USB media partition if the app supports moving to sdcard.

The USB media can be used by apps like games. Games apps are installed on data partition but can use USB storage for the game download files. So for your 1.5gb game, the game app is installed to data partition which is only few MB but the game files like 1.5gb usually goes to USB storage.

If you are using data media android build both game app and game files goes to a single dynamic partition: data media partition which serves as a combination of data partition and USB storage partition.
[TouchPad Development] pdawg17:
For real this time last question.

So to "undo" datamedia I just need to redo the partition sizes and use a "normal" recovery image?
[TouchPad Development] googlephone:
For my understanding, you just need to flash back to a non-datamedia recovery then flash a non-datamedia rom. You can adjust the partition sizes if you don't like the data partition being so big as in datamedia build.

Edit: if you use a non-datamedia recovery and do a factory reset, you will loss all your apps and data on the data media partition from the previous data media build. So backup your apps and data on the data partition first.
[TouchPad Development] flintman:
OK MORE GREAT NEWS.

After digging, dmesgs,and the help of Jcsullins and flemmard the video reboot issue is resolved. I'm currently working on a test build now for everyone to try out.

HERE is what is BROKEN

* MIC

* BT

* Camera.

Everything else seems to be find but i need your help to test this out.

I have moved the device to the 3.4 kernel in evervolv so going forward all releases, nightlies, test builds will be for the 3.4 kernel. The broken items are actively being worked on. Remember you will need to update your recovery to support SELINUX. Linked in a few posts back.

Have a safe and Happy New Year
[TouchPad Development] siralsmooth:
The news I think everyone has been waiting for. Great way to close out 2013 Flintman. Many thanks for all you and the other developers have done for the touchpad community this past year.
[TouchPad Development] flintman:
OK link is up Please read the first post for what is not working and all the good stuff. Logcats/Dmesg if anyone is having an issue with help to solve these problem.

Enjoy and more to come 8)

Have a safe and Happy New Year
[TouchPad Development] dplane:
sweet awesome. Thx flintman. i tried one of your way early kit kat builds but have since been back on the jb base but the recent kernel changes make me want to try kit kat again. question though; i found the IMG file for the suggested recovery but is there also a flashable zip somewhere or does it need to be adb pushed?

Thx!!
[TouchPad Development] flintman:
There is no Zip will need to adb push it. I believe i also posted a link to how to adb push it if you need it
[TouchPad Development] jerryatherton:
BOOT FAILED

Clean install, do I need to remove old evervolv.uImage
[TouchPad Development] dplane:
Okay np, Ill look for it. I assume it's not a whole lot different from adb pushing things through fastboot/hboot on HTC devices (done that a lot).

thx again and happy new year to you and your loved ones as well! :highfive:
[TouchPad Development] jerryatherton:
Download the file in his post a few pages back . Use a root explorer rename it, uImage.TWRP , then move it to the Boot folder, works fine

---------- Post added at 01:32 PM ---------- Previous post was at 01:17 PM ----------

OK, that worked. Do a backup with your new TWRP, then reboot into system, go into Boot folder and delete evervolv.uImage.

Shut down system, start up and boot into TWRP , I did a full wipe then install.

And it boots up

But WiFi will not turn on.

EDIT: Reboot made WiFi work
[TouchPad Development] dplane:
hmm installed TWRP, did a full wipe and when I try to flash the new build I get this error:

Formatting system

Installing Evervolv

symlink: some symlinks failed

E: Error ececuting updated binary in zip 'sdcard/Download/ev_tenderloin0testing-2013.12.31.zip'

Error flashing zip '/sdcard/Download/ev_tenderloin-testing-2013.12.31.zip'

any idea why or what is going on?

Thanks and sorry to be a pain..first time I ran into issues on the TP so its probably user error :/
[TouchPad Development] flintman:
Do an md5 on the file to ensure its not a bad download. Or try and redownload
[TouchPad Development] scy1192:
The new build installed and works fine, but when it falls asleep it doesn't wake up and needs a hard reset.
[TouchPad Development] nikos5800:
use power button to wake up touchpad
[TouchPad Development] flintman:
Can you get a logcat/last_klog?
[TouchPad Development] flintman:
Yes home key doesn't wake device. ATM
[TouchPad Development] scy1192:
On second look it seems maybe my battery died. Seems to not want to charge while the ROM is booted up (went from 20% to 0%, booted up and went from 3% to 0%). I'm charging it in WebOS right now so we'll see what happens. What could help diagnose a charging problem?
[TouchPad Development] flintman:
Dmesg. Ive had my drain down to 0 and charged while booting also try another cable. I have had a similar issue about a year back.
[TouchPad Development] pdawg17:
Having a "first time" problem with charging as well...plugged it in with TP cable and charger like always and now I came home and it had drained completely...weird...
[TouchPad Development] groo_pcd:
Just flashed the new test build (3.4 kernel). Great work devs, you did it again :)

Now for the bugs, missing stuff i found so far.

First, a question. What is the recommended gapps now? i was using the gapps-jb-20130813-signed.zip but since we are now using kitkat, i flashed the latest core that shows up in the update evervolv app.

Since its only the core, i had to reinstall some core apps (like youtube, gmail, etc), but unfortunatelly gmail still fcs on me.

So, what gapps does the devs recommend now? kernel 3.0 or interactive < kernel 3.0), so if you changed it with an app or the settings -> toolbox feature, and changed it to ondemand/interactive, YOU WILL TRIGGER THE SLEEP OF DEATH. KEEP IT AT PERFORMANCE AND THE SLEEP PROBLEM GOES AWAY.

conservative and performance appears to avoid the sleep of death, ondemand/interactive triggers it each time you turn off the display.

Conservative will crash and reboot after a few minutes with the display turned off, so its performance and lousy battery life for now. :)

Now, the correct way would be to allow us to overclock it at least to 1.5ghz (i run it always at 1.78ghz without a problem). and to test the governors to make sure its safe (i guess thats in the todo list :))

- missing printer services

this makes sense since google cloud print service is a gapps app and the cloud print in the play store is only the client. The HP printer service works fine if installed from the play store.

Over all, im very VERY impressed with the smoothness of this alpha build, its smooth at 1.1ghz, i cant wait to be able to crank it up to 1.78ghz.

looking forward for the nightly builds, and some word on the recommended gapps.

keep up the good work devs and community, you rock :)
[TouchPad Development] hwti:
I found something.

On 2.6.35 (milaq CM11), I have :

/sys/kernel/debug/clk/pixel_lcdc_clk/measure => 96Mhz

/sys/kernel/debug/clk/pixel_mdp_clk/rate => 128Mhz

On 3.4 (Invisiblek build) :

/sys/kernel/debug/clk/pixel_mdp_clk/rate => 106.5Mhz

pixel_lcdc_clk follows pixel_mdp_clk

The available pixel_mdp_clk rates are not the same on 2.6.35 and 3.4 kernels...

I only get the blue pixels with the 106.5Mhz clock, other values (not too low, else display blinks or is blank) work.

For example, "echo 109714000 > /sys/kernel/debug/clk/pixel_mdp_clk/rate" immediately fixes the problem (but the values resets itself each time the screen is turned on).
[TouchPad Development] flintman:
I used pa gapps. The old jb gapps no longer work with with 4.4.2. Make sure you used kk 4.4.x gapps. Ill locate some and post a link when i get home
[TouchPad Development] flintman:
http://d-h.st/Iyf These should work fine
[TouchPad Development] flintman:
Looking at this now. Along with some other fixes
[TouchPad Development] groo_pcd:
tks flintman, happy new year ^_^
[TouchPad Development] flintman:
Working a new build for tomorrow. Should fix alot of the issues you may be having with lagging and what nots. Also working on adding in MTP with the option to use UMS. That may or may not be in tomorrow build
[TouchPad Development] nevertells2:
Actually the name should be uImage.TWRP. And that's an uppercase i in uImage, not a lowercase L.:)
[TouchPad Development] RolandDeschain79:
Good things coming in 2014

Great news Flintman thank you:good: Looking forward to another great year of exciting HP TouchPad Development! Have a very Happy New Year Flintman:highfive:
[TouchPad Development] nevertells2:
Lots of apps on the Play Store that let you overclock. It's built into Rom Toolbox Lite. Set CPU and Antutu CPU Master Free are some others.

---------- Post added at 10:31 PM ---------- Previous post was at 10:30 PM ----------

Wonder why Google has not put out a KitKat Gapps yet?
[TouchPad Development] allstar319:
I actually thought the same thing when I loaded up the 20131226 build (i think?), but the 1.1ghz option was the highest SetCPU would go.
[TouchPad Development] jerryatherton:
Oops, sorry
[TouchPad Development] groo_pcd:
I agree, but the kernel needs to have the option to be over clocked compiled. in its current form, this release kernel only goes up to 1.1ghz. the apps only change whatever range was configured at compile time.
[TouchPad Development] flintman:
Want to get a solid kernel then can work on being able to over clock.
[TouchPad Development] pit-pit:
anybody have issues with vibration ? i have no vibration at all but its not a big issue for me just wanted to point this out btw good job to all the devs finnaly a 3.4 kernel what a grat way to start the year :D
[TouchPad Development] gradular:
Google? Lol. You mean goo.im?
[TouchPad Development] siralsmooth:
While agree on a solid kernel w/o overclock, there are the select few such as myself with a 64gb with the 1.5 native clock. Considering the touchpad was underclocked on the normal models , wouldn't a 1.5 clock be a normal clock for testing?
[TouchPad Development] allstar319:
I believe that was because HP needed something else to differentiate that model from the others, so they downclocked the 16 and 32 gig TP's. Eh... While I would like to OC to 1.5, I'd rather the rest of the work be done on the kernel first.
[TouchPad Development] nevertells2:
Not really. They just host files. Here is what it says on this link under licensing/download: http://wiki.rootzwiki.com/Google_Apps

"Please note: The CyanogenMod Team, TeamDouche, Steve Kondik (Cyanogen) and related parties are not involved with the creation of the Google Apps packages. The packages are found on the Internet, tested by a variety of community members, and if they pass testing and fill a need, they are marked as recommended by the Android community, and provided for download via trusted mirrors such as Goo.im.

The Google Apps are the intellectual property of Google Inc,

and are provided to restore the applications which come on devices which are licensed to have Google's proprietary code."

And yeah, I should have asked I wonder why someone had not created a GAPPS for KitKat yet. Definitely nothing here or on goo.im yet.
[TouchPad Development] _kevn_:
PA 0-day Gapps - http://xdaforums.com/showthread.php?p=44417509

Banks Gapps - http://xdaforums.com/showthread.php?p=34610569

Take your pick of which you'd like to use. Banks Gapps I've heard are more minimal where you usually won't get anything that can be downloaded from the play store. So if you like smaller packages his might be better.

I typically go with the PA Gapps because I've gone mostly all Google so I like to have them all installed from the get go, then I don't need to download the ones I'm using most often.

I suggest reading both of them and deciding which suits you best.

I hope that helps someone with their hunt for Gapps.

Ive subducted to both threads so I can go download the newest Gapps whenever I flash a new ROM.

P.S. make sure you download the correct version (4.3/4.4.x) accordingly.

transmitted via skynet
[TouchPad Development] flintman:
Posted a new link to a new test build added in MTP/PTP support.

To change the mode

Settings->Storage-> top right corner click the 3 dots then select USB computer connection and you will have the option for any of the three UMS, MTP, or PTP.

Also a few minor changes. Please read the Bugs/Issue section in the first post as i have updated with some work arounds for a few items.

Anything more then what is on the list let me know.

In regards to the charging issues i can duplicate this with a low end USB cable. Try to replace your USB cable and let me know if it continues and if you can get a dmesg that would be great

Happy New Year i think 2014 will be a great year..
[TouchPad Development] Lister Of Smeg:
Hi [MENTION=3716175]flintman[/MENTION],

Thanks for keeping us Touchpad users alive and upto date with the latest Android release(s). May I ask, and apologies if this has been addressed already, although couldnt see it in the OP... Is your latest build (02-01-2014) using the new Data-Media partitioning structure, or is it still set/used in the same way as it was for say Android 4.2 ???

Also, whats the best way to move upto this KitKat?? I already have an old version of Android 4.2.2 (just noticed my system partition needs increasing as its only 400Mb, but plan to use Tailor to take it to 600Mb). I have a build of CWM already on Tablet, but I think it's something like CWM 6.0.1.9, or something like that... How can I update this to take into account for newer version of Android...

Is this build going to be actively worked on, with the hope as it evolves, that most bugs will be ironed out...

Many thanks, Lister
[TouchPad Development] googlephone:
This is not datamedia.
[TouchPad Development] flintman:
There are a few videos and Tuts out there to help you upgrade to the 600MB http://www.youtube.com/watch?v=UK0RS9aLOxE

I have switched over to mainly work on the 3.4 kernel with 4.4 kitkat in hope to bring the device up to 100% working order.
[TouchPad Development] nevertells2:
Hey Flintman,

Now that Invisiblek has switched to a data/media build, yours is the only one left that is not. Don't know if you have been following either of Milaq's or Invisiblek's threads, but the only answer I can get to the question "why is data/media better or needed?" is, it's the way it's done on phones and other tablets, it's the future, it's flexible, it's moving forward, it puts the SD card in the same partition as the apps so the data partition can be as large as one wants. So what!!! All I see are the headaches and issues that a lot of the folks who try these data/media builds are having. It requires a lot of partition preparation that I think the average user is not prepared for and going back to a non-data/media build is not easy either. Having data/media may work for a device that only has a single operating system on it, but that's not our great TouchPad. If we had been doing data/media from the start, then the installation apps and the folks who use them would be optimized for data/media installs. I'm hoping that you will resist the urge to go the data/media route unless it becomes obvious that is the only way to get CM11 Evervolv working on the TouchPad.

And BTW, I'm sure you know about J.C. Sullins patches to increase /data if one needs more room to download and install more and larger apps. That has been around since CM7 and has worked great on every version of CM I have installed and I have tried them all.

Thanks for doing what you do. How many devices as old as the TouchPad are out there that are dual boot and already have a working version of CM11? None that I know of that are dual boot and not many that have CM11. Keep up the great work.

NT

P.S. If just increasing one's /system partition to 600mb is the goal, ACMEInstaller5 it the best method for ease of use and safety. Using Tailor is not well documented and can be dangerous.
[TouchPad Development] sstar:
Hi Flintman thanks for your updates..

I am trying to install you're latest version of this Rom with CWM6_tenderloin-20121215 and after doing a system wipe , I have this problem.

Formatting system

Installing Evervolv

Setting permissions

Set_metadata_recursive: some changes failed

E: Error in / sdcard / boat_browser_free/downloads/ev_tenderloin-testing_2014.01.02.zip

( Status 7 )

Installation aborted.

Does anybody know what Status 7 means or why I cant install.[COLOR="Silver
[TouchPad Development] Pada:
Error 7

Hi

I got the same Error. I checked the md5 sum was correct on PC . Tried transferring twice to the TP same thing.

I think it's SELINUX related? Or Data Media ?

As a FYI

I tried the 01012014 Ver 3 Kernel from Milaq.

Used the CWM 6.0.4.x .zip first and was able to install the CM 11 rom.

It's considered experimental

I'm going to flash it again with the new Gapps from this thread .
[TouchPad Development] flintman:
Need to use the updated recovery i believe its a few pages back i forgot to update the op with that information and link.
[TouchPad Development] jerryatherton:
I am not able to power off. http://paste.evervolv.com/view/4ac6fd41 is hopefully the kmesg. When i hold the power button, it accepts the turn off, i get the "this will shut down system". After abut 30 seconds it just locks up
[TouchPad Development] flintman:
Working this issue right now. it's related to the reboot when usb is unplugged
[TouchPad Development] jerryatherton:
I have 2 Touchpads, I just got the same thing on Invisibleks ROM.
[TouchPad Development] Lister Of Smeg:
Hi [MENTION=3716175]flintman[/MENTION],

Please can you help/asist me in trying to update my recovery please...?? I've seen you've added the new TWRP recovery in IMG format...

Before I saw this, I tried to update my existing CWM (6.0.1.9) as imagined that was well out of date, as was used to install Android 4.2.x on it. I saw someone had created a flashable CWM (6.0.4.5) which I assumed was the latest, and flashed in CWM and tried to reboot the Recovery, but now my Touchpad cannot boot into CWM..

I still have my MoBoot menu, and can boot into WebOS, Android 4.2, Ubuntu and WebOS Recovery. But not into CWM anymore... :(

Whats the best way to get CWM back on... or install/flash TWRP instead, as currently I have no recovery other than WebOS... and as we all know, there is limited space in the /boot partition. So dont know what to add/remove from there...

Thanks, Lister

---------- Post added at 02:50 AM ---------- Previous post was at 02:16 AM ----------

Hi [MENTION=3716175]flintman[/MENTION],

I've managed to restore access to CWM (6.0.1.9) in my MoBoot menu now, and can access it... So all back to square one... :)

How/whats the best way to update CWM 6.0.1.9 to something more modern that will support KitKat? Thats still MoBoot friendly, and fits inside the /boot partition? Does it replace cwm?

thanks, Lister
[TouchPad Development] O.a.T.:
I've used the attached, without problem. Just flash as a normal zip. Although it will say CWM in moboot, it is the TWRP flintman posted several posts back. Hope that helps.
[TouchPad Development] MerenQue:
I know that there are more important things to do but maybe this is interessting for the devs too:

[4.4/4.4.x][PATCH] Qualcomm-optimized Dalvik & Bionic libraries
[TouchPad Development] _Dorregaray_:
AFAIK this patch applies for APQ8064 (Snapdragon S4 Pro, Krait core) processor while TouchPad uses APQ8060 (Snapdragon S3, Scorpion core) processor so it may be not work if using Krait extensions.
[TouchPad Development] jsgraphicart:
I'm thinking of trying this out this weekend. So TWRP is what we have to use? I dont really like TWRP but I will use it if I have to.
[TouchPad Development] Lister Of Smeg:
Hi [MENTION=1892239]O.a.T.[/MENTION],

Thank you for your post, and for providing the link to required file... I did try to flash it in my current CWM (6.0.1.9) which went fine, however on rebooting the recovery, end up with the same failure as the new CWM... Said it couldnt boot from it??? and so have no Recovery again...

- not a bad thing, as I now know how to get my old recovery back... Just not sure how I can up date to this newer one??

Is my MoBoot causing the issue as I noticed it was only 0.35, and that there is a 0.38 build out there...

Cheers, Lister
[TouchPad Development] flintman:
I have been debating this for a while. In regards to the SELINUX and recovery. The reason i added this back into the install is that i feel since we now have an SELINUX kernel we should use it. Right now it's in passive so to help everyone out the next test build (today sometime) will not require any special recovery. Once we go full SELINUX this will be required. Some GAPPS require the SELINUX supported recoveries so make sure you locate the right gapps. The test build today will repair the shutdown/reboot issues that everyone has experienced and some other minor changes.

Tell me your thoughts on the recovery Update now or update later??
[TouchPad Development] flintman:
Im still running .35
[TouchPad Development] jsgraphicart:
My thoughts right now is that if I (or anyone else) dont want to stay on 4.4 due to stability issues or whatever (if there are any), it would be a lot easier to go back to what we were on before without having to switch the recovery again. I know technically, you could install the new recovery, make a backup and test the 4.4 builds and restore if you want to go back. For me, I would have to install CWM after going back because I am just not a TWRP user. Like you said, eventually, we will have to switch recoveries for good which is fine. I think during the testing phase, if its not required yet, it would be easier on people to keep the recovery they are using.
[TouchPad Development] Lister Of Smeg:
Hi [MENTION=3716175]flintman[/MENTION] / All,

For me personally (and it may just be me doing summit odd with this Touchpad?? I'm normally ok flashing Roms/Kernels, have been fine on my ZTE Blade, Samsung N7000, MK802-II, and other devices... But not sure if there is summit I'm missing due to the LIMITED small /boot partition, and the fact I am triple-booting already with WebOS, Android and Ubuntu) if that has any effect??

However, like the poster above me... Personally, Recovery Wise... I think it's best to go forward with Progress, and where the developer(s) feel the need is greater.... However, I too... would like the ability to be able to switch roms easily, between CM9, CM10 and CM11 without having to keep checking what Recovery I'm on.... If there is a Universal one, like there was for the early Note roms, then that would be dandy...

- Though not being a Dev, or Dev minded, not sure if this is possible...??

Thanks for all your efforts in bringing us KitKat (and not going via the Data Media route too, just to add another headache.. lol)

Cheers, Lister
[TouchPad Development] jerryatherton:
I have the what I think is the SELinux version of the TWRP installed. If we have to switch eventually. I would rather do it now. I am struggling trying to keep up with all the recoveries floating around.. Once they are installed i have not found a way to tell what version it is. It may also be good to put the version ie sel-twrp or non-sel-cwm in the file download name. I think i have made the mistake of trying to load using a Data-media recovery and had to do an uninstall to straighten it out. It was my fault i know but à description would have stopped me from screwing up.