1. stanip's Avatar
    I have been using the latest driver (.70) and found that even though it has become more BT stable and offers cleartype selection, the connection and reconnection time has become much longer. On a clean rom after hard-reset, the old driver .3060 connects via BT almost instantly (1-2 secs) but the latest driver .70 connects in 3-5 secs.

    After installing my other normal softwares and loading in PIM data...etc, the new driver takes 4-7 secs to connect while the old one takes about 2-4 secs.

    The longer and longer reconnection time slowly takes away the "almost instant-on" benefit of redfly vs. using a netbook at similiar price points. I use my redfly mainly for mails and note-taking at work. The longer reconnection time makes both tasks less effective especially after phone gets into sleep mode and try reconnect.

    Wonder if other uses have similiar issues or any suggestions for me. Thanks.
    12-25-2008 07:27 PM
  2. c1oudrs's Avatar
    On a clean rom after hard-reset, the old driver .3060 connects via BT almost instantly (1-2 secs) but the latest driver .70 connects in 3-5 secs.

    After installing my other normal softwares and loading in PIM data...
    For me its not the connect time per se, that is the problem. You said it: the problem is that after a hard reset . . .other softwares, etc. loading, the time between device loadup and redfly connect is much slower.

    So I can disconnect/connect my redfly by hitting the power button (disconnect) then hitting the redfly button (connect). Fast enough. There doesn't seem to be a problem.

    For me the problem, its like the timing is off perhaps between the device and the redfly on a soft reboot of the device, so that the redfly tries to connect, isn't able to because of a longer boot time, tries again and either connects or gives an 'unknown bluetooth error'. So that you have to try reonnecting again (which always reconnects the second time). Its not a big deal for me, but it does seem like something that the redfly team will be able to fix in the future.
    12-26-2008 04:46 AM
LINK TO POST COPIED TO CLIPBOARD