And what error are you getting when you do hciconfig with other baud- rate configurations??
On Nov 14, 3:49 pm, Ash <ashoks...@gmail.com> wrote: > Hi Mike, > > Let me understand your problem clearly. > > You are able to get the bluetooth on with 460800/921600 baud-rate > using hciattach?? > But you want to change the baud-rate using hciconfig too?? > > On Nov 13, 7:12 am, Mike <mikebro...@gmail.com> wrote: > > > HiAsh, > > Thanks for the reply. > > Yeah I checked the hciattch.c file, there is baud rate change code for > > 460800 as well as 921600. > > And I am able to do hciattach with the above configurations but the > > hciconfig hci0 up is not working. > > Please lemme know ... > > > On Nov 12, 8:46 pm,Ash<ashoks...@gmail.com> wrote: > > > > One more thing about: > > > > "If yes please let me know how can I do that since hciconfig hci0 up > > > is > > > not working with baud rate more than 115200." > > > > To resolve this erify that you platform specific code in hciattch has > > > required code to do the baudrate change. > > > > On Nov 12, 8:42 pm,Ash<ashoks...@gmail.com> wrote: > > > > > Hi Mike, > > > > > Yes, you need to increase the baud rate, chanding bit pool value will > > > > not help you definately. Ideally high quality A2DP audio data needs > > > > 320-350Kbps of band width. For running this you would need baud-rate > > > > of 460.8Kbps which will run basic audio(80% audio data) for you, but i > > > > would suggest you to use 921.6Kbps. > > > > > Changing the baud-rate will depend platform you are using. In BlueZ > > > > baud-rate is configured using hciattach tool during bluetooth on > > > > process. hciattach has platform specific code which does the vendor > > > > specific initialization and baud-rate change. > > > > > By the way which platform are you working on? > > > > > I am not sure hci0 up would work, i will verify and come back to you. > > > > If you are working on source code you can check in hciattach, whether > > > > it is possible or not. And intial configuration for hciattach is taken > > > > from init.trout.rc, you can set the configuration in there. > > > > > On Nov 11, 7:08 am, Mike <mikebro...@gmail.com> wrote: > > > > > > Hi All, > > > > > I am working on the eclair code base. And I just started enabling > > > > > BlueZ and started working on it. > > > > > The basic profiles seems to be working fine. But When I play media on > > > > > my headset there is a time delay oocured when playing the media on > > > > > headset and hence after 2 seconds of play it stops for 2 seconds and > > > > > plays again. > > > > > During this process I saw error message "a2dp_write failed err: -110". > > > > > > 1-01 00:09:48.980: INFO/AudioHardwareALSA(1991): Initialized ALSA > > > > > PLAYBACK device AndroidPlayback_Speaker_normal > > > > > 01-01 00:09:48.980: DEBUG/AudioHardwareALSA(1991): Set PLAYBACK PCM > > > > > format to S16_LE (Signed 16 bit Little Endian) > > > > > 01-01 00:09:48.985: DEBUG/AudioHardwareALSA(1991): Using 2 channels > > > > > for PLAYBACK. > > > > > 01-01 00:09:48.985: DEBUG/A2DP(1991): ********** a2dp_write ********** > > > > > 01-01 00:09:48.990: DEBUG/A2DP(1991): bluetooth_start > > > > > 01-01 00:09:49.000: DEBUG/AudioHardwareALSA(1991): Set PLAYBACK sample > > > > > rate to 44100 HZ > > > > > 01-01 00:09:49.000: DEBUG/AudioHardwareALSA(1991): Buffer size: 4096 > > > > > 01-01 00:09:49.000: DEBUG/AudioHardwareALSA(1991): Latency: 92879 > > > > > 01-01 00:09:49.080: INFO/vold(3225): Android Volume Daemon version 2.0 > > > > > 01-01 00:09:49.465: WARN/AudioFlinger(1991): OutputTrack::write() > > > > > 0x23cc0 no more overflow buffers > > > > > 01-01 00:09:49.490: DEBUG/A2DP(1991): wait_for_start: 500575 us > > > > > 01-01 00:09:49.490: ERROR/A2dpAudioInterface(1991): a2dp_write failed > > > > > err: -110 > > > > > 01-01 00:09:49.500: WARN/AudioFlinger(1991): write blocked for 512 > > > > > msecs, thread 0x23658 > > > > > 01-01 00:09:49.500: DEBUG/A2DP(1991): ********** a2dp_write ********** > > > > > 01-01 00:09:49.705: WARN/AudioFlinger(1991): OutputTrack::write() > > > > > 0x23cc0 no more overflow buffers > > > > > 01-01 00:09:49.820: WARN/AudioFlinger(1991): OutputTrack::write() > > > > > 0x23cc0 no more overflow buffers > > > > > 01-01 00:09:49.930: DEBUG/A2DP(1991): Received BT_RESPONSE - > > > > > BT_START_STREAM > > > > > 01-01 00:09:49.930: DEBUG/A2DP(1991): Received BT_RESPONSE - > > > > > BT_NEW_STREAM > > > > > 01-01 00:09:49.930: DEBUG/A2DP(1991): wait_for_start: 431150 us > > > > > 01-01 00:09:49.930: DEBUG/A2DP(1991): poll: 20 us > > > > > 01-01 00:09:49.930: DEBUG/A2DP(1991): send: 189 us > > > > > 01-01 00:09:49.930: DEBUG/A2DP(1991): avdtp_write: 297 us > > > > > > I tried reducing the bitpool till 20 and tried but I did not see any > > > > > variation in the performance. > > > > > As of now I am using the Baud rate of 115200 should I increase the > > > > > baud rate. > > > > > If yes please let me know how can I do that since hciconfig hci0 up is > > > > > not working with baud rate more than 115200. > > > > > waiting for ur reply guys > > > > > Thnaks in Advance! -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting