yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Fit GT 5670] yajnab:
I too spent a long to impliment SLUB. SQLB makes the device slow. Probably what I think we need to change the device specific files to #include<slub,h> as most of them are stuck at the slab.h and make according changes to get the support of slub.

---------- Post added at 04:51 PM ---------- Previous post was at 04:50 PM ----------

Believe me. It makes the device to lag. Boot time too increased.. We may have a different compression though
[Samsung Galaxy Fit GT 5670] alin.p:
Actually SLUB is a SLAB based allocator, and it still uses the main slab.h dependencies along with the additional ones in slub.h. I admit, I thought about this too, but turned out it's something else.
[Samsung Galaxy Fit GT 5670] yajnab:
DMESG can u provide me.. Wanna check it.. and the changes made..
[Samsung Galaxy Fit GT 5670] alin.p:
There is no way to collect kernel debug messages, the booting process doesn't get past the bootsplash and obviously ADB is not yet usable in this state.
[Samsung Galaxy Fit GT 5670] yajnab:
UART? Enable Early_printk=y in the defconfig and connect to UART
[Samsung Galaxy Fit GT 5670] alin.p:
I already said I can't connect to any other port than the default MicroUSB.

EDIT: [MENTION=4573740]yajnab[/MENTION]

Somehow I managed to pull the kmsg from /proc/ and found what the problem is. SLAB contains the malloc_sizes symbol, which is exported and used by the closed source FSR driver. SLUB is missing this symbol.

malloc_sizes represents the size for the kmalloc caches, which SLUB uses too, but only copying its define won't do sh*t for FSR. I inspected slub.c's code hoping I would find a similar symbol that I could rename to malloc_sizes, but SLUB doesn't define its kmalloc_cache sizes. I will look more on the code tomorrow, but I doubt there is any way that I could replicate that definition in SLUB.
[Samsung Galaxy Fit GT 5670] yajnab:
No need to waste the time on this then. If we do then we have to reprogram the algorithm on it. Better get an UART and join to get MTD working on 2.6 kernel. I can provide you stuff to get the UART working on 2.6 kernel
[Samsung Galaxy Fit GT 5670] alin.p:
Well Erik got the 3.0 kernel to boot until he can get the dmesg, so there is no absolute need for UART. All the debug info is already there.

I took a good look inside the msm_nand code and even diffed it with a working msm_nand from the original Android Kernel_MSM 3.9, and the differences are only trivial. The only noticeable difference was that our msm_nand contains additional functions for reading the DPRAM, which always needs more than one try to get loaded. But I don't think this would be the problem. The addressing code is pretty much the same, so no problems here either. It must be something with the write functions, but I didn't have much time to look at them. I'll take a better look tomorrow.

If we pull this out, then compiling 3.9 would finally be possible.
[Samsung Galaxy Fit GT 5670] yajnab:
We need the bootloader values for each partition allocation.
[Samsung Galaxy Fit GT 5670] Dark Passenger:
looking forward to what you diagnos as the problem.

so far yajnab made the most sense that it requires correct partition id's from the bootloader to correct the bad block allocation.

also wouldn't it be 3.10 not 3.9
[Samsung Galaxy Fit GT 5670] alin.p:
3.10 doesn't have MSM support yet. Of course it can be added, but it's easier to update a working 3.9 to 3.10 than to add the MSM dependencies yourself.

I'm kind of busy these days. I only had one hour to check the MTD code and Dmesg. It seems obvious what the problem is, but as always the solution is not that obvious at all.

First, the H/W controller ID for msm7x2xa is 0x307. By tracing the debug messages, one will see that the equality between our ID and 307 is false, making the IF statement go on the ELSE branch, without activating BCH ECC. Anyway, seems like the driver still recognizes a NAND device after this, but it is something to keep in mind when diagnosing the problem.

But the real problem(s) could be:

1. Too small OOB area allocated per page. I didn't check the values, but in these situations, this is a common problem for YAFFS

2. Bad chunk alignment because of wrong offsets. This is where those values hardcoded in the fsr.ko come in.

3. Probably just a coding error. This is improbable, but it would be stupid to neglect it.

I hope I will finish the work sooner, so I can put my whole mind on this. Anyway, everything seems promising at the moment, it is a big progress.
[Samsung Galaxy Fit GT 5670] yajnab:
Need the correct commandline to get the UART work.. Most probably this week. Then I can derive the offset values of the partitions. This is the thing what we want..

---------- Post added at 10:53 PM ---------- Previous post was at 10:53 PM ----------

I think we shouldnt dream much. First fix the 3.0.31 .. :)
[Samsung Galaxy Fit GT 5670] erikcas:
Hi Alin, it is not only the write functions, but also the read functions. If I cat a partition, it ends up with a lot of garbage.

Anyway, on mini S2 now, so my priority of msm7x27 are lowered. But as this has been a challenge for a while. So if you continue this work, I will be happy also to continue working on this.

And you are right. Getting this to work, will cut us loose from samsung as far as kernel development concerns
[Samsung Galaxy Fit GT 5670] erikcas:
this is not a problem. The partitions are passed correctly from atag. Order and sizes are correct. There is no reason to interfere with the partition table as you probably end up with and unrecoverable bricked device.

Maybe, in the future when the MTD driver works (maybe fairytales) it could make sense to alter partitiontable (increase size of system partition for example). But imo main concern is get the freaking driver to work.
[Samsung Galaxy Fit GT 5670] alin.p:
Yes, I was expecting this behavior on reading the data, but this can be caused by the misalignment between the MTD offsets, and the YAFFS OOB areas. The bad block marking function will mark all blocks as bad because it reads the good blocks in a wrong way, which is exactly what happens in our case. There is a little workaround we can use, but it is a little too hacky.

We could comment out the bad block marking function and stop the nand_write function from recalculating the ECC, and, hopefully, we might get correct writes. But this should be the last alternative and we should avoid it until we have no other choice than to hack the code.

I'll probably finish working on the kernel this week (the implementation of the auto-brightness feature is a pain in the ass), then I'll focus only on fixing the MTD. I'll PM you if I find any little hope for a solution. Brainstorming helps more than one tired mind.
[Samsung Galaxy Fit GT 5670] erikcas:
Fine with me :)

I earlier got read and write enabled by the way, with the original values for the OOB and no bad blocks. Problem was, that the partitions were only seen @ half sizes..

So I think, it might be related to changing 2112 to 4224 part in the patch. Maybe some other values / calculations need to be adjusted
[Samsung Galaxy Fit GT 5670] alin.p:
Good to hear you got such a big progress in this little time. :)

Yes, as you probably know already, Yaffs (and most of the filesystems) have their sizes linked together. For example, you can't increase the page size and neglect the OOB area/Pagesize/tag data ratio (which I will remember after a fast search on Google, but I think it was 28 bytes per KB if ECC is disabled).

I guess it's worth trying to increase the sizes based on the Yaffs size ratios. If we're lucky, we'll get the rest of the space back. Otherwise, we're in trouble. It means that the rest of the space is lost when writing the zero-ed blocks.
[Samsung Galaxy Fit GT 5670] Dark Passenger:
um dont know if you are or arnt comunicating with the androidarmv6 devs but might want to have a look at the newer posts here and here.

and that will be the last of me butting in:D
[Samsung Galaxy Fit GT 5670] alin.p:
Thanks for keeping me posted, I don't have much time to check all the news in the kernel section. I barely have time to respond on this forum.

Well, good to hear we have a success, but this implies that we should have high-speed(class) sd-cards to keep our system R/W speed as close as possible to the NAND speeds. From what I see, mounting the /system on sd is more of a safe-mode practice until we get fully working MTD, so nothing to worry about yet.

I'm really thankful for all the work done by Psyke, Erik, OuNao and whoever I don't remember right now. If they continue like this, they might finish 3.0 before I release my kernel :))
[Samsung Galaxy Fit GT 5670] Dark Passenger:
well all I can say is get your kernel finished already so you can (maybe?) move on to MTD.
[Samsung Galaxy Fit GT 5670] galfit:
links are offline :crying:
[Nook HD, HD+ Android Development] killersloth:
Disclaimers

-I am in NO WAY affiliated with Team Carbon-

-These builds are unofficial, and not endorsed or supported by Team Carbon-

These builds are tested by me, however, flash at your own risk, I am not responsible for:

-Bricked devices-

-Loss of data-

-Unforeseen complications-

-Intentional or unintentional misuse of controlled substances-

-Cold Coffee-

Installation Instructions

-Factory reset-

-Flash ROM-

-Flash preferred GAPPS-

-Reboot-

Downloads [DevHost]

Nook HD

Nook HD+

GAPPS

Thanks

verygreen - device trees

bokbokan - infos

Team Carbon - for the great work they put in on CarbonROM

webdroidmt, drakester09, pins2u, mehdi, and all others who helped me test the HD+ version before I got one :)​

CarbonRom is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.

Please feel free to look at, build, and use our code on CarbonDev GitHub.

We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained and can be viewed on our repository.

Special thanks also go to Slim Rom for some of their features, PA, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know.

Screenshots:

Features

Here are just a few of our features:

Android 4.2.2

PIE

Halo

AOKP Ribbons

Comprehensive speed enhancements, including Linaro -O3 and processor-specific optimizations

Option to hide lockscreen hints

Carousel lockscreen

Customizable lockscreen buttons and sliders

Chronus clock widget

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

Quiet hours

Volume rocker music controls

Full Rotation

Customizable battery and notification light

Long press "kill all" button in recent apps to clear cached apps

RAM Circle

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

Who is Team Carbon?

andros11

BigShotRob

dg4prez

Kejar31

mattmanwrx

morfic

nocoast

pixeldotz

slick_rick

winner00

​

Feedback is appreciated, let me know if you run into any bugs and I'll do my best to fix them.

Enjoy :)
[Nook HD, HD+ Android Development] killersloth:
Changelog

7/23---

[B11]*fixed carbon wallpapers
*customize home button wake options
*moar swag

[B10]*so many changes from carbon merged -- support for exfat, new app, lots of various fixes, just check their github ;)
*merged fixes from verygreen for dalvik heap size and memory leaks, he's a boss
*broke carbon wallpapers and VoicePlus, fix coming in the morning along with customizable home button wake options

///

7/15---
*merge upstream changes from CarbonDev
*revert rendering tweaks

///

7/10---
*merge upstream changes from CarbonDev and verygreen
*add rendering tweaks by Jeeco to ovation

///

7/7---
*revert to stock Launcher2 as included default
*merge upstream changes from CarbonDev

///

7/5---
*updated sgx drivers to latest from verygreen
*revert hummingbird to stock IVA freq

///

7/4---
*Merge changes from CarbonDev
*add sakuractive governor
*add wheatley governor
*set sakuractive as default governor
*enable 1.5ghz freq on hummingbird
*oc IVA to 500mhz on hummingbird
///

7/3---
*Merge changes from CarbonDev and verygreen
*add sio scheduler
*sio as default scheduler

///

7/1---
*Merge upstream changes from CarbonDev and verygreen
*include USB host switch app by verygreen

//

6/28---
*Merge upstream changes from CarbonDev
*media libs now compiled with -O3 strict aliasing
*include nova launcher
*new gapps package with some updated Google apps

//

6/25---
*initial release
[Nook HD, HD+ Android Development] killersloth:
Also reserved.

Just in case ;)
[Nook HD, HD+ Android Development] JeauxAdam:
Nice! Glad I picked this up on sale. Also glad because now, hopefully, more developing will occur.
[Nook HD, HD+ Android Development] killersloth:
When I was in the store, before I called my lady to see if she wanted it, I checked xda to see if there was active development ;)

Once I learn more about this device, I may go ahead and build for it's bigger brother (HD+) as well. Maybe not Carbon, this was sort of a spontaneous decision.
[Nook HD, HD+ Android Development] JeauxAdam:
This shows I should pay more attention to what I'm reading. I have the HD+. That could have been embarrassing. :)
[Nook HD, HD+ Android Development] killersloth:
I work 6 days a week, but any free time I can spend in front of the computer will be spent cleaning this up and working on HD+ support.

Perhaps I'll be able to start a build before work but don't get your hopes up :)

Started a build for ovation, I get home around midnight EST it should be successful (crossing fingers) and done by then hopefully, my laptop is on the verge of combustion lol. Sprint cell service is very unreliable here so it may or may not get uploaded until the morning :)

It won't be a new thread, just a combined thread.

Build almost finished before I had to leave, one small insignificant error while it was trying to make the otapackage... It'll be up by the morning.

Sent from my Galaxy Nexus to all you wonder nobodies!
[Nook HD, HD+ Android Development] mehdi_s82:
Superb rom

Just installed the rom on my Nook HD. I was on emmc CM10.1 and this rom is significantly faster! Thanks Team Carbon!
[Nook HD, HD+ Android Development] killersloth:
Ovation build is up, I don't have a HD+ so it needs to be tested. It 'should' work though, let me know ;)

They do quality work, I am very impressed by how smooth it is running as well :good:
[Nook HD, HD+ Android Development] webdroidmt:
This is great! Carbon is my favorite rom, as I also have it on my N7. I have an HD+ and I was able to port Carbon a couple of weeks ago. However, I ran into an issue with Settings/Storage force closing and MTP not being recognized by my PC for file transfer.

I've been working on these issues for the last week and finally got it working by decompiling framework-res and editing storage_list.xml. This was enough to get everything working great but it also resulted in a weird graphical glitch in Settings/Storage. Something else was missing and as yet, I couldn't figure it out.

When I saw your release for the HD, I figured your framework would hopefully be the last piece of the puzzle to clear up the glitch and it was. So, I just now replaced my framework folder with the one from your HD rom and all is good. :)

As expected, the rom is running great and I look forward to your HD+ release.

Thanks,

Mike T

---------- Post added at 12:24 AM ---------- Previous post was at 12:23 AM ----------

Yeah, Carbon runs really well. They give you some useful extras without a lot of bloat.

Mike T
[Nook HD, HD+ Android Development] webdroidmt:
EDIT: Somehow, my post got duplicated???
[Nook HD, HD+ Android Development] killersloth:
Make a CWM backup and give it a shot! Worst case scenario you have to restore, but I doubt it, should work just fine ;)

I need to know it works so I can know if I'll be able to get some sleep tonight lol
[Nook HD, HD+ Android Development] pins2u:
I'm installing it now on my ovation. I will report back soon. :)

----- UPDATE

Oops.. installation failed. I think there might be a few wrong permission scripts.

It says the following message.

set_perm: some changes failed.

E: error in /emmc/0/CARBON-JB-UNOFFICIAL-20130624-1358-ovation.zip

(Status 7)

Installation aborted.
[Nook HD, HD+ Android Development] killersloth:
Problem solved, upload will be done in two minutes ;)

Thank you brave sir, the ROM will be worth your trouble!
[Nook HD, HD+ Android Development] webdroidmt:
I don't generally make me too posts but same error as pins2u.

Mike T
[Nook HD, HD+ Android Development] drakester09:
Can you upload the fixed updater-script please? I can test it.

Thanks.
[Nook HD, HD+ Android Development] killersloth:
Here you go guys, and thank you very much :)

*pulled* updater-script cant be attached without a file extension, thanks xda :p it's at that link there
[Nook HD, HD+ Android Development] pins2u:
thanks! will report back again. :)

--- UPDATE

Installation failed and the same error message was displayed. T.T
[Nook HD, HD+ Android Development] killersloth:
Weird... Wish I could test this myself :(

I'll grab the updater-script from HD version and upload it, will post link in just a moment

Here you go: http://d-h.st/z3a

And thanks again!
[Nook HD, HD+ Android Development] srgibbs99:
Here is the thread where fattire introduced CyanoBoot for the Nook Tablet. Certainly doesn't apply directly to our device, but probably something to gleen from there :)

http://xdaforums.com/showthread.php?t=1522226
[Nook HD, HD+ Android Development] killersloth:
Thanks for the info guys, I'll read up tonight when I get off work.

XDA is full of developers with that elitist attitude, I don't need to add to their numbers :)
[Nook HD, HD+ Android Development] webdroidmt:
Hope you understand we're just trying to help, not cramp your style. LOL Since you're part of the dev community, I'm sure you know more about what goes on behind the scenes and in the IRC channels.

The main reason I suggested fattire is that I know he's been very prominent with the Nooks, starting with the Nook Color. And of course, Cyanoboot is his baby and it's become an integral part of Nook devices.

For about 3 years, between lurking and finally joining XDA, I've seen fattire help devs and many would-be-devs build CM for the Nook Color, Nook Tablet and the N7, as well as help them with Cyanoboot.

Anyway you're the man, just do your thing! :) What you've given us so far has been awesome.

Btw, looks like some decent changes in Carbon from 6/28-6/30 https://docs.google.com/document/d/1Zcp6iVWVw_7iH-ErnKgkYy3r5QuqV8PHFoQMb8hoBwQ/edit?pli=1 The one from 6/29 about performance looks interesting, wonder what they actually did?

Mike T
[Nook HD, HD+ Android Development] killersloth:
I definitely understand and really appreciate you guys helping me learn more about these two devices :)

Every bit of info helps me release a better product in the end.

Their change log since my last sync looks nice.

I have to flash a different ROM on my phone to get data tethering working lol.

I don't build for gnex, nexus device forums are full of custom ROMs already, it's very easy with support from Google ;)
[Nook HD, HD+ Android Development] 123421342:
Just flashed the rom, loving it a lot! Two things: is there a way to disable navigation bar on the bottom and also make pie controls bigger? Even at gigantic they are too small relative to the DPI.
[Nook HD, HD+ Android Development] Stevethegreat:
Yeah I'm an avid pie user too and I would like this extra bit of customization as well as the ability to add/remove all different kinds of buttons from pie (personally I never use "home" on tablets, others don't use "recents", etc). Thanks for the ROM though, till now it works very well...
[Nook HD, HD+ Android Development] killersloth:
Expanded desktop should remove the navbar, you might have to set it to "show status bar" to keep the notification bar from disappearing too, I'll look at that later. As far as button size I think that's as large as they will get.

Made a bunch of changes to my local repository, synced all up with carbon and verygreen. Included the USB host app and nova launcher in build packages and removed goomanager(they've been extremely slow and unreliable lately, so I don't use them anymore anyways).

Hopefully got the kernel situation fixed.

Building for hummingbird first to test, but its 3am so I might not get to testing tonight lol.

If all goes well I'll see what I can do about adding to the kernel, If I do though you probably won't get it until I can push sources to github. Don't want to violate GPL and get my thread pulled from xda :p

Did a lot of reading tonight, pulled in a lot of knowledge, thank you all for the input!
[Nook HD, HD+ Android Development] DriemMastR:
Mike T...

That'll work. Much thanks!
[Nook HD, HD+ Android Development] KCKitsune:
Question: Can we use verygreen's USB host mode apk to force host mode on this ROM? I use that apk allow me to hook up a keyboard and mouse to type.
[Nook HD, HD+ Android Development] bpaulien:
I just flashed this rom last night, over the CM10.1 to see what it was like. I started playing with the configuration settings for carbon and quickly got lost, but I'll give it another try later when I have more time. Seems pretty smooth until I tried checking my email. I guess I should mention that I didn't install the carbon version of gapps when I flashed the ROM.

Anyway, I flashed that and when I booted back up the Nook was lagging something fierce. I took probably 15 minutes to just complete the gapps setup (logging in, selecting language, seeing permissions and preferences, etc.) all the while getting messages like "Gmail has stopped running", "Google+ has stopped running " etc.

I decided to call it a night and put the tablet down. This morning I just picked it up and it seems to be working just as smooth as possible. No force closes or apps not running. Anyway, thanks for bringing a new rom to the Nook. I'm looking forward to playing with it.

And to the person who mentioned that XBMC wasn't working on it... Give it another shot. I watched a tv show on it last night with no problem. (using the build right after b2,whatever that one was called)
[Nook HD, HD+ Android Development] 123421342:
You don't have to post the source immediately the GPL does not state a time limit but it has to be reasonable. I doubt you will have any problems since you clearly have the intention to release it :)
[Nook HD, HD+ Android Development] jpisini:
Little bit off topic this thread got me to flash carbon on my phone for first time. Very impressed with it. Battery is about half again as good as what I got with CM10 on this phone.
[Nook HD, HD+ Android Development] webdroidmt:
Yes, and if you look just 2 posts above yours, you'll see that killersloth has included it in his next build.

Mike T
[Nook HD, HD+ Android Development] 123421342:
You said your battery lasts less on this ROM?
[Nook HD, HD+ Android Development] jpisini:
Badly worded sorry, I actually get 1.5x the battery on my Nexus phone with Carbon. I plan on installing this on my HD+ but I haven't done so yet. I am still reading. I need to figure out out to permanently install CWM first. Anyone have easy directions for CWM?

Thanks for everyone's help so far.
[Nook HD, HD+ Android Development] 123421342:
Look arty the cm emmc ROM for the HD not plus there a link to a good guide and I recommend twrp because cwm is primitive