![]() |
2006-06-15
, 14:55
|
|
Posts: 1,245 |
Thanked: 421 times |
Joined on Dec 2005
|
#142
|
Thanks for all the help. A couple of things:
1. I changed the 770 f/w to 5.2006.13-7. This appears to make maemo-mapper work for longer but, it still fails.
2. It looks like I have 2 options (can you confirm?)
a. Update to 2006 FW and see if this fixes it. I've heard mixed comments about the 2006 SW. Has anyone with dropping out problems moved to 2006 and has it cleared their problems?
b. Try the bluetooth reset script. Is this still a valid option or does the latest maemo-mapper code try this?
Thanks.
MPH
user ALL = NOPASSWD: /usr/sbin/hciconfig hci0 reset
![]() |
2006-06-15
, 15:46
|
Posts: 39 |
Thanked: 13 times |
Joined on May 2006
@ Bonn, Germany
|
#143
|
![]() |
2006-06-16
, 07:33
|
Posts: 4 |
Thanked: 0 times |
Joined on Jun 2006
|
#144
|
![]() |
2006-06-16
, 08:24
|
|
Posts: 1,463 |
Thanked: 81 times |
Joined on Oct 2005
@ UK
|
#145
|
![]() |
2006-06-16
, 12:30
|
Posts: 223 |
Thanked: 67 times |
Joined on Jun 2006
|
#146
|
<snip>Code:rfcomm connect 4 00:12:34:56:78:90
I think you have to run the above line every time you start Maemo Mapper, unless you (with root access) use rfcomm bind instead of rfcomm connect.
![]() |
2006-06-16
, 17:29
|
|
Posts: 1,245 |
Thanked: 421 times |
Joined on Dec 2005
|
#147
|
If you have root access you can edit the file /etc/bluetooth/rfcomm.conf. Replace the sample values with your own and set bind to yes.
Then the connection will be established at each reboot.
![]() |
2006-06-16
, 20:04
|
Posts: 223 |
Thanked: 67 times |
Joined on Jun 2006
|
#148
|
Is that different from rfcomm bind?
![]() |
2006-06-16
, 20:23
|
Posts: 25 |
Thanked: 1 time |
Joined on Feb 2006
|
#149
|
![]() |
2006-06-18
, 22:33
|
|
Posts: 1,245 |
Thanked: 421 times |
Joined on Dec 2005
|
#150
|
1. I changed the 770 f/w to 5.2006.13-7. This appears to make maemo-mapper work for longer but, it still fails.
2. It looks like I have 2 options (can you confirm?)
a. Update to 2006 FW and see if this fixes it. I've heard mixed comments about the 2006 SW. Has anyone with dropping out problems moved to 2006 and has it cleared their problems?
b. Try the bluetooth reset script. Is this still a valid option or does the latest maemo-mapper code try this?
Thanks.
MPH