yashsingh1/xdaforums huggingface dataset:
[TouchPad Development] middle_road:
(3) Running 7.1.1 - (2) on Nightlies, One on TESTING.

3.0.2 TWRP

When EV 7.x first hit and I set these up, I made /system 2048 right from the start.

As I've mentioned before, mantra is 'always make it larger if you can', then you're not chasing memory gremlins.

I also set the recovery partition to 6GB. I copy all the ROMS onto it and flash from ../ttinstall with MD5 engaged.

I also have one directory filled with APPS for initial installations so I don't have to mess with Playstore straight off.

I've got a mix of ext4 and f2fs but can't remember which one is configured which way. (gotta keep better notes.)

One thing I have noticed is that under Terminal - 'DF' never shows more than 800K being used on /system.

Just checked #Three and it's showing 645560...

I haven't had any UI crashes either. Wish we could pinpoint where it's coming from.

As far as 'wiping' with TWRP for a clean install I do the following

- Factory Reset

- Reboot into Recovery

- Advanced Wipe

. - Each choice separately but NOT Micro SDCard.

Now something I find confusing is that Cache and /System still show a 'used' size under terminal of 10 & 30MB respectively.

Something else that I do is delete the Android directory on the 'external card' probably doesn't matter but feels good.

[MENTION=223188]nomad[/MENTION], as mentioned, if you feel up to it - start over from scratch with TPTB and nuke it.

I was thinking that the UI problem might be similar to the Blue Screen problem I was having on one where I finally replaced the

system board, but I don't think so. Your lockups seem to be spread out and random which hopefully is just a 'soft' problem and

not a hardware problem developing.
[TouchPad Development] crawford69:
May Give It A Try

Thanks. I may give it a try. Do you install the nightlies through Recovery or the built in updater?

---------- Post added at 03:52 PM ---------- Previous post was at 03:49 PM ----------

Sorry, I did install 7.1. Maybe my problem was that sometimes I installed the nightlies using the built in updater and other times I installed them using Recovery.
[TouchPad Development] nevertells2:
Back in the day when Sullin's was developing TPTB, to the best of my memory, someone asked if he could include a feature to increase /boot. He explained the reasons why it could not be done, but can't tell you where that might be found. Probably in his original thread if you want to read all 51 pages/900+ posts. :D

NT
[TouchPad Development] middle_road:
OK, NT, that tripped something in the ol' memory banks from back in the time of 5.x or 6.x and setting /system larger than it needed to be.

Rather foggy, but I'm thinking that is why I initially went with 2MB on 7.0. Something to do with the difficulty of resizing /system.

_Dan
[TouchPad Development] cityengineers:
Why the search bar on home screen is not working ? Or is it only me ?
[TouchPad Development] athlonxp2300:
Looks like mine was having problems with ipv6 also. No reboots since 1.07 nightly. It makes sense that it was wifi related. Mine would reboot just after getting to the home screen while the wifi was connecting.
[TouchPad Development] elginsk8r:
if you installed gapps you have to enable launcher3 widgets by clicking the gear icon in the search bar
[TouchPad Development] Sivabalan:
That's was not working finally I used tp toolbox and it worked like a charm!! Thanks.

---------- Post added at 10:09 AM ---------- Previous post was at 10:07 AM ----------

Guys which is the latest some what stable build that we can use as a daily driver. Because of the issues with the latest nightlies I flashed the test naughat build and the touchpad is some what ok.
[TouchPad Development] middle_road:
Dirty flashed r01.09 this afternoon.

While browsing device reboots randomly. Dolphin, Chrome, Opera Mini.

(perhaps the tablet doesn't care for current state of news...)

Changed to SystemMax.

Angry Birds finally ran fine, browsers still rebooting device.
[TouchPad Development] db_white:
There should be a couple of files with names that start with last_klog in the /proc directory. Last_klog is the most recent crash, last_klog3 is the oldest and last_klog2 falls in between. Start at the end of the file and read backwards. Hopefully, you'll find a common trigger (like WebView, perhaps) leading up to your reboots.

Do you get application not responding toasts, or does it just crash? Finally, what filesystem are you using for cache? I just switched mine back to ext4 and the Testing ROM "feels" more stable - even while overclocked to 1782. Too early to tell for sure, possibly placebo. I'd love to find what's making my Touchpad misbehave.
[TouchPad Development] solid.snake:
Hi there,

I didn't find any related root section into Evervolv Toolbox soft, How should I proceed please ?
[TouchPad Development] Nomad1600:
Scroll down Settings until you see #Sudo.
[TouchPad Development] YoshiFtJ:
This has been stable for the duration I have had it installed, but it is incredibly slow to do anything. What's the best way to get this thing running smoothly?
[TouchPad Development] solid.snake:
Thanks mate.

Maybe the OP should update the 1rst post
[TouchPad Development] shumash:
It's unlikely they're going to update it. They've moved to devs-base.
[TouchPad Development] elginsk8r:
Nah, we like our new home. :)
[TouchPad Development] solid.snake:
Hello there, I did update to the "today nighly", but no way to find out where is the new UPDATE section.

It used to be into parameters menu right under Toolbox menu, but I can find it anymore.

Who can help please ?

EDIT : find in into the last menu in parameters [ABOUT]
[TouchPad Development] Sivabalan:
Thanks for your reply friend. Finally used the TPTB for partition resizing and it worked like a charm.

---------- Post added at 11:34 PM ---------- Previous post was at 11:33 PM ----------

True the option was there but not functional. Finally used TPTB and it worked great. Thanks for your reply!!

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

Guys which latest nightly is stable. I faced lots of issues with latest nightlies last week and reverted to the test build. It's somewhat stable. Can someone point me to a latest build that is reasonably stable??
[TouchPad Development] rob_z11:
I downloaded the latest 7.1.1 nightly, and it is really slow even after I have bumped up the CPU Boot, and just not sure what's going on.. 1/17 is the one I have downloaded. I am going to back to 6.x version which seems to be running smooth.
[TouchPad Development] solid.snake:
Can anyone remind me how does the 6.x version handle ? Especially comparing with the 7.1.1 one
[TouchPad Development] rob_z11:
6.x is solid and runs great...
[TouchPad Development] solid.snake:
OK, got it,

Think I can flash with 7.1.1 partition size ?

Are we talking about the :

Userbuild 6.0.1 from 20/09/2016 ?
[TouchPad Development] solid.snake:
OmG !! Yes yes yes, Version 6.0.1 is ten time smoother than 7.1.1 (indeed)

I do know the dev team is working hard to make the 7.1.1 usable, but for those like me who are looking for a usable rom, I do recommand you to install the 6.0.1 immediately.
[TouchPad Development] HP_TOUCHPAD:
Nothing compares to the Evervolv 7.1.1 ROM. Is fast as anything ever install on the long lasting HP TouchPad.

With Shumash 1836KHz CPU/320MHz GPU Overclock Kernel "" it SCREAMS SPEED ""

Nothing is as fast, is amazing you can run WindowsXP, WindowsNT, Windows98 using LIMBO and it all works with no reboots, is just pure amazing.

Not all HP TouchPads are created equal and not all processor can be overclock, it depends who was the supplier. But if you got a good one, is insane.

And the camera works, using Open Camera you can do anything, is not the greatest resolution, but why do you need to see your microscopic molecules on the screen?

It just works..!

WiFi is strong and steady, no drops and far reaching!

The Devs-Base team is just amazing, for keeping this tablet alive and running as if it where brand new!

This shows that is in all in the code!

I do not have any complains, but to says a trillions thanks for all the hard work everyone has done.!
[TouchPad Development] rob_z11:
Where is this magic build of 7.1.1.. one I ran nightly from yesterday was very slowly after I overclock.
[TouchPad Development] HP_TOUCHPAD:
Go to the Evervolv Nightly Builds 2017.01.17. (All of them works) minor changes are added, look into the Log.

Get the overclok kernel ( make sure your processor can scale to the higher frequency)

Install Kernel adiutor and fine tune it to the MAX

Enjoy your Speed Demon Tablet !
[TouchPad Development] tpuserhp:
I found my touchpad was slow too under 7.1.1. I set background process limit to 4, turn off ksm and set low memory killer to very aggressive in kernel auditor. Now my device is usable.
[TouchPad Development] rob_z11:
Turn off ksm?
[TouchPad Development] tpuserhp:
Turn off ksm in kernel adiutor or in Settings-Toolbox-Performance-General.
[TouchPad Development] HP_TOUCHPAD:
99.99% of the issues are due to " US" the users that need to know too many technical details for the fast pace evolution of Android on the Touchpad.

It takes a lot of playing around and there are a lot of options to tweak, and one option or bad settings can make the tablet very slow!

My settings:

CPU max 1836MHz Minimum 192Mhz ( yes it works with no issues on low ) ( CPU Governor dancedance ) but you can change it on the spot if you want it faster !

"set all the frequency to 1836" for the others

CPU hotplug set to maximum perfomance ( touch boost ) on

GPU to max and ondemand governor

I/O scheduler Tripndroid (but it all depends of your use of the device) read ahead 2048kb if you have a 32GB 16GB 1024kb

Kernel Samepage Merging ( KSM ) ON it will reduce your memory

Pages to scan 1024 ( reduces memory usage but has impact on the cpu ( on)

Sleep between scan MAX 5000ms ( you do not want your cpu working all time, but you want it to free up memory by merging ( that is the point)

Low memory killer ( up to you ) depends the use of the device ( for only one app ) Very aggressive ( for multitasking ) light

Virtual memory ON

Entropy ( OFF)

You can make the tablet faster by also making changes to the build.pro file ( keep in mind ) the HP Touchpad is UN-BRINK ABLE ( you can always restore it ) no matter what you do to it ( that is the MAGIC !)

Do a search for all the options you can do to speed it up by modifying the build.pro

Do not use the toolbox to make changes to the CPU, only use the Kernel Adiutor. I will recommend to disable the toolbox to avoid conflict.

Also use the Kernel from shumash for optional speed !

As always do a back up of your system, before any tweaks ( it will save you time )

We all have different usage and demand from our Tablets and the devices also are different and some will perform better than others ( they are not 100 % clones )
[TouchPad Development] BGrosse:
Which is the kernel from shumash you used for that? Can you provide a link?

For me the latest 7.0 is a good one and I use it as a daily driver without problems. No need to go back to 6.x.
[TouchPad Development] HP_TOUCHPAD:
https://xdaforums.com/hp-touchpad/development/kernel-skz-overclock-kernel-evervolv-t3513534/page5?nocache=1

All the information is on the Main Page for the Touchpad on this site! and very easy to find, read the direction carefully and follow the steps.

Knowledge is power!

Your tablet will work fast and stable like a brand new device but it all depends on YOU. The time you put in to it and figure out how works, which is very easy thanks to the tools that all the developers have done and gave us thru the years.

There is no special link or software that will do all the tricks at once, but everything is out there.

This is not just any Tablet, but a very fun and useful device due to the fact that we the user have full control over it thanks to the developers for creating all the software!

Many thanks to all of them !
[TouchPad Development] fk2:
hello

Wifi version

I copied the 3 files on the pad with TP Toolbox v42 and I have an error saying "unrecognized/unsupported zip "FLINTMANN-TWRP-touch-data_media-SELINUX-f2fs-3.0.2.0-09.11.16.zip"

Tried the other version with the same issue

Any idea of what to do ?

Thanks

Fred
[TouchPad Development] HP_TOUCHPAD:
What are you trying to do?

You do not use the TP Toolbox v42 to install TWRP, it will fail.
[TouchPad Development] BGrosse:
Use FLINTMAN-TWRP-touch-data_media-SELINUX-2.8.3.0-12-23-14.zip instead (Google is your friend) and update to the 3.02.0 or 3.0.30 directly from within the TWRP 2.8.3.0 after it has been installed correctly. After TWRP updated, flash the ROM and Gapps you want with TWRP.

Use TPTP only to create the partitions with the correct sizes, install moboot and the older TWRP 2.8.3.0. Do the rest of the setup from within TWRP and you will be fine.
[TouchPad Development] HP_TOUCHPAD:
A quick trick:

1. Extract the FLITMAN-TWRP (any version)

2. Copy the file uImage.TWRP to the tptoolbox_v42 directory

3. Rename uImage.TWRP to uImage

Edit the tbtb_v42.bat file and replace:

set TPTB=TPToolbox-2014-08-10-v41.bin

to:

set TPTB= uImage

4. delete everything after goto EOP

5. safe the .bat file with any name you want

6. run the new .bat file

This will load the TWRP (any version) to memory instead of the .bin file.

Now you have TWRP loaded, you will need to installed the TWRP file, so that it will be copy to your \boot directory and you will have it as an option on your boot menu.

All credit goes to JC sullins ( the GOD Father of the Touchpad ) for creating the Toolbox, without it nothing can be done..!
[TouchPad Development] nevertells2:
The trick is you have to use a version of TWRP or CWM that Sullin's TPTB does support. It does not support Flintman's version of TWRP. If you look at post three in his TPTB thread here: https://xdaforums.com/showthread.php?t=2756314 you will see the recoveries that TPTB does support. Once you have a recovery and the Rom + Gapps installed, then you can use recovery to update to Flintman's version of TWRP. Don't forget during the install you have to increase the size of /system to what Flintman suggests or larger if you choose. Personally, I don't think increasing it to much more than what Flintmans suggests will gain you any benefit. Also, if you install the smaller version of TWRP that Flintman created, you should be able to put TPTB in /boot so you can run it from there.

NT

---------- Post added at 02:19 PM ---------- Previous post was at 02:18 PM ----------

Not quite sure what it is you are trying to do here. Can you explain please.

NT
[TouchPad Development] HP_TOUCHPAD:
The tptb_V42_win.bat ( is a windows batch file )

It will load TPToolbox-2015-01-08-v42.bin file into the Touchpad memory.

This is the same as the following novacom boot command:

novacom boot mem:// < uImage

When the touchpad is connected using WebOS Recovery you can run: "In windows command prompt"

C:\Program Files \Palm, Inc>novacom boot mem:// < (place any uImage file name here) and it will be load it into memory and boot, without copying the file to the boot directory of the touchad.

This will work with any uImage that is design for the touchpad.

I think that it will be very helpful to include this command on any recovery method, you can load any version of backup and recovery at any time even if is not in your touchpad boot directory, or if you have it full and won't let you copied any more boot images.

You can run any backup and recovery , "webOS Recovery" once is connected to any PC with novacom drives install, that way you can have in your boot directory the boot images for WebOS, LuneOS and Android. (Yes I do use all three OS install on one Touchpad).

Is a very powerful simple command that it will load anything without having any footprint on your /boot directory.

Corrections: You run the novacom.exe that is in the Palm, Inc directory on a windows PC with the command " boot mem:// < uImage ( the uImage needs to be in the same directory as the novacom.exe program.
[TouchPad Development] nevertells2:
That's a handy trick. Fortunately, Flintman did create a version of TWRP that is small enough that there is enough room in /boot to allow the TPTB uImage to be copied into /boot.

NT
[TouchPad Development] HP_TOUCHPAD:
There is plenty of space in boot directory for two separate boot "uImage" version of Android and a full size TWRP (backup and recovery).

The novacom boot mem:// < uImage command is very handy to load anything regardless of what is on your boot directory.

You can run anything without install to boot, possibilities are endless!

It should also be advice to users ( if they have access to a computer ) for simple steps to install a recovery for the first time.
[TouchPad Development] nevertells2:
So to continue this discussion so it is clear for me and everyone else, once you have modified the bat file, connect your TP to your PC, boot the TP into WebOS recovery and run the batch file from the command window. After the script runs, next thing you will see is which ever version of TWRP, named uImage, you have in the same folder with the batch file. I doubt WebOS would run to well since all the supporting directories, files and such are not on the TP. All those were removed during a complete data reset. Anyway, once a recovery is running via this method, one could then use it to install their recovery of choice.

Thinking out loud, I'm trying to figure out what situation someone would find themselves in that using this would help them out with. If I have already used TPTB to install Moboot, a recovery, Rom and Gapps, and I want a different recovery, I can just use the current recovery to flash the different one. And like I suggested to fk2 above, there are versions of CWM and TWRP that will work with TPTB. Thanks

NT
[TouchPad Development] HP_TOUCHPAD:
nevertells2; So to continue this discussion so it is clear for me and everyone else, once you have modified the bat file, connect your TP to your PC, boot the TP into WebOS recovery and run the batch file from the command window. After the script runs, next thing you will see is which ever version of TWRP, named uImage, you have in the same folder with the batch file.

Correct you will see and be able to use any recovery regardless of version or type.

I doubt WebOS would run to well since all the supporting directories, files and such are not on the TP.

You do not need WebOS to load any uImage into memory using the novacom command or the toolbox script.

All those were removed during a complete data reset. Anyway, once a recovery is running via this method, one could then use it to install their recovery of choice.

The user has an option to do a complete data reset or keep WebOS. You can always install WebOS at any time. LuneOS runs inside WebOS at the moment.

Thinking out loud, I'm trying to figure out what situation someone would find themselves in that using this would help them out with. If I have already used TPTB to install Moboot, a recovery, Rom and Gapps,You will need old version and I want a different recovery, I can just use the current recovery to flash the different one. And like I suggested to fk2 above, there are versions of CWM and TWRP that will work with TPTB. Thanks

The Toolbox can not install a new version of TWRP, ROMS or GAPPS becuase it has not been updated and there is no need for it, is great at what it does except install new versions of Android. I think that the option should have only been ( Install a recovery and let the recovery do the installation of Android.)

No need to look for old versions to get a new one install, that is the idea
[TouchPad Development] RrNr:
No keyboard issue after boot for me. Camera is working, but it's upside down when taking the picture. Is right side up when viewing it afterwards.

Small run down of what I did:

1. Installed Novacom on PC

2. Launched TPToolbox-2015-01-08-v42

- Complete Data Reset

- Install Android

- - > Copied Files: FLINTMAN-TWRP-touch-data_media-SELINUX-2.8.3.0-12-23-14.zip ---- cm-13.0-20160722-UNOFFICIAL-tenderloin.zip ---- gapps-601-base-20160606-1-signed.zip to ttinstall

- At prompt before Installing selected to Resize Android Volumes

- - > Freed up Media to so I could allocate to other volumes (left 1040 for NewSize)

- - > cm-cache 200

- - > cm-data 27008

- - > cm-system 1536

- APPLY Changes for Volume Resizer

- Continue Android Install

3. After Reboot, don't allow it to boot in to Android, boot to TWRP instead

4. Flashed FLINTMAN-TWRP-touch-data_media-SELINUX-f2fs-3.0.3.0-12-22-16.zip in TWRP

5. Still don't boot to OS, Reboot to TWRP again

6. Wipe

- Advanced Wipe

-- > System Only

7. Flashed ev_tenderloin-7.1.1-nightly-2017.01.20.zip and open_gapps-arm-7.1-pico-20170121.zip

8. Reboot to Android
[TouchPad Development] HP_TOUCHPAD:
Camera is working, but it's upside down when taking the picture. Is right side up when viewing it afterwards.

As mentioned by Flitman from Devs-Base page:

The camera preview is upside down, takes pictures but pixing is off ( camera works perfectly using Open Camera )

Camcorder does record, just can't playback with stock player. it works with MX player
[TouchPad Development] rob_z11:
I mean, all of the hacks, it is usable for 7.1.1, but I wonder if it is as smooth as 6.x? Thanks to dedicated people here, this tablet is relevant still after out for so long.. Best Money I have spent..
[TouchPad Development] middle_road:
Not sure what I did to achieve this and your mileage will vary.

I had Tablet #One sitting on my side desk, kinda forgot about it, been dinking with the other two.

There's r01-04 flashed on it, and it been sitting since noon on the 18th.

Battery today at noon is at 67% ... It must have gone into stasis or something.

The other four - if I leave them for a couple of days attended, are usually dead.

One oddball thing that keeps happening is that my selection for wallpaper doesn't stay on all three that are running v7.x

It's always reverting to the Miami Vice colored image. I have one flashed with r01-17 and the wallpaper is black, no image.

I probably messed things up installing Nova Launcher. Heck I probably have messed up more than that... :cool:
[TouchPad Development] shar88:
Is there enough space for moboot, twrp, TPTB, and evervolv?? I have TWRP 3.0.2.0 from the 11th (smaller one), TPTB uImage already copied to /boot and when I was trying to install this rom it keep saying checking uimage..... invalid size boot failed. (This was first week in Jan)

I do have other stuff that I didn't put there, bin, etc, lib, lost+found, and usr folders and some tga files. Can I nuke everything but the moboot and the uImage* files?

lib and lost+found are emtpy, etc and usr have lvm files, and bin normal bin files.

(note, theres currently a uImage.cyanogenmod cause I flashed it after evervolv failed to boot cause of the invalid uImage size)
[TouchPad Development] udownwitopp:
Chrome seems to really slow on this, using the puffin browser solves that problem for me.
[TouchPad Development] geddy3:
Wallpaper is an issue, sounds like the devs are working on it according to the other forum.
[TouchPad Development] HP_TOUCHPAD:
The size of the BOOT directory after a total reset using the toobox is about 1.9 Megabytes (18 files) you do not need to delete anything else. The total capacity of the boot directory is about 30 Megabytes. So 30 Megabytes minus 2 Megabytes from the basic install, you got 28 Megabytes free that you can copy anything there. You can copy any image into the boot directory at any time, you do not need to have everything there as you will not need to load it every time. There is space for all of that TPTB 10, TWRP 9, Evervolv 6, total 25 Megabytes out of 28. You can remove any images but no directories.

---------- Post added at 04:36 AM ---------- Previous post was at 04:32 AM ----------

The first thing that I do is to select no wallpapers and never had any issues. Why load unnecessary images to take resources and memory it will make the tablet slower?

Every single bytes count.!
[TouchPad Development] middle_road:
Looks the same as mine except for the cyanogenmod.

Wipe /system & Cache in recovery and try reflashing EV...

I received the 'invalid' message before and just reflash and then success.