yashsingh1/xdaforums huggingface dataset:
[TouchPad Development] lippy lipkowski:
Does your post have a point?

If so what was it?

Because it seems like nothing more than some self righteous drivel to me. Perhaps I am wrong but close to every post I have seen since the 28th and 29th have been people claiming the device is lagged since those flashes. YOU ARE VERY ANNOYING and your posts seem to offer little in the way of advice or practical. And why you have my post...ESPECIALLY that one and referring to it as a claim that the ROM isn't worth it seems VERY odd and out of place since I claimed nothing of the sort.

Quit yer *****ing.....*****ing about seemingly NOTHING.

I run this ROM on 3 tablets and have been empirically observing and stating the difficulty.

The performance of the ROM positively went south with the 1-28 and 1-29 flashes.

Your post seemingly has no purpose other than to *****.

Mine was meant to inform the devs about the observations I am making since I run it on 3 tablets since the 6.0.1 Flintman and am VERY familiar with the way to performs.

The other day you were suggesting another kernel be used which would clutter the dev scenario and pollute the pool of information on how THIS ROM runs.

Now you are purporting something else which once again really just seems like pointless *****ing.......in blue even.
[TouchPad Development] brchickery:
Same thing happened on the last 2-3 releases and my touchpad is barely even functional since then. I have been waiting for a new release but I haven't seen one since the end of January. Anyone have any updates?

Thanks!
[TouchPad Development] db_white:
Flintman indicated on devs-base that there will be a drop tonight for performance testing.
[TouchPad Development] BinkXDA:
While I’ve been generally pleased with my “recent” jcsullins CyanogenMod 12.1/5.1.1 build, I’m considering upgrading from the dark ages to 7.1.1 (my Nexus 5x is on 7.1.1 and I get annoyed—a muscle memory thing I guess—with doing various things the legacy way every time I grab the tablet). While 5.1.1 tends to get sluggish as well often, any idea if 7.1.1 performs better? My Wi-Fi and sleep (maybe 2 or 3 percent overnight) are pretty darn good right now. It also appears the latest builds have performance issues, but I also know forums tend to contain more negative posts versus positive ones by their nature. So, well, definitively, which recent but older 7.1.1 build still performs well? There seems to be some back and forth on this on this thread and it appears the oldest build I can readily download is from 1/20. I also noticed a newer build might drop tonight, but I have no issue going with a slightly older build and upgrading later.
[TouchPad Development] brchickery:
Thanks!
[TouchPad Development] tpuserhp:
After updated my device to 0209 test build, I got double/triple characters during typing of a character. I have not got to other testings yet.

After a reboot, duplicate characters during typing is not as bad as before. Also performace is better with this test build. Thanks.
[TouchPad Development] nevertells2:
Try following Devs Base here: https://devs-base.com/viewforum.php?f=46

NT
[TouchPad Development] BinkXDA:
Thanks for this—didn’t know about Devs Base. Almost reminds me of what xda used to be before it became ad ridden and sluggish because of this.
[TouchPad Development] chmcarro:
7.1.1 Testing build 2/10 is up. My initial impression is its noticeably snappier than 1/29 and 2/9 nightlies. BFQ/Interactive/1728Mhz max. May need to update directly from the embedded evervol update in android settings since there's no direct link on evervolv.com.
[TouchPad Development] tpuserhp:
From a quick testing, I found 0210 test build has fixed the sensitive keyboard typing issue. It also provides good performance. I have removed the performances changes I put in and just use the default settings. So far so good. Thanks flintman.
[TouchPad Development] chmcarro:
Gboard seems slightly snappier than the AOSP keyboard so you may consider getting it, although this may be a subjective performance difference.
[TouchPad Development] lippy lipkowski:
Tooltimers is as tooltimers does ehhhh Nevertells? Muwhahahahahahaha

I EAT TOOLS FOR BREAKFAST!

---------- Post added at 10:25 PM ---------- Previous post was at 10:24 PM ----------

You know what? I am running Ublock! That is why I wasn't getting what people were finding so bad about XDA!

I haven't been seeing ads since I AM BLOCKING THEM!@

HAH!

Touche!
[TouchPad Development] rob_z11:
So latest nightly fixes the slowness? I am going to restore my nandroid backup, and flash it tonight. 6.x is running decent at this point..

Thanks for everyone's help.. one of my best investment :)
[TouchPad Development] TaylorV:
An open question for anyone, posting here because it's related to Evervolv rather than creating a new thread:

Between Evervolv 5, 6, and 7, is there any single build that is rock solid, fast, and reliable? Evervolv is constantly getting better on 7, but I've used versions of Evervolv (either builds from Android 5 or 6) that felt like they were running on a flagship phone - instant responsiveness and quick. Current 7 builds run, but they're just not snappy - even after letting them settle down for a couple days.

I want to be done updating my HP Touchpad forever. I want it to be snappy. In your opinion, what is my best option? Or is there some configuration of CPU IO modes that will significantly speed up 7?

Thank you
[TouchPad Development] cityengineers:
Touch Screen freezing issue is not resolved yet. Its annoying and hope it will be addressed soon.
[TouchPad Development] nevertells2:
You really should post at the link below, the devs are not using this forum anymore.

NT

https://devs-base.com/viewforum.php?f=46
[TouchPad Development] BinkXDA:
My TouchPad is reborn, again. I happily wiped WebOS a long time ago for jcs’s CM 5.1.1 and thought I couldn’t be happier. I had the latest Android goodness for 99 bucks (via the fire sale)! However, not all was well. While I had Android, it was slow. It was unbearably slow at times and, lately, some of my favorite apps stopped working. I decided to do something about this and grabbed the latest EV 7.1.1.

Wow. WOW! My TouchPad is faster, all my apps work again and this legacy hardware is running the same version of Android as my Nexus 5x. Yay!

In the hope this helps another jcs CM user, here’s a quick rundown on how I quickly did it:

Load TPToolbox (thank you again jcs!), update system size to 1312MB and copy over legacy TWRP, modern TWRP, EV and open gapps

Boot into CWM and install legacy TWRP (Is this step required? I took some guidance from https://xdaforums.com/showpost.php?p=68557244&postcount=3.)

Boot into TWRP and install modern TWRP

Boot into TWRP, wipe system, data, cache and ART cache, and install EV and open gapps

Reboot, see lengthy, but colorful, EVERVOLV animation and continue to take advantage of the best $99 you ever spent!

I might come back and update this OP with my first impressions and related.

Thank you again EV team!
[TouchPad Development] TaylorV:
Just a note for anyone having issues with lag - if you're choosing the option to restore your device when first setting up the tablet, try instead to set it up fresh and see if that changes anything. This may have been mentioned previously, but I've been struggling because of this and figured it could be said again. Setting it up fresh (even if I install the same apps again later) seems to make the TP function much better.

Also, the only real issue I'm having with the latest builds is that wifi refuses to stay connected for too long. Anyone know of a fix for this?
[TouchPad Development] nevertells2:
No need to flash the legacy TWRP first. You can use CWM to flash the modern TWRP. You did all the correct things by enlarging /system first, then

wiping /system, /data and all the caches and installing EV and Gapps together. Doing it this way avoids all the issues of incompatibility between

a CM Rom and EV Rom. A couple of questions, when you say modern TWRP, do you mean version 3.0.3.0 and which Gapps did you install?

Because you did it this way, you can pretty much flash any Gapps zip you want. It's issues with TPTB only being compatible with certain versions

of Gapps and TWRP that makes the way you did it the best way. TPTB v.42 was released in Jan. 2015. An update is needed to make TPTB compatible

with all these newer versions of TWRP, CWM and Gapps. Don't know if Mr. Sullin's ever plans an update, but that is what is needed.

The alternative installation method using TPTB v.42 would be to use all legacy versions of CWM or TWRP and using an older EV Rom and a compatible

Gapps after doing a complete data reset. Once these are installed, use TPTB to enlarge /system and then flash the modern TWRP and use that to install

EV 7.1.1 and your choice of Gapps.

NT
[TouchPad Development] BinkXDA:
Cool.

This was my way of thinking as well.

FLINTMAN-TWRP-touch-data_media-SELINUX-f2fs-3.0.3.0-1-23-17 and open_gapps-arm-7.1-pico-20170217.

Thanks for taking the time to better explain why my process worked as well as it did.
[TouchPad Development] lebenskuenstler:
Hi,

I just wiped my Evervolv 6.x install and flashed 7.x and pico gapps.

My lvm-volume for system is aprox 900 MB from which 460 are available after install.

Maybe partitions recommandations should reflect the gapps package that the user may choose. Esp. on 16G Touchpads space is very limited and thus valueable.

Evervolv 7.x and nano package shall just be fine with 750 MB (not tested). Half a gig saved.

Best,

LK
[TouchPad Development] nevertells2:
I would suggest you follow the recommendation of the developer of the Rom to avoid issues. He did not arbitrarily pick that size for the /system volume.

NT
[TouchPad Development] crazyates:
My 32GB TP used to be laggy, slow, and almost unusable. It is so much better now! Thanks so much for these steps! I did everything here, with a few changes:

Step 3: While you're copying the older ROM/Gapps/TWRP into the "ttinstall" folder, I also copied everything you need for the new install into an "evervolv" folder. This way you can copy everything at once, and formatting a volume in TWRP doesn't destroy your install files.

Step 4: I have a 32GB TP, and don't use hardly any of it, so I increased the System to ~2GB, and the Cache to ~1GB. I figured going on the big side couldn't hurt.

Step 6: There's a newer version of Flintmans TWRP, 3.0.3.0(12/22/16).

Step 8: After you wipe the System, reformat the Data and Cache volumes as F2FS. Because your install files are on the External_SD instead of the Data, you can do this without recopying your install zips back again. I installed the system twice, once with Ext4 and once with F2FS. It feels snappier, and runs a lot better with F2FS.

Step 9: I used the Nightly build for the ROM, which is working great. Then the newest Gapps. Then I also flashed the SKZ overclock kernel at the same time.

Step 10: This is the most important step. Thanks so much guys! It's great to see this still being worked on!

Few other notes: Changing the Governor to LionHeart and Scheduler to Tripndroid made a noticeable difference for me. Also, because this doesn't have a lot of RAM, I gotta be careful with what I install, and how much I try to use it. Do NOT install Chrome from the app store. It will eat every bit of RAM available, and slow the whole thing down. I also use Greenify (with root permissions) to hibernate any app I can so it saves a lot of RAM that was as well. I'm using ~329MB (40%) for the system, with ~500MB (60%) available for apps.

Again, thanks so much for this fantastic ROM & development & support!
[TouchPad Development] AlwaysLucky:
I'm glad those steps helped you out. I also updated my post with the new TWRP 3.0.3.0 link. Thanks! :good:
[TouchPad Development] NE0HP:
Latest TWRP is 3.0.3.0-1-23-17 here is the link http://evervolv.com/static/builds/misc/FLINTMAN-TWRP-touch-data_media-SELINUX-f2fs-3.0.3.0-1-23-17.zip
[TouchPad Development] AlwaysLucky:
Post updated. Thanks!
[TouchPad Development] nevertells2:
I'm curious, I checked the official TeamWin website and the latest release number according to them is 2.0.2.0. So what exactly is 3.0.3.0?

Thanks,

NT
[TouchPad Development] AlwaysLucky:
It appears TWRP 3.0.3.0 is unofficially out for dozens of devices. However, regarding the specifically compiled TWRP 3.0.3.0 version for the HP Touchpad, I think your question would be better suited for the author of it and the OP of this thread: [MENTION=3716175]flintman[/MENTION]
[TouchPad Development] nevertells2:
BTW, my bad on the version, TeamWin version is 3.0.2.0. Hopefully Flintman will clue us in.

NT
[TouchPad Development] AlwaysLucky:
We knew what ya meant, no worries. :) And yes I am a little curious about it as well.
[TouchPad Development] nevertells2:
I was curious and looked on the OP and did not see a link to 3.0.3.0. Where did you find it?

NT
[TouchPad Development] garux:
It's in the devs-base nightlies forum, 2nd post.
[TouchPad Development] AlwaysLucky:
http://evervolv.com/static/builds/misc/

---------- Post added at 09:39 AM ---------- Previous post was at 09:28 AM ----------

I also noticed the OP isn't being updated at all with new ROM versions.

Here are the Wifi model builds and the 4G model builds. I'll update Post #3 with these links as well.
[TouchPad Development] nevertells2:
I wasn't thinking, Evervolv has abandoned this thread, so makes since nothing it being updated.

NT
[TouchPad Development] AlwaysLucky:
Well that's rude to not even notify this thread. Hopefully the new thread (if there even is one) author had the decency to not put the entire OP in quotes again like a nooooob. :eek:
[TouchPad Development] garux:
If you search in this forum, you'll find back around January 18th they start talking about the new thread that was created.

Just my 2 cents.
[TouchPad Development] shumash:
Perhaps looking before posting would be less rude.
[TouchPad Development] nevertells2:
Not reading this thread dude is to your detriment. It is well documented that Evervolv has moved on to a new forum called Devs Base.

And be careful, you are treading very close to crossing the line in making personal attacks which is against the rules.

NT
[TouchPad Development] Nomad1600:
There are other ROMs. Perhaps you'd be happier using another ROM.
[TouchPad Development] joshua764:
Which is the most stable version to recommend

Enviado desde mi Touchpad mediante Tapatalk
[TouchPad Development] DoubleStuff:
After reading some chatter on the XDA threads, I believe there is an alternate facts "start from scratch" method for installing Android 7.1 that I have had success with. We all know the tried and true AlwaysLucky #3 post. Well here is another method, now it may take a little more technical maneuvering, but should be easy enough. At least you have choices ( yea 2+2=5 ). And I will post the steps I use for success.

The pro's of this method is you only need 3 ZIP files, ROM, Gapps, and TWRP. No need for the old "TPTB compatible ZIPs" as we will only be using the TPTB to do 1) complete data reset, and 2) resize the Android volumes. The actual install will be done by the temporary install of TWRP on TP.

I will attached a custom zip file that contains 2 new files ( .bat and uImage file ), which you should download and extract, and place the files in the same directory as your working tptb_v42_win.bat on your PC.

I will post my steps and attachment next....
[TouchPad Development] DoubleStuff:
IMPORTANT as of 3/25/2017

I am no longer updating this post #956, but please go to link below for

the updated post, and how to video!!!

Press Here to go to most up to date post and how to video!

Version 03 updates made

( Version 03 zip at bottom of post )

* assuming you have already loaded and have working TP Toolbox v0.42.

* No TPTB Compatible ROM, GApps or TWRP needed.

Steps to success for loading Evervolv 7.1 ROM from scratch:

I. Download doubleStuff_v03.zip:

I have attached the doubleStuff_v03.zip file containing these key files:

1. TWRP_TmpLoad_v03_win.bat

2. uImage.TWRP

Download and extract, and place both ( 1 & 2 ) files in the same directory as your working tptb_v42_win.bat on your PC.

II. Download ROM, Gapps and TWRP ZIPs:

Perform the following steps on PC to prepare it for load:

Download Permanent TWRP Recovery zip:

FLINTMAN-TWRP-touch-data_media-SELINUX-f2fs-3.0.3.0-1-23-17.zip

Download the latest Evervolv 7.1 ROM ( WIFI model is most common )

WIFI ROM

4G ROM

Download the latest 7.1 OpenGApps

7.1 Open Gapps

Set these aside on your PC for now, we will need them later.

III. Touchpad/PC Execution steps:

Boot into WebOS Recovery ( giant USB symbol ) with cable connected to PC.

Run regular tptb_v42_win.bat and perform:

1) 'Complete Data Reset'

2) 'Resize Android Volumes'

Resize Volumes to:

--Media: 1000 MB,

--Cache: 200 MB,

--System: 1312 MB,

--Data: the rest of the memory.

3) Press APPLY to commit changes, then....

4) Reboot into WebOS Recovery ( again )

Run TWRP_TmpLoad_v03_win.bat, and it will temporarily load and bring up the TWRP Recovery ( 3.0.3.0-1-23-17 version ) but remember later on you still have to load the permanent TWRP with install.

Running TWRP recovery automatically creates a folder in the /data/media directory called TWRP, on the Internal SD card ( data ).

IV. TWRP Install steps:

( If screen falls asleep, and power and home buttons don't respond, tap screen )

Once in TWRP Recovery, go to your PC which is still connected via cable to TouchPad:

1) Copy ROM, Gapps, and Permanent Recovery zip files into the

/Touchpad/InternalStorage/TWRP mounted Touchpad volume.

( P.S. actually you can copy the zips anywhere in 'Internal Storage' or 'Micro SDCard' Touchpad mounts, as long as you know where to find them on your Touchpad, I am just giving you the default location for simplicity sake )

2) Once copy is complete, you can disconnect the USB cable from the PC and Touchpad.

3) These zips will then show up on the /sdcard/TWRP or /data/media/TWRP directory on your Touchpad.

4) Select INSTALL from TWRP, drill to /sdcard/TWRP directory, then load the ROM, Gapps and TWRP zips, via 'add more zips' button, then swipe to flash.
[TouchPad Development] RolandDeschain79:
Thanks for sharing I'll test it out:highfive:

I just put together a little video to help with the confusion about the lack of Devs Base links, might want to add it to your post. I was also confused by the lack of info at first until I read the whole thread, lets keep the forum friendly people. I made several posts about the new location but the mods have removed them all.

[YOUTUBE]KDEkSQ5Xgbw[/YOUTUBE]
[TouchPad Development] AlwaysLucky:
:laugh: :laugh: :laugh:

And for those without excessive sodium chloride issues, I'll keep my simple guide in Post #3 updated with current links. :good: Lets hear it for the edit button! Hooray!:highfive:
[TouchPad Development] DoubleStuff:
Of course you should keep your Post #3 updated, but I was also hoping you, Nevertells, and Lippy would test my "NaCl" method, and then if you guys have success, you can give me tips and I then can have a nice clean post for "Android O" with all nice links and stuff like AlwaysLucky has.

Remember we here in this thread are essentially the testing arm of Evervolv, and like RolandD always says in his videos, "Evervolv, always evolving, Evervolv", so lets keep evolving and growing and helping as a team!! :) :)
[TouchPad Development] nevertells2:
After reading your post several times, you might want to clarify the folder where your files should be moved to. What you call the " /tptoolbox_v42 directory" is actually C:\programs files\Palm,Inc. I've been playing around with Sullin's TPTB long enough to know where you are talking about, others might not. In fact, you might want to make the instruction read to "Unzip my doubleStuff.zip into C:\programs files\Palm,Inc. No need to unzip it elsewhere and then copy the to files there. I'm not quite sure why you did not name the uImage file in your zip to uImage.TWRP or does it get named uImage.TWRP when it is unzipped? Thus no need to rename the file as you mention in your instructions. Otherwise, very slick idea on your part. Since it does not appear Mr. Sullins is going to update TPTB, your method eliminates the need to install older Roms, Gapps and recoveries that it recognizes and then use TWRP or CWM to flash the newer Rom, Gapps and recovery. BTW, what version of TWRP did you put in your doublestuff.zip?

I just noticed that whoever is following your instructions needs to go find the latest version of Flintman's TWRP. You might want to include a link to that download in his Nougat thread or provide a copy with your doubleStuff.zip. So basically, one is going to have your batch file and uImage.TWRP residing in C:\programs files\Palm,Inc and the Rom zip and Gapps zip and the TWRP.zip residing in this \TWRP folder located in the /media volume on the TouchPad. Do I have this right or am I having trouble understanding your instructions? BTW, how does that TWRP folder get created? Does your batch file create it? What happens to the ttinstall folder? Does TPTB create that when "Complete Data Reset" is run? If it is already there, /TWRP is not needed or does your batch file look for that folder instead of ttinstall?

NT
[TouchPad Development] DoubleStuff:
Hello Nevertells, thanks for the excellent feedback, thats what I was looking for. Believe me if we ever made a Tenderloin software company called "EverTells", you would be put in charge of "quality control". LOL :good:

To answer some of your questions well the directory "C:\Program Files\Palm, Inc" essentially is for Novacom stuff, and its used by the TPTB but its usually not the directory where the TPTB bat and bin files reside. For example when you take Sullins last v42 version TPToolbox-2015-01-08-v42.zip and unzip it, the user is allowed to edit wherever it gets extracted to, I think the default is to /TPToolbox-2015-01-08-v42. But since my bat adds "C:\Program Files\Palm, Inc" to the main PATH variable, it can find executable like Novacom.exe from any directory.

So because of your good advice, I will tell the user to extract my zip to the directory where they have their current working TPTB. But the main point is my bat and uImage have to be in the same directory, if not, my bat file will complain, and give an appropriate error message.

And you are correct, I could have kept the name 'uImage.TWRP', but because in my bat code I hardcoded the string 'uImage', I am stuck with that name for now. But going forward to Android O, I can make tweaks to my bat file accordingly. Unless Sullins makes an appearance and updates his TPTB to v43, which would make all these phacts and phun obsolete! LOL :highfive:

And BTW yes, my uImage was extracted from the current TWRP, FLINTMAN-TWRP-touch-data_media-SELINUX-f2fs-3.0.3.0-1-23-17.zip. But you still have to install this zip, if you want a permanent copy on your TouchPad. If you don't want a permanent copy, to save space in boot for example, you would have to run my bat file from PC every time you want to use TWRP ( not ideal ).

Good question about the TTINSTALL and TWRP directories. As you probably know there is a black box program in TPTB called TPToolbox-2015-01-08-v42.bin, which nobody has the source code for, not Flintman or anybody, but only JC Sullins. So I can only guess that Sullins black box program is creating TTINSTALL and maybe TWRP, I am not creating the TWRP directory, it was just there after complete data reset.

Its important to note, that after doing a 'complete data reset', and Resizing Android Volumes with TPTB, we then are essentially done with the TBTP. So what I am saying is we will never select "Install Android" on TPTB, thus no need for TTINSTALL directory anymore. And the reason we have to manually Resize all Android Volumes in my method is because usually "Install Android" on TPTB does it automatically, but we are not going to run that.

Bottom line is we are not installing the Android 7.1 ROM via TPTB, but via temporary Recovery TWRP, which is loaded by my new bat program. Once in TWRP, most users then know the drill on what to do, load ROM, Gapps, TWRP zips ect...