yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 General] secretdeath2019:
WANT HELP

i got the same problem but now i cant find these flashing files. if you have all these files that helped you then please share it. i will very thankful to you .
[LG Optimus G (International)] Svennjamin:
Ok, so i was going to install the kdz for my OG so i restarted into recovery and erased everything of the phone so when i tried to restart into download mode nothing happened and still doesnt. So i managed to start phone in cwm touch (by going into fastboot vol up+power) but there is nothing there.

does anyone have an idea of how i can install a rom onto my device ?

is it possible to use sideload ? and if so how do i use it?

**EDIT**

I downloaded http://developer.android.com/sdk/index.html this file and when i turn my phone on into cwm touch and go to "install zip from sideload" then i start up my cmd.exe (C:\adt-bundle-windows-x86-20130729\sdk\platform-tools) in this folder and type "adb devices" i get no devicese connected.

I have my Lg usb drivers installed. why cant the cmd find my device ?
[LG Optimus G (International)] kimitza:
First of all,if you want to use kdz,you don't need to wipe everything before. Do a hard reset after.

Just google around adb sideload.

It's really strange you can enter cwm,but not download. Are you sure you pressed the correct buttons? For dl mode turn off the phone(make sure you did that),press vol up+vol down and while you do that,connect the phone to pc. Voila,magic happens and are in download mode.

Sent from LG E975 pwd by CM 10.2/smart phones,dumb people.
[LG Optimus G (International)] Svennjamin:
yes i pressed the right buttons. and i have been googling all night to find a way out and no matter what i do when i go into the adb cmd the cmd will tell me it cant find my device. :(

and it seem as the device wont charge when the phone is turned off....
[LG Optimus G (International)] Svennjamin:
pls anyone ?
[Nook HD, HD+ Android Development] jisoo:
What is Carbon?

Carbon Community on Google+: http://community.carbon-rom.com

Carbon ROM website: http://carbon-rom.com/

What is Carbon?

Carbon Features:

Android 4.3

Active Display

Halo

AOKP Ribbons

Option to hide lockscreen hints

Carousel lockscreen

Customizable lockscreen buttons and sliders

Customizable hardware and software keys

Transparent navbar and status bar

Customizable navbar ring

Navbar arrow keys

Navigation bar widgets

Customizable power menu

Notification power widget

Notification brightness adjustment

Customizable quicksettings panel

Statusbar mods including center clock and color

LCD Density

Theme engine

Full Rotation

More that haven't even been mentioned, and more to come!

Infographics on Carbon Rom: http://imgur.com/a/ovxNp
[Nook HD, HD+ Android Development] alk195:
Does this build have TRIM disabled so as not to cause the brick bug?
[Nook HD, HD+ Android Development] jisoo:
Yes. The device-specific files are pulled from CM10.2 github, so trim is currently disabled until they feel it's safe to enable it. If that happens, I will put a note in the op.
[Nook HD, HD+ Android Development] Escaperoute:
I'm actually exciting for this build. Good work man
[Nook HD, HD+ Android Development] moac2k:
thanks for good rom...

youtube not working...
[Nook HD, HD+ Android Development] jisoo:
Are you sure? It's working fine for me (latest YouTube from Play Store)

[Edit:] Tested a bit more. HD video does not work. SD and HQ work fine. I'll try to fix this in the next build.

I would appreciate any advice on what could be the potential reason.
[Nook HD, HD+ Android Development] moac2k:
Rom is so satisfying. Thank you.

But

In mxplayer hardware rendering does not work.

Probably the same reason is like playing the youtube.
[Nook HD, HD+ Android Development] JeauxAdam:
In the olden days disabling he overlays would sometimes fix it. I haven't flashed this yet so I can't test.
[Nook HD, HD+ Android Development] jisoo:
It appears that there is some minor issue with the TI-specific libraries, and this is causing hardware rendering of h264 video to fail. I'll see if I can't get this fixed by the next build.
[Nook HD, HD+ Android Development] adwait.bhandari:
Wow! Thank you for this awesome ROM. I feel this is much smoother than CM10.2.

Applications are flipped sideways in recent bar.

Hope I can soon take screenshots. Dont really care about the youtube HD playback as my internet sucks bad.

Again thank you! :)
[Nook HD, HD+ Android Development] jisoo:
Thanks. I've noticed the flipped recents view as well.

I'm away on holidays until next Friday, and will do the next build when I get back. I'll see if some of these bugs have been fixed in the source by then, and try to address the remaining ones individually.
[Nook HD, HD+ Android Development] allrockedout:
Screen shot isn't working also android system is killing the battery faster than screen
[Nook HD, HD+ Android Development] jisoo:
I'm looking into the screenshot issue.

Battery drain from android system is a known 4.3 bug with a variety of possible cause and fixes: https://code.google.com/p/android/issues/detail?id=58126. It is not a bug specific to this ROM, so there is no fix I implement at my end.
[Nook HD, HD+ Android Development] jisoo:
OK, this has now been fixed and new build (20130917) uploaded and added to OP.
[Nook HD, HD+ Android Development] adwait.bhandari:
When in landscape mode, the navigation bar becomes big, ugly and flipped. I could live with this but as the buttons are flipped I accidentally press the kill app button.
[Nook HD, HD+ Android Development] moac2k:
In this update, video problem solved.

Although there are still some problems for me this rom is the best.

Thank you.

Short English'm sorry .. ;
[Nook HD, HD+ Android Development] djmax:
I had this problem with CM10.1. I cured it by uninstalling a load of system apps. I'm not sure exactly which one was the culprit, but I think it may have been GoogleBackupTransport. The screen is now the major draw on the battery, and android system is way down in fourth place.
[Nook HD, HD+ Android Development] jisoo:
Thanks for the report. Carbon and Cyanogenmod handle rotation a bit differently, and this bug is probably caused by a conflict between the two implementations.

I'll have a look at fixing this over the weekend and expect the next build to be ready on Monday.

By the way, it looks like screenshot is working for you? I was assuming this issue was related to the other graphical glitches...
[Nook HD, HD+ Android Development] adwait.bhandari:
I actually used a screenshot app from the Play store. Taking screenshot from the android system so doesn't work
[Nook HD, HD+ Android Development] king200:
I am using the HD as well. The newest kernel does not work. The original, dated 0824 does. I don't know where it is on XDA at this time but https://www.dropbox.com/s/6dslm4d9fyqoamx/kernel-fstrim-hummingbird.zip. should get it for you.

If you read recent posts in VG CM 10.2 thread you'll see some terminal commands discussed.

In Settingns/Developer options, I have the animations set to 0.5x. That seems to make a difference to me. I do not use: Settings/Performance/CPU Governor, sometimes changing to ONDEMAND from the INTERACTIVE, but it has made differences (check the box to Set on Boot). Technically, I know little about these settings but they are a carryover for me from working with my HTC HD2 phone.
[Nook HD, HD+ Android Development] fma965:
OK Thanks :)
[Nook HD, HD+ Android Development] agantai:
you are absolutely right closing the case & opening it again fixes the issue. thanks very much :good:
[Nook HD, HD+ Android Development] Weirdy346:
Just for some info, but I was on CyanogenMod 10.2 Nightly 30/10 and tried a dirty false of this latest Carbon ROM and kernal which didn't work then tried again with a full factory wipe and it worked perfectly :) Much quicker overall and better download speeds to :)
[Nook HD, HD+ Android Development] dbh369:
Glad to help! That drove me crazy too...
[Nook HD, HD+ Android Development] tebra:
I had FC with browsers (FireFox et Feedly) and each time logcat show me some url that can't be reached before FC.

So, I remove AdAway and reboot. No more FC for now.

Sorry for my bad english
[Nook HD, HD+ Android Development] jisoo:
Final update, maybe

I finally managed to fix Bluetooth tether (yay...), and will upload the updated builds within the next 24 hours (tested on ovation, building hummingbird now). The update has only this one fix, so

if you don't need BT tethering, you don't need to update

.

I'm also too lazy to do multi-window builds, but if there is a user who wants both multi-window and bt tethering, send me a pm (or post here) and I will update those as well.

Development on the 4.3 branch of the Carbon ROM has more or less been frozen, and the Carbon Team is now busy reviewing the code changes for 4.4. From what I've read, the plan is for them to do a full rebase for 4.4, meaning they will start with the clean 4.4 AOSP codebase, and merge the Carbon features one-by-one.

At the same time, the Cyanogenmod team has also initiated development on 4.4 (CM-11), and is now updating device trees. It is, however, still unclear if it is possible to port 4.4 onto TI OMAP devices (including B&N Nooks, Amazon Kindles, and the Galaxy Nexus), though there are a lot of smart devs working on this.

If everything goes well, we should be able to attempt unofficial 4.4 builds sometime after a few weeks. If the CM team decides not to update our the trees for our devices, though, we may be permanently stuck in 4.3. Time will tell.
[Nook HD, HD+ Android Development] tebra:
Is it multi-window a stable feature? No FC?

If yes, i'm interested for a build :)

Thanks for your work on nook HD+

Envoyé depuis mon BN NookHD+ avec Tapatalk 4
[Nook HD, HD+ Android Development] vuo:
There's already some unofficial 4.4 releases out for the galaxy nexus so hopefully the TI OMAP chips won't pose a problem for us.
[Nook HD, HD+ Android Development] dbh369:
So this is curious, I don't use adaway, but I do have a long list of hosts that I load to wipe out most ads. Wonder if something is phoning home(or the nsa)...
[Nook HD, HD+ Android Development] jisoo:
Multi-window is mostly stable. It does not cause FCs, as far as I've seen, but it does take over the Halo floating window function and there are some graphical glitches in general.

There was an update on the code in the Carbon gerrit, so I need to update the mw patch and test before I can upload the mw builds.

[edit:] was looking at the wrong patch set. mw will be same as before. will upload the mw builds with bt tethering soon.

[edit2:] OK, updated mw builds are in the OP now.
[Nook HD, HD+ Android Development] tebra:
Thanks for the mw build. I will try it tonight :D
[Nook HD, HD+ Android Development] beyored:
im new to nook hd just had one delivered a few hours ago.....installed this rom about an hour afterwards an had no problems. great rom keep up the good work....:good:
[Nook HD, HD+ Android Development] tebra:
multi-windows is very nice feature for a 10 inches tablet.

Some graphical glitches but no FC.

Just need to rotate the nook to re-draw the window layout.
[Nook HD, HD+ Android Development] Software Guru:
Might give this a try later today
[Nook HD, HD+ Android Development] wifesabitch:
Does the "tablet ui" work with ROM? I tried and couldn't get passed the boot screen, had to restore a backup of the ROM.

Couldn't find much searching either thread. Hate the buttons where they are now.
[Nook HD, HD+ Android Development] jisoo:
Unfortunately, Tablet UI is not supported in Carbon anymore.
[Nook HD, HD+ Android Development] wifesabitch:
Oh well, I can get use to this layout.

Keep up the great work on this ROM. :good: Loving it.
[Nook HD, HD+ Android Development] 320flyboy320:
Anyone have any luck trying to change fonts with Carbonrom? I've tried an app called Myfonts and when I try to use it to change fonts it results in a boot loop and I have to re-flash the ROM to get it back...:confused:
[Nook HD, HD+ Android Development] beyored:
I use ROM toolbox to change fonts....

just hit thanks if I helped.....
[Nook HD, HD+ Android Development] ms2003:
i found when i am watching videos, the battery drop down quickly, almost 50% per hour, do you have similar issues?
[Nook HD, HD+ Android Development] Esotic:
Gesture/Swipe Typing in Carbon 4.3 Borked?

Hi,

When I attempt to swipe through the letters on the keyboard no words are inserted into the relevant text entry area. If I push the individual letters then it works fine. Anybody else noticing this? Is there a fix for it?

Aside from random glitches that seem to get corrected by a reboot this has been the most responsive ROM I've tried on my Nook HD+.

Thanks,

Dave\Esotic
[Nook HD, HD+ Android Development] jisoo:
I'm using Swype so I've never really tested the AOSP keyboard on Carbon. I checked the Carbon source of LatinIME.apk (default keyboard package), and the only difference with what CyanogenMod packages is in the autocorrection threshold...

I honestly do not know if this is the cause of your issues, but the easiest way to test is to pull the LatinIME.apk file from a CM nightly build (the last significant change was in August 24 so any nightly after that is fine), put that in your /system/apps and reboot.
[Nook HD, HD+ Android Development] adwait.bhandari:
This is because you have not flashed the full gapps package. Flash the gapps package again. You can flash either Slim_AIO_gapps.4.3.build.2 if you use the Dark Carbon toggle or gapps-jb-20130813-signed.zip if you dont use the dark toggle.
[Nook HD, HD+ Android Development] Esotic:
I'll try flashing the full gapps to see if that fixes the gesture typing. When I was using CM 10.1 I found the gesture typing to be pretty slow/laggy. I wasn't really sure what I was sacrificing by installing the slim gapps, but the potential for less bloat and quicker performance made it worth trying out.

Cheers,

Dave\Esotic
[Nook HD, HD+ Android Development] yahn77:
how to edit toggle menu?

I want screen rotation toggle.... how to edit toggle menu?

This Rom is very good !! Thank you!!:good::good:
[Nook HD, HD+ Android Development] didopicha:
ROM options

Carbon Fibers option in Settings stops working for me very soon after I install the ROM. It somewhat works in the beginning (the options inside are not always visible and I have to go back to Settings and click it again to see them) but probably after the first restart every time I try to open it gives me an error and closes, making the settings inside virtually inaccessible. It tried several versions of the ROM but it's the same thing. Does anyone else has that?
[Nook HD, HD+ Android Development] king200:
Settings>Carbon Fibers>Statusbar>QuickSettings(column after Battery, Clock, Notifications)>Static Tiles>Tiles and layout>+ORIENTATION

If you don't see the QuickSetting column, exit Carbon Fibers and try again. There is a setting in Quicksettings to show the same toggles in the notification area.
[Nook HD, HD+ Android Development] Foax:
HDMI

Thinking of getting the hdmi adaptor for HD+. Does it work with this ROM?
[Nook HD, HD+ Android Development] yahn77:
Thank you

Thank you for your kindness!!:good::good:
[Nook HD, HD+ Android Development] jisoo:
That should not happen. I just watched a 720p x.264-encoded movie and lost about 25% over 2 hours. Are you using HW decoding in your media player?

The invisible options is a common tablet bug in Carbon, but the FC error should not happen... It's probably an exception thrown by a conflicting or unexpected setting (which would be a bug, I admit). You can either try to get the logcat of the crash (which would hopefully let us know where the exception occurs) or clear data for the CarbonSettings app (which will reset your Carbon settings, unfortunately).

I honestly have no idea. If it works in CM-10.2, it should work here as well as I used the same kernel and video driver sources as CyanogenMod.
[Nook HD, HD+ Android Development] felacio:
I have the adapter and it does in fact work fine with this ROM.
[Nook HD, HD+ Android Development] smurfster:
I flashed the latest NookHD+ ROM and upon booting I'm receiving a error "carbon fibres has stopped working"

any ideas?.

I've wiped the entire storage, cache etc. and flashed several times.
[Nook HD, HD+ Android Development] king200:
Just ignore the message. Carbon Fibers works ok. The continuing problem is that you have to go back to the initial Carbon Fibers menu to see some of the sub menus.
[Nook HD, HD+ Android Development] ms2003:
you can see. when i watching vedio the battery drops almost directly. and at last, 1% battery can last a very long time. i am using the latest version on 6th
[Nook HD, HD+ Android Development] radium22:
Nice ROM! It is smooth and fast. Is there a way to disable dual panel for Settings? Thanks.
[Nook HD, HD+ Android Development] linhnt:
USB host (OTG)

This is my current rom and very happy with it.

Just wonder if it supports USB OTG?

Thanks
[Nook HD, HD+ Android Development] grukko:
I concur. Aside from a few wifi hiccups now and then this ROM is very fast and stable. Props to the dev!
[Nook HD, HD+ Android Development] jisoo:
USB OTG is enabled in the kernel, and I think it should work, but I've never personally tried it. Would be interesting to find out, though.
[Nook HD, HD+ Android Development] kmare:
1% battery is hw issue. It will happen in stock ROM. Go back to stock and rma
[Nook HD, HD+ Android Development] ms2003:
you means i flash back to stock rom and then? what is rrma??

my nook battery status is normal till i flashed this 6th latest rom.
[Nook HD, HD+ Android Development] gotbass:
how do you screenshot in this rom? without having to hold down the power button?

MC4 goes to pause menu when i do it so i dont get a proper screenshot =/

thanks
[Nook HD, HD+ Android Development] Lavrentsii:
Stick in in your quicksetting tiles?
[Nook HD, HD+ Android Development] king200:
Add the power button to the navigation arrows/home and then hold the power icon? Settings->Carbon Fibers->Navigation>+ add and then then save. That works for me.
[Nook HD, HD+ Android Development] Kubombelar:
does the kernel in this rom support undervolting? if not kindly advise on which does
[Nook HD, HD+ Android Development] jisoo:
Sorry, the kernel does not have specific support for undervolting (unless this is in the standard CM kernel).
[Nook HD, HD+ Android Development] jisoo:
Trim kernels

OK, here are flashable kernels for ovation and hummingbird with the trim function enabled. These include commit 50c7f9d622a3b57d24ce935f6117bf5b8a5fc5e1 which possibly prevents the eMMC brick bug from triggering.

Once you boot with a trim-enabled kernel,

trim function will run automatically in the background and cannot be disabled by the user

!

These are identical to the trim-enabled kernels verygreen has recently posted in the CM-10.2 thread, except they include the Carbon ramdisk so are usable on the last builds of this ROM (both BT-tether fix and the build before that as far as I can tell).

If you are not sure what this is, or want to understand the risks involved better, please read this thread first: TRIM: FAQ, Discussion, Risks.

I have been running the ovation kernel on my device for 72 hours now and the device has not yet been bricked (yay!). Performance is considerably better with very little lag between apps.

Here are the kernels:

USE AT YOUR OWN RISK!

trim-kernel-carbon-hummingbird-20131122.zip - 4.11 MB

trim-kernel-carbon-ovation-20131122.zip - 4.10 MB

I would recommend you backup your /boot partition before flashing this, in case the device does not boot or you want to go back to a trim-disabled kernel.
[Nook HD, HD+ Android Development] gotbass:
hi thanks for the reply, i tried that and it still pauses so i get a screenshot of the pause menu.

---------- Post added at 09:38 PM ---------- Previous post was at 09:34 PM ----------

how would i do that?

thanks for the reply
[Nook HD, HD+ Android Development] jamus28:
With trim enabled, cm10.2/carbonjb3 work great and are faster than old carbon/xperia

Carbon tends to perform a tad better than cm usually. but since 11/13 cm10.2 got a WiFi driver upgrade which has given me awesome speeds since. I would hold off until jisoo gets the opportunity to update.
[Nook HD, HD+ Android Development] Kubombelar:
Hi, so am guessing i backup the boot partition with titanium backup? backup includes the kernel with trim disabled or would a backup of the rom itself recommended?
[Nook HD, HD+ Android Development] jisoo:
It's better you back up the /boot partition using the recovery (CWM or TWRP).
[Nook HD, HD+ Android Development] jisoo:
Unfortunately, the Carbon Team is not pulling new patches to the JB3 branch anymore, so whatever Wi-Fi updates CM-10.2 has recently implemented are not getting pulled either.

In addition, the Wi-Fi issues were not in the drivers but mainly in the framework base and settings (they somehow broke how the TI Wi-Fi driver looks for new APs and how it maintains the connections). However, there could be additional changes to somewhere else in the source tree, and it's not a trivial task to identify and pull these into the Carbon tree.

So in short, I don't think I have enough free time to take on this task, as I am still hoping we will be able to move to 4.4/Kit Kat at some point.

Now, the wonderful news regarding this is that Hashcode has just released the first 4.4/CM-11.0 alpha builds for the Amazon Kindle Fire HD 8.9. This device has the same SoC (TI OMAP 4470) as ours, so there's renewed hope that we will be able to get 4.4 on our devices as well.

The device tree sources are not up yet (because it's very early stage), but I believe we have a good chance that CM will bring the Nooks to CM-11.0, and therefore it'll be possible to do unofficial ports for other ROMs -- including Carbon -- as well.
[Nook HD, HD+ Android Development] Kubombelar:
wow, there's definately hope we just have to wait. Talking about wi-fi drivers, am assuming this current carbon rom has no wifi bugs and that wifi speed is relatively good? Also i did not get the chance to ask earlier, is there any work around to enable undervolting in the kernel? Thanks
[Nook HD, HD+ Android Development] king200:
I did some testing this morning. WiFi is more reliable in Carbon(CR) vs CM 10.2(CM) in MY TEST. I don't know about undervolting.

I have 2 HD+. both with same chips. Unit 1(1) has been on CR since 10/29. At one point, there were WiFi problems but they were resolved. The Carbon Trim kernel was installed.

CM was installed on Unit 2(2). CM 11/26 was installed with v2 of Trim kernel after full wipe and format of /bootdata*. Rom was booted and the connect to WiFi was very fast. Booted to recovery, Gapps, booted to system and reboot to CWM. Advanced restore of /data of a previous, CM 10/29 backup.

Checked to be certain that the MAC addresses were different and that the assigned IP were in range of good performance in my wireless network. Router was rebooted. 1 and 2 next to each other about 12' from WiFi router.

In Speedtest, CR constantly completed the test with ~14,000D/500U. CM, when able to complete the test, had similar speeds. More frequently than not, the "Try Again" message came up when the UP part was running. The same test was run with Speakeasy.net/speedtest and the results were similar. The test completed consistently with CR and failed frequently with CM. Tests for different cities were done too.

Then CR was installed on 2 with trim and an advanced restore of /data from the CWM backup of 1. Again the MACaddress and WiFi IP were confirmed different. ! & 2 then had similar results with both Speedtest and Speakeasy.

I conclude that CR is more reliable than CM with WiFi. I actually have no issues with WiFi and CR.

* cloning 2 units with the same backup can cause the same MACaddress to be assigned. When that happens, and both units are connected to the same WiFi, the performance is erratic. The procedure of formatting /bootdata, booting to system, and then restore of only /data avoids this problem.

Why I have 2 HD+? That's a story for another post!