• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][OFFICIAL][9.0] Evervolv for HP Touchpad

Search This thread

elginsk8r

Senior Member
For those that don't know what Evervolv is, Evervolv is an AOSP (Android Open Source Project) rom aimed at Snapdragon powered devices. We're fully open sourced and encourage it with no restrictions. The work put into this rom is community driven and and Evervolv Project is made up of numerous members and contributors.

If you would like to contribute to Evervolv, please visit our Gerrit Code Review.

Current version: Based off 9.0 (Pie)

Features:
  • Extended PowerMenu
  • Battery %
  • Battery icon shapes
  • Volume button music control
  • Lineage Styles
  • Key rebinding
  • Expanded desktop

Bug Reporting:
Please provide the following info:
If the device was hard reboot, please provide the file "/proc/last_kmsg".
If the device was soft reboot or is "bootlooping", please run a logcat and provide the full output.
Please use EVPaste to post your logs.

Downloads:
Available downloads

Source:
Evervolv Github
Branch: p-9..0

Changelog:
Nightly changelogs are available on download page (EVUpdater too!)
or you can view them at the Evervolv Gerrit

Bug list:
  • Bluetooth (In progress)
  • Camera (In progress)

Donations:
If you wish to donate please do so here (Paypal)
 
Last edited by a moderator:

elginsk8r

Senior Member
Can't be installed with TWRP 3.1.0.
Error message is "wrong device".
Does it include swap partition (as latest DU build)?

Gesendet von meinem Mi MIX 2S mit Tapatalk

I'll investigate when I get time tonight. The swap partition is not updated yet to match DU, however the rest of the performance enhancements are.
 
  • Like
Reactions: Geomatic

HP_TOUCHPAD

Senior Member
Jan 18, 2017
1,171
488
I'll investigate when I get time tonight. The swap partition is not updated yet to match DU, however the rest of the performance enhancements are.
I was able to install the ROM using TWRP by removing the following code from the updater-script
Code:
assert(getprop("ro.product.device") == "tenderloin" || getprop("ro.build.product") == "tenderloin" || abort("E3004: This package is for device: tenderloin; this device is " + getprop("ro.product.device") + "."););
ui_print("Target: hp/hp_tenderloin/tenderloin:6.0/MRA58K/2256973:user/release-keys");
But it goes into a boot loop, it does not work.
 

elginsk8r

Senior Member
I was able to install the ROM using TWRP by removing the following code from the updater-script
Code:
assert(getprop("ro.product.device") == "tenderloin" || getprop("ro.build.product") == "tenderloin" || abort("E3004: This package is for device: tenderloin; this device is " + getprop("ro.product.device") + "."););
ui_print("Target: hp/hp_tenderloin/tenderloin:6.0/MRA58K/2256973:user/release-keys");
But it goes into a boot loop, it does not work.

what twrp are you using? im using twrp 3.2.1 from flintman
 
  • Like
Reactions: johnleo

HP_TOUCHPAD

Senior Member
Jan 18, 2017
1,171
488

shumash

Senior Member
Jun 1, 2008
1,782
2,811
Google Pixel 3
I flashed the TWRP 3.2.1-0 version and flashed the ROM file you posted.
It does not boot into Android, after selecting Android from the moboot menu it displays and active screen but black, after a minute it reboots.

That's probably because the Android uImage isn't being removed, which is what the DU uImage is named. Delete it manually and reinstall the ROM. Then you'll have the Evervolv uImage to boot.
 
Last edited:

HP_TOUCHPAD

Senior Member
Jan 18, 2017
1,171
488
That's probably because the Android uImage isn't being removed, which is what the DU uImage is named. Delete it manually and reinstall the ROM. Then you'll have the Evervolv uImage to boot.
I always test a new ROM on a complete clean Tablet, nothing in boot.
But by looking at the updater-script, that is what would happen.
Code:
package_extract_file("moboot.splash.Android.tga", "/boot/moboot.splash.Android.tga");
package_extract_file("moboot.default", "/boot/moboot.default");
run_program("/sbin/busybox", "rm", "/boot/uImage.CyanogenMod");
run_program("/sbin/busybox", "rm", "/boot/moboot.splash.CyanogenMod.tga");
run_program("/sbin/busybox", "rm", "/boot/uImage.Dirty-Unicorn");
run_program("/sbin/busybox", "rm", "/boot/uImage.Evervolv");
run_program("/sbin/busybox", "rm", "/boot/moboot.splash.Evervolv.tga");
It should removed everything and then copy the new uImage.
I did installed it manually, with the same results.

---------- Post added at 01:30 AM ---------- Previous post was at 01:28 AM ----------

So after testing and rebuilding, it looks like i forgot to push a bionic commit which is breaking libs. So when I resynced and rebuilt before uploading the commits never got pulled in
Good to know you were able to find the needle in the haystack!
 

HP_TOUCHPAD

Senior Member
Jan 18, 2017
1,171
488
This is to confirm that the new posted build of Evervolv 9, boots and works!
It also using the swap partition, is fast and smooth.
I will take more time and report any suggestions.
Thank you for providing this new ROM!
Extremely important:
If the Tablet goes to sleep or standby it will not wake up, the user may think that the Tablet is brick (is not).
A hard reset is require and the buttons needs to be hold down for long time.
I also notice from the Ramdisk files that KMS and CPU boost are enable. From my testing, those modules create more problem than the benefit it try to provide, more useful on a phone.
The idea of using the swap partition is to allow Android to place processes there without killing it or creating an unstable system. KMS is the opposite to swap it will Kill anything to make more RAM. The CPU Boost will make the CPU jump to a higher frequency only when touch, that will create double tap when typing and not an smooth user experience. Once the governor is set to performance the CPU will work just like it does on a PC, the way all computer works.
 

HP_TOUCHPAD

Senior Member
Jan 18, 2017
1,171
488
Extremely important:
If the Tablet goes to sleep or standby it will not wake up, the user may think that the Tablet is brick (is not).
User BGrosse tested the ROM and made me aware that there was not a problem wake up the tablet.
I re-tested today using the Home button, or menu button and it does wake up.

A hard reset is require and the buttons needs to be hold down for long time.
It seems as the power saving is very aggressive.
When connected to PC, when screen is off it will lose connection.
I also notice from the Ramdisk files that KMS and CPU boost are enable. From my testing, those modules create more problem than the benefit it try to provide, more useful on a phone.
The idea of using the swap partition is to allow Android to place processes there without killing it or creating an unstable system. KMS is the opposite to swap it will Kill anything to make more RAM. The CPU Boost will make the CPU jump to a higher frequency only when touch, that will create double tap when typing and not an smooth user experience. Once the governor is set to performance the CPU will work just like it does on a PC, the way all computer works.
BGrosse flashed the Pico Open Gapps and the Android Keyboard (AOSP) keeps stopping.
I can verify that is does happen with mine as well. That is an easy fix, a flash zip file can be provided to fix the issue as I do with the other ROMS.


---------- Post added at 09:38 PM ---------- Previous post was at 09:36 PM ----------

@elginsk8r
If you allow me I can apply all my settings that I have done to all the other ROMs and all should be fix.
I only need a direct link to the specific kernel version been use for this ROM, and I will re-compile a new version.
 

sireangelus

Senior Member
Dec 30, 2011
618
211
Extremely important:
If the Tablet goes to sleep or standby it will not wake up, the user may think that the Tablet is brick (is not).
A hard reset is require and the buttons needs to be hold down for long time.
I also notice from the Ramdisk files that KMS and CPU boost are enable. From my testing, those modules create more problem than the benefit it try to provide, more useful on a phone.
The idea of using the swap partition is to allow Android to place processes there without killing it or creating an unstable system. KMS is the opposite to swap it will Kill anything to make more RAM. The CPU Boost will make the CPU jump to a higher frequency only when touch, that will create double tap when typing and not an smooth user experience. Once the governor is set to performance the CPU will work just like it does on a PC, the way all computer works.
Ksm does not kill anything. Is called the kernel same page merger and it allows for any program to share common pieces of code in ram instead of creating duplicates and it has a purpose in reducing ram usage. I use it on servers and it does wonders you can run 24 VMS in the ram space of 6.in no way it's involved in the oom mechanism
 

HP_TOUCHPAD

Senior Member
Jan 18, 2017
1,171
488
Ksm does not kill anything. Is called the kernel same page merger and it allows for any program to share common pieces of code in ram instead of creating duplicates and it has a purpose in reducing ram usage. I use it on servers and it does wonders you can run 24 VMS in the ram space of 6.in no way it's involved in the oom mechanism
Correction: I double check the kernel modules and all is removed.
The wakelock settings is different and causing the Tablet not to wake up.
You are correct, is the Low Memory Killer ( LMK ) and not Kernel Samepage Merging (KSM)
Both are removed, but settings are present in the Ramdisk files, but are not active anyways.
Tested the ROM and youtube videos does not play, audio does but not the images.
 
  • Like
Reactions: Gborg3

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Just playing with my old touchpad and installed this. Is it me or is this super laggy and essentially not useable?
    It shows its age when using some apps. With the maxtreme kernel, minimal apps and light real world use it can be usable. But that usable is with an understanding of what the hardware can handle.
    1
    Just playing with my old touchpad and installed this. Is it me or is this super laggy and essentially not useable?
    it all depends how it was flashed, or installed.
    9 is set up to use a swap partition, just as webOS and every Computer Operating system ever created.
    Also how many or types of Apps are install on a fresh 9 ROM installation ( bloatware )
    Google Open Apps ( Play store ) slows down the tablet, for the many background services it uses to collect user data.
    For a 10 year old device, with great sound speakers, wireless charging , perfect screen size and the many different ROMs available, still have a lot of uses.
    The Tablet can be set up as a dedicated " specific" use device, once the App is running will perform just the same.
    Here is a video of a super installation of Google Open Apps, is a killer and not to be use this way. But it shows that it can handle it and perform.
    HP Touchpad Evervolv Pie Super Open Gapps
  • 26
    For those that don't know what Evervolv is, Evervolv is an AOSP (Android Open Source Project) rom aimed at Snapdragon powered devices. We're fully open sourced and encourage it with no restrictions. The work put into this rom is community driven and and Evervolv Project is made up of numerous members and contributors.

    If you would like to contribute to Evervolv, please visit our Gerrit Code Review.

    Current version: Based off 9.0 (Pie)

    Features:
    • Extended PowerMenu
    • Battery %
    • Battery icon shapes
    • Volume button music control
    • Lineage Styles
    • Key rebinding
    • Expanded desktop

    Bug Reporting:
    Please provide the following info:
    If the device was hard reboot, please provide the file "/proc/last_kmsg".
    If the device was soft reboot or is "bootlooping", please run a logcat and provide the full output.
    Please use EVPaste to post your logs.

    Downloads:
    Available downloads

    Source:
    Evervolv Github
    Branch: p-9..0

    Changelog:
    Nightly changelogs are available on download page (EVUpdater too!)
    or you can view them at the Evervolv Gerrit

    Bug list:
    • Bluetooth (In progress)
    • Camera (In progress)

    Donations:
    If you wish to donate please do so here (Paypal)
    7
    here you go. I'm going to recharge my device and make sure I posted the build I have running on my device.
    7
    Finally got preview and image capture from the camera in pie, looks like it was shot using a potato but its a start. now to get bt working. Will push an update as soon as im done with a round of debugging
    6
    Don't think we have forgotten about you guys. ;-P We have been busy bringing our daily devices up to snuff and learning the ins and outs of android 10. We currently are putting effort into breathing life back into this device. So far we have made some progress but nothing that is able to be tested (Not even at full boot yet). So hopefully in the coming weeks we will have something for you to play with. Don't hold your breath though, this device is fighting us tooth and nail.
    5
    new build uploaded that actually boots, swap was added as well