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

[elginsk8r]

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)

 

[Geomatic]

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

 

[elginsk8r]

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.

 

[HP_TOUCHPAD]

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

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]

I was able to install the ROM using TWRP by removing the following code from the updater-script

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

 

[HP_TOUCHPAD]

what twrp are you using? im using twrp 3.2.1 from flintman

The TWRP version I am using is 3.1.0-0 from Flintman from here:
http://downloads.codefi.re/evervolv/misc
The ROM install after removing the verification for the device, but it won't finish booting not even the animation starts, then it reboots again.
Can you provide the link to the TWRP 3.2.1 from Flintman?

 

[elginsk8r]

here you go. I'm going to recharge my device and make sure I posted the build I have running on my device.

 

[HP_TOUCHPAD]

here you go. I'm going to recharge my device and make sure I posted the build I have running on my device.

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.

 

[shumash]

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.

 

[elginsk8r]

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

 

[HP_TOUCHPAD]

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.

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]

Here are the settings that I have applied to get the most out of the Tablet, is very basic and simple if you decide to incorporated into your ROM it will be as fast and stable as the current DU v13.
The Boost Optimize settings for all Android ROM ever created for the HP Touchpad

 

[elginsk8r]

new build uploaded that actually boots, swap was added as well

 

[HP_TOUCHPAD]

new build uploaded that actually boots, swap was added as well

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!

 

[HP_TOUCHPAD]

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]

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.

 

[44quattrosport]

Not tested now, but thank you!

 

[androfanatic]

thanks a lot for the rom

 

[sireangelus]

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]

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.