yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] steven676:
Mostly snake oil. All of the TCP options (selective ACK, window scaling, timestamps) have been enabled by default in Linux for ages and ages and ages. RFC1337 specifies methods for avoiding "TIME-WAIT assassination"; when tcp_rfc1337 is not set, Linux avoids this via a method not specified in the RFC. ECN either increases your throughput or results in your being unable to connect, depending on whether the routers in between you and the server are broken or not. Metrics caching improves performance in most cases; unless your tablet is bouncing between wifi networks very quickly, or network conditions vary greatly, it shouldn't hurt.

That leaves the TCP buffer size options. tcp_rmem and tcp_wmem settings won't stick -- Android resets them for you whenever you enable/disable/change networks according to the value of the net.tcp.buffersize.* properties. (Also, the values in that thread represent a decrease in window sizes from the Android defaults for wifi networks.) Increasing the size of tcp_mem (which controls how much memory TCP will use as a whole) might potentially improve performance -- but the values are in units of pages (4 KB on ARM), and 187,000 pages represents more than 730 MB -- way more than we actually have on the system. The default values selected by the kernel (40-80 MB) seem to be reasonable, but I could see more being potentially useful. The number being given is completely ridiculous, though.

At a guess, these tuning settings come from some early-2000s guide to network stack tuning. Moral of the story: don't blindly apply settings when you don't understand what they're doing!
[Nook Color Android Development] bmw2k1:
Bros everytime I click something on jb it keeps giving me an android process media has stop error.
[Nook Color Android Development] Lakland:
This rom is running very smooth and snappy!!!!! Yeah :D:sly:
[Nook Color Android Development] hwong96:
More details please. Did you install CM10 on SD card or internal emmc? What GApps version did you install? Only version jb-GApps-20121011 works with CM10. What version of CM10 did you install-alpha, beta or latest nightly?
[Nook Color Android Development] Lakland:
I am really impress with this rom!!!!!! Today i have 1 ramdom reboot, but besides that, everything is running just almost a new tablet!! Yeah rock on devs!!! Very happy with this rom.

My current setup:

Cpu governor: interactive

Not overclock: max clock speed 1000

I/o scheduler: cfq

Memory mgnt: zram default, purging assests and kernel merging check

16 bit trans check

I have enable seeder app

Using nova launcher

:sly::thumbup::D:p

---------- Post added at 05:03 AM ---------- Previous post was at 04:44 AM ----------

I just pluged to charge the nook and nook reboots itself. It noots very fast, but that also happening with 0113 rom
[Nook Color Android Development] Lakland:
Another random reboot in this rom :eek:
[Nook Color Android Development] anapospastos:
Anyone?
[Nook Color Android Development] WJThomas:
In the past I was using my phone for GPS for the Nook (CM7), but I had problems with the phone Bluetooth dropping out every time I got an incoming call. I have since purchased a Bluetooth GPS receiver.

It works very well with CM7, but was a struggle with CM10 and PA. For a while I thought btpair (from the market) was helping, but now I am not so sure. I seem to have good results just booting the Nook, turning on the GPS, and enabling GPS on the Nook. Note that I have previously paired with the GPS receiver and selected it as the GPS source. I know it is working when the GPS icon shows up in the notification bar. Sometimes the Nook's GPS will turn off without connecting. I play around with turning it back on and/or power cycling the GPS receiver and/or rebooting the Nook.

I've never used any special GPS software for the Nook, except in the very beginning with CM7 until I discovered that my connection difficulties were from the GPS apps interfering with the built in CM7 GPS capabilities.
[Nook Color Android Development] hwong96:
I use a Bluetooth GPS receiver-Keychain GPS 2000. It works with The BluetoothGPS app. It works on both CM7 and CM10.
[Nook Color Android Development] k8108:
Is there a way to access My Apps in the play store menu? I noticed it is missing in my version with CM 10 and also in the PA build. (I have googled and searched, but can't find an answer)
[Nook Color Android Development] leapinlar:
It is not in the menu. There is a down arrow on the top bar. Hit that and you can scroll between installed and all apps you have installed in the past.

Sent from my HD+ running CM10 on SD with XDA Premium
[Nook Color Android Development] Lakland:
I am having random reboots and SOD in this Rom. Is running smothered and snappy but with this catch
[Nook Color Android Development] meteorrock:
Running the nightly from Jan, 14. What a HUGE improvement. Performance almost doubled for me flashing that nightly from the Jan 4th nightly.

No SODs to report, I was not having that problem though for CM 10 from the beginning. Still noticed the icon for the pull up notification screen is out of place, which is probably common knowledge now.

All and all, great work from the team. Still going with the settings I posted earlier in the thread here, overclocking and other tweaks in the performance settings for CM 10. Not noticing other outstanding bugs now. Lag is almost disapeared, only appears on graphic heavy websites with videos interlaced within the pages, for example youtube and their webpages.
[Nook Color Android Development] Lakland:
I am running 2013-0113 nightly and i agree with you on performance. But i am having sod when charging and some random reboots.
[Nook Color Android Development] meteorrock:
You have done a wipe of your data and your caches then upon updating your nightlies? I had one SOD when they first put up the nightlies for me in December but I have not had any problems since then when I went ahead and wiped the data, caches in clockworkmod or TWRP, whichever recovery software you are using. I don't do it everytime, but those that don't sometimes have that problem with SODs

Make sure to do an nandroid backup with those above apps and try that. If no luck there then you will know if its a legit bug or not for you in CM 10.
[Nook Color Android Development] jsmith8858:
This might just be yet another placebo effect, but the latest "lag fix" app here on xda seemed to make things a bit snappier for me:

http://xdaforums.com/showthread.php?t=2104326
[Nook Color Android Development] thejrcrafter2:
Is 01-14 the last nightly update for the nook?
[Nook Color Android Development] leapinlar:
Yep

Sent from my HD+ running CM10 on SD with XDA Premium
[Nook Color Android Development] eyeballer:
CM 10 has moved to weekly builds, as most efforts are now on CM 10.1 (which will get nightlies).
[Nook Color Android Development] kcls:
Do you think you could repost or link me to what you are using? Because I installed the random seed app and forced 2d GPU rendering in the settings but it's still kind of laggy for me.
[Nook Color Android Development] t499user:
No, there is one from today.
[Nook Color Android Development] pk2_76:
Anyone tried it?
[Nook Color Android Development] leapinlar:
Yes, it works ok.

Sent from my Galaxy Tab running Tapatalk
[Nook Color Android Development] Mr-Glass:
I tried it.. Having issues with this and 1/14... CPU is pegged at 100%.. I am sure a complete wipe should correct it just have not got to that yet, was not having this issue before with the nightlies.. It is almost like it is stuck on performance and I have always used 300/1100 Interactive with Noop.. Looks like I will TB - and wipe all/reset..
[Nook Color Android Development] leapinlar:
That is the media scanner. It always does that for a few minutes when I flash a new ROM. It settles down after it finishes, depending on how much stuff you have on your SD.

Sent from my HD+ running CM10 on SD with XDA Premium
[Nook Color Android Development] Mr-Glass:
Leapinlar, I am not sure that is it exactly, for example last night I picked up the NC and had been using it earlier in the day and it had dropped 25 percent battery without wifi on.. checked system panel light and it was at 100% CPU - could not see anything standing out that would be using that much cpu.. I have witnessed on almost all ROM updates the media scanner you are talking about and as you said it settles down after awhile..
[Nook Color Android Development] leapinlar:
With system panel, set it to show system apps too and you will see what is running.

Sent from my HD+ running CM10 on SD with XDA Premium
[Nook Color Android Development] Mr-Glass:
Thanks, I will have to check that.- in the process of wiping and adding apps back right now....
[Nook Color Android Development] mybeeky:
I have just installed 20130114. It so great with new UI and lots of useful function. And one more importance thing is it will sleep when I charge. The CM 7.2 will turn on the display all day if I forget pushing power button. But I don't know why sometimes it turn on the display suddenly and dim immediately when it sleep. Anybody have the same problem
[Nook Color Android Development] Dave08:
You can always see the latest changelogs at http://10.cmxlog.com/?device=encore.
[Nook Color Android Development] unicyclingEMT:
Can anyone talk about what is involved in moving the nook CM10 to CM10.1? What are some of the issues involved? What kinds of things are missing in the current code base? Is there any way we could help?

Thanks.

SG
[Nook Color Android Development] steven676:
It builds fine, as I understand, and runs -- I haven't had time to do much more with CM10.1 than play around with a build briefly. My quick impression is that performance isn't nearly as good yet and that there are a couple of rough edges. All the usual features work except for Bluetooth (and I think we know how to fix that). That said, there's not that much in the way of new user-visible features in 4.2 either -- most of the change is under the hood.
[Nook Color Android Development] bluepen61:
Experience with 12/17 move to 1/14 and then 1/20 nightlies.

I

updated

to 1/14 and had daily SOD's. Also, it decided not to charge properly. I suspected I should have wiped the NC.

So I wiped and installed 1/20. Looks like I am back in business! I have yet to update the launcher or the keyboard. What to see how my most used apps work with stock setup.
[Nook Color Android Development] pdahiker:
I've been running the 1/14 build for several days, and the performance seems to be better in terms of lag and overall usability.

I also tried something new to see if I could prevent the continuing S.O.D.'s and I believe this following solution has fixed it for me:

I installed the free app "Wake My Android Pro" from the market, and set it for "19 minutes" (how often it will do an invisible wake lock) and "Auto Startup". These are the only options I am using. I also went back to a 15 minute WiFi timeout during sleep. Since I have started using this app I have not had a single S.O.D. while charging or after being inactive for a while, and the Nook wakes up from sleep instantly now. I am not sure if there is any correlation, but battery life while the unit is inactive seems to be quite a bit better than before. Not sure why this is, I would have thought the opposite.

The other issue I have had, like many others, is the lack of volume out of the headphone port. After trying nearly all of the "volume bosters" and finding them lacking in quality or just not working at all, I fixed this by purchasing this Pyle headphone amp:

http://www.amazon.com/Pyle-PHE3AW-Headphone-Amplifier-Boost/dp/B004V9G22G

Overall sound quality through this little amp is MUCH better from the Nook and from other devices I have tried it on, especially with larger headphones.

Now, if we can just get the notification clear button moved back to where it was, I am very close to having everything I need.:)
[Nook Color Android Development] stolenmoment:
Can you describe the charge behavior? Mine is stuck at 34% (reported by multiple sources), but it does notice when it's plugged in, and the LED on the cord went green pretty much on schedule.

I had a couple of shutdowns without the usual popup at 14% when I suspect the battery ran dry. I wiped system and caches and installed several old ROMs without fixing the charge behavior.
[Nook Color Android Development] Mr-Glass:
Leapinlar - I did my complete wipe and have been fine since, however I just connected to my laptop in mass storage mode to move over 7 ebooks, just 22mg - and for the last 15 minutes the android.process.media has had the CPU pegged again.. I am not sure why this is happening.. I only have about 12gb used on a 32gb card so I would not expect this to run so much.. any ideas? Thanks
[Nook Color Android Development] bluepen61:
Hmm. It is pretty difficult to discern, but here is what I remember. Unplugged the NC knew it was discharging. When plugged in, the NC knew it was hooked to the charger but it didn't charge. I rebooted the NC and that didn't help. After several hours, my NC barely charged.

After doing a clean install, it charged to 100% and green overnight. I wish I was of more help.
[Nook Color Android Development] leapinlar:
Go to the folders that you are sure you do not want indexed and put a file named .nomedia. Be careful though, media scanner is how MTP gets refreshed so it shows on your PC and you want your files showing.

Sent from my HD+ running CM10 on SD with XDA Premium
[Nook Color Android Development] aeturnus77:
Hmmm so I flashed the 01/20 update on my nook color yesterday, as I've been doing when new nightlies/weeklies since November 19... I sat there and watched it reboot and go into the installer, left for a bit and when i came back, my nook color was completely dead. I thought perhaps it SOD'd but nothing I'm doing will get this thing to boot up. Held the power in for over a min, tried various combos with power and n, and with volumes.. any ideas??
[Nook Color Android Development] leapinlar:
Take the card out and try to boot to stock. You may need to hold the power button for a long time, then release and try to power on normally.

Sent from my HD+ running CM10 on SD with XDA Premium
[Nook Color Android Development] aeturnus77:
Thanks for the response, Leapinlar. still no response whatsoever from it. By long time, would 5-10 min be considered long?
[Nook Color Android Development] leapinlar:
Edit: I monitor too many devices. I thought you were talking about the HD+ with CM10 on SD. Scratch everything I said below. You were talking about the Nook Color, probably on internal memory. You definitely have corrupted boot files in your interior boot partition. If you insert a bootable CWM card it should turn on and you can reflash your CM10 rom to revive the device.

Forget the below and read the edit above.

No, I meant a minute or so.

With the nook colors they had a feature that if it could not find valid boot files in the boot partition, it would not power on. But the configuration of the HD/HD+ is much different internally than the color. It has separate image partitions for xloader, bootloader and kernel, so I don't know how that plays out. On the SD, it is much like the color, with xloader, bootloader and kernel being files in a single boot partition. I am not sure how, but I think that is the mechanism that is happening. It thinks a card is present to boot from, but cannot find the files and will not turn on. And the SD takes precedence over the interior files at boot time.

Someone in another thread said something about having to wait 30 minutes after inserting a bootable card before it would boot with the card in. That is why I wanted you to hold the power button, to be sure any power on mechanism is totally off and maybe it would try to boot from the interior files.

I'm not sure how any of this helps, but maybe with this knowledge someone will come up with the right solution. And so far only people with the HD+ have had this happen.

I just had a thought, what about burning a fresh card and trying to boot with that? Maybe your boot files got corrupted somehow.

Sent from my HD+ running CM10 on SD with XDA Premium
[Nook Color Android Development] t499user:
I had something similar happen the other day while flashing some stuff. I was going to give it a few days to kill the battery, but instead disconnected the battery, it was only 2 screws, I think T-5 was the size. Once you have the back cover off just have to pry the battery connector up. Put it back on after a brief time and it booted fine.
[Nook Color Android Development] aeturnus77:
Actually had it open last night but didn't have anything to unplug the battery with at the time so maybe I'll revisit that tonight when i get home. Otherwise I'll give leapinlar's suggestion a try once I relocate my boot card.

Thanks guys I'll let you know how I make out!
[Nook Color Android Development] bluepen61:
I would like to add to my prior post:

When it was in SOD mode (again last night), plugging in or unplugging the power cable did not wake-up the NC. Fiddle as I might, it remained in SOD. Only after holding the power button did it wake up. Then, it did charge correctly overnight. After a brief use this morning and sleeping (about 3 hrs), it is now SOD.

Didn't have this problem with 12/17 nightlie. Most of the apps, I restored from Titanium Backup. Maybe I should do a direct download from Playstore, next time.
[Nook Color Android Development] hsiangyang:
Just flashed the CM10 nightly 0120 from 11/10 MiRaGe - KANG build CM7.2. Use the ADW as launcher and found that the

desktop icons become bigger than original size in CM7.2. As I remember, there is a configurable setting in CM7.2. I just can't

find the similar setting item in CM10. Does anyone know how to change it??
[Nook Color Android Development] leapinlar:
If you use ADW as your launcher, I believe the icon size setting is in ADW settings.

Sent from my HD+ running CM10 on SD with XDA Premium
[Nook Color Android Development] pissat4motion:
I'm getting an "insufficient storage" when updating apps through play store. Hadn't encountered this before updating to 1/20 nightly. Probably a simple fix or me missing something. Any ideas?

Showing plenty of space on emmc and SD card..

TIA
[Nook Color Android Development] leapinlar:
It needs space on /data to download and install apps. Make sure you can write files to /data. Sometimes it gets set read only. You may need to go to recovery and fix permissions.

Sent from my HD+ running CM10 on SD with XDA Premium
[Nook Color Android Development] hsiangyang:
Thanks for the reply. That is what I think too. But I checked the ADW settings item by item, in the screen and Icons setting, I can

only change the columns, rows of desktop or the text size, color. There is no setting to change the icon size.
[Nook Color Android Development] leapinlar:
I use ADW EX which does allow icon sizing. Do you have the latest version of free ADW? I think they just added it to the ADW EX. They might have it in the new free too.

Sent from my HD+ running CM10 on SD with XDA Premium
[Nook Color Android Development] aeturnus77:
This worked like champ. Thanks! I'll have to pick up another SD card to burn as a boot since my old boot disk has turned into my nook HD boot, so that was actually the hardest part!
[Nook Color Android Development] pissat4motion:
Checked to make sure data is set to R/W ..also fixed permissions. Theres a little over 100mb showing available. Any other idea?

* I actually may still be on nightly 1/14 so all download and tty 1/20
[Nook Color Android Development] leapinlar:
Did you actually try writing something to /data? And 100MB is not much space on /data. Play Store may want more space than that available. You might try moving some apps to SD to free up space.

Sent from my HD+ running CM10 on SD with XDA Premium
[Nook Color Android Development] mrapollinax:
I had this issue and removing some CM images freed up the space to updatte apps. For me it was the Facebook app that kept throwing up the exception while other (possibly smaller apps) were updating fine.
[Nook Color Android Development] pckoloji:
1/20 nightly and for the 1st time overnight charge (turned off after plugging) was upto 77% so i guess it is slower than before because 4 hours was enough until now. original cable and charger. not stuck at 77%, it continues to charge until full but slower than before.

there is no problem at all. never got sod with cm10.

should i keep turned on for faster charge or something changed in code?

update:

1- 6 hours (turned off) during night charge 14% > 77%

2- 1 hour (turned on) morning charge 77% > 93%

somehow turned on charging faster or after some charge it accelerates?
[Nook Color Android Development] 1800collect:
I've tried installing the 1/20 nightly but keep getting the error "android keyboard aosp has stopped" when loading into CM10. I do the exact same process for the 1/14 nightly and I don't get the error. The same gapps file is used. I've checksum'd the 1/20 and it says it is correct. I downloaded it multiple times. Dunno what the problem is with 1/20 not working for me but 1/14 does. Format data/factory reset, format cache, format davlik cache were all done and same steps done for each.
[Nook Color Android Development] bluepen61:
The wipe didn't resolve the SOD's. Then, I did boot to CWM recovery and ran fix permissions. No SOD's so far.
[Nook Color Android Development] steven676:
New test kernel

EDIT: This test kernel has been superseded -- the next one is posted here.

Here's a new test kernel for everyone to try out. (Source code: https://github.com/steven676/ti-omap-encore-kernel3/tree/8bca6dfc4f369131ee55f86155f3b437f93347e2) The changes are a grab bag of bug fixes, mostly in power management code, but I'm not sure whether they fix any of the reported problems on that front; there are also one or two changes which might improve overclocking stability.

Please try out and report back, particularly if you have an ES1.1 chip and have been experiencing SOD. (Please also speak up if you experience SOD with this kernel, but not with the kernels from recent nightly builds!)

Installation: From recovery, flash the ZIP file attached to this post over an existing ROM to install the new kernel.
[Nook Color Android Development] Mr-Glass:
Just installed the new weekly - Every week I hope that the clear notification button is moved - every week no joy.. Any idea if this done purposely or if it is just waiting for a fix.. Everything else works fine on the two NC's that are running this..
[Nook Color Android Development] derekr:
No problem with the new test kernel so far....

Update: Not so good - things have become very slow. Never seen Nookie like this before. Going back to 1/27...

Note - I lost 55% of the battery in 4 hours while turned off, never had this problem before!
[Nook Color Android Development] Lakland:
I have been on 20130120 nighly. I did a clear install. So far is almost smooth. One random reboot, no sod. Nook app works ok, I mean the latestnook app. On other nightlies, nook app do not open some books. I use lagfix app. I was using seeder, but I see better performance in his one. Sometimes there is lag and freze on browser. I have maxton, chrome and default browser. Maxthon do better. I may try 0127. Let see how rhe feedback is.
[Nook Color Android Development] skwalas:
Lakland, i am prepping for test to see if lagfix, seeder, or others are actually doing anything. Since you've used both, can you please share your settings, either on my performance thread under general or by PM? Thanks!
[Nook Color Android Development] Lakland:
I PM you, but the performance topic is very good. I will try your recommendations :D:thumbup: