yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] Arbelzapf:
r7:00000000 r6:ca1c7c9c r5:d4549ed8 r4:d4719be8

[ ] (create_dir+0x0/0xa0) from [ ] (sysfs_create_dir+0x44/0x60)

r8:d925cadc r7:cd314ac0 r6:d925cadc r5:00000000 r4:ca1c7c9c

[ ] (sysfs_create_dir+0x0/0x60) from [ ] (kobject_add_internal+0xec/0x1c0)

r4:ca1c7c9c

[ ] (kobject_add_internal+0x0/0x1c0) from [ ] (kobject_add_varg+0x40/0x50)

r9:00000000 r8:ca1c7cc0 r7:cd314ac0 r6:d925cadc r5:00000000

r4:ca1c7c9c

[ ] (kobject_add_varg+0x0/0x50) from [ ] (kobject_add+0x54/0x60)

r7:cd314ac0 r6:ca1c7000 r5:ca1c7c58 r4:ca1c7c58

[ ] (kobject_add+0x0/0x60) from [ ] (device_add+0x7c/0x44c)

r3:ca1c7cc0 r2:c0415cfc

[ ] (device_add+0x0/0x44c) from [ ] (hid_add_device+0xec/0x120)

[ ] (hid_add_device+0x0/0x120) from [ ] (hidp_add_connection+0x25c/0x57c)

r5:d4719d24 r4:d4719d2a

[ ] (hidp_add_connection+0x0/0x57c) from [ ] (hidp_sock_ioctl+0x11c/0x33c)

[ ] (hidp_sock_ioctl+0x0/0x33c) from [ ] (sock_ioctl+0x1f0/0x240)

r7:c9515ac0 r6:00018370 r5:400448c8 r4:c9515ac0

[ ] (sock_ioctl+0x0/0x240) from [ ] (vfs_ioctl+0x34/0x94)

r7:c9515ac0 r6:400448c8 r5:00018370 r4:c9515ac0

[ ] (vfs_ioctl+0x0/0x94) from [ ] (do_vfs_ioctl+0x530/0x578)

r7:c9515ac0 r6:400448c8 r5:c9515ac0 r4:df7feb28

[ ] (do_vfs_ioctl+0x0/0x578) from [ ] (sys_ioctl+0x40/0x64)

[ ] (sys_ioctl+0x0/0x64) from [ ] (ret_fast_syscall+0x0/0x2c)

r7:00000036 r6:0000f310 r5:00018370 r4:00000014

Code: e59f0070 eb096409 e59f006c e1a03004 (e5941020)

kxtf9 1-000f: IRQ TAP2 [4]

kxtf9 1-000f: IRQ TAP2 [4]

kxtf9 1-000f: IRQ TAP1 [2]

kxtf9 1-000f: IRQ TAP2 [2]

Kernel panic - not syncing: Fatal exception

Rebooting in 1 seconds..

No errors detected

Reboots everytime once it's paired to my brand new apple mini keyboard :(
[Nook Color Android Development] verygreen:
that's not enough, there should be more.

paste everything starting from kernel BUG line (if there is one ) plus a few lines before that.

Or start with the line where it complains about an object taht already exists.
[Nook Color Android Development] Arbelzapf:
I'd love to post more, but since I flashed #17 over, I can't get bt to turn on again...
[Nook Color Android Development] Backwardsblade:
The most recent commit stated that the BT firmware is not included in the most recent nightly. I'd stick with that build floating around if BT is a dealbreaker for you.
[Nook Color Android Development] bonobomidwest:
Try a cold reboot. That works for a lot fo people.

I had to erase /cache and /data... if you need to don't be stooopid like me and forget to use ADW's backup function, or TB will not be able to completely recreate your home screen!!!

But I have BT working with CM7 #17 and the OC kernel.
[Nook Color Android Development] bonobomidwest:
Apologies for posting this in more than one thread, but I have started a thread over in accessories, with the intention of trying to put all the knowledge of working (and non-working) bluetooth devices together in one place in a standard format. Hopefully this wil help the communty and the DEVS

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

... and on that note has anyone got the microphone in a BT headset to work. There's loads of people getting audio playback, but i can't seem to find a clear report one way or another of the microphone working with any app (voice recorder, dialer, skype etc.)
[Nook Color Android Development] Arbelzapf:
Okay I haven't tried wiping data yet...that's going to hurt
[Nook Color Android Development] KitF:
Hard reboot (hold power button until it shuts off, turn it back on). It took me 2 reboots to get the BT to turn on

this is wrong. While the initial gerrit didn't include the firmware, everything patch 2 and up (was merged with patch 4) included it. So the firmware is in the nightly.
[Nook Color Android Development] webvan:
Good idea but that link is cut, here is the valid one : http://xdaforums.com/showthread.php?t=990854
[Nook Color Android Development] bonobomidwest:
Thanks dude!
[Nook Color Android Development] lafester:
it is not a good idea to spam the board with links to your thread.
[Nook Color Android Development] bonobomidwest:
Well aware I was bending the rules there a little... hence the apologies... but the Bluetooth information is proliferating in mutating copies across the board so it seemed like it would help cut down on that if we could collect it all in one place... otherwise people are going to be asking the same question in multiple threads... :)
[Nook Color Android Development] rohit275:
Thanks, this helped me out. I was wondering what I did to break it haha.
[Nook Color Android Development] Arbelzapf:
Okay thanks to the help in this thread, I got it running again. Too bad it still reboots.

Here's the complete log:

http://pastebin.com/T4LvFrjk
[Nook Color Android Development] DigitalMD:
Advanced Audio Distribution Profile (A2DP) works . My BT-3030 stereo headset works for listening only.

It appears that no audio input is implimented yet and so applications that require audio in do not recognize devices, and headset and handsfree profiles do not function

My BT-3030 stereo headset works for listening, but apps that want audio in show no mic present so more development is needed and I'm sure thye are working on that.
[Nook Color Android Development] verygreen:
Well, this is a generic bug in the kernel bluetooth stack.

I see some number of kernel patches that might fix it, but since I cannot reproduce it myself, I cannot verify which one would work for you in the end.

I think this one has a good chance to fix it since it comes from a very similar report to yours: http://git.kernel.org/?p=linux/kern...it;h=a67e899cf38ae542d1a028ccd021f9189f76fb74

I verified and it applies to our tree.

If you don't have an ability to build your own kernels, I can build one for you.

You'd need to put into your boot partition by hand, though.

Just let me know.
[Nook Color Android Development] Arbelzapf:
Wow, thank you. I'd sure love to try it :)

What exactly would the boot partition part mean ?
[Nook Color Android Development] verygreen:
Partition 1 on your eMMC if you are running from that or partition1 on sd card if yuo are running from SD card.

In fact just for these experiments it is probably a good idea to run from SD card (I have an image posted that you can grab, need to replace uImage file with another one that I'll compile for you).

So, next question, do you use dalingrin's standard or OC kernel?
[Nook Color Android Development] Arbelzapf:
I'm perfectly fine with trying from SD-card first :) I use the OC kernel
[Nook Color Android Development] verygreen:
Ok, use this kernel (unpack the archive)

put this file on 1st partition of sd card image with the name uImage (instead of the existing file with that name).

If it works on sd card, you can copy it to your eMMC from sd card

(just mount /dev/mmcblk0p1 somewhere and replace uImage there with this new one that you'll already have on /dev/mmcblk1p1
[Nook Color Android Development] Arbelzapf:
Meh, I can't write the image to my 2gb cards.

Using adb, will these instructions work? http://forum.androidcentral.com/barnes-noble-nook-color/55420-how-new-version-install-nookie-froyo-internal-memory.html

Or is there a better way?
[Nook Color Android Development] verygreen:
Yes, the instructions on that link will work.
[Nook Color Android Development] will75:
bleh nm .... fixed.. eh
[Nook Color Android Development] Arbelzapf:
Holy ****, it worked!!! It says it can't find an sd-card, but I was able to successfully use my keyboard to google for "bananas"

EDIT: Awesome. I am writing this on my nook using the keyboard. Thank you so much for helping me out. Any idea what's wrong with the sd-card?
[Nook Color Android Development] verygreen:
Ok, thanks for confirming it.

I'll push the change into the kernel repo then so that subsequent builds will have this fix.

Edit: No idea about the SD card problems. I am not even totally understand what sort of SD card problems you have. Also I imagine daligrin will update his OCed kernels in the near future and you'd be able to use his builds just fine after he merges this fix.
[Nook Color Android Development] Arbelzapf:
Yeah, it's probably just a matter of time :)

The issue also seems to have fixed itself while i'm writing this. The sd-card error just vanished after some reboots :D
[Nook Color Android Development] mad1100:
I was having the same bluetooth keyboard rebooting the nook as the other fellow, so thank you for helping solve this little problem we were having. I will wait for it to be integrated into the OC kernel to add it to my nook!
[Nook Color Android Development] Arbelzapf:
There still seems to be an issue with turning BT on. Rebooting helped again, but apparently the issue tends to come back.

(I have yet to update to #18 and dalingrin's new kernel if that makes any difference. I'll keep you posted)
[Nook Color Android Development] richbutler1:
I'm awaiting the mic working also. I'll test out some Skype calls when confirmed. thanks for updating that A2DP works. This may get me to inject some more money into the economy and buy a BT wireless headset (w/mic)

ANYONE: Is there such a thing as a BT Webcam for Android that might work with the NC w/BT???
[Nook Color Android Development] Afad:
So happy the BT functionality has been activated at last! Voice functions are expected soon, i hope!

By the way managed to connect NC to 3G/EDGE network via SE K850 cellular's BT PAN profile.

First, have paired both devices and granted access for NC to all the BT services on the phone (by default K850 got connected as HID device, could control NC as a joystick, quite curious), then having active BT link between NC and K850 have run these simple commands via adb shell or in virtual terminal on NC:

pand --connect {your phone's BT hex address}

ifconfig bnep0 down

dhcpcd bnep0

setprop net.dns1 8.8.8.8

Mobile phone's BT hex address can be obtained in a cellular itself (or on its sticker), as well as directly in NC's paired devices settings (Network Info II for example). After "pand --connect XX:XX:XX:XX:XX" command i mentioned active 3G connection have got running on the paired phone. To test whether we got successfully connected or not i've just run the constant ping to google.com simultaneously in NC's virtual terminal (nslookup works as well, it's usefull to check the IP obtained during "dhcpcd bnep0" command via "ifconfig bnep0" command too). Typing "ifconfig bnep0" after all should show obtained IP-address from the cellular network. Sometimes "dhcpcd bnep0" didn't work so i had to run it twice. Finally, have put all these commands in one GScript shortcut - connects and holds the link like a charm. Mention the BT signal is poor and disconnects sometimes due to small working range so don't walk far )).

Hope, this will help someone!
[Nook Color Android Development] rulevoid:
I have my HTC Incredible and Nook Color paired in Bluetooth but then when sending a *.log file from root explorer via bluetooth on the Incredible, it fails and says that the receiving phone can't receive that data type (extension im assuming) IS there a way to allow receiving of any file?
[Nook Color Android Development] danger-rat:
Why not tether your phone over wifi, and use the Tether GPS app?

Works perfectly for Google Navigate and CoPilot...
[Nook Color Android Development] Divine_Madcat:
TeatherGPS is a great app, but not all apps support mock locations (which is the service that it has to use). Its not really one or the others - its what app is needed for certain things; on some, a true GPS connection is required.
[Nook Color Android Development] webvan:
Besides TetherGPS requires you to have an Android Phone.
[Nook Color Android Development] chisleu:
And doesn't work unless you have IP tables support and a true network config like android-wifi-tether

I have to use the Barnacle Wifi Tether program (requires root) and doesn't use IP Tables because of my phone's kernel's lack of iptables. So I use bluetooth for the GPS. "Bluetooth GPS" on the tablet, and "Bluetooth GPS Output" on my android phone work for me.
[Nook Color Android Development] webvan:
"Bluetooth GPS Output" is to export the GPS data of your smartphone via Bluetooth ?
[Nook Color Android Development] aludal:
To Verygreen & all able coders

I fully realize that this here bootable SD w/CM7 v17 is not much more than a proof of a concept, plus BT demo, and might be abandoned at any minute, if not already. Yet the lure is big, and the more NC users try this SD, the faster BT mic and other problems might be solved.

So, if I may suggest, our glorious coders are politely requested:

-- to build the same around CM v19 (or 20?) (v17 with its 161 dpi IMHO was the worst in screen density artefacts, etc., please do default DPI 169.3333 -- see explanations in my blog fineoils.blogspot.com

-- add the latest Gapps/Market right into a ROM, as the usual routine is way too convoluted,

-- add some sizeable (1GB) "practical" partition to the ROM, to play more freely before that ROM gets stuck,

-- Volume+/- to Back/Menu hack.

Enjoy the response and possibly bugfixes from thousand more users of your ROM. I wouldn't be surprised to see YouTubeHQ working smoothly at last on this ROM -- just by some playing with stagefright stanzas in buid.prop. Sure, it still takes IVA2 (DSP) working full blast, but "software" YouTube "HD" decoding of Eclair was too nice to throw it away in the interim period.
[Nook Color Android Development] EpicFail236:
So technical things: After researching a bit, I've found a few devices that have the same chipsets as we do in the nook, including the SE x10e pro. So, since they have roms with bluetooth already good to go, I thought it prudent to view their configuration files to see if I could make some edits and get things to work properly. Seems the only major differences between theirs and ours is one line in the ini:

STRFRefClock = 2

Theirs is set to 1 instead of two. looking it up on the interwebs, it seems this line is the one everyone needs to fix when having problems with embedded devices, so I tried switching this to 1 and rebooting, upon which i found that neither wifi nor BT would work. Is this something that needs to be recompiled in the kernel maybe? Or am I simply grasping at straws trying to get this thing to work?
[Nook Color Android Development] verygreen:
I was advised against doing not to attract any attention from Google lawyers. ;)

which one do you mean? data partition, instead of bunch of FAT space at the end that you also can use? (well, after the vold fix).

What do you mean by "ROM gets stuck"?

Dalingrin works on proper DSP support and would greatly appreciate any help.

But so far nobody was able to make it totally work with new libbridge.so
[Nook Color Android Development] kassemja:
All we hear from you is complaints. I’m sure the devs hear find your comments insulting.

You could easily resolve your own requests if you did little reading and goggling to investigate a little.

Gapps / Market can not be baked into to roms due to a licensing issue.

DPI screen res, Volume+/- to Back/Menu hack and most your other requests are personal preferences and can be easily tweaked by you.

I find your posts subjective. Given you know the status of things concerning video acceleration / DSP adding the stagefright lines to the build.prop will do little seeing drivers are broken.

The devs here on XDA work hard and have produced great results on the nook.

aludal you are way out your depth, best you keep your posts to your blog.

A little appreciation and some praise from you wouldn’t go astray.
[Nook Color Android Development] khaytsus:
Name one program that doesn't work with Mock locations. No, you don't get satelite feedback (11 sats, etc) but I have yet to find a program that doesn't work.

I extensively use GPS on my phone, and besides Tasker using it every 10 minutes without my interaction, all of my GPS use is via my bluetooth GPS using Bluetooth GPS Provider.

List of apps I know work: Tasker, Google Maps, Google Navigator, Waze, Backcountry Navigator, GeOrg, c:geo, Compass, more..

Apps that don't work because they have their own BT GPS code: WhereIGo

Apps that don't work: (null)
[Nook Color Android Development] Arbelzapf:
Hm...I'm on #19 now and can't enable BT even after a cold reboot. Any ideas?
[Nook Color Android Development] KitF:
You're turning it off by holding the power down right? Not pressing it and hitting Shutdown?

It needs to be done the first way. If not, try a couple of more times.
[Nook Color Android Development] Arbelzapf:
Worked after the third time :)

I hope it doesn't come back this time
[Nook Color Android Development] motitas:
if it comes back try clearing your cache through clockwork
[Nook Color Android Development] EhudBenjamin:
Parallel Kingdom
[Nook Color Android Development] KryptoNyte39:
Sygic Aura?
[Nook Color Android Development] khaytsus:
.....seriously?

I'd write them and tell them to fix it, everything else works. I suspect they are requiring X number of sats before assuming they have a signal.
[Nook Color Android Development] EhudBenjamin:
Yes seriously. You asked for ones that don't work. If you think people are not using these devices for games your wrong. Look at all the above posts for connecting a Wii remote.
[Nook Color Android Development] chisleu:
Yes as soon as I can get a wiimote I hope to do some NES gaming.

if I rotate the screen to view a webpage, my bluetooth keyboard's arrow keys get disorientated. I have to press left to go down, etc. As if the keyboard also changed orientation.

I also have an issue of intermittent keyboard functionality. Although it is directly next to the NC, it acts like it is going in and out of range. It wll stop working and the catch up. Sometimes it stops working and when it starts working it will only hit one of the keys in the buffer and then lock up requiring a BT or system reset to regain functionality.

Anyone seeing this? I could not even finish typing this before the keyboad died.
[Nook Color Android Development] RoboRay:
Does a BT keyboard use the Dpad entries in qwerty.kl for the arrow key function? If so, since the NC doesn't have a Dpad, you could edit the file to obtain proper operation of the BT arrows in landscape mode.

This would screw up the arrow key orientation in portrait mode, but may be preferable if you consistently type in landscape.
[Nook Color Android Development] chisleu:
That is definately undesirable. It can not be that hard to stop the auto rotation.
[Nook Color Android Development] greenleaves:
I don't seem to find the A2DP in Market that works with my Motorloa H17 BT headset. I got BTGPS to work fine. What A2DP app you are referring to? Appreciate your help.
[Nook Color Android Development] DigitalMD:
Its not an app, A2DP is the protocol for stereo audio that is built into bluetooth. no extra software required, but its for stereo headsets, although some single ear pieces support it for listening to media audio, not phone. Most bluetooth phone headsets do not support A2DP, and therefore not media audio.
[Nook Color Android Development] greenleaves:
Thanks for the clarification. I'm hoping a BT driver that can work for regular BT headsets.
[Nook Color Android Development] DigitalMD:
You're welcome. I'm sure people are working on getting full functionality for BT, but at the moment its not complete. Needs to be done at the operating system and driver level.
[Nook Color Android Development] sinanju:
I've managed to pair my Blueant headset and my Holux GPSlim 236. Neither work, of course. I was hopeful Bluetooth GPS Provider might help... it does find the paired device, but won't start.

So close...

EDIT:

WORKING!

Bluetooth GPS (Free in the Market https://market.android.com/details?id=googoo.android.btgps) did it! I now have a working connection in Google Maps via that tool connected to my GPSlim 236. I had to hit Connect several times to get it going, but it works!
[Nook Color Android Development] Arbelzapf:
I wanted to make this a separate thread, but it was immediately moved to die in the themes&apps-forum.

Now that I see you guys talking about a similar subject, please allow me to paste my post here:

I have tried several apps that claim to support a German layout with BT keyboards, but none of them worked.

I then opened system/usr/keylayout/qwerty.kl and replaced y and z so I at least have a basic qwertz-layout.

Now I'm stuck. I have no idea what to put in there to get umlauts working and I'm starting to think that changes in the qwerty.kl alone won't be able to get me a fully working German layout

Can anyone help me out here? Google didn't help much :(
[Nook Color Android Development] chisleu:
EDIT: doesn't use the kl files. those are for reference. it uses a binary format file in the other directory.

Can't figure out if there is a generic UP/DOWN (vs the KEYPAD directions)
[Nook Color Android Development] chisleu:
New info! Making some headway on the bluetooth keyboard mapping.

Logcat (whatever that is) complains that it can not open the keycharmap file. It is trying to open "Bluetooth_Keyboard.kcm.bin"

Apparently this is a binary version (non-ascii) of the keyboard layouts that is generated when you build.

Working on editing the default map (what android is defaulting to) in order specialize it as a "driver" for my keyboard. I'm using a market app called "KeyEvent Display" which lets you see which keycodes are being sent from the keyboard.

Still no idea why the keyboard keeps disconnecting (requiring power cycle on the keyboard to get it working again.)

It happens far too often to be usable.
[Nook Color Android Development] chisleu:
OK... what a day... I guess I can call it "productive."

I managed to remap my , and . to have < and > when you shift+keypress (default is ; and :)

copied qwerty.kcm.bin

modified it (it's a binary file, use a hex editor)

renamed it Bluetooth_Keyboard.kcm.bin

copied it back to the /system/usr/keychars/

What a pain.

I am unsure if there is a problem with the bluetooth, or my keyboard. something is wrong. It gets stuck on key-down loops (like long presses) but when it happens, they come in slower than normal. Sometimes it doesn't come out and requires power cycling the keyboard to get it out of the loop.

I hope it's not the keyboard because i'm not sure if I can find the packaging to send it back to newegg.

Anyone else have a bluetooth keyboard they are working with?

Do you have any other keys working (caps lock, etc?)

Also I'm using the hardkeys app/mod and it modifies the volume up/down on the keyboard to match the settings. haha. so at least I have a back/menu on the keyboard too.

I get scancodes for many of the keys that are not mapped, but I'm not sure where a keycode is given to the scancode, but an application could use the button by scancode (so you can make special keys do something with a custom app.)

On the arrow key rotation problem:

That is being done above the application level. They kernel, driver, or something else is intercepting the arrow keys and changing them based on the rotation of the screen.
[Nook Color Android Development] verygreen:
I have an apple bt keyboard and it works fine.

The range is pretty small so keep it close to the nook.

I did not try capslock now that I think about it. But using it for navigating and typing urls and such worked fine.

There is number of success reports with various keyboards in this thread too.
[Nook Color Android Development] chisleu:
[/QUOTE]

if you are editing text and rotate the tablet to landscape, does it mess up your arrow key orientation?

See if caps lock works for me too!
[Nook Color Android Development] cybertimber2007:
The orientation didn't affect my keys IIRC. It was off in either orientation... to move up/down, I had to press the left/right arrow on they keyboard.

Edit: nope, changes with rotation. Up/down arrows work normally in portrait mode, and incorrectly in landscape.