yashsingh1/xdaforums huggingface dataset:
[TouchPad Development] MikeN68:
Trevor4706

The uImage.webOS file is a symlink to the actual kernel: uImage-2.6.35-palm-tenderloin. Just create a new symlink to this, calling it uImage.webOS and all shoudl be well. It should be 3.69MB

Oh, and if you fancy doing this again, you'd have to move the actual kernel not the symlink . . .

I found that when the /boot partition runs out of space it doesn't always fail to copy, but the file you copied might be smaller than the file should be.
[TouchPad Development] trevor4706:
Mike N68

Thanks for your response. I am not sure what exactly is a symlink. I googled it and confess I am not much wiser. If it is just a small file that points to the kernel, I don't understand how it could be 3.69 MB, which is about the size of the uImage.WebOs I currently have. Can you amplify?

I am pretty up on using text commands -- been doing it since DOS days, if that helps.
[TouchPad Development] shumash:
Well, just guessing at this, but in order to use TP Toolbox in /boot, it's not just the uImage that has to be deleted, the WebOS partition has to be gone, as in deleted by TP Toolbox and its space allocated among the other partitions. Restoring the WebOS image won't work because it's partition space is gone. You'd have to restore the WebOS volumes in toolbox.
[TouchPad Development] nevertells2:
Portuguese version:

Você percebe que WebOS está morto. Os servidores web são desligados, o apoio é ido. Então, por que você quer continuar a usar WebOS?

Desculpe sobre os outros caras comentar, ele não é muito educado.

NT

English version:

You do realize that WebOS is dead. The web servers are turned off, support is gone. So why do you want to continue to use WebOS?

NT

---------- Post added at 09:41 PM ---------- Previous post was at 09:29 PM ----------

Portuguese version:

Então, se eu entendi corretamente, você removeu WebOS e deseja instalá-lo novamente e também Android?

NT

English version:

So if I understand you correctly, you have removed WebOS and want to install it again and also Android?

NT

---------- Post added at 10:04 PM ---------- Previous post was at 09:41 PM ----------

Can you open the uImage.WebOs you tried moving around with a text reader and see what it does.

Then you might understand a symlink and what it does. I Googled WebOS symlink and found this:

https://github.com/webos-internals/webos-linux-kernel/blob/master/fs/smbfs/symlink.c

That little bit of code is 1.44 mb in size. WebOS is a Linux based operating system, so if you

understand Linux, then you should be home free.

It's possible that in moving that file around, it got corrupted and now won't work.

NT
[TouchPad Development] MikeN68:
nevertells2,

I would sincereley hope that anyone using webOS now knows the servers are off. Certainly users coming to XDA (or webOS nations) should be aware!

Just because something has no official support and is not manufactured anymore doesn't necessarily mean it is useless. I use my webOS TP everyday. Yes, I also dual trple boot with Android (obviously!) and also LuneOS. I actually like webOS (the bits that still work) and whilst it may not be as fast or flashy as the newer Android OS's it does the job that I need it to and for me that is enough.

Some of us are just stuck in our ways :)

Oh, and it is people like you spending your personal time helping others that keep our aging devices working. So many thanks for that.
[TouchPad Development] Phenoum:
Hi All! Company decided they needed my iPad back, so I spent the week moving from CM9 to Evervolv 7 as the TP is now my only tablet :D Love the community and wealth of information that's here!!

For reference I used the TPTB to wipe the TP entirely, installed the JP "approved" CM and TWRP, and then wiped with TWRP and installed Nougat as per the OP in this thread.

Using the 2016.09.18 build - it's been quite useful. The only thing I cant get to work so far is BT. It will turn on and even see my BT device, but when i try to connect it fails, powers off BT, and then the TP crashes entirely.

No wifi issues for me so far - running on a 5G network at home.

I do have one question though: one of my primary use cases is to use the United Airlines app to watch personal-device-entertainment when i travel (for work). However, the DRM protection block replay as it sees that the device is rooted. I need to block the app from seeing that it's rooted... I have seen a few options out there, but was wondering if there is a specific recommendation from the Evervolv community for this custom ROM?

Options so far are:

RootCloak via: Xposed Framework (or Cydia Substrate platform)

A custom United app that apparently doesnt check for DRM...

Thanks!
[TouchPad Development] Hikikomorikruge:
Installing Xposed on Evervolv 6 for the Touchpad resulted in a boot loop. I don't think any additional Xposed compatibility has been added since my last test so Evervolv 7 is unlikely to work. If you on choose to test it make sure you have a full backup in TWRP before flashing.
[TouchPad Development] shumash:
You could try this:

Use Developer Options in Settings. If you don't already have it, go to Settings and then to About Device. Tap on build number continuously until you see a toast message that says "You are now a developer." In settings, you will now find Developer Options.

Scroll down in developer options and you will find an option to set permissions for root access.Click on it and you will find options as "only apps" ,"apps and adb","only adb".

Check "only adb" and root access will be disabled completely for apps.

It may be that once you log into your United app, you may be able to restore root to other apps as long as you stay logged in. Otherwise, you can restore root to apps after you finish with your app.
[TouchPad Development] racenrich:
Hello all...took the plunge and knocked out a 7.0 HPTP install. Had to got the old fashion route, thanks to ALWAYSLUCKY for that install method, worked perfectly!

going to give it some testing tonight.

Kudos again to the DEVS keeping my touchpad alive and kicking!

Gotta love it!

Rich K.
[TouchPad Development] flintman:
Hey all been super busy at work and getting ready for a cruise in which i head out Friday. I have been digging into BT when i have a spare sec and i seem to fix one thing to break another so really need to sit down and figure that out. Once back from my cruise ill have more time to sit down and hammer out some issues.

Just wanted to give an update.

Thanks
[TouchPad Development] pdechad:
Enjoy the cruise!
[TouchPad Development] nevertells2:
You would be surprised how many people, especially those who are dual boot don't realize WebOS support is gone. And no, it is not useless just because support is gone. If HP had not abandoned WebOS and continued to fix it's short comings, I probably would never have considered Android. I really liked it. At that point in time, it might have become a real competitor to Android. I am just trying to make folks like our friend @ joshua764 aware of the fact.

NT
[TouchPad Development] rebel1699:
Believe it or not, I slightly regret totally removing webos from my tp for only one real reason. The ability to connect my phone via bluetooth and route calls and texts to it. I loved using it as a desk "phone". I have long wished android would have given our tablets that same level of connectivity via bt.
[TouchPad Development] flintman:
Ok new build is up. I have switched away from Block style install. Block style is designed more for devices that have a fixed system partition to speed up install time. With the touchpad your able to change partition sized but Block style doesn't allow for that. Install is a little slower, not that noticeable to me, but the extra install time allow for you to make system partition what ever size you want. Also changed BT and im able to connect to my BT headset now. Test it out and let me know. Im still testing but wanted to get something out to you all before i go. If it doesn't connect the first time try a few times.

Thanks
[TouchPad Development] muerte33:
Thanks Flintman. My BT external speaker still works with this version.

I see you added the September Security fixes too!

What is the lag between when they release to Nexus devices before it is released to the open source community?

Thanks!
[TouchPad Development] db_white:
Many thanks to you! Seg faults appear to be cured, and Touchpad feels snappier as a result. (Currently overclocked to 1782 and still stable.) Will put it thru the wringer later.

I was a little surprised to see the install format 'system', but that's how I've been been testing, so no impact to me - other than having a full 2GB 'system' mount point.

Enjoy the cruise and thanks for all your efforts on this one!
[TouchPad Development] Geomatic:
Can it be dirty flashed over the 9/18 Version?

Gesendet von meinem Vienna mit Tapatalk
[TouchPad Development] muerte33:
That is what I did.

I just cleared the Dalvik cache and flashed it using TWRP.
[TouchPad Development] nevertells2:
Matthew gonna interfere with that?

---------- Post added at 10:52 AM ---------- Previous post was at 10:46 AM ----------

https://play.google.com/store/apps/details?id=com.tct.smartlink.phone

https://play.google.com/store/apps/details?id=com.apdroid.tabtalk

Something like this?

NT
[TouchPad Development] rebel1699:
I did beta testing for tablet talk when it was new, but habent used it in a long time. Ill try the other. I was more referring to native ability in our bt stack.
[TouchPad Development] BGrosse:
Hey [MENTION=3716175]flintman[/MENTION],

have a nice trip!

Bluetooth audio connection doesn't work here at my side. It's still the same like in the older releases. TP sees my Jabra REVO, tries to connect, then disables Bluetooth and starts over. I tried it a dozend times with no success.

Maybe you can have a deeper look inside when you're back. Anyway - thanks for all the work you spent already for this! :)
[TouchPad Development] Globaltraveler5565:
10/5 release dirty flashed over the 9/18 with positive startup.

Same experience with BT and my JBL Charge2+ speaker. I tried four times with noted results, turned on extended network logging and bt snoop logging, tried another five or six times. Finally gave up and turned off BT; will try after dinner again with HP keyboard (that was previously working in last Marshmallow version). Logs attached. It seems to fail when no pairing code is required from device, but works fine when pairing code needed and given.

Look at time stamp after 4:08pm EDT in logs.

http://cloud.tapatalk.com/s/57f6b50f521fe/2016-10-06_16.14-BT-failure.zip

http://cloud.tapatalk.com/s/57f6b7eb5ef5e/btsnoop_hci.zip
[TouchPad Development] Geomatic:
Same problem here with my Sony SRS X33 BT speaker.

Anyway thanks to flintman for providing this ROM!

Gesendet von meinem Vienna mit Tapatalk
[TouchPad Development] MikeFRG:
Last built is much more snapier and no more browser freezes!

Thanks
[TouchPad Development] Trainer_H:
How is the current in standby?
[TouchPad Development] Globaltraveler5565:
I'm seeing -17 to -20 while in standby without charger. But I keep the wifi on all the time and this morning I was also using Avast SecureLine VPN from a doctor's office. I usually get around -2 at home without the VPN. So your mileage may vary.
[TouchPad Development] middle_road:
It had d*mn well better not. Sounds to me like Flintman needs the break. :cool:
[TouchPad Development] Globaltraveler5565:
Updater keeps failing

When downloading the test image zip file. It always stops at the end of the download, perhaps while creating the md5 checksum. Logs attached. Look around the 12:15pm timestamp.

The small pop-up reads:

"Updater keeps failing" and gives two options to either close the app now or ignore until next reboot. This occurred right after I had just rebooted. It occurs every time I try to download any image from Marshmallow or Nougat,any release version. I'm using N 10.05 and fully patched to date from the Google play store.

http://cloud.tapatalk.com/s/57fa924ba870e/2016-10-09_14.51-UpdaterFai.zip
[TouchPad Development] db_white:
WiFi issues w/ 10/05

Tried to install Svox UK voice. Per 16:54 screenshot, installation failed due to internet issue despite a full WiFi radar pattern at the top of the screenshot in the notifications section.

Previously had seen a locale error message and WiFi renegotiations in the CatLog, but I'm not seeing anything this time.

Did a speed test and seeing 17Mb download on the TouchPad. For what it's worth, my Nexus 6P is clocking 30Mb down in the same location, same test site.

With a clean install of 10/05 (i.e. wipe data and restore), Netflix started pixelated but quickly upshifted to something looking like HD (at least to these old eyes). No problems to report with Netflix.
[TouchPad Development] db_white:
Xfinity TV / TV Go issues

TV Go crashes - missing an API to determine available codecs.. Xfinity TV returns "Subscription required" for a channel on my lineup. CatLog indicates a DRM failure.

10/05 version, as before.
[TouchPad Development] db_white:
Nougat WebKit patches?

I'm wondering if it's possible to get the subject patches included in this ROM? Don't try try this at home without a current backup, but flashing the "stock" Gapps package breaks the browsers due to the missing patches.

Thanks!
[TouchPad Development] Gborg3:
Does anyone else with the latest build and all previous N builds see their TouchPad freezing up to the point of requiring a forced reboot of holding power button and physical home button for 15 seconds to get anything more than a black screen and flashing home button when left on dock charging for more than a short time?
[TouchPad Development] db_white:
I've experienced freezes with the versions prior to 10/05. There was a problem with memory management that caused the Touchpad to run out of memory. In my usage, graphics intensive websites would lockup the browser followed by the Touchpad.

There's no sign of that Seg fault in CatLogs generated by the 10/05 version for my usage. Two suggestions - Capture a log to see if an app you're using is leaking memory. And two, use TWRP to repair the system partition. I've seen flakey behavior when system is corrupted. Life got better after a fsck and clean install.
[TouchPad Development] uzairmahmud:
Did a clean install to the latest alpha.

I am experiencing freezes with browser on graphically intensive websites.

Another issue is the touchscreen seems too sensitive. like typing would lead to two or three of the same alphabet being registered unless i do it super fast.

Other then that confirmed that the A.R.I.S.E sound mod works without causing bootloops or driver issues

http://xdaforums.com/android/software/guide-how-to-enable-google-assistant-t3477879

using the aove guide i was able to get the new google assistant up and running on the Touchpad. However its not working with ok google command. rather it works by holding the home button down like for google now except it brings up the assistant now.

its pretty cool that my years old tablet can un an AI voice assistant while my bootloader locked Samsung gm-870a only just got marshmallow without root . :mad:

Also thanks dev for all your hardwork.
[TouchPad Development] Moody66:
OK Google has had issues with these for years. Most disable it,
[TouchPad Development] uzairmahmud:
Ah no Ok Google is actually working perfectly in the rom. its just the way New google assistant was installed that is causing the issue. this issue is reproduced on a lot of different devices
[TouchPad Development] Moody66:
It works. But can and has caused issues. Search the touchpad forums .. loads of posts about it.
[TouchPad Development] EricBlade:
So, umm.. I'm just catching up here after months again, sorry, and .. I was curious.. has anyone tried the hacks to get Google Assistant in ?
[TouchPad Development] nevertells2:
Everything I read says that Google Assistant is just Google Now re-branded with a few cute features added. And we all know what turning on Google Now does to the current builds of Android on the TouchPad. You can still use Google voice search or text search.

NT
[TouchPad Development] lippy lipkowski:
Anyone know if JC's TP_Debrick addresses the battery with a question mark issue? One of the tablets went dead and is clearly charged because it remained on while unplugged showing the battery with question mark for like 90 minutes before I did the Home / Power button reboot combo.

After that it comes back up in the battery question mark mode again whether plugged in or not

If I do the Web OS recovery key combo of volume up / power after I get the reboot with the Home / Power button combo hold it goes right back to battery question mark mode

If I keep holding power and home key combo and then add the volume up as a THIRD button to hold immediately after the Home / Power button combo reboot actually reboots the tablet, I can get it to go off

If I hook up the stock 2 AMP HP supply to the USB charging port then I get the half light power button LED blink, BUT the power cylinder gets quite warm seeing to indicate it is getting fully drawn upon at 2 AMPS, but the tablet never comes out of that half light power button LED alternating blink

Have left it in that mode for 18+ hours and it did not snap out of it

Normally that mode will be indicating a trickle charge until a certain voltage is achieved and at the point it would normally reboot the OS and continue charging

I have tried it on a dock and the scenario remains the same

Nothing but battery with question mark or if I achieve the 3 button hold power off after the Home / Power hold reboot, then when I put it on the dock it does the trickle charge power button alternating half light blink just like it does plugged directly into the stock power cylinder.

Almost sounds like the A6 firmware is not up thusly the firmware does not know the battery is even there.

Very odd.

This happened on one of the 8-22-2016 6.0.1 tablets of the 3 I have been running.

Perhaps JC's TP_Debrick gets me out of this? Never used it. Anyone have a clue?

Perhaps I need to let the tablet totally die out again and try the trickle charge again? Anyways if anyone has a good clue here it would be much appreciated.

Thanks!

Lip Lip Lip
[TouchPad Development] dyingjedi:
+1

thank you! this is exactly my situation!! please to. if anyone could please give us a solution please it's my brothers touchpad mine worked fine and runs. I did my brother's touchpad then it's been bricked with question mark in battery for over a year.. thank you

Justin Cram

dyingjedi
[TouchPad Development] firepower9966:
Touchpad Toolbox allows you to Reflash the A6 firmware, try that , you need to be able to boot up it WebOS recovery mode showing the USB symbol.

You can also ask for help at www.webosnation.com
[TouchPad Development] lippy lipkowski:
Hmmmm just found this.......

http://finallystart.blogspot.com/2013/05/reviveunbrick-your-dead-hp-touchpad.html

Going to try it tomorrow

---------- Post added at 01:26 AM ---------- Previous post was at 01:24 AM ----------

Yeah I am not able to get the WEB OS recovery.

Otherwise I could reflash the A6 in TPToolbox and I would be out of this.

The TP Toolbox V42 is actually on my Boot Menu so I am VERY familiar with it

But thanks for the suggestion.

Lip Lip Lip
[TouchPad Development] db_white:
Dolphin hang

Looks like a WebView issue.
[TouchPad Development] kuaka:
Updated to 10/5 build and having intermittent WiFi drop when transfer speed is high (e.g., speed tests, high bandwidth video streaming). Normal usage appears stable. Will test A2DP tonight with two different speakers and report back. Otherwise this is a great build - getting close to a daily driver. Very snappy with F2FS on my 32GB WiFi Touchpad. Thanks for continuing to develop for this device :)
[TouchPad Development] exProphecy:
How does Daydream work on this? I use my Touchpad as a clock in my room in Daydream mode. It is important to my life. Can someone test it out for me?
[TouchPad Development] Moody66:
One... You can't run tpdebrick with it not being charged.

Two. This has been posted many times. Some have had to leave it on charge for days to get them to boot after this happens.

Try a high output charger. And a quality cable. It will work. Eventually. Seen two doing this myself. Both took a long while to boot back.
[TouchPad Development] nevertells2:
Lippy and dying, Short of J.C. Sullins jumping in to answer your question, the only way you are going to find out is go read his debrick thread from post #1 to the end. There is not one person with enough knowledge about debricking except Mr. Sullins, so you are going to have to learn about it by reading the thread. I remember seeing that issue discussed, but I could not begin to tell you where. There have been so many different techniques discussed from letting the TP discharge to zero to leaving it on the HP charger for days to weeks at a time. I've seen holding down the power button while pressing the home button dozens of times in rapid succession doing the trick. So get started reading guys. One thing I can impart, follow his instructions to the letter. You are not doing yourself any favors if you don't.

We all know the TP is over 5 years old. It is amazing that we see folks running Nougat on it. But our trusty TouchPads are getting long in the tooth and at some point we are going to have to let go. You cannot say we have not gotten our money's worth from it. Good luck in your efforts to revive your old friend. Please do keep us advised on how things go. We are really off topic here, so I would suggest further posts in his thread.

NT
[TouchPad Development] Gborg3:
TWRP system partition repair worked some good magic. I should have thought about the basics after going from a boot loop after flashing clear Play Store to immediately dirty flashing 10/05 over boot loop and somehow magically getting a mostly functioning 10/05 build. This tablet may never die.
[TouchPad Development] db_white:
WiFi offline

WiFi went offline after waking up. Had to refresh the connection, then fine.
[TouchPad Development] BGrosse:
It just fades in to clock mode. Clock is changing position from time to time. Clock is digital and shows day and date.
[TouchPad Development] kuaka:
Just following up on my previous post - Bluetooth would not pair with my Acoustix or my Oontz Angle BT speakers on latest build. Something still going on there. Both have full telephone support so that may have something to do with it. I'll see if I have any wireless headphones or something with a simpler BT profile to test next.
[TouchPad Development] Globaltraveler5565:
It also has an option for analog clock (for us old folks). And a delay timer (default is 2min) to control when the daydream clock kicks in. You can also set dark room mode or normal, bright room mode.
[TouchPad Development] Globaltraveler5565:
10/05 release Updater fails

Flintman released a new version today. When I tried to download and install it using the internal updater, it failed right after the download almost finished. It left a file ending with a name of .partial. I suspect it might have been trying to compute the md5 hash total. Note screen shots below.

I assumed the download file was actually good, but just with wrong name. I thus took off the part after the zip element and proceeded to flash. I tested the zip file with zarchiver and it said the file was OK. I flashed manually using TWRP. Logs attached, look around d 8pm EDT.

http://cloud.tapatalk.com/s/580966cad1c52/2016-10-20_20.50.zip
[TouchPad Development] Kodes:
I'm on the 0918 release and also got the .partial file via updater. 254MB downloaded.

Renamed the file to .zip.

Used the updater to do a dirty flash.

Zip file installs without errors.

Reboots just fine.

Will now try to see what's fixed/changed...
[TouchPad Development] chmcarro:
Anyone know anything about the new build posted yesterday 10/20?