yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] otaku91:
Thanks for this. It works perfectly when I edit build.prop, but doesn't seem to work when I add a file to data/property.

Any idea on a common mistake I could be making?

Thanks again.
[Nook Color Android Development] leapinlar:
May be the file permissions in /data/property. Make that new file have the same permissions as the other files there. And make sure it has a 1 stored in the contents.

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook Color Android Development] hushpup131:
So embarrassing, just installed 10.2 20130919, thought I'd do a safe & clean install by wiping dav & cache plus factory wipe... may I ask, which is the "correct" version of gapp to use?
[Nook Color Android Development] leapinlar:
It is the latest, which I believe is 20130813. Get it at goo.im.

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook Color Android Development] hushpup131:
Thank you, for the benefit of our readers, I'm posting this link for the table reference for the correct version of gapps for the correct ROM

http://wiki.cyanogenmod.org/w/Gapps
[Nook Color Android Development] aperezdc:
Also, I had to write exactly a “1” without a newline or anything else to the property file, like this from an ADB shell:

cd /data/property
echo -n 1 > persist.sys.vold.switchexternal

Otherwise it won't work.
[Nook Color Android Development] steven676:
New test kernel (and hwcomposer!)

Here's a new kernel for everyone to test out. This one contains the biggest changes we've seen in quite a while, and as such, may not be as stable as some of the previous test kernels I've posted -- please let me know how it goes.

Changes:

Updated to upstream (kernel.org) stable kernel 3.0.88, bringing in a huge number of bug fixes to core kernel code.

Synchronized with Android kernel/common up to the same point as the Galaxy Nexus AOSP 4.3 kernels, bringing in bug fixes to Android-related code.

Raised the maximum overclock to 1.2 GHz. A patch by loSconosciuto (correctly implementing an idea I tried and abandoned a while ago) is applied to disable the use of SmartReflex at that OPP, which should hopefully reduce the stability problems some people were experiencing at 1.2 GHz.

Reduced the screen refresh rate to 54 Hz. This allows us to use a lower pixel clock of 43.2 MHz, which allows us to set CONFIG_OMAP2_DSS_MIN_FCK_PER_PCK=4, which allows the DSS subsystem to downscale 720p video to fit our display. Why do we need this? Because ...

Included the (userspace) OMAP3 hwcomposer module, allowing full hardware-accelerated overlay scaling and rendering without touching the GPU (reducing memory bandwidth used and increasing performance). Many thanks to dhiru1602 and keyodi, who have been laying the groundwork to allow us to use the hwcomposer.

Known issues:

The DSS scaler's output image quality seems to leave something to be desired -- this is most obvious when viewing 720p video.

Occasionally, the PVR drivers will decide to throw a tantrum (very visible in dmesg), causing the system to pause for seconds at a time. It's unknown why this occurs, and the only cure is a reboot.

I'm most interested in feedback on performance and on stability of the system with hwcomposer. I'd also like to hear from you if the 1.2 GHz overclock causes crashes with this kernel AND those crashes didn't appear with CM7 (or other 2.6.32-based ROM) at 1.2 GHz. For clarity: I am not interested in reports that overclocking to 1.2 GHz causes you problems UNLESS those problems didn't appear when running at 1.2 GHz with an earlier kernel.

Source code: kernel, hwcomposer, wl12xx wifi modules.
[Nook Color Android Development] pastordl:
9-21 nightly?

What's up with the 9-21 nightly? It's about 18 meg smaller than the previous nightlies. Don't want to try the new kernel to the nightly if it's not complete. I have installed the nightly and it boots fine but haven't tried much else yet. If its ok it must be some house cleaning, almost 10%.

:confused:
[Nook Color Android Development] pastordl:
Tried it & liked it.

Tried this kernel with 9-21 nightly. Like it, smoother videos both Netflix & YouTube. Tried @ 1200mhz and got flakey, force close, etc. This unit ran fine @ 1200mhz+ with cm7. I had been @ 1000mhz before with cm 10. Still curious about the "missing" 18 meg on latest nightly.

:good::highfive:
[Nook Color Android Development] DizzyDen:
The major differences are the following modules have been removed from /system/lib

libexiv2.so

libglib-2.0.so

libgmodule-2.0.so

libgobject-2.0.so

libgthread-2.0.so

libjni_mosaic2.so

libpano13.so

libpopen_helper_jni.so

libtiff.so

libtiffdecoder.so

libvigraimpex.so

libxml2.so

libxmphelper_jni.so

libxmptoolkit.so

and the following removed from /system/bin

autopano

celeste

enblend

enfuse
[Nook Color Android Development] andtron:
My nook froze at 1,2ghz using Steve's new kernel, now rolledback to 1.0.

Could we have the 1.1ghz back :)?

Edit: With the new kernel, my PC no longer recognizes the device, I did update the new 4.3 SDK. I have no such problem with the 2013-09-16 build, even without the 4.3 SDK.
[Nook Color Android Development] hliew88:
Broke some apps

The switch worked like a charm! sdcard1 is now mounted as my internal partition...

...which brought up a problem. I had apps that were installed on my SD card (like games that took up >35MB), but even though I moved all the files from external to internal when I did the switch (nothing out of the ordinary), after reboot and Dalvik wipe, the data for the apps on the SD card seemed to have gotten wiped.

Is this something that could be avoided?
[Nook Color Android Development] leapinlar:
Did you move the Android folder and all of its contents. A lot of app data gets put there.

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook Color Android Development] hliew88:
Yes, I moved the Android folder, and I know because all my other app data is there. Even after I reinstalled all the SD card apps, their data was still there (for example, my Firefox history was all still there and I didn't have to start over in Candy Crush)!

I guess this is something anyone who does this switch has to be careful about.
[Nook Color Android Development] leapinlar:
I'm not really sure what you mean by SD card apps. All apps are installed on internal memory (/data/app). And all apps store their primary data and settings on internal memory (/data/data). But a some apps store extra data like game data and media files on SD (either in the Android folder or their own created folder). Those extra data and media files are the ones you want to move if doing the swap.

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook Color Android Development] webyrd:
Only been running for a few hours, no problems here at 1200 so far - thanks
[Nook Color Android Development] Arbelzapf:
No problems here either. I have been running my nook at 1200 all day without problems. It does feel snappier as well :) Thank you very much for this kernel, I hope it continues to behave well
[Nook Color Android Development] hliew88:
I ran out of space in /data (since it's only 1GB), so I used the native apps2sd to move the data otherwise stored in /data/app to the SD card. It's in the options when you go to Settings -> Apps, but I used Link2SD to do it automatically. Either way, I had manually moved all the data (it checked out size-wise), but it didn't work upon reboot. Not a problem anymore, just putting it out there.
[Nook Color Android Development] leapinlar:
You must be running CM7 (gingerbread) for there to be that option (app2sd) in settings. ICS and above do not support it natively. And if you were running link2sd (which I have used before on old devices) on CM10.1/CM10.2, unpredictable results could happen running my swap. I have not heard of anyone running link2sd successfully on anything above gingerbread. But I guess it is theoretically possible.

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook Color Android Development] kwood129:
I have been having a little bit of trouble with a little freezing at times but what caught my attention right away was that I couldn't get WiFi to work. I would click it on, it would go gray for a while and then turn back off. Reinstalling the ROM corrected the problem but of course no overloclocking again.
[Nook Color Android Development] andtron:
Hliew88 is right, even with 10.1, 10.2 you could use setting->app then to the individual app (downloaded, e.g, Dolphin Brower) and click the option MOVE TO SD.

Of course, you couldn't do it for google apps, which always stored in the internal sd card.
[Nook Color Android Development] leapinlar:
I see that now looking at CM10.2 on emmc. That is something implemented for nook color then. My other jb devices (Nook HD/HD+ and Galaxy Tab2) do not support it. It may be because those three devices emulate sdcard from /data. I have too many devices to keep up with.

And since this is not really my swap, but CM's, it should work ok if you use app2sd.

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook Color Android Development] granny smith:
I am on nightly 9/23 with the new kernel at 1200 mhz and my issue is that eventually the nook freezes and completely shuts off. It happened twice in about 4 hours. Also, while watching Netflix i noticed brief visual artifacts. The 2nd time my nook froze and shut off, there were a lot of visual artifacts right before it shut off.

Edit: I ran CM7 at 1200 mhz and I did not ever experience this issue.
[Nook Color Android Development] frankusb:
Tried this out tonight. I used to run CM7 at 1.2GHz with no known problems due to overclocking. I set this kernel to 1.2GHz and it completely locked up within about 4 minutes of playing a Youtube video. Running at 1GHz since just fine, watched several YouTube videos.

Things are oh so smooth but there are definitely glitches. At one point, desktops were overlapping (the adjacent desktop was showing) on the home screen. Rotating from landscape to portrait and back made the overlap go away.

Frank
[Nook Color Android Development] aperezdc:
This kernel seems to be quite stable in my Nook. I experienced the pauses you mentioned from the PVR drivers twice (and rebooted), but apart from that no other problems. I don't use YouTube/Netflix much in the Nook, but it seems to work fine and in my personal experience, with this kernel there's no video tearing (which happened sometimes with the kernel included in the CM10.2 nightlies for certain videos in YouTube). For the record: never had problems with my Nook previously at 1.2GHz with CM7.
[Nook Color Android Development] viskon:
I just updated to the latest nightly from the 9-14 nightly. The old NC is so much snappier now. Thank you to all the devs that contribute.
[Nook Color Android Development] pastordl:
Test kernel verdict?

Will the 3.0.88. 9/21/2013 test kernel be merged soon? I find it does run smoother and definitely helps video. Still doesn't help OC, but happy with what it does.
[Nook Color Android Development] webyrd:
Still no problems with test kernal at 1200 on my NC, never had OC problems on CM7 either
[Nook Color Android Development] snives:
Here's a fun one...

Using 9-24 + test kernel at 1.0

Watching a few shows through Plex

Video starts to jitter

pull up overlay to fast forward and check if it's a bad encode, Jitter stops

Drop overlay and jitter comes back

Repeated 3x to confirm... The overlay somehow fixed playback.

Hopefully someone greater than me might be able to figure out where some fixes might come from. I'm forgetting my exact hardware build, but it was from the first month of sales.
[Nook Color Android Development] steven676:
This is actually a CM10.2 Trebuchet bug (to reproduce, open the app drawer in landscape, then close it and do some swiping between home screens).

Not as such. The 3.0-stable and Android kernel/common stuff will go in when I get back to a computer (I'm on vacation until Friday), but you guys have uncovered some bugs in the rest to be ironed out.

Along those lines: can someone who had a stable 1.2 GHz overclock on CM7, but not with this kernel, provide dmesg output from running CM7 at 1.2 GHz?

Yep, introducing additional layers can change the rendering path when hwcomposer is enabled. I assume this works correctly without hwcomposer (e.g. on any CM10.2 nightly without the test kernel package installed)? If so, could you please supply a dmesg and logcat from when this happens?
[Nook Color Android Development] purpleurkle:
I've been running 9/18 nightly, on SD. When I loaded test kernel, nook became so unresponsive I struggled getting to performance settings, but once I was able to overclock to 1.2 it smoothed back out. I too am getting visual artifacts while watching Netflix
[Nook Color Android Development] webyrd:
SOD on test kernel

Had my first SOD in quite a while today, had charged overnight yesterday, unplugged this morning without using. Came home to SOD, battery at 45% after reboot. Last_kmsg at https://db.tt/BfG4z704

Running test kernel over 9/25 nightly, OC'd to 1200, first irregular behavior, other than occasional artifacts (minor) during HD video playback, that I have seen on the kernel.

Edit - unable to reproduce after two more sleep cycles - has been working fine since
[Nook Color Android Development] Der_Neger:
Hi Dev's,

my Nook is running fine @ 1,2Ghz. But i have a question if it is possible to overclock the gpu aswell Quarx has achieved it for the Motorola Defy

link:

http://xdaforums.com/showthread.php?t=2385250

Even USB OTG should work as they said with the Aero Kernel for the Defy. (instable/ but it's a start)

I think this will be helpful because our Nook Color has almost the same Hardware platform.
[Nook Color Android Development] samcoinc:
I am running steves test kernel (3.0.88-04380-g9fe676d)

If I overclock to 1200 the nook will reboot within 15 seconds or so.. :)

I don't remember if I could ever do 1200 though - even with cm7.. This might just be a limit of my nook.

Overall though - This has been the best build yet. Youtube videos (full screen) seem very smooth. (windowed playback still tears)

Thanks for all the hardwork!!

sam
[Nook Color Android Development] pastordl:
Reboot recovery

Was anything done in the 10/1 nightly that might have effected the reboot to recovery? I use the Elixir widgets reboot widget and tbe reboot to recovery option just reboot after 10/1 nightly installed. The power shutoff reboot to recovery still works.

Also have the working parts of the latest test kernel been merged into the nightly? Just curious.
[Nook Color Android Development] steven676:
Sorry, I haven't had time to look at anything at all this week -- family emergency.
[Nook Color Android Development] kwyrt:
1. Don't apologize. We are all grateful for what you do for our ole Nook Colors. I hope all is well with you are yours.

2. I just have to say, I am amazed at what you and the other devs have managed to accomplish with this kernel and ROM. It runs FAR better than it has any right too on this old hardware. Truly astounding. :good:
[Nook Color Android Development] moocow1452:
Anyway, paid $35 for a used Nook Color on Glyde, got it unopened with the box and the plastic wrap still on it from 2010. What did I miss guys? :)
[Nook Color Android Development] metapolis:
Steves test kernel (3.0.88-04380-g9fe676d)

Hi, were can I download it? And where can I overclock it? Do I have to use an add App?
[Nook Color Android Development] pastordl:
Lesson

A little search for "Kernel" in the "search this thread" and voila.

http://xdaforums.com/showpost.php?p=45785641&postcount=107

All your questions answered.

It's how I learned what little I know, now it's yours.
[Nook Color Android Development] bigbob23:
This kernel has been working quite well for me. Are there plans to incorporate it into the nightlies?
[Nook Color Android Development] EAK128:
Just curious if something like this could be used on our kernel to gain some more available RAM. Thanks.

https://github.com/franciscofranco/Tuna_JB_pre1/commit/a5200bf56b02453da6d8d33e83baf2e51f014845
[Nook Color Android Development] viskon:
I upgraded from one of the earlier nightlies, and I must say I am shocked by how well the latest nightly runs.
[Nook Color Android Development] pastordl:
Email problem with update - again

I updated from 10/14 to 10/19 nightly. Everything seemed fine till I checked my email (android) and tried to reply. Forced close every time. Had no problem before. Tried a restore from TB with data. No change. Rebooted and restored from backup of 10/14 made before update. Email not working. Had worked about 1/2 hr before backup. Tried again with TB restore app & data. No joy. Deleted data in manager, re-entered account info for three accounts worked. Then back to recovery, backup, install 10/19. On reboot tried email, same problem. Deleted data, reentered account info, working.

Was something changed from 10/14 to 10 /19 that messes with the email data? Since the same problem happened with the update to 10/19 twice, it begs the question.

Just updated to 10/21same problem, attempt to reply causes FC. Was able to do restore from TB and its back running. Something with updating ROM is messing with android E-mail.
[Nook Color Android Development] steven676:
Doing some catchup here ...

Still looking for this. Anyone? (I want to see what voltages are actually in use on CM7 systems running at 1.2 GHz.)

Sorry, nope -- the OMAP3 reserved heaps are already about as small as they can get (LGE elected to increase them a bit over what we have because some of their tests were failing). OMAP4 is a different story there.

Assuming we mean the AOSP "stock" email app, I don't see any changes this month to it. It could theoretically be a change elsewhere, but it's impossible to say without more info (as usual for any app crash, a logcat would likely be useful).

Probably -- whether it's going to be stable for everyone is another story. If you're trying to reach the edges of the performance envelope, factors like the thermal properties of the case and the quality of the power supplied to the chip matter, and those vary from product to product.
[Nook Color Android Development] frankusb:
You may want to poll in one of the CM7 threads since anyone still running CM7 probably doesn't read this thread. Also keep in mind that on CM7, there was a utility to adjust voltages after boot. I used to under volt I think all the frequencies.

Frank
[Nook Color Android Development] pastordl:
Changed email client

Changed from ASOP email to K9 yesterday. So no longer an issue. Like K9 much better. Didn't get a chance to edit post.Thank you for trying to help.
[Nook Color Android Development] webyrd:
I am running fine at 1200, the voltage settings that I used on CM7 were those recommended in mr72's thread http://xdaforums.com/showthread.php?t=1443292, 1.325v @ 1200
[Nook Color Android Development] pastordl:
Voltage report on 7.2 for test kernel

Installed 7.2 and checked voltages, 1200mhz, @ 1.325v and at 1300, @ 1.375v. Hope this helps.
[Nook Color Android Development] Tom2112:
Sorry for the total n00b question, but how do I install the test kernel? Is it as simple as flashing the zip file like I would with a ROM?
[Nook Color Android Development] pastordl:
That's it

Yep, just like a ROM in recovery, (CWM or TWRP), i just overwrites the kernel.

:good:
[Nook Color Android Development] EAK128:
Yes, you can wipe cache and dalvik cache while you are in recovery, but you don't really have to.
[Nook Color Android Development] hliew88:
Test Kernel w/ Youtube

I've been really heavily using the test kernel since it's been out, and it's been so smooth, except for one problem that's really bugged me out.

I get some video tearing (don't care). HD videos on Youtube (only) just refuse to play for more than about 1 or 2 minutes before one of these scenarios happens:

1. Video freezes/goes black, audio still playing. If I kill Youtube and restart it, it will not play any video (HD or not). Only a reboot fixes this.

2. Nook crashes and hard reboots.

If I didn't use my Nook to watch so much Youtube, I would love to keep using the kernel... sometimes I forget to turn off HD and then I have to wait for it to reboot.

Otherwise no crashes, SOD's, anything! Great work! :D
[Nook Color Android Development] bigbob23:
If you later install a new nightly you will need to reinstall the test kernel. I update using the Cyandelta app, which can be configured to reinstall the kernel as part of the process. It also only needs to download the parts of the nightly which have changed.
[Nook Color Android Development] webyrd:
Still working very well for me over various CM nightlies and over tdm's Gummy ROM
[Nook Color Android Development] Mr-Glass:
Booted up the NC - has not been on since 10/7 - could not get internet access even though it shows I am connected to my router - the wifi icon is gray not blue - put the latest nightly on and same thing.. I know I have been spending more time with other devices, but am I missing something obvious here... Everything else I have is currently on wifi so I know that is not an issue.. hmmm

Edit**** Oh snap - the battery must have gone so dead that the date reverted back to before Android.. and the automatic time was not checked... set the time and everything eventually started working.. I have never seen that before...
[Nook Color Android Development] steven676:
Another new test kernel (3.0.101)

Here's another new kernel for everyone to test out. This one, like the last one, contains a large number of changes -- feedback is appreciated, particularly if you use zRAM on your device.

Changes since the last test kernel:

Updated to upstream (kernel.org) stable kernel 3.0.101, bringing in a huge number of bugfixes to core kernel code. (Upstream support for the 3.0-stable series terminates with the release of 3.0.101, so we're on our own from here on out.)

Reverted back to a 1.1 GHz max overclock due to the reported instability at 1.2 GHz. We'll have to look into ways of offering both of the overclocking steps (and why 1.2 GHz is less reliable on the newer kernels).

Reverted the refresh rate change and removed the hwcomposer module from the package -- the hwcomposer/dsscomp rendering paths don't seem to be stable for us just yet. We'll want to try this again at some point in the future.

Backported a huge number of bug fixes and performance improvements for the zRAM code from kernel.org kernels.

Backported the extra_free_kbytes feature from the Android kernel/common android-3.4 branch. (This won't actually do anything unless you run CM11/Android 4.4 or set the value yourself, but I'd like to get some testing for the changes to core code the patch introduces anyway.)

My aim is to push this to the NookieDevs and CyanogenMod repositories for inclusion in future nightlies next weekend, if testing doesn't uncover anything else.

For this kernel, I'm particularly interested in your experiences if you use zRAM -- does this kernel improve stability and/or multitasking performance?

Note that if you're coming from the previous test kernel, you should either reflash your base ROM, or do the following after flashing this update:

Remove /system/vendor/lib/hw/hwcomposer.omap3.so from your device.

Replace /system/etc/powervr.ini with https://raw.github.com/CyanogenMod/android_device_bn_encore/cm-10.2/etc/powervr.ini .

Source: kernel, wl12xx wifi modules.
[Nook Color Android Development] pastordl:
Another new test kernel (3.0.101)

Working great, seems smooth, no stability problems so far. Installed over 11/11, and using Z-ram @ default level. Runs best at 1000mhz,1100 is a little bit choppy running YouTube or Netflix.

Did need to install with signature verification off.
[Nook Color Android Development] webyrd:
No problems so far, also leaving zRam at default - this is over Gummy 10/31 nightly.

One thing, wifi icon is staying grey, not turning blue, even though wifi is working fine. This happened once before after a dirty flash, downloading latest CM nightly now, will update after clean install and a while on CM

Edit WiFi icon normal after clean install, all seems OK after an hours use