yashsingh1/xdaforums huggingface dataset:
[TouchPad Development] flintman:
I remember somewhere looking at a diagram of the usb plug somewhere and i remember seeing diodes in line with the + and -. If this is true then HP didn't want to use this as a power source for some reason. I need to do some research or even locate a dead TP board to determine if those diodes are present. also without knowing what the traces on the board are rated at i wouldn't feel comfortable adding this in. you can easily make a cable with an external power source small and compact. I would need more information before i would even test this. Great find on it though. If you want you could always download the source and try it out but be warned that know having all the facts could destroy the board.
[TouchPad Development] mpgrimm2:
I'm going to be tied up through next week so can't contribute much to the conversation (not a Dev or EE either), but I do know an EE with a TP that has prototyped a powered USB OTG 2 port sensing hub add in card for the TP (similar to, but more advanced than my mod). I would bet he researched some of the details Mordred mentioned before making his add in card. I will have to see if I can get a hold of him again (been a while).

As Flintman indicated, keep in mind that just because the chip is on the board, it doesn't necessarily mean HP connected all the traces/hardware from the chip for every function. Without seeing a schematic of the circuit from the chip to the port, its hard to know if it is physically possible or not (although all prior information indicates that it is not). Perhaps all that is needed is shorting across/removing a diode. Here's hoping you found the needle in the haystack!

(Mind if I quote these posts in my Powered OTG mod thread?)

Sent from my "Up All Night Sleep All Day" Nexus 5!
[TouchPad Development] k4ever:
I don't know if I should ask this here given the nature of the app, so I apologize in advance: has anyone got popcorn time to work on this ROM?
[TouchPad Development] rickpub:
I got their first android version to work though it is a bit flakey, the new 1.1 version will not work for me though
[TouchPad Development] k4ever:
Thanks! It's not working for me either. Works on my phone though.
[TouchPad Development] len207:
Not sure why this thread is so dead lately? Maybe it is working so good for most they have nothing to gripe about so say they say nothing... I'm not an expert so can't really comment much. The nightly updates continue and seem to work fine. The one real obvious known exception is Netflix. Keep up the good work flintman and improve KitKat for our TPs! I don't really want to go to a DM ROM if it can be helped on this tablet!
[TouchPad Development] flintman:
Nightlies are setup for DM rom's only. The only update on the non data media comes from the download link in the OP it has an extension of -nondatamedia.
[TouchPad Development] len207:
Thanks for the response but I am still getting updates more or less every couple days through the ROM itself. My last one was dated about 3 or 4 days ago. As far as I know these should be the same as the initial install which was a non-data media flavor.
[TouchPad Development] flintman:
You will still receive update but they are for data/media only.
[TouchPad Development] len207:
Thanks for the clarification flintman. So without formating and still using one of jc's old CWM Recoveries I am now using a data/media ROM... interesting. I am using ev_tenderloin-nightly- 2014.05.21and this would be a d/m ROM?
[TouchPad Development] flintman:
Correct. If you do a factory reset you will wipe the internal SD card with that recovery. It will install no problem with any recovery as data media gets setup on start up
[TouchPad Development] flintman:
All. With the addition of the 4g im thinking of ending the non data media ROM. With apps keep growing and ROMs size continuing to grow it makes sense to move to data/media. These kitkat ROMs require increasing system partition size so why not just increase the data also. With the new toolbox that jcsullins has released makes it even easy to swap including removing webos all together which is nice BTW. Im willing to help you upgrade and there are a lot of great videos out there. Like i said I'm thinking about it and looking for feedback from all of the non data/media users out there.
[TouchPad Development] MerenQue:
Let me answer this with the famous lines from the St. Crispin's Day Speech of Shakespeare's Henry V:
[TouchPad Development] garux:
I would like to say 'Thanks' for all your efforts keeping the non-data-media ROM going as long as it has. It was wonderful for me to take my time to migrate to the data-media ROM.

Thanks again and keep up the GREAT work.
[TouchPad Development] gaww:
I converted to data media a few months ago, and am looking at doing a friends - is the "new toolbox that jcsullins has released" newly released, or are you referring to one that has been been out for awhile?
[TouchPad Development] k4ever:
[MENTION=3716175]flintman[/MENTION], I used the toolkit and converted to your data/media ROM last night. Everything was smooth. The system is running well, so far. One thing I did notice was that the toolkit will only recognize and install your nightly ROMs.

Edit: Forgot to thank you for making a non-data/media 4.4.x ROM for us to play around with. I would have never took the plunge to 4.4.x if I had to go the nuclear route and wipe/resize my partitions. Having a non-data/media ROM allowed me to first see if 4.4.x was even worth the trouble to install. I had the option of going back to 4.2.x without losing data if 4.4.x wasn't worth it. Your 4.4.x ROM is very stable and everything works well enoug, plus the toolkit is a godsend; it made switching to data/media easy.

I just want to let all of the guys who were pushing data/media from the beginning know that some of us rely on our TouchPad heavily. Switching to a new ROM with all of its quirks and bugs is hard enough without added all of the extra mess that data/media brings. You can't expect us to want to dive in head first.
[TouchPad Development] flintman:
The new released toolbox
[TouchPad Development] gaww:
Got it - thanks. Going to use nondata media ROM on it to see if she is comfortable with it. Then jump to data media.

Looks like the new toolbof will be an easier route (did mine in pieces).
[TouchPad Development] flintman:
Well that toolbox is setup for data/media only. Also you can resize the partitions from this tool.
[TouchPad Development] gaww:
That is what i would use the tool for - it already has CM on it. I will use taylor first to make room for your non-data/media ROM.
[TouchPad Development] nevertells2:
Check the OP. It does provide some limited support for legacy Android Roms. Imagine the next version will provide additional support. Sullins said he would have a new version out the weekend of May 31st, but nothing yet. Suspect he is in the process of continued improvements and tweaks. He plans a permanent installation that shows in the Moboot menu. Remove WebOS, never have to connect a PC again to remove or install a CM Rom or modify partitions, awesome! :good:

---------- Post added at 08:01 PM ---------- Previous post was at 07:55 PM ----------

This taken from the toolbox OP:

"Assuming those tests pass, it will create a set of volume resizing criteria based on the type of Android being installed (i.e. DataMedia vs Non-DataMedia) and confirm that you have available space on the device."

So if you use the toolbox to install Flintman's non-data/media Rom, the toolbox will set the appropriate partition sizes. Pretty cool! :)

P.S. And you have the ability to use the toolbox to tweak the partitions if you wish. One other thing to keep in mind, if you decide to keep WebOS, it is advisable to remove the old version of Andorid with ACMEUninstaller2 and boot WebOS and go to device/setting/reset/erase USB Drive to free up the memory the toolbox will move to the data partition. Otherwise, I have seen the toolbox bog down if you don't do that.
[TouchPad Development] gaww:
Well, this nondata ROM installed and ran pretty good on friends TP, which was on CM9.

Going to make a backup, and then setup data media. Want to be able to update it, and have to move on to new setup to do so.

Already resized system to 600 with Tailor (surprised it wiped android sd when it ran, but all backed up). Did not mess up mine when I resized system.

Both nice ROMs OP, and will be using modded TWRP from the OP this time.
[TouchPad Development] theonlyrealperson:
I agree. Tailor worked really well for me. The automatic zips didn't work at all (and in fact messed things up a little I think).

Tailor was nice because I could resize to a point webos still had a decent amount of space.

Loving the data/media Evervolv.
[TouchPad Development] gaww:
Another reason I am moving over is battery drain on TP if turned off while in Android. On HP or in recovery when shut down, no problem (so don't think A6 had anything to do with it).

I am on data/media version, and no longer have that issue, but on the one on nondata/media ROM - still an issue.
[TouchPad Development] Lister Of Smeg:
Hi All,

Has development on this (the last, and only non-DM) rom finished now...??

Would be great if it could be updated, like the other one is...

Would also love to try the PAC rom, but wary of converting over...

Thanks, Lister
[TouchPad Development] johnsmith33584:
Just curious, with the release of Mr. Sullin's TPtoolbox, why would you be messing around with the antiquated methods of installing Roms?
[TouchPad Development] Moody66:
Probably because it will not work with the rom he installed.
[TouchPad Development] 2WhiteWolves:
I didn't mind the few corks in the non dm, not really looking forward going to data media.
[TouchPad Development] gaww:
All I wanted to do was set up the data partition, and could do so this way without hooking up to PC (was on the road). I don't know if the tool would install Evervol ROM - not an issue, as I always use recovery for installs.
[TouchPad Development] endofwed:
hello. I downloaded a nightly build from the Evevolv updater.

However, when i reboot into cmw, I cant find the nightly build.

I think it might be due to the partition? How do i find the tenderloin build because I can only seem to find the files under the wrong hard drive partition.
[TouchPad Development] nevertells2:
Mr Sullins says he supports all the current CM11 roms.

**********Quote**************

It will recognize as a compatible KitKat/DataMedia ROM files that look like:

cm-11-*-tenderloin.zip or

ev_tenderloin-nightly-2014.??.??.zip or

aokp_tenderloin_kitkat_*.zip

---------- Post added at 09:00 PM ---------- Previous post was at 08:55 PM ----------

Which data/media version of clockworkmod are you using? If you are not using JcSullin's Philz cwm6.0.4.7 DM touch 20140317, give that a try.
[TouchPad Development] johnsmith33584:
Hey Flintman,

From the lack of builds and chatter in this thread, would it be safe to say you have called it a day on this Rom?

John
[TouchPad Development] flintman:
No just very busy at work. Been pulling 16 hour days. And my family is up north so i head out on Friday. Usually not busy at work and have time to build while the FAM is away.
[TouchPad Development] gt5oh:
Which is the most stable Evervolv Rom to be using on the HP Touchpad?
[TouchPad Development] MIKEYSAKZ:
All builds evervolve tend to be the most

Stable
[TouchPad Development] jerryatherton:
I don't use the non-data media ROM but the 4.4.4 data media ROM is very stable.
[TouchPad Development] Lister Of Smeg:
Hi [MENTION=3716175]flintman[/MENTION],

I think from when we last heard from you, that you did still intend to do both builds (DM and non-DM builds) of your rom. Is this still the case, or have you given up on the non-DM releases?

This is not a chase up, or a request for an ETA... Just curious to see if you're still supporting the non-DM builds.

I'm sure everyone will say, just move over to a DM build, but I have my Tablet setup just fine with WebOS, Android and Ubuntu at the moment... So don't really wonna lose that, or start again as such... :(

Cheers, Lister
[TouchPad Development] flintman:
In sorry but i dumped non data a little while ago it was getting to much supporting all the different devices. If i ever get lollipop running (it's been a challenge) i may toss out a non data but it wont be supported and it wouldn't be until i get lollipop solid.
[TouchPad Development] willias:
My data is noton
[TouchPad Development] Pada:
Kit Kat

Hi

I did the WebOS partition size update for 4.3 about two weeks ago.

So I just went ahead and flashed this after wiping of course.

Get the Black Screen in Stock Browser Not sure if it's any quicker than CM 4.3 rom yet.

Just a note I flashed my ASUS TF101 to Kat Kiss's 4.3 rom and it was the fastest , smoothest one I'd seen yet

So there's still hope that this Touchpad might get a bit more responsive.

Thanks for all the hard work.

I'll test Netflix next .
[TouchPad Development] daedric:
[MENTION=3716175]flintman[/MENTION]: isn't sdcard failing to mount ?
[TouchPad Development] flintman:
No can you send a logcat if you are having issues
[TouchPad Development] daedric:
Ok. For the sake of clearness, /system, /data, /cache were wiped. ev_tenderloin-4.0.0p1-queo was flashed and nothing else.

mount:

root@tenderloin:/ # mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p13 /boot ext3 ro,noatime,errors=continue,barrier=1,data=writeback 0 0
/dev/store/cm-system /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/store/cm-data /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/store/cm-cache /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0

Logcat:

--------- beginning of /dev/log/system

I/Vold ( 163): Vold 2.1 (the revenge) firing up

D/Vold ( 163): Volume sdcard0 state changing -1 (Initializing) -> 0 (No-Media)

D/Vold ( 163): Volume sdcard0 state changing 0 (No-Media) -> 1 (Idle-Unmounted)
...

dev:

ls -la /dev/store
ls -la /dev/store
lrwxrwxrwx root root 2013-11-17 14:20 cm-cache -> /dev/mapper/store-cm--cache
lrwxrwxrwx root root 2013-11-17 14:20 cm-data -> /dev/mapper/store-cm--data
lrwxrwxrwx root root 2013-11-17 14:20 cm-system -> /dev/mapper/store-cm--system
lrwxrwxrwx root root 2013-11-17 14:20 filecache -> /dev/mapper/store-filecache
lrwxrwxrwx root root 2013-11-17 14:20 log -> /dev/mapper/store-log
lrwxrwxrwx root root 2013-11-17 14:20 media -> /dev/mapper/store-media
lrwxrwxrwx root root 2013-11-17 14:20 mojodb -> /dev/mapper/store-mojodb
lrwxrwxrwx root root 2013-11-17 14:20 root -> /dev/mapper/store-root
lrwxrwxrwx root root 2013-11-17 14:20 swap -> /dev/mapper/store-swap
lrwxrwxrwx root root 2013-11-17 14:20 update -> /dev/mapper/store-update
lrwxrwxrwx root root 2013-11-17 14:20 var -> /dev/mapper/store-var

Full Logcat:
[TouchPad Development] flintman:
Did you have issues with the previous build? Also is this a 16 or 30gb.

Anyone else having issues??
[TouchPad Development] jerryatherton:
TiBu sees my SD card and it shows in settings/ storage. I am running great. I am Full PA Gapps w/out Photosphere. Running KK launcher. Set system partition to 600. TiBu says 660 with 79.9 free. I said it earlier that for some reason when i flashed the script for changing the partition, it didn't stick. I had to run Tailor. I don't know if that has anything to do with the SD card not mounting.
[TouchPad Development] long2know:
Previously, I increased my data partition to about 8.5 GB. Is it recommended to continue to allocate a large portion of space to /data?
[TouchPad Development] daedric:
32GB version. Had issues with the previous version.

My advise is to NOT take me into consideration. I screwed my TP so bad that i had to use novaterm and recreate the lvm, webosdoctor 3.0, then 3.0.5, then ACMinstall4 (a new version on rootzwiki, can't remember which particular one i used).

If this problem is not reported by anyone else, please let's call this MY problem and not Evervol problem.

I didn't use recovery scripts to alter partitions, always tailor.

It depends, i have 3 users on my tablet and because theres the app on SD problem, i rather have a large /data to accomodate it all.
[TouchPad Development] spica123:
Smoothest ROM ever tried on HP touchpad! Thank you so much!

Only drawback for me is that most emails displayed in k9 are blacked out. So back to 4.3 till there is a workaround.
[TouchPad Development] Y314K:
Anybody tried to Skype on Test 2 ???
[TouchPad Development] cqloveqc:
great work, love it very much

Only one problem for me, i can't use feedme app, it's a app need to sign in with google account by feedly, but after click login, it come out a black screen without any place to signin

thanks

---------- Post added at 09:36 PM ---------- Previous post was at 09:34 PM ----------

great work, love it very much

Only one problem for me, i can't use feedme app, it's a app need to sign in with google account by feedly, but after click login, it come out a black screen without any place to signin

thanks
[TouchPad Development] fattyjian:
No Idea What Happen, after flashing now my computer cant detect the touchpad. ><
[TouchPad Development] flintman:
What are you running for an OS on your computer??
[TouchPad Development] jerryatherton:
Win7 doesn't see it either. Same thing happened on my phone when I loaded 4.4.
[TouchPad Development] RolandDeschain79:
You need to enable it from the device

Note: Windows users may need to do the following in order to attach the Touchpad with the USB cable.

1. Go into the Device manager. You will see "MTP USB Device" under portable devices.

2. Right Click it and select update driver software

3. Select Browse my computer for driver software.

4. Select Let me pick from a list of device drivers on my computer

5. Select USB Mass Storage Device then click next.

and/or

6.To transfer files to PC, turn on USB mass Storage from the USB connection notification on the Android device.
[TouchPad Development] cqloveqc:
drivers problem

I have the same problem

I think it`s the problem of drivers
[TouchPad Development] garux:
Here's what I did in previous version of Evervolv:

How to Fix MTP USB DRIVER problem in Windows 7 64-bit

Since upgrading to Evervolv 3.3.0p1, I’ve been trying to use the MTP USB Driver and every time it would fail.

Though I was unsuccessful in my Google searches, I never found a solution to make it work for me.

What I did was search for files on my Windows 7 64-bit PC for any combination of mtp and I found 2 files in the C:\Windows\Inf with mtp, they were wpdmtp.inf and wpdmtp.PNF. I tried to install the .inf file but I was unsuccessful. Then I rename the wpdmtp.inf file so I would still have it in case something happened.

I plug the USB cable from my Windows 7 64-bit PC to my HP TouchPad and would you believe it actually worked. I even rebooted my PC and just plugging the PC and the TouchPad worked. Once done, be sure to EJECT the HP TouchPad as you would when you used WebOS.

I can’t speak for other Windows Operating System, but all I can say is, this worked for me.
[TouchPad Development] fattyjian:
Window 7 32Bits.
[TouchPad Development] flintman:
Have you tried everything that everyone has posted and still doesn't work ?
[TouchPad Development] fattyjian:
Nope, but i tried booted back to webOS and then move the files. will try those solution later ><

---------- Post added at 03:11 AM ---------- Previous post was at 02:54 AM ----------

This solution works! thanks ! xD
[TouchPad Development] nevertells2:
So you have found the alternative solution to moving files via USB cable until the developers can figure out the issue with these latest versions of Android. One can also boot to recovery and use the USB file transfer option there. It's not really that big of a deal if MTP does not work. How often does one move files that it is that big a deal to boot recovery or WebOS to take care of it. There are also wireless apps too. Let's not forget this build has only been around for about a week.
[TouchPad Development] ANDR01DN00B:
Hello all! I'm new to this, so please bear with me, so I downloaded all the files, the ROM, kitkat gapps, and the partion resizer zip, flashed all of them, wiped data (i do have a nan ready) then rebooted into Evervolv, but it gives me this error...

Checking uImage... Invalid size

BOOT FAILED!

Press SELECT to coninue

What should I do in order for the boot to work? Thanks in advance. :good:
[TouchPad Development] nevertells2:
Do you know for a fact that the /system partition size was increased. Did you flash that first before trying to install the Rom and Gapps? You really need to verify the /system is large enough. Restore your backup and install Quick System Info Pro and have a look at the /system size.
[TouchPad Development] ANDR01DN00B:
Haha never mind I got it. I flashed the partition updater AFTER the ROM, being the idiot I am. :silly: Thanks for the reply, though.
[TouchPad Development] chris5s:
Installed and running nice and smoothly.

No real issues apart from those already documented - black screen on stock browser/email apps, random disappearing apps - but all pretty good so far.

Thanks flintman for continued efforts and rom development!
[TouchPad Development] SteveoSupremo:
Yes I have the same issue. I can't do the 2step verification because it uses the browser.....

I used ACMEInstall5E with Evervolve 4.3 Hung at startup animation so I used CWM and flashed Evervolv 4.4 and then the PA Gaps (200+ meg version, i didn't know there were other versions available.)

Everything seems to be working well (or as expected) just need to find a way to get my account signed in.

Thanks Flintman!
[TouchPad Development] SteveoSupremo:
I've been reading on some other forums that some have disabled OpenGL in the browser and that has taken care of the issue. I don't know if that helps or not but I'm willing to help however I can.

/************ Edit *****************/

Found on the KitKat version info page here http://developer.android.com/about/versions/kitkat.html

Graphics

GLES2.0 SurfaceFlinger

Android 4.4 upgrades its SurfaceFlinger from OpenGL ES 1.0 to OpenGL ES 2.0.

and I found this tidbit in another un-related 4.4 AOSP Rom

http://rootzwiki.com/topic/36706-ro...like-stock-android-44-krt16m-no-bugs/page-841

The only major bug right now involves an interaction between the new webviews and OpenGL. In some apps (e.g. the AOSP browser, Google Search) there are black boxes rendered randomly throughout the content. This is a consequence of incompatibility between our outdated GPU drivers and new surfaceflinger code. It is being actively worked on.
[TouchPad Development] cqloveqc:
I have the same problem, and can't sign in with feedly
[TouchPad Development] SteveoSupremo:
Ahhhhh Dang..... Tried to edit build.prop to get AutoAwsome videos and now I'm boot looping...... Time to re-flash.
[TouchPad Development] GizModio:
Wow!

Evervolv! You've done it again!

Brought the Touchpad Back to life. Again.

I'm very impressed with your work.

The current build still needs work. My analysis shows the WiFi is very slow (Well downloads anyway) very responsive and haven't experienced bugs as of yet. Obviously Bluetooth doesnt work and other things. But its damn impressive!

I must add that web browsing experience with the AOSP browser as well as Google search is quite poor. Could do with some work but thats due to the dated hardware. Maybe a Driver update is in need!

I recommend giving this a try:good:
[TouchPad Development] jsgraphicart:
I have seen in the Galaxy Nexus forum that Cyanogenmod has added something into their last nightly that aparently gets rid of the black box issue. People are already confirming that they are gone. Maybe it will help with the TouchPad.

http://review.cyanogenmod.org/#/c/54291/