yashsingh1/xdaforums huggingface dataset:
[TouchPad Development] nevertells2:
Glad to see you are still around. I saw a post a while ago by either Shumash or Flintman(sorry, don't remember which) hinting that you had retired from Rom building.

NT
[TouchPad Development] xspsi:
Thanks!
[TouchPad Development] deafasheck:
GAPPA Link is dead, https://milaq.net/downloads/gapps/gapps-lp-20141109.zip

gonna try thelp= 201502 22 signed. will update results..
[TouchPad Development] djbrian:
Hello. Great forum. I have a touchpad running 4.4.4 and it has been running great. Problem now I just bought a smart one light keyboard for my son and the keyboard doesn't recognize the touchpad when plugged in via USB. Works with my phone but not tablet. Any ideas? Thank you
[TouchPad Development] nevertells2:
The TouchPad does not supply power to USB devices. If 4.4.4 supports OTG, go watch this video to see what you need to set up a TouchPad with OTG:

https://www.youtube.com/watch?v=Nc7tlPwFQpg

NT
[TouchPad Development] mpgrimm2:
Here are some of my notes about it to go along with that video...

[INFO] HP TP USB OTG Notes, Tips, & Tricks (4-28-14)

Props to NT for being so helpful throughout the TP forum on a regular basis!

Up All Night Sleep All Day via my LG G4 on Tapatalk
[TouchPad Development] Bushwalker8:
Is there another link to the original working gapps 2014-11-09 ? The download link from the first post times out. Thanks
[TouchPad Development] nevertells2:
The Lollipop Gapps from here works great:

http://xdaforums.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368

NT
[TouchPad Development] polish23:
Thank you!
[TouchPad Development] Bushwalker8:
Thanks for that, installed build 2016-09-01 with these Gapps working.

I am experiencing one issue with this build combination in portrait mode, very top & bottom of screen apps are not responding to touch. Rarely able to activate any buttons in those areas of real estate. If I get buttons to respond it's only if I offset the touch point, e.g. at the top touching the bottom edge of the icon. Rotating to landscape the buttons (now on the sides) all sense fine. Previous Milaq version 4.4 had no issues anywhere on the screen. Build 5.0 2016-08-01 is the same.
[TouchPad Development] nevertells2:
Unless Milaq is actively working on this Rom, your options are going to be live with it or install a different one. I have not seen a post on here from the developer since March and just because there is a 9/1 build does not mean there is anything new in it. Google has released Android 7, Nougat, which is two versions newer, so development on Lollipop has long since ceased . If you want something newer and relatively stable, you might want to try the Evervolv Marshmallow build.

One question, are you sure the problem started with this build? Restore your backup( Build 5.0 2016-08-01 ?) and verify the problem is gone. You could also try a clean install sans Gapps to see what happens. BTW, you did not mention how you installed this build and Gapps.

NT
[TouchPad Development] Bushwalker8:
Thanks. I fully appreciate where we aren't on the development cycle. The intention was to go to something newer than my previous Milaq 4.4, consistent with LP 5.0 on my other devices and not bleeding edge so hopefully more stable......and staying with Milaq given the good run I had previously. I only just updated a couple of days prior to the post and noticed it immediately. I went back the one version to 8/1 to see if it made a difference which it didn't.

To do the update I used toolbox V42 to do a complete wipe, removed WebOS in the process, updated system to the recommended 896Mb, media 896mb & cache 200mb and installed from there.
[TouchPad Development] nevertells2:
If you made a backup of the previous install that worked for you, I would reinstall that. If not, do a complete wipe again with TPTB and install the last Rom that did work correctly and be happy with that. And if you want a really good working KitKat Rom, IMHO, you should try J.C. Sullin's last build dated 11/16/15. I have nothing against Milaq's builds either. Just suggesting try Sullins too and use whichever works best for you. And for good measure, you might want to try reading the Evervolv thread for Marshmallow: http://xdaforums.com/hp-touchpad/development/rom-evervolv-6-0-0p1-dm-t3238427

Be sure to pay attention to what the users post about different dates. From what I have read, the latest builds are working really well.

NT
[TouchPad Development] X-Nemesis:
Hello fellow touchpad users. So I got my TP back from my Mom cause I bought her a Shield K1 tablet to use. I wanted to update the TP to a newer LP build or even MM if possible.

But I'm having problem's just getting Novacom installed on Windows 10 and then getting the TPToolbox to notice my Touchpad. I've followed the links for the Novacom drivers and ran through the install process but NovaCom doesn't show up in Windows 10's installed programs, but it is showing up in the Uninstall window.

I then run the .bat file for the Toolbox and it says that it doesn't see the "TPToolbox-2015-01-08-v42.bin", even though I'm looking right at that file.

Anyone able to help out?
[TouchPad Development] nevertells2:
I think doing some reading at the link below will get you going. There are videos as well as written instructions.

NT

https://xdaforums.com/hp-touchpad/help/rom-guide-how-to-install-android-4-4-x-t2912820
[TouchPad Development] richtw:
back off the package name from the url and you can see all the versions available. there is a lp version with a later date. I suspect the pinned post may not have been updated....since I am a noob I am prevented from sharing the url
[TouchPad Development] johnbelloh:
Clean install cm-12-20170201-NIGHTLY-tenderloin.zip

I have been away for a while using JcSullin's last 12.1 rom. It started getting flakey on a number of my daily driver apps. When I tried to clean install again I could not find a gapps that would work with the toolbox and gave up after trying over a dozen different 12.1 gapps. Instead I clean installed cm-12-20170201-NIGHTLY-tenderloin.zip from Milaq along with 2014-11-09 gapps. I am pleased to report that every one of my apps works better than before. The only problem I can report is Chrome won't work. It would not work with JcSullin's rom either since 2 chrome updates ago. A big thank you to Milaq. If he issues any more updates I will install them.
[TouchPad Development] nevertells2:
[MENTION=5045004]johnbelloh[/MENTION], Did you by any chance read my post right above yours? You did not explain, but from the problem you experienced, I'm guessing you were trying to use Sullin's TouchPad Toolbox. It is well documented that TPTB has problems with newer Gapps and recoveries. Using DoubleStuff's method overcomes TPTB's problem. However, in your case, instead of using TPTB, I would have suggested doing a factory data reset from recovery, then flashing Gapps from recovery. That would have reset you back to the equivalent of a fresh installation of 12.1. You could have also tried the factory reset and then flash 12.1, then Gapps.

DoubleStuff's method is really aimed at overcoming the short comings of TPTB, but really could be used to clean install any data/media version of Android. As far as it is known, Sullins has moved on, so an update to TPTB does not appear likely, so that is where DoubleStuff's method comes in very handy.

I tried 12.1 for a while, but had too many issues with it and went back to Sullin's CM11 which is about a close to a mature, bug free version of Android one could want.

NT
[TouchPad Development] johnbelloh:
NT - Thanks for the response and heads up on moving up to a newer rom. I have been using Phil's recovery and had become comfortable with it. I have two more spare Touch Pads. As soon as I get some time I will have to try your suggestion using DoubleStuff's method with TWRP & Evervolve.
[TouchPad Development] johnbelloh:
NT - I took your suggestion and installed the latest Evervolve 7.1.1 rom & gapps on one of my touchpads. All I can say is WOW and thank you for the post. I tried a different approach and will share it here. I used the TPTB to resize memory as described in DoubleStuff's post. I then reinstalled an old data media 12.0 ROM with old gapps that work with the old toolbox along with Recovery Clockwork PhilzTouch 6.0.4.9. After installation I did a USB transfer of the Evervolve ROM & gapps to the download folder of the old ROM. I went to Phiz recovery did a complete reset and installed the new ROM and gapps with Clockwork recovery. The new system came up bug free and works like a charm. I have a TWRP zip in the download folder and could install it now. I have never used TWRP and don't want to break the system now. Is there any advantage to using TWRP over Clockwork if they are both compatible with data media ROMS?
[TouchPad Development] nevertells2:
Which 12.0 Rom did you install first, an Evervolv one? CWM and TWRP each have certain things that the other does not. It's easier to make and restore a data only back up with TWRP than with CWM. On the other hand, it's easier to prepare the TouchPad for the install of a very new or different developer's Rom with CWM than with TWRP. Otherwise they both get the job done. The biggest drawback is backups made with one is not compatible with the other. So if you switch, you have to make new backups with the recovery you plan to use.

NT
[TouchPad Development] johnbelloh:
Thanks for your take on CMW vs TWRP. To answer your first question I used milaq's cm-12-20170201-NIGHTLY-tenderloin along with gapps-lp-2014-1109-signed and Philz touch CMW 6.0.4.9 for the initial install after resizing the file system to your Evervolv 7.1 recommendations with TPTB. I moved the 7.1 ROM, open pico 7.1 gapps and TWRP into the download folder with windows and installed the new ROM & gapps with CMW. After running it for a while I flashed TWRP using CMW to replace the recovery. I played with TWRP for a while and being "an old dog" decided I liked Philz touch CMW better. I noticed that as I added additional apps one at a time from the play store the entire system was getting slower & slower. I stopped at that point and decided to try increasing the cache to see if that would help. I did a complete reset with TPTP and increased cache from 100 to 196, re-flashed the A6 firmware and started over from scratch. I tried using the first 7.1.2 ROM on my clean install but found a bug where it asks the google set-up question restore your apps or start fresh. I went back and did another clean install with the last 7.1 ROM and let Google restore 47 apps. All 47 apps work! I used CMW to do an android backup followed by an update of today's 7.1.2 Rom. I cleared cache and delvic and rebooted. Eveything still works. Here is the strange part. I have been repairing and programming on computers going all the way back to vacuum tubes when it took four tubes to make one flip flop. This Rom must be analyzing each app when it is loaded for the first time and adjusting the cache to accommodate the requirements of the app. The larger apps like Facebook and Chrome browser stop the system and must be given time to adjust by retrying and giving the system time. It even stops completely with a locked screen. After the screen times out if you allow it to recover it eventually comes back and gets faster and faster and works great on subsequent reloads. It needs to do this on most of the larger apps. I now have a "daily driver" with 47 working apps. I hope my crazy description helps the crew. Thanks for your help and patience.

John "The old Dog"
[TouchPad Development] nevertells2:
First off, be careful flashing Evervolv Roms over CM Roms. Unless you use the "Prepare device for a different Rom" function of CWM, you could run into issues.

Read Sullin's TPTB thread and you will see that the size of the cache volume should be at least 200mb. /System should be at least 1312mb for a Nougat build, but I know others have been setting it to 1800 or larger.

As far as I know, your assumption about the Rom setting cache size is not true. Since Google changed from using Dalvic Runtime to it's own version, Android Runtime(ART), the way that is handled is different. This is why on a new install, it takes a really long time on the first boot because ART is analyzing each app currently installed. Where as Dalvic did it on the fly each time you launched an app. Google's approach was do the homework first and that way, apps should load faster. Here is something I pulled from an article about this:

"Dalvik is based on JIT (just in time) compilation. It means that each time you run an app, the part of the code required for its execution is going to be translated (compiled) to machine code at that moment. As you progress through the app, additional code is going to be compiled and cached, so that the system can reuse the code while the app is running. Since JIT compiles only a part of the code, it has a smaller memory footprint and uses less physical space on the device.

ART, on the other hand, compiles the intermediate language, Dalvik bytecode, into a system-dependent binary. The whole code of the app will be pre-compiled during install (once), thus removing the lag that we see when we open an app on our device. With no need for JIT compilation, the code should execute much faster.

Except for the potential speed increase, the use of ART can provide an important secondary benefit. As ART runs app machine code directly (native execution), it doesn't hit the CPU as hard as just-in-time code compiling on Dalvik. Less CPU usage results in less battery drain, which is a big plus for portable devices in general."

Hope that helps,

NT
[TouchPad Development] johnbelloh:
NT - Thanks for the primmer on Android. Times and names have changed over the years but the concepts are the same. Back in ancient times I programmed with interpretive code in "BASIC" and compiled code on "COBOL".

I went back and read the Evervolv 7 thread. I also tried resizing both system and cache muliple times and I really don't see any difference in performance. I wonder if their code has to change to take advantage of more memory? Your point about portable devices is well taken. They are probably coding to fit in limited space and use less battery power. I actully am running on this rom with double the recommended cache. I have it set right now at 400 instead of 200. If the system doesn't take advantage of the extra space I would suggest they make it a peformance parameter. The larger apps sure look like they are strugling with not enough memory. I have a full suite including most of the larger Google apps installed. I am impressed that I have yet to find a bug or feature that does not work as long as you have the patience of a saint to wait for them to execute. If they solve this problem we are looking at a dynamite system. Just my two cents. Thanks for listening to an old dog.

John
[TouchPad Development] nevertells2:
Speaking of old dogs, the tablet we are using is definitely an old dog that only has 1 gig of ram. As time has passed I'm sure developers are writing code that puts a heavy strain on that limited amount of memory thus we see slower execution. Most newer devices come with two or three gigs of ram. Most programmers today are lazy and don't write the nice tight code like was done years ago when memory was limited. I also suspect that our old dog's six year old video processor does not have the power needed to quickly run today's more processor hungry programs. It's still a great tablet and had Nougat running on it before Google's Nexus and Pixle devices did. And how many other manufacturer's devices do you know of that have Nougat?

NT
[TouchPad Development] kusumacdr:
I have hp7 voice tab any 5.0 lollipop ROM for this please help me
[TouchPad Development] nevertells2:
Google is your friend pal. Try it, it's easy.

NT
[TouchPad Development] middle_road:
Would anyone know where I might find a link to the last version of milaq's cm-12?

Milaq's download section is empty.

I'm trying to use one of mine for controlling a hunk of machinery. 7 just keeps acting up on me.

It is me an not the release of 7.1.x

Thanks,

_Dan
[TouchPad Development] Moody66:
Once the reboots gets fixed this will be one hell of a ROM.
[TouchPad Development] nevertells2:
It's a 100% Android Runtime build now, so first boot takes a very long time. Subsequent boots should be normal. From what I have read, your experience is very normal. Patience is the name of the game. I would hate to see what happens if someone forced a reboot in the middle of that 30+ minutes. :(

NT
[TouchPad Development] Cosmic Ranger:
Fantastic ROM

Loaded this on my TP yesterday to replace an Evervolv 4.4.2 build (which was great). Absolutely fantastic! Great speed and stable for what I do with my TP. Thanks to the devs!!
[TouchPad Development] Mchasard:
Many thanks milaq for this lollipop ROM.... I was before under evervolv 5.0 and im surprise by the smooth of this cyanogen ... Really good job
[TouchPad Development] googlephone:
Update:

Today I upgraded the 20150124 nightly. I did the same things as last time when I upgraded from jcs cm11 20150113 build: wipe cache, wipe dalvik cache, format system. This time it takes only 4 minutes to pass the spinning screen (I noticed that we have new boot animation), and a total of 18 minutes to finish boot up.

I have the same hundred apps.

So maybe milaq made something magic to speed up the boot process.

BTW: Cyanogenmod clearly claimed that from cm11 build after M12, no clean install is required to upgrade to cm12. So no data reset is needed if you have the latest cm11 build (later than cm11 milestone 12).

---------- Post added at 12:08 PM ---------- Previous post was at 11:58 AM ----------

Milaq, does your rom force the system to 800MB?

I resized my system to 1024MB, but after flashing your rom, the system reduced to 800MB.

I went back and resize my system to 1024MB again, then reflashed your rom again, then the system size was reduced to 800MB again.
[TouchPad Development] nevertells2:
He probably put something in his install script to avoid folks having issues since LL needs at least 800mb. At least it's easy enough to change with TPTB. :good:

NT
[TouchPad Development] futurepr0n:
uh oh.. so I was trying to upgrade from a 4.1 (I believe it was a 'toasty' rom or something) I thought everything was going to be ok because I had 1.3gb for the android partition and I was able to upgrade my cwm from the link on the first page. So anyways, I was looking at the guy on page 3 who said he wiped cache, dalvik and formatted /system - so I assumed these 3 steps were a pre-requisite. Once I went to install the zip after doing all three I had an error that said installation aborted.

I am stuck hanging when I try to reboot (so I guess my old system is a loss). Is there any chance I can recover from this some how? Was I not supposed to install like that? I didn't have this datamedia thing before, and all of a sudden after the CWM update my storage sd card was slightly different than before - Did that somehow corrupt?
[TouchPad Development] googlephone:
You need to go back and read on what data media is before you flash any data media roms. You need to resize the android system partition to at least 800mb and possibly also increase the android data partition (the 1.3gb you were talking about is the data partition, not system partition).
[TouchPad Development] futurepr0n:
OK so in realizing I mucked that up for the moment, can you comment on whether or not I've completely ruined things or help me understand my roadmap to recovery at this time? I had read briefly over that section before beginning the attempt, I didn't realize I was making a mistake. When I was about to use the resize android through the jscullins tp toolbox it was showing me 1300 mb on what I thought was my android partition. Now I cannot run repair (fsck) through his tool.. I can get into cwm and use webos recovery to get to the toolbox again but from here I'm worried I am not going to be able to fix.

Thanks
[TouchPad Development] googlephone:
Nothing is ruined. You can read the touchpad toolbox thread by jcs, and use touchpad toolbox to do the resizing and install the rom.

Maybe you need to completely uninstall android first, follow the instructions. You can uninstall android with ACMEUninstaller, or use touchpad toolbox to remove webos and android together.
[TouchPad Development] futurepr0n:
Alright thanks. I was trying to upgrade from 4.1.2 jb to lollipop.. I will try and see about reading through the thread suggested. I did put some considerable time there yesterday, I'm worried to do the complete refresh which removes all oses, if that removes webos and android I'm boned aren't I? Sorry to clutter up this thread its not my intention, I just am really lost and googling the errors hasn't turned up any similar touchpad related problems similar to mine. I realize the android on touchpad community is pretty small - and those who've taken the similar upgrade to lollipop path - even smaller.
[TouchPad Development] Atari-San:
When you use the TP Toolbox, it litteraly erase everything on the toolbox, after this, it will create the android partition, it will ask after for plugin the usb cable on your PC and transfer the android roms you want to install and the gapp and a recovery of your choose which support lollipop (read the tp toolbox OP for knowing which one you need). Then, it will install everything. Don't forget to make it charge full and wipe the A4 Battery Firmware from the TP Toolbox. The first boot might take 15min to 30min before you see the setting screen, don't panic, it's just not the same style of managing the cache. Setup your TP Touchpad on Android, when finish, leave it 5min sitting and reboot it (seem it's recommended on some news maker of XDA).

Remember, you will lose WebOS and you cannot install it anymore. You can also remove the old shared partition if it's not doing it already. If it don't, i will post the procedure again. Finally, because the Touchpad's a very old device and the battery start to get some unworking or low charge sector, i recommand to install a certain app from the play store but it got removed, idk why. So i will leave the name there because it made a great job on my device but it might not be safe, it's called "com.BoshBashStudios.batterydoctorrepair"
[TouchPad Development] Moody66:
Can always go back and install webos.
[TouchPad Development] puhleez:
Navigation buttons are partially off the screen (too far to the right) in landscape mode for the 1/30 release... anyone else seeing this? How to fix? probably DPI setting?
[TouchPad Development] futurepr0n:
I was getting some reboots as the play store was trying to download/install Chrome. I am on the 01/29 Nightly. I am not sure if Wifi issues were responsible. I do know that I have experienced some flakiness though with Wifi. Usually turning it off and on (the wifi) will resolve the problem.

Also "Reddit Now" my reddit reader is unable to load up, crashes nonstop. Everything else seems to have no real struggles.. I can run plex, some games (solotaire), chrome, dolphin browser hd, VNC (but crashes the odd time citing "SDK" licence issue?).

Im super pumped to continue testing this ROM. Thank you for helping extend the life of my TP yet again!! You developers are amazing.

edit: Bluetooth doesn't appear to be working either. Cannot pair properly with Microsoft wedge bt kb, bluetooth service will stop before paired successfully
[TouchPad Development] hasei:
I have the same issue with the same release.
[TouchPad Development] Torqd505:
So do I. OK in portrait but messed up in landscape.
[TouchPad Development] nARMstrong20:
Would changing the launcher possibly help with the whole navigation bar thing? Also, I've asked this several times on the Q&A thread, but I thought I'd ask again, is this ROM supposed to read both SD cards? I have been unable to get both sd cards read, although ClockworkMod does read the other SD card, so it is there. Am I doing something wrong, or is milaq's build not built to read the other card?