yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] RoboticBuddy:
No changes in the 20121120 build?

And I'm not asking when, but will OTG support be implemented?
[Nook Color Android Development] meteorrock:
Hey guys, I was able to capture a logcat of some of the lag I got happening on my nook color.

Mine lags at random times, like when I come out of sleep mode, for about 10 minutes and smooths right up.

Sometimes it will start lagging once and awhile during use for no reason when I am browsing on the web, other times it it fine.

It acts like a memory leak or a buffer overflow at this time. After a few minutes of lag it stops. The CPU will be pegged during this time.

I was able to capture a logcat report while this was happening. I will include it here.

This is for the CM 10 11-18 nightly build

~~~~~~~~~~~

Here is my specs on the motherboard: QI 11M98TD6K

Date of manufacture: 01/18/2011

OMAP: OMAP3isp :Revision 15.0

Touchscreen: FT I2C Touchscreen driver
[Nook Color Android Development] lekofraggle:
I am just poking and learning as I go. However, I am trying to figure out how to add OTG. I do not think this is the correct thread, so check the USB Host thread for links and progress (or lack of?).

Here is the short...

I am not a kernel dev.

With DJGutz's help, I figured out how to trace the code to add OTG. [EDIT, he taught me how to begin tracing the code]

There seem to be some changes from the .32 kernel

I have a repo which builds.

I do not yet have OTG, and it is not that stable.

I am still going to poke until either someone who knows more than I gets it working first, or I get too frustrated, confused and give up.

Cheers,

Leko

P.S. I am going away for the holliday and am only taking my Nook (no computer), so I will not be able to work on this probably for a little while.

P.P.S. I am sorry if I am stepping on toes here, I just would really like that feature too, and rather than ask all the time, or bite my nails waiting, I thought I would take a stab.
[Nook Color Android Development] pkchainsaw:
Thanks

---------- Post added at 02:44 AM ---------- Previous post was at 02:41 AM ----------

Thanks
[Nook Color Android Development] meteorrock:
Well, I just looked through that last log I posted, not much useful information in there? Let me try again guys. Looks like a problem with that "playerpro" app I got loaded, looking back through the log. Sorry about that, I was half tired that night. Some sort of hang with that app. Its the latest version from the playstore. :p

Looks more like a fault on the developer from the playstore, not optimizing his apps for JB. I guess you have to close it in the pull down notification box. I will close all apps running through the notification box and try again. Might not be optimized to close all the way and sits in the notification box, on CM 10 JB running in standby. Just a guess. Seriously not trolling, ugggh. Makes me look like an idiot.

Could count as a bug, I do not know, with CyanogenMod not closing apps that are loaded in the notification tray by closing it through the app?

~~~~~~~~~~

Let me try again. Here is some better logs with < I/Activitymanager > lines included. Shows some kernel actions. I will look into researching on how to better filter my results. Been looking online. I see you can filter down to just the faults that come up. For anybody following along here is the link I will go over in the next couple of days. That should help the developers out more. http://www.linuxtopia.org/online_bo...loping/tools/android_adb_filteringoutput.html

Thanks guys. :)

Motherboard: QI 11M98TD6K

Date of manufacture: 01/18/2011

OMAP: OMAP3isp :Revision 15.0

Touchscreen: FT I2C Touchscreen driver
[Nook Color Android Development] envygreen:
I guess add me to the list of people with black screen of death. I installed fresh to emmc after we went to official nightlies (had been on SD install during beta) and I've updated to the most recent.

It was really good at first, but I had some issues with extreme sluggish performance, long lag between input and response, etc. Tried optimizing the scheduler to bfq and changed to performance from interactive etc, but no luck. Now, every time it goes to sleep it doesn't wake.

I'm working today, but I have the next two days off, so I'll try to make some time to go through the hardware survey and pull some logs or will make a backup and fresh install from scratch.

Edit - I had used system tuner to set memory management (OOM) to aggressive, reverted to medium. Also dropped from 1.1 to 800. It woke up after sitting here for a bit. Will play around and see if I can reproduce the problem on demand with one of the two settings by tinkering while I work today.
[Nook Color Android Development] borrego:
11-20 Nightly Build is really good. Adds 1100Mhz OC and consistently gives more free memory.
[Nook Color Android Development] RoboticBuddy:
The problems with OC on CM10 Nightly are not present in the PA 2.55 build.
[Nook Color Android Development] commanderaj:
Screen Lock

Hi All

I have just flashed the lastest nightly build and all appears to have gone well, but it now boots to a lock screen and I have no idea what the pattern is, any ideas?

Wrong rebooted and now it keeps booting into CWM.
[Nook Color Android Development] hwong96:
Place finger on the white lock and slide to the right until you get the open lock.
[Nook Color Android Development] commanderaj:
Its the pattern lock not the swipe lock.
[Nook Color Android Development] Maximum Dude:
Perhaps you previously used a pattern lock, and somehow the setting got changed. Try using any patterns you might have set in the past.

If you never used a pattern lock, then try holding the power button until the NC powers off. If the pattern lock is required upon booting it again, you may have to re-flash.
[Nook Color Android Development] commanderaj:
I think a long time ago I tried to enable it in CM7.1 and it didn't work, will have to try wipe all and try again
[Nook Color Android Development] third son:
I have been using this for a couple of hours now and have to say that it runs much better than cm7 ever did
[Nook Color Android Development] thejrcrafter2:
Ive got two pretty annoying issues:

1. Every so often, the screen randomly locks then unlocks to google chrome without requiring a password.

2. The home button (soft and hardware) do not work, I need to "back" out of any apps to get to the home screen.

3. Turning the screen back on sometimes won't work, it just very very dimly shows what I was doing before I turned off the screen.

I'm running 11/19. Did these issues get fixed in more recent builds?
[Nook Color Android Development] bytte:
There is a recovery via your Gmail account. Keep getting it wrong and it will ask if you have forgotten etc.
[Nook Color Android Development] cmendonc2:
did u restore apps and data using TI backup?
[Nook Color Android Development] doncaruana:
So, after almost 3 and a half days of almost exclusively just stand by, the batter is still at 78%. That's pretty damned amazing if you ask me. That's as good a stand by as I've had on any rom, including any CM7 variant.

Obviously YMMV, but this is pretty spectacular...
[Nook Color Android Development] afzalarsalan:
I recently noticed that my nook color can not connect to ad hoc networks like my phones wifi hotspot. I remember there being a fix way back in the past but am currently on a tablet and the mobile app can't search threads.
[Nook Color Android Development] RallyStyle2003:
2 display issues

I hate to say, but I am bothered by the color banding on the display with the 16 bit color, and I miss the 32-bit. Is there a way to toggle or re-enable it since nook tweaks isn't for cm10?

Also, I ran a touchscreen test in Vellamo with the nook unplugged and got these results:

total unique events: 105

skipped events: 200 (bad)

duplicated events: 0

events analyzed: 305

I don't remember seeing that many skipped events before. I have the cypress screen. I tried the nook screen recalibrate but that had no effect. my screen is clean and there are no scratches. is this a display driver issue perhaps?

fun fact: i was trying to research this a bit more, and this post showed up on google in less than 10 mins.
[Nook Color Android Development] WoodmanMN:
I got tired of the lag I was having, so I did a complete wipe, restored a backup I did of CM7.2, and it ran fine. Battery was what I was used to, as well as performance. So, because I'm not content to leave well enough alone, I downloaded 11/22, did a full wipe, cleared cache/dalvik, and installed fresh. It was running so much better, but I'm having all kinds of play store issues. I couldn't even download the updated Google Search without a package file invalid. I googled it up, cleared the app's cache, the download manager's cache, fixed permissions, turned off auto restore, and it still won't download any major apps (Barnes and Noble Nook Reader for android, Angry Birds Space, etc...) Heck, I can't even use the built in downloader to download the 11/20 nightly, it keeps giving me an MD5 error. Any ideas?

Again, here's what I've done.

Wiped app data/cache

Wiped download manager data/cache

rebooted

In recovery, fixed permissions.

Running GApps 20121011

Going to try downloading 11/20 nightly, and 7/26 Gapps. Will update tomorrow, I'm tired from turkey consumption.
[Nook Color Android Development] meteorrock:
Happy Turkey day for those in the USA :) and also to all of the other developers around the world.

I had one SOD yesterday using the CM10 11-18, it seems that the wakelock bug is still present from CM 7.2 stable. For a workaround I went into the options of CM 10 for the wifi and called up the advanced features in there by pressing the three button vertical column in the top right hand corner. I select the wifi from "never turn off in sleep mode" to "Always off in sleep mode" , however that was labeled. Had to do a hard reboot to recover the nook, by holding in the power button for a few seconds. Did a complete wipe of my data/factory reset cache along with my dalvik caches when I flashed over to this nightly through clockworkmod before mounting this image file. The SOD happened for me with the nook color overnight with it not in use for hours.

Doing that seems to have solved my SOD that I had before, now I have no problem waking up the nook color out of sleep mode constantly today, been using the nook color nonstop for about 6 hours with it constantly going into sleep mode. Lock screen appears when I hit the N button. Still OC up to 1100 MHZ.

Lag for me is spotty. Sometimes my ROM runs smooth as butter, other times I will lag, this is while using the options of CM 10 and browsing the web. The lag will seem to settle down for over a hour or two of use then come back. The lag will last up to 5 or 10 minutes then cease. However, I am heavily modded. Here is my thread on how I modded the services.jar for those wanting to debug and try to eliminate some of that lag you have. http://forum.cyanogenmod.org/topic/61744-cm10-discussion-of-nightlies/

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

No problems here downloading any apps from the "playstore" that I need.

Captured some more logs with using the app "alogcat" today , I have the logcat filtering set to "debug mode." This capture was of a log of me using the "playstore," had some lag at one point during use and one "Wait" option box come up on me today while browsing the playstore. I will post the log here. I set the logcat readout to HTML so it will be easier for the developers.

Going to flash another nightly here in a day or two up from CM 10 11-18.

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

NOOK COLOR:

Here is my specs on the motherboard: QI 11M98TD6K

Date of manufacture: 01/18/2011

OMAP: OMAP3isp :Revision 15.0

Touchscreen: FT I2C Touchscreen driver
[Nook Color Android Development] EAK128:
Have noticed that occasional lag at times and it usually happens after/during market browsing or using the browser. Guessing it is WiFi related.

As far as the market issues downloading or updating I was having that issue on 4.2 on my N7 and the fix was to remove the google account after clearing the market data and then signing back in to your Google account.
[Nook Color Android Development] meteorrock:
Thanks! Sounds like good advice. I will try that and see if that helps.
[Nook Color Android Development] lorddunlow:
I have noticed a strange bug since switching to the nightlies. I've been noticing that when the Nook is sleeping, the screen will flash briefly. This happens about once every 2 minutes. Anyone else notice this? No problems this is causing, unless it's the reason my battery is draining slightly more rapidly. It occurs on nightlies 11/17, 11/18, and a cyandelta update to 11/21.
[Nook Color Android Development] meteorrock:
Going to start looking into changing my I/O scheduler tomorrow before up-flashing to see if I can eliminate the rest of my lag. Running at CFQ. For those that need to get up to speed check out this link here called [REF][TWEAKS] Kernel Governors, Modules, I/O Schedulers, CPU Tweaks, AIO App Configs-- http://xdaforums.com/showthread.php?t=1369817

NOT running 16 bit transparency at the moment, looks like I just got rid of the rest of the lag I had on the playstore by remounting the .gapps file. We will see.

Update: Just changed the I/O scheduler to <noop> and that seemed to have done it on the UI front. Opera works and is up and going for me with no noticeable lag. Running governor at "interactive" . OC at 1100Mhz. I will report back tomorrow and see if this will hold up without an SOD. Says the <noop> is not too good on battery life at the above link but oo well :) CPU is scaling down fine, was hung up at max for awhile after I changed the I/O scheduler inputs.

Running with V6 supercharger with a modded services.jar. Aggressive 1 OOM memory settings. Bulletproof launcher.

Changed setting in wifi advanced options to "turn off on screen standby"

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

NOOK COLOR:

Here is my specs on the motherboard: QI 11M98TD6K

Date of manufacture: 01/18/2011

OMAP: OMAP3isp : Revision 15.0

Touchscreen: FT I2C Touchscreen driver

Governor: interactive

I/O scheduler: noop

V6 supercharged.
[Nook Color Android Development] perakesson:
Greetings from Sweden and thanks for your detailed report! During past week I had 3 SODs and some lagging. Worst lagging was AFTER I had run V6 supercharger, maybe I made some mistake. One of the SODs was running at 1100.

Now I run the November 21 nightly at 1000, all default settings.

No widgets and no fancy stuff. More laggy than CM7.2 but acceptable.

Thus my Nook is good enough to keep me from buying a Nexus.

Questions:

Did you notice improvement after running V6?

Which launcher are you using?
[Nook Color Android Development] derekr:
I read on the Nexus 7 forums that an app called "Forever Gone" eliminated much of the lagginess they were complaining about in 4.1.2 and 4.2. So I tried it on CM10 nightly 11/23 to see if it might have the same dramatic effect on Nookie. The thing is that I can't really tell - certainly not dramatic but maybe a bit smoother. But then, my Nook was not bad to start with.

I offer this just in case it might help people with a bad case of the lags....

ps - Forever Gone simply overwrites all deleted files and then frees up the space. It was written for security purposes. I have no idea how it is supposed to help lagginess, but there are many people claiming good results.
[Nook Color Android Development] swaaye:
A lot of the tweaks out there are entirely placebo effect and people simply don't realize it. Sometimes their tweaks are literally not affecting any settings because they are improperly applied and yet you will still see claims of positive results.

Much of the lag with the Nook Color is caused by the slow CPU, small RAM capacity and the slow EMMC. Overclocking helps. Tweaking the automatic application kill settings (OOM) helps. IO scheduler might help but I don't really sense any tangible change there (the EMMC is just simply slow and if you write to it with say an app install it will drag the system down no matter how it is scheduled).
[Nook Color Android Development] plasticarmyman:
I meant to comment about this!....i am running 11/17...and yes, this happens...it is odd...
[Nook Color Android Development] That Baker Guy:
i've had this problem since the beta's. except it was only when charging i havent noticed it in a while though
[Nook Color Android Development] EAK128:
Yup me too, it happens very rarely, at least I notice it happening rarely.

Another thing that is working for me with lessening the lag is turning sync off. I've only been doing this recently, but so far it helps.
[Nook Color Android Development] thejrcrafter2:
home button issues

hello,

my home button (both soft and hardware) does not work. all that happens when i click it is the screen sort of flashes, the soft buttons go away then come back, and the current app is still on the screen. sliding up on the home (or any other soft buttons) to get to GNow does not work either. Here is a logcat of what happens when I press the home button (only when i press the home button, should i provide the whole logcat from boot to shutdown?)

http://pastebin.com/udGmNByF

this error occurs with every app, i am running 11/23 but it happened since 11/19.
[Nook Color Android Development] bytte:
I'm unfamiliar with these so ran the suite against 7.2 (1200) and B5 (1000).

Metal was down 10% (193 v 220) reflecting the reduced CPU.

HTML was very much improved (788 v 580) presumably reflecting the hardware decoding.

I too got poor results from the touch skipped results (110 - 150) over several trials. 7.2 had no issue (5 skipped) - both with cyttsp.

I don't know what to make of the results for metal / storage / rand-write: 7.2 achieved 80 - 180 over 3 trials, B5 got 8 - 15 ops.

These tests were run on 2 different but similar NCs booted from SD.

Interestingly on B5 device details / sensors doesn't report gravity, linear acceleration or rotation (perhaps there is some interface change in GB that they haven't caught up with).
[Nook Color Android Development] meteorrock:
NO SOD for me overnight, yet I am not using wifi in sleep mode. Changed it in the wifi advanced options to "off in sleep mode." See if that helps. My build is holding up.

I found running V6 supercharger helps allot. For the skeptics? Download a bench-tester from the playstore and see the results. You have to apply the modded services.jar. I shaved up to almost .6 microseconds off on calling up options in CM 10 and with apps. I use" An tu tu benchmark" from the playstore to check results.

Changing the I/O scheduler could be a placebo effect, if it is my build must of settled down and is working more nicely today. Have not done much research into I/O schedulers until yesterday with the link I provided in this thread.

I am using ADW EX 1.3.3.7 launcher

Changing the governor from the default "ondemand" to "interactive" seemed to help for me. Could it be a placebo effect? Could be. My kernels might of settled down on their own also. Researching this though shows it does help.

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

With that and applying mods helps me learn more about the workings of android and linux so its a win win for me. Some of you in here could benefit from learning a bit more. You guys should be posting logcat reports of any bugs you have so the developers can track them down easier. :) Very nice for a fresh nightly build. Is it as fast as 7.2 stable at this point? No. But I am pleased with the developers for giving us this JB build on our nook colors. With some time for the kernels to strengthen on cyanogenmods mainframe computers rebuilding it, it will get faster and better.

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

Not going to lie, I still experience an occasional lag here and there, but now its only for a few seconds here and there over an hour of use. Not getting all of the dreaded force closes and "wait" option boxes like a couple of days ago.

~~~~~~~~~~~

For me I am very pleased with the results on a low end tablet like our nook color running JB at the moment. I will wait a week now and let the code strengthen some before flashing a new nightly. "Angrybirds starwars" plays for me with no lag. Up to the Path of the Jedi levels now, cleared the rest of the levels on this build. They want you to pay to play? ugggh.

~~~~~~~~~~~

I tried the Chrome browser last night on my build. Works for me with a slight touch of lag, I feel when these builds go stable Chrome browser problems will be worked out. Got one or two force closes on that browser while surfing the web. Opera works splendid though.

NOOK COLOR:

Here is my specs on the motherboard: QI 11M98TD6K

Date of manufacture: 01/18/2011

OMAP: OMAP3isp : Revision 15.0

Touchscreen: FT I2C Touchscreen driver

Governor: interactive

I/O scheduler: noop

V6 supercharged. CM 10 11-18 OC 1100mhz
[Nook Color Android Development] meteorrock:
Also for you guys getting SODs you need to put your OMAP Revision number like I have done in my threads.

<fattire> brought in a team of code specialists 4 months ago and reversed engineered the binary code sitting on the processor and the processors caches and found that some of our OMAP processors have a hardware flaw in them that software can not compensate for. Mine has that flaw. OMAP processors get rebuilt and released to specs that have improved just in a few months. You can go over what the team has done through the thread started here. http://xdaforums.com/showthread.php?t=1370873

They can not help much with those issues for SOD since its not software related or code related. So make sure to follow box 4 of this thread. I think the newer nooks do not have this problem. You have the best of the best programmers in the world working on this device from the side, guys. :) And turn off your wifi in sleep mode and see if that helps as a workaround.

Also did some more research into I/O schedulers, its a established branch in the computer scientific field. So do not let waysayers say different :Dx

NOOK COLOR:

Here is my specs on the motherboard: QI 11M98TD6K

Date of manufacture: 01/18/2011

OMAP: OMAP3isp : Revision 15.0

Touchscreen: FT I2C Touchscreen driver

Governor: interactive

I/O scheduler: noop
[Nook Color Android Development] swaaye:
Oh it is. I've played with it on my EeePC 900 for the same reason as we are here. SSDs and flash memory work different than hard disks and Linux tends to come configured for hard disks. CFQ is designed for hard disk mechanical properties. NOOP and Deadline get recommended for flash. But I really have never noted a change when tweaking the IO scheduler on terribly slow flash media like our EMMC or my EEEPC 900's ultra slow SSD.

I am perplexed by Android 4.x's seemingly much slower IO performance on Nook Color compared to Andoid 2.x though.
[Nook Color Android Development] ajrty33:
Do you have more info on the relationship between kernel strength, time, and mainframe computers? I'd like to learn more about that.
[Nook Color Android Development] plasticarmyman:
I am running the 11/24 build...it showed up when i was halfway through downloading 11/23 :P i ran it at 1100 all night, wifi was off and no SOD, do not know if the flickering screen issue was happening....going to run it with wifi on all day and see what happens, but so far so good...

as a request, could we possibly get the BFQ I/O Scheduler?...I am not throughly experienced but I know I have definitely seen a difference with my previous phones running the BFQ vs Noop or Deadline...not a huge difference between it and CFQ but it did change my beanchmark scores for the better...

sorry if i am asking something that is impossible or anything, not trying to be rude just making a request...
[Nook Color Android Development] pastordl:
Check settings performance, i/o schedule. Its in the list and has been there for a while.
[Nook Color Android Development] JeremyNT:
I noticed this as well. Very odd.
[Nook Color Android Development] jeff.p:
The mute toggle in the notifications area mutes but doesn't unmute.
[Nook Color Android Development] himasura:
Just set it once as you need:

Spoiler content hidden.