yashsingh1/xdaforums huggingface dataset:
[Nook Color General] califrag:
Okay so I came across this reddit post the other day (http://www.reddit.com/r/programming/comments/ehsf4/support_for_fullhand_multitouch_the_android_way/) and was looking at how we enabled multitouch for the nook (by adding the android.hardware.touchscreen.multitouch.xml). I saw from the link this stuff :

public static final String FEATURE_TOUCHSCREEN_MULTITOUCH
Since: API Level 7
Feature for getSystemAvailableFeatures() and hasSystemFeature(String): The device's touch screen supports multitouch sufficient for basic two-finger gesture detection.
Constant Value: "android.hardware.touchscreen.multitouch"

public static final String FEATURE_TOUCHSCREEN_MULTITOUCH_DISTINCT
Since: API Level 8
Feature for getSystemAvailableFeatures() and hasSystemFeature(String): The device's touch screen is capable of tracking two or more fingers fully independently.
Constant Value: "android.hardware.touchscreen.multitouch.distinct"

public static final String FEATURE_TOUCHSCREEN_MULTITOUCH_JAZZHAND
Since: API Level 9
Feature for getSystemAvailableFeatures() and hasSystemFeature(String): The device's touch screen is capable of tracking a full hand of fingers fully independently -- that is, 5 or more simultaneous independent pointers.
Constant Value: "android.hardware.touchscreen.multitouch.jazzhand"

If I understand correctly we are currently on 2.1 which is API Level 7... Does 2.2 enable API Level 8 and 2.3 enable API Level 9? Will we be able to enable android.hardware.touchscreen.multitouch.distinct to track more than two fingers? or possibly 'jazzhands' to enable full hand finger control?
[Nook Color General] pokey9000:
The TMA340 touchscreen controller reported both by the kernel and the TechRepublic teardown is a Cypress Semi 3rd gen TrueTouch, which according to their site supports "10+" points of touch. If you need more than 10 touch points on the screen, either you killed my father and should prepare to die, or I don't want to get anywhere near your NC.

Cypress is responsible for the kernel driver too, so up to the device layer we should have all the multitouch we could want.
[Nook Color General] ws6kid:
so now how to get 10 point multitouch.. i would been fine with 5 though.. :)

I really want to use it for some piano apps..
[Nook Color General] norkoastal:
epic post pokey... 100000 bonus points 4 u....
[Nook Color General] Bootstrap Bill:
Are there any updates on this? Is the Nook Color still limited to two simultaneous touches?

Does this also apply to the Nook Tablet and the Kindle Fire?
[Nook Color General] koopakid08:
Post your question in ONE thread.

---------------------------------
[Nook Color General] Dj-Gutz:
Sorry for the bump but I've found some interesting info

http://martinezjavier.blogspot.com/2011/09/benefits-of-open-source.html

Anybody knows more? It would be great to finally have more than 2 touch points

EDIT :

Looks like it's still being worked on :)

http://lwn.net/Articles/464200/

http://www.spinics.net/lists/linux-input/msg18281.html
[Nook Color General] martinezjavier:
Hello guys, thanks for the interest in the driver. I'm the one is modifying the original Cypress driver for upstream submission.

The Cypress TrueTouch Gen3 micro-controller are a family of micro-controllers. From this family there are micro-controllers that recognize from 2 fingers to 10.

Unfortunately the one found in the Nook is the CY8CTMA340 that only reports 2 fingers. When the third finger makes contact, the device reports as if no finger is over the screen. Once you lift up one of the fingers then the device reports 2 fingers again.

So, that means that as far as I know the 2 fingers in the Nook is NOT a software but a hardware limitation.

Since I don't have access to the hardware data-sheet I can be wrong but I'm pretty sure about this by looking at the cyttsp device behavior.

Hope it helps
[Nook Color General] Dj-Gutz:
Thanks Javier

I did some digging using your posted details on the controller and found some info that suggests it IS actually software and not hardware related

Here is a partial/preliminary data-sheet of the CY8CTMA340

http://wenku.baidu.com/view/d844c21cfc4ffe473368ab36.html?from=related

look @ the feature list it actually states that it supports up to 4 in-depended finger positions

Is the documentation wrong?

EDIT :

It seems the TMA430 is also found on HTC Surround & Mozart ( running WP7 ) , and it does support multiple fingers according to this

http://www.htcphones.net/htc-surround-and-mozart-feature-cypresss-truetouch-solutions/

EDIT 2 :

OK , Further investigation came up with this

CY8CTMA340-48LQI-01 is the specific controller found on the NC

SOURCE

http://www.elnec.com/device/Cypress/CY8CTMA340-48LQI-01+[QFN48]/

01 = 2 fingers

I Guess that's it :\

It's a HARDWARE limitation after all
[Nook Color General] koopakid08:
Dang.. Thanks for looking into that guys. I guess we will all just have to love with it then.

Sent from space
[Galaxy Tab General] dclaar:
I thought I'd start a thread on the connector pinouts. I don't have all the answers, but I've got the USB and the TV-Out Video cable (SAMTABRCA), and I've beeped them out.

Since this is a non-standard connector, it isn't clear which end is 1, so I've chosen #1 to be the farthest left pin as you are looking at the connector with the Samsung logo up.

The ground pins are all connected together, and are common between both cables.

It appears that pin 18 on the video cable tells the TAB that there's a cable connected?

Pin 23 on the USB cable doesn't seem to be connected to anything. It's probably too much to hope that it is a USB to go pin, although a floating ID pin indicates a device, while a grounded ID pin indicates a host...

I've attached photos of the business end, in the orientation I used.
[Galaxy Tab General] radoslaws:
Numbers are reversed (printed in CAR PCB)

30 Ground (in HDMI and CAR too)

29

28 Audio R (in HDMI, CAR and maybe Video cable)

27 Audio L (in HDMI, CAR and maybe Video cable)

26

25

24

23 VIDEO Composite

22

21

20

19 (Red or G or B signal in HDMI)

18 (Green or R or B signal in HDMI)

17 (Blue or R or G signal in HDMI)

16 Ground

15 Ground

14

13 VIDEO measures 12K to ground (4,3K to ground in HDMI dock only if plug audio out cable, 7,25K to ground if connect CAR dock)

12

11

10 USB +4 (maybe + inside battery)

9 USB +4

8 (conect with 7 and +5V power from USB power supply 2A HDMI and CAR)

7 (connect to 8 and passthru to 7&8 in next connector in HDMI)

6 (Passthru to next connector in HDMI dock)

5

4 USB DATA- (Passthru to next connector in HDMI dock) (in CAR connect with 3 and connect via resistor 40k and 10k to ground to external +5V - recognize power supply ?)

3 USB DATA+ (Passthru to next connector in HDMI dock)

2 (Grounded in HDMI dock)

1 (Grounded in HDMI dock)

Radek
[Galaxy Tab General] dclaar:
Well, I had a 50/50 chance...

Figures I'd get it backwards!

Now we have to figure out where to get the connector! Neither Digikey nor Mouser have this one, just the backwards iPod one! I've got an iPod connector that I got from Spark Fun, and the only way that it might possibly work is with an exacto knife.

Does the car connector or HDMI dock have any writing on the connectors?

Also, not sure what the USB +4 is? Does it connect to a USB pin? Which one?
[Galaxy Tab General] radoslaws:
CAR dock have numbers on PCB where connector is soldered.

USB +4V is maybe +5V (I measure voltage and find 3.98V)

and maybe this is not for USB ?

Maybe this is power from battery for supply external components ?

Power from USB Host (or 2A 5V power supply) to charge is connect to 7 & 8 pin.

I think TAB send MHL digital video/audio packets to HDMI dock and dock convert it to HDMI (I found Silicon Image Sil 9290 chip inside HDMI dock).

Next chip inside HDMI is micro controller 89C58RC from SST(for control Sil 9220)

Next chip is DC/DC converter 5V->3.3V for supply chips

(HDMI not working without external power from external USB host, power supply)

30 Ground (in HDMI and CAR too)

29

28 Audio R (in HDMI, CAR and maybe Video cable)

27 Audio L (in HDMI, CAR and maybe Video cable)

26

25

24

23 VIDEO Composite

22

21

20

19 (MHL out in HDMI dock )

18 (MHL out in HDMI dock )

17 (MHL out in HDMI dock )

16 Ground

15 Ground

14

13 VIDEO measures 12K to ground (4,3K to ground in HDMI dock only if plug audio out cable, 7,25K to ground if connect CAR dock)

12

11

10 ? ( about 4V maybe for supply external components )

9 (connected to 10 in CAR dock)

8 (connect with 7 and +5V power from USB power supply 2A HDMI and CAR)

7 (connect to 8 and connect to 7&8 in next connector in back HDMI dock)

6 (to next connector in back HDMI dock)

5

4 USB DATA- (Pass through to next connector in back HDMI dock) (in CAR connect with 3 and connect via resistor 40k and 10k to ground to external +5V - recognize power supply ?)

3 USB DATA+ (Pass through to next connector in HDMI dock)

2 (Grounded in HDMI dock)

1 (Grounded in HDMI dock)
[Galaxy Tab General] dclaar:
I'm bummed about pin 8, though! I was hoping it was USB-to-go, but clearly it is there to take the current for fast charging. <Sigh>

Although I'm curious about the USB connector on the HDMI doc. Any idea what can plug into it?

When I mentioned writing on the connector, I was hoping for some sort of part number. Guess just the pins are numbered. I think that getting a connector is going to be tough!
[Galaxy Tab General] radoslaws:
USB is for Computer connection and for Charging
[Galaxy Tab General] zeb crs:
USB data lines is normally used under "USB setup" to set usb high speed or low speed mode. This is just set using pullup or pulldown resistors. Many devices that uses USB for charging uses the datalines in the charger too. Like GPS's I've seen also has a pullup on one of the datalines in the charger to tell the device that it is connected to a charger only and not expect a data connection.

On some devices it also tells whic charger mode. High current or low current charging.

For pin 13 we should try to go into the source code and see if there is anything that can catch a glance of what voltages it expects (values) there for different mode selections (if it is open at all and not just a precompiled lib).

Or if it is possible to make a program that can force the Tab into deifferent modes by overriding the reading of this analog input.

We should at least make a table her on different voltages/resistance for the different modes.
[Galaxy Tab General] dclaar:
Only source I've seen is WebKit and the kernel. It's possible that there are clues in the kernel, but I'm not sure how likely that is.
[Galaxy Tab General] zeb crs:
I just tested som things here at the office today.

I took the original car holder and modified it a bit.

I soldered in wires and a 3,5mm stereo jack to get audio output without the need to plug in more cables on the holder.

I soldered the wires to pin 30(gnd),28(Right)and 27 (left)

At first try nothing happened....

The solutions to get audio out there is changing R2 from 1,6Kohm to 6,8Kohm's.

Then the tab accepts this as an audio output instead of a passive car holder.

So now the holder works better for me.
[Galaxy Tab General] vinclar:
Nice findings, hope this helps:

Here some huge photos off the tab dismantled from ifixit: http://www.ifixit.com/Teardown/Samsu...eardown/4103/1

http://guide-images.ifixit.net/igi/h5GYlFtNW5BMQhHo.huge

http://guide-images.ifixit.net/igi/a21sLFOa4ZGm1jvE.huge

Will be nice to find in the source code any related info about the controler, in the galaxy S Thebeano find something about the microusb controller to put the mobile into diferents modes, with resistors.

http://xdaforums.com/attachment.php?attachmentid=489028&d=1294967439
[Galaxy Tab General] zeb crs:
Now I have been checking a bit more in the source thanks to TheBeano's findings on the I9000.

This is the list of stuff it detects on the port.

It is detectede resistance between ground and ID pin.

//CR7 : ADC Register

#define	USB_OTG	0x00

#define	SEND_END	0x01

#define	AUDIO_REMOTE_S1_BUTTON	0x02

#define	AUDIO_REMOTE_S2_BUTTON	0x03

#define	AUDIO_REMOTE_S3_BUTTON	0x04

#define	AUDIO_REMOTE_S4_BUTTON	0x05

#define	AUDIO_REMOTE_S5_BUTTON	0x06

#define	AUDIO_REMOTE_S6_BUTTON	0x07

#define	AUDIO_REMOTE_S7_BUTTON	0x08

#define	AUDIO_REMOTE_S8_BUTTON	0x09

#define	AUDIO_REMOTE_S9_BUTTON	0x0A

#define	AUDIO_REMOTE_S10_BUTTON	0x0B

#define	AUDIO_REMOTE_S11_BUTTON	0x0C

#define	AUDIO_REMOTE_S12_BUTTON	0x0D

#define	RESERVED_ACCESSORY_1	0x0E

#define	RESERVED_ACCESSORY_2	0x0F

#define	RESERVED_ACCESSORY_3	0x10

#define	RESERVED_ACCESSORY_4	0x11

#define	RESERVED_ACCESSORY_5	0x12

#define	AUDIO_DEICE_TYPE_2	0x13

#define	PHONE_POWERED_DEVICE	0X14

#define	TTY_CONVERTER	0x15

#define	UART_CABLE	0x16

#define	CEA936A_TYPE_1_CHARGER	0x17

#define	FACTORY_MODE_BOOT_OFF_USB	0x18

#define	FACTORY_MODE_BOOT_ON_USB	0x19

#define	AUDIO_VEDIO_CABLE	0x1A

#define	CEA936A_TYPE_2_CHARGER	0x1B

#define	FACTORY_MODE_BOOT_OFF_UART	0x1C

#define	FACTORY_MODE_BOOT_ON_UART	0x1D

#define	AUDIO_DEVICE_TYPE_1	0x1E

#define	USB_OR_ACCESSORY_DETACH	0x1F

I will try to find the correct values for theese modes as well.
[Galaxy Tab General] zeb crs:
This is from TheBeano in the I9000 thread:

Here is a list of all the resistor values, from fsa9480_i2c.h in the open source code for JPM. The resistor goes from pin 4 to pin 5 of the micro USB plug (full details on how to wire this up are in this thread (http://xdaforums.com/showthread.php?t=819551)). When you connect the plug with the resistor (in Froyo) you should see some messages from the fsa9480 driver in the kernel log, which you can view with the "dmesg" command.

RID_USB_OTG_MODE,	/* 0 0 0 0 0 GND USB OTG Mode */

RID_AUD_SEND_END_BTN,	/* 0 0 0 0 1 2K	Audio Send_End Button*/

RID_AUD_REMOTE_S1_BTN,	/* 0 0 0 1 0 2.604K	Audio Remote S1 Button */

RID_AUD_REMOTE_S2_BTN,	/* 0 0 0 1 1 3.208K	Audio Remote S2 Button */

RID_AUD_REMOTE_S3_BTN,	/* 0 0 1 0 0 4.014K	Audio Remote S3 Button */

RID_AUD_REMOTE_S4_BTN,	/* 0 0 1 0 1 4.82K	Audio Remote S4 Button */

RID_AUD_REMOTE_S5_BTN,	/* 0 0 1 1 0 6.03K	Audio Remote S5 Button */

RID_AUD_REMOTE_S6_BTN,	/* 0 0 1 1 1 8.03K	Audio Remote S6 Button */

RID_AUD_REMOTE_S7_BTN,	/* 0 1 0 0 0 10.03K	Audio Remote S7 Button */

RID_AUD_REMOTE_S8_BTN,	/* 0 1 0 0 1 12.03K	Audio Remote S8 Button */

RID_AUD_REMOTE_S9_BTN,	/* 0 1 0 1 0 14.46K	Audio Remote S9 Button */

RID_AUD_REMOTE_S10_BTN,	/* 0 1 0 1 1 17.26K	Audio Remote S10 Button */

RID_AUD_REMOTE_S11_BTN,	/* 0 1 1 0 0 20.5K	Audio Remote S11 Button */

RID_AUD_REMOTE_S12_BTN,	/* 0 1 1 0 1 24.07K	Audio Remote S12 Button */

RID_RESERVED_1,	/* 0 1 1 1 0 28.7K	Reserved Accessory #1 */

RID_RESERVED_2,	/* 0 1 1 1 1 34K Reserved Accessory #2 */

RID_RESERVED_3,	/* 1 0 0 0 0 40.2K	Reserved Accessory #3 */

RID_RESERVED_4,	/* 1 0 0 0 1 49.9K	Reserved Accessory #4 */

RID_RESERVED_5,	/* 1 0 0 1 0 64.9K	Reserved Accessory #5 */

RID_AUD_DEV_TY_2,	/* 1 0 0 1 1 80.07K	Audio Device Type 2 */

RID_PHONE_PWD_DEV,	/* 1 0 1 0 0 102K	Phone Powered Device */

RID_TTY_CONVERTER,	/* 1 0 1 0 1 121K	TTY Converter */

RID_UART_CABLE,	/* 1 0 1 1 0 150K	UART Cable */

RID_CEA936A_TY_1,	/* 1 0 1 1 1 200K	CEA936A Type-1 Charger(1) */

RID_FM_BOOT_OFF_USB,	/* 1 1 0 0 0 255K	Factory Mode Boot OFF-USB */

RID_FM_BOOT_ON_USB,	/* 1 1 0 0 1 301K	Factory Mode Boot ON-USB */

RID_AUD_VDO_CABLE,	/* 1 1 0 1 0 365K	Audio/Video Cable */

RID_CEA936A_TY_2,	/* 1 1 0 1 1 442K	CEA936A Type-2 Charger(1) */

RID_FM_BOOT_OFF_UART,	/* 1 1 1 0 0 523K	Factory Mode Boot OFF-UART */

RID_FM_BOOT_ON_UART,	/* 1 1 1 0 1 619K	Factory Mode Boot ON-UART */

RID_AUD_DEV_TY_1_REMOTE,	/* 1 1 1 1 0 1000.07K	Audio Device Type 1 with Remote(1) */

RID_AUD_DEV_TY_1_SEND = RID_AUD_DEV_TY_1_REMOTE ,	/* 1 1 1 1 0 1002K	Audio Device Type 1 / Only Send-End(2) */

RID_USB_MODE,	/* 1 1 1 1 1 Open	USB Mode, Dedicated Charger or Accessory Detach */
[Galaxy Tab General] zeb crs:
Here is the table of modes:

00 - GND

01 - 2k

02 - 2k604

03 - 3k208

04 - 4k014

05 - 4k82

06 - 6k03

07 - 8k03

08 - 10k03

09 - 12k03

0A - 14k46

0B - 17k26

0C - 20k5

0D - 24k07

0E - 28k7

0F - 34k

10 - 40k02

11 - 49k9

12 - 64k9

13 - 80k07

14 - 102k

15 - 121k

16 - 150k

17 - 200k

18 - 255k

19 - 301k

1A - 365k

1B - 442k

1C - 523k

1D - 619k

1E - 1000k07 / 1002K

1F - open
[Galaxy Tab General] agentdr8:
Which pin on the dock connector side is ID?
[Galaxy Tab General] zeb crs:
http://xdaforums.com/attachment.php?attachmentid=489028&d=1294967439

This the schematic for the dock connector. This is from the phone schematics.

Pin 13 is the ID pin
[Galaxy Tab General] chetweewax:
RCA Out with Charging

Has anyone hacked up the RCA cable and the usb charging cable to make one cable that will do both? Strange that this is not available, since watching movies kills the damn thing so quick.
[Galaxy Tab General] Technomancer:
So pins 20,21 are serial port

FIRST_UNIT : 132

NO_UNITS : 1320

===============================

ID : DBDATAFS (0x17)

ATTR : RW STL SLC (0x1101)

FIRST_UNIT : 1452

NO_UNITS : 348

===============================

ID : CACHE (0x18)

ATTR : RW STL SLC (0x1101)

FIRST_UNIT : 1800

NO_UNITS : 140

===============================

ID : MODEM (0x8)

ATTR : RO SLC (0x1002)

FIRST_UNIT : 1940

NO_UNITS : 64

===============================

loke_init: j4fs_open success..

load_lfs_parameters valid magic code and version.

reading nps status file is successfully!.

nps status=0x504d4f43

load_debug_level reading debug level from file successfully(574f4c44).

reading nps status file is successfully!.

nps status=0x504d4f43

p1_process_platform: Debug Level Low

get_charger_status : 0

p1_process_platform: final P1 booting mode = 0

DISPLAY_PATH_SEL[MDNIE 0x1]is on

MDNIE setting Init start!!

vsync interrupt is off

video interrupt is off

[fb0] turn on

MDNIE setting Init end!!

LCD type: TFT PWM(CMC623)

Autoboot (0 seconds) in progress, press any key to stop

boot_kernel: Debug Level Low

FOTA Check Bit

Read BML page=, NumPgs=

FOTA Check Bit (0xffffffff)

Load Partion idx = (6)

..............................done

Kernel read success from kernel partition no.6, idx.6.

setting param.serialnr=0x3830860d 0x714900ec

setting param.board_rev=0x12

status.param_int_list.param_list[idx].value = 0

setting param.cmdline=console=ttySAC2,115200 loglevel=4

Starting kernel at 0x32000000...
[Galaxy Tab General] JamTheMan:
How did you read those data?

I am looking to hack a GTab together with an Arduino to make use of several different sensors, and am trying to figure out how to read that data. Could you give some pointers on how to make it happen?

PS. I am kinda new to this hacking part of Android, but am experienced in coding it in java.
[Galaxy Tab General] Nikropht:
Galaxy Tab Conenctors

Found a website that has Galaxy Tab Connectors:

http://shop.kineteka.com/products/199-samsung-galaxy-tab-connector.aspx

-Nik
[Galaxy Tab General] StarLog:
WOW, it has JTAG TX and RX, nice..
[Galaxy Tab General] StarLog:
They also have a SamsungTab breakout connector so we can solder wires for testing.

Very nice find.
[Galaxy Tab General] Alt.F4:
Does anyone have one of those keyboard docks? What pins does it use?

I'm guessing that the keyboard is a USB client, so that means the tab has to have host functionality exposed. (Or at least OTG) Should be possible to have USB Host functionality on the tab once we get the pins straightened out.
[Galaxy Tab General] zeb crs:
The tab has OTG possibilities. Everything in the USB driver points to that.

If You check the driver for the USB multiplexer chip in the source code You will see it.
[Galaxy Tab General] Alt.F4:
Yea, the processor inside the tab says that it has both USB Host and OTG support. (You can find a 2400+ page spec sheet floating around the net. Just Google for "S5PC110_EVT1_UM10".) What was confusing me is why the tab would only act as a USB Client when you use the standard USB cord that comes with the device. (The one shown in the OP)

Then I saw the fact that there was an official USB keyboard. I figure it must use a different set of pins than the standard USB cord. Or maybe it uses the same pins but shorts one (some) of them? I dunno. But there has to be something at the hardware level that lets that keyboard act as client, but not when I plug in a USB keyboard through the standard cable.

I'm looking for the correct pins to use to make my own cable to enable USB host on the tab. Ordering one of these (shop.kineteka.com/products/199-samsung-galaxy-tab-connector.aspx) like someone else pointed out would probably be a good idea too.
[Galaxy Tab General] StarLog:
This is one of the connectors I got, figured, it is easier to test with this one.

Once we get a stable pinout, then I will make an original small cable and connector, by soldering with super big magnefier.. lol
[Galaxy Tab General] zeb crs:
Where did You get that nifty connector from? Have to order a couple of those :-)
[Galaxy Tab General] Nikropht:
Galaxy Tab Pinout

Kineteka has now has the full Galaxy Tab Connector pinout.
[Galaxy Tab General] StarLog:
It is posted several times in this thread.

http://shop.kineteka.com/category/77-samsung-connectors.aspx
[Galaxy Tab General] zeb crs:
Ordered, soon I will be playing with it:-)

Come OTG features......
[Galaxy Tab General] beemerTPPC:
I've dismanteled my Tab keyboard dock because I'm trying to reconfigure it to have the tab in landscape instead of portrait.

It won't be easy, but in the meantime I leave here a shot of the mainboard that only has a chip:

SONIX

SN8P26L38FG

10BNATB01

Unfortunately this one is an 8 bit uC so it says nothing about the way the KB is connected. Probably it is only to manage the KB keys and the TAB-KB comunication.

http://pdf1.alldatasheet.com/datasheet-pdf/view/301693/SONIX/SN8P2602B.html

There is nothing interesting in the other side of the board so I've followed the lines TP30 and 31 and seems to go to PINS 21 and 20 respectively.

Unfortunately these PINS are not identified at this moment.
[Galaxy Tab General] mcuppens:
According to this table, pins 20 and 21 would be some kind of serial in and out.

I'm also trying to find out if this could be used for a serial connection with a GPS device. The built-in GPS works perfect to get a position, but when using XCSOAR (navigation software for gliders), there is an option to connect an external GPS device which also provides barometric pressure and position reports of other planes in the vicinity. The specifications for the dataport can be found here: http://www.flarm.com/support/manual/FLARM_DataportManual_v5.00E.pdf

Does anybody know if I can just connect the serial in/out of this GPS device to the pins 20/21 of my Tab?

Thanks for your help!
[Galaxy Tab General] staylo:
Don't connect it directly, the FLARM port is true RS232 with signals that switch between +12V -12V. If it is a serial interface on the Galaxy Tab, it will most likely be expecting 0 - 3.3V signals. You can use a converter (RS232-TTL converter) to get the signals into the right voltage range.

Might be worth asking about this on xcsoar-devel mailing list.
[Galaxy Tab General] Alt.F4:
Looks like pins 3 and 4 (USB data) go into that chip on the bottom of the picture. (Since the top pins go to the audio out, I assume those are pins 27 & 28) That is possibly discouraging. I wonder what exactly that chip does. Thanks for linking to the datasheet, but it's still hard to discern what its purpose is.

If the tab uses the standard USB data lines to connect to their keyboard dock, why does connecting a normal USB keyboard not work with the tab? I fear that the chip on that keyboard dock does some proprietary magic to allow a USB keyboard to function... Or possibly there is some proprietary driver in the stock Tab firmware which is enabled when it receives a signal from that chip? I should try flashing my Tab back to the stock image. (I have CyanogenMod on it now)

I've got one of those breakout connectors from kineteka, and I'm trying our different combinations of pins. I can confirm that I can charge the tab's battery by hooking up pin 7 to a USB power line, and pin 1 to ground. But that's all I've got at the moment. XD
[Galaxy Tab General] mcuppens:
Ok, I'll try my luck over there. Thanks for the advice...