Active Topics
-
OS2006/Maemo 2 posts? (0)
to Community by teroyk - 3 days, 13 hrs ago -
Help needed to recover from botched user config preventing boot (1)
to MeeGo / Harmattan by Halftux - 3 days, 14 hrs ago -
Maemo repository (37)
to Community by dredlok706 - 4 days, 12 hrs ago -
Brand new Nokia N9 dont power on (3)
to Nokia N9 / N950 by teroyk - 6 days, 9 hrs ago -
Mono Diablo Packages (2)
to OS2008 / Maemo 4 / Chinook - Diablo by meetpatty - 6 days, 23 hrs ago - more...
 |
|
2008-02-03
, 04:25
|
|
Posts: 102 |
Thanked: 5 times |
Joined on Dec 2007
|
#42
|
No,don't bother with the on screen keyboard. I did try that by mistake....it doesn't work. Just do everything in the exact order and make sure to hit the enter key. Sometimes you have to hit it several times. Keep trying. I was frustrated too but it finally did work!
|
|
2008-02-03
, 05:07
|
|
Posts: 28 |
Thanked: 4 times |
Joined on Aug 2007
@ Kuala Lumpur Malaysia
|
#43
|
There is a bug report on this issue at https://bugs.maemo.org/show_bug.cgi?id=2640
The issue appears to be isolated to a number of text files created in a directory (/var/lib/bluetooth/<your:bt:mac:address>/). If any of the files contains blank lines above the keyboard's MAC address, pairing won't work. For me what worked was to systematically go through each file and remove the empty lines, a process which took several attempts at pairing and then checking the files. I repeated this approach after 3 re-flashes (with and without backup). as well as on my wife's brand new N800. Both devices now recognize the iGo seamlessly.
The unfortunate news is that it's a frustrating and time-consuming undertaking. Additionally, you must have root access to the files, and either VI or nano for editing the files. And you may find that you've edited the same file numerous times. Search the forums for information on "becomeroot" and "VI."
Last edited by chrisblessing; 2008-02-03 at 05:12.
The issue appears to be isolated to a number of text files created in a directory (/var/lib/bluetooth/<your:bt:mac:address>/). If any of the files contains blank lines above the keyboard's MAC address, pairing won't work. For me what worked was to systematically go through each file and remove the empty lines, a process which took several attempts at pairing and then checking the files. I repeated this approach after 3 re-flashes (with and without backup). as well as on my wife's brand new N800. Both devices now recognize the iGo seamlessly.
The unfortunate news is that it's a frustrating and time-consuming undertaking. Additionally, you must have root access to the files, and either VI or nano for editing the files. And you may find that you've edited the same file numerous times. Search the forums for information on "becomeroot" and "VI."
Last edited by chrisblessing; 2008-02-03 at 05:12.
|
|
2008-02-03
, 20:20
|
|
Posts: 38 |
Thanked: 7 times |
Joined on Dec 2007
@ Colorado
|
#44
|
That sounded promising, chrisblessing. But I just did that: called up each file in turn:
classes
features
input
lastused
config
hidd
lastseen
names
but there WERE no empty lines. I then retried pairing. Enter passcode, enter. Enter passcode numerous times, enter numerous times. Nada.
I even tried to turn off "trusted device" - nothing.
I do have a question, though. My situation is a N800 user, upgrading from a successful pairing in 2007, to OS 2008, AND restoring from backup. Is that part of the pattern? Has anybody tried just upgrading, and NOT restoring from backup, then trying to pair?
P.S. Another thought occurred to me. What happens if you delete the bluetooth/MAC directory and try to rebuild it?
Last edited by jaslar; 2008-02-04 at 00:17.
classes
features
input
lastused
config
hidd
lastseen
names
but there WERE no empty lines. I then retried pairing. Enter passcode, enter. Enter passcode numerous times, enter numerous times. Nada.
I even tried to turn off "trusted device" - nothing.
I do have a question, though. My situation is a N800 user, upgrading from a successful pairing in 2007, to OS 2008, AND restoring from backup. Is that part of the pattern? Has anybody tried just upgrading, and NOT restoring from backup, then trying to pair?
P.S. Another thought occurred to me. What happens if you delete the bluetooth/MAC directory and try to rebuild it?
__________________
If at first you don't succeed, don't take up skydiving. - Anonymous
If at first you don't succeed, don't take up skydiving. - Anonymous
Last edited by jaslar; 2008-02-04 at 00:17.
|
|
2008-02-04
, 22:01
|
|
Posts: 2 |
Thanked: 0 times |
Joined on Feb 2008
|
#45
|
Well, I resorted to reinstalling the OS. But I tried OS2008 first. This time, I did not run my backup restore with the OS install and after rebooting, I went first to pair the keyboard (canceled the startup for restore, phone, etc). This time, the pairing works. I then restored my data and all seems well so far.
I'm glad that I got OS2008 to work because OS2007 did not work with my phone for GPRS/EDGE communications (Samsung D357).
Hopefully, this solution will work for others with this upgrade/bluetooth issue.
Thanks,
Strick9
I'm glad that I got OS2008 to work because OS2007 did not work with my phone for GPRS/EDGE communications (Samsung D357).
Hopefully, this solution will work for others with this upgrade/bluetooth issue.
Thanks,
Strick9
 |
|
2008-02-05
, 23:08
|
|
Posts: 239 |
Thanked: 53 times |
Joined on Jan 2008
@ Massachusetts
|
#46
|
Got my 4 row iGo keyboard today.
Pairing it to my N810 was a bit of a nuisance, there's something hit or miss there.
Got it working, though. When it powers down, the onscreen keyboard comes back, which is cool.
Likewise if I disconnect through the Bluetooth icon.
A little sad to see there's no Fkeys.
When the keyboard times out, it seems I have to Ctrl-FnBlue-FnGreen the keyboard,
and then Bluetooth icon|Devices|Edit|Connect|Cancel|Close|Cancel on the N810
to reconnect and get back to what I was doing.
Surely there's a better way?
Pairing it to my N810 was a bit of a nuisance, there's something hit or miss there.
Got it working, though. When it powers down, the onscreen keyboard comes back, which is cool.
Likewise if I disconnect through the Bluetooth icon.
A little sad to see there's no Fkeys.
When the keyboard times out, it seems I have to Ctrl-FnBlue-FnGreen the keyboard,
and then Bluetooth icon|Devices|Edit|Connect|Cancel|Close|Cancel on the N810
to reconnect and get back to what I was doing.
Surely there's a better way?
 |
|
2008-02-05
, 23:28
|
|
Posts: 5,478 |
Thanked: 5,222 times |
Joined on Jan 2006
@ St. Petersburg, FL
|
#47
|
Originally Posted by dubwise
It just reconnects when I press a key here. . . .
When the keyboard times out, it seems I have to Ctrl-FnBlue-FnGreen the keyboard,
and then Bluetooth icon|Devices|Edit|Connect|Cancel|Close|Cancel on the N810
to reconnect and get back to what I was doing.
Surely there's a better way?
|
|
2008-02-06
, 10:59
|
|
Posts: 223 |
Thanked: 67 times |
Joined on Jun 2006
|
#48
|
Originally Posted by chrisblessing
I found that by removing all references to the keyboards MAC address from these files I was able to repair it.
The issue appears to be isolated to a number of text files created in a directory (/var/lib/bluetooth/<your:bt:mac:address>/). If any of the files contains blank lines above the keyboard's MAC address, pairing won't work. For me what worked was to systematically go through each file and remove the empty lines, a process which took several attempts at pairing and then checking the files. I repeated this approach after 3 re-flashes (with and without backup). as well as on my wife's brand new N800. Both devices now recognize the iGo seamlessly.
The unfortunate news is that it's a frustrating and time-consuming undertaking. Additionally, you must have root access to the files, and either VI or nano for editing the files. And you may find that you've edited the same file numerous times. Search the forums for information on "becomeroot" and "VI."
Try:
cd /var/lib/bluetooth/*
grep Think *
This should list the line in the names file showing the keyboards MAC address. Using all or part of the MAC address type
grep <your MAC address> *
This will list all of the files you need to edit.
EDIT: As musikgoat points out below, you need to reboot after editing the files.
Hope this helps
Last edited by gowen; 2008-03-12 at 14:01.
| The Following 3 Users Say Thank You to gowen For This Useful Post: | ||
|
|
2008-02-06
, 13:15
|
|
Posts: 239 |
Thanked: 53 times |
Joined on Jan 2008
@ Massachusetts
|
#49
|
Originally Posted by GeneralAntilles
See, I knew there as a better way.
It just reconnects when I press a key here. . . .
__________________
.
.
---------------------------------------------
---------------------------------------------
---------------------------------------------
|
|
2008-02-08
, 04:34
|
|
Posts: 38 |
Thanked: 7 times |
Joined on Dec 2007
@ Colorado
|
#50
|
Boy, I continue to be baffled. I did find the file in which the MAC address of my keyboard was listed. To be clear, these are the steps I followed:
1. sudo gainroot
2. cd /var/lib/bluetooth/
3. ls
4. cd [mac address]
5. Look in the config file to see what Mac the keyboard is assigned
6. Edit each of the remaining files to remove that MAC address
7. Go to control panel
8. Choose Bluetooth keyboard
9. Get the keyboard flashing (Ctrl-blue fn-green fn)
10. Choose Pair
11. Select the name of the device
12. type the passcode, hit blue fn-OK a bunch of times
13. select OK
And it fails!
Grrrrrr.
1. sudo gainroot
2. cd /var/lib/bluetooth/
3. ls
4. cd [mac address]
5. Look in the config file to see what Mac the keyboard is assigned
6. Edit each of the remaining files to remove that MAC address
7. Go to control panel
8. Choose Bluetooth keyboard
9. Get the keyboard flashing (Ctrl-blue fn-green fn)
10. Choose Pair
11. Select the name of the device
12. type the passcode, hit blue fn-OK a bunch of times
13. select OK
And it fails!
Grrrrrr.
__________________
If at first you don't succeed, don't take up skydiving. - Anonymous
If at first you don't succeed, don't take up skydiving. - Anonymous
If at first you don't succeed, don't take up skydiving. - Anonymous