yashsingh1/xdaforums huggingface dataset:
[Nook Color General] dcahoe:
Finally had success installing Tablet UI on CM10a1 SD boot image. Thanks leapinlar and mateorod.

I tried both methods.

First I modified the /system/etc/vold.fstab file and installed the patch with CWM for SD (thanks for this btw, I didn't know it existed). Still got a bootloop.

Secondly, I wrote a new rev5 sd-card-image to SD and flashed CM10a1, then installed the TabletUI patch using CWM for SD and still bootlooped.

Third, I went into apps and cleared Trebuchet data, booted into CWM for SD again, wiped cache, installed TabletUI patch again, and voila, it worked!! Now I can start playing around with it. It already looks closer to my favorite AOKP rom, but the font sizes and spacing seem off at first glance. Like I said, I'll start playing with it...
[Nook Color General] iamnotspock:
Still having trouble

Sorry for my noobness, but I am still unable to install the updater using the alternate CWM. I checked the boot partition of my SD card and confirmed that uAltImg and uAltRam are located there. I also copied the updater zip file to the boot partition. I booted into the alternate CWM-based Recovery v.6.0.1.2 for SD and am presented with the following menu:

- reboot system now

- install zip from sdcard

- wipe data/factory reset

- wipe cache partition

- backup and restore

- mounts and storage

- advanced

I chose "install zip from sdcard" and moved to the next menu:

- choose zip from sdcard

- apply /sdcard/update.zip

- toggle signature verification

- choose zip from internal sdcard

I chose "choose zip from sdcard" and got:

- Android/

- Download/

- LOST.DIR/

- ReceivedFiles/

- TuneIn Radio/

- TunnyBrowser/

- Winamp/

- burstlyImageCache/

- kindle/

- madden12/

- xda.download/

- yume_android_sdk/

I don't know where to go from here. I don't see the updater zip as expected, even after I mounted the boot partition using the earlier "mounts and storage" option.

Clearly, I don't understand CWM very well, or I haven't done what I was supposed to in some other way.

Can any of you walk me through this? I would appreciate any help you can provide. I am excited about the progress made thus far on CM10 for Nook Color, and would like to investigate the Tablet UI.
[Nook Color General] leapinlar:
Dont put the update zip on the boot partition. Put it on sdcard while still having the SD in the nook.
[Nook Color General] iamnotspock:
Still having trouble

OK, I went into the XDA app, downloaded the updater from this thread, booted into CWM alternate, chose " install zip from sdcard", then chose "choose zip from sdcard", then located update-TabletUI-CM10.zip in /sdcard/xda_download, selected it, the install completed, and I rebooted. Now I seem to be back where I started, in a never-ending bootloop.

Any clues as to where I went astray this time?

Update: I was able to apply the restore, and can now again boot into CM10. But, alas, still clueless on installing the Tablet UI updater.
[Nook Color General] leapinlar:
You did it all correctly this time. I suggest you go back to the Alternate CWM and select advanced and clear dalvik cache and then reboot again.

When you say neverending bootloop, you mean stuck on boot animation forever or bootlooping where it reboots and reboots and reboots all the time?

The first time it boots after the flash should take a while since the dalvik cache needs to rebuild itself.
[Nook Color General] iamnotspock:
I meant stuck on the boot animation for many, many minutes. If you say I got it right this time, I will repeat the process again and let the boot animation run for a long time if necessary. Any idea how long it should take?
[Nook Color General] leapinlar:
If it is rebuilding the dalvik cache it should take two or three minutes. But I would flash the update-restore zip before trying the update-tabletui again.
[Nook Color General] iamnotspock:
Success!

I did flash the restore zip, rebooted, then shut down and rebooted into CWM alternate, used it to wipe dalvik cache, flashed the updater zip again, rebooted, and lo and behold, it booted right up without hanging on the boot animation. It did take a very long time "upgrading" Android, but I am now staring at the Phablet interface and anxious to check it out.

So, many thanks to all who helped walk me through this.

First observation: Many of my widgets seem cut off on the top and bottom in landscape mode (I am using Nova Launcher, which I had set to allow the maximum number of cells on the home screen). I will play around with my settings to see if I can adjust them to make the widgets fully display.

Thanks again!
[Nook Color General] can80an:
Hmm, I feel a little silly, with all the different things I had been trying I somehow messed up those two files and they did not end up where they were supposed to be. I did manage to get things to work (sort of) but when it rebooted it got hung up at the 'Stargate' and wouldn't move beyond that. I applied the restore and things are back the way they were.

I'll try it again tomorrow.

Thanks

Edit: Tomorrow is here and I wiped the Dalvik Cache, reflashed, rebooted and all seems to be working well. Wiping Dalvik seems to be the key ...

Thanks all
[Nook Color General] pckoloji:
cm10 alpha 1 + nemus launcher + update.zip > tablet ui no problem but power widget is missing like others reported.
[Nook Color General] jpaden:
Trebuchet Grid Size

I think I noticed one other person mention that, after applying the Tablet UI, their homescreen seemed to stretch off the screen. I'm seeing that too, like homescreen is rendering a larger resolution than the screen is. I wiped cache and dalvik-cache, and applied the Tablet UI zip, with the Alternate CWM, all provided by leapinlar.

So I played around with it a bit, and what I think I'm noticing is that Trebuchet appears to ignore the grid size (number of columns, rows) in the settings. It gives me 7 columns and 6 or 7 rows (don't have it right in front of me), even though I have specified 5 columns and 5 rows in the homescreen settings (in an attempt to shrink the homescreen size down to my actual screen size). 7 columns is definitely too large to fit on my screen with amount of space used in between icons.

Has anyone else had this problem, and potentially found a fix? I'd love to keep using Tablet UI, but this issue just makes it feel wonky to me. Thanks!

EDIT: I should also mention I'm using the nightly build that has been floating around the last couple of days with lots of stuff (everything?) fixed, not the Alpha 1 build.

-JP
[Nook Color General] mateorod:
You could just run your current build through the original tool. The command and the link is on the OP. Haven't messed with the new build myself, but I didn't notice any grid problems. Although I didn't run it very long either...
[Nook Color General] davidr415:
I found that after you move the icons around, they behave properly.. correct size.. all on screen..
[Nook Color General] lollyjay:
Same here. Moving icons fixed the problem.
[Nook Color General] mateorod:
Okay then this is simply a cache issue. Wipe your caches, folks and there won't be any problems.

There is a new build out. Until I hear otherwise, I expect the attached zips in the OP to stay relevant. If you find they don't work, you can let me know, or just follow the instructions on the first post.

Literally zero programming knowledge is required, and it works on OSX, Windows and Linux.

But like I said, if you guys have an issue and I see it, I will update the attachment myself.
[Nook Color General] stolenmoment:
Sorry to say that this appears to be incompatible with the new beta CM10. I tried it three times, and got permanent boot animation each time.

Flashed beta, update, gapps, wipe both caches, boot to animation. Flashed beta, gapps, update, boot to animation. Flashed beta, gapps, boot (OK), boot to recovery, flash update, wipe caches, endless animation. For one of those, I left it while I showered, just to give it time.

After that, I flashed beta and gapps again and all is well; if the update didn't work, I wasn't going to trust the restore (it worked for me on the alpha).

Kinda smells like they made some change in the framework that breaks your mod, but I haven't followed the source changes to be sure (job, kids, and now a hurricane alerts me to a leaky house).

Damn, I like this interface *much* better than stock.
[Nook Color General] dparrothead1:
+1 on the endless boot animation using the TabletUI zip. Without the zip.....no problems.:confused:
[Nook Color General] mateorod:
Okay, I will update it. Just for kicks, this is how it is done...

Download the latest Auto-Patcher (or the GUI for Windows)

Run it on any PC (Windows, OSX, Linux. OSX and Linux users will need Java, patch and cpio installed in your usual manner).

./auto_patcher cm-10-a1-encore-fullofbugs.zip tabletUI

Collect your update.zip. Wipe caches before install.

New update.zip will be on the OP momentarily.
[Nook Color General] dcahoe:
I had this problem and found that if I used Root Browser Lite (or similar) to open the /system/build.prop file (just use the RB Text Editor) and modify the following line as shown:

ro.sf.lcd_density=140

then save the file (must have root privileges) and reboot and everything looked normal/great. This line was abot 3/4 way down in the file for me just above the # ADDITIONAL_BUILD_PROPERTIES section.

Alternately, download an lcd density app and change the system density to 140 with it.

I do love the Tablet UI, I think Krylon360's AOKP jb build spoiled me on this.

Thanks mateorod for the beta 1 update patch, it works great.

EDIT: Moving the icons around as others suggested did not work for me..

I followed the above procedure when I was runing CM10 alpha 1 off of SD card. I installed CM10 beta 1 on my internal memory (emmc) and the lcd change was not taking. I wound up changing the density to 140 in the /data/local.prop file and voila success!
[Nook Color General] davidr415:
It was also mentioned in that thread that all you have to do to correct the problem is to move the icons around on the homesreen and that, after they have been moved, they are correct size.
[Nook Color General] stolenmoment:
Much better! Thanks for the update! Seamless installation.
[Nook Color General] pmpartners:
Worked like a charm on Alpha, Icon position was off but moving seemed to help. Thanks.

edit:I used the Auto-Patcher GUI to create the update file, worked great as well!
[Nook Color General] sisterchick:
Thanks!

I tried out ApG on my Windows 7 x64 computer to run AutoPatcher and make my own flashables for beta 2. Easy to do and worked well. THANK YOU.

Love the tablet interface!!

PS: Link to Windows installer broken in OP. I got it here!
[Nook Color General] mateorod:
Whoops. Looks like I linked to a git object, somehow. That won't get us very far! Fixed in the OP.

My strong feeling is that the zip for beta1 will work for beta2. These system jars tend to go out of date every 7-10 days or so, so we should be good. Let me know if that ends up to not be the case.

Edit: And sisterchick, thanks for trying the tool. Not so hard, huh? That can give tabletUI to any rom or device.
[Nook Color General] stolenmoment:
Yes, it does! Beta2 has serious SoD problems, though.
[Nook Color General] majorpay:
haven't seen the b2 faux SOD

Haven't seen it since installing this on b2. This SOD appears to be related to the lock screen, so fingers crossed today that it doesn't come back.
[Nook Color General] mpkrcl:
Which version of cm10 are these .zip files for? I have tried this on beta2 using the sd installer, but I just get an endless boot animation. The tablet interface is really the only reason I'd want to update from cm7.
[Nook Color General] can80an:
Try clearing the Dalvik Cache, reflash and reboot ...
[Nook Color General] mpkrcl:
That's what I tried the first time...you mean wiping the dalvik cache within CWM for SD, correct?

Just tried it again, same result...loaded cm10 beta 2 via verygreen v5 installer, reboot to CWM for SD and clear cache and dalvik cache, install the update zip....and endless animation...
[Nook Color General] leapinlar:
Which update zip are you using on which rom? Mateorods zip was hard coded to install to emmc. I don't know if he modified his newest one to be generic.

---------- Post added at 07:58 PM ---------- Previous post was at 07:56 PM ----------

My zips were for Alpha 1. I have not updated them for beta.

EDIT: Here are beta1 zips updated to be generic. Can be used on emmc or SD. For emmc flash with normal CWM and for SD flash with Alternate CWM for SD.

EDIT2: Attachments have been moved here.
[Nook Color General] mpkrcl:
Thanks...I am running beta 2 right now...I tried your beta 1 zips, and same result. I created the beta 2 "hard coded" emmc updates via the method posted earlier....but I don't know what needs to be done with them to make them "generic"
[Nook Color General] leapinlar:
Generic means that the zip updater-script in my zip mounts system as /system instead of as /dev/block/mmcblk0p5, which is on emmc. So if you use the alternate CWM for SD, it puts it on SD. If you use an unmodified CWM it gets put on emmc. With mateorod's zip it always goes to emmc.

To fix the zip for beta2, take the three files out of /system/framework in your zip and put them in the same location in my zip, replacing my files. Then it is generic with the beta2 files.
[Nook Color General] andrewddickey:
Here's the tablet ui zip for Beta 2
[Nook Color General] leapinlar:
Those are still hard coded to emmc. Attached are generic versions.

EDIT: Attachments have been moved here.
[Nook Color General] mateorod:
Leapinlar,

I have to be honest, I have paid very little attention to this since you first posted a fixed set for alpha. I figured you had it under control and didn't think about it again.

But maybe I misunderstanding something.

Are you saying that your fixed versions of the zip can be used for regular CWM, to be flashed to the emmc? And if so, is that basically saying that they are superior (since they are useful for people) to the original zips I posted?

And if so, considering the fact that the updater-script I am using is 100% exactly quoted from the aplha/betas released by our erstwhile CM10 team, what exactly is the benefit of them using the updater script I/they are using?

Finally, I don't believe that you are all modding the updater script for the alpha/betas, so why does that same updater-script work for complete roms yet has to be modified for sdcard?

Perhaps I should have numbered those questions. I ask because if the updater-script can be (and in fact is) improved by your additions- to the point where it works for both emmc and sdcard installs, then we should knock out the improved edify practices and send them upstream.

Just because the current method happens to work doesn't mean that it is the best method. But, like I said, I have not really looked at sdcard installs at all, like, ever, and this could be a recognized dead-end.

Edit: And while we're talking...since you are posting fixed sdcard zips, would you just pick a post and use that to store your uploads? Then I could just link to one sdcard-centric post in the OP.
[Nook Color General] lollyjay:
I'm posting that I downloaded and installed the new tablet mode and noticed that the context menu (three dots) stopped working. I then went back to the b1 version (beginning of this thread) and it's working again.

QI0CM9787SV

12/11/2010

ES1.2

cyttsp

CM10 Beta 2, Trebuchet, Tablet Update-b1
[Nook Color General] mateorod:
Ha! Guess they broke something in frameworks, then. There's the workaround people have been asking for, then. Could just as easily replace the files from restore if they don't want tabletUI but DO want the menu fix.
[Nook Color General] leapinlar:
You are taking your script from a ROM zip which are always hard coded to go to emmc. My zip is more like gapps that just mounts /system. The CWM recovery you are using defines where /system is for you so it knows where to put it. Almost all zips use the generic /system designation unless they want it to go to a specific partition (like CM wants for ROMs). And yes, my zip is superior to yours because it can be used for either emmc or SD depending on which CWM you are using (normal or modified for SD).

For ROMs, you do want to use the script as hard coded, that is why CM has it that way. But for other zips like gapps and zips you are creating with your AutoPatcher, they should be generic and let CWM decide which partition is /system. That is why gapp zips work on all devices and they do not have to be modified for a specific device. The CWM takes care of it for them.

If you modify your zips in the first post to be generic, I would not have to modify them for SD users and attaching them to different posts. (EDIT: See below for consolidated location of modded zips.)

BTW, thanks for doing this. I don't use it because I like the phone interface, but I know a lot of users appreciate it.

---------- Post added at 12:51 PM ---------- Previous post was at 12:18 PM ----------

Thanks for that! I usually use PA 1.6, but I have a spare SD that I play with CM10. I just updated to Beta 2 and lost the menu button. Flashed the B1 restore zip that I made for SD and Whammo, menu's back. I don't know what else I am missing from the B2 frameworks, but I need that menu.

EDIT: All of my TabletUI zips modded to be generic have been moved here.

EDIT2: Mateorod: I just looked at your Autopatcher link. Amazing. I now understand why your zips come out the way they do since you are running autopatcher on a ROM zip. I don't think there is anything you can do to make them automatically come out generic for SD users. The zips have to be manually edited. I will keep doing that when I can. I will also move the modification instructions that I posted earlier to that consolidated post linked above in case users want to do it themselves. You can just refer all SD users there.

EDIT3: Mateorod: I just reread your earlier post. I did not answer one of your questions. You ask why the ROM zips work when installing to the SD without modification. That is because we do not use CWM to flash ROMs to the SD (if we did, the ROMs would end up on emmc). We use the script that verygreen wrote for the SD. It dynamically modifies what is in the zip to make it install properly on the SD. That is why your update.zip should have worked using the script installer. It did install it, but there was a problem with dalvik-cache that prevented it from booting properly. So I had to use the Alternate CWM and then is when we have the issue of generic vs. hard coded.
[Nook Color General] mateorod:
I just saw this, somehow. My subscription to this thread is not being honored for some reason.

I had just updated the OP for beta 3. I used your updater-script and naming practice (I think) so it should be ok for all Nooks.

Edit: Trouble with upload. Give me 15 mins... Done.

Yeah, this mod was actually originally used for Nexus 7 and some of the other 7 inch tabs that didn't have tabletUI. But then the Nook needed it all of a sudden, so I brought it out.

I will redo the OP a little later to point to your post for alternate zips, so if I made a mistake with the universal zips, people should be able to find where to go. I have never used an sdcard install and didn't realize it had it's own recovery. No wonder that bootable CWM card I made so long ago gave me trouble. I just went back to non-Touch, lol.
[Nook Color General] can80an:
Mateorod or Leapinlar

Does this universal zip eliminate the need to use the alternate CWM install method for installation on an SD card or can we just use the SD recovery to install

Edit ... Just tried using SD recovery with just the universal zip and it did not work for me ...
[Nook Color General] RoboticBuddy:
I just installed B3, and the Tablet UI mod, and it works like a charm! :D

I just have one question, is there a way to change the font of the clock, and place it all the way to the right?
[Nook Color General] leapinlar:
No, you still need to flash with the alternate CWM for SD. He called it universal, I called it generic, but it is exactly like I would have modified it for flashing with CWM for SD. Don't forget to wipe dalvik cache too.
[Nook Color General] DizzyDen:
You can unzip the tabletui zip file and refresh the system folder in the ROM's zip file... or to make it easier... use my IMEI Generator with its custom patche option and include the tabletui in the ROM zip file before flashing.
[Nook Color General] dparrothead1:
As info, the B3 zip works with B4.:thumbup:
[Nook Color General] mateorod:
I have updated the program in the OP as well. For the Nook Color it will output zips that work on either SDcard or EMMC installs.

Thanks to Leapinlar for the info about the SDcard install needs.

As we move towards nightly builds here (There will be at least two options for nightly builds here soon, how crazy is that? The Nook is great) I wanted people to have the ability to patch their roms on their schedule.

When the nightlies get going, I will revamp this thread with more info better instructions. Let me know how it works for you if you try auto-patcher 2.4.2.
[Nook Color General] Kitten:
CM10 + Tablet UI: notification drawer issue

I'm on CM10 b4 + Tablet UI + Nova launcher and have an issue with the notification drawer. It is not customizable in any way and always has a default view (Airplane mode, Wi-Fi, Bluetooth etc). Any changes made in Settings -> Notification drawer have no effect.

"Power control" widget with 5 buttons is not customizable as well. In CM7 I was able to remove buttons I'm not using but not in CM10 with Tablet UI.

Both issues are there since I've started with CM10 b2, whatever clean install or update. Firstly I've posted this question in CM10 betas devs thread but the problem seems to be related to Tablet UI. Can someone confirm or it is only my bad luck?
[Nook Color General] lollyjay:
Yes, I can confirm that I have the same situation. Phone UI is customizable but tablet is not.

QI0CM9787SV, 12/11/2010

ES1.2, cyttsp, CM10 Beta 4

Tablet UI, Go Launcher HD
[Nook Color General] mateorod:
Well, this was kind of a hack to simply enable the tablet UI. There have been some improvements to the code, and I can probably enable it to the point where the tablet UI is turn on/off in settings itself.

let me look at it tonight/tomorrow.
[Nook Color General] can80an:
You'll have to forgive my ignorance, I have no idea what's involved in doing this stuff. Could this routine not be incorporated into the ROM itself and as you want to do - be able to toggle it on/off?

Or am I just naive? :)
[Nook Color General] lollyjay:
Hi mateorod,

First, I love the tabletUI! Thanks for your work to bring it to us. Just checking in to see if you have any solution to making the notification bar customizable.

QI0CM9787SV, 12/11/2010

ES1.2, cyttsp, CM10 Beta 4

Tablet UI, Go Launcher HD
[Nook Color General] dparrothead1:
Update-universal-b3.zip works with Beta 5....at least on internal....:thumbup:
[Nook Color General] Darrian:
Thanks for this. It works great. I don't know why the option isn't part of the CM settings by default. I love CM10, but I don't understand why anybody would ever want to use a phone UI on it with a tablet.
[Nook Color General] stolenmoment:
USB mounting broken!!

This tablet UI patch apparently breaks USB data mounting. No volumes are readable from the desktop when plugged in. I was having trouble with mounting as USB storage from the desktop, so as a data point, I flashed today's daily (1120) without it (that is, I didn't install the restore zip), and /emmc was mounted as expected (although not /sdcard).

I've been using the universal-b3 patch.

Can we get this patch applied to the current CM10 source files?
[Nook Color General] nfreebairn:
power widget status bar after ui change

I did the tablet ui patch to cm10 and now the options: airplane mode, wifi, bluetooth, autorotate ... i cant seem to add to or remove any of those and i used to be able to. Is this fixable?
[Nook Color General] mateorod:
I don't think so. Some featuers are hard coded into cefrtain layouts, don't ask me why. I can take a deeper look at it tomorrow and see what I see. I have been meaning to take a little look at tabletUI anyway. But for the moment it is a known issue.