yashsingh1/xdaforums huggingface dataset:
[TouchPad Development] allstar319:
It's not the gapps package. Its related to the kernel, so you'll have to wait until we get the 3.4 kernel release (there's a test build on the evervolv thread, though sound doesnt work last I checked). Either stay on 10, 10.1, 10.2, or use Chrome as a browser on 11 (though you'll still have the black boxes on those apps that use the browser API like GMail).

Battery life is the same as the other versions of CM, though it seems a tad bit better on 11 from my use of it.
[TouchPad Development] jayblahX:
Thanks for the reply. I wonder if the app Reddit News uses the Browser API, because I get blackscreens whenever I load a site.

Which 10.2 Touchpad ROM do you recommend, with which GApps?
[TouchPad Development] allstar319:
Probably does.

I'd probably just go with Milaq's 10.2 rom considering I don't know what's going on with the Evervolv 3.3 nightlies (no new one since August). Bluetooth works with Milaq's 10.2 as it incorporated JC's bluetooth fixes, Flintman even recommended using JC's rom since Evervolv didn't have it at the time (and who knows since there hasn't been a new nightly :p). Use the 20130813 gapps.
[TouchPad Development] invisiblek:
Here's a preview build with the new 3.4 kernel using cm -caf HALs:

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

Hold on tight, this thing is buttery.

(BT and Camera are busted still, probably a few other minor things too)

This was a collaborative effort by several people including Flemmard, flintman and jcsullins. I don't deserve much credit here other than building it. This is a huge step toward getting official cm builds again.

We are actually using the latest code from codeaurora for this which is simply amazing on this old device. :p

Please don't clog up this thread with any bug reports for this build or anything, that's not my intention of posting this. Things are broken, that's known, and actively being worked on.

Enjoy!

EDIT: you should be able to flash this over milaq's build without an issue.

EDIT2: It seems to be plagued with watchdog reboots related to the audio which was recently fixed. Beware!

EDIT3: Trouble installing? http://xdaforums.com/showpost.php?p=48793992&postcount=326
[TouchPad Development] jerryatherton:
I have downloaded twice and tried to install with CWM and installation aborted both times. ROM manager said it created a log but I am sorry, I can't find it.
[TouchPad Development] texastutt:
Wow, we're getting closer to this old beast being up to date!

---------- Post added at 10:27 AM ---------- Previous post was at 09:30 AM ----------

I got

E: error in ... Your package

(status 7)

Installation aborted
[TouchPad Development] murso74:
the first couple of lines could have something to do with peoples flashing issues
[TouchPad Development] gradular:
What recovery are you using?
[TouchPad Development] googlephone:
Thank you all devs.

Invisiblek, is it possible for hptp to go back to official cm after skipping cm10,10.1,10.2 and 10.3? That would be amazing, just like a new life for touchpad.
[TouchPad Development] McBeanTIO:
How do you install the new .IMG (Flemmard TWRP with SE support) file in that quote?

I tried converting it to a .zip with no success. Not sure if there is an app I need to use to run this, or convert it to an .APK package.

Will keep at it and see if I can find success.

--McBean
[TouchPad Development] googlephone:
You can use terminal emulator.
[TouchPad Development] McBeanTIO:
OK...not technical in the line commands for the emulator. Will have to look into it then.

I already tried the SGS4 and the [Root] Recovery Tools-Flasher apps from the Play Store to no avail.

--McBean
[TouchPad Development] texastutt:
I missed that post. Thanks, I'll try it on Boxing Day
[TouchPad Development] murso74:
it was actually in the other thread (everevolv)... i just remembered seeing it and thought it might do some good here
[TouchPad Development] invisiblek:
oh, yea, you'll want Flemmard's selinux twrp

http://flemmard.net/recoveries/openrecovery-twrp-2.6.3.0-tenderloin-selinux.img

Place it at /boot/uImage.TWRP
[TouchPad Development] nevertells2:
Rename the .img file to uImage.TWRP and use a file browser like Rom Toolbox Lite to copy the file into the /boot folder. And that is an upper case i in the name uImage.
[TouchPad Development] allstar319:
Are we limited to 1188 mhz currently with the 3.4 kernel? Would like to go a bit higher unless I'm just blind.

Can't seem to set /data/media/0 as the home directory, though it shows sdcard0 fine. I guess the external_sdcard is now sdcard in this build as Diceplayer shows it as sdcard now, cant get to the data/media/0 from diceplayer now. Might just be this version of TWRP though not supporting datamedia I guess.
[TouchPad Development] jerryatherton:
I can't find my downloads in TWRP. I can find them with root browser
[TouchPad Development] bombaw8:
Mount data partition then find your file in /data/media/0/... This version of TWRP does not appear to be data media aware.

If you are using data media, I'd avoid flashing this build right now if you want everything to work out of box. Some tweaking needs to be done, at least for SDcard storage...

It does run much smoother however and black browser screen related errors are all gone! Yeah!

---------- Post added at 07:22 AM ---------- Previous post was at 07:06 AM ----------

The SDcard links are broken. They should go to data/media instead. Anything relying on a working SDcard (such as Dropbox) will probably barf.

Simply relink /sdcard didn't work. I'm sure it's not a hard problem to fix however.
[TouchPad Development] nikos5800:
will the cm11 + kernel 3.4 work with non data media touchpad?
[TouchPad Development] gradular:
Yes. Its non data media build, so copy anything you want to save or you can't access it easily.
[TouchPad Development] patoberli:
Just updated from jscullins build from July (or around that) to this build. For this I first increased the space of the /system in WebOS, then installed a much more current CWM (the one from post 1). After that I took a new backup (to sdcard-ext), installed todays (25.) nightly, installed GAPPS, cleared cache (and only cache!) and rebooted. So far everything seems to work!

Just run Antutu benchmark and the speed went from 8808 to 11033!

Details (left old, right new)

1547	1894

618	926

831	1076

549	599

366	491

656	766

725	688

2771	3174

440	1079

305	340

2506	2506

Thanks a lot! :)

[edit1]

Encoutered the first issue. Simpsons Tapped Out is not starting because of to little space. I greatly increased /cache (to 1.4 GB) and /data (to 16 GB). Let's hope that will help, but I fear it's because of something else.
[TouchPad Development] nevertells2:
I would recommend undoing everything one has to do to install a data/media build and install an older CM10.1 before trying to install Invisiblek's new CM11. I've already read of apps not wanting to install and apps in the new partitions not being found after installing the new CM11 over a data/media Rom.
[TouchPad Development] drt054:
disregard.. just read the 10.2 OP..
[TouchPad Development] Kyle Chen:
My data media partition is currently 1.5 GB. I have tried to partition it, first using the zip. It increased my system partition but it gave an error for creating data media. I tried tailor, but if gives me a filesystem error and gives me an option to repair it. The repair option does not work. Help? Thanks
[TouchPad Development] allstar319:
Repair should work. Sometimes you have to run it twice.
[TouchPad Development] Stryeguy:
As said above, try repairing it a few times in tailor; it took me a few times, too. I completely deleted all my paritiions (after backing up my SD contents on my laptop) after a few frustrating attempts.
[TouchPad Development] noseph:
The hijacking of this thread makes it very hard to follow OP issues.
[TouchPad Development] ce tiger:
anyone know if the new build fixes the black boxes in gmail and browser?
[TouchPad Development] nevertells2:
Only thing that is going to fix the black boxes is a new kernel.
[TouchPad Development] Swetnes:
What black boxes? I just installed on my TP yesterday and I didn't see any black boxes in gmail, and neither Chrome nor the standard AOSP browser. Maybe it's caused from something else?
[TouchPad Development] gradular:
They are NOT fixed if you flash the OPs builds by Milaq. The kernel updates are still alpha and are not yet merged. There are still issues being worked to make ok for daily use.
[TouchPad Development] vinukondamahesh:
i am not a dev r admin but request for me plzzzzzzzzzzz. post invisiblek rom in separate threads actually getting confused with all rom discussion in one place
[TouchPad Development] googlephone:
Not true.

Another way is to disable hardware acceleration for the apps with blackbox issue to fix the issue.

A new kernel can fix the blackbox issue ane it's the best method but not the only method.
[TouchPad Development] woodytrain:
Agreed. I was confused with the initial posting and now the follow-up discussion. Should start as new thread and include in title "EXPERIMENTAL PREVIEW".
[TouchPad Development] woodytrain:
So how to disable hw acceleration for individual apps?

Reading this post it appears I can disable "video.accelerate.hw" for the complete system in system/build.prop

http://xdaforums.com/showpost.php?p=25310988

To test I added the parameter and set property value to zero. But I still see the black box in default browser, gmail, etc.

So are there similar individual hw accel parameters/properties for each app (e.g. default web browser, gmail, etc)?
[TouchPad Development] Swetnes:
I was just saying I don't have black boxes and I am on Milaq cm11 with the standard kernel. Maybe it's because when I went from his 10.1, I used the acme uninstaller, then used acme 5m, tailor in webOS to adjust the data partition? Then installed Milaq cm11 from the data media cwm. Maybe someone else can try it til kernel 3.4 is ready. But again I have NO BLACK BOXES.
[TouchPad Development] Atlasstorm:
I didn't have black boxes the first time I flashed cm11 but the second time I did
[TouchPad Development] jerryatherton:
The invisiblick 3.4 Kernel is working with the 11/24 nightly. You need to install a special TWRP to install it. It didn't work real well over the CWM data recovery. Never tells suggested starting over at CM 10. He was right. I couldn't figure out thee files at all by just putting the new recover over the data media recovery. I will endorse never tells suggestion. I did the following:

Ran the acmeunistaller2

Followed rolandDeschin79's guide on installing android " The Easy Way"

I used the CM10 files for my cminstall folder

I ran the ACMEinstaller5 (because it was the last non data media recovery)

Downloaded the new recovery image (in is I block posted a few pages back)

Downloads the 11/24 ROM that in is Invisiblick posted a few pages.

Seems to be working great, no black boxes.

I don't know if the 11/25 and 11/26 have the 3.4 kernel. I will try to dirty flash them.
[TouchPad Development] ZeroZorro:
I did just that (exactly that) but i do have those black boxes....so...random? Nah...
[TouchPad Development] floxigen:
bLUETOOTH Works ?
[TouchPad Development] ZeroZorro:
It does for me...keyboard and Jabra BT620s
[TouchPad Development] Swetnes:
?? Too wierd
[TouchPad Development] woodytrain:
I never had any Android installed on my Touchpad before installing CM11 4.4.2 (12/12/13). The blackboxes were present. Then installed 12/14 nightly and observed the same. Been awaiting kernel updates ever since.. Will install today's nightly and see if any diff. (unsure if the current nightly yet includes required Kernel update).
[TouchPad Development] jerryatherton:
The 12/26 does not have the new kernel so it does have the black boxes. The 12/24 rom with the new kernel are in post 315 with the recovery in post number 326.
[TouchPad Development] nevertells2:
Woody, please read Milaq's commits on the OP. If you do, you will know exactly what he has included.

---------- Post added at 09:31 PM ---------- Previous post was at 09:27 PM ----------

Just for the record, that's invisiblek's build in that post, not Milaq's
[TouchPad Development] woodytrain:
My mistake. Just installed 12-26 nightly and black box syndrome still present. Checked milaq's github and appears no kernel updates for Milaq's CM11 as of yet. But most recent device tree updates include:

12-26 remove custom dosfs tools

12-24 dev: pmem has to be world accessible for now

12-21 fix screenshots

Interesting recent dev action can be viewed at:

https://github.com/CyanogenMod/android_device_hp_tenderloin/network

Since I already have the TouchPad storage setup for datamedia I rather not go through all the gymnastics of changing to non data media format and installing custom TWRP to test invisiblek's new rom and then have to change storage configuration again when CM11 data media version is released. So will await an update to Milaq's CM11 version with new kernel and hopefully be able to continue to use CWM.

---------- Post added at 07:14 PM ---------- Previous post was at 06:41 PM ----------

On the GitHub fork network map I observe other CM11 associated builds for KitKat Tenderloin (HP TouchPad):

Milaq has a "cm-11.0_3.4" build which differs from his "cm-11.0" build. Flintman has merged his builds into one build named "tender", and invisiblek has a a build titled "cm-11.0_btwip" which supports bluetooth tethering, separate from his "cm-11.0" build. And Dorregaray has a build with recent gyroscope/magnetometer updates.

So how does one wishing to help test these builds obtain a "summary" of differences between these builds?

---------- Post added at 07:46 PM ---------- Previous post was at 07:14 PM ----------

Not wishing to plug up this thread with discussion of Invisiblek's build, however since there is no other thread to comment on such (hint to invisiblek)...

Invisblek github shows an update just posted to support "data media".

https://github.com/invisiblek/andro...mmit/2906b40dbbc70738b3c857210185a071bfea3a95

So can I now install this build without having to alter my current data media setup?

And if so, must I install using the new custom TWRP to install, and not use CWM v.6.0.3.6 tenderloin.

(Forum moderator: could you please create a new thread for the Invisiblek mod build and move relevant posts to the new thread).

---------- Post added at 08:01 PM ---------- Previous post was at 07:46 PM ----------

UPDATE: Just checked http://invisiblek.org/tenderloin/roms/cm11.0/

and no new build since 12-24. So will await an updated Invisiblek build supporting datamedia.
[TouchPad Development] Young Cardiac:
maybe someone can help me out here.

I haven't touched my touchpad for the last 1.5 years. I still have a cm9 nightly on it from 2013/03/29. If I want to put this kitkat rom on it how would I go about it? Do I need to put a newer recovery? I currently have cwm v5.0.2.6.

Thanks!
[TouchPad Development] texastutt:
I did the same setup but I had black boxes from the start. So, there's a bit of luck of the draw...
[TouchPad Development] woodytrain:
milaq's CM11 12/26 nightly

Installed milaq's CM11 12/26 nightly (cleared cache first).

Then numerous apps (Google Voice Search, SoundRecorder, Apollo, YouTube, DSP Manager, GooglePlay, etc) wouldn't render content or freeze up. And android would spontaneously reboot itself. After three spontaneous reboots I decided to give the 12/26 build one more chance before reverting back to the 12/14 build.

So immediately after restarting Android I shut down all apps which auto started (via Task Manager app).

And all the above apps operated correctly.

Was able to BT pair/use both an HP and Logitech keyboard and do a BT transfer with a Windows laptop.

The Touchapd could see the Plantronics bluetooth headset (PLT_BB903) but during pair attempt BT on the TouchPad would spontaneously turn off and on, and headset wouldn't pair. The headset pairs fine with my other BT devices and with CM9 and CM 10.1 on another TouchPad.

No spontaneous reboots after two and a half hours since last reboot. But battery appears to discharge at much higher rate than previous.

Any ideas why the system acted so flaky, just after installing the 12/26 build? Then why, after numerous restarts the system appears to have stabilized? I haven't observed similar flaky post-install behavior with previous CM build installs.
[TouchPad Development] potatohead:
invisiblek's CM11 12/27 nightly (datamedia)

invisiblek has created a datamedia version of his nightly that includes 3.4 kernel

http://invisiblek.org/tenderloin/roms/cm11.0/datamedia/cm-11-20131227-UNOFFICIAL-tenderloin.zip

for those who wish to give it a go, remember to flash using datamedia selinux edition of open recovery, either twrp or cwm

http://invisiblek.org/tenderloin/cwm_selinux_6.0.5.4_datamedia.uImage

or

http://invisiblek.org/tenderloin/openrecovery-twrp-2.6.3.0-tenderloin-selinux.img

as with invisiblek's 12/24 non-datamedia CM11 rom, the included 3.4 kernel indeed solves the 'black box' issue :)

CM's default music app Apollo is not included in the rom, I downloaded a simple free music player from Play store - Omich Player; music playing works as per normal both with screen on and off.

volume buttons' track skipping function when screen off works too :)

only gripe lies with internal speaker not being disabled when external speakers / headphones are plugged in, def a deal breaker for headphones user; for those using external speakers - free quadro sound :D

many thanks to all the devs working hard behind the scene!
[TouchPad Development] _kevn_:
OK, as awesome as this is to have here immediately for us to download, and I do mean awesome as in as soon as I get to my tp I'm going to download and flash, I really think it might be time for a separate thread for that build by invisiblek so we can keep bugs/any issues/discussion separate from Milaqs thread so we can further the development of our beloved tp with as little confusion or frustration as possible.

Talk about a run on sentence huh!? Sorry if that's hard to read, it makes sense in my head

Anyway, huge thanks to Milaq and also to invisiblek and of course everyone else working on the tp to give it the latest greatest Android!

Kevin

P.S. I mean no disrespect to those of you who are posting these other builds but let's give Milaq the respect of having only his builds in his thread so he can concentrate. I think it'll be beneficial to all of us.

Thank you :)

transmitted via skynet
[TouchPad Development] jerryatherton:
What will be the standard recovery? Data Media or the legacy. It would be nice if this was consistent.
[TouchPad Development] GizModio:
You haven't used your TouchPad for 1.5 years, but you're running a version of android that's not even a year old? :confused:

But in regards to your question, I managed to simply update from 4.2 to 4.3 with out a change of recovery. But it's recommended that you use 6.0.4.4 of Clockwork mod.

Just simply format System, Cache, Dalvik Cache. then install your Rom using the desired GAPPS. :good:
[TouchPad Development] ranjib:
Pull all Android from your touchpad, install tailor within webos and then push kitkat on it.

Afterwards change partition sizes. Nearly everything described here.
[TouchPad Development] jimmypop13:
I need some help getting this installed. I'm running cm10.2 and have cwm 6.0.3.6 data media edition. I just tried to install this rom(2013-12-27) and kept getting an error status 7 for the file. Do I need a newer version of cwm? If so can someone point me to it. I saw one a few posts up but it downloaded as a txt file which is confusing. I need a zip bc I don't have a computer or fastboot near me.

Thanks guys
[TouchPad Development] allstar319:
Error 7 for installing the actual build, or the gapps? I recall getting an error like that when trying to install the 20131208 gapps, but fixed that with installing the noselinux version of the gapps.

Video playback wasn't working on the first 3.4 kernel build that invisiblek posted, not sure if it's fixed in the other one.
[TouchPad Development] woodytrain:
Need new thread for Invisiblek ROM build

Just PM'd the following to Dan (invisiblek).

Hi Dan. Whenever announcing/releasing a new build it is best practice to create a new thread specific to that build.

After your initial build announce post to the CM11 nightly thread for Milaq's KitKat build, it has become difficult to identify which build is being referred to (Milaq'a build or your build).

Could you please initiate a new thread for your build ASAP , with install instructions, download links etc, in the initial post (you may want to make a second post as well to reserve for future use). And then request the forum moderators to move the current posts specific to your new build over to your new thread.

Maybe title your thread similar to:

[ROM] [CM 11.0] [Kitkat 4.4.x] [Experimental/Test+ Preview by Invisiblek]

Hope you can do this ASAP. Thanks for the build. Hope to try it out shortly.
[TouchPad Development] allstar319:
I would imagine that once it's stable enough, Milaq will incorporate it into his official builds and this thread considering Invisiblek's is just Milaqs rom with the 3.4 kernel (I'm assuming anyways since his is the only CM11 rom we have). Most of the 3.4 kernel discussion is going on in Flintmans Evervolv 4 thread. With that considered, I would think that thread would probably last just a few more weeks before the other major kinks are worked out.

I guess it's better than all the people reporting black box issues though. :p
[TouchPad Development] woodytrain:
Understood. I suspect all the developers working on parallel mods are "sharing" their work and understand that invisiblek is doing nicely providing us all a preview of the new kernel.

But I wish to continue testing/discussing Milaq's nightlies, as well as Invisiblek's mod. Different recoveries are required for the two builds. Not having separate threads for each nightly, no matter how temporary, makes it very difficult for everyone to follow what's going on and troubleshoot their own specific issues. Especially many of the folks moving from CM10 to CM11 and/or those who are coming this thread for the first time.

Both are publicly announced test builds, and thus the threads should be separated, even if Invisiblek's build is a temporary one. IMHO.
[TouchPad Development] Kyle Chen:
Everything on my touchpad was working fine. Suddenly this morning android is bootlooping and when I boot into cwm it says "warning no file_contexts" and goes back to the reboot menu. WebOS boots up fine. What do I do?
[TouchPad Development] woodytrain:
You don't say what version/build of mod you are running. So you want us to guess? CM9 is listed in your signature. Or since you are posting in this thread is it safe to presume have you installed a version of Milaq's CM 11 ROM build and were testing? If so, please provide ROM/build and recovery specifics (version number, build date, etc).

If you are running CM11 (again which build/version and which specific recovery version are you using), what were you doing on the TouchPad just before you observed the bootlooping? What did you install/update/upgrade most recently?

You should provide this kind of info whenever requesting assistance.
[TouchPad Development] Kyle Chen:
Sorry about that. Yes I was running CM11 DEC 22 nightly and CWM 6. It was bootlooping every once in a while. But it was fine. Today it just got stuck on CWM logo. I tried booting into CWM recovery but it says warning no file_contexts and just goes back to moboot. WebOS boots up fine. I am guessing something is corrupted. Should I use ACME uninstaller and then ACME 5 or should I just try ACME 5 without uninstaller?

Thanks.
[TouchPad Development] jaltman:
While I am not really a newbie, I am at a loss as to how to install one of the alternative recoveries to try Invisiblek's rom. I have searched but dont find anything on installing the uimage or img files. ODIN? ADP? Acmeinstall? A pointer would be helpful, TIA. Currently I am running CWM 6 and Milaq's latest ninghtly.
[TouchPad Development] waynekirby:
Place it in /boot with the correct name and permissions