yashsingh1/xdaforums huggingface dataset:
[TouchPad Development] jack901:
it is early in the game just like it was when the first roms came out. there were issues there too but they found and fixed them.but too bring this up to a dev and say I speak for the avg touchpad user well stay on what works for you.if you want new and cool go by a device that it was meant for not harangue a developer to "think of the children" . there are all sorts of tutorials out there.if they want to move forward they can read.and ask questions in the tutorial threads not clutter up dev rom post does this work are we going to do this etc. what happened to the 2 week rule? alot of people seem to be entitled to a devs answer or future plans. if you do not like it release your own rom the way you want it done.

me I am glad we have devs that want to push ahead.we hae already lost some good ones to demand of user guess all will be happy when there are no more.we had a doomed from the start device the only reason we have them is because of the fire sale.yet we have some great devs trying to get more out of the engine that could and get us in line for future stuff that will bring the latest versions to our devices. how many other devices can even say that? be happy with what you have for what you spent.
[TouchPad Development] graffix31:
long story short if you follow the directions you wont have any problems. if your worried about losing everything what is wrong with you. if your flashing android on an hp touchpad for webos and not backing up before you do what are you doing. not to mention all of this kitkat stuff is super experimental. seems like people are cowboys on these threads flashing away with no real knowledge of whats going on. i dont claim to be an expert at all. far from it really. but i read read read and back up before i do anything. i havent had a single issue. i personally like the date media builds. people have been asking for a way to get rid of webos and i think this is closest we will ever get.

i dont mean to come off harsh, nevertells i have seen you around forever. just saying hacking the touchpad is really not for the faint of heart. i think our amazing devs have done a great job of making it as easy as possible.

thanks for all the work on the 3.x kernel guys. getting official cm11 would be quite the accomplishment.
[TouchPad Development] RolandDeschain79:
Hi Invisiblek,

I have been enjoying your previous builds and I'm very happy to see you starting threads and continuing development for the HP Touchpad. I was also hoping to see you add Bluetooth support to your CM10.2 builds. Its really nice to see alternative non data media builds of CyanogenMod for the HP Touchpad. Many new or inexperienced users find the necessary changes too complicated for them or have an issue and want to revert to a previous build. People tend to leap before they look and very often they don't bother reading the instructions at all, no matter how clearly they're laid out.

I can also confirm the problems Googlephone has listed as I have heard many similar reports from users on YouTube and Rootzwiki. It should be noted that the majority of new users who encounter issues are unable to report them in the XDA development section due to the post restrictions for new users.

There are many problems encountered during the partition changing that are troubling users.Tailor is a particularly problematic app, there have been many reported problems after attempting to use it. It would be much safer to have an ACMEInstaller that can make and unmake these changes without the frequent users error issues. Its true that many users are lazy and do not fully read the information before installing things. Also there is some confusion over what the WebOS doctor does and many users run into problems simply because the don't uninstall Android before running it. They seem to think they need to run the Doctor in order to do a clean install and make these partition changes.

These are not issues caused by data media Roms in anyway but are a consequences of not having a good and easy method of installing or removing them if issues are encountered. If we had an ACMEInstaller/Uninstaller to make these changes, a cmisntall package could be created and a proper install would equip the average users with everything they need to enjoy these fine Roms without issue.

I have nothing against data media builds and fully understand why developers want to go in this direction but I think the reported problems are a valid concern. Thank you for helping to develop the 3.4 Kernel for our TouchPads, I have nothing but respect for all our talented tenderloin developers.
[TouchPad Development] k4ever:
All, I tried one of milaq's data/media ROMs and had all the problems nevertell listed. I followed all of the installation instructions to the letter. I had reboots when I tried to play videos. Most of my apps would not install when Google Play did its recovery. Some of the apps that I got to install uninstalled themselves on reboot. I immediately went back to 4.2.2. I then tried invisiblek's cm11 ROM because I thought it was a non-data/media ROM and spent the whole day after Christmas borking my Touchpad. I'm now running 4.3 and waiting cautiously until 4.4 ROMs are more stable.

People are having real issues with the data/media set-up on the Touchpad. It may not be you and if it is not consider yourself one of the lucky ones. Even Roland has a warning next to the data/media ROMs in his threads. The fact that we still have ROMs with the old format confuses the issue even more.

I believe that it is counter productive to argue with someone who is voicing his/her concerns about an issue that effects the usefulness of a ROM in a thread that was made to address issues with a ROM. If it is too much trouble to maintain two ROMs with different file structures, then so be it. Most of us will just wait until the data/media ROMs become more stable or better (failsafe) instructions are posted. Nobody likes to spend a whole day recovering lost data...
[TouchPad Development] RolandDeschain79:
Sorry k4ever, that might be my fault because Invisiblek does have a non Data media CM11 build but now that i'm checking my thread I can see why that is confusing. Thank you for reporting your experiences with the Roms, in a fair and informative manner. I will have to fix my posts now, sorry for any confusion I might have caused you. No one wants to spend all day fixing their favorite tablet:o
[TouchPad Development] k4ever:
Roland, no sweat. Thank you for taking the time to put together detailed instructions on how to install the various Touchpad ROMs out there. I really enjoy your posts and videos.

Thank you also, invisiblek and all the developers who have worked hard to bring the latest versions of Android to our Touchpads. Hopefully as more people post their experiences with CM11 the various problems with stability and data/media will get resolved.
[TouchPad Development] invisiblek:
Stability fix in the next build. Reverted a patch for audio wakelocks that wasn't working as expected. Should fix the sleeps of death we've been seeing.

Also - I switched to using the ath6kl (wifi) driver that's in the 3.4 kernel rather than the 3.10 backport driver we've been using

This has a few advantages:

1) much easier to maintain and build it

2) wifi optimization works, (it re-connects after waking the device)

3) less repos to keep track of (ricardo will like forking less repos)

Umm, that's all I can think of for right now....enjoy =)
[TouchPad Development] vinukondamahesh:
after reading all your post ...whether i am eligible person to react i dont knw

as average user i can say one thing if we want to install cm9 ..we create folder keep all 4 file and change to recovery mod givesome command ...

like that if someone create file to install a datamedia rom it will very usefull i dont hom much pain need for dev create ..just asking???? are Idiots Guide from starting to end....
[TouchPad Development] BUFUMAN:
Sry but i cant install this rom i am on datamedia cwm i get that install error "status 7"

With 600mb partion .......

Pls help normal cm 11 is really buggy with black screen .....

Gesendet von meinem SM-N9005 mit Tapatalk 2
[TouchPad Development] allstar319:
You need to use a SELinux supported recovery. There's one in the first post in this thread that you can use.
[TouchPad Development] BUFUMAN:
Thank you! Installation as usaul@ cwm with Flashable zip?

Ok i found it thank you very much!!!!

Gesendet von meinem SM-N9005 mit Tapatalk 2
[TouchPad Development] allstar319:
Yep, reboot after flashing the flashable zip, then install the rom.
[TouchPad Development] GnatGoSplat:
I had most of those problems with both Invisiblek's CM11 w/3.4 kernel and milaq's CM11 w/3.0 kernel. However, I had milaq's CM10.2 on my Touchpad and still have it on my wife's. It was rock-solid stable on both, and my wife uses her Touchpad all day long.

I'm almost certain the issues are CM11 and/or new kernel related and have nothing to do with the datamedia setup itself. Datamedia is how all modern Android devices do things.
[TouchPad Development] BUFUMAN:
thx everything so far.

but i cant load the files from ex_sdcard. ex_card not mount.

i checked the filesystem with tailor everything fine.

i can only see /0/clockworkmod [MENTION=969149]cwm[/MENTION]. @ Win there is no folder like /0/clockworkmod....:eek:
[TouchPad Development] Moody66:
That's the issue with data media.. U will have to drag it to a folder flash can access.
[TouchPad Development] BUFUMAN:
hmm but i dont see that folder @ Win. thats my problem

ok i would say i fu**ed up my touchpad.....

cant find any information about my problem
[TouchPad Development] arky33:
I had the same problem trying to flash Milaq's roms (see http://xdaforums.com/showpost.php?p=49021456&postcount=436). As an other user suggested, it was probably a recovery problem. I ended up flashing an older (working) recovery & rom via ACME, before upgrading to the newer recovery posted by Invisiblek at the step 2 of the instructions (the flashable zip).
[TouchPad Development] GnatGoSplat:
Did a clean install of the 1/3 build and Gapps 12/8 from the OP link. Gmail and Browser works, but I can't get Play Store to work. It says "No connection" with a Retry button. Also doesn't wake using Home button.
[TouchPad Development] jaltman:
The latest nightly build, 0104 seems to be bad. Twice downloaded, won't install. Musta been a bump in the process. FYI. Thanks to all for the hard work going into this. Great fun playing.
[TouchPad Development] jerryatherton:
Same here, have downloaded twice and 01/04 will not install.
[TouchPad Development] McBeanTIO:
I have had similar experience with this build. I get a very eradic network connectivity, and any app installs result in an error 920. Seeing the notes that 0104 is borked makes me think I need to roll back to an earlier build for the meantime.

--McBean
[TouchPad Development] graffix31:
Just installed 1/4 dirty over milaqs 3.0 kernel and everything working great here.
[TouchPad Development] McBeanTIO:
I can echo the 0104 build works to install.

I'm still getting the error 920 on any app install/update. Need to figure out what went to pot and how to fix that. I've seen some comments that it's a permissions issue, but not sure how to resolve specifically on the TouchPad.

--McBean
[TouchPad Development] arky33:
Same thing for me, error 920 keeps coming back, even after clearing caches (whether the Play store cache or the rom cache). I tried disassociating my google account and logging back in, but that won't work either. I am still getting random reboots every 15 minutes or so. A shame because otherwise the rom is very responsive and fast!
[TouchPad Development] invisiblek:
Anyone tested netflix on this thing? I don't have a netflix account but want to know if its working correctly. Thanks.
[TouchPad Development] invisiblek:
I'm looking into the play store issue right now.

The reboot issue I think is related to the microphone (per flintman)

Turn off voice recognition in your launcher, should fix it (if its the same ones I was seeing)
[TouchPad Development] arky33:
Thank you very much, I'm gonna try this right now. Great job on the rom! :good:
[TouchPad Development] puhleez:
Still unable to install 0104. Trying to open it with zip viewer says file is corrupt. Downloaded three times with different browsers. What am I missing? :confused:
[TouchPad Development] invisiblek:
Hard to say.

Here's the md5sum:

091671087ecb8fecf157efbbfd1ede0f cm-11-20140104-UNOFFICIAL-tenderloin.zip

If a zip program says its corrupt, its pretty obvious you have a bad download.

On another note...

The market wifi stuff should be sorted out in tomorrow's build. Props to flintman for finding the fix:

https://github.com/invisiblek/andro...mmit/779cd79a54d7eb9cad8b41cd701b75fd733b4304
[TouchPad Development] murkurie:
Netflix video comes up black and white, and complains about the connection to their servers on the latest data/media build
[TouchPad Development] McBeanTIO:
Thanks for finding this. Alas, I got impatient and nuked my device back to stock. I tried several different iterations of the ROM to clear the 920 error, but was unsuccessful. That's when I decided to blow it all off and start clean again.

Again, thanks to the team for finding the root cause and resolving the 920 issue!

--McBean
[TouchPad Development] McBeanTIO:
In my attempts to nuke my TouchPad back to stock to repair the 920 error, I may have missed something. On my 32-Gig HPTP, I'm only seeing about 27/28 Gig when the device formatted back to pure WebOS. I ran the acmeuninstaller before running WebOS Doctor, but that doesn't appear to have "restored" the partitioned data.

I'll search for answers, but didn't know if someone had seen this and knew how to recover that missing partition space? (I put Tailor back onto my device, but am not seeing some extra partition.)

--McBean
[TouchPad Development] Moody66:
Seems to me that is correct. Webos updated takes up the rest. If memory serves me.
[TouchPad Development] jaltman:
It appears that the bug that prevents the play store from working is also what prevents a good download of the update. I have had to go back to a last known good version ( i had a good copy of 12/27 in my cminstall directory) in order to be able to transfer the 0105 update into the tp and then install that. Keep some of those old nightlies around as without them you might be stuck going back to acmeinstall and whatever is in your cminstall directory. I guess we could go over to webos and transfer a good copy from there too.

As long as I am writing, I note that in the reboot menu reboot shuts off and recovery reboots. Not a big deal, but something to be added to the eventual to-do list.
[TouchPad Development] jerryatherton:
My download from 01/05 was bad just like the 01/04. It is bad when I download it directly to my TP but is fine if I download it to my PC and copy and paste it to the TP it works fine. The WiFi works fine, but I never had a problem before. The playstore works fine, and the shutdown lockup problem is gone.

Thanks for your work.
[TouchPad Development] invisiblek:
Likely related to the wifi bug which has now been fixed. That's the same thing that was happening with the play store (corrupt downloads).
[TouchPad Development] jerryatherton:
Netflix show bottom 1/3 at the top of the screen. It did hook up with the Chromecast and of course the picture is fine there. If there is a log that will help, let me know. I normally do not run Netflix on this machine, so I honestly don't know if it ever worked.
[TouchPad Development] sokratz:
*w00p* I can finally post here!

First, thanks Invisiblek for your work here. Excited to see a new kernel coming together in 2014.

Now a question, is it a known issue that the TP will crash if playing sound and screen goes to sleep? I'm on the 1/5 build.

As for datamedia or not, I don't mind, it's kind of a pain to switch between the two but the user community needs to adapt to where the development is. Maybe another thread could be created again (in a user friendly posting place) for folks to discuss and vote. I'm sure Roland could drive traffic there too. Perhaps some scripts to make the transition back and forth could simplify the process. For me, I keep 1TP on DM and 1 not just for fun.

Thanks,

Sokratz/Froz@RW
[TouchPad Development] graffix31:
Anyone seeing a screen glitch on 1/5? Don't see it all the time. But in Xbox smart glass I get at least one line across the screen sort of pixilated. Other than that seems to be running OK. Really excited about the new kernel. Going to be great when everything is worked out.
[TouchPad Development] xdmx:
finally i can post here... the 10 posts and 5 minutes limit is crazy

i've installed the last build (5/1) and most of the things work. I've found that davdroid and the owncloud news reader unfortunately don't work. When i try to create/connect an account it says i/o error connection went time out... with the 2.4 kernel i got a 403 forbidden error

connecting from another android device with the same apps it works, so i don't think it's a problem on the server or in the app, but probably something in the rom

and btw, thank you all for your awesome work, it's a dream having kitkat on the touchpad!!!
[TouchPad Development] invisiblek:
Try this build:

http://invisiblek.org/tenderloin/roms/cm11.0/dragons/cm-11-20140106-UNOFFICIAL-tenderloin.zip

I updated the ath6kl (wireless) driver a bunch (about 75 commits). Let me know if it works out.
[TouchPad Development] xdmx:
i've upgraded to the 6/1 build, but i still get the timeout error on both apps when i try to connect the account :(

---------- Post added at 05:54 AM ---------- Previous post was at 05:50 AM ----------

i've also just noticed that when the tablet is sleeping, if you press the front button, it doesn't wake up, and sometimes doing so it crash (not showing anything) and then it restarts itself after a while...
[TouchPad Development] invisiblek:
Hmm. Some logs would help. I'd rather not pay for an app in order to try and debug this. If you know of anything free out there that fails too, let me know.
[TouchPad Development] jerryatherton:
I am running the 01/06 build. The play store seems off, it comes up as not responding, I press Wait, it becomes like frozen the up to 5 mins later it does the download.

I also found an app that will not run and it is free in play store. 2XL MX Offroad. It flashes blue screen then black screen.

This does not affect how I use this touchpad, I use it to test different Roms for how they handle the graphics.

Logcat: https://skydrive.live.com/redir?resid=40C8D1F2C97F457!1369&authkey=!AKkNbVBbuHP7W0c&ithint=file,.txt

Thanks for your work.
[TouchPad Development] xdmx:
you can install them both for free from the f-droid market (https://f-droid.org/), it's legal, since they are opensource projects, and that market it's all about opensource apps :)

otherwise at the github repo there is the apk: https://github.com/owncloud/News-Android-App/
[TouchPad Development] sokratz:
Giving some updated info on experience:

I'm on the 1/5 build and notice that the wifi disconnects on sleep and successfully reconnects on wakeup. However, I have the settings set to always on during sleep with wifi optimization turned off.

Google calendar appointments trigger a sound and if the TP is asleep, it'll ZZZZZZZZZZZZZZz and then crash. It was an interesting reminder at 9:30AM ;)
[TouchPad Development] arky33:
Hi!

I'm running your latest 1/6 build and everything is A1 so far! Yesterday I used it heavily reading the news with Currents while multitasking and it was running fine, but the moment it went to sleep it rebooted instead. 3 hours in 1/6, still no random reboot, wifi is good, nothing to report here!

Thank you very much!
[TouchPad Development] allstar319:
I'm still getting SoDs everytime the TP goes to sleep, voice recognition was turned off (I think?), with your build from sometime yesterday (1/6 dragons). Coming from Milaq's 2.6 build anyways if thats a factor. Gonna try the build that got built a few hours ago and see what happens, again.

edit: Same story. Gonna try clicking up the min clock again.
[TouchPad Development] sokratz:
What's the diff between the "Dragons" build and the datamedia build? I don't have that issue with the datamedia build.
[TouchPad Development] invisiblek:
"dragons" builds are just testing, coined from "here be dragons"

stick to the builds linked in the OP unless i give you one specifically to test something (which will end up in the dragons folder)
[TouchPad Development] graffix31:
I don't know why but my WiFi is still not working right even after clean installing both 1/6 and 1/7 nightlies. When I turn the screen off and then back on I have nothing. I will even see the data indicators but the icon is totally clear like there is no signal. Any ideas?
[TouchPad Development] noseph:
Are you sure your WiFi is not working? With CM11 the WiFi indicator is no longer blue when synced with Google.
[TouchPad Development] graffix31:
yeah im sure. i have wifi optimization off too. when i bring the screen back on and try to do anything it says no network connection or whatever.
[TouchPad Development] ilikenwf:
Seems headphone plug detection still doesn't work on this one, a problem we've had since CM9 or before?

That said, the audio doesn't go to sleep and not wake it seems, so I don't have to reboot with the headphones plugged in anymore to get audio. I like that.
[TouchPad Development] vinukondamahesh:
even though my tp is power offf still its battery draining to 0%
[TouchPad Development] jerryatherton:
Test, is this open again?
[TouchPad Development] mattyguk:
Was this locked for a reason? I've been updating through the link in the op without anynproblems.
[TouchPad Development] sokratz:
Just upgraded to 1-12's datamedia build. Sound works while screen's off now. Great fix!
[TouchPad Development] invisiblek:
Dunno. Second time this has happened to one of my threads. I didn't notice it was locked until then lol. All good now =)
[TouchPad Development] nevertells2:
Then you have a bad battery or defective hardware. When your TP is off, if's off.
[TouchPad Development] vinukondamahesh:
how to find out ?

but it was fine with cm 10.2
[TouchPad Development] _Dorregaray_:
Try newer nightly. There was some work in 3.x kernel in order to make the kernel properly turn off and reboot the device.

If this won't reboot the device from CM and shutdown from recovery - if the device won't reboot and shutdown start it again and shutdown from recovery.
[TouchPad Development] vinukondamahesh:
ya thank you i have done some thing like that ....i went in to webos and then i shutdown it
[TouchPad Development] nevertells2:
Hey Big "D",

So you are saying that something in the kernel code is acting like it is turning off the TouchPad, when in fact it is not? I have never heard of this happening in almost three years of using a TP. Back in CM7, when turn off was selected, the TP would just reboot and if the user was not paying attention, then their device was sitting there turned on. Is this what this Rom is doing? I caught mine doing this with CM7 and would stop the reboot at the Moboot menu and shut it down from there.

If when running this Rom the tablet appears to be turned off, that is not good.
[TouchPad Development] _Dorregaray_:
The way of shutting down and rebooting the Touchpad is customized by Pam. The 2.6.35 kernel we're using comes from Palm and has this patches already, but the 3.4 kernel doesn't have them by default.

For 3.4 kernel this has been fixed about 2 weeks ago in invisiblek's repo:

https://github.com/invisiblek/andro...mmit/70e6f34840c160eaece3d92b1dfc813aa2d5e2de

https://github.com/invisiblek/andro...mmit/051c60aacb6aea23306def34a28d31090ff2d773

The flintman's kernel repo on github doesn't have them yet.

Without this patches the kernel won't shut down the Touchpad properly and even won't reboot it (shutdown instead of reboot) but the battery still can be drained - I've observed such situation when working on 3.4 kernel.