yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] eyecrispy:
posting from jameshmiller who doesn't have enough posts to post in this forum but thought this might be helpful for those having wifi issues on CM7:

==================

I'm quite the newb, so I can't post on the developers thread. I'm passing this on from the CM7 nightly discussion from valeryan. I hope it helps.

I have had wireless issues with all the nightlys so far. I have come across a few others having the same issue and have tried a few fixes. As far as I can tell it is only a issue for those using wpa/wpa2 and seems to be confined to dlink's routers. Not really a major issue for most but if you are having issues connecting using wpa/wpa2 it is some how related to the WiFiAdhoc setting in tiwlan.ini found in /system/etc/wifi/. WiFiAdhoc is set to 1 on the cm7 builds but if you change it to 0 wpa/wpa2 will work. To confirm my findings I did a complete wipe and installed build 13 to make sure the issue still existed. Then I installed root explorer and changed the WiFiAdhoc to 0 and reboot. Now my nook connects using wpa/wpa2. I can also change my router to use wep and it will connect. I am not sure why enabling adhoc networking would cause issues with dlink and wpa but it seems to be the case. I offered a fix in a previously post but found that it didn't fully fix the issues, but changing this setting does. Anyway, just thought I would share my findings to help anyone else that might experience this issue.
[Nook Color Android Development] aludal:
I think I could help -- if just a little.

Not all D-links are made equal, so to speak. Neither other "consumer grade" routers can reliably work in adhoc mode which seems to be added as an afterthought, then crippled if it's not for the cell carrier re-brand.

Those D-Links that are more equal than others, so to speak, are called "DD-WRTable" (Google out DD-WRT supported devices, it's a quite long list, but some routers didn't/couldn't make it there.)

Long story short, I've got me that throwaway D-Link DIR 615c re-brand called Fry's FTR300 ($29.95 when new, or $20 from the open box: a return of a disgusted customer). Had all the problems with g/n mixed connectivity, let alone adhoc for my WPDN. Then, a half a year ago or so, DD-WRT flashable FW for 615c appeared. Procedure is quite convoluted, but works in skilled hands. Read it in my blog.

No problemo with my WPDN or NC since. Sure YMMV.

fineoils.blogspot.com
[Nook Color Android Development] J-ROCK:
Anybody else having issues with rockplayer's playback when playing videos of the web? It tends to play in slowmotion after about 3 minutes.
[Nook Color Android Development] Fishfoot:
Hey guys,

I'm trying to get this all setup. I installed the gapps found on the regular CM7 wiki and after a reboot I get:

process android.process.acore has stopped unexpectedly

I'm a relative noob at this. Can somebody help me out?

Thanks
[Nook Color Android Development] brashmadcap:
Did you wipe everything before you installed? I MEAN EVERYTHING

and did you install the right gapps? I know there's only one for CM7 now but are you sure that's the one you installed? usually if you're getting process.acore stopped, it's bad news and you're looking at a reinstall in my experience.
[Nook Color Android Development] Fishfoot:
Thank you, that definitely points me in the right direction. When you say "Wipe Everything" what exactly do you mean.

I formatted system, data and boot as ext4. Besides that I wasn't aware that more had to be done (but that's likely a result of my ignorance).

And yes, as far as I know I got the right gapps. I grabbed it off the CM wiki and it was the only version for CM7.
[Nook Color Android Development] KitF:
I'm pretty sure you DO NOT WIPE BOOT.
[Nook Color Android Development] eyecrispy:
Definitely don't wipe boot. Just do system, data and cache.
[Nook Color Android Development] MACLUIS1:
I had the same problem. Solved by cleaning data and cache on any apps with Contacts in the name in Applications settings.
[Nook Color Android Development] Chahk:
Trying to register for updates under Settings -> CyanogenMod settings -> System -> Update notifications -> Register and it sits there spinning until I kill it. I do have RomManager Premium purchased and installed. Here's what the logcat shows:

D/CMUpdateNotify-NightlyLicense( 2087): validLicense() = true
I/ActivityManager( 966): Displayed com.cyanogenmod.updatenotify/.MainActivity: +325ms
D/dalvikvm( 2087): GC_FOR_MALLOC freed 266K, 54% free 2618K/5575K, external 258K/543K, paused 32ms
D/CMUpdateNotify-DeviceRegistrar( 2087): Registration Error: 404

Is error 404 = page not found?
[Nook Color Android Development] elwood1229:
Glad to know someone else is having the same issue.
[Nook Color Android Development] wpnyc2009:
Plus 1

Ditto. I'm manually updating for now. It's not that inconvenient; just an FYI. :)
[Nook Color Android Development] will2live:
FYI that will not fully work. you either need to manually install 3.0.1.0 & kernel or use the *.zip file.

Rom Manager can not install the updated kernel that is needed for use with 3.0.1.0 which is stated in the OP of the 3.0.1.0 thread (http://xdaforums.com/showthread.php?t=971197)
[Nook Color Android Development] tominabox1:
Mine did...
[Nook Color Android Development] mrkrabs:
jus flashed nightly 15...cannt get flash workin at all....tried stock and firefox....loaded flash player from the market ....ne ideas????
[Nook Color Android Development] huemedia:
sleep replacement

How do you all send your device into sleep given that it doesn't really work in CM7?

Thanks
[Nook Color Android Development] dalingrin:
You shouldn't have to do anything. The idle state has approximate the same power draw as Froyo or Eclair. CM7 should last several days off the charger if left idle with the screen off.
[Nook Color Android Development] pstein2:
I never turn mine off, just turn the screen off and let it sit. I can go about 2 days before I have to put it back on the charger with lite use.
[Nook Color Android Development] Paul22000:
Either you take the battery hit or you turn off the device.

I turn mine off at night and when I know I won't be using it for a long time.
[Nook Color Android Development] aludal:
Seriously OT! (hope not....)

On SOD:

I was browsing through 100s of more or less current dev pages, have found this:

"ARM: S5PC11X: CPUFREQ: Fix power suspend cpu frequency

Power suspend often crashes the device if the cpu frequency is not

equal to SLEEP_FREQ. If the current cpufreq policy does not include

SLEEP_FREQ, cpufreq_driver_target() does not change the cpu frequency

for power suspend, resulting in crashes. This gives

cpufreq_driver_target() a modified cpufreq policy that includes

SLEEP_FREQ to force the frequency to SLEEP_FREQ upon power suspend,

regardless of the current cpufreq policy.

Signed-off-by: Michael Huang <mike.g.huang@gmail.com>"

Mind you, I know that

-- CPU (here S5PC110) is different;

-- kernel is different (2.6.35, whereas we've been stuck at 2.6.29 which might turn inadequate/unpatchable)

fineoils.blogspot.com
[Nook Color Android Development] Narfx:
Hum, I see this merged:

http://review.cyanogenmod.com/#change,3771

but I still see "(No service)" in the pulldown bar and in the lockscreen (just synced and compiled)....

At least the signal icon in the notification bar has been removed :)
[Nook Color Android Development] fattire:
Consider a make clobber and maybe wiping /system. If you haven't clobbered lately you'll probably also have RC1 instead of RC2 in the filename.
[Nook Color Android Development] Narfx:
Yep, you're right, I still see RC1. I thought make clean was enough. Clobbering and remaking now. Thank you.
[Nook Color Android Development] fattymcdirty:
could u upload a build with the latest fixes concerning removed icon and "no service"?
[Nook Color Android Development] Narfx:
Hmm, I formatted /system, made clobber and clean before brunch, and now I see RC2 in About Phone, but I still have the No Service banner :(
[Nook Color Android Development] Slack3r:
It seems that no matter what I do, I can't get Google Apps to install with build 15 and the newest gapps package. I wipe system, data, cache, and dalvik before I install. Any ideas?
[Nook Color Android Development] Snyperx:
Wait for the build. Build 16 did not go last night for whatever reason. You could always build from source.
[Nook Color Android Development] newellj79:
My market wasnt working after flashing v15 over v14. I was told there was a new gapps dated 3/7 and I should try it. I just flashed right over everything with out wiping and it worked fine. (i was not prompted to pick which apps install, upon reboot though)
[Nook Color Android Development] eyecrispy:
Devs,

I am currently on CM7, v14. Realized today that I can't download books because the INTERNAL_STORAGE variable wasn't set in the init.rc file. I added it and it fixed the issue. Could you guys update this in a future CM7 release?

Reference http://xdaforums.com/showthread.php?t=966339 for more info.

Thanks!
[Nook Color Android Development] dalingrin:
Thanks for the pointer. Kind of sad they rely completely on that environment variable....
[Nook Color Android Development] dalingrin:
Are you able to mount both sd card and emmc via USB?
[Nook Color Android Development] dalingrin:
Updated the OP with bluetooth info and a video made by IOMonster/thecubed, our resident tester.

err sorry for 3 posts in a row....
[Nook Color Android Development] fattire:
I had a premonition. *****in' vid. Makes me want to get some sort of bt peripheral at some point.
[Nook Color Android Development] eyecrispy:
I havent tried since adding the variable. I'll try when I'm back from the gym. I will say, though, that I could mount it before but had a lot of trouble ejecting it from my MacBook pro.
[Nook Color Android Development] eyecrispy:
dalingrin -- i just tested and yes, i can mount both sdcard and emmc (media) via usb. funny thing is before setting variable, i had a really hard time ejecting the mounts when i was finished. now, it ejects just fine.
[Nook Color Android Development] gge5:
Wow, you guys are great. It's sort of too bad that there will never be a case made for the nook with an integrated keyboard. I wonder if I could get Torque working with this...

Keep up the great progress, and I look forward to getting DSP support!
[Nook Color Android Development] bonobomidwest:
Yeah dude... you tell us that BT is working and you APOLOGISE!!!!!??????!!!!

I might have just pooped my pants with excitement... hey pants dalingrin says sorry 'bout that he just can't help him and the CM7 Devs being genius rockstars... :)
[Nook Color Android Development] aludal:
LOL, I remember that your premonition, and it was true in money this time. Sure, I also can't wait to pick me some BT mic & headphones and start happily Skyping. I mean, for a phone BT works -- almost -- fine. On too short distance my take BT radio in NC is at its default power level (100%?) which is no good.

Please, don't forget to tell us, unwashed masses, about your further premonitions on:

1. Full DSP (and SGX, codecs) HW acceleration for Flash 10.1+, video, YouTubeHD, vocoder.

2. Kernels of 2.6.32...38 in CM7 for NC.

3. USB Host (cameras anyone?).

4. FM... no, strike this one out
[Nook Color Android Development] rainmaker002:
I have what might be a silly question. DSP and video acceleration is not currently working, and the devs are hoping to get everything up and running. My question is: will that affect 2d performance within the operating system? I am running dalingrin's OC'd kernel at 1.1Ghz, using ADW Launcher and Dolphin HD browser and no matter what I'm doing things are kind of sluggish. It's not like an iPad where scrolling is perfectly smooth (well, close enough) or a desktop web browser where movement is judder free.

Is it the dev's expectation that eventually that's where things will be at? Or will things always be somewhat sluggish?
[Nook Color Android Development] dalingrin:
Bluetooth build posted for those interested.

The DSP does not affect 2D functions. The sluggish scrolling cannot be fixed until Honeycomb. Some 3rd party browsers use techniques similar to the iPhone for scrolling but they must not be based on libwebcore. Dolphin is just the stock browser with a better UI. You can try either Opera Mobile, Opera Mini or Firefox. They use tiling to break up the webpage into chunks that are easier to process.

Honeycomb supposedly partially fixes the scrolling issue by adding GPU hardware acceleration. The next Opera Mobile coming out will also have hardware acceleration. Video example of the next Opera for tablets: [youtube]a1pnuXZVfyk[/youtube]
[Nook Color Android Development] starkruzr:
So I flashed CM7 Nightly 15 and:

1) Bluetooth cannot be turned on,

2) The keyboard doesn't pop up when I try to put my Google account name in.

Am I somehow doing it wrong?
[Nook Color Android Development] jkurl:
@Dalingrin i see you posted the bluetooth only reaches about 1-5 feet. It sounds like either there is not enough voltage going to the chip to put it at the right DB level. I have the spec sheet for the chip used for WLAN/BT operations in the nook color. if you got it to transmit and receive(tx/rx) somehow power just needs to be upped. The min DBm is 12 and the max is 15DBm. The nook color might not be able to push the power high enough but I am sure it can. I wouldn't see why B&N would put this chip in the Nook Color unless they had plans to use it in the future. I sent you a tweet about looking at the code for the bluetooth module.
[Nook Color Android Development] bonobomidwest:
Try

ADW settings > System preferences > Scrolling Cache > Auto

I have my home screen (ADW) locked in portrait mode, i think this my help the above setting work better, but i do not know for sure. In any case the improvement is huge.

I have also found that the interactive governor (Dalinigrin's most recent kernel) also seesm to kick things up a notch.
[Nook Color Android Development] k4str0:
Can the 1100 OC kernel be used with the BT preview build on post 1?
[Nook Color Android Development] timekeeper:
No, but he has said he's building an OC kernel that includes the work on bluetooth.
[Nook Color Android Development] Snyperx:
So what kernel does this BT build have? Is it 2.6.35?

EDIT: Nevermind, found it. It's 2.6.29.
[Nook Color Android Development] timekeeper:
uname -a says 2.6.29
[Nook Color Android Development] RileyGrant:
I click on "Turn bluetooth on" under the wireless and networks setting, bluetooth starts to turn on but then unchecks itself and then again shows the option to "turn bluetooth on."

Anyone?
[Nook Color Android Development] Snyperx:
No issue here. Working good on my end. Weird. hmmm....???
[Nook Color Android Development] TheTodFather:
Hey at least your bluetooth videos puurddy!
[Nook Color Android Development] RileyGrant:
Ya... Might just wipe and reflash, don't really need my apps right now seeing as I use Honeycomb for my daily. hehe. Just wanted to get on the early BT train.
[Nook Color Android Development] dalingrin:
I've posted an OC kernel thats compatible with BT.
[Nook Color Android Development] combustiblemonkey:
You win the cableweb intrarnets.
[Nook Color Android Development] EpicFail236:
flashed new build, can't power up bluetooth:

Logcat shows an error:

E/bluedroid( 999): bt_enable: Timeout waiting for HCI device to come up

if that helps. going to try the ini file edit and see if that helps.

Update: changing ini file

BThWlanCoexistEnable = 1

allowed device to turn on, but it acts strange, including invalid discovery session?:

V/BluetoothEventRedirector( 1151): Received android.bluetooth.adapter.action.DISCOVERY_STARTED
D/dalvikvm( 1619): GC_CONCURRENT freed 481K, 56% free 2553K/5703K, external 0K/0K, paused 2ms+2ms
E/BluetoothEventLoop.cpp( 992): event_filter: Received signal org.bluez.Adapter:DeviceFound from /org/bluez/1872/hci0
D/BluetoothService( 992): updateDeviceServiceChannelCache(43:29:B0:00:00:00)
V/BluetoothEventRedirector( 1151): Received android.bluetooth.device.action.FOUND
D/dalvikvm( 1151): GC_CONCURRENT freed 395K, 52% free 3034K/6215K, external 705K/1113K, paused 2ms+3ms
W/KeyCharacterMap( 1151): Can't open keycharmap file
W/KeyCharacterMap( 1151): Error loading keycharmap file '/system/usr/keychars/cyttsp-i2c.kcm.bin'. hw.keyboards.65537.de
vname='cyttsp-i2c'
W/KeyCharacterMap( 1151): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
E/BluetoothEventLoop.cpp( 992): event_filter: Received signal org.bluez.Adapter:PropertyChanged from /org/bluez/1872/hc
i0
E/BluetoothService.cpp( 992): stopDiscoveryNative: D-Bus error in StopDiscovery: org.bluez.Error.Failed (Invalid discov
ery session)
E/BluetoothEventLoop.cpp( 992): event_filter: Received signal org.bluez.Adapter:DeviceCreated from /org/bluez/1872/hci0

D/BluetoothService( 992): 43:29:B0:00:00:00 bond state 10 -> 11 (0)
E/BluetoothEventLoop.cpp( 992): event_filter: Received signal org.bluez.Adapter:PropertyChanged from /org/bluez/1872/hc
i0
V/BluetoothEventRedirector( 1151): Received android.bluetooth.adapter.action.DISCOVERY_FINISHED
V/BluetoothEventRedirector( 1151): Received android.bluetooth.device.action.BOND_STATE_CHANGED
D/BluetoothService( 992): 43:29:B0:00:00:00 bond state 11 -> 10 (0)
W/BluetoothService( 992): setBondState() called to unbond device, but reason code is invalid. Overriding reason code wi
th BOND_RESULT_REMOVED
I/BluetoothEventLoop.cpp( 992): agent_event_filter: Received method org.bluez.Agent:Release
E/BluetoothEventLoop.cpp( 992): event_filter: Received signal org.bluez.Adapter:PropertyChanged from /org/bluez/1872/hc
i0
E/BluetoothEventLoop.cpp( 992): event_filter: Received signal org.bluez.Adapter:DeviceRemoved from /org/bluez/1872/hci0

D/BluetoothService( 992): setRemoteDeviceProperty addr = 43:29:B0:00:00:00 name = UUIDs value = null
V/BluetoothEventRedirector( 1151): Received android.bluetooth.device.action.BOND_STATE_CHANGED
W/CachedBluetoothDeviceManager( 1151): showUnbondMessage: Not displaying any message for reason:9

I'm also getting errors around airplane mode. Going to try a wipe and reinstall, since it's been some time since I've done that anyway.
[Nook Color Android Development] Kendr1ck:
Does the BT preview build also have the

change that was mentioned at http://cm-nightlies.appspot.com/?device=encore?
[Nook Color Android Development] Arbelzapf:
I can't enable Bluetooth as well

Edit: Sorry, I didn't flash the kernel yet
[Nook Color Android Development] dalingrin:
Probably but it is not relevant to us.
[Nook Color Android Development] eyecrispy:
Does anyone have the md5sum for the bt build?
[Nook Color Android Development] NuroSlam:
I for the life of me cant find my BT headset.

Is there a difference in range when WIFI is on/off?
[Nook Color Android Development] openallnight:
Couple of issues/questions

1)I tried to build from source myself but bluetooth does not work. The size difference between file in post and my file is almost 4 megs. Is there some additional steps needed to build from source with bluetooth support? I have built and flashed successfully before

2)Using the zip from the OP I am able to start bluetooth and successfully pair my headset. Although I cannot start voice search etc. see a whole bunch of ALSA driver errors for microphone in my logs. anyone successfully have voice working?
[Nook Color Android Development] AWiseMonkey:
Mine did the same thing, I powered off and booted back up and it works like a champ now... :cool:
[Nook Color Android Development] newellj79:
Same here. I'm using dalingrins of kernel.

Edit... rebooted and it works fine now.
[Nook Color Android Development] myecomemail:
I have successfully connected a MS and a Dell BT mouse. I needed to reboot after flashing to get BT to enable but now I can pair with the devices and use the mouse to navigate. Back buttons don't seem to work so not all that useful. Now I need to go get a keyboard...and some new headphones...
[Nook Color Android Development] barrist:
my bluetooth headphones pair easily. but i have to be like 6" away from the nook or it'll start to break up hah.
[Nook Color Android Development] jkurl:
Can someone turn wifi off and leave bt on and see if it increases the range. If it does then in know why the range is so small if not I still have a theroy in this. I am at the in laws and the NC is at home so I can't test it.
[Nook Color Android Development] NuroSlam:
Im thinking if there is then its a multiplexing probliem
[Nook Color Android Development] jkurl:
Yep that is what I am thinking or a voltage problem. Since wifi and bt are on the same chip power might now be being distributed right.
[Nook Color Android Development] :
Dropbox timezone?

Getting an error setting up dropbox on current build.

"The clock on this device is wrong. Please check time."

Ideas?
[Nook Color Android Development] NuroSlam:
Im pretty sure multiplexing is handled via software so can be addressed, however I think voltage issues would be a chip problem. perhaps these are faulty BT component chips?
[Nook Color Android Development] tgallant21:
Not sure if this helps but with the latest overclocked kernel i get a range from 6-8 feet and this is with wifi on or off. Maybe I am just lucky... not sure yet
[Nook Color Android Development] faceman66:
FYI about Range Issue..

I just flashed the BT rom with the BT oc kernel, then downloaded Wiimore COntroller and linked my Wii REmote to my NC...

I was able to send button data to my nc well over 20 feet away...

I was surprised enough to post this, will check back in soon. :)

Update

So far so good, playing Mario Brothers with my Wii Remote no problem... the possibilities are opening up!
[Nook Color Android Development] jkurl:
Could be. I have the spec sheet for the chip and it has one antenna output so what could be happening is the actual antenna might nit be able to handle both wifi and bt. I an most likely wrong about that. The bt needs a min of 12DBm to work properly. So most likely it is software. If B&N never wanted bt to work they could have had something out in to limited it hardware wise but again I am most likely wrong cause I don't see them buying a chip that would do more than one thing and not intend on using it.
[Nook Color Android Development] RoboRay:
They would if it's cheaper to buy a multipurpose chip that is being produced in much larger numbers than the less common dedicated chips. Economy of scale can do surprising things to your Bill of Materials.
[Nook Color Android Development] jkurl:
True I forgot about that.
[Nook Color Android Development] dalingrin:
When I said 1-5ft i am being a little conservative. But it also depends on what you are using. Some devices can handle tx/rx errors better than others. A2DP for instance can't handle many errors and my maximal distance was based on that.
[Nook Color Android Development] dalamchops:
flashing v17
[Nook Color Android Development] eyecrispy:
I've successfully paired my NC to a Captivate and also an iPhone4. In both cases, it says "Paired but not connected." I don't use bluetooth much but I would expect it would actually connect? If so, how do i get it to actually connect?
[Nook Color Android Development] SgtSpike:
Bluetooth in Nightlies?

Is BT support now rolled into the Nightlies?
[Nook Color Android Development] tominabox1:
Yes.

Anybody have a on pixel line of transparency just to the right of the center... of course I would take a screenshot...

Also, has anybody got xda app working again? I think it works if you have a static imei number
[Nook Color Android Development] Dadeeo:
Holey underwear, all this effort into BT and all I want is

Youtube

to work, isn't it about time I got what

I

want!!! :D
[Nook Color Android Development] TheTodFather:
Yes grab a link from the op from team douche
[Nook Color Android Development] TheTodFather:
Patience young grass hopper
[Nook Color Android Development] TheTodFather:
No its just yours
[Nook Color Android Development] EpicFail236:
Okay, after some experimentation, I've finally gotten Bluetooth to turn on and connect, but the range is miserable. Even with a wiimote, which seems to be the best at long range, dies completely when more than a foot away. No major radio interference, with and without wifi on. Any suggestions?