Sponsored Content
Operating Systems Linux Android Mini Review: Samsung Galaxy S (Android 2.1) v. Nokia E63 Post 302455842 by Neo on Wednesday 22nd of September 2010 01:36:29 PM
Old 09-22-2010
I've been using a Holux M-241 for the past few years with my E63 and it works great (Bluetooth).

Oddly, I read somewhere that this Samsung phone does not support off-platform GPS via Bluetooth .... !!! If it did, I would try using the Holux with the phone like I do on the E61.
 

5 More Discussions You Might Find Interesting

1. Virtualization and Cloud Computing

Mini Review: SliceHost v. Linode Customer Service

This weekend I planned to set up two OpenX servers to serve some rotating images to the forums. First, I signed up with SliceHost. Working outside of the US, SliceHost naturally required some additional information. They emailed me with 15 minutes of signing up asking for more information to... (4 Replies)
Discussion started by: Neo
4 Replies

2. Virtualization and Cloud Computing

Mini Review: SliceHost v. Linode Ubuntu 9.10 Setup

October 2010 Update: Linode Versus Slicehost – One Year Later A few days ago I posted Mini Review: SliceHost v. Linode Customer Service. At that time, I was going to cancel my account with Linode based on problems during the sign-up period. However, Linode asked me to give them another... (2 Replies)
Discussion started by: Neo
2 Replies

3. Android

can I upgrade samsung galaxy SII to android 4

I am thinking of buying samsung galaxy S II. I would like to know, does this phone capable to support ICS ? Because I am not sure if to buy now and just upgrade the phone to then next OS or should I wait to but the next phone version? (3 Replies)
Discussion started by: programAngel
3 Replies

4. BSD

Connecting a samsung galaxy siii to freebsd

I am connecting a samsung smartphone (galaxy s3) to a freebsd machine. It does not automatically mount. When plugging this machine in, the following message appears: ugen 7.2: <SAMSUNG> at usbus7 When disconnecting, the following message appears: ugen 7.2: <SAMSUNG> at usbus7 (disconnected)... (13 Replies)
Discussion started by: figaro
13 Replies

5. What is on Your Mind?

My Experience: Samsung Galaxy Phones versus the iPhone6

Just a quick note and not really a detailed review of mobile phones.... I have been a Samsung Galaxy owner since the first Galaxy S came out on the market. On a daily basis I work on two MacBook Air computers; but I wanted the openness of an Android phone; so I bought the Galaxy S, Galaxy S2,... (3 Replies)
Discussion started by: Neo
3 Replies
HCSECD.CONF(5)						      BSD File Formats Manual						    HCSECD.CONF(5)

NAME
hcsecd.conf -- hcsecd(8) configuration file DESCRIPTION
The hcsecd.conf file is the configuration file for the hcsecd(8) Bluetooth link keys/PIN codes management daemon. The hcsecd.conf file is a free-form ASCII text file. It is parsed by the recursive-descent parser built into hcsecd(8). The file may con- tain extra tabs and newlines for formatting purposes. Keywords in the file are case-sensitive. Comments may be placed anywhere within the file (except within quotes). Comments begin with the '#' character and end at the end of the line. FILE FORMAT
The hcsecd.conf file consists of a list of device entries. Each device entry defines a link key or PIN code for a remote Bluetooth device. Each remote Bluetooth device is identified by its unique BD_ADDR. The device entry device { option argument; [option argument;] } The following section describes all supported options and arguments. bdaddr BD_ADDR Specify remote device BD_ADDR for the entry. name device_name Specify user friendly name for the entry. Name is a string in straight double quotes. key link_key Specify link key for the entry. Link key is hexadecimal string up to 32 characters in length starting with '0x'. key nokey Specify no link key for the entry. pin PIN_code Specify PIN code for the entry. PIN code is a string up to 16 characters in length in straight double quotes. pin nopin Specify no PIN code for the entry. EXAMPLES
A sample hcsecd.conf file: # Default entry is applied if no better match found # It MUST have 00:00:00:00:00:00 as bdaddr device { bdaddr 00:00:00:00:00:00; name "Default entry"; key nokey; pin nopin; } # Ericsson T68 phone device { bdaddr 00:80:37:5e:4d:d4; name "Ericsson T68 phone"; key nokey; pin "0000"; # PIN code } # Dummy device device { bdaddr 00:11:22:33:44:55; name "Dummy"; key 0x00112233445566778899aabbccddeeff; # 16 bytes key pin nopin; } SEE ALSO
hcsecd(8) AUTHORS
Maksim Yevmenkin <m_evmenkin@yahoo.com> BSD
May 26, 2003 BSD
All times are GMT -4. The time now is 03:13 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy