Recently, I built an FM application [console based] to work with one of the BT/FM chips on a development platform, which talks to the FM chip using HCI Vendor Specific commands.
The observation is when the application is built "statically" [uses bluetooth.a & proprietary fm_stack.a] and executed from an android file-system [file-system shouldn't matter when built statically...i suppose], it executes at a reasonable expected pace. However when I try and build the same along with the android build system[android's bluez bluetooth.so & proprietary fm_stack.so], after breaking it up into an .so and then a binary which uses it, it takes incredibly "large amount of time" to send in the same number of HCI VS commands. Any idea ? why ? PS: Also if someone's thinking, why would anyone want to build a console based application on android, Hey its not my idea..... --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
