The Windows 10 April 2018 update has arrived! Get the new Dell XPS 15, starting at $999.99
  1. anon159272's Avatar
    Thanks to Ashby.scott01 noting that there is a new driver release (1.5.0.156). Any changelog items that are meaningful to Windows Mobile users? The increment of a minor version number would normally register as "interesting" in my book, implying some new functionality over simple bug fixes.
    08-24-2009 06:39 PM
  2. anon159272's Avatar
    Bluetooth pairing has changed....you connect via USB, then go into the redfly menu, hit the 'pair' button, which kicks you back out to the phone, then Redfly gives you a code which you have to enter on the phone. More like the traditional pairing method we would use for any other device except the newer generation of headsets for which the auto-pair sequence of 0000 works.

    Is the advantage here that this new pairing scheme will work with newer 6.1 ROMs? I'm not able to flash and do a test, but I do recall some discussion awhile back about how the RF BT connection didn't work with some 6.1 ROMs because of the way it detected that BT was actually turned on.

    Under the "Performance" tab now instead of "Image Clarity" (at least I think that's what it used to say) it now says "Image".

    Given the size of this flash file and phone CAB, I have to assume there's more going on here.
    08-25-2009 12:53 PM
  3. ckj's Avatar
    There is not a lot on the surface that has changed. As haus pointed out, Bluetooth paring now works similar to paring most other Bluetooth devices (like a headset) and you no longer have to have the phone and REDFLY connected over USB to do the initial BT pairing. Just press FN+F7 and the REDFLY will search for any BT device then you can initiate pairing with a 4-digit code. Once paired, you press only F7 as before to connect/disconnect over BT.

    Also, if you go into Settings>System you'll (temporarily for now) see two versions of the REDFLY Settings app. One is the same old one you're used to. The other is a newer graphical interface version that's not fully functional yet. Eventually (sometime before it's out of beta), the driver will only include the graphical interface version instead of the old version.

    While you may not notice many new features, under the hood this is a major update for us. We're moving from 1.4.0.xxx to 1.5.0.xxx. We're on build 156 of 1.5 so you can see we've been working on this for quite a while internally.

    It's coded to be more stable, faster over USB, and enable support for new phones and features in the future. But it's still beta right now so you may see some issues.
    08-25-2009 02:46 PM
  4. anon159272's Avatar
    Nice. I didn't realize pairing could be initiated without a cable now - that *****AWESOME*****. So far I haven't gotten the grey menubar, but I'm wondering if that's just a side effect of the post-install soft-reset. I know that's been a long-standing issue.
    08-25-2009 04:19 PM
  5. anon159272's Avatar
    FYI my today screen sometimes isn't fully drawing; it stops at the clock/date and shows nothing below that until the softkeys at the bottom. The items are still there (I can down-arrow to the "invisible" item below the clock/date and press enter and email pops up), I just can't see anything on the today screen. (Sprint Touch Pro, stock ROM.)



    Then there was this wicked cool display when I connected USB and disconnected BT without turning off the RF first:



    Turning off and back on cleared it and the RF connected normally over the cable. I would normally not switch between BT and USB in one session without turning off the RF first, though, so this is not really an issue, just thought I'd mention it as part of the testing process. (I also now get a screen like that for just a brief instant every time I turn on the RF, just before the "REDFLY" logo appears on the grey screen).
    Last edited by haus; 08-25-2009 at 04:42 PM.
    08-25-2009 04:25 PM
  6. itsy's Avatar
    Still does not seem to work with 6.5 in case anyone was wondering but otherwise looks like some good stuff in here.
    08-25-2009 05:59 PM
  7. anon159272's Avatar
    Colin, there's one more thing wrong with 156; I lost my large finger friendly menus on the TP again. This was fixed in prior driver versions so it's something that apparently got left out of this development thread. I will need to hard reset to restore them.
    08-25-2009 07:00 PM
  8. jwebb56's Avatar
    Where did you find the 1.5.9.156 beta? I only find 1.4.0.208 on their site (released today). Is the driver significantly faster in its display rate?
    08-25-2009 09:45 PM
  9. anon159272's Avatar
    Lost my HTC dialer and phone skin too...I do not recommend installing this on a Touch Pro until these issues are resolved. Maybe that's why they removed it...1.5.0.156 was on the bottom of the "tested smartphones" page where you now see 1.4.0.208. Also, for those of us with the C8, it's now not clear which file to download, as only the C7 and C8N are represented.
    08-25-2009 10:23 PM
  10. ckj's Avatar
    I apologize for any problems you may be having, it looks like the 1.5.0.156 beta build was released prematurely.

    Most phone models have no problems at all, but a few certainly are having sporadic and unpredictable issues with this beta driver. So for now, we've pulled 1.5.0.156 from the beta install website and replaced it with the previously released beta build 1.4.0.208.

    Anyone that is having problems and would like to revert back to an earlier build please contact me and I'll have a top-tier support person contact you immediately. Due to the nature of 1.5.0.156, you can't just download and install an older firmware build in the normal fashion to your REDFLY - there's a special process we need to walk you through.

    You can PM me through the WMexperts system or email me at

    colin [dot] kelly {at} celiocorp [dot] com

    or you can always call 1-888-4REDFLY and tell support you need help reverting from beta build 1.5.0.156 to 1.4.0.208

    Again, I'm very sorry, we'll get a 1.5.0.xxx build back up on the beta testing install page when it's more ready for prime time.
    08-26-2009 11:29 AM
  11. Velvis's Avatar
    Which device do I pick if I have a C8 as the beta website only lists C8N and C7 as options. Or are they all the same?
    08-26-2009 06:08 PM
  12. anon159272's Avatar
    Velvis, tech support says you can use either one, apparently. I assume that's "for now". Until they make it clear on the download page, you'll just have to ask for every release to be on the safe side.

    Note to Celio: you need to make it clear which version C8 users should use. Just in case it happens to matter one day. There are enough of us with the C8 that this will be confusing.
    08-26-2009 07:14 PM
  13. ckj's Avatar
    Sorry, I'll get the text on those pages updated to be more clear. If you have an original red C8, you can click on either C7 or C8N for now on the beta page.
    08-27-2009 11:19 AM
  14. jwebb56's Avatar
    When are the 1.5.0.x builds coming back? They were described as more responsive which would be a very good thing.
    10-23-2009 07:17 PM
LINK TO POST COPIED TO CLIPBOARD