yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] leapinlar:
Not yet.
[Nook Color Android Development] Milltac:
first off I just want to thank everyone who built this rom. holy **** it is amazing that the nook color has CM10. I installed it over the stable CM7.2 yesterday using the 12/5 nightly and it is working without error.
[Nook Color Android Development] cybertimber2007:
You installed it over CM 7.2? You really shouldn't for about two dozen reasons... backup your data, then wipe and flash just CM10 before you start to have problems.
[Nook Color Android Development] meteorrock:
<legofraggle> I will go ahead and pull that USB hosting code off of your repo and look through it on this diff I got for syntax errors though my git gui. I will try to juggle around the code a bit as this diff I got highlights errors and splits up the code on its GUI. When I am done I will just upload that script here.

Could not get up to IRC, just too social and scary ATM for me. Give me a few days and I will reload that code back up in this thread. This should be interesting. I don't have any way of testing this, I got a build on my computer called "cygwin" I used to build CM 10, but I do not have any USB hosting device for testing. I am not sure if this is the right way to do it........:)

I see you dont have any zip file for a straight downloading through your git. I will try to pull those files though my git here. Does anyone have the PATH for that .ko? If not I will go fishing for it. Is the commit for it the"attempt to add usb host?" That is what I am going to pull.

Have fun guys.

I had to close my PM guys, too much hate-mail. I dont get that from people, why do some want to criticize and hold back development for me? Apple fanbois? For that one guy wanted git help I will try to get back to him and let me PM me.
[Nook Color Android Development] perakesson:
reverting to CM7.2

Dear Nookers,

After a month with CM10 I give up for now. I tried several installations with various nightlies. No matter what settings, spending overnight on the charger will ALWAYS result in SOD, even at 800 MHz. But overnight, not on charger, usually survived without SOD. I had wifi policy set to "never".

Also it was always very laggy, even after V6 Supercharger. Perhaps I made a mistake. Perhaps my Nook happens to have a hardware issue.

Specifications for my NC, which I already reported in the survey:

sn QI13M92BEP4

03/16/2011

command dmesg does NOT return OMAP version, only "Device omap-dsp failed to suspend"

Now I use good old CM7.2 MiRaGe again, and everything is smooth and stable, even at 800 MHz and no V6.

Only issue with CM7.2 is wifi not always reconnecting until I turn it on and off.

Thanks for excellent efforts developing CM10! Good luck to all, perhaps I try CM10 or CM10.1 later on. I have no plans to buy a Nexus.

I use the tablet mainly as web client, ebook reader, notebook and simple games, so performance is enough.

Apologize from diverting from topic:

I work with software development in Sweden. I consider Android the best OS for tablets for now. I love Android, having used Palm handhelds for 10 years. But in the near future, I think the present Android and iOS on iPad are very outdated. The functions of a tablet and a notepad are merging. Soon lots of portable computers will have touchscreens, so in future hi-res tablets I want:

to be able to run all my usual Win/Mac applications, e.g. Adobe InDesign

split screen /multiple windows OS

a good file manager built in, similar to Win/Mac

Unless Google and Apple radically change the tablet OSs, and Apple modifies OS X for touchscreen MacBooks, Microsoft may be the winner, merging notepad OS with tablet OS.

Again I aplologize for diverting from topic. If anybody wants to discuss this further, I suggest we continue as a new thread under "Nook Color General"

:)
[Nook Color Android Development] rkleinhenz:
ADW launcher EX

I'm on the 12/5 nightly. I like ADW launcher EX. Whenever I reboot I am asked which launcher to use. There's the choice of ADW and Trechuchet. There's a secondary selection 'always' or 'just once'. Even if I choose 'always' I get asked the next time. Is this a bug or am I missing something? Is there an additional setting somewhere I can force this choice? I've looked through settings and could not find one
[Nook Color Android Development] hwong96:
It is a bug in ADW not locking in your choice. There is a setting in 'settings' 'apps' 'all' in system apps that allow you to disable the app. Trebuchet is a system app.

Edit: The disable tab is greyed out, so your option is to back up and remove it.
[Nook Color Android Development] leapinlar:
I contacted the author and he said it is a bug in the way play store in jellybean installs the app. He said to copy the apk somewhere, uninstall the app. And reinstall using your launcher. It fixed it for me.

Sent from my Nook HD+ Running CM10
[Nook Color Android Development] rkleinhenz:
Thanks for checking this out! Where in the file system would I find the apk? I searched for adw*.apk with root explorer and didn't find it. This is a purchased app, I would not expect to find it on the web, Or do I need to use titanium backup?
[Nook Color Android Development] lekofraggle:
Meteorrock,

It is too bad people are being too curt and spamming you to boot. Thanks for the support.

I have not posted zips because they do not work yet. I have a few builds, but they crash once OTG is enabled.

As for the commits...

The most recent commits on the usb_host branch are where we hit our road block. The nook freezes (and in one of last two commits I lost wifi).

As for the path, my git has the entire kernel. If you follow the path you will find the changed files. I do not have my computer and cannot remember where the kernel lies, but I think it is the root of your android build directory. I think this discussion is off topic for this thread though. So, perhaps we should move it to the usb host thread.

~Leko

P.S. I will hit up irc, but I may not have time for the next few days.

Sent from my NookColor using Xparent Cyan Tapatalk 2
[Nook Color Android Development] leapinlar:
It should be under /data/apps. The name is org.adwfreak.launcher-2.apk.

When I first installed mine on play store, it said it was copy protected. I'm not really sure now how I got it. I think I backed it up and got it there. If you can't get it, PM me and I can send you a temporary link to mine.

Sent from my Nook HD+ Running CM10
[Nook Color Android Development] rkleinhenz:
I find org.adwfreak.launcher-1.asec in /data/app-asec. Don't know what an asec is - I know the 'sec' part refers to secure? But I don't know if I can simply safe that offline and reinstall from it - somehow I doubt it
[Nook Color Android Development] leapinlar:
I think that is the same problem I had. That means it is copy protected. I think that is what the author was talking about by saying how play store in jellybean installs. I have an app called SystemPanel that lets me back up. I think that is how I got it. But try Titanium Backup to see if that does lit.

Sent from my Nook HD+ Running CM10
[Nook Color Android Development] rkleinhenz:
YUP!!! I backed up with titanium backup, uninstalled app, then restored from backup - and now it works as intended. And I also see the apk in data/app! Thanks for he help - I had also contacted adw.support but not got an answer yet,
[Nook Color Android Development] leapinlar:
Did that bug where all CM10 installs get the same MAC address ever get fixed? I have on Color running the latest CM10 and one running PA 2.99 (built from CM10) and they both have the same MAC address and are given the same IP address by my router.

Sent from my Nook HD+ Running CM10
[Nook Color Android Development] Mr-Glass:
I did not know about that bug - just checked the Cisco here, and the two NC CM10 that have been on today have unique MAC's
[Nook Color Android Development] leapinlar:
I think I know what happened. I had a nandroid backup of my older device and when I got the newer device I restored the old device's nandroid to it so I would not have to reinstall everything. It must have a saved setting in /data that used the old MAC address instead of the real one that is stored in my devconf folder in /rom. Now I just need to figure out how to tell CM10 what my real MAC address is.

So the bug was fixed, it's just my problem.

Edit: I fixed it. There is a file in /data/misc/wifi named wl1271-nvs.bin that needed to be hex edited. Got the instructions here on XDA in the Kindle Fire forum. I guess they had a lot of MAC address problems early on with CM7. All working now.

Sent from my Nook HD+ Running CM10
[Nook Color Android Development] meteorrock:
Ok, I am pulling through that android_kernel_bn_encore code on my end. Here is the link for that, if anyone is interested. https://github.com/lekofraggle/andr...e9803844ff38820233aa9ee8afe6cfeb747006#diff-2

That upload from the git is crazy slow. I will take a look through that code on this diff I have and look through it for syntax errors.

Interested in learning? Check my thread here. http://forum.cyanogenmod.org/topic/50994-follow-along-with-me-trying-to-learn-how-to-code/

~~~~~~~~~~~~~~~~~~~~~~~~~~

Update: <Legofraggle> you got two lines conflicting in my diff here on my end. Here is the lines between the "\android_kernel_bn_encore\arch\arm\configs\encore_defconfig" and the" \android_kernel_bn_encore\drivers\usb\musb\omap2430.c" and "\android_kernel_bn_encore\drivers\usb\otg\twl4030-usb.c"

One of those lines below should go, on mine the top line "--- a/drivers/usb/musb/omap2430.c" is highlighted red, through those file hierarchy folders I listed above. You should delete one of those lines throughout that file hierarchy and do a makefile for it into a .ko. Or I can take a look into doing it for you here in a few days. Never made a .ko before so that would be interesting. But I don't want to bump someone out of their work. Got in trouble for that last time. SO..............will wait for permission for a go ahead or go play on cyanogenmod.

~~~~~~~~~~~~~~~~~~~~~

diff --git a/drivers/usb/musb/omap2430.c b/drivers/usb/musb/omap2430.c

index 25a7218..78bf18e 100644

--- a/drivers/usb/musb/omap2430.c <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< one of these lines must go without looking further

+++ b/drivers/usb/musb/omap2430.c <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< through the code I am not sure which.

@@ -60,8 +60,10 @@ static void musb_do_idle(unsigned long _musb)

also the lines on 45 and 46	< u8 devctl = musb_readb(musb->mregs, MUSB_DEVCTL); > in the "\android_kernel_bn_encore\drivers\usb\musb\omap2430.c " is marked red. Line 34 < else if (twl->chgd_capable) > is marked red also. Line 46 < if (linkstat == USB_EVENT_ID) { > is marked red. Same through the " \android_kernel_bn_encore\drivers\usb\musb\omap2430.c"

~~~~~~~~~~~~~~~~~~~

In the "\android_kernel_bn_encore\arch\arm\configs\encore_defconfig" the line 40 < CONFIG_MODVERSIONS=y > and the Line 41 < CONFIG_MODULE_SRCVERSION_ALL=y > and line 14 < CONFIG_CGROUP_DEBUG=y > Line 22 < CONFIG_CGROUP_CPUACCT=y > Line 17 < CONFIG_CGROUP_DEBUG=y > but that next line is for a < # CONFIG_CGROUP_DEBUG is not set >

There are other lines marked red in this same file, but they are passive lines for, like the joystick not set, gameport not set, mouse not set, ect. Do not know if those should be deleted, as that might come into play with the USB host controller up and going. Might want to keep those lines in for breakpoints.

Line 189 and 190 in this same file are conflicting, not too sure on these lines. < CONFIG_DEBUG_KERNEL=y >

< CONFIG_DEBUG_KERNEL=y# CONFIG_DEBUG_KERNEL is not set > probably breakpoint lines for your debugger?

Hope that helps you. :)
[Nook Color Android Development] ChrisDDD:
I'd like to second this. I use CIFS manager to access network shares on most of my Android devices. I can still do it without CIFS support by using a few specific file explorers, but it's much more seamless when I can just mount the shares to the device.

Otherwise, this is running absolutely perfectly.
[Nook Color Android Development] arkas79:
Yes, it's really useful for a lot of functionality. I have asked some times myself but haven't received any answer. Of course I realize noone "has" to answer this question, and I am grateful to all devs on working on our device. I am not too familiar with kernel and ROM compiling and I am just curious what could be the reasons we don't have CIFS support. Is it technically difficult because of lack of drivers or something else or does simply has someone to download the kernel source and compile it with CIFS support or compile a separate module?

Thanks
[Nook Color Android Development] Whompy:
Keyodi submitted a patch for CIFS support I believe. It has not been merged yet though.
[Nook Color Android Development] lekofraggle:
Thank you for checking this out. I will make those changes as I get time. It will be a crazy weekend though.

I am building whole kernel updates and not *.ko. I do not mind if you build one though.

I will let you know the results when I get the changes finished.

~Leko

Sent from my ADR6425LVW using Xparent Cyan Tapatalk 2
[Nook Color Android Development] meteorrock:
I will help you. :) I will clean up that diff for you and push the change for you. Let me try to tinker with that USB host kernel module over the week here and I will push that finished .ko for you on my git. If I can I will try to fork it into <fattires> repo.
[Nook Color Android Development] eyeballer:
It's merged now, will be in the next nightly.
[Nook Color Android Development] eyeballer:
steven676 and keyodi have been working some more kernel magic and we need some testers who have been getting SODs with the nightlies.

Here's a build to try - flash right over your current nightly and report back on whether you get SODs with and without OC.

http://techerrata.com/file/eyeballer/cm-10-encore-20121208-2306-unofficial.zip

PS: CIFS is also built into this (for those that want to try it)
[Nook Color Android Development] steven676:
Other things which you may or may not notice in this kernel:

Improved interactive performance, particularly with GPU-heavy tasks

Lower power consumption in sleep
[Nook Color Android Development] RandomPooka:
I'll download and flash it on my son's NC right away. Just dirty flash the updated rom and gapps over his original 12/08 rom?
[Nook Color Android Development] bigrat:
Do you have recommended settings for I/O, memory, zRam, etc i.e. how would you like this to be tested?
[Nook Color Android Development] MechaGen:
WOW!

It's too early to give you any feedback on the SOD's, but it has a very noticeable bump in UI speed. (this has been my only complaint with CM10 since the first alpha)

Nook Color system info

Motherboard serial number: QIOCM9DMV3X

Manufacture date: 12/23/2010

CPU revision: OMAP3630 ES1.1

Touchscreen type: cyttsp

Rom: emmc cm-10-encore-20121208-2306-unofficial

Phone UI, LCD Density=240

Nova Prime, Dolphin w/Jet Pack

SD Card= ADATA 16gb C6

CPU Frequencies 300-1100 MHz

CPU Governor INTERACTIVE, (tried them all)

I/O scheduler noop, (tried them all)

Memory Management, zRam disabled
[Nook Color Android Development] steven676:
For purposes of verifying whether this fixes crash bugs and SOD, we're interested in default settings only. Specifically, that means:

Maximum CPU clock speed at 1000 MHz or lower.

I/O scheduler: BFQ or CFQ. Unless a particular scheduler is outright buggy, it should have no bearing on SOD, but we like to eliminate variables, and those two schedulers are by far the most well-tested.

zRam and KSM both disabled. Again, should not really affect these problems, but it keeps the number of variables down.

Now, if you have problems which occur only when you move off the default settings, bug reports are appreciated, but you need to test with the default settings first to rule out other causes. Bug reports from systems not running the default settings will be ignored unless you tell us whether or not they happen when you run with default settings! Also, crash bugs caused by the optional knobs and switches have lower priority than bugs affecting the system in its default configuration, for obvious reasons -- don't expect prompt support.
[Nook Color Android Development] dombeef:
I am installing it as I'm writing this, but I have noticed since the betas that when my nook is asleep, the screen flashes every few seconds. Could you disable that for better battery use, or is that there for some purpose?

Once again, great job on all of this,I am still surprised that the old nook has gotten CM10, nonetheless even nightlies. Now too bad there aren't as many developers developing for the Nook Touch...
[Nook Color Android Development] steven676:
That's a bug. Check your dmesg -- do you have messages of the form "Powerdomain (core_pwrdm) didn't enter target state 0"?
[Nook Color Android Development] dombeef:
Ok, I will check.

And no, I get 7 lines throughout the code that says "<6>Successfully put all powerdomains to target state", but thats in the new rom, it may be fixed in this version. Also what ever you did in this build, it makes my nook run generally amazingly, I have need for speed most wanted, and on the old nightlies it would run ok, some lag here and there. On this build there is no lag what so ever. What did you change, if I may ask?

I just checked my Nook after being asleep for a few minutes, and no flashing light, so that is fixed for my nook, at least.
[Nook Color Android Development] webyrd:
Have had no SOD's using interactive governor at 800, 1000 or 1100. On previous nightlies I had constant SOD's but only when using interactive governor and occasional SOD using KSM. See my post #1230 this thread. Plan to leave on interactive @ 1100 overnight, will try KSM tomorrow. Thanks for all the good work.:good:

Edit - no SOD overnight - THANKS
[Nook Color Android Development] pastordl:
Wow

Wow haven't had any SOD issues before but tried it since some noted improved ui. Everything is better and faster. Wifi connectstwo to three seconds faster. Dolphin beta up and ready three to six seconds faster. Goolge play two yo four seconds faster. All transitions faster. Used your recommended settings no problems. Ran with all the previously recommended speed up settings ut flies. Thanks for a great update. If have been running the latest Nightlies. Seen little improvements but, this "unofficial" is fantastic.

Thanks for all your hard work. Nook Color devs rock. May the Nook Color run forever.
[Nook Color Android Development] mrapollinax:
I'm running the unofficial nightly now and as others have reported I'm seeing an increase in performance and responsiveness. I do have a question about how Cyandelta will work with this though. Will it overwrite the kernel?
[Nook Color Android Development] bigrat:
Don't mean to rain on the parade - I don't notice an increase in performance, really. It may be the default scheduler and memory settings, since the NC was more responsive for me with noop, zram, and samepage enabled. The slightly lower clock setting doesn't seem to make much difference.

Wiped cache/dalvik, installed, fixed perms, and back to default settings.

No SOD, though.

v1.2 CPU

cyttsp
[Nook Color Android Development] leapinlar:
Yes it will. It flashes a complete ROM including kernel. That is why I did not flash this morning.

Sent from my Nook HD+ Running CM10
[Nook Color Android Development] meteorrock:
<legofraggle> I pushed that cleaned up USB host file through on the git. Its in the ^^HEAD of the kernel tree, I hope that is ok. I don't have the finesse of these other developers but its up.

I will start trying to work on that .ko for you. I might need a few days though on that, as this will be my first go on developing a kernel. I will try to test it first then push it into the git for you.
[Nook Color Android Development] eyeballer:
legofraggle and meteorrock,

Thanks for your contributions and glad to see you're making some progress, however can I politely request you move your USB host discussion over to the CM10 development thread instead of in this rom thread? It'll just help to keep things more organized in here with bug reports/test roms we put out. Thanks again! :)

http://xdaforums.com/showthread.php?t=1370873
[Nook Color Android Development] ibilln:
New experimental zip does seem snappier. I have default settings as described above. Also, moving from one app to another is better. Before it was like the NC ran out of memory btw apps. I had messed with the memory settings to no avail. Now, with stock settings, all seems good. No SOD after about 5 min! :)
[Nook Color Android Development] arkas79:
First of all thank you for the CIFS support. It is working perfectly. No reason for me to return to CM7 anymore.

Performance for me seems a little worse than cm-10-20121203-NIGHTLY-encore, I had before, but can't say for sure. It's just a feeling.

I had no SODs lately, so can't say anything about that.

Keep up the good work. Thank you.
[Nook Color Android Development] macrossmerrell:
Did you try rebooting into recovery and fix permissions? Possibly reflash the ROM as well.

Merrell
[Nook Color Android Development] christiankk:
I just did a fresh install of a 1208 nightly and I have the "black page" issue when reading magazines.

I've skimmed this thread but I've been unable to find a solution.

Is there a fix for this issue?

Thanks!
[Nook Color Android Development] West@:
Thanks for CIFS support, but not enought some (maybe one) modules (nls_utf8.ko and md4.ko?). Does anyone have these modules? Or maybe give a link where I can get it?
[Nook Color Android Development] GizmoTheGreen:
what kind of formats are supported by the HW acceleration?

I try to play a 720p anime episode, mkv container, AAC audio, 8bit eencode. it plays very well (not 100% perfect) but MX Player says it's using S/W decoder, it says can't play with H/W or H/W+...

any ideas?
[Nook Color Android Development] hwong96:
Did you enable hardware acceleration option in Mx player settings menu? Software decoding is the default.
[Nook Color Android Development] GizmoTheGreen:
I can choose even after video has started and it says it can't use H/W or H/W+ to decode the video, and jumps back to software.
[Nook Color Android Development] webyrd:
Flashed cm-10-encore-20121208-2306-unofficial.zip Saturday night, changed to interactive Governor, ran fine at 800, then 1000, then 1100 with no SOD's (even overnight at 1100). On previous nightlies I had constant SOD's but only when using interactive governor and occasional SOD using KSM. Enabled KSM Sunday, ran OK at first but started getting ANR's, lag and freezes after using for an hour or so, disabled KSM and performance remained pretty good for the rest of the day. Used V6 Supercharger Sunday evening, running very good now, still no SOD's.

Thanks steven676, keyodi, eyeballer and the rest

MSBN QI0CM9PJ23L

DATE 12/25/2010

CODE OMAP3630 ES1.1

CYTTSP

OMAP3ISP REVISION 15.0
[Nook Color Android Development] Lakland:
is this file cm-10-encore-20121208-2306-unofficial.zip could be the latest nightly ? I mean, loaded in to the CWM web page as the latest cm-10-20121210-NIGHTLY-encore.zip ?

HAve pretty good results I am planning to loaded into the NOOK
[Nook Color Android Development] leapinlar:
As you can see by the quoted post above, that is not a nightly. It is a special test zip. Read.

Sent from my Nook HD+ Running CM10 on SD
[Nook Color Android Development] Lakland:
thank you leapinlar. I follow your procedures and they are excellent. Question: I can install nightly build number 10 (latest on CWM web site) and if I encounter the problems of laging and SOD, I then install this patch at the top of the latest build?
[Nook Color Android Development] dombeef:
Same here, it would be nice to get this working
[Nook Color Android Development] afzalarsalan:
Hardware limitation dictates that video acceleration can only be done up to 800x400
[Nook Color Android Development] leapinlar:
You can try a nightly and if you don't like it, you can install this test zip over the top of it. It is a whole ROM, not just a patch. It is just like you are installing another nightly.

Sent from my Nook HD+ Running CM10 on SD