02/13/2012, 09:27 PM
Yes, I had that for the first few times I turned on the BlueTooth modules, (it seemed to be the expanding of some database) never could find which one...
Originally Posted by sidotij
But once it expanded to handle the new functionality it stabilized.
When I first brought over the files from the tar I had turned on BlueTooth then the phone locked up, had to reboot, pull battery, but kept turning BlueTooth off/on took I think 3 times, looking at my post...
But once it settled it settled...
As I am on webOS 2.2.4 now, I can not test, but even with webOS 2.2.4 the BlueTooth does not seem as stable as it used to be (it always turned on right away, worked with all my devices, still does, but I have read in these forums others now having issues with Ford's Sync, Headsets, Saabs, and other devices).
But the MAP function is fun and cool and they should have released it as an update like Bing MAPS and Enyo...
Put that aside, maybe the BlueTooth modules needs to be disabled/re-enabled over and over to kick in?
cp -r /var/log/message* /media/internal/
then drop into usb mode and copy the message logs and view them with notepad/textedit(use favorite text editor) it might shed light on what it is doing...
Also look to see if you have any faults in /var/log/reports?
The other thing to note when you copy all the files from the bt.tar, make sure you have no errors... If there any files not copied it will fail, all files are needed the two I noted were locked (in use, even though BlueTooth was turned off from a reboot), BluetoothMonitor and PmBtStack seems to be called via powerd.