yashsingh1/xdaforums huggingface dataset:
[TouchPad General] raimerik:
Hi [MENTION=8005714]HP_TOUCHPAD[/MENTION] !

Thanks for your directions. I really appreciate them!

I spent the last 3 hours following them and kept on smiling (while researching ALL xda) about something I teach my students as the expert(ise) bias - how much we tend to forget how much we've learned over the years in order to become experts which we consider as our status quo... ;)

So, although I'm in Android Custom ROMs since 2011 I tend to start from scratch because I just tinker with a device once or twice a year and my expertise fades.

Therefore I want to document how I followed your instructions - maybe it will help others:

1. Use the ToolBox: Wipe all , data reset. Create WebOS volumes (partitions)

>>> I got the ToolBox and the NovaCom drivers from this post: https://xdaforums.com/showpost.php?p=52765126&postcount=2

2. Using the ToolBox, create Android partitions and create /system to be 1400mb or higher not need to be more then 2G.

>>> I got the partition sizes from https://xdaforums.com/showpost.php?p=78642584&postcount=125 and/or https://xdaforums.com/showpost.php?p=78942675&postcount=1

3. Install WebOS if you know your way around Install the app Tailor to create LuneOS partition or must be created manually.

>>> This is where the researching ALL xda started due to a lot of outdated links and threads... Lots of open variables: webOS doctor versions / no more online registration and all

>>> So right now I used a webOSdr JAR of v3.05 from here: https://xdaforums.com/showpost.php?p=52922166&postcount=64

>>> after that I used the offline installation found here: https://xdaforums.com/showpost.php?p=63104423&postcount=23 (download link: 'Note:WebOS activation with instructions here' )

4) Install the unzipped TWRP 3.1 (=uImage.TWRP) from the first post of this guide by putting the file in the NovaCom Folder and entering the following into the NovaCom-Console:

novacom boot mem:// <uImage.TWRP

(thanks for https://xdaforums.com/showpost.php?p=79236813&postcount=128 )

5) Install (DU) Android + open Gapps (pico) + Keyboard + SKZswap1728000 (as layed out in the first post) [+ Wipe Cache/Dalvik +Reboot System]

ToDos / WorkInProgress:

5b) Install moBoot in order to have a boot menu to switch between webOS + Android + TWRP?

6) Tailor-installation

7) Install LuneOS (The partition must be already created, or look at my guide for LVM how to create one) >>> research the recommended partition size and luneOS-installation-guide

8) If you want create a 2G Linux partition >>> I'll keep this for another project... ;)

Again, I like this although it can be frustrating. Therefore this is for documentation not for whining or asking others to do my work...

Cheers! raimerik
[TouchPad General] HP_TOUCHPAD:
[MENTION=5373375]raimerik[/MENTION]

It is way more simple that all those steps and basically not necessary. All those tools are for general users and to make it easier to do for everyone.

If you are familiar installing any Operating System (OS) on any Personal Computer (PC) then this is just the same.

The first step before installing the OS, is to properly partition the Hard Drive (HD) or the storage.

In the PC is done before the installing the OS at start up, there are options on how and how much space the user wants to allocate to the new OS been install. In Android as is a Mobil device that step is not available, because is not need it, is a smartphone and there is no options to install any other OS besides what comes with the device.

The HP Touchpad is exclusively unique, one of a kind.

1. The Tablet uses Logical Volume Manager (LVM)

2. Different OS are available to install (WebOs, Android latest (PIE), LuneOS, Sailfish, different Linux flavors and who knows of how many more custom OS are in the wild !

3. Is a portable Linux mini-laptop

The only step need it to master all is to know how LVM works, which is the volume (partition) manager. This is standard now days in all Linux installation and Servers, it is extremely powerful.

I explained in my guide the basics of LVM, all the information is available in the internet.

Once you know how to partition the internal storage then you can install any OS as the layout is already configured properly and the only thing to do is flash the ROM.

I wrote all the code for LVM on my guide:

The most Powerful Feature of the HP Touchpad (LVM)

That is the only thing you need to partition everything on the HP Touchpad.

Shumash provides this zip file for WebOS that has it all:

Click here for Shumash HPTP WebOS essentials.zip

Is basic and simple, the only thing that makes it confusing is LVM which is used by Linux Servers and not Mobile devices. That is the missing link !

Learn LVM, configure the HP Touchpad and everything after that is just a flash!
[TouchPad General] raimerik:
See - this is what I mean by expert(ise) bias... ;) We are on different planes of expertise that you can't even imagine (anymore). I'm looking forward getting into LVM one day, but right now I'm struggling with profane troubles like:

a) getting TWRP 3.1 onto my factory reset TP in order to follow your guide here. It won't 'stick' after installing it following this (most up2date guide? - Step IV): https://xdaforums.com/hp-touchpad/general/rom-guide-alternative-method-to-install-t3575861

So I wonder if I can install your 4 zips from this thread (DU + GA + Keyboard + SKZswap) with the TWRP 3.0 from 'doublestuff_v03' ?

b) Figuring out if or what version of MoBoot is compatible with these up2date TWRP and ROMs and how to install it. Installing-MoBoot is not mentioned at all in the most recent guides anymore.

c) After a+b figuring out how to get TAILOR onto my TP in order to prepare a LuneOS-partition

See? I like this kind of research / 'sherlocking', but it's hard for experts to see what way they've come and which steps they had to learn because they were not trivial (before learning them - thus making them seem trivial after you have the expertise but forget how it developed)... ;)

Again, not to whine, just to share perspective. ;)

Cheers! raimerik
[TouchPad General] HP_TOUCHPAD:
@ raimerik

To load any version of TWRP to any HPTP (HP Touchpad) is very simple by doing the following.

You must have a PC with the Palm novacom driver install.

The Palm novacom driver is what communicate to the HPTP using USB.

Download TWRP 3.1 from the Guide, Click here.

1. Unzip the TWRP 3.1, the file that is need it is uImage.TWRP

2. Set the HPTP into Recovery Mode:

If the Tablet does not have moboot 0.3.8 or it has WebOS only then do the following:

The HPTP can not be connected by USB at this moment:

Press Power button and the left Volume Key (closer to the Power button) at the same time, hold both until a white USB symbol shows up.

3. The HPTP is now in recovery mode, now connect it to the PC by USB.

4. To find out if the novacom drivers are properly install and working, Click here for details

On a terminal window (command prompt) enter:

novacom -t open tty://

((then press enter and type))

help

(( you get a command list )) now close the terminal window.

That shows the HPTP is recognized by the PC and the novacom drivers are working.

5. Load the TWRP image into the HPTP by opening a terminal window (command prompt).

Enter this command:

novacom boot mem:// <uImage.TWRP

(((press enter)))

The novacom loads the TWRP into the HPTP memory and boots from there. At this moment TWRP is only in RAM and not install.

6. Now TWRP 3.1 is loaded and the Wipe All to create Android with Swap partition from this guide can be flash.

It will re-create /boot and also install TWRP 3.1 in it, is all done.

Less confusing steps:

Place HPTP in Recovery mode

Enter this command in PC:

novacom boot mem:// <uImage.TWRP
[TouchPad General] raimerik:
Hi [MENTION=8005714]HP_TOUCHPAD[/MENTION] !

Still working through my 'Beginners' Guide To Reset A TouchPad To New Glory'... ;)

I hit a brick wall because my reset-to-webOS-default-TouchPad would not let me install Android although I had manually set the partitions with ToolBox... (although the guide said: "WebOS has the swap partition and it can be share with Android, there is no need to Flash the file Wipe_All_and_Create_Android_with_Swap_Partition." )

So for more tinkering-enlightenment I tried your WIPE-file and was pleased to see that it installs moBoot + TWRP 3.1 on the way... Great.

One feedback for you: the LVM-command (step15 of instructions.gif) would not work for me - 'not supported' or similar... Or is it a different command than LVM (within the TWRP-Terminal)?

And would you have (by any chance) a WIPE-file that sets up the partitions while leaving a freshly installed webOS alone = unharmed (if this is possible at all I don't know)?

And is it normal that ToolBox won't show the swap-partition after the WIPE-file-execution? It just shows:

media 504

cm-cache 200

cm-data 11488

cm-system 1848

Last, where in your 4 steps would you install moBoot 0.3.8 and TWRP 3.1? Between steps 3 and 4? (And would you happen to have a 'WIPE-file-version' installing both of them without wiping anything else?)

1. Use the ToolBox: Wipe all , data reset. Create WebOS volumes (partitions)

2. Using the ToolBox, create Android partitions and create /system to be 1400mb or higher not need to be more then 2G.

3. Install WebOS

4. Install Android

Cheers! (and let me know if this becomes annoying) raimerik
[TouchPad General] HP_TOUCHPAD:
They are great questions ! thanks for taking the time to follow the guide and learn!
[TouchPad General] raimerik:
Cheers again for taking your time and clarifying some misunderstandings!

I was under the impression that installing Android onto a freshly reset webOS-System could not be done via ToolBox, because it was 'outdated'... So I found myself between a rock and a hard place not being able to install moboot and thus not being able to install a dual-boot system with the recommended DoubleStuff-method...

I ended up with manually renaming and copying uImages follwing an obscure video ( https://www.youtube.com/watch?v=YMlFY2kz4gc ) - what a ride. ;)

So before writing up my beginner's step-by-step protocol I'll try out setting up TWRP3.1 manually before installing Android9 via ToolBox as you suggested. Another go.

Thanks for the LVM-commands! I literally entered LVM into the terminal windows, not knowing better (or literally following the GIF)...

After that: entering the world of installing TAILOR onto webOS which does not trivial to me yet... ;)

Cheers - you save my sick week lying in bed and recovering while tinkering with TouchPads - occupational therapy...

raimerik

PS: tried your LVM-instructions (enter TWRP > mount boot > goto Terminal > cd /boot/usr/bin > ./lvm.static lvs) and got lots of 'file descriptors' errors 'leaked on lvm.static invocation' and no results... :(
[TouchPad General] HP_TOUCHPAD:
The WebOS partitions will not show using this process. To see all the partitions of WebOS the commands must be enter into a Terminal inside WebOS or when connected to PC.

The ./lvm.static lvs will display the partitions after Android was created by the ToolBox or the Wipe All file has been flashed from the guide.
[TouchPad General] Kamiccolo:
Heyo

I've been running cm 4.4.4 for a long time now on this hp touchpad and it works great and fast. Along time ago i upgraded to 7.1 and the tablet ran horribly.... like literally snale cant even play hearthstone on it which would play like nothing with 4.4.4. Saw this this month and gave it a try. Install went perfect and everything booted fine but its even worse than 7.1. Hearthstone wont even launch or does after forever and then crashes on the 1.7ghz..... i could even play ff9 on 4.4.4 no problem but on this it literally insta crashes. Surfing the net is horrible takes forever to load anything just seems insanly bogged down.... ive tried alot to get it running like 4.4.4 but something about the operating system is just not compatible i think or im just dumb lol. Im going back to 4.4.4 because my tablet is literally almost useless running this version. If anyone has the same experience as me and has gotten 4.4.4 performance on 9.0 please let me know. I followed steps perfectly but it just seems to hate it lol. Thanks guys and awesome job on the installation really epic and smooth!!
[TouchPad General] Kamiccolo:
Hey everyone so i tried both versions now 7.1 and 8.1 with every different skz including the stock ones. All versions crash when trying to play ff9 or hearthstone. I even underclocked and changed voltages literally every setting possible and nothing stops it from crashing. Having the swap file or not dosnt matter or stock kernel or skz kernel 1.7ghz. Ive underclocked the gpu to stock nothing works to keep either of these builds stable. I really need some help here as it seems only cm11 4.4 nightlies and jcsullivans works fine and does not crash on heavy load. I actually think it is the 3.4 kernel in general that it causing this as no matter the overclock or settings it crashes. If anyone here has experienced this please lend a helping hand. Thanks everyone for your time.
[TouchPad General] Lister Of Smeg:
Hi [MENTION=8005714]HP_TOUCHPAD[/MENTION],

Apologies for the delay getting back to you, been a bit tied up recently... But just wanted to say THANKS for all your super advice and help in the various Touchpad posts. I've finally got around to picking my Touchpad up, and was curious about flashing one these Swap partition kernels. As apparently I don't need to do any wipes as such, as you said because I already have WebOS, I must therefore have the 400MB default partition.

However, I was hoping to try and expand this partition to 500MB.... But don't really want to lose my WebOS setup, or my /Boot partition with the various uImages setup.

I've tried to have a look in WebOS Tailor, or booted the uImage.Toolbox to resize the Android partition, and hoped to find SWAP in there....

I've already set my system partition up, from when I first setup Android.... and my Android volumes are as follows (according to HP Toolbox).

Partition - Size - Used - Free

Media - 11800MB - 472MB - 11328MB

CM-Cache - 256MB - 8MB - 248MB

CM-Data - 14080MB - 8944MB - 5136MB

CM-System - 2056MB - 872MB - 1184MB

So was just wondering, do I need to do anything to my partitions, or do I still have the 400MB default swap partition, just it's not visible under most apps...?

Is it just a case of finding the correct SWAP ramdisk kernel, depending on my current version of Android ??

/ sorry for being a pain... ;) all help gratefully appreciated !! :)

Thanks, Lister
[TouchPad General] HP_TOUCHPAD:
Android 7.1.2, 8.1 and 9 works with the help of the swap partition by allowing to free more memory to run Apps.

I am in the process to update all the flashed files to provide even better performance and Hearthstone will play on all.
[TouchPad General] HP_TOUCHPAD:
You are very welcome, the more questions the more we all learn. The pain comes when ignorance controls your intelligence.
[TouchPad General] shumash:
https://en.wikipedia.org/wiki/Android_Runtime?
[TouchPad General] HP_TOUCHPAD:
Google can change the Runtime to keep avoiding paying license feeds to use Java, but the code still execute in a Virtual Machine, is not running natively in Android. Anyone can easily test this and see the difference immediately.

Change the numbers on the following settings in the build.prop and then apply chomd 644

dalvik.vm.heapstartsize=

dalvik.vm.heapgrowthlimit=

dalvik.vm.heapsize=

low numbers will make the Tablet useless

higher numbers faster but Apps with high memory usage will crash.

By the way I have merged your Skz CPU and GPU frequencies into the stock kernel of Pie ( 9 ) and it works with no issues.

Are you planning to release a version of Skz for Pie or can I post the Hybrid Kernel?
[TouchPad General] shumash:
My point is that it's Android memory management that's the issue, not dalvik, which is deprecated. My code is open source, do what you want as long as proper credit is given.
[TouchPad General] Kamiccolo:
Hey everyone

So i tried the heap sizes.

Changed from 256 to 128 and 48 to 64 half and ff9 still crashes.

Changed from 250 to 512 and 48 to 256 half and android will no longer boot.

So far i still have no idea why this is happenening and cannot get stable with anything other than jcsullivans... seriously bonkers. That was with install using f2fs as well on 1728 kernel. I think im gonna flash back to kit kat and record all the devlik setting and copy them over. If this sounds like a good idea let me know so im not just wasting time. 6th flash trying to get this to work...
[TouchPad General] Kamiccolo:
Ok so on jc sullivans 3.0 4.4.4 kitkat the setting for heapsize and everything are the same... so it must be how much memory the tablet is using in general then. I dont know but nothing works on not allowing me to run apps stable like on kitkat even with same overclocks.
[TouchPad General] shumash:
DU

EV
[TouchPad General] HP_TOUCHPAD:
I am posting today complete new Kernel optimize that will provide maximum performance and RAM gain. It will be extremely easy to follow, the only thing to do is just flash the files an all will be fix !
[TouchPad General] HP_TOUCHPAD:
It is very frustrating, trust me I have done over a trizillons of reboots to figure it out. Yes it is RAM but specially in the build.prop there are settings that makes the device slow to conserve power. All the settings are to be use on an Smartphone making the Tablet useless. To have the Tablet working as it needs to be a laptop with a touchscreen is not to add any settings, besides the swap partition. Is to removed a lot code that has been added since 2012 that are not need it. You will see it today with my new post.
[TouchPad General] HP_TOUCHPAD:
Thank you for taking the time and update your kernel to 9, this are my comments:

It does boot and works, even have access to the SDcard.

I have made changes to the swap settings that will improve performance, is only on the Ramdisk and can easily be added.

But this modules are still active on the Skz kernel and are not available anymore on the Stock Pie Kernel by Flintman and that is what I have done all my testing and performance with. Attached are the screen shots of the settings that are still active, plus the 3D GPU settings are not set to full frequency.
[TouchPad General] shumash:
That's because I'm not defaulting to your settings. It's still up to the user to decide what they want. They can easily set those parameters with Kernel Adiutor or any other kernel tuner. Not everyone considers particular parameters as "optimized". Your's are for video performance; personally, I set mine for battery life. Different strokes for different folks.
[TouchPad General] shumash:
two
[TouchPad General] HP_TOUCHPAD:
I do believe in options and the ability for anyone to make decision based on their needs. That is why the HP TP is very special it can be set up any way you want it.

But Android is specifically designed for Smartphones with settings that only apply to the use of conserving battery to make sure you can make that emergency phone call at the last minute. In the PC or Laptop environment is the opposite, the software and settings are to get the most of the hardware by overclocking as your Kernel for the best user experience forgetting about battery as there is a power cord and outlet everywhere. In my opinion the HP TP is a portable laptop that needs to be charging all the time when not in use. Provide the fastest performance when the user needs to use, if battery time is a concern then get a portable DVD player and buy DVDs to see anything and keep the Tablet for light use. The ironi to all this, Smartphones now have 8 cores, massive DPI with more RAM than a Desktop, but then all the tools and tweaks are to get the most battery life and that is reducing performance, why have all that processing power when it needs to be slow down?

The settings that I am suggesting and provided are nothing more than ( NO SETTINGS ) is removing all the Tweaks and nonsense of getting more battery by reducing the performance of an old device that is been choke on restrictions. By installing more Apps design to give more battery to Smartphone like Kernel Adiutor is creating more problems with a 1GB RAM device. None of those settings will make the tablet faster, it will reduce performance and have the user figuring out why video can not play.

Once the tablet is on standby (press the power button) the battery consumption is the same regardless if the CPU governor is set to Performance and maximum frequency.

I am only giving my suggestion to avoid confusion, DU v13 Android 9 has all Kernel features removed and using the swap partition as default, is how PCs and laptops has always worked and are been use now. But if you want to offer an Overclock Kernel to conserve battery and reduce the processing potential of the Tablet it is fine, just make the user aware .
[TouchPad General] shumash:
Well reasoned. Like I said, different strokes for different folks. I'm not going to debate. Use my kernel, don't use it, whatever.
[TouchPad General] HP_TOUCHPAD:
We are here to debate in a positive constructive way, to share our point of view and provide options. Nobody is right or wrong, but two brains think better than one and that is part of a debate. The Kernel and Ramdisk provides 90% of all the settings as you know I have posted guides on how to do it all, but is confusing and asking too much for a regular user to do, the best we can do is provide the users and easy way to use the Tablet to its maximum capabilities and at the same time is a learning challenge on how to get things working on a extremely low antiquated resource device by today's standard.

Look I had to learned how to play this game, ( I am not a gamer) just to prove that Android 9 with a swap partition with my suggested and posted settings works.

Click Here for How to Play HEARTHSTONE® by Blizzard Entertainment on HP Touchpad
[TouchPad General] shumash:
You seem to have all the answers. One world, one way. My stuff is gone, as am I.
[TouchPad General] HP_TOUCHPAD:
I think out of the BOX and those that like to be contained inside six WALLS will see me as a threat, but I only want to set them free.
[TouchPad General] MasterDebater2:
You two should GROW UP

I hope that you two "senior members" figure out who has the bigger manhood. Meanwhile you have both done this thread a disservice as well as the HP Touchpad community with your pathetic and immature little p'ssing contest. Shumash's immaturity to the point of taking his ball and going home while deleting his two kernels from this thread, and apparently all of your comments from his threads and then you for doubling down on stupid in your little contest. Thanks from all of us.
[TouchPad General] HP_TOUCHPAD:
For the record, there is no issues between Shumash and myself, we have always communicated that way and is good that we think differently.

In regards to MasterDebater2, a new member just now, but has been an XDA member for many years ( that is how knows what is going on), just keep your Police expertise to yourself and open your own THREAD about regulating people's different point of view.

To all members, this type of Drama is not part of the HP TP optimization just ignore it.

More ROM are coming with the provided settings!
[TouchPad General] MasterDebater2:
Yeah, no issue between you two at all.... Which is why he basically told you to F OFF, deleted his two kernels, and deleted all of your posts from his threads. Well, there is obviously a problem now. And as for my 'new' id yeah, I didn't want to take the chance of losing my old id when if I was so inclined to tell you to f*u*ck off. And the funny thing is at first I thought Shumash was the one making an issue where there was none. Now I realize that you are the as*sh*ole and he was right to break off from you and your pathetic crap.

Then this "To all members, this type of Drama is not part of the HP TP optimization just ignore it." From YOU, THE VERY PERSON CREATING THE DRAMA... GO F YOURSELF