yashsingh1/xdaforums huggingface dataset:
[TouchPad General] HP_TOUCHPAD:
Read the section of this Guide ( First page ) I provided Flash files that will Clean boot, Flash the ToolBox into Boot and Removed it from Boot, all is done by just a flash.

Here are the files, but read my details explanation of the boot partition : Click Here for Flash ToolBox to Boot Files.

If the user is using the ROMs from this guide, there is no need to backup and restore boot for the following reasons:

The only file that boots Android is the uImage.Android of about 7MB. I provide the flash files for the settings with Swap or Stock. Once the backup is restored the corresponding Flash file can be flash and it will removed the old with the new.

If the user is using the Tablet with Swap, but wants to use it with the Phone setup then flash the Stock flash file, that's all.

During the restore process TWRP, wipe boot ( all files removed ) then it formats /boot and finally copy all the files again., all that for only a 7MB file !

The most important partition of the Tablet is the fixed (can not be changed ) 32 MB /boot. Reformatting /boot every time a ROM gets restore is unnecessary and " if " by reformatting constantly it may degrade the life of that partition and then the only way to boot will be connecting the Tablet to PC and use Novacom drivers to load the uImage file. Very important in TWRP go to Settings (Third option down from left ) Check (( Use rm -rf instead of formatting )).

I will be posting very soon the HP_Touchpad_Novacom_Recovery_Android; with that any user can do the following with one click on any Computer, old or new.

Load the ToolBox (flash the A6 Firmware)

Fix /boot using Create_Boot ( If the Bermuda Triangle shows up ) or the Tablet can not boot.

Automatic_Wipe_All_and_Create_Android_with_Swap ( Total Data Reset ) Or if the Tablet needs to be set up only for Android.

Change the Ramdisk, make all setting modifications and create a Custom boot file.

If the user needs help, the Tablet can be setup "completely" from starting with the Automatic_Wipe to Android, remotely by another user any where in the Milky Way Galaxy that has an internet connection.

The Novacom Driver and Android ADB Shell will be fully working and permanent all the time regardless of the PC been use.
[TouchPad General] anonxlg:
want to give me 2 cents again having tested 5.1 and 7.1.2 for a while now:

tldr: 5.1 is in general more 'stable' than 7.1.2. but 7.1.2 is better when it works

I could not reproduce the 'super low' battery drain i was getting on 4.0.3

To clarify, super low means it takes hours (sometime many hours) before registering -3mA on 3c battery app. For example, over 10-12 hours, it might drop a few percentages

I was able to reproduce this behaviour in 7.1.2, so all around battery life is better on 7.1.2 due to better deep sleep/idle.

I've mentioned in a previous post, 7.1.2 feel snappier and is a better experience when it works. There are random stutters that make it feel sluggish. My best guess for this is when launching a new app, or app switching, the swap is being used and since it's slower, that's what's causing these stutters. This fits my theory because when I have an app fully loaded, i *rarely* experience any hiccups. These stutters happen more frequently as uptime increases. Having said that, these stutters still happen when i newly bootup the tablet, so it's probably something to do with slow emmc or a combination of everything. Of course I have no way to prove this and if these stutters happen without the swap mod, then problem lies with either the emmc, and/or the the rom/kernel is not being optimized along with old specs.

This bring me to my next observation (which i'm very certain of)

As far as I can tell, after all my testing, there is something (a process or service) that randomly takes up 99% of cpu usage. It's so bad that it makes the tablet unusable and require a hard reboot.

I believe in my case, it is some google service (i think it has something to do with the play store), but considering there was someone else here that said they were running microg and was encountering this, it could be something more fundamental or it could be a bug.

2d and 3d games run better on 7.1.2 than 5.1. Performance wise, i would say for 3D games, 7.1.2 > 5.1=4.0.3. 2d games 7.1.2=4.0.3 > 5.1. Here I would guess 4.4.x would perform similar to when I was running 4.0.3

Long term wise, I can live with using 7.1.2 and it's random stutters. However, it's hard to ignore the '99% cpu usage' problem i mentioned, but as long as it doesn't happen too often, I would use this over 5.1.

I will have to use this longer to see how tolerable I am to it.
[TouchPad General] HP_TOUCHPAD:
It all depends how the tablet is used for and each ROM provides some advances over the other. Is a different Android version and also Kernel plus the Hardware Support.

Overall 7.1.2 is a very good ROM that does it all. Use TOPS to take screenshot of the process using the CPU too mch and a solution can be applied. I can easily apply changes to the Kernel of 7.1.2, 8.1 and 9. All the posted settings does not have any Kernel modification at all, the Kernel is stock. But if there is an issue and the user find it, I can try to fix it and post the new setting which all user will benefit.
[TouchPad General] smithylovestouchpad:
HPTP created a zip to place TouchPad Toolbox into /boot. However, if you are comfortable using an app like Rom Toolbox Lite or Root Explorer, then copying TPTB into /boot works fine, done it many times. You can also use the file manager in TWRP to copy TPTB into /boot. Just remember to "Mount" /boot first.

I also agree with HPTP, using TPTB to look at your TP's partitions does not do any harm. Just don't use it to make any changes to them.

Smithy
[TouchPad General] DoubleStuff:
Ahhh Smithy those instructions remind me of the "good ole days" of the this forum, when maybe back in 2015 somebody would ask, "How do you get TBTP into the moboot?" And usually the person who answered first would get a few "thanks".....So I will give you a "thanks" just for the memories...
[TouchPad General] smithylovestouchpad:
:o
[TouchPad General] anonxlg:
yeah, my suspicion was correct, it's google play store and/or service causing it:

com.google.android.gms.persistent and com.google.android.gms

and like i thought, it was using alot of I/O dispute not seeing any apps/instant apps being updated
[TouchPad General] HP_TOUCHPAD:
Did you take screenshot showing any of those process using the CPU at 90 + plus percent for over a minute?

Attached are screenshot of PIE with the Open Gapps variant SUPER ( the maximum any android device can have installed )

Take a look at how idle the CPU is working and the services you mentioned, also youtube is playing on one of the screenshot.

It could easily be an App that is installed causing the Android com.google.android.gms service, but the play store by itself does not create that issues unless is checking for updates or downloading and installing.

It is important to have the Tablet on connected to WiFi all time to keep all system sync and ready to be use.
[TouchPad General] smithylovestouchpad:
So the Media.codec using over 83% isn't a problem? Looks like your TP would not be able to do much else.

BTW, I finally figured out the issue on my PC not running scripts thru Novacom. The Novacom driver was corrupted and had to uninstall and reinstall and it worked OK. Go figure!!!!

Smithy
[TouchPad General] HP_TOUCHPAD:
I am done with the HP_Touchpad_Novacom_Repair_Android, no need to ever worry about the Novacom drivers working or keeping an old Operating System on a PC just to use it. Testing at the moment, will post very soon.
[TouchPad General] HP_TOUCHPAD:
The HP Touchpad Novacom Repair Android Guide can be found here:

Click HERE for HP Touchpad Novacom Repair Android Guide and File

This guide will be updated, hopefully I can get Universal Authority guide done.
[TouchPad General] smithylovestouchpad:
Deleted
[TouchPad General] LightC:
I have two 32GB HP Touchpads. It seems as if the flash process only works on one of the two touchpads. One of them will just endlessly load Evervolv. If I just flash Evervolv after 'Automatic_Wipe_All_and_Create_Android_with _Swap', it seems to boot fine. It's when I flash the HpTp Universal Optimize Swap Settings and ROM Reducer on this tablet that causes a problem when booting into Evervolv.

It's weird because the two Touchpads are identical and I would expect the flash process to be exactly the same. I tried to copy the files to the problem Touchpad a few times in case it has to do with an error during the transfer but had the same issue on subsequent flashes.

Any ideas? [MENTION=8005714]HP_TOUCHPAD[/MENTION]

Here is the flash process I'm using:

Automatic_Wipe_All_and_Create_Android_with _Swap

Evervolv 7.1.2 ROM (I can get the problem Touchpad to boot after this step if I don't flash the remaining below)

HpTp Universal Optimize Swap Settings

ROM Reducer

Open Gapps
[TouchPad General] HP_TOUCHPAD:
What is the CPU frequency that is been used on both Tablets?

Use the lowest CPU frequency on the Tablet that is not booting into Android. That is the only reason that it hangs.

The flashing process will work on ALL tablets, but not all Tablets can handle the same CPU frequency.

Use the HpTp_1674_CPU, if it does not boot then let me know and I will create a lower frequency HpTp.
[TouchPad General] LightC:
I was using the 1674 frequency on both tablets. Is it possible that flashing Automatic_Wipe_All_and_Create_Android_with _Swap twice on one of the tablets caused this issue? It looks like I'm not having the same problem on the first tablet after running through the same flash process that worked the first time. I'm starting to think I may have flashed this twice on the problematic tablet and it screwed something up: Automatic_Wipe_All_and_Create_Android_with _Swap

Now that I did the procedure again on the working tablet, both of them are endlessly cycling the Evervolv logo... Ugh

Any suggestions on how to fix this easily?
[TouchPad General] LightC:
So interestingly, I noticed that even after flashing the wipe all on both tablets, the moboot menu is different on each Touchpad. The one that works fine with flashing the optimized swap file has Boot Recovery, Boot Evervolv, Boot WebOS recovery, reboot and shutdown.

The problematic Touchpad has an extra option in the moboot menu. It has the following moboot options: Boot Recovery, Boot Evervolv, Boot Cyanogenmod, boot WebOS recovery, reboot and shutdown.

I'm able to boot into Evervolv using the Boot Evervolv option if I don't flash the optimized swap. If I flash it, it hangs upon boot.

Interestingly, if I flash the optimized swap and choose boot Cyanogenmod, I'm able to boot into Evervolv with even the highest CPU frequency swap file. I verified the CPU frequency with cpuz in Evervolv.

I suspect however that the swap settings are not active as it clearly runs uImage.Cyanogenmod when clicking the Cyanogenmod option in moboot.

[MENTION=8005714]HP_TOUCHPAD[/MENTION], any thoughts? Maybe I need to use the toolkit on the problematic tablet to get the moboot to match the Touchpad that doesn't have an issue? There is something wrong with the changes made to uimage.Evervolv on the problematic tablet that has the extra moboot option preventing it to boot.
[TouchPad General] HP_TOUCHPAD:
@LightC Finally just now I am able to logging in to XDA Web site, after I replied to your last message the XDA website has been down from my side with no way to logging at all.

I did found the issue and fixed it, here is the problem:

The HpTp setting are completely different from previous ones. When the changes were added to Evervolv 7.1.2, the codes to enter the CPU frequency where placed before the old code and I did no noticed it. When the new CPU frequencies got applied, the previous settings overwrote it at boot time. That created that all the frequencies were set to 1782 and that made all tablets to run on 1782 only on Evervolv 7.1.2. One of your Tablet can a handle higher frequency of 1782 but the other does not and all the files had the same 1782 as per my mistake. I did change it and uploaded the new files and also added the 1512.

Both of your tablets works fine and I am sorry for the mistake and created the waste of time and frustration. The Cyanogenmod is the name of an older Android boot image from Kitkat or Lollipop. The Wipe_All works on all Tablets and after the process the only thing available on the moobot menu are : Boot Recovery, Boot WebOS recovery, reboot and shutdown. After flashing a ROM the specific name will be available.

Redo the Wipe All on the tablet that did not boot, it will clean boot and download the new files for Evervolv posted on this guide. Start with 1674 and increase it after successfully running Android.

Now that I have access to the site again the guide will be updated to include the new Evervolv 9 Pie updated on Friday.

Thank you for reporting the issue!
[TouchPad General] LightC:
Thanks for your help. I'll try flashing the updated files.

The one curious thing is that I flashed the wipe_all multiple times on the problem tablet but the Boot Cyanogenmod does not get removed from the moboot menu.

It definitely flashes as I see that it changes moboot for the initial wipe boot but it reverts to the same moboot menu aftrrwards
[TouchPad General] HP_TOUCHPAD:
When does it reverts back?
[TouchPad General] LightC:
It *think* it added the "Boot Cyanogenmod' option after flashing the old optimize swap files. I can't replicate it now with the new ones you've posted but your fixes did the trick. The touchpad that wasn't booting is now booting just fine. Thanks again! I'm still not entirely sure why the same flash process worked on a different Touchpad with the old Hptp optimization files.

Do you know if there is a way to get microg on here with full Google play services support? It seems like the ROM needs to have 'Signature spoofing' enabled to get microg to fully be recognized as Google Play by other apps. Or do you recommend to just use opengapps?
[TouchPad General] HP_TOUCHPAD:
All listed ROM works perfectly with Open Gapps and support the Play store.

If the user wants to use Microg, it was discussed on this thread beginning at post 310

https://xdaforums.com/showpost.php?p=79892169&postcount=310

The user [MENTION=4222665]schwatter[/MENTION] is the expert on using microg, I followed his guide and was able to get it working.
[TouchPad General] HP_TOUCHPAD:
Update: Evervolv 9, Universal Authority

The guide has been updated:

Evervolv 9 is available and working perfectly !

https://xdaforums.com/hp-touchpad/development/rom-evervolv-hp-touchpad-t3923512

Universal Authority ( updating commands )

https://xdaforums.com/hp-touchpad/general/hp-touchpad-universal-authority-t3963766
[TouchPad General] johnbelloh:
A great big thank you to all the developers contributing to this project. I just clean installed the latest Evervol release on 7 touchpads. I have never seen the HP touchpad perform at this level since its inception. It not only runs all applications but does so smoothly. Congratulations to all involved. You have resurrected this old reliable workhorse and carried it forward into the modern world.
[TouchPad General] HP_TOUCHPAD:
All the listed ROMs from this guide using the HpTp settings performs very similar.

Now with two good working Android PIE ROMs, the Tablet can finally be lay to rest when Google in the future completely stops support for PIE as of right now, we are seen Apps not supporting KiKat. There still 5.1, 6. 7.12, 8.1 and then 9 !

Only time will tell for how long this workhorse of a tank will last !

Thanks for the feedback, is the only way for the developers to know their work is been use and successful.
[TouchPad General] Steelskinz:
Any chance you add lineage-14.1-20180906-UNOFFICIAL-tenderloin in your list ? I had to reinstall it for DRM and tv apps but i'm not sure i have swap on it right now. Thanks.
[TouchPad General] HP_TOUCHPAD:
I will have to rebuild same as I have done for all the other ROMs.

Yes I can do it, post on here the link of the ROM's source to download and I will post the HpTp settings for it.
[TouchPad General] Steelskinz:
This is it : https://drive.google.com/file/d/1sc9Y2Yp5yHAet9VxmZi7FjNdtfpV2jgT/view
[TouchPad General] LightC:
Does Google Assistant work well on any of these ROMs? it would be cool to use the touchpad as a smart display
[TouchPad General] HP_TOUCHPAD:
I believed that the Microphone works well on all ROMs post it on this guide and that is the only thing need it for the Google Assistant to work, give it a try and let us know !

At this moment I am working on updating all the Kernels to improve performance, all listed ROMs will work faster !
[TouchPad General] anonxlg:
so i've been somewhat continuing to monitor the lag issues, and I'm not sure it's *directly* google playstore/services' fault anymore.

recall that that i've been suspecting something is overly causing high amounts of disc usage, i've been seeing upwards of 20mb/s being used with monitoring overlay when tablet is idle upon tablet wake up, turn on, or app switching.

I believe it's some internal mechanism and playstore/services definitely has something to do with it but not totally cause.

because it's some sort of disc access bottleneck, the process using all the disc access might not be using any cpu cycles, so it's kinda hard to pinpoint the problem:

if you take a look here, iow is using most of the 'cpu cycles' and it's not part of the user/system resource list.

it's not unusual for iow to go up to 70-80% which user+system is like 20%

not sure how to 'fix' this, but it takes like 3-5 minutes after turning on or waking up from sleep to like the iow/disk usage to stabilize before it's usable
[TouchPad General] Steelskinz:
Any news about settings for the lineage build ? Thanks.
[TouchPad General] HP_TOUCHPAD:
There is going to be big news for lineage build and all the listed ROMs from this guide.

I have been optimizing the Kernel and found extra RAM (Memory) that has been excessively reserved for no use at all and settings that makes the Tablet run slower. All ROMs have it set up that way. I will provide the new setting as HpTp_MAX_ for all the ROM's that the Kernel can be properly re-compile.

The Tablet will work even faster and smoother than now, with an average of 100 MB of extra RAM.

That is the reason that I have not provided the settings for Lineage, I am redoing them all.

The attached screenshot is from Evervolv 9 Pie flash with Super Open Gapps showing 931.9 MB of RAM, that is even more than the RAM available in WebOS.
[TouchPad General] DoubleStuff:
See pic below now on CM 11 w/swap and 887 MG of RAM, while running RunRace 3D while simultaneously listening

to a podcast with the app Castbox ( both connect to internet ), I still get errors like "RunRace 3D has to stop, wait, close app, ect..." then I take a look at the RAM and there is only 43 MB free.

Is there a way to connect the HP TOUCHPAD to the puppy linux terminal window, while I am playing RunRace 3D and listing to Castbox, and somehow take a live look at the RAM being used and the SWAP? Like using "top" or any other LINUX command, I want a live look at the memory usage.
[TouchPad General] HP_TOUCHPAD:
Yes the Tablet can be connected to any PC with ADB shell install, open a terminal window:

Adb shell

to display the memory and swap type

free -h

The command must manually be enter, is not going to refresh by itself. In the older version of Android top does not do that, but new version Top does refresh and display all the info.
[TouchPad General] DoubleStuff:
Yes I understand I could play "RunRace 3D" without using the internet, remember we talked about that a long time

ago, and that the players that join the race are just "bots", I could also download a podcast and run it on Castbox without the internet also, but I choose to use the internet to get close to the limit of RAM use on this device, I am actually trying to break it for testing purposes. ( I wish it would not break ) That being said I tried on both my Touchpads CM 11 and Nougat to try to run ADB and perform the "top" and/or "free -h" commands to watch live memory usage, but even though the Touchpad is connected, I get this funny error when starting the ADB terminal window. Is there anyway to fix it?? During my Journeys last couple weeks, ADB was working with success. I will post a picture below.
[TouchPad General] HP_TOUCHPAD:
To test the limits do this:

Load the system to almost all RAM is use, then using the Universal Authority run swapOFF, or look at the script it can be run from adb shell as root.

The easiest and fastest way install this App and run it:

https://play.google.com/store/apps/details?id=me.empirical.android.application.fillmemory&hl=en_US

To be able to use Adb shell commands, make sure is enable in developer's mode. The message that is display in Linux is that the service is not running in Android. Connect the Tablet and use adb shell command, before start testing.

By the way, is official the Tablet can drink WINE, it works perfectly get ready to get drunk with WINE, I will post a guide on it, got to finish the new MAX settings first.
[TouchPad General] DoubleStuff:
my comments in blue above
[TouchPad General] middle_road:
Back in July (~11th) I flashed Pie the night before I had to leave on a 3-day trip.

(Trip ended up turning into a 17-day trip from h*ll...)

By the end of the trip the TP had bogged down and gone belly up.

I'm pretty sure I flashed something incorrectly in my rush to get packed up.

Flash forward to this month and I'm starting over and trying again.

So far I've done one up with Elginsk8r's EV9 and another with EV 7.1.2

The Pie is working very nicely except for the battery drains overnight. I've got to do some digging into that problem.

The Nougat isn't performing well at all. Very sluggish and a lot of 'Waits' or 'Close' popups.

I flashed the '1674' Optimizer on both.

On the Nougat one though, I'm not sure if I flashed 'SKZ-tenderloin-kernel-2017-12-01-1147.zip'

Any or all of the problems might be hardware or operator errors...

Having issues on one with the Touchscreen failing and having to turn the tablet screen off/on.

===============

Going over my notes I may have messed up and flashed the non-SR5 version on both...

What is the difference between the two SuperSU packages floating around?

SuperSU-v2.82-201705271822.zip

vs.

SR5-SuperSU-v2.82-SR5-20171001224502.zip

Going to go nuke two others now... and find some time to catch up on this thread...

Thx.

---------- Post added at 01:43 PM ---------- Previous post was at 12:55 PM ----------

I really have to get caught up on this thread.

Just flashed another one of mine with EV9 and while waiting for it to do it's First Boot I went back and started reading previous posts and came across this. . .

Again, thanks [MENTION=8005714]HP_TOUCHPAD[/MENTION] and All for the effort put into this.
[TouchPad General] HP_TOUCHPAD:
Thanks for the feedback, I keep the first page of this thread "guide" updated with all the latest changes and ROMs available for the Tablet. The files to flash are color coded to download and flash in the same order. It must be flash all at once with only one boot. The listed flash files in the order specified is the only way the Tablet will work properly and use the swap partition. If an older process is done from years ago and other flash files applied, the Tablet will work at its worse. Is very easy and simple, read the first page in details and if there is anything missing let me know and I will add it.
[TouchPad General] middle_road:
That's where I think I went wrong on the 11th.

I rebooted between each flash of each file.

This time around I've done them all at once as you have listed. Except for one where I reversed the Optimizer & the Reducer. Started that one over. . .