yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] Kubombelar:
thanks for your assistance. Seeing that you posted the original thread, i thought i would update you. I think i accidentally found a fix for graphical glitches in carbon fibers. When you tap carbon fibers, you hit interface next and tap lcd density. You go on step 1 (change lcd density to stock value) and choose 320. Skip steps 2 to 6 and powe off completely not a reboot. Power on, go back to carbon fibers and play around with various options and you will not notice any graphical glitches. I havent had any in 4 hours. If it works sucessfully for you maybe you could update original post
[Nook HD, HD+ Android Development] king200:
That's a great find! I experimented a bit editing the build.prop file line, ro.sf.lcd_density and tried a few different values. 320, 300 and 290 worked. 256 (B&N) and 280 didn't. This post http://xdaforums.com/showthread.php?t=2072822, guided me.

I tested a few apps only. Now to determine if I like the larger size of the graphics.
[Nook HD, HD+ Android Development] marscandybars:
been running this rom version and cant seem to scan for "new" access points (wifi)
[Nook HD, HD+ Android Development] jisoo:
I believe the bug is caused by the layouts because this bug only occurs on the official manta (Nexus 10) and other unofficial tablet builds. There is some dp threshold which causes the selection of a buggy layout and breaks Carbon Fibers (as well as the navbar in portrait mode which we avoided with a dirty hack), and the Carbon devs have never been able to fix it because none of them have large-sized tablets.

There's a module for the xposed framework called app settings (xda thread) which can be used to set per-app resolution and dp values. (By the way, if you want to try xposed, I recommend going with the new beta version which has many performance improvements: link)

Playing around with the different settings, I notice that setting the resolution to 600x1024 eliminates the bug in Carbon Fibers. This makes me wonder if the bug also occur on hummingbird?

Definitely a good find by Kubombelar, thanks for reporting.
[Nook HD, HD+ Android Development] Kubombelar:
speaking of bugs, my wifi has been off and am by a farm with no wifi connections. But my battery stats says my wifi has been using 5% of my battery for the past 6hrs. Not normal right?
[Nook HD, HD+ Android Development] gotbass:
It could be that setting which allows scanning for networks even if you've switched WiFi off. Apologies if I'm just stating the obvious.
[Nook HD, HD+ Android Development] jamus28:
I was actually referring to the wifi changes under android_hardware_ti_wlan on 11/11 which are merged into carbons manifests, like:

http://review.cyanogenmod.org/#/c/51224/

http://review.cyanogenmod.org/#/c/51130/

I just noticed a significant wifi speedup since upgrading from my early november build, which is why I thought those may be responsible.
[Nook HD, HD+ Android Development] Guiyoforward:
Hi, the newest carbon build is the one on the OP initial post? No update? Thanks!
[Nook HD, HD+ Android Development] jisoo:
Thanks. I'll make an updated build with these commits and give it a go.

There have been no updates since the latest ones in the initial post, that is correct. I'll try the Wi-Fi commits pointed out by jamus28 above and update the first post later in the week.
[Nook HD, HD+ Android Development] markrs:
Had a Google but can't find out how to backup the /boot partition within Cwm. Any help would be very appreciated :)
[Nook HD, HD+ Android Development] Guiyoforward:
Great, can't wait! Thanks
[Nook HD, HD+ Android Development] Guiyoforward:
Hi, any news on 10.2 CM STABLE-based Carbon?

Thanks!
[Nook HD, HD+ Android Development] bowlofturtle:
Is there a problem with auto brightness?
[Nook HD, HD+ Android Development] king200:
I don't think the device has auto brightness. Carbon Fibers, Status Bar, Brightness Slider helps to adjust brightness.
[Nook HD, HD+ Android Development] dangrayorg:
What was done to the ROM to fix Bluetooth tethering? Is it implementable in other CM ROMs for the Nook?
[Nook HD, HD+ Android Development] bpaulien:
The device doesn't have a brightness sensor. No ROM will have this feature. Not supported by hardware.

EDIT: THIS WAS A reply to the previous question which I see was already answered. It had nothing to do with Bluetooth. Sorry.
[Nook HD, HD+ Android Development] DarkStarr:
Can we get some fixed DLs? It seems most of the links are broken as well as the latest trim kernel links.
[Nook HD, HD+ Android Development] angelofmenoth:
The trim kernel from the CM 10.2 threads works.
[Nook HD, HD+ Android Development] entonjackson:
Is this ROM stable, compared to CM 10.1.3 ?

Does WiFi work?
[Nook HD, HD+ Android Development] stegg:
jisoo, i tested the last CM build (1210) for an hour and... i switched back to your rom! it's really faster and smoother than CM, don't know what Carbon dev made but the difference is noticeable.

what about adding the new 3x5 touchscreen sensitivity? :)

cheers from foggy italy
[Nook HD, HD+ Android Development] entonjackson:
does wifi work?
[Nook HD, HD+ Android Development] stegg:
sure!
[Nook HD, HD+ Android Development] DarkStarr:
FYI the kernel from the other thread does work just fine. I had a bit of lag using the trim kernel but I had previously been running carbon without any trim so perhaps the lag I experienced was due to the first trim run? It was not immediately after flashing the kernel but a few hours afterwards.
[Nook HD, HD+ Android Development] king200:
I use no software decoding with MXPlayer Pro (v 1.7.17) and it works fine. Youtube is working fine too.

---------- Post added at 01:54 PM ---------- Previous post was at 01:46 PM ----------

What bugs there are are very minor. Most are in the enhanced features of CarbonRom vs CM. The developer is very attentive and problems with things like WiFi and Bluetooth tethering were handled promptly.

The best way to know is to try it.
[Nook HD, HD+ Android Development] TheDannemand:
As for using verygreen's trim kernel from the CM10.2 thread, jisoo posted Carbon-adapted versions of that kernel in a post here dated 11/25, linked below, which I would think are a better fit for this ROM.

http://xdaforums.com/showthread.php?p=47818336

I just tried both download links in that post, and they DO work if you click the small Download button - the big buttons are spam traps.

[MENTION=5347546]jisoo[/MENTION]: It would be great if you can add those links to the opening post next time you come by :)
[Nook HD, HD+ Android Development] DarkStarr:
Yea I had attempted those links but evidently DevHost was having issues so they were broken when I tried them.
[Nook HD, HD+ Android Development] jisoo:
Thanks for waiting. I've been super busy with work recently. I did do an updated build, but I just didn't have enough time to test and upload it. I've found some time now (and the build has been working fine for the past 7 days), so I'll update the OP in the next few hours with the new builds.

Carbon has not marked any "stable" builds for 4.3 as far as I can tell, and development work has moved on to 4.4 on the officially supported devices. This means that there won't be any "stable" (in quotation marks again as this is a somewhat arbitrary designation) for 4.3 (i.e. CM-10.2) builds, and in fact the latest update (which will be in the OP in a few hours) will be the last update for 4.3.

Hopefully we can start working on 4.4 (CM-11.0) builds soon, but I can't make any promises.

There is an additional network configuration service which needs to be defined for Bluetooth tethering to work. This service definition needs to be included in the device-specific sources for ROMs to enable the feature.

It's an extremely simple fix (as you can see in my commit for ovation: cb0d2bc624ea8ea09a0498aef04b296935620ab2), and should work on any CM/AOSP based ROM which does not have this service defined.

Dev-host is unfortunately not up 100% of the time. However, they are the only hosting site I have access to.

Thanks for the feedback. Can you point me to more info on the 3x5 feature? I have not heard of it before.

The only difference between CM and my Carbon kernels I can think of would be related to the ramdisk, so on some builds using a CM kernel might break the ROM. However, I've stripped out the telephony packages from these unofficial Carbon builds, and as these are the processes that usually break with a wrong ramdisk, it should be OK to use CM kernels most of the time with this ROM as well.

I'll add a link to the trim kernel post into the OP, but I'd rather not put direct download links because users who don't know what trim is (and why it could be dangerous to have it) may get confused.
[Nook HD, HD+ Android Development] TheDannemand:
Thank you jisoo, that sounds great. My nook HD+ has been on CM10.2 (and before that CM10.1) but I've been watching this one and wanting to try it out. With your latest update, I'll give it a shot this weekend.

I think your approach (and caution) with the trim kernel is good (and prudent). My impression from following the various threads is that we haven't seen any reported bricks since verygreen released that kernel with the patch. Of course we DO have bricking reports from CM10.1 when people just ran lagfix.

Great work, thank you.
[Nook HD, HD+ Android Development] Guiyoforward:
Great - and thanks a lot! I thought Carbon was mainly based on CM (my mistake), that's why I asked about a stable Carbon.

If you have a minute and time for this, could you explain why Carbon is faster/smoother than CM? (that's what I feel - your mileage can vary!). They are based mostly on the same code as far as I can tell. Are there any optimizations or chunks of unnecessary code removed?

Thanks again!
[Nook HD, HD+ Android Development] stegg:
i am referring to this kernel mod

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

i'm actually using the 3x5 trim kernel with your 1029 build: all's OK and clicking a link is definitely better
[Nook HD, HD+ Android Development] king200:
I'm trying the kernel with the 1205 build. I really don't see much because I didn't notice the problem the 'touch-ovation-kernel-trim-3x5.zip' was supposed to fix. I haven't seen an consistent, objective test.

I'm guessing shortcuts with swype functions might behave better.
[Nook HD, HD+ Android Development] TheDannemand:
[MENTION=5347546]jisoo[/MENTION]: You may want to update the following paragraph in the opening post, since you now posted a December build. I know, just a detail, not a functional issue ;)
[Nook HD, HD+ Android Development] jisoo:
Carbon Team says they are using mainly AOSP as base, though there are a lot of commits coming from CM as well (there's also a lot of stuff from Paranoid Android, AOKP, and Chameleon OS).

The device-specific trees I'm using are from CM, so a big thank you needs to go to the CM devs (verygreen, Hashcode and drmarble) who've done a lot of work to get all of the hardware supported.

I can't say what the big differences in the codebase between Carbon and CM are. I think the biggest difference is that the CM nightlies (and stable builds) need to support a huge variety of devices, so there are occasional code commits which are not so useful for our devices (and which in some cause issues).

Of course we are also able to strip out some of the code (like telephony) which we don't need but which CM cannot remove without impacting all the other supported devices.

I believe you can just flash those kernels and they should work fine with this ROM as well. Let me know if this is not the case, and I'll make custom kernels for Carbon.

I do use the Swype keyboard, but have not noticed any problems with the touch screen accuracy.

Thanks, that's a good point. I've updated the paragraph now.
[Nook HD, HD+ Android Development] king200:
The kernel seems to be working fine.

I am referring to the "Swipe Action" for a desktop shortcut. They behave a bit erratically now and I have avoided them. It is nice to 'swipe' the messaging shortcut to get the email app instead. It works beautifully with "AppDialer" from the Playstore. You 'swipe' the app drawer shortcut to see the T9 app finder.

I've observed nothing yet. Thinking of the area that my finger touches is constant for a 4 inch and 9 inch screen, would lead me to believe that there was merit to this concept.
[Nook HD, HD+ Android Development] LivinOne:
Just got my Nook HD+ and considering rooting it and putting on Carbon. I have used Carbon on my SG3 for many months, just updating to the unofficial 4.4.1 -- while it is very smooth/fast, Carbon ROMs 4.3 & 4.4 for SG3 eat battery 2x as fast as 4.2 builds for me.

How much faster/smoother is this Rom compared to stock?

What affect on Battery life does it have?

Thx for the input.
[Nook HD, HD+ Android Development] laofan:
Personally speaking, they are very close in speed/performance. It is just a personal taste of different features.

battery life it is very hard to tell( Carbon and stock are both very good). I usually charge them over night and I haven't run into battery low so far. So probably 2 days?

Test it yourself you would find out how it actually

---------- Post added at 06:43 AM ---------- Previous post was at 06:38 AM ----------

Not sure if that only happen to my Nook hd+.

Every time I go to about tablet-->status, it just FC.

On 12/5 carbon. non trim kenel. I do wipe data/cache.ect.

recently flash 3X5 touch fix but I could not tell if that is the reason.

Anyone have the same issue?
[Nook HD, HD+ Android Development] kaleavi:
Yes, same thing here. I have flashed or modded nothing on the rom, flashed just the rom only but i see the same fc. So, not just you. FC does not bother me though.
[Nook HD, HD+ Android Development] riboswitch:
FIXED EVERYTHING, READ LAST PART ONLY :)

Uff i totally screwed up.. I wiped everything expect the bootdata and now I got these problems.

TWRP is installed on emmc.

I installed the rom, but I get the "Unfortunately, Carbon Fibers has stopped."

Also I cant write, a window pops and closes fast.

Also the "back" button is not working... ah and I Installed the Touch sensity Kernel.

edit:

The tablet gets regocnized in windows, but I cant access it.

USB Debugging and MTP is enabled..

________________________________

Wiped everything again and now it works like a charm!

Still I cant acces my nook in windows, any help?

(gets recognized but cant access it)

2nd edit: Deinstalled in windows the adb driver and now it gets connected properly!

___________________________________

It the Tablet UI missing in this release?
[Nook HD, HD+ Android Development] king200:
Backup. Wipe system and data. Flash only the rom and correct gapps. Boot to system. The Carbon Fibers message is normal. See if your bugs are gone. Flash the desired kernel and boot into system again. If problem, flash kernel for THIS rom. Advanced restore,data only,no bootdata.
[Nook HD, HD+ Android Development] riboswitch:
Is there a possibility to change the tabletUi?
[Nook HD, HD+ Android Development] jisoo:
TabletUI was stripped out of the AOSP code with 4.3. Some ROMs added support (PAC, for instance), and some can be patched to support this (CM).

Unfortunately, Carbon is neither and the amount of work required to integrate TabletUI is non-trivial.

If there was a patch set floating around which added TabletUI, I would be happy to have a look at bringing this into Carbon, but I've have never seen one, and don't have the capacity myself to work on this.
[Nook HD, HD+ Android Development] beyored:
Have you tried xposed module for tablet ui....

Edit....I just tried and it didn't change a thing....
[Nook HD, HD+ Android Development] RALIR:
Switching from cwm 6028

Hi Jisoo,

Currently I am on CWM-6028 on a Nook HD+. My Nook is more than a year old. I would very much like to try your Carbon ROM. Per your post, I need to be CM 10.2. I am wndering if it would be possible to flash your Zip from CWM-6028. Or do I really need to be in CM 10.2. I have asked this question of Leapinlar also. Hopefully one or both of you will be able to guide me to your Carbon ROM.

Thank you in advance of your help and guidance.

Best Regards,

RaliR
[Nook HD, HD+ Android Development] jisoo:
Hi. You don't need to have CM-10.2 to install this ROM. The only thing you need before installing is a custom recovery (CWM or TWRP) and obviously backups of what you want to carry over, as you do need to wipe both /system and /data partitions (internal storage does not need to be wiped).

I had a quick look at the CWM/Stock root install by leapinlar (thread), and I believe you currently have only a modified stock ROM and therefore no custom recovery installed on the emmc.

This means that you need to first install the recovery. You can look at verygreen's original instructions here to understand how this is done. Then just remember to wipe /system and /data, flash Carbon + 4.3 gapps instead of CM, and you should be good to go.

If you do want to have the option to go back to stock, you need to look up instructions on how to back up and restore the stock nook ROM (when I bought my nook second-hand, it already had CM installed, and I've never had to deal with the stock ROM).

Also, if you need to have your app data preserved, you need to use something like Titanium Backup or Helium Backup to accomplish this, obviously backing up before you install anything else.

I'm sure other people in this thread can also give me detailed instructions in case you get stuck.
[Nook HD, HD+ Android Development] RALIR:
Hi Jisoo,

Thank you very much. Everything seemed to have worked beautifully. From what I have seen by playing around with this ROM so far, I have been very pleased. My NOOK HD+ looks and feels so different. Again I want to express my thanks to you for a job well done.

Best Regards,

RaliR
[Nook HD, HD+ Android Development] dbh369:
I have loved the ROM, but still getting crashes on any browser. I'd tried rebuilding from a clean wipe twice, still getting them. Trying the latest nightly of cm10.2 now, so far no issues.
[Nook HD, HD+ Android Development] laofan:
If you want to figure out why, here is what you could do

1. check package MD5. both carbon and gapps( do you install the right gapps?)

2.write down you install process here. maybe there is something wrong.( just maybe)

3.upload a catlog.

As far as I know, carbon is doing great for daily drive.

Only "issue" I know is Carbon fiber sometimes need a little bit time to load and About Phone FC.

Not any browser issue so far for me.

Anyway, cm10.2 is also a good choice.
[Nook HD, HD+ Android Development] jisoo:
Some users have reported similar issues that were caused by AdAway hosts file filtering.

I'm running AdAway myself but have not had browser crashes, so the actual origin of this bug is still unclear.
[Nook HD, HD+ Android Development] dbh369:
Thanks, I actually did that a few pages back... Its a weird bug, just shuts down without an error message at all. Maybe kit kat won't have the issue!:)
[Nook HD, HD+ Android Development] bpaulien:
I finally decided to give this a try after a couple months on SlimBean. So far so good. One question I had about a fairly minor issue is it seems like the "CRT Screen off" feature-on the display settings, behaves kinda flaky. There are 3 options under the animation mode, portrait horizontal, portrait vertical, and orientation dependent. None of them behaved the way I would expect.

* When in portrait horizontal mode

- Held in portrait orientation, when screen is turned off, the screen quickly switches to landscape and the beam goes the short way across the screen.

- Held in landscape orientation, when screen is turned off, the screen quickly switches to portrait and the beam the short way across the screen.

(the beam behaves as expected in both cases but the screen does the opposite)

* When in portrait vertical mode

- Held in portrait orientation, when screen is turned off, the screen quickly switches to landscape orientation and the beam goes the long way across the screen

- Held in landscape orientation, when the screen is turned off, the screen quickly switches to portrait orientation and the beam goes the long way across the screen.

(again, beam does as expected, but screen does opposite )

* When in Orientation dependent mode

- Held in portrait, the screen quickly switches to landscape orientation and the beam goes the short way across the screen.

- Held in landscape, the screen quickly switches to portrait orientation and the beam goes the short way across the screen.

(this time, it seems to behave like the portrait horizontal mode )

Any way, that was probably too long, but I just wanted to point it out.
[Nook HD, HD+ Android Development] LivinOne:
Just installed... THANK YOU!!!

I got the Nook HD+ 2 weeks ago and loved the screen, hated the slow response and launcher is crap.

Your ROM makes it a really nice machine now!
[Nook HD, HD+ Android Development] jisoo:
It looks like you uncovered a rotation-related bug I was not aware of. I am not using the CRT effect, so never noticed it.

Unfortunately, I don't want to do another build just to issue this bug, as I'm trying to use my spare time on building for KitKat, but I'll keep this bug in mind and will address it as soon as I have a working 4.4 build for testing.
[Nook HD, HD+ Android Development] bpaulien:
Awesome. No worries, not looking for a quick fix, just wanted to bring it to your attention.

Looking forward to seeing the 4.4 version.
[Nook HD, HD+ Android Development] Esotic:
Mulitple Users/Profiles

I'm trying to setup a "Guest" account on my Nook HD+ using CarbonRom. Under "Users & Profiles" it keeps saying the guest account is "Not set up". The guest account icon is on the lock screen, but if I click it the device reboots. Has anyone else gotten this to work?

Thanks,

Dave\Esotic
[Nook HD, HD+ Android Development] arh2o:
AWESOME Jisoo! Can't wait to give the 4.4 build a spin :laugh::good:
[Nook HD, HD+ Android Development] supergroverthm:
I also can't wait for the 4.4 build. Someone has posted a Nook HD+ booting into 4.4....http://m.youtube.com/watch?v=w0r89JbSUp0&desktop_uri=/watch?v=w0r89JbSUp0
[Nook HD, HD+ Android Development] jisoo:
That's interesting. Fellow Korean also playing with the same device.

By the way, does anyone know what the minimum version for TWRP or CWM you need to install 4.4? I'm stuck with a build that I can't test because my current recovery does not support 4.4
[Nook HD, HD+ Android Development] bpaulien:
I'm not sure what happened but I keep getting a notification on my nook that the SDcard is blank. I popped it out and back in, still shows blank. I even looked at it with a couple different file managers and they both indicate that it's blank.

I almost panicked, so took it down to my computer and read it, and it's definitely not blank. I all my videos, backups, various ROMs, and everything else I expected to be there was there. But as soon as I pop it back in the nook, it shows up blank again.

Does anyone have any idea what is going on? Why would the HD+ all of a sudden not be able to read my SDcard? I accessed it earlier today so I'm not sure what happened to lose it. I even tried booting into CWM recovery, and it couldn't read my card either.

It is a 32gb SanDisk type 4 which I've had for about as long as I've had the device, which is almost a year.

Any help would be appreciated.

Thank you.
[Nook HD, HD+ Android Development] antebr:
On nexus 4, CWM 6.0.4.3 and TWRP 2.6.3.3.
[Nook HD, HD+ Android Development] drmarble:
You could use the recovery you built with the 4.4 rom. But that can be a chicken or egg problem. For cm, you can apply the following patch to use an older recovery:

http://review.cyanogenmod.org/#/c/53559

You can probably make a similar change to your CarbonRom chain and get a flashable build.

Good luck with kitkat. I still can't get mine to boot. Not even a logcat or last_kmsg (I never get a last_kmsg anyway).
[Nook HD, HD+ Android Development] webdroidmt:
CWM 6.0.4.5 and TWRP 2.6.3.0 will work with KK on our device. I'm sending both of you a PM.

EDIT: drmarble, please forward the PM I sent you to jisoo. Thanks.

Mike T