yashsingh1/xdaforums huggingface dataset:
[TouchPad Development] Globaltraveler5565:
NT, I just tried to inspect the size of my boot volume and found that TP toolbox doesn't like the cache and system f2fs partitions. So it won't even begin to analyze the volumes, throwing an error. End result: I can't see what size boot is today. But I have TWRP, Evervolv.com and TP toolbox installed in boot, along with moboot and a few small support files, with some extra free space to spare. It may have occurred when I originally migrated off webos to CM 4.4.4 long ago.

NT, do you know of another method/app to determine volume sizes?

Update: I found boot directory contains 32.85 MB at this time, so the volume is at least this large. I still can't tell what the full size is now. Still looking for an app or tool to diagnose volumes, even f2fs, sizes.
[TouchPad Development] mculbertson:
A good app i use is x-plore from the play store. I changed my file system, but I believe it read file and directory f2fs sizes when I played with that structure in the past.
[TouchPad Development] BGrosse:
NT, I am also an TWRP 3.0.2.0. Please find attached my /boot folder.

As Evervolv was a complete new install for this TP, there is no CM lingering around. But I have not deleted WebOS while installing the clean Evervolv. So there is some 3,19MB used, which I could have made available (if I had deleted WebOS which I didn't do at that time). But only this would not help me out since I need some 6MB additional to my current left space for successfully copying the uImage.TPToolbox file into /boot (I actually can copy some 4MB, which is my left space in /boot). So for the 10MB file of uImage.TPToolbox I need additional 6MB. Deleting the WebOS from my system would not help me out, since I would only get 3,19MB of it, right?

And I think, the other files and folders in /boot are completely needed - am I right...? :confused:

So I am stuck at this point because I found no possibilty to free some space in /boot. Even If I reinstall Evervolv's MM and kill WebOS, this only gives me 3,19MB - not enough for the 10MB TPToolbox Image. Or Am I missing something...? :confused:
[TouchPad Development] Nomad1600:
Here's a screenshot of my boot with the Toolbox in place:

[IMG="Boot"]http://i366.photobucket.com/albums/oo104/rbrusuelas/TouchPad%20Boot%20Screenshot_zpsynr4d5ps.png[/IMG]
[TouchPad Development] nevertells2:
Yup, with WebOS still installed your options are limited. Tell us why you are keeping WebOS. It's pretty much a dead OS. No servers, no support.

Removing WebOS should free up around 5 gigs. There are other files you don't see that go away when you do a comeplete data reset. Having TPTB in /boot is just a convenience. The only thing I use it for is reflashing A6. Everything I do is through recovery.

NT

---------- Post added at 08:40 AM ---------- Previous post was at 08:27 AM ----------

Try Rom Toolbox Lite or Root Explorer. Good file browsers to use on rooted devices.

I'm still trying to figure out how you increased the size of /boot. I could swear I read somewhere messing with the size would cause problems. The fact that you changed /data and cache to f2fs could be an issue.

NT

---------- Post added at 08:48 AM ---------- Previous post was at 08:40 AM ----------

How much space do you have in /boot? What is the total size of /boot? Best browser app to check that with is Root Explorer.

NT
[TouchPad Development] Nomad1600:
Hi Nevertells. My TP works with the ToolBox in boot. I was just showing which files I had in my boot so the previous poster could compare with those in his. I already use (and paid for) ROM Toolbox Pro (which you see in the screenshot). Not really interested in buying Root Explorer... is there a free alternative that will provide the same info?

UPDATE: I added the "show storage bar" in ROM Toolbox Pro settings and it tells me that /boot is 27MB. Does that help?
[TouchPad Development] SublimeMogul:
Does anyone have any tips about resolving the wifi issues? The problems I'm experiencing consist of, not being able to connect automatically after turning the screen back on and not being able to connect to networks with hidden SSID unless I reinput the name and password again.

The issue with reconnecting after screen on bothers me most because I have wifi set to stay on in sleep yet it ignores that setting. The issue with not being able to use the saved wifi information to connect is annoying, but would be negated by the wifi staying on while the screen is off.

I'm open to any suggestions at all. The device is a wifi only 32Gb touchpad running on the 5/20 build currently.
[TouchPad Development] nevertells2:
If you would like to try Root Explorer, here is a link to my copy of the apk I keep up on Dropbox: https://dl.dropboxusercontent.com/u/86768134/APK'S/Root-Explorer-v2.17.1.apk

Just side load it and allow superuser permissions. I've used it for years. It gives very detailed info about file and folder sizes. If you want to use it to copy a file to a protected folder like /boot, you have tap the "Mount R/W) at the top of the screen so you can paste a copied file into the folder. Once done, tap "Mount R/O" to protect the folder again. I like the fact you can copy files to a protected folder with Rom Toolbox without have to do any extra permissions.

I checked "Show Storage" in Rom Toolbox Lite and /boot shows 30mb used and 1.9mb free. Root Explorer shows 29.55mb used and 1.93mb free, so they are close in what they report.

And BTW, I have a moboot.background.tga in /boot which is 1mb in size. This gives me a cute little backgound behind Moboot instead of the plain black backgound.

NT

---------- Post added at 05:56 PM ---------- Previous post was at 05:37 PM ----------

Looks like you are running the latest testing build. The latest nightly is dated June 3rd. You might want to try out something newer to see if WiFi works better. I don't normally try to connect to hidden AP's, but I would think that having to re-input the SSID and password again would be normal behavior. And I am not seeing others commenting about WiFI reconnect issues, so you might want to explain more about how you installed Evervolv on your TP. Why are you having issues and not others?

NT
[TouchPad Development] SublimeMogul:
I will try a newer build in a few minutes after this my backup completes. I installed using TWRP version 2.8.3.0. I imagine it's a bit on the older side, are you thinking it may be my issue? I honestly hadn't flashed anything new in a very long time on this device. I did however adjust my partition sizes via the toolbox before I started down the path of catching up on the touchpad builds. Like I said I'm open to suggestions and appreciate any help offered, I searched for anyone with even remotely similar issues and came up empty so far. This is why I decided to comment as I did, this is a phenomenal build of MM and I'm really hoping it's just something I may have done in error.
[TouchPad Development] Nomad1600:
I don't know if it solves all your problem but certainly updating TWRP will be a good move. Flintman has a copy of 3.0.2.0 in the OP.
[TouchPad Development] nevertells2:
What did you have installed before you installed the Evervolv version of marshmallow? It really should be done buy a clean install. You should not install this ROM over older Android versions like JellyBean or KitKat or other Developer's versions such as CyanogenMod or Packman. Copy your nandroid backup over to your PC, use touchpad toolbox to do a complete data reset again, and then install Evervolv Marshmallow with touchpad toolbox as I recommended in post #987. BTW, TWRP 2.8.3.0 is perfectly fine to use.

NT
[TouchPad Development] Globaltraveler5565:
I'd like to share what I've learned recently about batteries in TP devices. Humor me for a minute.

It was recently suggested that the internal battery of the HP Touchpad devices are NOT composed of smaller "cells". After contacting multiple battery providers (specifically HP-Z1 batteries) and asking a fair number of pointed questions, Tom at Laptop Battery Express (440-261-4411 or 866-514-2590) provided the clearest and most detailed answers.

The HP-Z1 battery is encased in a hard plastic shell. Inside there are numerous small "pockets" or bags of Lithium Ion polymer jelly with isolation separators between them. Subsets of these pockets are wired in series to achieve 3.7v and then these subset groups are wired in parallel to achieve 6,000 mAh capacity. There is also a firmware chip inside made by Texas Instruments or Samsung to control the charging/discharging of the cells to protect them from over charging or total exhaustion, both conditions would be very bad and possibly dangerous. No one could answer definitively if the flashing of A6 addressed this internal chip or some other component. It's possible, though.

So the battery does not hold stacks of the metal hearing aid type batteries, per se. But the definition of a battery cell could be satisfied by the jelly pockets described by expert sources.

Please *DO NOT* try taking one of these batteries apart, as Lithium - Ion chemicals are quite dangerous. The HP-Z1 battery manufacturers also sell this battery format for at least six other common tablet devices on the*market today.

Can anyone else offer additional info on this matter?

Update: the company mentioned above sells TP batteries for $66, free shipment, 2 year warranty, expected recharge cycles around 500 times. YouTube has videos how to open the case, it's tricky and needs a special flat tool. Don't rush...
[TouchPad Development] nevertells2:
I'm afraid that the only folks who could shed a clear light on this are no longer in the HP TouchPad business. From what I have learned over the years is the A6 battery controller is part of the TP, not the battery. It is my understanding that the HP hardware and software engineers built the reflashing of the A6 firmware into WebOS Doctor. So anytime you used WebOS Doctor, the A6 firmware got refreshed. That tells me that HP knew the A6 firmware was a problem and this was their idea of a fix. I believe Mr. Sullins figured out that there was a routine that one could access via a small script from the terminal emulator app in WebOS to refresh of the A6 firmware. Before TPTB came along, those in the know used this script to reflash the A6 firmware periodically.

The following is attributed to Mr. Sullins:

(Posted by J.C. Sullins in the "How to install CM10 thread)

"I've been developing/testing the low battery drain for several weeks now with minimum drain as mentioned elsewhere. Then, a few days ago, all of sudden, it wouldn't drop below 18-22mA. After checking several things, I decided to check in webOS. Same thing in webOS.

So, on a hunch, I decided to reflash the A6 firmware (see tpdebrick-v004 thread).

Back to normal now.

My explanation: The A6 firmware is a bit flakey and reflashing it's firmware resets some of it's non-volatile memory to a known-good state."

So with that in mind, when he created TPTB, he included the ability to reflash the A6 firmware. I still have the command you would run from WebOS,

PmA6Updater -f -d 0 /lib/firmware/a6_firmware.txt.00

This script acccessed a routine built into WebOS to reflash the A6 Firmware.

I have not used it since Sullins included the ability in TPTB and I believe he included it in his Debricking script too. You would copy and paste the above command in the WebOS term app . Also, if you want to watch a couple of videos about flashing the A6, RolandDeschain79 created some. You will find them here:

http://rootzwiki.com/topic/39743-touchpad-battery-drain-issues-how-flashing-a6-firmware-can-help/

I can attest that when I notice battery drain increasing while the TP is asleep, I run the A6 reflash and battery drain returns to normal. I use Battery Monitor Widget by 3c to track battery drain.

NT
[TouchPad Development] sdemun:
Anyone having mic issues? I have noticed with every build of Evervolv 6.0 my mic works for google voice search but otherwise is non functional in any other apps.
[TouchPad Development] lippy lipkowski:
The user having trouble with the wifi reconnect issue might also want to try the Android Volumes Repair in the tptoolbox.

Also after getting TWRP 3.2 flashed, repair permissions and selinux contexts in TWRP
[TouchPad Development] Globaltraveler5565:
Flintman, I just downloaded and flashed the 6/5 release Rom. It matched the md5 checksum, backed up the old existing system/data/boot and flashed after wiping Dalvic and cache. It went through the usual startup sequence and rebooted. After this settled down for 2-3 minutes, it spontaneously rebooted again. Look at the attached logs around 8 or 8:05 pm time frame. It's been running fine for the last 25 minutes or so. I don't know why it restarted, as I wasn't doing anything on the tablet (it had gone into daydream clock mode at that time).

http://cloud.tapatalk.com/s/5754c1d87e9d1/2016-06-05_20.18.zip
[TouchPad Development] lippy lipkowski:
The 06-05-2016 flash seems batloads faster!

Kudos Devs!

Thanks much.

Still idling at -2ma when battery is fresh

-3 or -4 when battery is under 70%

Very very nice.
[TouchPad Development] nimms:
Same problem.. but mine never settled. was on 5/28 build, tried 6/5, had to do a factory reset.
[TouchPad Development] muerte33:
Thanks for the heads-up, glad I did not install this version.

Will wait for the next one!

:)
[TouchPad Development] jerryatherton:
Worked fine for me..
[TouchPad Development] eKeith:
Me too
[TouchPad Development] Nomad1600:
Downloaded and flashed (dirty) fine for me as well.
[TouchPad Development] flintman:
one thing i know its was noted before. Close out all recent apps before installing update. Also make sure you clear cache and dalvik.
[TouchPad Development] Flexmaen:
Hi! Thank you for the work.

I had problems installing this with the TPToolbox since the Gapps-Version you linked did not work.

But I had success using this one. (I used it with the nightly from 3rd June, but I guess this gapps version should work with other versions too.) Maybe you'd like to link that working version in your main post.
[TouchPad Development] Globaltraveler5565:
Flintman, I've downloaded the new release today (6/7/2016), flashed it using the embedded updater (wiped cache, Dalvic and system before flashing ROM. It went well, rebooted, updated 8 apps, rebooted again. This seemed normal and all took less then 30 minutes. However, after letting it settle without using anything for about 8-10 minutes (it went into sleep mode), the tablet spontaneously rebooted again. It came up normal and has been running well since then. Look at the attached logs around 7-7:10 pm.

http://cloud.tapatalk.com/s/57575a1492d37/2016-06-07_19.24.zip

Any advice what I can check or change?
[TouchPad Development] Alinaki:
Hi! Yesterday I installed latest nightly evervolv marshmallow build, and everything seems to be good but Google Chrome (even dev and beta) freezes on some complex websites. It's Chrome problem or just my device? Firefox seems to work just fine.
[TouchPad Development] lippy lipkowski:
Anyone see their home screen blank out with the exception of the dedicated ICONS on the bottom of the screen with the 6-7-2016 flash?
[TouchPad Development] muerte33:
Trying out the 6/8 build now, has not finished rebooting yet though.

Took a LONG time in the "android is upgrading" "optimizing app xx of 19".

It then rebooted after the "starting apps".

Had to employ the FIOPS and SMARTMAX under performance to get back the speed of the previous versions.

After a manual reboot, it went back to BFQ and INTERACTIVE, and it seems to be running OK now.

I guess I just needed to be patient and let it get acclimated.

Thanks again for all these updates and new builds!
[TouchPad Development] flintman:
ya sometimes if you have apps open it will take a while to boot after you clear cache and dalvik. In regards to changing to fiops and smartmax in the lower right check that to save on reboot.
[TouchPad Development] Globaltraveler5565:
Same results. Also noticed the settings, tools, performance reverted back to old settings. I updated to FIOPS and SmartMax. It rebooted twice; once after optimizing some apps as usual and again about 10 minutes later. It seems to be stable now. Look in the attached logs about 7:10 pm.

http://cloud.tapatalk.com/s/5758adbc48dc6/2016-06-08_19.30.zip
[TouchPad Development] w1ll1m:
I've installed the nightly 8/6 over 24/5 build and I have to say that it is a substantial upgrade. It is faster, smoother and more pleasant to use.

Thanks again flintman
[TouchPad Development] gassyjoe:
WiFi constatnly dropping out?

First off gotta say, love the build, it's brought new life back to my Touchpad. I am having one issue but I don't know if it's with the build or if my TP is just dying. My Touchpad is constantly dropping it's WiFi connection. Every 3-5 minutes I have to open up WiFi settings and click on the AP to get it to reconnect. It never says anything when it drops, just all of a sudden it no longer has a connection.

Is anybody else having a similar issue? If not I fear that the wireless radio on my Touchpad is dying :crying:

I have tried several nightly builds and it still happens so I fear that it's a hardware, not software issue. I am currently flashing the 6-8 nightly to see if that fixes anything.
[TouchPad Development] Globaltraveler5565:
Flintman, good news! The 6/10 release seems to fix the double reboot aft flash. Yeah! Been running smooth and fast for at least 3 hours. WiFi connected up fast and automatically and has held it solid.

Good job! And thanks!!
[TouchPad Development] k4ever:
Definitely Need Help with Web Browsing

I'm having the same issue with Chrome, Chromium (just keeps crashing), and Dolphin when I have JavaScript enabled. My Touchpad becomes highly unresponsive, websites freeze up or have trouble scrolling, and the problem lingers well after I exit the browser.

I mentioned having JavaScript trouble in a previous post, but no one replied. I use my Touchpad (and the other tablets I own) to surf the internet and watch YouTube videos. This is causing trouble with 1/2 of what I use the tablet for. I wish someone would look into this.

BTW, since Firefox is working fine for you, I will give it a try.

P.S. I would like to know what browser besides Firefox that others are using that doesn't have issues...
[TouchPad Development] Nomad1600:
Here's a slightly different question. Did the boot animation get changed to black and white or what I am seeing get somehow changed by a theme or other change I unintentionally made?
[TouchPad Development] k4ever:
Ok, so this is what I've done to make my TouchPad more stable and usable for Web browsing:

1. Go to "Developer options" in settings

2. Set the "Background process limit" to "At most 3 processes"

3. Go to "Toolbox" "Performance" in settings and ensure "FIOPS" and "SMARTMAX" are set (covered before in other posts)

4. Download "UC Browser" and set it as default

I believe that limiting the background processes reduces the amount of RAM being used by the Touchpad, which helps with the low amount of RAM the tablet has.

I also recommend hiding the icon for the Chromium browser or removing it all together. I have experienced Javascript issues with the Chrome, Chromium, and Dolphin browsers on this ROM. I have also experience the screen locking up (requiring it to be turned off and on) when using the Firefox and Opera browsers, as well as scrolling issues. The UC Browser is fast and doesn't seem to have any of these issues.

I hope this helps someone.
[TouchPad Development] muerte33:
I am not having any problems with the 6/10 build, but I am curious as to which UC Browser to use?

UC Browser

UC Mini

UC Browser HD (for android tablets)?
[TouchPad Development] Globaltraveler5565:
On the point 3 above, be sure to click the setting in the bottom right corner to restore your selection on reboots. Otherwise, it goes back to a default setting not necessarily your preference. [emoji2]
[TouchPad Development] k4ever:
UC Browser... I will try the one for tablets later.

I had a lot of trouble with scrolling and locking up with Javascript enabled on the other browsers.

---------- Post added at 02:04 PM ---------- Previous post was at 02:03 PM ----------

Thanks for pointing that out. [emoji2]

---------- Post added at 02:20 PM ---------- Previous post was at 02:04 PM ----------

After using UC Browser HD for about 5 minutes, I uninstalled it. I definitely prefer the normal UC Browser. It is easier to use and has (believe it or not) more easier to use settings.
[TouchPad Development] w1ll1m:
I limited background processes to 4 and I have been using Firefox nightly since lollipop
[TouchPad Development] viskon:
From a browser perspective, Opera Mini works best for me
[TouchPad Development] lebenskuenstler:
[MENTION=3716175]flintman[/MENTION]

Is there a specific reason why ActiveSync Support is not included? (Sorry for repost, though.)

Thanks for the rom, this is fastest and best ROM I ever had on my TP.

Okay, initial cm7 was rock solid, but nodody wanted to use that antique piece of software :)
[TouchPad Development] flintman:
Well Google removed https://android.googlesource.com/platform/manifest/+/a0b15d0a707c50391e4a718934482471518ae1b7%5E!/#F0 but quick search found this

http://www.androidpolice.com/2016/05/11/google-adds-exchange-services-to-the-play-store/
[TouchPad Development] Globaltraveler5565:
Flintman, I've noticed an occasional issue with the display (maybe one in ten times). When in daydream mode (power plugged in), the wakeup screen touch does not wake up the tablet, but actually puts it to sleep. I have to press the home button or the power button to bring it back to usable operation. I can't tell if this is related to the double touch issue or something new in the 6/10 release. I'll get a log the next time this happens. Just a minor irritation at this time...
[TouchPad Development] mthous01:
Bluetooth Blues

I've had an issue repeatedly that the official HP Touchpad keyboard and a HP Bluetooth mouse work well while in constant use, but when they aren't touched for a few minutes (I haven't timed yet) they disconnect. Sometimes moving the mouse or typing will cause them to reconnect, other times, not so much. Is this a factor of the bluetooth in the Touchpad having too short a "timeout" period, or a function of the hardware I'm connecting to the touchpad? Any ideas?
[TouchPad Development] ZeroZorro:
I only have the HP touchpad keyboard but don't have experienced this problem on the last builds.

And also with my Jabra BT headset I have no disconnection problems. It automatically reconnects after turning off the headset and turning on again also.

Sent from my GT-I9295
[TouchPad Development] lippy lipkowski:
Wow anyone else seen periods of -1 ma in sleep? I am only seeing it on the one new tablet but i am also remembering that doing the tptoolbox A6 flash twice has gotten me better sleep drain before.. i'll try the double A6 flash on the other brand new one i have and report back. -1 is fabulous. Nice work. I'm running the latest 06-10-2016. SWINGIN! Thanks devs.
[TouchPad Development] monfiston:
Hello

is what it is planned to operate the camera,

you have a date?
[TouchPad Development] Nomad1600:
Asking for ETAs is frowned upon...
[TouchPad Development] deafasheck:
Well I've gotten complete wipe, reinstall JC Sullivas latest lollipop cwm and have mastered tptb all but resizng, I gotta learn mgb that equal GB.. I've got my back up install on laptop, I'm gonna give JC Sullivan's twrp a trry. Gotta find that post I was in.

This. Lollipop asop keyboard I dislike, was using you touch pal, but like to see a default one with copy paste button.

Going to download this and tptb install it, first I'm gonna try flash install it. That is what tours saying I can do fright? JC. Sullivan's twrp and 3.0.20. Am I on right bvase? Thanks guys,
[TouchPad Development] lippy lipkowski:
I am having fairly good stability on 3 tablets dirty flashed all the way up to the current 6-10-2016. Two fully charged tablets with all recent apps cleared, have shown hours long periods of solid -1 ma sleep. WILD.

What a cool rom

Last few flashes took quadrant standard from 3400 up to 3960. Fabulotastic in the EXTREME!

Oh thank you thank you tha aaa aaank you devs.

I'M GUILTY -0- TOUCHPAD LOVIN!

Bwhahaha

8)