Can any one provide some inputs?
On Wed, Aug 31, 2011 at 9:15 AM, Pratik Prajapati <
pratik.prajap...@gmail.com> wrote:
> Dear All,
>
> For production of the device, android APKs needs to be signed. I have
> created keystore as explained in
> http://developer.android.com/guide/publishing/app-sign
Just a supplement here. If you don't want to download the whole Android
source, the prebuilt toolchain in the NDK can also be used. :)
William Liang
2011/8/30 joerg simon
> Dear Ramya,
>
> They are not binary but afaik source compatible. I am 100% sure for
> the SKULL driver, you can compile it
On Wed, Aug 31, 2011 at 9:46 PM, parth shah wrote:
> Hi Gil,
>
> Thanks for that response. Just before few minutes i tried that and i was
> surprised to know that even after changing the baudrate i'm getting 8.06uS
> pulse width.
>
> which means even i'm trying hciattach /dev/ttymxc1 texas 9600 n
Hi Gil,
Thanks for that response. Just before few minutes i tried that and i was
surprised to know that even after changing the baudrate i'm getting 8.06uS
pulse width.
which means even i'm trying hciattach /dev/ttymxc1 texas 9600 noflow but the
UART packet is going out at baudrate of 115200(8.0
On Wed, Aug 31, 2011 at 9:27 PM, Gil Zhaiek wrote:
> One more thing - try a different baud rate (using a different bts
> file).
> Try 115200 bts - because you see that this works.
Is the firmware version read already ?
The logs you sent in the first mail doesn't show that ...
Can you put some lo
One more thing - try a different baud rate (using a different bts
file).
Try 115200 bts - because you see that this works.
Gil
On Aug 30, 11:42 pm, parth shah wrote:
> Hi Pavan,
>
> We are using imx515 platform from freescale.
>
> We have pulled up connected with BT_EN with 1.8V. and BT_EN is co
Hi,
It seems that after switching baud rate (from 115200 to 300) the
device is not communicating again.
Make sure the BTS file is set to 300 (it is in the file).
The device is on, and you are able to communicate with it - it is the
switch that gives you problem.
Gil
On Aug 30, 11:42 pm,
On Tuesday, August 30, 2011 8:49:44 PM UTC-4, Behnam wrote:
>
> I am currently moving to Android Kernel 3.0 for my development and I
> realized that adb no longer works in 3.0 kernel. I did a bit of
> digging and came across a commit that completely removes any ADB
> functionality from USB gadge
Well yes this seems like the logical case, but he does say Android kernel
which should point to some version of linux instead of the Android sdk/ndk
3.0 code.
On Wed, Aug 31, 2011 at 2:01 PM, Zhao Wang wrote:
> He is probably talking about the Linux Kernel 3.0... Not the Android 3.0...
>
>
> For
He is probably talking about the Linux Kernel 3.0... Not the Android 3.0...
For all I know Android 3.0 uses 2.6.36 kernel...
On Wed, Aug 31, 2011 at 1:37 PM, mike digioia wrote:
> Where are you able to see the 3.0 source?
>
>
> On Tue, Aug 30, 2011 at 5:49 PM, Behnam wrote:
>
>> I am currently
Where are you able to see the 3.0 source?
On Tue, Aug 30, 2011 at 5:49 PM, Behnam wrote:
> I am currently moving to Android Kernel 3.0 for my development and I
> realized that adb no longer works in 3.0 kernel. I did a bit of
> digging and came across a commit that completely removes any ADB
> f
I am currently moving to Android Kernel 3.0 for my development and I
realized that adb no longer works in 3.0 kernel. I did a bit of
digging and came across a commit that completely removes any ADB
functionality from USB gadget f_adb.c. I am not sure if this has been
moved to another location or it
Dear Ramya,
They are not binary but afaik source compatible. I am 100% sure for
the SKULL driver, you can compile it for android.
For compilation you need a ARM cross compilation tool chain. One is
f.e. included in the android sources as prebuilt package. Then compile
the scull driver with ARCH=AR
On Tue, Aug 30, 2011 at 10:42 PM, parth shah wrote:
> Hi Pavan,
>
> We are using imx515 platform from freescale.
>
> We have pulled up connected with BT_EN with 1.8V. and BT_EN is connected to
> GPIO.
>
> We are making sure that before any BT activity BT_EN should go high.
>
> Is there any other r
Dear All,
For production of the device, android APKs needs to be signed. I have
created keystore as explained in
http://developer.android.com/guide/publishing/app-signing.html and signed my
APKs with that keystore.
I am doing it for eclair.
I need to know following things.
(1) Do I need to sign
Yes, it should be fine to do i2c accesses during the thread_fn handler.
You should not attempt i2c during the actual handler though as most i2c
drivers require sleeping.
When requesting the threaded irq, you can not set the handler, and just
set the thread_fn, but make sure that you use IRQF_ONE
16 matches
Mail list logo
