yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] joenathane:
Some eye catching changes in CM7 as of late,

Not entirely sure if these changes are what I think they are... hardware acceleration in Gingerbread?

http://review.cyanogenmod.com/6831

http://review.cyanogenmod.com/7062

And an update to the Nook kernel, from Dalingrins twitter it seems it may only be one change having to do with USB support...

http://review.cyanogenmod.com/6995

any thoughts?
[Nook Color Android Development] newellj79:
Hmmm. If a new nighty doesn't come out tonight with the kernel update I will build in the morning and see if I notice a difference.

Edit... couldn't wait, building now. Truth be told though, development has come so far that most of the time, if it isn't a UI change, I can't even tell.
[Nook Color Android Development] dalingrin:
We are in the middle of merging OMAPZoom framework changes primarily for OMAP4 device support(3D, new DSP, etc) but much of it affects the Nook as well. Media playback should improve somewhat for the Nook. Thus far I have new DSP codecs working but the overlay still needs some work.

The kernel commit that was finally merged is just some kernel clean up to eliminate possible causes of instability and SOD. No new features yet.

My 1st priority is to get the OMAPZoom framework changes merged because it affects multiple devices. After that I will focus back on the kernel hopefully figure out SoD and such.

Longer term, TI has been working on an OMAP3 2.6.35 kernel finally and I would like to look into that for the Nook down the road.
[Nook Color Android Development] newellj79:
Just curious, I just built and it came out at 99.67mb, almost 2mb smaller than n149. Everything is working fine though. I did copy proprietary files before syncing too.
[Nook Color Android Development] joenathane:
Thank for the update, and for your efforts, great to know development is charging right ahead.

With such great developers the Cyanogen Nook community has and all the progress, it makes me wonder what exactly the hell these big companies and their developers are doing to release such crappy, featureless, bug ridden "ROMs". With my tech work I'm always helping my customers setup and configure their phones, which has thoroughly convinced me never to buy a phone or tablet that doesn't have the Cyanogen 7 Mod and a good community with good devs. Even most flagship phones have major issues with the stock software, which customers are lucky if it only takes half a year for the company to fix or if they even fix at all. It is astounding what a few talented and dedicated developers can accomplish.

Anyway that's just a really long way to say thank you!
[Nook Color Android Development] SeaFractor:
Thank you for your diligent efforts dalingrin!

Also thanks to the rest of you how have been working hard on different Nook developments. Love those themes joenathane!
[Nook Color Android Development] patruns:
Good point, certainly one many are asking. One thing this development community has that the big companies don't is a ton of dedicated end users testing it every step of the way with fixes and improvements almost daily. If you are a big company, you don't want to and can't afford the frequency of updates that we see here, so you have to get it right the first time and limit your fixes/updates. Kudos to all the developers and users here, but let's not forget we have resources that the big guys do not. :cool:
[Nook Color Android Development] joenathane:
Beta testers come free, I'm using Firefox 8.0 alpha1 as my primary browser just to illustrate and have participated in beta testing Windows Vista and Windows 7; As far as employing developers, the "upline" Cyanogen Mod team is made up of around 10 members plus about 5 maintainers for the Nook. I'd imagine that about 5-6 full time employed developers could handle that workload(someone correct me if I'm wrong) at about $90,000 a year per developer, that's about half a million a year for a team. B&N 2010 revenue was 6.92 billion dollars just for example, I think they can afford a few full time developers, not to mention the much bigger companies like Samsung and Motorola.

Even with that said, Google does a good deal of the work, it seems companies must spend more time stripping out the features Google includes in AOSP than implementing useful features...

Maybe I'm missing something, but it seems to me that these companies could be doing a much better job with their Android ports, considering what some hobbyist and skilled developers produce in their free time...
[Nook Color Android Development] dalingrin:
One thing that I think the big OEMs need to change is how they organize their device development. If you look at how CM works, it is one source for all devices. All devices use the same branch. Instead of hacking up the Android framework to get feature X to work on device Y, we make it work in a device agnostic way. This is something that Samsung and others don't seem to always do. They have separate trees/branches for even the same devices(all the galaxy S variants). The end result is a mess and it makes it much more difficult to get timely updates to your devices. Additionally, some random person may decide to contribute a new feature to Android and with very little effort all CM devices reap the benefits(such as the recent boot speed up). Fixing problems at the device level can be more difficult than hacking the framework in the short term but in the long term it makes maintaining and improving Android much easier.

I haven't been a part of CM for that long but I am definitely proud of how a small group of folks that work on something part time have been able to achieve what they have. While it can be aggravating that CyanogenMod gets kanged so much with little or no credit, I guess its better than no one wanting your work.
[Nook Color Android Development] DigitalMD:
Really for OEMs its more that they can never catch up and don't really have to. Hardware capability always outstrips software by months or years. Every 6 months or less, Apple, Samsung, etc. have a new generation of hardware that their in house developers have to get the hardware abstraction layer working for so they tend to push out buggy software just to stay ahead of the competition in time to market. They know people will buy hardware with new features even if the software lags and hopefully they or third party developers will kind of catch up, but after a few month the OEMs can't be bothered, they are off to sell the next new toy.
[Nook Color Android Development] chisleu:
I need more bandwidth.
[Nook Color Android Development] chisleu:
When trying to copy the proprietary files from my NC... Any ideas what I've done?
[Nook Color Android Development] Nburnes:
You have adb set up right?
[Nook Color Android Development] newellj79:
Sounds like adb is not setup correctly. Does adb devices show your NC serial number?
[Nook Color Android Development] jeremyshaw:
As someone on the paying end of a Florida based business... 90k salary is roughly 170k or so paid out on my end. Iirc, b n isn't doing well, and has been looking for a merger/buyer for a while. For a product line that may barely make 10-20% more than is/was being invested into it, and it's upkeep (RMA, user/employee training, returned units because of slow GUI...), hiring even a small dev team might be a pinch more pricey than possible. As for making sure everything works... well, that's another issue, but I don't know much about that side of product development (from the dev side).

Btw, to the people upstream of me, making the OS, and maintaining it for finicky end users like myself, thank you very, VERY much!

P.s. typing this post in the stock os versions... impossible. CM7 = rocks.

I'll stop polluting your dev channel now.
[Nook Color Android Development] chisleu:
Nope. When my phone is plugged in it will say:

When the tablet is plugged in it says

I'm not sure. I'll double check the steps right now and be sure I didn't miss something. I didn't see a step to put it into the path in the wiki, and with the latest version of ubuntu, I had to install a package that wasn't mentioned to get adb to work at all. Otherwise it would act like there wasn't an executable there.

OT, but I dislike the way linux has gone. I ran slackware exclusively for many years. from version 2.x->7.x. I remember when 2.0 kernel came out! :)

It used to be a pain to ./configure;make;make install and figure out dependencies myself, sure, but at least everything worked! :)

EDIT: I don't need the sun java 6 sdk or whatever installed to use adb do I? I don't have it installed yet because I can't get it from the repo for some reason.
[Nook Color Android Development] Nburnes:
This should help. http://nookdevs.com/NookColor_USB_ADB
[Nook Color Android Development] chisleu:
I don't have a "/etc/udev/rules.d/50-android.rules"

I also don't have su yet... sudo my buttcrack...

EDIT: I added it to the file I have there (70 something) and now I don't get a permissions error, but when I plug in my phone it does the same as the tablet, just having an empty list of devices.

EDIT: If I close the term and open another, it goes back to saying no permissions.
[Nook Color Android Development] newellj79:
U need to make the android rules. Unfortunately the guide did not solve it for me. Eventually a Google search did. If u don't get it figured out I can email u a couple files that u can replace and it should b good to go.
[Nook Color Android Development] joenathane:
Thought this warranted a mention here given our previous discussions http://gadgetu.net/cyanogenmod-ringleader-now-working-with-samsung-mobile/#more

Steve Kondik, CyanogenMod creator has been hired by Samsung Mobile, which is exciting news to say the least, I wonder if this will having any bearing on the future of CyanogenMod....\

Combined with the news of Googles plans to acquire Motorola makes me not sure of what Android device manufacturer will have the best stock firmware...
[Nook Color Android Development] swaaye:
It likely means he's done with CM due to a Samsung NDA.
[Nook Color Android Development] Nburnes:
Negative.
[Nook Color Android Development] swaaye:
That just sounds like Samsung unsurprisingly wants nothing to do with Cyanogenmod. Or that he's not working on Android software over there. Who knows. But if he is working on their Android builds then it could become a conflict of interest if he works on CM.

I'm not too worried about CM going anywhere though as long as there are Android devices with people who want to run alternative OSs.
[Nook Color Android Development] malisha1:
I just installed a fresh copy of the nightly CM7 and now i'm unable to install flash or maps and other apps
[Nook Color Android Development] Colchiro:
settings... applications.... find market and uninstall updates.
[Nook Color Android Development] khaytsus:
And that does absolutely nothing, the actual filtering is on Google's side.

http://xdaforums.com/showthread.php?t=1196417
[Nook Color Android Development] patruns:
Not true. Only partial filtering being done by Google. Your link involving the LCD density change is for using the new market. Going back to original market will allow searches to find apps with download buttons. I am running old market now and updated YouTube, Flash and Facebook with it. They don't show up in "my apps" but you can still download them.
[Nook Color Android Development] ianPhillips1:
Still using the titanium freeze(market updater) ,and I have no issues in market, everything updates fine and I have updated numerous nightlies.

sent from my secret pocket machine
[Nook Color Android Development] patruns:
Are you including the Google apps pack with the nightly updates? If so that is nice to know that the Titanium freeze stays put even though a new updater is installed. I have to go back and uninstall the update app every time I do a nightly update....
[Nook Color Android Development] ianPhillips1:
I flash gapps right after a nightly update, and market stays the same.

sent from my secret pocket machine
[Nook Color Android Development] Ronin3178:
I haven't flashed gapps in months, with every nightly I only flash that and wipe cache / davlik. No problems yet, I froze market updater with TB like a month or so ago.
[Nook Color Android Development] acme2ajax:
CM7 to NC emmc is, well, improper

Hi,

I brought a new nook color (the blue dot version) and wanted to install cm7 to emmc.

I created a CWM card (3.0.1.0) and put in the cm7 175 full file from the nightly links. and, i aslo put in the gapps zip.

Then, i went to install zip from sd card and installed both....and then i rebooted....

Now, here's where the fun begins....

The system booted directly to the home screen...no lockscreen, no tablet tweaks status bar.

I went to cyanogen mod settings, but the damn thing force closes whenever i click on it...cyanogen mod settings is out of access to me.

SO now, I want to know what has gone wrong?

What could be the possible steps to fix this? Either some workaround or to flash to stock nook color completely...need ideas....

Any help will be appreciated.....

Thanks.....
[Nook Color Android Development] newellj79:
Did u fix the partitions first? On the blue dot version there is some repartitioning needed before cm7 install. If not, ill dig up the link and post it in a bit.
[Nook Color Android Development] acme2ajax:
No...I did not fix the partitions. Installed the CM7 directly.....Is this what has caused the problem?

So now, do i need to repartition the nook and then install cm7?

I think this is the link for the repartition process..

http://xdaforums.com/showthread.php?t=914690
[Nook Color Android Development] newellj79:
No it isn't. This is the link for one way. Its not the way I did it but still looks good. What u posted is for returning to stock. Good luck. As long as u can get into cwm u should b fine.

http://xdaforums.com/showthread.php?t=1094371
[Nook Color Android Development] acme2ajax:
Great....

Will try this and see what happens.....

Thyanks for your help....
[Nook Color Android Development] khaytsus:
THIS is your problem. You have a horribly old CWM.

http://xdaforums.com/showthread.php?t=1030227
[Nook Color Android Development] patruns:
You used an older version of CWR. Go here and do it again: http://mrm3.net/nook-color-how-to-install-cyanogenmod-nightlies/

Make sure you use version 3.2.0.1 of CWR.
[Nook Color Android Development] newellj79:
Can someone try to repo sync cm7. I've been trying to all afternoon and I get a connection error/connection refused. Thanks.

note... i posted similarly in cm7 users earlier but got no response. Maybe it's more appropriate here.

Edit... 5 hours later still no dice. Can somebody PLEASE verify its not something on my end.
[Nook Color Android Development] dalingrin:
If its kernel.org then its not on your end. Kernel.org was "compromised"
[Nook Color Android Development] newellj79:
Sure was. Thanks dal.
[Nook Color Android Development] newellj79:
Two and a half days and I still can't repo sync. I can't connect to kernel.org. Daligrin said they were having "problems". Anybody know when they will be back online?
[Nook Color Android Development] bigbob23:
From http://kernel.org:

What happened?

Intruders gained root access on the server Hera. We believe they may have gained this access via a compromised user credential; how they managed to exploit that to root access is currently unknown and is being investigated.

Files belonging to ssh (openssh, openssh-server and openssh-clients) were modified and running live.

A trojan startup file was added to the system start up scripts

User interactions were logged, as well as some exploit code. We have retained this for now.

Trojan initially discovered due to the Xnest /dev/mem error message w/o Xnest installed; have been seen on other systems. It is unclear if systems that exhibit this message are susceptible, compromised or not. If developers see this, and you don't have Xnest installed, please investigate.

It *appears* that 3.1-rc2 might have blocked the exploit injector, we don't know if this is intentional or a side affect of another bugfix or change.

What Has Been Done so far:

We have currently taken boxes off line to do a backup and are in the process of doing complete reinstalls.

We have notified authorities in the United States and in Europe to assist with the investigation

We will be doing a full reinstall on all boxes on kernel.org

We are in the process of doing an analysis on the code within git, and the tarballs to confirm that nothing has been modified
[Nook Color Android Development] paleh0rse:
Thanks for the info. What was the initial date of the compromise?
[Nook Color Android Development] dalingrin:
just run "reposync -f" to get passed the sync error
[Nook Color Android Development] newellj79:
I tried to repo sync using -f like dal suggested. That is to by pass the kernel.org issues. I end up with this. Does anyone have any ideas?

Creating filesystem with parameters:

Size: 461942784

Block size: 4096

Blocks per group: 32768

Inodes per group: 7049

Inode size: 256

Journal blocks: 1762

Label:

Blocks: 112779

Block groups: 4

Reserved block group size: 31

critical error: make_directory: internal error: dentry for zcat ends at 4108, past 4096

make: *** [out/target/product/encore/obj/PACKAGING/systemimage_intermediates/system.img] Error 4

newellj79@ubuntu:~/android/system$
[Nook Color Android Development] rhester72:
Sounds like you want to consider a (local) fsck...

Rodney
[Nook Color Android Development] saulhaul:
Might be a day late dollar short with this but.. I had the same issue when I didn't format the data and system before flashing the CM7 nightly.

Just an idea.
[Nook Color Android Development] newellj79:
I posted a thread in Q&A called help building cm7. I had things running fine and it screwed it up. Please see my post there is you know what your doing. I would really appreciate it. Thanks guys!
[Nook Color Android Development] Sincitybronze:
I posted this in the general thread but perhaps this is a better location for it. Any possibility of seeing the new e-mail apk for CM7? This might help with wakelock problems.

http://xdaforums.com/showthread.php?t=1253583
[Nook Color Android Development] sisterchick:
Anyone heard an update on progess?
[Nook Color Android Development] newellj79:
Nope. I check everyday. I'm anxious to build with the new commits.
[Nook Color Android Development] bigbob23:
Unless there is a need to use a kernel later than 2.6.32 (I think the latest is 3.0 or later), is kernel.org git access necessary to prepare a new nightly?
[Nook Color Android Development] newellj79:
Yes. Dal posted a work around for me a few pages back but I had bad results. So I guess no, if you can get it to work. I think it was: repo sync -f
[Nook Color Android Development] dealmaster00:
So there are no new nightlies since Aug 31 because of kernel.org going down, correct?
[Nook Color Android Development] newellj79:
Exactly.

10char
[Nook Color Android Development] Nburnes:
kernel.org needs to be up. I need my flashing fix. Can't even set up my dev box again without it >.<
[Nook Color Android Development] traumadog:
Anyone able to update to 197?
[Nook Color Android Development] bigbob23:
I updated this morning via ROM Manager. So far, so good.
[Nook Color Android Development] Colchiro:
I upgraded over #177 and very pleased. #177 seemed a little laggy, but #197 is speedy. :D
[Nook Color Android Development] bhundven:
I just watch lkml. here is the latest:

http://lwn.net/Articles/460376/
[Nook Color Android Development] newellj79:
thanx for the update. someone had posted a link for a work a alternative way to install the repository but it didn't work. I wait patiently.
[Nook Color Android Development] dalingrin:
Thanks for the tip. Ill test and submit.

There are a couple of reasons the Nook will be slower:

1 - the nook has a higher resolution display as you noted. This is exasperated by the fact pre-honeycomb, Android doesn't use much acceleration for 2d functions. This means the majority of pixel crunching is done sequentially by the CPU. Sequential processing does not scale nearly as well as a parallel processor like a GPU.

2 - CM7's theme engine hates tablets. The theme engine kills scrolling performance because the garbage collector is constantly trying to reclaim memory. Since we have only 1 CPU, the garbage collector is interrupting the CPU which we perceive has "hitching" or slow fps. Fortunately, the theme engine doesn't affect everything. The browser performance is as good or better than froyo or eclair. It really only affects lists and even then not all. I've reported this bug but I don't expect it to be fixed before honeycomb source drops.
[Nook Color Android Development] Narfx:
Yep. 169 is the "truest" one to the device size and resolution, but IMHO 160 is much better until all the apps fill the screen as they should (right now, with 169 or any other value greater than 160, google reader and three or four other of my installed apps are a tiny square surrounded by blackness).

Especially since we can installl google maps 5.0.0, which works perfectly fine with 160 dpi.
[Nook Color Android Development] Narfx:
Ouch :(. Well, hopefully with the xoom out it won't be long until honeycomb source goes to AOSP :)
[Nook Color Android Development] diomark:
My wifi is still not working when configured with AES cipher under nightly 8. (works w/ tkip cipher)

-mark
[Nook Color Android Development] ericman77:
Browser has dead spots when scrolling. If I slowly slide from top to bottom it scrolls and stops then scrolls again adout 1/2" spaces in between all the way down.

Never mind that forgot it dose that when I have the charger plugged in.
[Nook Color Android Development] dtownsend:
Still no My Apps in Market for me (this is with a fresh install of nightly 8).

Also I noticed a fix earlier in the week for live wallpapers but they still don't seem to be present for me.
[Nook Color Android Development] tominabox1:
You can grab the livewallpaper picker from another CM7 rom and install it like normal
[Nook Color Android Development] bonobomidwest:
Sure thing.

1. I used root explorer to edit build.prop directly

2. navigate to system

3. set system r/w

4. long press on build.prop and then open with text editor

5. Find the line "ro.sf.lcd_density=160"

6. and edit it to read "ro.sf.lcd_density=169.33333" (no quotes)

7. Save and exit (root explorer nicely saves the original file as a backup for you)

8. reboot

I have confirmed this works with maps, google earth, nook, kindle, and ezpdf, and google reader

here is the link to the notion that 169.33333 is the default:

http://xdaforums.com/showthread.php?t=889951
[Nook Color Android Development] bonobomidwest:
Dude, If I've actually found soemthing that helps you out, then that makes my week! :) Thanks for all the hard work. I love my NC more and more with each update.... is there a special prize for hackers-in-white-hats, and if so can we nominate you for it? :)

Wracked my brain for the original source for that info, found it here

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

and it is 5 decimal places (169.33333), confirmed that it works on my system with all the apps causing trouble for others...
[Nook Color Android Development] tominabox1:
Could additional 3's make it not work? I tried earlier today and it was unsuccessful.
[Nook Color Android Development] bonobomidwest:
Oh I had exactly the same thought, once i found the original post and saw that i had an extra "3"s in my post. I figured that might be an issue so went for overkill and and tried it with even more decimal places, but it still worked for me.

Apologies to everyone that i did not track down the 'correct' number of decimal places before posting, but on my machine at least it seems to not make a difference.