yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] racks11479:
Running much smoother on CM7v8. But XDA Free is still fc'ing on me. As well as Live Hold'em Poker unless I use a crappy hacked framework. :)

Looking forward to the next nightly. Thanks for the great work you guys are doing by the way. My nook is far more than what I would have ever wished for because of the great devs here.

Edit: forgot to mention that I was getting the "There is a problem parsing this package" error when trying to install some apps. This is before and after the patched framework. Same issue. Is it just me? Or is anyone else having this issue as well. Thanks.
[Nook Color Android Development] philburkhardt:
Yeah, you're right. My FC's are back too. Bummer :(

EDIT: No issues installing anything, so far.
[Nook Color Android Development] Narfx:
****, I forgot the latest market. With dpi=160 it doesn't show My apps. With >160, it works. So it's either >160, so all programs work but some of them use only 1/4th of the screen; or 160, so market 2.3.x, google maps 5.1.0 and some other programs fail miserably but those that work at least use all the screen. (edit) NVM, I uninstalled market updates, cleared cache and let market update again and I'm seeing My apps now. Don't know for how long though.

Hell, this bug is annoying. What where the google guys thinking when they implemented the retarded dpi setting? Is it so difficult to make everything work decently between a reasonable range of dpi values, as occurs in desktop OSs? Is it so difficult to program Maps, Reader or Market as dpi-independent programs? :confused:
[Nook Color Android Development] jkurl:
I am still on V6 for now. I have been to lazy to update and didn't want to here my wife ***** everytime something went wrong. I might put V8 on my nook today.
[Nook Color Android Development] diomark:
I'm actually finding 180 to be the best compromise on my nook.

-mark
[Nook Color Android Development] cosine83:
I flashed nightly 8 over nightly 5 and my market is no longer working. Any ideas? I tried clearing cache, data, and uninstall updates. No dice.
[Nook Color Android Development] bonobomidwest:
There's a post from dalingrin on this a few days ago, just after v8 was released if i remember correctly. You need to clear the cache for market app AND for the supporting service (sorry i'm blanking on the name of it right now).
[Nook Color Android Development] brashmadcap:
Google services framework
[Nook Color Android Development] combustiblemonkey:
Any word on nightly build delays? And anything we can do to help?
[Nook Color Android Development] tominabox1:
They are due to the wimax updates, no builds are making it through completely on any device. Would be nicer if we could see the buildbot process, but we can't anymore since they moved to a new bot. For now, we're just in the dark as to when/what is going on back there.
[Nook Color Android Development] newellj79:
bummer. as lame as it sounds, for a few days i couldn't wait to get out of bed so i could download and flash the latest nightly. if the wife asked if i could get up with the baby, no problem. :)
[Nook Color Android Development] fattire:
If you have to have your fix, you could always build from source. :) The newest build actually has a lot of new stuff from upstream-- gb 2.3.3... That's right... get ready for a new Airplane Mode icon!!!!! w00t!!!
[Nook Color Android Development] tj!2k7:
Thanks CM devs for all your hard work!

So, um yeah, about that... I was wondering if there might be a fairly simple way to disable the Airplane Mode icon, as well as the (No Service) text in the notification section? Thanks!
[Nook Color Android Development] newellj79:
Unfortunately that's a little over my head. I'm looking into taking some programming classes though. :)
[Nook Color Android Development] digitalslacker:
I didn't know you could do that...and there goes my afternoon!
[Nook Color Android Development] lucifurious:
Is it possible to set your IMEI to a valid one? Like my phone's?
[Nook Color Android Development] Narfx:
You don't have to know programming to compile something ;)

BTW, is gcc 4.5 supported? Everything seems to work ok with GRI40 but RomManager (force closes at boot). I wonder if I should emerge gcc 4.3 or it's a known bug. (edit) NVM, some leftover from the previous ROM. It works now.

(edit) Wait, the music player doesn't detect my files either.

Anyway, I don't know if it's 2.3.3 or what, but it feels awesomely snappy. I think I'll build from source from now on :D
[Nook Color Android Development] combustiblemonkey:
loading now... Will share if it doesnt blow my Nook up :)

edit: github keeps hanging up on me :(
[Nook Color Android Development] philburkhardt:
There will be. It has been stated that they are not working on this type of modification yet. Probably not until CM7 out of the nightly stage.
[Nook Color Android Development] burbank:
Installed CM7 Nightly v11 on top of v8. Wiped cache. Changed LCD Density to 168.33333.

Market works great. (Including My apps.)

Quadrant Advanced still stops at the H.264 benchmarking.

YouTube app launches but won't play video.

Every other app I tested seems to work great! Dev's are making good progress! Thank you!
[Nook Color Android Development] newellj79:
What program r u using to change LCD density. I've tried 2 but I can't change it past a whole number.
[Nook Color Android Development] tnpapadakos:
try this:

http://xdaforums.com/showpost.php?p=7850938&postcount=1

havent tried it, but looks good
[Nook Color Android Development] burbank:
I just edit the file. It's a text file. Use something like Root Explorer and edit the file "build.prop". Look for the line "ro.sf.lcd_density=160" and change it to "ro.sf.lcd_density=168.33333". Reboot. Done.
[Nook Color Android Development] bonobomidwest:
Presuming this is a typo, but the value is 169.33333, not 168... just in case you're having issues
[Nook Color Android Development] newellj79:
For me 161 is working great.
[Nook Color Android Development] Snyperx:
I am not able to pull any logs here at work, but I thought I would mention that even with the LCD density set to 161 I am still getting scaling issues in some of the programs.

* Mint Personal Finance

* Google Reader

* Engadget
[Nook Color Android Development] tj!2k7:
Vol +/- Key Intercept for added Menu/Back functionality

I was hoping CM folks might be able to take a look at this suggestion for inclusion into the CM7 ROM. I know there are a lot more pressing issues, but think this would go a long way towards the overall usability of the nook:

[IDEA] Vol +/- Key Intercept for added Menu/Back functionality

Not sure if this is the correct way or place to post in order to catch the attention of devs, but if there's a better or more appropriate place I should pose this question, let me know.

Thanks.
[Nook Color Android Development] RoboRay:
Since holding the Menu and Back keys are important functions, how would that work with this?

I think the usual method of simply remapping the hard buttons to Back and Menu and adding a widget for soft volume buttons is a superior solution.

If they were combined, the first thing I would do would be ask how to revert the change.
[Nook Color Android Development] tj!2k7:
I see it as being similar to the concept CM6 employs at the lockscreen when music is playing, where briefly pressing a volume button modifies volume, pressing and holding volume button skips track forward/backward.
[Nook Color Android Development] lafester:
i don't like this idea at all. keep the keys as they are please :)

i would absolutely love a key mapping app though.
[Nook Color Android Development] RoboRay:
Yeah, but how would it handle pressing and holding for the long-press Menu to open the recent apps list and long-press Back to kill the current task?

That's THREE functions that would need to be combined on each of those buttons, not just two.
[Nook Color Android Development] tj!2k7:
I understand where you're coming from, however, long pressing the nook/home key brings up recent tasks, so that appears to be redundant functionality.

As far as long-holding back to kill the current task is concerned, that would be a trade-off for such an option, however, speaking from my personal experience, quick and easy access to both volume and menu/back would be used more often than the need to kill a task (for which instances for me are few and far between) - I pretty much always use a task manager for those occasions anyway. I could definitely live with that.

But I do get your drift. Nevertheless, it would be fantastic to see this as an option. Better? =)
[Nook Color Android Development] RoboRay:
Oops, I mispoke... Long press Menu opens and closes the keyboard.

I could certainly see your suggestion being a useful option, but feel the default behavior should remain as is.
[Nook Color Android Development] EpicFail236:
Check my sig, I posted an apk update that should let you set the volume buttons as whatever you want. It sadly requires a restart before a remap can occur, but I'm hoping to find a way around that.

It would be nice to be able to set both short and long presses for buttons to be whatever we want. If you find any more leads on this, let me know, I'm willing to devote some free dev time at some point or other. Never hurts to try. :D
[Nook Color Android Development] lafester:
yes with only 4 keys it would be very nice to have multiple options for each key.

ae button plus for winmo had single, double, triple AND long press options which was crazy.
[Nook Color Android Development] hoban_eris:
Nightlies 11 and 12 have been released. Things seem to be on track again for the most part.
[Nook Color Android Development] woolmonkey:
Does anybody know why the nightlies are delayed again.
[Nook Color Android Development] Backwardsblade:
I compiled one yesterday and the top bar seemed glitchy, might be ironing some issues out.
[Nook Color Android Development] tgwaste:
these have been out for days. wheres 13?
[Nook Color Android Development] tony1208:
anyone get snes emulators working on cm7?? cant load on my nook
[Nook Color Android Development] taylor.fowler:
According to attn1 in the Aria Forums, the build bot is down. They're working on getting it back online, but right now none of the devices have been updated in a couple days.

Edit: Link tto post
[Nook Color Android Development] tgwaste:
Yes snes works fine for me on nook running cm7 12. Try uninstall then reinstall.
[Nook Color Android Development] newellj79:
Does it run smooth? I'm thinking of buying it.
[Nook Color Android Development] tgwaste:
if you're referring to the yongzh version, then yes it runs amazing. buy it. also the buy the n64 emulator.

keep in mind I run my nook @ 1.1ghz though.
[Nook Color Android Development] newellj79:
yongzh version? I'm at 1.1 too. I meant the n64 emulator.thanks.
[Nook Color Android Development] tgwaste:
Only download emulators by yongzh.
[Nook Color Android Development] tgwaste:
looks like 13 is up. anyone got a changelog?
[Nook Color Android Development] timekeeper:
http://review.cyanogenmod.com/#q,status:merged+project:CyanogenMod/android_device_bn_encore,n,z
[Nook Color Android Development] igor.tonky:
i'm developing a tool to track nightlies, you can check out the beta: http://cm-nightlies.appspot.com/?device=encore

as you may guessed i own dhd and nook :) but i plan to add more cm devices and improve on this, eventually.
[Nook Color Android Development] Narfx:
Nice :-)...
[Nook Color Android Development] painter_:
Thanks, This is really cool. I tried to change the url to look at the heroc but no love. I really look forward to this being available to other devices as well.
[Nook Color Android Development] siraltus:
Aldiko is FCing on the last two builds - anyone has this happening?
[Nook Color Android Development] Bimboy:
On v12 with perfectly working Aldiko. I find the app easily gets corrupted when doing upgrades, even with my phone. Uninstall/reinstall Aldiko usually works.
[Nook Color Android Development] burbank:
Thanks for doing this. It's really nice.
[Nook Color Android Development] phiredrop:
+1 Thanks for this.
[Nook Color Android Development] will75:
Any news on bluetooth front? Cm7 + Wei controller + nook = win
[Nook Color Android Development] wpnyc2009:
Downloading #13 right now

Thanks for all the hard work.

Great job m8s!
[Nook Color Android Development] Snyperx:
igor,

Just tried your link in Firefox and IE and it displays nothing. Are you working on the app by chance?
[Nook Color Android Development] racks11479:
I've just tried this and I am stuck at the "ANDROID _"

Can't seem to get pass this part. Any help or suggestions to point me in the right direction would be grateful.

Thanks,

Racks

EDIT: I even unpacked the uRamdisk and checked the init.encore.rc and the changes were made accordingly.

# mount partitions

mount vfat /dev/block/mmcblk0p2 /rom sync noatime nodiratime uid=1000,gid=1000,fmask=117,dmask=007

mount ext4 /dev/block/mmcblk1p2 /system wait ro barrier=1

mount ext4 /dev/block/mmcblk1p3 /data wait noatime nosuid nodev barrier=1

mount ext4 /dev/block/mmcblk1p5 /cache wait noatime nosuid nodev barrier=1

Any other code it need to edit to get this working?
[Nook Color Android Development] fattire:
Can you pastebin how far it got in adb logcat?

Also are the partitions on your sdcard ext4?
[Nook Color Android Development] racks11479:
So sorry I took up your time. Thank you for pointing out the obvious.

"Also are the partitions on your sdcard ext4?"

Totally went super newb on myself and forgot about that. I apologize.

And thank you, gonna try it out tonight.

-Racks
[Nook Color Android Development] fattire:
Heh. Sometimes it's the most obvious thing. ;)
[Nook Color Android Development] Snyperx:
I just uploaded my first logcat log. Not sure if it helps any of the devs, but here is the link.

http://pastebin.com/AR8bdZ6C
[Nook Color Android Development] rulevoid:
Is there a way to force show at all times the notification bar? I use apps that dont have a way to get into the options without a physical button, so finding a way to lock the notification bar as shown would allow me to use the options button and back button.

Anyone? Thanks!

Sorry I would delete if I could. Moving post to USER thread.
[Nook Color Android Development] fattire:
Why are you uploading it?

And what's "juicedefender"?
[Nook Color Android Development] fattire:
Try the app called "Button Savior".
[Nook Color Android Development] timekeeper:
An app that supposedly helps you preserve battery life through selectively disabling things like wifi, and gps, and background processes.
[Nook Color Android Development] dalingrin:
No news isn't always bad news..... ;)
[Nook Color Android Development] pavlos46:
Hey thanks for all v14 is really good and fast even YouTube on flash works on full screen at 340p. Amazing work I believe its the most complete cm7 so far.

Three things missing BT, Sleep and DPI and we are on heaven.

Keep it up fellas.
[Nook Color Android Development] shad0wf0x:
I have no problems with mounting the sdcard via usb on both windows and linux. I do have a problem using adb in windows, it works fine in linux. Windows tries to find a driver for it when plugged in but cannot. This problem has been going on since you guys got the sdcard/usb fix way back when. I have the same problem when booted in cwm. mount usb storage works fine, but adb devices shows no devices found. Again this problem is only in windows, in linux it works fine.

Somehow CM7 has a different device id or something than any of the other builds, nookie froyo, stock 1.0-1.01, all work fine on this windows machine, also stock cwm from rom manager doesn't have this problem.
[Nook Color Android Development] eNkrypt:
Here is a mirror for those of you who do not want to wait:

http://r00tyou.com/android/nook/cyanogenmod/update-cm-7.0.0-RC1-encore-KANG-signed.zip
[Nook Color Android Development] nullexe:
I've noticed I can't connect to my D-Link DIR-655 (g/n) wireless network with cm. I done all the usual troubleshooting, but still no luck.

I am able to connect to regular wireless g networks, I've tested with a dd-wrt and the using an N1 as an access point.

I took a logcat and noticed that it's associating with the AP just fine but looks like it's timing out. Has anyone else had the same problem?

Now for the praise: I love having CM7 on the nook. I've been waiting for this for a while, keep up the great work!
[Nook Color Android Development] faceman66:
I second this, my Win7.64 does not see the device at all, but I can mount USB storage. So SUB mounting is good, but ADB is not.

Go into your router and try disabling N and just running as G. And then try the reverse, disable G and just run N. Either of those should work, I had a similiar problem with my CM6.1 G1 phone and I had to pick one or the other, having a 'mix' caused my phone issues.

UPDATE:

I just flashed the nightly (http://mirror.teamdouche.net/?device=encore) and noticed I was back to a stock kernel, reflashed the oc kernel from dalingrin (1100 for CM7).

Seems to boot fine, but I have noticed that on the first build my CPU usage would be at 100% constantly after I installed SetCPU. I removed SetCPU and it would return to normal variations of usage depending on activity.

I flashed the nightly, then reflashed the 1.1 oc kernel, reinstalled SetCPU and configured main settings to OnDemand and 1100-300, set on boot. Rebooted.

Seems all is ok, so I set up my profiles:

Screen Off - 300max/300min - 90% Priority

Charging - 1100max/300min - 80% Priority

Battery < 15% - 300max/300min - 70% Priority

Battery < 25% - 600max/300min - 60% Priority

Battery < 50% - 800max/300min - 50% Priority

Enabled and Notifications on. Rebooted.

CPU utilization pegged at 100%. I changed my screen timeout to 30 and let sit for 15 just to give system a chance to settle in, no change. When I opened SetCPU to disable profiles it FC. But the CPU utilization released from 100%.

Something is not playing nice with profiles and the kernel.
[Nook Color Android Development] inxaos:
I'm unable to download Touchdown Exchange from the marketplace. It shows up, but it says "The request item could not be found."
[Nook Color Android Development] painter_:
Flashed from the unoffical one posted yesterday to the nightly today. Live wallpapers are not listed.
[Nook Color Android Development] RileyGrant:
Can we flash the nightly via rom manager?
[Nook Color Android Development] painter_:
Logically the answer would be no. Since to flash this you need Clockworx 3.0.0.6 and Rom manager only will install ver. 3.0.0.5.

Also this is in the release post.
[Nook Color Android Development] faceman66:
Disregard, I moved this post to Users, I hit up the wrong thread. Sorry.
[Nook Color Android Development] dalingrin:
I've noticed the same. I am looking into the issue but its admittedly fairly low priority atm.
[Nook Color Android Development] bdcrim:
Tried and it is a no go. OP says so for a reason.
[Nook Color Android Development] dalingrin:
THIS IS AN OLD BUILD!

Do not download from this mirror. If your md5 does not match the one in the first post then you have an old build.
[Nook Color Android Development] faceman66:
Installing your new zip over the nightly now, your OP doesn't mention and I can't remember from my G1 days, do I need to wipe before installing the new zip or can I do this like a nightly and just flash over top without wipe/format, etc?
[Nook Color Android Development] Instant Gravy:
USB storage mounts fine here (installed from zip linked to in OP, mounted on macbook 10.6) with dalingrin's 1.1ghz oc kernel installed. Aside from Market limitations and a slight screen flicker at higher brightness levels the RC1 is running pretty damn smoothly. Good work CM team!
[Nook Color Android Development] faceman66:
Follow up:

Latest build working great.

I was able to mount USB still with ease.

I am still NOT able to see device via ADB.

I was able to use built in ROM Manager to boot into recovery and flash the OC kernel no problem.

Seeing same CPU issues when profiles are active.

!! Interesting, once I rebooted after flashing OC kernel - device is listed in ADB

I also noticed that when I go to the online Market (market.android.com) my device is now shown with good device name, but it is not compatible with ANY app I try to install from the web. So something is missing there still.

However, doing an app search from the Market App, most things are showing up now.
[Nook Color Android Development] Chahk:
Removing telephony components

I noticed that Cell Standby is eating most of the battery power. In nookiefroyo you could fix this by removing TelephonyProvider.apk and Phone.apk from /system/app/ directory. Would it be safe to do the same on CM7, or are there services that rely on these components?
[Nook Color Android Development] painter_:
I thought that it was proven to be the placebo effect.
[Nook Color Android Development] Chahk:
For whatever reason, the PID for NOOKcolor has changed from "0002" to "0003" for these builds. Easy fix:

Locate the drivers you used to install NookColor originally (or download a fresh copy.)

Open the file "android_winusb.inf" in a text editor (I recommend Notepad++).

Find every line containing "VID_2080", and on that same line change "PID_0002" to "PID_0003".

Save and close the file.

Right-click My Computer, click "Manage" and go to Device Manager.

Connect NC via USB, and click the "Scan for hardware changes" button.

Right-click on the "NookColor" device (should have an exclamation mark next to it) and select "Update Driver" option.

Navigate to the folder with modified android_winusb.inf file and click "Next". Drivers should now properly install.

Open Command Prompt and type "adb kill-server" and press Enter.

Type "adb devices", press Enter, and it should now find your NC.
[Nook Color Android Development] dalingrin:
I need some folks to test this kernel with CM7 to see if this fixes adb in windows while still letting you mount sd card as it should.

http://www.multiupload.com/EQMM97OW4P
[Nook Color Android Development] 10equals2:
Torrent

Hey, I hate multiupload. Here's a torrent.

This is my first time making one, so if anyone wants to use it, be sure to tell me if it

doesn't work right.

well, give me a minute...

http://thepiratebay.org/torrent/6187468
[Nook Color Android Development] will75:
Still rocking froyo.will update soon I think
[Nook Color Android Development] wpnyc2009:
having issues flashing into v14....

I have Rom Manager 3.0.1.2 & CWR 3.0.0.6. When I downloaded v14 and tried to flash from RM it just keeps booting normally. I have my boot disk with which I'll flash v14 and re-flash Dalingrin's OC so I'm no concerned but is this 'normal?' Or have I done something that needs correcting?

Thanks m8s!

edit: I used the boot disk method. Got it rocking v14.

re: Pavlos46 - v14 is really good and fast even YouTube on flash works on full screen at 340p. Amazing work I believe its the most complete cm7 so far. How so? Do you mean using Dolphin and Youtube desktop? Did this way! Wow its cookin'!!!
[Nook Color Android Development] tominabox1:
you should flash cwr 3.0.1.0. go to Rom Manager and hit flash recovery and select "Nook Color" (NOT "Nook Color (old)")
[Nook Color Android Development] Narfx:
You don't need Dolphin. The stock browser also has a working youtube.