yashsingh1/xdaforums huggingface dataset:
[TouchPad Development] agent00f:
Question for the experts: I accidentally flashed the datamedia zip over an old CM ROM when I meant to do the non-datamedia, and apparently I now have a 1.5 gig user storage space and 10gig SD space not readily available from inside the device. Is the best course of action to redo with the non-datamedia build, or somehow fix this problem?

Thanks.
[TouchPad Development] Moody66:
Assuming you are still using a non data media recovery just reflash previous ROM.
[TouchPad Development] agent00f:
Well, there's no backup of the previous ROM (since it was just an evervolv 3 tester) so I just straight up flashed the non-datamedia with no wipe. Seems to work and storage is back. 3/24 build produces ~30-40ma draw which is good for now.

Also just btw, when I first stupidly flashed the datamedia 4.0 over evervolv 3 it kinda almost worked, but activate ART and it's crash-city. So I obliviously flashed datamedia again w/ wipe which worked pretty well other than the storage issue. These ROMs are impressively hardy.
[TouchPad Development] Moody66:
Most avoid Art. It generally causes issues. Especially depending on which gapps you use. Even new Google devices aren't really implementing It Yet.
[TouchPad Development] graffix31:
I've been running art on my nexus 5 since I got it and it had been super stable, fast and smooth.
[TouchPad Development] nevertells2:
More KitKat coming!!!!

http://bgr.com/2014/03/24/android-4-4-3-kitkat-update-release-date/
[TouchPad Development] Moody66:
You turned It On though correct?
[TouchPad Development] graffix31:
Um yeah...lol. Wouldn't be running it if I didn't. Works great with slimkat.
[TouchPad Development] chris5s:
I've been running ART for a while now, no problems at all. Using PA gapps, modular mini.

Cheers
[TouchPad Development] graffix31:
Same gapps I use [emoji106]
[TouchPad Development] Moody66:
Pagapps And banks gapps shot work fine with art. If The rom supports it. Lots of people report lagging with it. And FCs SoDs etc. Randomness Sucks. Seems ART makes The U I more responsive but lagging in app use. This will of course likely be lessened by a higher end device.
[TouchPad Development] chris5s:
No lagging noticed here. Nor FC's or SOD's.

Running latest build at 1.5GHz, can play, for example, Dead Trigger2 at high performance no problems. Runs pretty much like that stuff I put on my toast...buttah! Ha ha.

Cheers
[TouchPad Development] woodytrain:
Roland's page has a link to KK gapps:

http://d-h.st/EIM

Is that a safe download? What is the best ay to check, without a PC? TWRP failed at checking MD5 for both the 1-10-15 ROM and gapps.

And on a clean install (that is after a factory reset/full wipe), TWRP threw up an error installing the 1-10-15 Evolv ROM a couple times. Rebooted TWRP one more time, and the ROM sucessfully installed. Now I see an updated build is available. Will test soon.

Question: I have both two backups of my CM11 install, one done in cmw and the other in TWRP, just before flashing the 1-10-14 Evolv ROM. Can I use advanced restore to re-install the apps and some data I had set-up on CM11, into the Evolv install. Or do I have to start fresh, e.g. and re-enter my router wifi pwd, Google pwd, re-configure my launcher layout, and re-set various Settings. etc?

Thanks for the ROM and being able to test the 3.4 kernel!
[TouchPad Development] flintman:
I use the 12-08-2013 gapps http://www.androidfilehost.com/?fid=23269279319202484. Inregards to the advanced restore it will not work as CM and Evervolv are different. Best bet is to backup via titanium backup and restore that way.
[TouchPad Development] nevertells2:
I'm surprised that no one has ever figured out a script to add a few mb to the /boot folder. Just because HP had no foresight in this doesn't mean we have to behave the same way. ;)

Having both recoveries could have it's advantages.
[TouchPad Development] Colchiro:
I think the problem is a screwed up "boot" = BRICK.
[TouchPad Development] flintman:
I keep all my recoveries on my SDCARD (data/media version) use external sdcard of course. And just move them in and out of /boot. Remember deleting the wrong file in /boot can be bad VERY VERY VERY BAD. but that is how i get around the small boot partition.
[TouchPad Development] nevertells2:
I'm not saying delete any files. If JC Sullins can add memory to the /data partition using a zip file and not harm any of the files in the data partition, why can't we do the same thing in the boot partition? Older versions of clockworkmod and TWRP are small enough that I am able to keep both programs in the /boot partition and still have about 750 kilobytes of memory left. I suspect you have learned how easy it is to move recovery programs in an out of the /boot partition just using a file browser with root permissions. I've never looked into this, but do you know if Tailor has the ability to change the size of the /boot partition?
[TouchPad Development] siralsmooth:
[MENTION=4396896]nevertells2[/MENTION] William Castro could probably be of help with resizing the boot partition as well. His works in the other development forums for linux/ubuntu/multiboot is nothing shy of amazing. He knows the memory block /partition layout very well.
[TouchPad Development] jerryatherton:
I generally always used CWM but have tried Flintman's TWRP. I now have it on both my Evervolv and CM 11 machines. It has on occasion just locked up when it is done installing the zip. On the high note on the CM 11 machines i can dirty flash the two available CM11 ROM's over each other.

Great job, thanks for your work.
[TouchPad Development] nevertells2:
Thanks. I would suspect that J.C. Sullins knows how do it too. It's just getting him interested that is the issue.
[TouchPad Development] jsgraphicart:
So I'm going to finally update from the non data/media build and install the latest. Just so I have this right, I flash the latest recovery from the op, then the flash the ROM and gapps?

Do I also need to put the files in a certain location before flashing the recovery or will they be seen in the normal sdcard location?
[TouchPad Development] jsgraphicart:
Went ahead and updated. All is good so far
[TouchPad Development] emph4tic:
Clean install of the latest build and your alpha TWRP recovery:

dmesg -

http://pastebin.com/d1syqYsx

logcat -

http://pastebin.com/RM0JT2XJ

logcat radio -

http://pastebin.com/CDZGhhM4

Same issues on TP4G: WiFi won't toggle and flipped landscape orientation. Also, I'm not sure if I may have messed something up, but I can't seem to transfer files from /data/media directory to Windows, but the reverse operation and adb works fine.

Yep, I've tried that out to no luck. I'm assuming that unique HW in the 4G model like the USB host and sensor mapping is probably the culprit.
[TouchPad Development] woodytrain:
All above same here.

Would be cool if we could enlarge /boot and allow TWRP and CWM to co-exist.
[TouchPad Development] jsgraphicart:
So all is good with the latest build. But the WiFi likes to disconnect a lot when the device goes to sleep. This isn't good for when I have music playing on my chromecast and it loses connection and stops playback. I have to keep the screen on. I have tried with Wi-Fi optimization on and off. Same results with both
[TouchPad Development] aHecticLife:
Is it safe to update to this rom? I use the HP Touch for daily usage. I don't need the camera and all that, I just want to know if it's almost stable and it won't give me random reboots :)
[TouchPad Development] jerryatherton:
I use it daily. I use it alongside my PC at work for listening to Sirius, a calculator, web browser, XDA, and Facebook. Nothing real taxing but very handy.
[TouchPad Development] Kodes:
sleep of death

Anyone else getting a sleep of death issue with this ROM?
[TouchPad Development] jsgraphicart:
As in the device wont turn on? No. The worst I get is the WiFi disconnects
[TouchPad Development] aHecticLife:
Thanks bro, thats the answer I wanted :) :good: :highfive:
[TouchPad Development] groo_pcd:
yes, it's a known bug, don't change the governor to anything besides performance or the touchpad won't come back from sleep.
[TouchPad Development] Moody66:
On lower end devices that isn't the case. Also Some kernels do Not play nice with ART. Swapping kernels may end your luck. Even The Google gnex had issues until kernels were further developed.
[TouchPad Development] nevertells2:
FYI, Link to Gapp in post #2 is not working.
[TouchPad Development] mpgrimm2:
Is everyone on Evervolv using PA Gapps?

Yep. Link has been dead for a bit...

Sent from my "Up All Night Sleep All Day" Nexus 5!
[TouchPad Development] agent00f:
The device can lag as it does the Ahead Of Time optimization (esp first boot) or whatever other related activity. Otherwise much more deterministic performance compared to runtime optimizations.
[TouchPad Development] Moody66:
Run antutu or something similar with both running. Might surprise ya. My nexus and optimus g both run apps faster with dalvik instead of art. Both however do run better flipping thru apps and starting the apps.
[TouchPad Development] nevertells2:
Actually, I'm using gapps-kk-20140105.zip. No issues with it at all. What's special about PA Gapps?
[TouchPad Development] flintman:
Ill update when i get to my PC
[TouchPad Development] jerryatherton:
PA Gapps keeps their apps current. They also give you a selection for smaller or larger packages.
[TouchPad Development] agent00f:
Antutu or similar benchmarks run native machine code, not interpreted java bits, so you've been testing for nothing.
[TouchPad Development] mpgrimm2:
Aside from what jerryA said, I found that the app names on the home screens are cut off with the gapps from goo.im, Milaq, and Invisiblek's sites (all the same md5). Pa Gapps dont have the issue. Not sure why; DPI issue? Launcher issue? Idk. Just an observation.

Sent from my "Up All Night Sleep All Day" Nexus 5!
[TouchPad Development] Moody66:
Still affects them. http://www.androidpolice.com/2013/1...ormance-wont-blow-away-today-will-get-better/ My nexus launches faster but half the stuff I run doesn't agree with art. Some apps like tibu hated art . I think latest version has fixed that issue with tibu. So many apps out there I'm not about to test them all.lol I also experienced a warmer phone running art. Of course Google didn't release kit Kat for the nexus. So the work arounds may be adding to that as well.
[TouchPad Development] agent00f:
Again, the runtime has zero effect on the actual benchmark given it's not used, so differences are likely some kind of artifact of setup or teardown or timing issue.

If half your apps don't work with ART, perhaps you should use more apps.
[TouchPad Development] Moody66:
They work. They just run laggier. I run what I use. The pobnlem lies in resource management more likely. Since what would show up more with benchmarks etc. Web is full of posts that tell same story. Faster in some ways slower in others. If a car is hard on gas driving on different roads isn't going to change the mileage.

---------- Post added at 08:54 AM ---------- Previous post was at 08:31 AM ----------

New version of PAGapps out yesterday. 3/29/2014.
[TouchPad Development] kspanks04:
Hey guys I'm on the latest nightly w/ regular gapps. I'm getting a lot of lag especially while multitasking... I also can't play YouTube videos with the app or in browser.

I flashed using CWM, could that be causing me issues?
[TouchPad Development] endofwed:
from what i've read, try using the pa gapps?

on to my own problem now...

I can't seem to find tailor in preware. I think it might have something to do with this error I get everytime i open preware as its downloading feed information

"unable to run command:/usr/bin/curl -s-1 --user-agent Preware --location --fail --show-error http://ipkg.preware.org/feeds/webos-curl: (22) The requested Url returned error:404 "

any help? I've installed/reinstalled/ rebooted, but nothing works.

update: solved, you need to enable beta/alpha feeds.

steps here:

http://www.webos-internals.org/wiki/Testing_Feeds

The website made it a little confusing so here are the steps i took.

1. uninstall preware

2. open up webos quick install (dont click on globe yet). go to tools and go into linux command line

3. enter the following commands, i enabled copy/paste in the command line to make it easier on me. I entered the first line then pressed enter, then the 2nd line and then enter. not sure if it makes any difference.

type mkdir -p /var/preferences/org.webosinternals.preware

touch /var/preferences/org.webosinternals.preware/enable-beta-feeds

4. install preware as you normally would.

5. my tailor came up blank with a white screen, if this happens, do a reboot.

done
[TouchPad Development] jerryatherton:
I had the same issues. I did a full wipe and clean install. I used the beta Twrp. Even after I did that it seemed slow at first but it actually got faster. I usually run a quadrant score a few day after a new release and this rom is usually slightly lower scoring than the CM 11 ROMS. Now that it offers OC it can probably be better. I never OC devices myself. I am more interested in stability. These ancient tablets are running KK and it is almost 50% faster than what ICS was running when I first put android on a HPTP. I am amazed with what these developers and the general HPTP community have accomplished.

I would suggest trying a clean wipe and fresh install. I find the Evervolv slightly more stable than the CM11 ROMS. I have 3 machines and I have each one dedicated to a different ROM. I use them daily but each one has a specific purpose.
[TouchPad Development] garux:
When testing out different gapps, can I wipe cache and dalvik partitions, then flash new gapps with CWM? Or, is it recommended to do a clean install?
[TouchPad Development] graffix31:
just a heads up 1.5ghz is actually stock for the touchpads processor. if i recall correctly they underclocked the 16g to 1.2 and left the 32gb at 1.5. just for a stat bump i believe. when i had webos running and a custom kernel was always at 1.5 -1.7 with no issues. so i def recommend leaving it at 1.5
[TouchPad Development] jerryatherton:
I would try it by just wiping cache.
[TouchPad Development] garux:
Thanks, That worked.
[TouchPad Development] blmvxer:
On the latest nightly. Straight from stock webOS and I'm still getting SoD when leaving the tablet unattended for awhile.
[TouchPad Development] Moody66:
Try setting governor to performance?
[TouchPad Development] blmvxer:
I didn't want to suffer extreme battery drain, but if that's the only stable solution then I'll take my charger to work. :p
[TouchPad Development] Moody66:
Just to see if that's the cause. If so maybe flintman can resolve it.?
[TouchPad Development] martroy73:
Same problem here and changing the governor to performance doesn't seem to fix it. Coming from a CM11 dm build, I've re-installed everything from scratch :

- ACMEUninstaller2

- ACMEInstaller5E to install Moboot 0.3.8, PhilZ_CWM-jcs-dm-tenderloin-20140317.zip

- Tailor to resize the system partition to 700mb since the GAPPS would not install and 25gb allocation for data (32gb TP)

- CWM installation of ev_tenderloin-nightly-2014.03.24.zip and pa_gapps-stock-4.4.2-20140329-signed.zip

The system feels really responsive compared with what I've experienced with CM11 but the SOD is really killing it... Let me know if you need logs or more information...

Martin
[TouchPad Development] blmvxer:
I switched my screen time out to 30-min and have it plugged in. OC'd at 1.5Ghz and using interactive.

I have unplugged and turned the screen off for up to five minutes with no issues. Still any longer seems to cause the SoD. May try hooking it up to ADB and pulling a dmesg and logcat when I get off work.
[TouchPad Development] flintman:
If you can get logs that would be great. I took the weekend off from developing and enjoyed some playtime on my touchpad i didn't experience one reboot and I'm set at 1.5 or in very curious to see the logs.

Thanks
[TouchPad Development] graffix31:
do you have hot word detection still on? i still need to turn mine off in order to not have sod. other than that everything running great. i still get the occasional wifi disconnect but it is few and far between so i dont mind at all. thanks so much flintman.
[TouchPad Development] blmvxer:
I guess I won't need a log. I kept my tablets screen on all day plugged in. And ever since I got off work 3hrs ago no SoD's. :D
[TouchPad Development] blmvxer:
I guess I'll post a log if I do have an SoD. Still haven't had one. Battery life has been not too great but the battery is about two-three years old. But so far it's been great!
[TouchPad Development] deyanimay:
Where in the settings is this option I couldn't find it.
[TouchPad Development] graffix31:
What launcher are you using?
[TouchPad Development] garux:
With no problems, I've been using Nova Launcher since CM9.
[TouchPad Development] nevertells2:
Instead of setting to performance, use an app like Antutu CPU Master Free or similar app to set the minimum cpu speed to around 384 or slightly higher. Make sure you check "apply on reboot". You won't take a big battery hit and it usually resolves these kinds of issues.

---------- Post added at 05:35 PM ---------- Previous post was at 05:26 PM ----------

I am running the latest version of this Rom and not having any of the issues you are. You might want to have a read at the link below to see if any of the information there helps. Mpgrimm2 and I have done extensive testing and Grimm has complied and posted the results. It's come down to a specific method of using ACME5 to install JcSullin's Philz cwm6.0.4.7 DM touch 20140317 and Moboot 0.3.8. Then use CWM to resize /data to the size you want, reboot and install the Rom and Gapps of your choice. He has a ton of other information there, so it's up to you to decide if you want to read through it all or not. Here is the link:

http://rootzwiki.com/topic/116097-in...guide-3-31-14/

One tip, leave yourself around 2gb of ram for the old SD card. You need that for WebOS and the cminstall folder since that is where ACME looks for the files. I also put the Rom, Gapps and the resize zip on the old SD card root to install after Moboot and CWM are successfully installed.

NT

---------- Post added at 05:39 PM ---------- Previous post was at 05:35 PM ----------

If you are getting between -30 to -40mA, that is what this Rom gets. We may never see the -5mA that the non-data/media Roms were getting. Pretty sure that moving to a 3.4 based kernel has something to do with it too. Flintman?

---------- Post added at 05:48 PM ---------- Previous post was at 05:39 PM ----------

Tap and hold on any launcher home screen, and then navigate to Settings. Next, hit Voice, and uncheck “Hotword detection”. Or, you try this. Within Google Now, tap the microphone icon from the search bar, and from options, uncheck Hotword Detection.
[TouchPad Development] flintman:
You are correct the kernel needs work on the battery life this will come as small issues get fixed up. As some of you remember the 200+ ma in sleep. My goal will be to get down to 5ma in sleep.
[TouchPad Development] garux:
I myself am also using Antutu CPU Master, I have minimum set to 384 and maximum set to 1512. Without using Antutu CPU Master, you can also go into settings/toolbox/performance you can set minimum & maxiumum CPU frequency.

I’m also running the latest Evervolv 4.4 Data/Media Rom, using JCS CWM 6.0.4.7 along with Moboot 3.8. I’ve had no SOD’s or FC’s at all. I’m able to using 4 Bluetooth devices with no problems. I have Hotword Detection unchecked.

Just my 2 cents.

---------- Post added at 07:58 PM ---------- Previous post was at 07:57 PM ----------

WOW!!! That really sounds GREAT.
[TouchPad Development] nevertells2:
Speaking of kernels. What is the difference between the 3.0 kernel Milaq uses and the 3.4 kernel you use? Things seem to be moving along swimmingly with 3.4 development, while things like camera and Bluetooth still have issues in a 3.0 kernel based KitKat.

Thanks,

NT
[TouchPad Development] flintman:
Unsure. I know the Bluetooth stuff came from the 3.0 kernel and the camera was initally setup on the 3.4 kernel by Dorregaray. Im surprised that bluetooth isn't working in 3.0.
[TouchPad Development] jcsullins:
You have outdated information.

Bluetooth and Camera have worked for a while with 3.0 kernel.
[TouchPad Development] garux:
Does any one know a good Philz_CWM 20140317 video that I can watch to get a good handle how it is used? I did a google search and found many for a specific device but not for the HP TouchPad.
[TouchPad Development] mpgrimm2:
Doesn't exist yet. RolandDeschain79 has plans to do one but real life has him busy with other things so it may be a while.

There is a link in post 2 of my Data Media thread under the recovery details for the generic PHilz CWM thread that has a lot of screenshots and general details on features etc.

Sent from my "Up All Night Sleep All Day" Nexus 5!
[TouchPad Development] martroy73:
I've had the chance to re-install everything last night but I was still getting SoDs almost everytime it was going to sleep. I've tried disabling the hotword detection without success. Same thing for when setting the governor to Performance. In the end, what I did was to disable the Performance feature in the Evervolv Toolbox and I'm now using Antutu CPU Master set to 1512mhz with the interactive governor. It seems to be rock solid now but I'll need to do more testing tonight.

Martin
[TouchPad Development] garux:
Thanks for getting back to me. I understand this is new adventure for our HP TouchPad and life as it is must go on. I was hoping something like the nexus 7 would have something that be used temporarily until Roland gets time to put a video out.
[TouchPad Development] garux:
searched and looked through the link. i only found links that didn't work.
[TouchPad Development] Moody66:
Everything you need to know is in the post. Tells you what everything does. It is the same recovery regardless of the device.
[TouchPad Development] nevertells2:
Got the information directly from milaq's 3rd post:

***********paste ***********

Known bugs / caveats:

camera

bluetooth

you tell me...

So I modified my post to indicate issues rather than not working.
[TouchPad Development] jcsullins:
I find your characterization of 3.0 kernel development to be grossly inaccurate both in specifics and in general.

That post you referenced was last edited about 3 weeks prior to Camera or Bluetooth working in either 3.0 or 3.4 kernels.

As far as I know, Bluetooth and Camera currently work just as well, if not better, with 3.0 kernel based KitKat.