BTLE Gatt operating on incorrect channel [36977464]

Obsolete

Bug

Status Update

No update yet.

Description

br...@gmail.com

created issue #1

Aug 12, 2013 04:34PM

On an attempt to connect to a Heartrate server that follows the BTLE specification for a HeartRate monitor, the Android BTLE stack attempts to create a channel for Gatt operations that are not on channel 4. This attempt causes the device to reject the request. The Android stack is attempting to create an L2CAP channel (presumably for data) on 0x42. The L2CAP protocol states that the Gatt/Att protocol shall take place only on channel 4.

Attached is a set of three files that are from a Frontline BTLE over the air exchange between the example manager provided in the SDK and a BTLE Heart Rate monitor. The file viewing software is available free from the Frontline web site.

deleted

Restricted

0 B

deleted

Restricted

0 B

deleted

Restricted

0 B

Comments

ed...@gmail.com <ed...@gmail.com> #2Aug 13, 2013 08:49AM

Hi there,

I'm having trouble viewing Unicode Tamil Characters in my new nexus phone

I have already changed the encoding to UTF-8 in the browser settings

eg:

http://www.bbc.co.uk/tamil/

This is really embarrassing as I did not have any issue viewing them on my iphone

Thanks,
Faheem
Hong Kong

br...@gmail.com <br...@gmail.com> #3Aug 13, 2013 12:31PM

I already did. As far as I can tell my problem is the rejection of the request to establish a dynamic L2CAP channel; it expects to use the fixed L2CAP channel 4. I have sent the traces to StoneStreetOne as well.

ed...@gmail.com <ed...@gmail.com> #4Aug 13, 2013 12:34PM

Why to StoneStreetOne? Are you using HTC Low Energy APIs?

br...@gmail.com <br...@gmail.com> #5Aug 14, 2013 09:55AM

Please support Tamil fonts in android, I am also waiting for Tamil fonts in my Nexus one, this is a serious drawback for me because most of my browsing and my friends Tweet are in Tamil, and my friends using iPhone are able to view the tamil font without any issues. please include this font.

Thanks
James

br...@gmail.com <br...@gmail.com> #6Aug 14, 2013 10:12AM

Hi,
I am HTC desire user and i would be very happy if Android starts supporting TAMIL fonts.

ed...@gmail.com <ed...@gmail.com> #7Aug 14, 2013 05:36PM

Pls do provide Unicode Tamil language support in Andriod. Many of my friends are using Tamil on there smart phones. Pls do provide Tamil unicode support.

Nexus-One
Singapore

ma...@android.com <ma...@android.com> Aug 28, 2013 05:13PM

Assigned to ma...@android.com.

br...@gmail.com <br...@gmail.com> #8Feb 12, 2014 05:41PM

Please provide support for Tamil fonts in the Android. This is really embarrassing to say that Android does not support tamil font whereas iphone is able to support. This would tempt android user to switch to iphone especially with new iphone4 now.

sc...@gmail.com <sc...@gmail.com> #9Jan 8, 2015 06:07PM

Please do support tamil fonts and iphone can able to support.

en...@gmail.com <en...@gmail.com> #10Jun 30, 2015 09:11PM

I am searching every single day to see, if there has been a update, or a new way , or somthing tweaking that i can implement to get tamil / indian laguages working in android !

Google guys .... Please get this done for us. We are waiting to develop thousands of apps !

vi...@gmail.com <vi...@gmail.com> #11Sep 6, 2015 09:36PM

hi, as you've mentioned I've installed opera mini in my HTC desire but still I cannot view Tamil letters in web pages. can anyone suggest me if settings changes required for this?

sa...@google.com <sa...@google.com> #12May 19, 2020 02:32PM

Status: Won't Fix (Obsolete)

I would love to see Tamil UNICODE support in my NexusOne.

Issue 36977464

Description

Issue summary

Comments

ed...@gmail.com <ed...@gmail.com> #2Aug 13, 2013 08:49AM

br...@gmail.com <br...@gmail.com> #3Aug 13, 2013 12:31PM

ed...@gmail.com <ed...@gmail.com> #4Aug 13, 2013 12:34PM

br...@gmail.com <br...@gmail.com> #5Aug 14, 2013 09:55AM

br...@gmail.com <br...@gmail.com> #6Aug 14, 2013 10:12AM

ed...@gmail.com <ed...@gmail.com> #7Aug 14, 2013 05:36PM

ma...@android.com <ma...@android.com> Aug 28, 2013 05:13PM

br...@gmail.com <br...@gmail.com> #8Feb 12, 2014 05:41PM

sc...@gmail.com <sc...@gmail.com> #9Jan 8, 2015 06:07PM

en...@gmail.com <en...@gmail.com> #10Jun 30, 2015 09:11PM

vi...@gmail.com <vi...@gmail.com> #11Sep 6, 2015 09:36PM

sa...@google.com <sa...@google.com> #12May 19, 2020 02:32PM

Add comment

Issue metadata