Reply
Thread Tools
VDVsx's Avatar
Posts: 1,070 | Thanked: 1,604 times | Joined on Sep 2008 @ Helsinki
#11
Originally Posted by amorek13 View Post
i am getting a message that "q" is not implemented
Yes 'q' isn't but ':q' is: "and :q (quit) hit enter".
__________________
Valério Valério
www.valeriovalerio.org
 
Posts: 486 | Thanked: 251 times | Joined on Oct 2009
#12
Originally Posted by amorek13 View Post
i am getting a message that "q" is not implemented
A substitute for #6 is: Esc ZZ

That is press and release Esc key, then capital Z twice.
 
amorek13's Avatar
Posts: 245 | Thanked: 32 times | Joined on Oct 2009 @ CT USA
#13
thank you guys got it to work
 
Posts: 7 | Thanked: 0 times | Joined on Dec 2009
#14
Originally Posted by VDVsx View Post
Everything seems correct, but you don't have in the first line of the file this descriptor: "[General]" ?

If your file is different, for e.g doesn't have the text comments is because it was wrongly parsed by some application, but the problem should be somewhere else.
I have all the text lines, I just didn't bother writing them down. I also have "[General]". Do you have any idea where to find the solution next?
 
VDVsx's Avatar
Posts: 1,070 | Thanked: 1,604 times | Joined on Sep 2008 @ Helsinki
#15
Originally Posted by OskariU View Post
I have all the text lines, I just didn't bother writing them down. I also have "[General]". Do you have any idea where to find the solution next?
If your headset worked before, the easier way is a reflash, I would say. You can analyze the transmitted Bluetooth packages and try to find the problem but is not easy if you don't have knowledge of the BlueZ stack.
__________________
Valério Valério
www.valeriovalerio.org

Last edited by VDVsx; 2009-12-19 at 15:00. Reason: typo
 
x61's Avatar
Posts: 932 | Thanked: 278 times | Joined on Sep 2009 @ Kentucky
#16
I am in the or similar problem. It seems my BT headset is discovered but is not showing on the phone. There is beeb sound on the headset every minute or so or whenever I tried turning on/off the bluetooth. Anybody sucessfully connect to NOKIA BH-703 BLUETOOTH HEADSET.

Here is my bluetooth conf profile:
[General]

# List of plugins that should not be loaded on bluetoothd startup
DisablePlugins = network,input,hal

# Default adaper name
# %h - substituted for hostname
# %d - substituted for adapter id
Name = Nokia N900

# Default device class. Only the major and minor device class bits are
# considered.
Class = 0x00020c

# How long to stay in discoverable mode before going back to non-discoverable
# The value is in seconds. Default is 180, i.e. 3 minutes.
# 0 = disable timer, i.e. stay discoverable forever
DiscoverableTimeout = 0

# How long to stay in pairable mode before going back to non-discoverable
# The value is in seconds. Default is 0.
# 0 = disable timer, i.e. stay pairable forever
PairableTimeout = 0

# Use some other page timeout than the controller default one
# which is 16384 (10 seconds).
PageTimeout = 8192

# Discover scheduler interval used in Adapter.DiscoverDevices
# The value is in seconds. Defaults is 0 to use controller scheduler.
DiscoverSchedulerInterval = 0

# What value should be assumed for the adapter Powered property when
# SetProperty(Powered, ...) hasn't been called yet. Defaults to true
InitiallyPowered = false

# Remember the previously stored Powered state when initializing adapters
RememberPowered = true

# Use vendor, product and version information for DID profile support.
# The values are separated by ":" and VID, PID and version.
#DeviceID = 1234:5678:abcd

# Do reverse service discovery for previously unknown devices that connect to
# us. This option is really only needed for qualification since the BITE tester
# doesn't like us doing reverse SDP for some test cases (though there could in
# theory be other useful purposes for this too). Defaults to true.
ReverseServiceDiscovery = true

# Enable name resolving after inquiry. Set it to 'false' if you don't need
# remote devices name and want shorter discovery cycle. Defaults to 'true'.
NameResolving = true
 
x61's Avatar
Posts: 932 | Thanked: 278 times | Joined on Sep 2009 @ Kentucky
#17
I am in the or similar problem. It seems my BT headset is discovered but is not showing on the phone. There is beeb sound on the headset every minute or so or whenever I tried turning on/off the bluetooth. Anybody sucessfully connect to NOKIA BH-703 BLUETOOTH HEADSET.

Here is my bluetooth conf profile:
[General]

# List of plugins that should not be loaded on bluetoothd startup
DisablePlugins = network,input,hal

# Default adaper name
# %h - substituted for hostname
# %d - substituted for adapter id
Name = Nokia N900

# Default device class. Only the major and minor device class bits are
# considered.
Class = 0x00020c

# How long to stay in discoverable mode before going back to non-discoverable
# The value is in seconds. Default is 180, i.e. 3 minutes.
# 0 = disable timer, i.e. stay discoverable forever
DiscoverableTimeout = 0

# How long to stay in pairable mode before going back to non-discoverable
# The value is in seconds. Default is 0.
# 0 = disable timer, i.e. stay pairable forever
PairableTimeout = 0

# Use some other page timeout than the controller default one
# which is 16384 (10 seconds).
PageTimeout = 8192

# Discover scheduler interval used in Adapter.DiscoverDevices
# The value is in seconds. Defaults is 0 to use controller scheduler.
DiscoverSchedulerInterval = 0

# What value should be assumed for the adapter Powered property when
# SetProperty(Powered, ...) hasn't been called yet. Defaults to true
InitiallyPowered = false

# Remember the previously stored Powered state when initializing adapters
RememberPowered = true

# Use vendor, product and version information for DID profile support.
# The values are separated by ":" and VID, PID and version.
#DeviceID = 1234:5678:abcd

# Do reverse service discovery for previously unknown devices that connect to
# us. This option is really only needed for qualification since the BITE tester
# doesn't like us doing reverse SDP for some test cases (though there could in
# theory be other useful purposes for this too). Defaults to true.
ReverseServiceDiscovery = true

# Enable name resolving after inquiry. Set it to 'false' if you don't need
# remote devices name and want shorter discovery cycle. Defaults to 'true'.
NameResolving = true
 
Posts: 7 | Thanked: 0 times | Joined on Dec 2009
#18
My love-hate relationship with technology keeps growing and growing. I now tried to flash N900 according to instructions found in a wiki and the problem seems now to be my computer's usb which does not handle flashing and N900 very well... Ok, I don't need instructions for that. I decided to live without bluetooth for a while, at least.

Do you guys think next fw update could possibly fix my BT problem?
 
VDVsx's Avatar
Posts: 1,070 | Thanked: 1,604 times | Joined on Sep 2008 @ Helsinki
#19
Originally Posted by OskariU View Post
My love-hate relationship with technology keeps growing and growing. I now tried to flash N900 according to instructions found in a wiki and the problem seems now to be my computer's usb which does not handle flashing and N900 very well... Ok, I don't need instructions for that. I decided to live without bluetooth for a while, at least.

Do you guys think next fw update could possibly fix my BT problem?
Q: Does your headset worked before with the n900 ? or never worked ? (I understood that it worked, probably miss read)
__________________
Valério Valério
www.valeriovalerio.org
 
Posts: 7 | Thanked: 0 times | Joined on Dec 2009
#20
Originally Posted by VDVsx View Post
Q: Does your headset worked before with the n900 ? or never worked ? (I understood that it worked, probably miss read)
Yep, it worked. Before that f*****g connectivity manager. So I think the problem isn't hardware.
 
Reply


 
Forum Jump


All times are GMT. The time now is 00:13.