yashsingh1/xdaforums huggingface dataset:
[TouchPad Development] vik5:
I was on jcsull. Cm11 4.2 no issue with sod now when I change to cm11 4.4.4 I have sod and battery drain on my both tp same rom, yest I put milaq cm11 4.4.4 on 1off them I think no sod issue only netfix issue which they have hack and now netflix working fine but i will reply if i got sod and battery drain .I always clean instal .I was reading about sod some one mention change launcher to nova i install yest on this rom hope it solve the prob I will check to night. May be my touchpad acting i will check but great work guys because Off your hard work we can instal android on touchpad all dev working on rom thanks .
[TouchPad Development] gnuts:
No news on that, but the 7/30 build really ruined things for me. Constant SOD, not charging on touchstone and sound issues. Much worse that 7/22 where things were working well. Going to downgrade if no new build soon
[TouchPad Development] vik5:
Go to setting and lock screen choose none and from play store installed nova launcher make it default I did the same thing yest. And uptill now no sod issue, try it
[TouchPad Development] vik5:
I have noticed when I plug the touchpad for charging I will get sod .I will try A6 from hptoolbox ,I think it will solve the problem
[TouchPad Development] esqueue:
I've tested this rom and I have some issues with it. The tablet will not last a whole day off the charger, it will fall into a deep sleep 100% of the time and the sound would always stop working requiring a restart.. This is the second most unstable rom I've used since the CM7 alphas.

I had jcsullins which lasted a few days and didn't lock up almost every time I dock it but just wanted to test out roms.

Thanks for the work that you guys do. Keep up the work and I'm sure that this rom will get better in time.
[TouchPad Development] mschumacher69:
Try milaq's nightlies...
[TouchPad Development] McBeanTIO:
New ROMs are up....

I have not tested these yet, but it looks like ROMs are coming out again. See OP for updated download link.

Posting here for convenience as well: http://www.invisiblek.org/roms/cm-11.0/tenderloin/

(Have not tested yet, but will test tonight.)

--McBean
[TouchPad Development] vinukondamahesh:
is there any way to move app to sd card ,I am not able to install app due to low space
[TouchPad Development] mschumacher69:
What kind of partitioning scheme are you using? Use tptoolbox to re-size your partitions and make the data partition the largest. You wouldn't have a low space problem anymore...
[TouchPad Development] vik5:
I install new update from 8/25 to 8/29i cannot download from play store error 491 and from website also I tried everything than I went to back 8/25 wipe delvik and wipe cache part. Now I can download back to normal pls look in to it .pls tell me if any 1having this issue
[TouchPad Development] xamievilx:
i tried the 8/31 one earlier today and experienced the same thing...eventually went back to what i had been on previously...
[TouchPad Development] vik5:
Anyone did the new update and can u pls check if u can download from play store or u get error
[TouchPad Development] Jinjur:
Hey guys, couple of questions.........

just flashed the latest (i think) version of this onto my tp - cm-11-20140821-UNOFFICIAL-3.4_kernel-tenderloin.zip

firstly.....i cant see anywhere to add home screens, am i missing something?

also, couldnt find any overclocking built in so had to use antutu.......OC was included in an older version of JB i had and thought it was in this, no?

Jinj
[TouchPad Development] mschumacher69:
Hold an app or a widget and drag it to the right, it would create a new home screen.
[TouchPad Development] Jinjur:
Thank you.....i see now.

ONLY to the right. Dragging to the left does **** all :)

Also sussed the OC question, dev mode had to be enabled and i couldnt work out where to do that.

Connected a usb cable to computer and was present with the options. All good :D

Apart from Netflix being bucked, lovely release.

Thanks

A
[TouchPad Development] vik5:
I did update still same problem can download 09/03 it was fine 08/25 pls fix this probl

---------- Post added at 11:46 PM ---------- Previous post was at 11:43 PM ----------

I download the latest update but I can't download from browser or play store 491 error on play store last working update 8/25
[TouchPad Development] Jinjur:
I am currently running cm-11-20140821-UNOFFICIAL-3.4_kernel-tenderloin.zip installed using the TP Toolbox.

I want to drop cm-11-20140903-UNOFFICIAL-3.4_kernel-tenderloin.zip onto it, what is the best way to do this? I used to use CWM before, is that ok?

J
[TouchPad Development] mschumacher69:
Yes it is, just flash it through recovery (cwm or twrp) then wipe dalvik and cache.
[TouchPad Development] vik5:
Can anyone check 09/04 update if anyone can update or download any app from play store or it give u error

.8/25 working good
[TouchPad Development] miji2:
9/05 still has the problem. It's not just a Play store problem. I can't download anything using Browser or Chrome either. There is something wrong with temp storage on these builds. It's definitely baked into the ROM since even full wipe + system and installing just the bare ROM does not fix the issue.

However, BSOD seem absent since i have not seen one since last week.

BTW, anyone has 8/25 they can upload somewhere? It already rolled off the build archive on nvisiblek.org
[TouchPad Development] vik5:
Yes u can't download anything .I went back to 8/25 and if anyone get error go to setting- aps than choose all , than go to media storage clear cache and data
[TouchPad Development] mschumacher69:
Why don't you guys use [MENTION=1594835]milaq[/MENTION]'s builds? They seem to be more stable with fewer issues...
[TouchPad Development] shumash:
The download errors are fixed by jcsullins here http://xdaforums.com/showpost.php?p=55243500&postcount=289

Invisiblek will need to cherry-pick because it's not yet merged.
[TouchPad Development] invisiblek:
nvm...
[TouchPad Development] vinukondamahesh:
is this rom support otg cable?
[TouchPad Development] blmvxer:
I haven't used my HP Touchpad w/CM 11 in a couple months due to sluggish performance with Linux 3.4 kernel port. But today I decided to boot it up and update to today's nightly.

And wow this has gotten a lot faster!!!
[TouchPad Development] lirff:
Great Roms

Thanks Invisiblek, moved over from the great Milaq a few months ago, pleased I did and thanks Milaq

Got your last rom from last week, sooooo stable, looking forward to the future with CM12

Please keep up your good work

regards

Lirff
[TouchPad Development] Ajfink:
Trying to kang out a build and "scorpion" isn't being recognized as a valid cpu target. Thoughts, anyone?
[TouchPad Development] shumash:
use 'generic' or 'cortex-a8'
[TouchPad Development] galyenrc:
Am I missing a post or something or has a download link changed... I don't see anything newer than 11/09?
[TouchPad Development] invisiblek:
Since development on cm-11.0 has slowed to a snail's pace, you're not missing out on much. I've been focusing on cm-12.0 for all my devices. I'll probably roll another cm-11.0 at some point, but expect 12's pretty soon.
[TouchPad Development] vinukondamahesh:
I installed latest rom20141109,from 20140920,its taking lots of time to change than old rom in fact it's very quick in old rom..... Can anyone tell me it's happened only me??
[TouchPad Development] Ajfink:
I tried running a cm12 build out of your repos and it choked up on:

make: *** No rule to make target `/home/ajf/android/system/out/host/linux-x86/bin/mkimage', needed by `/home/ajf/android/system/out/target/product/tenderloin/boot.img'. Stop.

Any ideas what I should define in build.mk to generate this guy?
[TouchPad Development] shumash:
For some reason, the host files are not compiled when compiling tenderloin. You have to get the out/host/linux-x86/bin tools from a successful build, create the folder(s) and copy them into it. You can use this one:

https://www.androidfilehost.com/?fid=95832962473397823

Invisiblek can probably provide the info necessary to get the host files to build, but until then, you will have to copy those again each time you do a clean or clobber.
[TouchPad Development] derproblembaer:
A first CM 12.0 build appeared:

http://www.invisiblek.org/roms/cm-12.0/tenderloin/

Who is eager to try it?
[TouchPad Development] vinukondamahesh:
tryied its not installing may be need use some different recovery....
[TouchPad Development] gradular:
What recovery did you use?
[TouchPad Development] vinukondamahesh:
i used --PhilZ Clockworkmod 6.0.4.7

wen i am installing i got error so i tried recover from my backup i got black screen written in center of the screen as "www.palm.com/rom" now dont knw wat to do.............
[TouchPad Development] jerryatherton:
I tried it. I first tried to install Flintmans Twrp 2.8.3.0 and it wouldnt install. Then i tried to inatall with the 2.7.1 that was onthat machine and it wouldnt install. There may be a problem on that machine. Sent from my HP Touchpad running Evervolv Lollipop 5.0
[TouchPad Development] gradular:
You need to tell us what errors you getting or we can't help solve the issue.

Also do a full wipe in toolbox to get rid of all traces of evervolv or it won't install properly.
[TouchPad Development] jerryatherton:
I first tried to install on a CM machine. I also tried to install on a Evervolv 5.0 machine. Neither worked. Later on I will do it again and get recovery logs.
[TouchPad Development] derproblembaer:
It works for me. It's a little ruff and many settings from CM11 are missing but it's pretty usable for me.

My Settings:

- latest TWRP from flintman

- 800 MB system size (probably too big)

- full wipe

- latest PA Nano Gapps

It was stuck in a loop on first boot but then worked after a 3-button-reset. The fonts are looking worse than in CM11 on 120 DPI.
[TouchPad Development] jerryatherton:
Failed recovery log:

https://docs.google.com/file/d/0BxHG4DOa38sAUUlCdnN2MW5LX0k/edit?usp=docslist_api
[TouchPad Development] tjsooley:
Does anyone else have issues with video playback only in netflix?
[TouchPad Development] shumash:
invisiblek hasn't officially released cm-12.0, so discussing it here simply pollutes the cm-11.0 thread. If you want to discuss your issues in the hope that he will respond, one of you create a discussion thread elsewhere.
[TouchPad Development] jerryatherton:
I agree, I should have known better. I am sure he will let us know when its ready.

Sent from my HP Touchpad running Evervolv Lollipop 5.0
[TouchPad Development] nevertells2:
So where is that new CM12 thread you were going to start? :D

NT
[TouchPad Development] jerryatherton:
I don't start threads and don't recall saying i was going to. Inviblek started one. His ROM runs great.

Sent from my HP Touchpad running Evervolv Lollipop 5.0
[TouchPad Development] nevertells2:
Well, today I have something new to report. One of our users has created a method of installing newer versions of Android, Gapps and recovery that J.C. Sullin's TouchPad Toolbox can't do. I'm not going to explain how it works here, you are just going to have to go to the link below and read for yourself, OH, there is a video too!!!!

https://xdaforums.com/hp-touchpad/general/rom-guide-alternative-method-to-install-t3575861

And be sure to thank DoubleStuff for his hard work!

NT
[TouchPad Development] nevertells2:
First off, thanks for jumping in and adding your expertise to this Rom. But I have to ask a couple of questions.

I watch Milaq's threads and all the problems people have with his data/media builds. When I saw your first CM11 build that was not data/media, I said to myself, hallelujah, we'll have a CM11 that is easy to install. The TouchPad is not a phone and in not a single operating system setup like every other device available. Could you please explain why it is so important to make it a data/media build? Flintman is keeping his like it has been on the TouchPad since the beginning and it seems to be working out fine and only requires enlarging the /system partition.

No flaming please, I am not knocking Milaq's builds. He has done a great job. But with all the headaches that seem to come with a data/media build such as problems installing apps from the Play Store, apps can't find their data, having to modify several partitions with Tailor which requires the user to figure out how to install it in WebOS using Preware.(I wonder how many folks have never done that before?) And running Tailor comes with it's own issues as there is not a lot of information around about how to run it and folks panic if they get errors. One has to use a special version of CWM and don't forget Selinux support on top of all this.

And what do they do if they want to uninstall a data/media build? I don't see instructions in Milaq's OP or yours on how to do that. You got to remember, the folks that are going to try to install your build are not a rocket scientist like yourself. I've already seen that question asked at least once already.

Lastly, I'm wondering if it would be that big of a deal to build a non-data/media build along side of this one? I know you guys do this for the challenge and satisfaction of helping others out. I'm just thinking about the average user who finds your build and is totally unprepared for the issues of a data/media build. Hope you will consider a separate build, but if it's too much of a headache, I understand.

Just a thought, if someone could create an ACMEInstaller that takes care of setting all the partition sizes to the recommended sizes for a data/media build and an uninstaller that removes them that would be great.

Thanks
[TouchPad Development] aicjofs:
Set the governor to performance, suffer the bad battery life. I'm suprised so few people have reported this as an issue. Made me wonder if it's just mine.

It's all really a matter of opinion, and depends on who you ask if you judge by the "poll" posted a while back. Personally I love it, brings flexibility. Previously if you had a 16GB for stuff and 4GB for data, and 12GB for media you were locked in to that partition structure for Device X. If a person loved to install games they ran out of data space and had all this wasted space for media. Or go the other way and have 12GB for data and 4GB. The person that has a ton of music is upset they have no room on the device. If you make all the 16GB available for either by making media in the data partition everyone is happy, and get to use every last byte that is free. Well except media is formatted ext, so fuse is need to emulate fat. It's a fantastic tradeoff and why google went that direction. I completely understand your points, it's complicated to setup, if you want to switch back it's complicated. IMO the only people it hurts are those that still use WebOS. Personally I just see it as moving forward, OSes grow in size, ports go away(serial port), buses go away(ISA), the TP is aged and so it too is best changed by sticking with how the mainline development sees the future. That's my opinion, but I do understand and respect your question.
[TouchPad Development] nevertells2:
I guess you were not aware that J.C. Sullins created a process where by one could enlarge their data partition. It took the needed space from the SD card/media partition in up to 2048 chunks. If you applied the patch a second time, you ended up with 5.48 GB in data for all those games..

I'm not particularly happy that when you rob such a large chunk from the media partition to give it to data, that shorts the WebOS side. Who knows what kind of issues that is going to cause. This would all be fine if the TouchPad only had Android installed. Everything file wise you put in the Android data partition is hidden from WebOS like music, video and such.

You are forgetting the people it hurts, the poor guys who try to install this and screw up their TP.

You mention that the TP is aged. Android has been installed the old way from the beginning and now this far into it's life cycle seems kind of pointless to change to a complicated, landmine ridden process. I suppose the whole point would be moot if a non-data/media version were available too. Just sayin'.:D
[TouchPad Development] GnatGoSplat:
I'm having the same issue with the 12/31 build.

Also seems to be having trouble with home button wake and reboot seems to be shutting down (or going into SoD).

Google Voice app and Play Store were also both FC'ing.

Gmail and Browser work well though, no more black boxes.
[TouchPad Development] googlephone:
Datamedia has benefits but currently has compatibility issues, instability and difficulty to setup.

There are reports saying the datamedia recovery wipes the USB storage which would be nightmare if u didn't back up the whole touchpad data.

If let me choose, I would CURRENTLY weigh stability and compatibility over the datamedia benefit until datamedia becomes more stable and reliable.

Speaking of the poll carried by milaq, it's not a fair poll from statistical base. Average users don't follow every single thread in this forum. Some people maybe don't even look at the first post of thread. Most people voted are experienced users who follow the development of touchpad regularly, and who don't stand for the majority of touchpad users.
[TouchPad Development] puhleez:
Having trouble with wifi after screen off for a period of time. It disconnects (appears to turn off) and just hangs trying to turn back on. Already turned off wifi optimization. Any suggestions? Or just me?
[TouchPad Development] reynoben:
Netflix and OC CPU

Installed this last night. Had a few reboots when I shut the screen off, which as odd. The big things I found was with Netflix and the Max CPU. When playing any video in netflix, only the top 1/3 of the picture was clear. The rest was kind of grayed out with lines going through it. Also I could not overclock the CPU. In fact I believe the max was 1.18. In previous CMs I could OC to 1.78.
[TouchPad Development] jerryatherton:
Same problem. Have to reboot to reconnect.
[TouchPad Development] jack901:
if the way forward is data/media (which it is).people will that do not like it can stay on 4.2 and be thankful some brought us this far.and the others will gladly move forward.

devs are doing this because they want to and enjoy seeing if it can be done. but to say lets make 2 versions is unrealistic.when it goes beyond skill levels should just stay where comfortable. others will learn or try if they want to go beyond.

but to clutter up a thread about how abouts and whys is not the way. putting alot of time and thought and the best way to make it easier to go forward is the way to do it.

not to be a slam or whatever but I know there are not alot who read posts or understand but its like that in every other aspect too.

I did the data/media and went back and all I did was go down a clockworkmod release and re flashed 4.2 and as of yet seen no issues.webos have not been in it since android was avail. I know some use it still but that is where they have to make the decision to move forward or stay put.4,2 is just great and all works so what else is there?

I am just greatful we still have devs!!!!!!! thanks guys.
[TouchPad Development] googlephone:
With the new datamedia recovery (6.0.4.5?), you can't go down to a non datamedia cwm by flashing a zip in recovery. Like I said, there are problems with datamedia structure on our touchpad like compatibility issues and unreliability. For me, it's not the difficulty or datamedia structure itself but the compatibility and unreliability specified to touchpad preventing me to use datamedia.

The problems are not from datamedia structure itself. I have datamedia structure on Samsung s2, s3 without problems.

I am still on cm10.1 as an advanced android user with more then 10 android devices and flashing a lot on all of them and wait the devs iron out the problems with datamedia. Datamedia on touchpad should be more mature before average users move forward.
[TouchPad Development] nevertells2:
My feeling also. I would like to hear a response from Invisiblek on this. How about guy?
[TouchPad Development] invisiblek:
What 'problems' are we seeing with datamedia roms? Other than the fact that people are too lazy to switch over to it? I don't see any.

I'm not going to maintain two branches/builds but that doesn't stop anyone else from doing it.

I don't understand the remarks of it having "compatibility issues and unreliability". Simply not true.
[TouchPad Development] googlephone:
The reports I have seen about the compatibility and unreliablitity are:

datamedia recovery wipes some folders in the usb storage, even two reports saying it wipes the whole usb storage.

unmounting issue in recovery, some people had problems seeing contents or mount sdcard in recovery.

some apps are not working well,

can not revert back to non-datamedia recovery in datamedia recovery(at least for cwm 6.0.4.5), have to push or use rootexplorer.

These issues seem like from the datamedia recovery, not the datamedia structure itself.

Besides these, it is too much work to go back to previous non-datamedia roms or switch between cm11 and Evolv's AOSP builds. Considering the cm11 rom is not fully working or stable currently, users may want to go back to previous roms (like cm10.1 which is quite stable and fully working) after trying test build. When cm11 is stable and fully working, there will be no need to go back to old versions lick cm10.1 then everyone should move to datamedia.

For migration, it is always better to be smoothly move with buffer than jumping.

I understand and respect your opinion and it is your call. Thank you for your developement. Happy new year.
[TouchPad Development] jack901:
I set up the data/media 11 and when I seen it was not so stable I flashed the cwmod recover and then flashed skz tenderloin 4. with no issues or if you do a nandroind before you change you can restore the nandroid with no issues as I have done it.if its that big a deal I would stay on 4.2 and you will be happy. even worse you are going by other reports and not trying it yourself.they have brought the tp so far and want to go further and you sound like you should stay where you are. we are lucky any developer is moving forward and no way are they going to spend their time maintaing 2 dif builds.

thank you devs again!
[TouchPad Development] nevertells2:
So people's reports of SOD's, random reboots, WiFi unreliability, crashing when playing videos, Netflix crashing, disappearing app icons, home button not working, apps can't find their data because it's in he wrong partition, and everything Googlephone said are not problems?

I understand if you don't want to maintain two branches, that was just a probative question. Your are the developer and get to do it the way you want.

Why do you say people are too lazy to switch? What about the difficulty of setting up a TouchPad that the average user is not technically qualified for? What about the concerns of setting up a TouchPad if one wants to go back to a non-data/media build? Take all that and the problems/issues already mentioned, would be enough to scare off the average user, not make him lazy.

And thanks for really reading my post and addressing some of the issues I mentioned.:(

I know, you're a developer who has a better understanding of all of this and may not see it the same way as an average user.

But like I said, your are the developer, so press on the way you want. Good luck with your efforts.
[TouchPad Development] googlephone:
I tried and didn't have the issues I listed in my previous post which I just list what other uses have experienced. It doesn't mean I didn't try it.

As an advanced android users with devices from HTC G1, HTC HD2, NOOK, galaxy S2, S3, note3, touchpads, I don't have any problems with flashing. Just speak for average users, not for myself.