search

mikeweib / android-serialport-api

Automatically exported from code.google.com/p/android-serialport-api
0 stars 0 forks source link

Lost bytes #40

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. prepare a ramdisk.img with custom permissions in ueventd.rc (/dev/ttyS* 0666 
root root)
2. copy the example application to the device
3. select the loopback example

What is the expected output? What do you see instead?
Received back > 0, but all bytes sent appearing as Lost bytes 

What version of the product are you using? On what operating system?
Android 2.3.7, Kernel version 2.6.29

Please provide any additional information below.
I tried to increase the read timeout to 10s but it doesn't help.

Logcat says:
10-15 19:29:35.006: D/serial_port(1490): Opening serial port /dev/ttyS0 with 
flags 0x2
10-15 19:29:35.006: D/serial_port(1490): open() fd = 35
10-15 19:29:35.006: D/serial_port(1490): Configuring serial port
10-15 19:29:35.375: I/ActivityManager(861): Displayed 
android_serialport_api.sample/.LoopbackActivity: +406ms

after exit:

10-15 19:29:53.565: W/KeyCharacterMap(1490): No keyboard for id 0
10-15 19:29:53.565: W/KeyCharacterMap(1490): Using default keymap: 
/system/usr/keychars/qwerty.kcm.bin
10-15 19:29:53.906: D/serial_port(1490): close(fd = 35)

Original issue reported on code.google.com by ako...@gmail.com on 15 Oct 2013 at 7:30

GoogleCodeExporter commented 8 years ago 
It's worth mentioning that in the Console Demo the text typed into the Emission 
input is printed out to the console of the host machine which runs the android 
emulator.

Original comment by ako...@gmail.com on 17 Oct 2013 at 9:44