02-13-2009 06:19 PM
28 12
  1. bioart#WP's Avatar
    So it's been over a month since the last driver... is there still some development going on? or is there an assumption on Redfly's part that it is good enough for now?

    I'd love to see some progress... pretty please?

    01-22-2009 02:04 PM
  2. cplush#WP's Avatar
    did you not see the announcements at CES?
    01-22-2009 02:48 PM
  3. anon159272's Avatar
    I would rather see development time spent on fixing known issues than building new products. But I'm biased - I already bought my Redfly.
    01-22-2009 09:08 PM
  4. cplush#WP's Avatar
    i agree with you there. There are some bugs (RFstart....) that i wish would get fixed, but the emergance of new products will help the company in the longer run and hopefully allow them to be able to afford a larger support staff LOL
    01-22-2009 09:38 PM
  5. wodin's Avatar

    I've actually put my upgrade from a Touch to a Thouch Pro on hold until the TP drivers are working better. Who knows, I might even wait until my contract expires like I should anyway.
    01-23-2009 01:43 PM
  6. bioart#WP's Avatar
    I'd argue that having stable drivers should be as important (or more) than new products. You don't want to end up with a reputation of being a company with "almost works" products. If they can't show an amazing experience on phones, what guarantee is there that the other products will be good?

    First build a stable and loyal fan-base and then live off them. So far, there are lots of fans, but many of us are just losing faith that this will be the product we thought it was going to be when we bought it... It is a nice red color, but I don't need another paperweight.

    I still love the idea and the hardware... but it is just not usable in production.
    01-24-2009 06:27 PM
  7. cplush#WP's Avatar
    true, (but mine would be a black paperweight LOL)....in my case the lag with Docs to go(word only....excel is lightening fast with typing....go figure) and the crashing of RFstart are starting to become annoying the more i use the unit...but overall it is great.
    01-24-2009 06:56 PM
  8. ckj's Avatar
    We're still actively working on the beta drivers. RFstart and other bugs are on the list. One big issue too is with Opera 9.5 which we're pretty confident we can pull off and is currently under development. We don't think it fair to call a phone that ships with Opera 9.5 "fully supported" until Opera works so those phones will likely stay in beta until that happens.

    Make sure to send any bug reports to support@celiocorp.com and reference the beta driver so they can log bugs.
    01-26-2009 07:50 PM
  9. jwebb56's Avatar
    Colin, do you have an estimate on when the EPIX camera bug will be fixed (either with a new beta or final EPIX driver)?
    01-26-2009 08:01 PM
  10. ckj's Avatar
    Sorry, no word jwebb56 on the next beta build release date yet or if the EPIX camera bug will be addressed. That's a nasty problem that we're painfully aware of.
    01-26-2009 08:10 PM
  11. bioart#WP's Avatar

    I'm happy to hear we are not forgotten. I had to take a hiatus from using the redfly as I somehow got into a crash at reboot cycle where every reboot would result in a crash that left the phone unstable (no audio on calls/etc). Removing the redfly driver (72) fixed it (only thing that changed). I look forward to trying the new version.

    01-27-2009 11:50 PM
  12. mknollman's Avatar
    I cannot get my RF to connect to my Touch Pro via BT at all. But via cable it is great.
    01-28-2009 08:13 PM
  13. ckj's Avatar
    mknollman, what carrier are you on?
    02-03-2009 06:50 PM
  14. ckj's Avatar
    BTW, there will be a new beta build posted in about two weeks. That build should include some significant changes for all of the beta phones.
    02-03-2009 07:48 PM
  15. mknollman's Avatar
    I am on Verizon. Still as stated before, great using it with usb but get error when trying to authorize the BT address. It says I need to turn on BT eventhough it is already on. Tried disconnecting, BT off then back on, then reconnecting, and all kinds of other shuffles but no dice.
    02-03-2009 08:32 PM
  16. xraider13's Avatar
    I'm with you all the way.

    Though we paid for a primetime product, we're only getting the opening act. The promise is in the future, but call me selfish...I want the good stuff now. BTW- I think Celio should probably give Redfly early adopters like us free licenses on their upcomig software "Redfly" terminal that was shown at CES. That would be a nice concession for those of us helping them work out their bugs.
    02-04-2009 09:04 PM
  17. cplush#WP's Avatar
    shouldnt have bought it if the driver for your phone was unavailible/still in beta and had some bugs. thats what you get.
    02-04-2009 09:24 PM
  18. mknollman's Avatar
    I had mentioned that in the TP Beta Driver thread. When I bought my RF I had a Mogula and it worked flawlessly. I stated that we all need to be patient as no one was ever promised any kind of a timeline for the release of the driver. the only reason I menioned my issue is because I was asked. So far I think Celio has done well in developing these drivers. I don't know if "thats what you get" it quite right, but we all need to be patient.
    02-04-2009 10:26 PM
  19. cplush#WP's Avatar
    yeah, that was worded wrong. there are 180+ WM phones, and with 6.1 upgrades out and new phones being announced that number is even larger. it takes time and they are slowly getting it together, i just dont like the "give me free stuff cause i bought something that is in beta and it doesnt work perfectly' attitude...
    02-04-2009 10:47 PM
  20. xraider13's Avatar
    FYI- I'm not on a beta driver. I'm using one of the "supported" phones and OS versions. Even so, there are bugs. It's not even that there are so many, but the few are very annoying and even deters me from using.

    It is definitely the software because I have hard reset my phone twice and with Redfly being the only new app loaded, it's still buggy. Celio should do their due dilligence, and if it's not ready, then keep it in beta...but that's not the case in my situation, because I'm using a Sprint Touch w/ WM6.1 and is "supported".

    I've even reached out to Customer Support, and the answers I've gotten like "you'll need to reset your phone" just don't jive with the $300+ that I spent for an otherwise dumb terminal.
    02-04-2009 11:55 PM
  21. xraider13's Avatar
    Also, I'm not asking for free stuff for nothing. I think it's a fair concession as a work around until the hardware is more optimal. At the end of the day, give me free stuff is fair when all I've been given is something that doesn't work as advertised.

    If you don't have this problem, then you're lucky. But I don't think I'm out of line given my situation.
    02-04-2009 11:58 PM
  22. ckj's Avatar
    xraider13 I'll have someone contact you. The great majority of Sprint Touch users don't have problems, but every once in a while, a Touch does some strange things with the REDFLY driver on it.
    02-05-2009 12:38 AM
  23. ckj's Avatar
    New beta build (No. 93) will be posted tomorrow. See this post.
    02-12-2009 05:38 PM
  24. ckj's Avatar
    I cannot get my RF to connect to my Touch Pro via BT at all. But via cable it is great.
    mknollman, try the new beta build 93 when it's posted on Friday and let me know if you're still having problems with that Verizon Touch Pro.
    02-12-2009 07:30 PM
  25. anon159272's Avatar
    Is anyone using the beta drivers for phones *not* on the beta list? I'm running WM Pro 6.1 on my 800w and I'd love to try out the latest improvements once build 93 posts, but I don't want to brick my Redfly before I anticipate needing it next week.
    02-13-2009 01:53 PM
28 12