[ROM] CM 11 (kitkat 4.4) nightlies

[colchiro]

Very experimental. For experienced users only.

[ROM] [EXPERIMENTAL] [NIGHTLY] [KitKat] [4.4] CyanogenMod 11.0 nightlies - xda-developers

• These are datamedia builds. What is a data media device? | TeamWin
• Datamedia version of CWM recovery required.
• Advised partition layout:

system - 500mb
cache - 200mb
media - 400mb
data - [remaining space] (i.e. ~11.5gb for 16gb TouchPads)

 

[Unforgiven]

Whoah, really???

That's really cool for those that can run this. The touchpad is what, 3 years old.:thumb:

 

[colchiro]

Something like that.

Just flashed it a bit ago, my first try at anything higher than 10.1 and my first datamedia rom.

Milac's nightlies don't have the new kernel yet so some things, like Browser, still have black backgrounds. The new kernel is going to be huge, since we've been stuck with an old kernel for some time. I think it date before gingerbread.

 

[Deleted User]

Very experimental. For experienced users only.

[ROM] [EXPERIMENTAL] [NIGHTLY] [KitKat] [4.4] CyanogenMod 11.0 nightlies - xda-developers

• These are datamedia builds. What is a data media device? | TeamWin
• Datamedia version of CWM recovery required.
• Advised partition layout:

system - 500mb
cache - 200mb
media - 400mb
data - [remaining space] (i.e. ~11.5gb for 16gb TouchPads)

iMarck90 provided a really good explanation over on Rootzwiki about why one might want to install a DataMedia version of CM:

"I have finally understood why Milaq has decision to migrate to the new standard, the motivation is simple "Multiusers".

If you want use correctly multiusers you need the new standard. Try with CM 10.1 the multiusers and you can see when you create a new users there is a soft reboot but the user is create correctly.
The division of space isn't correct, you can see the new users occupied the same space like your owner user and when you try to install a game like Asphalt that share the same data with the new users, Asphalt is crash when you launch with the new users and some minor issues.

So this is the motivation. If you want a stable multiusers functionality you don't have another choice."

If multiuser functionality is not your cup of tea, then I would suggest installing the Evervolv version which does not require all the partition adjustments or the datamedia cwm. One still needs to use the newer ACMEInstaller4 or 5 to increase the /system partition size so the install will fit.

 

[colchiro]

I have no use for multi-user on any of my devices. In our household, it's one device per user. I DID install this, but was a little disappointed it didn't have the new kernel and it didn't prompt me to update to a new nightly, but I suspect that functionality will come.

I had no problem installing, but decided I needed to increase my system a bit, since it was a little under the 500 mb cutoff, then after restoring apps via TIBU, ran out of data, so had to increase that a LOT, which I again used Tailor. I naively assumed it would assign all the free space to data automagically.

Still, pretty solid for a alpha build, a little laggy at times, but aside from the black screens in gmail and browser, which the new kernel will fix, a pretty sold build. (I'm still on the initial build.)

 

[Deleted User]

I have no use for multi-user either. I have no use for having to manipulate the partitions either just to get what most of us would consider a totally different way of installing Android. I suppose at some point if one wants to continue installing newer versions of Android on the TouchPad, data-media will become the norm. Personally, the version I am running now works so well, don't know I will bother with any version past it.

The fact that there are developers out there that even consider writing code for a tablet that is rapidly approaching three years old is amazing. One would think they would want to move on to something newer and more modern.

 

[colchiro]

The fact that there are developers out there that even consider writing code for a tablet that is rapidly approaching three years old is amazing. One would think they would want to move on to something newer and more modern.

I agree. Not much going on with other devices I own.

 

[colchiro]

Just acmeuninstall2'd Milaq and now running acmeinstller4ET to install Flintmans' Evervolv 4.

I see it just booted up.

 

[Deleted User]

Hooray!!!!

 

[Deleted User]

For those of you who have questions, want info, need guidance on the installation of Android 4.4 in whatever version you want to try, Evervolv by Flintman, CM11 by Milaq and Invisiblek, Rolanddeschain79 who has created so many great threads and videos about installing all the different versions of Android has just posted a new thread dedicated to Android 4.4, data/media builds. Be sure to drop by the link below and thank him for his excellent support of Android on the HP TouchPad:

http://rootzwiki.com/topic/113874-r...roid-44-data-media-builds-on-the-hp-touchpad/

 

[colchiro]

I'm about ready to try a new D/M build.... coincidence? I think not.

 

[Deleted User]

Good luck! Even you as an experienced user, I bet you have problems, but we'll see. IF I were going to install one, it would be Evervolv. I'm quite happy with J . C. Sullin's CM10.1 KERN3 builds.

 

[colchiro]

Last time the biggest problem I had was figuring out which acme installer to use.

I tried all the versions 2-1/2 to 5-1/4.... It really shouldn't need to be that complicated. Have one installer that asks a few questions or throw them all in a grid:

Recovery, Rom, D/M, etc.

 

[Deleted User]

Ah, then you need to read post number nine here:

[ROM GUIDE] How to install Android 4.4 Data Media builds on the HP TouchPad - HP Touchpad - RootzWiki

And personally, I would not use ACMEInstaller to install one of these data/media Roms.

Read Rolands new thread, same link and then tell me what you think. Then let's see if you are still smiling.

And BTW, Flintman is still supporting his Android 4.4 non-data/media, 3.4 kernel build for now.

 

[colchiro]

Thanks, I saw that earlier. I updated last night and it was a chore. Couldn't get Flintman's build to install via Acme 5m so instead installed Milaq's, figuring I could upgrade that later. Both my TP's were idle for about a month so not too worried about them as long as I don't brick them. I do have to admit all the recoveries and rom versions are going to screw up a lot of Touchpads.

 

[Deleted User]

That's putting it mildly! :dong:

Don't forget, Evervolv and CM builds are named differently when installed. Check what grimm has been looking into, post #14:

[ROM GUIDE] How to install Android 4.4 Data Media builds on the HP TouchPad - Page 2 - HP Touchpad - RootzWiki

 

[colchiro]

Cool! I'm glad he's looking into it, although I don't think Roland needs to add it to the OP. Most people that use his guides just want the basics and it's already too cluttered. I like Roland's guides, but after awhile there gets to be too much info. Still he does better than I do. Once I saw his guides, I quit writing them and just referred people to his.

I used Acme5m to install, yet still had to move 24 gb to the data partition and add 100 mb to system with Tailor. I thought Acme was supposed to do all that for me?

Also found out I have Milaq's CM 10.2 so guess I'll be wiping soon. It was one of Roland's link-with-all-the-files in it so I knew it should work. It's also quite laggy so I assumed it was the latest and greatest and time would fix it.

 

[Deleted User]

The only thing ACME5M does is add 600mb to the /system partition. You should do the Tailor stuff first minus increasing /system since ACME will do that. My thinking is to use Taylor to change everything else except /system, then use ACME to increase /system, and install just moboot and recovery. Then use the modified recovery to install the data/media ROM and Gapps. Want to be my guinea pig?

 

[colchiro]

Actually I was acme uninstalling everything first (3x during the course of the evening) so hard to start out making changes before.

Acme will increase system to 600 mb if it's less, otherwise leaves it alone. I had trouble with reinstalling gApps to fix a PlayStore issue until I increased system.

I do have another TP, what you got in mind? (I should donate it to a dev so I have one less to maintain.)

Made sure I updated the firmware last night and left it running so we'll see how the battery use is tonight.

 

[Deleted User]

Use Tailor to set up the partitions. Run ACME5M to install just Moboot and Milaq's recovery. Use recovery to install the data/media Rom and then Gapps.

I've heard that some of the Gapps packages are huge and can cause one to run out of /system memory. There are some smaller ones around or I read, increase /system to 700mb.

I just asked Flintman if flashing his test TWRP.zip using CWM first removes CWM before installing TWRP. When I get an answer, I'll have another idea for you.

 

[colchiro]

K.

 

[Deleted User]

Wow, rather long post I typed last night just up and disappeared.

Flintman confirmed that flashing his hybrid TWRP using CWM first deletes CWM before installing TWRP. So, my theory is that if done the right way, you should be able to install any of the 4.4/3.xx/data-media kernel Roms using his TWRP. Here is what I propose:

1. More or delete as much as you can off the current SD card, as you are going to use Tailor to move most of the memory over to the data partition. One way to do this would be from WebOS/settings/reset options, reset USB drive. Run Tailor and set up the partitions as suggested by the developers. If I were doing this, I would leave a gig or two for WebOS to use.

system - 600mb( or maybe even 700mb)
cache - 200mb
media - 400mb(leave a gig or two here)
data - [remaining space] (i.e. ~11.5gb for 16gb TouchPads)

2. Run ACME5 to install just Moboot and CWM
3. Use CWM to flash Flintman's hybrid TWRP.
You will find it on the OP here:[ROM] Evervolv | 4.0.0p1 [AOSP 4.4.2] [3.4 kernel] [Nightlies] With /data/media - xda-developers

4. Flash one of the 4.4 data/media Roms from Flintman, Milaq and Invisiblek and the Gapps of your choice for KitKat.

Remember when switching between CM and Evervolv, the uImage is not named the same. I believe Flintman said that when you install Evervolv, his scripts are built to remove CM, but not the other way around. So I would suggest running ACMEUninstaller2 and doing a clean install of each Rom using Flintman's TWRP. And yes, I believe ACMEUninstaller2 undoes all the partition size changes you made with Tailor.

As far as I understand, none of the ACMEInstallers will install a data media Rom. That is why one has to use one of the special recoveries. And now you know why I am not particularly interested in trying any of the data/media Roms. Although, Flintman is still supporting an Evervolv 4.4/3.xx kernel that is not a data/media build, at least for now.

If you choose to accept this mission Grasshopper, I disavow any responsibility for any reboots, bricking, or black holes created by trying this.

 

[colchiro]

Try all this risky stuff Grasshopper, but if it goes bad, you didn't get it from me....

OK.

I'll see if I can work it into my weekend.

 

[Deleted User]

We will be cheering for you! arty:

 

[colchiro]

LOL.

We? You and your 7 drinking buddies?