Ok thx man.Just download the apk from some of apkmirror or some of the other sites. Yes the tablet runs much faster without the gapps.
Ok thx man.Just download the apk from some of apkmirror or some of the other sites. Yes the tablet runs much faster without the gapps.
Youtube or using bromite browser works on all ROMs with no green screen.
Make sure you are using the latest youtube App or Browser.
Select the correct open gapps and use the latest:
https://opengapps.org/
Also it can be tested by downloading bromite web browser apk to PC then install on Tablet:
https://www.bromite.org/
Thanks for verifying that it works !video plays well on bromite although I don't like the fact it is about 90Mb in size ... I have been trying to use very lightweight apps (like via as browser which is very small)
Thx for the explanation and overall your work on hp touchpad. It is indeed a forever tabletThanks for verifying that it works !
Bromite is based on chromium, is a full feature web browser.The App installation size does not matter. It needs to have all the resources to make all work. The Android system partition of the Tablet after the Automatic_Wipe_All is 2.2 GB in size which provide enough space for any app to be install, there is nothing to worry about running out of space in system partition. The installation size does not mean it will use the same space in RAM, installation size will be even more, but it provides all the files and resources to make it work. One of the reason the Tablet has survive for so long is due to the use of LVM : Logical volume management.
The size of the internal storage can be set to accommodate any Android installation size requirements.
For example, there were better devices with faster components that the tablet, but the system partition size could not be alter, making it impossible to resize and preventing the use of any ROM after Android 5,6 or 7.
The Tablet survived because the system partition can be change. So even 50 years from now, apps needs a bigger system partition size, it can easy be change to any size to the maximum of about 15 GB for the 16 GB model, so still can be use.
At the moment everything is moving to the cloud and devices are becoming just a terminal with a touch screen, even the operating system will run from a server and not on the devices, it is done now.
Enjoy your forever Tablet !
You are very welcome!Thx for the explanation and overall your work on hp touchpad. It is indeed a forever tablet. What rom do you use btw?
molotov player. DRM on 7 doesn't work on 9.Why is Evervolv 7 being used over Evervolv 9? Also why are you using a browser for YouTube over Newpipe, YouTube Vanced, or just the YouTube app? EV7 and EV9 both do not seem to function correctly when trying YouTube in a browser. It closes the stock browser and OH Browser without a pop-up or anything. Luckily the YouTube apps work with no real issue.
To enable higher frame rate, is part of the individual App not the ROM.
The boot partition was created with the basics to get everything working and provide
enough storage to accommodate:
TWRP/Recovery 3.2, each of the listed ROMs from Kitkat to Pie and the ToolBox.
The size of /boot is 32MB, is a fix size and can not be expanded.
Boot partition details after Automatic_Wipe_All:
Directories: size file name
bin 647.5k busybox
etc 16.1k lvm.conf
lib
lost+found
usr 1.2M lvm.static
Files: size
android.default.recovery 9 bytes
uImage 13 bytes (link to uImage.moboot )
uImage.moboot 63.8 K
uImage.Recovery 10.6 M
Total:
/dev/block/mmcblk0p13 size used available Use %
32.0M 14.1M 17.9M 44% /boot
A clean /boot has 17.9M of free space
Free Space After Pie ROM
/dev/block/mmcblk0p13
32.0M 20.8M 11.2M 65% /boot
The ToolBox is 11.2M
After flashing the ToolBox
/dev/block/mmcblk0p13
32.0M 31.6M 395.0K 99% /boot
There is only 395.0k available.
/dev/store/swap none swap defaults swapprio=0, 0 0
on boot
# Define TCP buffer sizes for various networks
# ReadMin, ReadInitial, ReadMax, WriteMin, WriteInitial, WriteMax,
setprop net.tcp.buffersize.default 4194304,5242880,6291456,4194304,5242880,6291456
setprop net.tcp.buffersize.wifi 4194304,5242880,6291456,4194304,5242880,6291456
# Assign TCP buffer thresholds to be ceiling value of technology maximums
# Increased technology maximums should be reflected here.
write /proc/sys/net/core/rmem_max 6291456
write /proc/sys/net/core/wmem_max 6291456
# system server cannot write to /proc/sys files,
# and chown/chmod does not work for /proc/sys/ entries.
# So proxy writes through init.
on property:sys.sysctl.extra_free_kbytes=*
write /proc/sys/vm/extra_free_kbytes 20480
# write /proc/sys/vm/extra_free_kbytes ${sys.sysctl.extra_free_kbytes}
on fs
# Enable swap partition
swapon_all /fstab.tenderloin
on property:sys.boot_completed=1
# Swap Partition Settings
write /proc/sys/vm/block_dump 0
write /proc/sys/vm/dirty_background_bytes 0
write /proc/sys/vm/dirty_background_ratio 10
write /proc/sys/vm/dirty_bytes 0
write /proc/sys/vm/dirty_expire_centisecs 600
write /proc/sys/vm/dirty_ratio 20
write /proc/sys/vm/dirty_writeback_centisecs 600
write /proc/sys/vm/drop_caches 3
# change in ramdisk init.rc write /proc/sys/vm/extra_free_kbytes 20480
write /proc/sys/vm/highmem_is_dirtyable 0
write /proc/sys/vm/laptop_mode 0
write /proc/sys/vm/legacy_va_layout 0
# write /proc/sys/vm/lowmem_reserve_ratio 32 32
write /proc/sys/vm/max_map_count 65530
write /proc/sys/vm/min_free_kbytes 40960
write /proc/sys/vm/min_free_order_shift 4
write /proc/sys/vm/mmap_min_addr 32768
write /proc/sys/vm/mmap_rnd_bits 16
write /proc/sys/vm/nr_pdflush_threads 0
write /proc/sys/vm/oom_dump_tasks 0
write /proc/sys/vm/oom_kill_allocating_task 1
write /proc/sys/vm/overcommit_memory 1
write /proc/sys/vm/overcommit_ratio 50
write /proc/sys/vm/page-cluster 8
write /proc/sys/vm/panic_on_oom 0
write /proc/sys/vm/percpu_pagelist_fraction 0
write /proc/sys/vm/scan_unevictable_pages 0
write /proc/sys/vm/stat_interval 1
write /proc/sys/vm/swappiness 100
write /proc/sys/vm/vfs_cache_pressure 100
# Increase readahead buffers on MMC devices
write /sys/block/mmcblk0/bdi/read_ahead_kb 0
# CPU Scaling
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 384000
write /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq 384000
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq 1674000
write /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq 1674000
# Configure Performance
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor performance
write /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor performance
# Entropy
write /proc/sys/kernel/random/write_wakeup_threshold 2048
write /proc/sys/kernel/random/read_wakeup_threshold 1195
# I/O
write /sys/block/mmcblk0/queue/rq_affinity "0"
write /sys/block/mmcblk0/queue/scheduler "bfq"
For the record, the Kernel is stable and solid and the ROM is not the problem. The issue is how Android is designed to work, as an operating system is the worse ever created and I will explain why.Hey everyone so i tried both versions now 7.1 and 8.1 with every different skz including the stock ones.
With the current settings Hearthstone will play on 8.1, updating the files.
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 have done all those testing, but none of that are the issue and I just found out about 2 days ago by applying changes to Android 9.
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.
There is going to be big news for lineage build and all the listed ROMs from this guide.
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.Well reasoned. Like I said, different strokes for different folks. I'm not going to debate. Use my kernel, don't use it, whatever.
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.