Would it be possible to map it so that the volume keys work in their intended function when the home key is held?
Has anybody been thinking about how to get audio input support?
Hi,
I dig in kallsyms and i find 3 things :
The accelerometer is a kxtf9
The touchscreen is a cytts ( www dot cypress dot com/?rID=44238)
The board seems to be named "boxer"
We need the panel and backlight drivers (and few gpios) and we wiil able to build a kernel from scratch. Other hardware is pretty common with the omap3 platform.
More to come ...
Occip
Has anybody managed to side load quadrant? From there you can find out an awful lot
It IS very interesting. If not to say scandalous. Unsupported Frame buffers may mean mediocre video playback and so-so UI snappiness (compared to what OpenMAX/Open GL ES 2.0 can offer when engaged in full.)Interesting. I have the same GPU (OpenGL) information on my DroidX and yet the NC has "Frame buffers: unsupported" whereas its "supported" on DroidX.
Also noted that the Sensors section is fairly sparse (again in comparison to my DroidX)
So why do you think BN would intentionally not use supported frame buffers?
After dig around with omap iplementation sites, this link look interesting. it appear that I ca not post URL link yet so here come the text.It's clear that the NC is based on TI's ebook reference platform. Given the amount of TI silicon in there I wouldn't be surprised if TI cut them a deal on this WiFi module such that it was cheaper than another company's WiFi-only one. It's not clear what's inside the module, and for all we know there is no BT/WiFi switch, which would make it impossible to run anything but WiFi.
As long as the module has a switch, it wouldn't make any sense for BN to hard-disable the bluetooth. There aren't that many connections just to get BT data, and I'm pretty sure the OMAP doesn't use those connections (1 GPIO, 1 UART) for anything. It would only cost a few PCB traces and maybe a pullup resistor or two, less than a couple of cents at scale.
So far I have compile the kernel using B&N release with bluetooth support and drop that kernel into the NC, it boot up but seem to be sluggish. However, even when the support for bluetooth is there but the hardware not available.
I have comb through the config file on NC and did not see any explicit setting that disable bluetooth, in fact they leave all those file default.
Actually, the droid incredible does not have n support. Check out the verizon page for it. The support evidently cannot be handled through a firmware update. If the hardware is not there, aka. the peripherals that handle the high speed communications, then software cannot do anything for it. I think.