yashsingh1/xdaforums huggingface dataset:
[TouchPad Development] ankorez:
hi everybody

somebody know how install this rom on my HP please?

i have try with HP Toolbox but no work :(

HP Tool box dont install recovery or rom or gapps = it's failed :(

thank you for you help
[TouchPad Development] EricBlade:
Hello, everyone. Long time no see. Had a family emergency come up the day after my last post, and this is the first time that I've had to come back and check in.

I have yet to see a version of Android where Home actually works to wake up a TouchPad. (I am also a month behind on these)

Probably a little known secret: While holding power+home for 30 seconds does force a reboot -- there's another power+home sequence that you can do -- Holding Power and pressing Home 20 times will power off to the absolutely lowest power drain mode that the hardware can do. It is referred to by some as a "battery disconnect". It is a hardware function, and should work at all times, so long as your power and home buttons are both functional :) I do this when I am not going to be using a tablet for a long time, and have had less than a few % battery drain over weeks of time.

There are two A6 devices in the TouchPad (as well as one in all the webOS phones, and the Pre3 and Veer had 2). One of them is used as the battery charging controller, handling the multiple different power inputs (touchstone, usb connector). The other one handles the communication with the Tap-To-Share coil, that was used in webOS to share small bits of data between TPs, Pre3s, and Veers by tapping them together. The devices are also capable of reading the serial numbers of the TouchStones that they are attached to, and probably a whole host of other things that were never really capitalized upon. (there was a version of the Tap-To-Share software in development at the time of product cancellation that was able to actually transmit entire files, not just short bits of data, but it was lost forever in product cancellation)

The default operation for the doctor was to only upgrade the A6 firmware if the firmware already installed was a lower version number. There was, however, an option to force it to re-flash. So I don't think that there was necessarily significantly known issues with the production A6 software, but we *are* 5 years out from the development of this software, so it's entirely possible that there could be issues that were never discovered. Also, there were probably software updates to the A6 firmware between 3.0.0 and 3.0.2 which most devices came out of the box with, and 3.0.5 which was the last official release. (it's unlikely that there were any changes in the 3.0.6 webOS release that has made rounds out there, but getting a diff on the A6 firmware file between the two could be useful, although I'd expect it's been long enough that someone would've done that, if we're not all already using the 3.0.6 version)

Unfortunately, the TI A6 chip was not really used for anything else out there, as far as I've ever heard, so there's probably only like 2-3 people in existence who could be helpful to providing any further information or improvements, and they are totally not interested.
[TouchPad Development] nevertells2:
Welcome back. Hope your emergency wasn't too serious.

I have to dispute your home button assertion about waking up the TP. I have had virtually every version of Android installed on my TP, CM9, 10,10.1, 11, 12.1 and all of them allow me to wake up the TP using the home button. What has happened starting around CM11, the home button became less responsive and sometimes won't wake up the TP on the first try. I just repress the button, sometimes holding it down for a second or two and the TP wakes up. And I still stand behind my findings about avoiding the use of the power button to wake the TP up. I've never seen the power + home button 20 times thing. I remember reading in Sullin's Debrick thread that was used when trying to wake up a bricked TP. What kind of battery drain do you see if you use this?

I get -6mA drain as reported by BMW when putting the TP to sleep the normal way.

J.C. Sullin's was the one who advocated that reflashing the A6 firmware helped in keeping battery drain in check. That is why he incorporated it into his debricking script and TPTB. Don't know if you remember there was a couple of ways that you could force the reflash using a Terminal emulator command that ran it from within WebOS or Android. Like I said in my previous post, only the HP engineers could tell us exactly how the A6 works. Good luck finding one of them.

NT
[TouchPad Development] deafasheck:
Hi gang, im wanting to try and install marshmallow using tptb.. can you post the links to the ROM I found the links to the Re covery and GAPPS .. Only ROM I found says AOSP
[TouchPad Development] EricBlade:
Unfortunately, the emergency involved the loss of a family member, which is what kept me away for so long. Someone asked me today what mobile devices I use now, and I thought about it and realized that I hadn't actually even touched a tablet in probably 4 months except to install the first working data build of MM on the 4G. So I realized I needed to come back and see what was going on.. and that I hadn't been on since the day of the incident. :-S .. and had to catch up on about 15 pages or so of stuff.

Power + 20x home is probably pretty close to immeasureable, it shuts *everything* off instantly. I don't know exactly what the difference is between that and just issuing a regular "poweroff" command, but in some technical docs that I've read, it indicated that that would enter the absolute lowest power consumption mode available. I don't have any software installed for monitoring battery.

I am not disputing that the A6 could be getting screwed up (especially when running "alternative" software like Android :) ) and need more regular reflashing.. just disputing that it was something that the original Doctor software did every time.

I am going to go charge up my 4G TP and see if I can get it to download the latest. :)

I do know one of the A6 engineers.. he's not really terribly interested in helping out unless it involves a very very very minimal amount of time though. I can probably get away with asking him some questions, and if he remembers the answers, but I wouldn't want to make him angry by pestering him regularly.
[TouchPad Development] DarkShadowAy:
Hi Guys, I've been out of the game for a while. The last android build I had on was Cyanogen 10.2 (Android 4.3.1) with Kernel 2.6.35

I also have Clockwork mod installed. I've downloaded the latest nightly build, gapps and TPToolbox.

Could someone please nudge me in the right direction in regards to steps of what to do? I'm guessing I have to resize partition sizes first, then do a clean and install the nightly build and gapps.

Many thanks :)
[TouchPad Development] nevertells2:
Evervolv is an AOSP Rom. All the links you need for this Rom are in the OP.

NT

---------- Post added at 01:01 PM ---------- Previous post was at 12:56 PM ----------

Start here:

http://xdaforums.com/hp-touchpad/help/rom-guide-how-to-install-android-4-4-x-t2912820

Read here:

http://xdaforums.com/showthread.php?t=2756314

and then this post:

http://xdaforums.com/showpost.php?p=66178263&postcount=987

NT
[TouchPad Development] patrafter:
I flashed Gapps, the latest nightly and TWRP but when i start it I get a pop up which I can't get out of "unfortunately google play services has stopped". Clicking ok makes it pop back again over and over.
[TouchPad Development] david_inuk:
I am almost sure u r supposed to flash the rom first and then gapps
[TouchPad Development] viskon:
I would flash TWRP first then use TWRP to wipe data, flash the rom and then the gaps.
[TouchPad Development] nevertells2:
So what did you have installed before trying to install this Rom? And please explain in detail what you did and what you used to do it.

NT
[TouchPad Development] nickb2b:
Question, if I want to flash a new nightly do I also need to reflash gapps again before rebooting?

Thanks in advance.
[TouchPad Development] jerryatherton:
Don't re flash happy unless you did a full wipe.
[TouchPad Development] patrafter:
Heya. Yea thats what I did. I guess i should have been clearer. I fixed it anyway. I went back into TWRP and wiped the cache and data to reset it. The next bootup took a while again but I guess it set it up properly because I could go through the google settings this time.
[TouchPad Development] exProphecy:
Installed 7/14 nightly and I am getting no response from touching the screen. I used tptb to install the ROM with a gapps 99MBs. After that didn't work, I did a regular flash of all data, cache, system etc and only installed the ROM itself. Touch still doesn't work.. any ideas?

Note: Touch works in TWRP tho. I've set cm-cache and cm-system both to 2GB each.

EDIT: Touch works on 7/13 build.
[TouchPad Development] muerte33:
According to the log, only one change was made, but it must have been a critical one!

2016.07.13..2016.07.14

Project: device/hp/tenderloin-common/

1a4af21 tenderloin-common: add build barrier
[TouchPad Development] Globaltraveler5565:
Me, too! Same finding. Restored back to previous release and all is working again. Whatever the problem was, I couldn't get into the system enough to catch the logs any way I tried. Sorry...
[TouchPad Development] flintman:
Looking into it now
[TouchPad Development] lippy lipkowski:
I had the same trouble on 2 of my 3 Touchpads that are running the 6.0.1 Evervolv. Dirty flashed the 7-14 and no touch function. Thankfully I didn't flash the third one cause it still works!
[TouchPad Development] Nomad1600:
I was lucky and updated from 7/2 to 7/13 (before 7/14 appeared in my Updater. I dirty flashed using the Updater... so it may because I didn't wipe everything like I often do. But has anyone noticed the 7/13 is a bit laggier? Again, it may be because I was lazy and only wiped cache and dalvic, or it may be time to reflash A7. Just wondering...
[TouchPad Development] Cobra11Murderer:
yup 14 causes touch to not work and constant reboot
[TouchPad Development] WildKun:
Hello guys, can you suggest a nightly build for daily usage. Seems like latest one is out of question for now.
[TouchPad Development] ZeroZorro:
I don't have the problem described above with latest build, only thing is that the error about being connected to WiFi but no internet is back with 14 build
[TouchPad Development] nevertells2:
Do you mean flash the A6 firmware with TPTB? If that is the case, A6 would have nothing to do with your TP having lag problems unless you thing your battery could somehow have an effect on performance. The A6 controller and it's firmware only have to do with the control of your TP's charging and usage. That is why flashing the A6 firmware seems to help when battery drain gets worse when the TP is asleep.

NT
[TouchPad Development] tedrogers61:
I flashed the 2016.07.14 Nightly and the screen was totally unresponsive. Even after several hard reboots. Eventually went back to 2016.07.02 Nightly, which was the only one I had downloaded in on my TP, did a dirty flash and were back up and running again. Typing this now from it. Just thought I'd mention this screen unresponsive issue with 7.14.
[TouchPad Development] jerryatherton:
The 7/02 build was very stable. I am sure Fintmanwill get the 7/14 problem corrected quickly.
[TouchPad Development] Nomad1600:
Yup A6, my fumbly fingers. Wondering if I should go back to 7/2...
[TouchPad Development] sdemun:
Same finding here as well on a clean install of 7/14. Used TWRP to restore a backup of 7/2 release as well.
[TouchPad Development] k4ever:
I wish I had checked this forum before installing 7/14. I have the same problem. The screen is unresponsive. Guess I will go back to 7/2.
[TouchPad Development] muerte33:
Looks like there is a 7/16/2016 build

Fix up build barrier

Change-Id: Ibdb5986e1d64a88640c38f20d6e2212dc63cca4b

http://review.evervolv.com/#/c/20758/
[TouchPad Development] tedrogers61:
7/16 is a bit better than 7/14....on it now...still laggy though which makes it seem like touch isnt always working...it is working but it seems to take a long time to respond. Maybe it just needs time to settle after flash.
[TouchPad Development] nevertells2:
At least until Flintman sorts things out.

NT
[TouchPad Development] lippy lipkowski:
I am booting it now after using recovery to get the 7-16 ROM on one that I flashed to 7-14 that bombed the touch screen. I will know if this fixes the tablet shortly.

I will do it on the 2nd tablet that is in the same state having flashed the 7-14 to it as well.

I am also waiting for the 3rd tablet I run this rom on to boot the 7-16 dirty flashed over the 7-13. This third tablet is the one I had not flashed to 7-14 and never did because I found that it bombed the touch screen on the other two hehe.

Seeing the first one that I flashed 7-16 over bombed 7-14 and it isn't even optimizing any apps. It already says STARTING APPS. Muwhahahahahaha

Love this ****, So much fun hax0rizing these devices. THANKS FLINTMAN MUCH LOVE!

Ok it just did a reboot after the ART boot so now this will be the real thing.......

---------- Post added at 03:20 AM ---------- Previous post was at 03:06 AM ----------

There seems to be QUITE some time after a flash before the tablet starts to respond nice.

I almost ALWAYS let the thing sit for quite a while after hitting the initial lock screen and letting it go to sleep.

Usually like 20-30 minutes just to let it chill.

To add to my post immediately above this, this looks like a 2ND ART boot cause it is slow booting. I suspect it will not update apps perhaps.......

The tablet I had NOT flashed the 7-14 to and went right from 7-13 to this new 7-16 completed the ART boot updating 19 Apps and seems to already be running nice and snappy, so I am not seeing any lag on that one.

Still waiting for the 2ND ART boot to complete on the tablet I flashed 7-16 over a touchscreen bombed 7-14. This is one of the longest ART boots I have ever seen so I am going to walk away from it now and crash out for the night likely....

More tomorrow

Thanks a lot Flintman,

P.S. Just to let you know how much class this Flintman individual has, a month and a half ago or so I offered him a donation in private messages and he responded....."Thanks anyways bud but I just do it for the fun"

I MEAN THAT IS A BIG WTF in my book in this day and age so Kudos Captain Flintmon dude mon dudeman dude! And the Mon is NOT a typo hehehehe.

Flintmon!

8)

Ok so while I finished typing this the first touchscreen bombed tablet upped from 7-14 to 7-16 finally finished the 2ND ART boot and went to lock screen and then to dock clock as I have it in the dock during the flash.

Lets see if it has touch.

Opps WAY WAY Turbo laggy..........but working. I suspect this will subside in a bit. Going to pull up CPU-Z Here and see what is up.

I am actually starting to think this pig is running the OS in ART mode as it is VERY VERY SLOOOOOOWWWWW hehehehe

But ALAS after a slight bit more time it is starting to run nicely. So it just needs more time after the flash to settle.

NICE!!!!!!!!

You rock sox Flintmon!

Weeeeeeeeeee
[TouchPad Development] BGrosse:
Hi Flintman,

thanks a lot for updating the nightly to 07-16. 07-16 ROM runs fine again and smooth. The WiFi ROM as well as the 4G ROM. The WiFi build is excellent in every concern; the 4G build has the "SIM card not found" error, I experienced in every ROM version until 07-16.

I just uploaded a log from the latest 07-16 ROM for the 4G build, which - as all other ROMs before - is rebooting spontaneous from time to time (10 times the last night). I dirty flashed before 18:00, let it settle, charged it to 100% and let it run on battery from 18:00 upwards. Within half an hour it rebooted 2 times and I noticed, the "SIM card not found" is still there. This seems to come along with a huge current consumption in stand-by (sleep) mode (~150-200mA).

Please find attached the log: http://paste.evervolv.com/view/316a1905

Let me know if I can do anything for further assistance to get this "SIM card not found" error catched.

And as always: excellent ROM so far! Thank you soooo much!
[TouchPad Development] Globaltraveler5565:
7/16 working well...

I flashed 7/16 last night using the internal updater/TWRP and let it settle overnight. I don't know how many reboots occurred, but I saw at least two. And the colorful Evervolv boot banner seemed to go on for five minutes each (that appeared longer than usual). This morning the TP runs like normal, with only a few events that "felt" sluggish or laggy. Network connects and holds the link. Bluetooth works fine on my two keyboards and external speakers. Battery drain is still at an amazing -2 when sleeping or idle! Firefox and Orfox work as expected. My collection of games appear fine. Email w/BlueMail is great. Fitness tracker and diet planning app works.

I'm a happy camper. Thanks, Flintman! Keep up the fine work.
[TouchPad Development] muerte33:
Just as I got the 7/16 one installed the 7/17 one appears !

The log file is GIGANTIC!

http://evervolv.com/devices/tenderloin

Who's going to be the guinea pig on this one?
[TouchPad Development] yoruuba2:
This message is being typed on my TP running the 07/17 build - code: MTC19Z72. After the usual 2 reboots, system is very snappy. All my apps have been updated. Wifi hooks up quick and stays connected. Kodi is working fine, so is XtremeMusic , LSpeed, and the other apps I use on a regular basis.
[TouchPad Development] yoruuba2:
And a big Thanks to Flintman and the Evervolv team for their continued efforts to keep this old device alive.
[TouchPad Development] muerte33:
I went ahead and bit the bullet and installed the 7/17. So far so good.

Looks like a lot of the updates may have been security related?

I noticed the Android Security Patch level went to July 5, 2016 from June 2016.
[TouchPad Development] Globaltraveler5565:
7/17 release working well

After TWRP flash there was a very long startup (about 20 min with the rotating color Evervolv banner), followed by optimization of a handful of apps seemed normal), then about ten minutes of usual operation (I just left it to stabilize in sleep mode) and a second reboot that progressed normally in about ten minutes. No other reboots observed yet. All apps appear to run properly. Network connects quickly and early in the boot sequence; and holds the link without disruption. All Bluetooth devices good. Battery drain seems good for the limited time testing. Camera appears to work in snapshot mode; haven't had time to capture a video.

What more could one ask for. Thanks, Flintman, et al.

Update: reminder... after flashing new release remember to reset your Settings/Tools/Performance to FIOPS and SmartMax, if you desire.
[TouchPad Development] elginsk8r:
yeah, i updated the july security updates last night, also instant patching should work if any of you guys use arcus.
[TouchPad Development] nickb2b:
Camera working?

I thought the camera didn't work on the marshmallow releases. Has this been fixed with 7.17 update?
[TouchPad Development] Globaltraveler5565:
Yes, my bad. I was looking at a photo image viewer, not the camera app. I followed up with several of the available apps in the store without success in using the on board camera. Still more work needed on this area. This matter is not that important or useful to me anyway. Any modern (or even ancient) smart phone can do the job nicely and in higher resolution.

Sorry for any confusion regarding the camera. ? It still doesn't work. Apps either bomb out immediately or report an error and abandon quickly.
[TouchPad Development] Nomad1600:
After seeing lagginess in the 7/13 version (didn't try 7/14) using the EV Downloader with only Cache and Dalvic wipes, I did a full wipe and reflashed 7/2 which was a good performer. I am now trying 7/17, but downloading directly, full wipes, and see how it goes. I don't have many files on my TP so having to full wipes and re set up isn't that much of a hassle and seems to result in a better experience.

btw, since changing my browser to UC Browser I have also seen a better browser experience (seems to be faster).
[TouchPad Development] muerte33:
Now there is a 7/18 rom with a pretty good size log.
[TouchPad Development] elginsk8r:
Mainly theme engine fixes for certain apps
[TouchPad Development] BGrosse:
07-18 runs smoothly, updated from within update tool while cleaning Dalvik and cache. Everything works like a charm, TP is snappy. YEAH!! :D

I also think, this was the first update which did NOT reboot while/after updating. After 15 minutes of settling time, it was responsive a usual and I did a manual reboot. Now charging to 100% and then... it's playing time! :fingers-crossed:
[TouchPad Development] flintman:
Ya im trying to figure out why sometimes you get a reboot and others you don't. I want everyone before they update to clear recent apps and see if that helps.
[TouchPad Development] TaylorV:
edit: Shortly after posting this, I was able to work around the issues by booting into WebOS recovery mode, executing touchpad toolbox, and mounting from there. Mount issue seems to be with TWRP.

Not sure if this is related to the build I recently put on that killed the touchscreen, but I'm unable now to mount my TP through TWRP. After flashing the 7/14 Evervolv build and noticing that the screen wasn't working, I figured I'd boot into recovery and flash back to an earlier build. However, when I try to mount my TP through TWRP, it doesn't seem to actually mount. I've got all the novacom drivers installed and have never had this issue before. So at this point I am unable to access Android because touchscreen doesn't work, and while I'm able to boot into recovery, I'm unable to mount the TP and access storage from my PC, so I can't transfer another build to flash.

I haven't had much time since realizing this issue a few days ago to work on it, but I'm free today so I'll be trying to figure this out. If anyone has had a similar issue and can offer any advice, I'd appreciate it.
[TouchPad Development] BGrosse:
Hey flintman!

Thanks for your response - I can acknowledge at least two recent apps, which have been in the list before I started the update: 3C Toolbox Pro (for battery monitoring primarily) and the Settings/update dialog of course. Maybe a third app which I use for tracking spontaneous reboots called "Restart Counter" may have been also in the recent apps list (although the "Restart Counter" is not needed for the WiFi ROM - for the 4G ROM which does reboots up to 07-17 every once in a while its very helpful to get a clue on how often it reboots spontaneously).

Is the reboot during the update process a problem of a watchdog forced reset? Maybe due to heavy system load? :confused:
[TouchPad Development] nevertells2:
Not related.

NT
[TouchPad Development] TaylorV:
7/18 build is a nice change from 7/14, lol. Touch is very responsive and lag seems to be down tremendously from the last working build I had (I think it was 7/2)

Keep up the good work (y)
[TouchPad Development] jessesam:
I installed the latest 7/18 build and the blue-tooth doesn't turn on, does anyone know how to fix this issue ?
[TouchPad Development] elginsk8r:
I will investigate when i get home, can you post a log trying to toggle it on?
[TouchPad Development] jessesam:
When I toggle it on, the button stays for 5 sec and then toggle back off. It doesn't find any Bluetooth devices during that period and I clean flashed the latest build.
[TouchPad Development] elginsk8r:
Thanks for the description, but that wont help...i need logs from logcat