yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Q&A, Help & Troubleshooting] Quevvy:
So I thought it was showing me hidden devices, but it wasn't. When I view hidden devices, it was listed under Portable Devices. I then right-clicked and then uninstalled the driver to try and install the ADB drivers for the Kindle (ADB setup). When I plug it back into the computer, then it really doesn't show up on Device Manager (but again still on Devices and Printers)
[Kindle Fire Q&A, Help & Troubleshooting] sd_shadow:
Mine show as an android phone.
[Kindle Fire Q&A, Help & Troubleshooting] Quevvy:
While it does show up that way, adb devices returns nothing. I've even tried kill-server and start-server to try and restart it. This means that when I run the Kindle Fire Utility, it doesn't do anything because it can't detect the device.
[Kindle Fire Q&A, Help & Troubleshooting] sd_shadow:
Reboot pc
[Kindle Fire Q&A, Help & Troubleshooting] Quevvy:
Had tried it before, but tried it again: ADB comes up with nothing.

I even tried it on another computer, with similar issues. I also tried resetting it to factory defaults, which didn't help either.
[Kindle Fire Q&A, Help & Troubleshooting] sd_shadow:
you unzipped KFU, and not running it still zipped?
[Kindle Fire Q&A, Help & Troubleshooting] Quevvy:
I have unzipped it, and am running it from the unzipped location.
[Kindle Fire Q&A, Help & Troubleshooting] sd_shadow:
check specific drivers do they match this?
[Kindle Fire Q&A, Help & Troubleshooting] Quevvy:
I was able to get the ADB working on a Windows 8 computer, but then when KFU tried to reboot into fastboot mode, it said "waiting for device" for a long time. I think it has frozen. I've tried resetting it by holding the power button for 20 seconds, but I haven't been able to get past the splash screen.
[Kindle Fire Q&A, Help & Troubleshooting] sd_shadow:
it maybe in fastboot mode, try restarting KFU a few times, or try command prompt

fastboot reboot-bootloader

if fastboot commands work you can flash Twrp manually
[Kindle Fire Q&A, Help & Troubleshooting] Quevvy:
I tried fastboot, to no avail. Then I ran KFU and during it, Windows said that the ADB device had been recognized, and then the installation of TWRP supposedly went through (have not been able to check it). Then I tried installing FFF, but got the < waiting for device > that was the original problem. This was back on the original computer (Windows 7), but will try on the Windows 8 computer now that the Kindle is back on.
[Kindle Fire Q&A, Help & Troubleshooting] sd_shadow:
FFF installs with Twrp now

---------- Post added at 11:42 AM ---------- Previous post was at 11:40 AM ----------

if twrp installed boot logo should have changed

do you see a press power for boot options?

---------- Post added at 11:45 AM ---------- Previous post was at 11:42 AM ----------
[Kindle Fire Q&A, Help & Troubleshooting] Quevvy:
Hmm, the boot logo is still the same. I'm going to try and install TWRP again.
[Kindle Fire Q&A, Help & Troubleshooting] Quevvy:
So this is what seems to work the best for me (even though it doesn't work). With the Windows 8 computer, the Kindle is recognized in the ADB devices. I can run KFU and it actually is able to communicate with the device, but then the Kindle stalls when trying to reboot in fastboot mode. I cannot do anything with it in Windows 8. So I connect it to the Windows 7 machine, where I cannot install TWRP, but I can reboot it into normal mode, so it is not bricked, and it is still usable.

As far as I can tell, it never even got to the point where it would have started installing TWRP.
[Kindle Fire Q&A, Help & Troubleshooting] sd_shadow:
try manually reboot to bootloader with

[fastboot] stock 6.2.1 fastboot mode without rooting or cables

if that works manually flash TWRP with Fastboot.exe
[Kindle Fire Q&A, Help & Troubleshooting] Quevvy:
I think my issue was the computer not recognizing the device once it was in fastboot mode. I reinstalled the drivers (which I had done before), but this time they worked on the Windows 8 computer, so I was able to get TWRP and FFF on the device. I am working on getting CM11 on it currently. Thanks for all the help so far!
[Kindle Fire Q&A, Help & Troubleshooting] Quevvy:
Done!

I got it all working: TWRP, FFF, and CM11. As far as I can tell, there are no issues any more. I haven't tried ADB after putting CM11 on it, but I'm not going to worry about that since I already have the recovery and bootloader installed.
[Moto E Q&A, Help & Troubleshooting] newhor1z0n:
Fix

Open smd_init_dt.c and replace:

#include <smd_private.h>

with

#include "smd_private.h"

Should do the trick!

Bye the way, are you sure that the msm8610_defconfig should be used? I don't own the device so I'm not sure.

Cheers.

If I helped you or you like my work please click the [IMG="Thanks"]http://media.xda-developers.com/images/thanks.jpg[/IMG] button.
[Moto E Q&A, Help & Troubleshooting] dr34m3r94:
Thanks! I was getting the same error. Fixed now! :D
[Moto E Q&A, Help & Troubleshooting] sgh6:
smd_init_dt.c not found

i have this error but dont fix!!!!!! what should i do ??
[Nook HD, HD+ Android Development] jamus28:
CM10.2.1 Stable* for Nook HD+ (Ovation)

Credit to

-Verygreen and CM team for Ovation's CM10.2

-JustArchi for build optimizations

-Caldair for TabletUI patch

In this edition:

--- TabletUI capable. Caldair's patch stopped working after nightly Dec 5, 2013. I reverted minor commits to mainly translations and circle battery to allow the patch to succeed:

--- ArchiDroid Optimizations using GCC 4.7

http://xdaforums.com/showthread.php?t=2754997

The build using GCC 4.8 toolchain would not boot, but all other optimizations remain.

--- 30 media volume steps

--- 0.25x animation speed options under developer settings

--- Tiny reduction to cm10.2 speaker gain to reduce distortion at highest volumes.

--- STABILITY. Not my doing. In my experience, cm10.2 rarely reboots or crashes.

--- Flash videos works well enough

*Technically a June 14 nightly post-stable. However, there have been very few commits since the 10.2.1 stable was released months before.

**Touch fuzz 3x5 and Trim support are already integrated into the CM10.2 kernel. No need to flash an old separate kernel.

__________________________________________________________________________________________________________​

Installation notes:

-Compatible with New and old CWM recovery (no need to downgrade)

1)Format /system AND factory reset (data, cache), then flash ROM zip

2)Flash GAPPs for android 4.3. These work: http://xdaforums.com/showthread.php?t=2240652 (Use 4.3)

-DO NOT restore system data from CM11

3)First complete a full boot and setup of the rom before installing tabletUI patch

Download ROM: http://d-h.st/jpd

Download TabletUI Patch: http://d-h.st/5Ar

*DO NOT install the tabletUI patch without first completing a full boot and setup of the rom.*

__________________________________________________________________________________________________________​

TIPS

For a permanent menu button, I like to set my nook hardware key to open/close menu.

Xposed modules can do this or you can edit the gpio user key file very easily.

Go to the folder user - > key layouts - > gpio-keys.kl

Edit the file with system rw.

Change the word "HOME" to "MENU". Reboot.

Default trebuchet launcher slow? Try Nova or Apex from store. They work a lot better in my experience.

__________________________________________________________________________________________________________​

UPDATE 6/21:

Fixed ExFat support.

Added ROW I/O, Intelliactive CPU governor.

Get flash player below!

Enjoy!

__________________________________________________________________________________________________________​

Chrome Pop-up blocker perfect for visiting Dev-Host
[Nook HD, HD+ Android Development] jpisini:
Looks good I will try it out later this morning and let you know how it goes.
[Nook HD, HD+ Android Development] leapinlar:
You are going to be sorry you did that if someone with an HD gets a hold of this and tries to flash it. It will brick his device.

A better solution is to use the update-binary from a kitkat zip and the assert works.
[Nook HD, HD+ Android Development] jpisini:
Overall pretty good so far. Very smooth. Still testing.

---------- Post added at 11:29 AM ---------- Previous post was at 11:00 AM ----------

Screen can be a bit twitchy, anyone know if there is a fuzz kernel for 10.2?
[Nook HD, HD+ Android Development] jpisini:
Was trying an app called map book and it reboots my tablet. Never used it before so it could be an app issue and not a Rom problem but figured I would mention it if someone else wanted to try it.
[Nook HD, HD+ Android Development] jamus28:
I see what you're saying, but it's a bit of an exaggeration to say someone will brick. They'll need to boot into recovery and flash a new Rom.

I deleted the line because not everyone has the new kk recovery, and I want it to be compatible with both.

Dr. Marbles touch (3x5 I remember?) fuzz commit is already integrated. If it's laggy for you, maybe try to run a manual trim with lagfix and reboot. Also, the stock launcher is a bit slow, I'd get Nova or similar.
[Nook HD, HD+ Android Development] leapinlar:
If you did what I said it will be compatible with both new and old recoveries. That way you will not be responsible for causing grief for noob HD users.

The issue is not that the assert line exists, it is because the KK recovery using the older update-binary interpreter from older zips causes the assert statement to fail. If you put a new update-binary from a kk ROM in your ROM then the kk recovery will interpret the assert command correctly and it passes. The beauty is that older recoveries also interpret the assert command correctly using the new kk update-binary.
[Nook HD, HD+ Android Development] jamus28:
I didn't know the new assert line was backwards compatible. I'll upload a new one. Would using the newer update-binary be enough or do I need to alter the update-script as well?
[Nook HD, HD+ Android Development] leapinlar:
Just put the original assert line back and put the kk update-binary file in your ROM zip replacing the one that is built with the CM10.2.1.
[Nook HD, HD+ Android Development] jamus28:
Ok done. Thanks for clearing that up.

For those who didn't understand what leapinlar was talking about, don't worry. The ROM is exactly the same. No need to reflash.

Also, since there's some confusion around, I should mention that 3x5 touchfuzz and trim support have been in all cm10.2 nightlies/stables since november 23 and jan 8, respectfully. There's no need to download an old separate kernel from the one of the threads.

https://github.com/CyanogenMod/android_kernel_bn_omap/commits/cm-10.2
[Nook HD, HD+ Android Development] NishantM:
Took a break from cm11 due to the aggressive memory management affecting multitasking, and installed this. Pretty solid, smooth and speedy. Great work!

Just found out that my 32gb Samsung MicroSD card formatted with exfat file system doesn't seem to be mounting. It shows up fine in TWRP though.
[Nook HD, HD+ Android Development] jamus28:
Edit: Fixed below
[Nook HD, HD+ Android Development] NishantM:
It works fine on official 10.2 Nightlies and the stable 10.2.1. Just a heads up.
[Nook HD, HD+ Android Development] laofan:
This is the exact rom I have been looking for: a solid, smooth, stable rom with optimization.

Even though I jumped boat to 4.4 for one night, but 10.2.1 is my all time favorite! Now with this rom I don't think I would even need to use recovery in the future!

Thank you so much for the work, [MENTION=3813358]jamus28[/MENTION]
[Nook HD, HD+ Android Development] jamus28:
You know what, you're right. It's the kernel optimizations. I see a commit patch for it too. When I get the chance I'll recompile those files.
[Nook HD, HD+ Android Development] Jann F:
Could you also test setting the fuzz to 8x8?

Just as a test build, maybe separate?
[Nook HD, HD+ Android Development] jamus28:
Try this

http://d-h.st/jpd

Haven't had chance to test.

Also added Row I/O scheduler and intelliactive governor options
[Nook HD, HD+ Android Development] NishantM:
Thanks for the quick update and this fixed the mounting issues of sdcards formatted with exfat. Thanks a ton!
[Nook HD, HD+ Android Development] jpisini:
Been running this since yesterday morning looking very good fast and stable. Thanks for all your work.
[Nook HD, HD+ Android Development] krsboimo0o0o:
Loving this. One glitch I noticed was with the xposed framework per app settings made my status bar disappear. Odd and probably the fault of the app. But still loving this ROM. Thanks a million! My only request is a menu button in the status bar.
[Nook HD, HD+ Android Development] jpisini:
I am using exposed just using YouTube hacks hdmi fix and ad blocking. No issues so far.
[Nook HD, HD+ Android Development] jamus28:
I

So the one downside of a defunct user interface that Google left in their code for 4 Android versions is that it's not very customizable. Any apps that try to change the tablet ui layout will likely break it.

For a permanent menu button, I like to set my nook hardware key to open/close menu.

Xposed modules can do this or you can edit the gpio user key file very easily.

Go to the folder user - > key layouts - > gpio-keys.kl

Edit the file with system rw.

Change HOME to MENU
[Nook HD, HD+ Android Development] krsboimo0o0o:
I was using the per app xposed module to change perfect viewer to 160 to make the books on my book shelf look bigger and the same goes for systemui, to make the icons a little bigger.

One other issue, and again probably the fault of the app, Ninjamorph will always say not enough memory in system and immediately close. But its definitely not a deal breaker. This is my DD.

Thanks again, for the tip on the menu button. BTW this rom is smooth as silk for me.
[Nook HD, HD+ Android Development] robbierob03:
Just to get a couple more reviews in: installed earlier today with the suggested method (factory reset and format of system). Outside of a few app force closes after restoring user only apps through TB and one random reboot, this rom has performed very well after settling in. Transitions between apps and different pages is fairly smooth and fast. Every now and then I was getting a few missed touches but that may have just been before the rom settled. Think I found my new daily driver, thanks Jamus!
[Nook HD, HD+ Android Development] jpisini:
I noticed Aldiko acting very weird turning the page would leave me on the same page but then I could tap the center to bring up menu and tap again to dismiss and be on the right page. Aldo on 4.2 and 4.4 works fine same version.
[Nook HD, HD+ Android Development] jamus28:
Sounds like you may have restored data from a kitkat install. Even if not, data restores get finicky.

Most epub and pdf readers on android are slow and bloated.

I like repligo for pdfs,

FBreader for Epub is much faster than the competition and has online library access.

https://play.google.com/store/apps/details?id=org.geometerplus.zlibrary.ui.android&hl=en
[Nook HD, HD+ Android Development] wellersl:
I thought I knew this -

How do I swap the soft buttons with the status?

IOW - I want the soft buttons on the right...

EDIT: Oh, crap. I followed the instructions in the OP. Then I went to restore the back up -

but it just hangs at the CyanogenMod spinning logo. I tried clearing Dalvik and factory reset. No joy.

Help? Please?
[Nook HD, HD+ Android Development] jamus28:
You restored a titanium backup and now it won't boot? Be careful about restoring data between android versions (ie cm11 to cm10.2). Also, definitely do not restore system data that may conflict with the UI.

Just reflash the rom and start again. Don't flash tabletUI until you've completed a full boot cycle. So:

-Format system, cache, data

-flash rom, flash gapps

-Reboot normally into cm10.2. Enable developer settings, turn on advanced reboot

-Reboot into recovery and flash tabletUI
[Nook HD, HD+ Android Development] wellersl:
Hi, jamus28. First I obviously need to clear up a bit of confusion.

I followed leapinlar's Dummies Guide to make a bootable SD card imaged with cwm-recovery-ovation-3, with copies of your

"cm-10.2-20140621-optimized-OVATION.zip",

"YourZgappsXS-4.3-2014.03.16.zip", and

"update-tabletUI-20140621-OVATION.zip"

Then I booted from the SD card and backed up my existing 10.2 installation. Then I installed your files one at a time, as described in your OP, completely booting through to completion each time.

So...

Nope. Don't use it. Don't trust it. Not worth the risk/effort/aggravation to me. I don't like it. It doesn't like me. :p

That shouldn't cause it to get stuck at the spinning CyanogenMod logo - or would it?

That's where I'm at right now. On your ROM. With the Tablet UI. It seems I can flash pretty much anything I want and get it booted up no problem.

What I can't do is restore the back up I made when I first booted it from the SD card.

Ideas or suggestions?

BTW - Thanks for the really nice ROM. A few bugs but far and away very, very stable and quick. I just need want the navigation buttons on the right (for mainly personal reasons).
[Nook HD, HD+ Android Development] jamus28:
Oh I see, so you're restoring a cwm backup directly after installing this rom? That would just overwrite the rom completely with your old version of cm10.2 and doesn't make much sense. If you're desperate for your app settings and data, you're better off using titanium.

The fact that it doesn't boot with the restore may be due to number of things. One of which may have been creating the backup with the SD recovery and not an internal recovery... I'm not an expert in that. Search leapinlars thread.

Sorry, there's no way that I know of to swap the button position outside of reprogramming the framework.
[Nook HD, HD+ Android Development] wellersl:
That's OK. Thanks for getting back. I'm pretty happy with this at the moment since I remembered button savior.
[Nook HD, HD+ Android Development] laofan:
Two issues about the Tablet UI:

1. the battery icon is really small and hard to read digits when set to "Circle with Percentage". Actually I just need the Percentage, but If I just choose " Percentage", it only shows battery icon . Is there any way we could increase the font size of Percentage?

2. Is there any other way to change the toggles from " Airplane mode", "Wifi" Auto-rotate screen" " Brightness"" Notifications", "Settings" to some more, like sound?

and could we rearrange the order of the toggles?

I attach screen shot.

thanks
[Nook HD, HD+ Android Development] Scorchgid:
Bluetooth isn't working. Anyone else had a problem such as this
[Nook HD, HD+ Android Development] jamus28:
Bluetooth tethering with my galaxy S4 running CM10.2 works perfectly. What's the issue for you?

[MENTION=4314948]laofan[/MENTION] No. As mentioned previously, unless you can go in and recode the framework files yourself, you're stuck with tabletUI as it comes.

Despite the drawbacks of not having customization, I still prefer having everything on the bottom half my screen and having the saved screen real estate.

Plus, with cm10.2, I can watch amazon video among other flash sites without issue.
[Nook HD, HD+ Android Development] krsboimo0o0o:
Anyone know what font is used by the lock screen clock or where the PNG files are located for the circle battery?
[Nook HD, HD+ Android Development] Scorchgid:
I'm unsure, it would turn on and I can sort of add devices to it but it will refuse a connection when attempted and in some cases not find devices at all. I decided to use a different from based on CM11. That rom does not have any issues.
[Nook HD, HD+ Android Development] lordsilencer:
Just want to know if your fixed Tablet UI can apply to the official CM10.2.1 rom?
[Nook HD, HD+ Android Development] krsboimo0o0o:
Well I never got ninjamorph working on this ROM, it works on the yellow kernal ROM, but adb pull and push work, so here's a screen shot of your awesome ROM running my favorite theme. It is a bit old school but hey its just my personal preference. Tablet UI for us lefties plus PNG files from 3.2 and other sources. I could have just used the theme manager but I like this as the default theme. I love your ROM its as smooth as silk.
[Nook HD, HD+ Android Development] :
WHERE'D YOU GET THOSE HONEYCOMB .PNGs?

---------- Post added at 12:24 PM ---------- Previous post was at 12:13 PM ----------

Can't verify that it won't but in this thread

http://xdaforums.com/showthread.php?t=2275939

[Nook HD+ / MOD] CM10.1 EMMC/SD Install "tabletUI" modification - Updated: 7/12

It appeared that had to different patches for each new CM 10.2 nightly, so I think that this patch may not work for CM 10.2 stable.

But, I can't verify this, as I'm on Succulent's CM11. If you'd make a backup, and flash this tablet ui patch, worst that could happen is that you'd have to dirty flash CM10.2 to restore system ui.apk back to normal phablet ui, or just restore your backup.

Tl;dr

Probably won't work but you could

Backup and try to flash the patch, if it doesn't work dirty flash CM again, or restore a backup
[Nook HD, HD+ Android Development] jamus28:
No it won't sorry. That's why i built this version. It's the same as official cm10.2.1 plus my additions mentioned.
[Nook HD, HD+ Android Development] krsboimo0o0o:
Jamus in the op had to roll back a few commits to make the tablet ui work. Its just as good as the official 10.2 but better! If you want 10.2 and tablet ui, this is the ROM you want.

As for the honeycomb PNG files just use theme manager and Google cm10 honeycomb theme, look for v2.4. It is much easier that way. Adb pull, then decompile & recompile then adb push can be a pain if you mess a small detail up. Renaming the hc pngs to match what jellybean uses and .9.PNG for example. Errors in framework-res can cause it not to boot and errors in systemui can cause the status bar to be gone as well. So stick with theme manager or get real comfortable doing advanced restore system. Just my 2 cents. Also some of the pngs I used came from that so I can't spread that around like its mine or without permission. Google it, its on xda I believe, make sure to thank them. And some came from the hdpi folder in a Xoom honeycomb rom just renamed them to match jb's needs.

Another odd thing, in per app DPI settings in xposed, setting things to 340 makes them much bigger. I use that on a few apps in that screen shot.
[Nook HD, HD+ Android Development] melvinchng:
Just curious, is it smoother than cyanogen mod 11? ( just bought a nook)
[Nook HD, HD+ Android Development] adwait.bhandari:
No. CM11 is smoother and faster than this. But this is bretty good too.
[Nook HD, HD+ Android Development] wellersl:
I came back to this one from CM11. This is my daily driver.

BTW - Everything in that danasoft.com sig widget thingy is wrong. :D
[Nook HD, HD+ Android Development] krsboimo0o0o:
Is there anyway to increase the ram? It only shows 783mb available for use. 241 mb missing. When ever I close all apps it shows I have between 220mb to 330mb free. Is it possible in this rom?
[Nook HD, HD+ Android Development] leapinlar:
No, it is not possible with any ROM. The missing ram is used but the operating system for things such as the screen buffer and cannot be changed.
[Nook HD, HD+ Android Development] PMikeP:
I agree with you. I'm pretty much liking CM11 since late June builds, but I wish they'd put zRAM back in CM11 like Succulent has in his build, and as CM had in 10.2.1. I find that my aviation moving map is always having to restart if I have my web browser running. Makes "multitsking" really slow with our limited RAM.
[Nook HD, HD+ Android Development] FirePsych:
What recovery were you using and did you have to downgrade your recovery or bootloader to go from KK back to JB?

Never mind. Wiped everything 3x and restored a 10.1.3 nandroid. That worked fine. I expect I should have no problems with 10.2.
[Nook HD, HD+ Android Development] infra_red_dude:
Just wondering if this has been reported beofre (sorry if it's a duplicate report), the mute icon doesn't show up in the status bar with tabletUI patch. Is this expected?