Touch Diamond and Touch Pro beta drivers

[anon159272]

Haus:
What I was referring to was the screen showed when TF3D is on and the TP is in *landscape* view (keyboard open). This is the interface I had when using the previous driver, as opposed to the standard WinMo screen.

Laurie, can you or someone comment on this? I've never gotten any part of TF3D working (portrait or the dumbed-down landscape version) while connected to the Redfly. I thought the Redfly driver disabled TF3D entirely. When I'm connected to the Redfly I see the standard WinMo today screen along with the "My First Phone" look.

 

[Litt]

I'm at the end of my rope . . .

Okay, I'm about ready to give up on this whole thing. My TouchPro no longer connects to my Redfly. I can't update the Firmware on my Redfly. No matter what updates I do to my phone it always reads:
Firmware Version 1.4.0.72 (the software version changes with each of the million different versions I have tried).

I've soft rest, I've removed the program, I've deleted the files, I have deleted the folder, I have changed the cable. None of these work. I'm on the stock Sprint Rom.

I had the Redfly working for 2 months. I loved it. I would get positive comments from everyone who saw me using it, but now it is a brick.

Sorry if this sounds uber-negative, but I've tried everything I can think of and I am stuck (and if I have to re-install the software and soft reset my phone one more time tonight I think I might scream).

Please, someone help.

 

[Boo Radley]

I hate to say it but your best bet may be to hard reset your phone and then try putting on the latest build (72 is a bit old after all ). I recall having troubles with that build and was about ready to give up on it. In the end I just had to run the firmware cab again to get it working right. However, if you aren't able to get anything working through your TP, a hard reset may be your only option. I know from experience its a pain in the but sometimes you have to regress before you can progress.

I know that's not what you want to hear so hopefully someone else here will have a better response for you.

And on a side note, the more I use my Touch Pro the more I find the abbreviation fitting. If it weren't for my Redfly (and if Sprint had something better), I'd have ditched it by now.

 

[Litt]

Thanks, yeah the idea of a hard rest makes me shutter. I truly hope that isn't my best solution. It seems odd that after removing the program and deleting every Celio file I could find that when everything was reinstalled that the Firmware still comes up as 1.4.0.72. I've got to think there is some sort of hidden file that can be removed to help me start over. Perhaps it is all wishful thinking.

 

[mknollman]

For troubleshooting I see 2 options.

1. get ahold of someone else approved winmo phone and try to connect it to gthe RF

2. use sprite or spb backup and make an image of your TP then hard reset. install ONLY the redfly software, and try to connect. If it works you are good - if not restore the backup.

If neither of the above work I would say you have yourself a defective Redfly my friend.

 

[anon159272]

This morning after resetting I'm getting ARM11 fatal errors again out of the blue. I haven't reinstalled AE Button Plus.

oncrpc_xprtrtr.c line 674

and one other I clicked through by accident (was going too fast - I haven't had these errors in a few days so I thought 163 was fully stable on the Touch Pro without AE Button Plus). I was just getting into using my Redfly again; I wonder what's causing the conflict. I use .NET CF 3.5, and Pocket Shield, which is more of a must-have than the Redfly (!). I wish there was some explanation as to what sorts of things might cause these ARM11 fatal errors so that we could help determine what other software might be causing the conflict. It would be a lot better than trying to blindly remove and reinstall things until the problem reappears, particularly considering that at least in this case the problem disappeared for a few days and then suddenly came back (and I haven't installed anything new).

 

[mknollman]

@haus

I make the same suggestion to you as I did above:

-Backup image with Sprite, SPB Backup or the like (they do offer trials)
-Hard Reset (have faith - the backups do work - heck make 2 and store them separately - lol)
-Install only the RF stuff - VERY FIRST
-Install your required software one at a time with a soft reset each time to see if you can draw the error.
-Install as little software as possible and try it out for a week and leave out AEbutton and the other questionables. ( I know a week seems painful without the toy store, but it will be worth it to hash this out once and for all).
-If the errors come back - you will have to live with it - restore your old OS and move one
-If they are gone - some odd file somewhere was screwy and you will have to bite the bullet and just roll with the clean install. Know that in Windows uninstalling does not always really remove the entire program and put things back the way they were - especially if it as written by a mediocre coder.

PS - this time as soon as you are set up - back up then - this is now your "factory fresh" image with all your programs preinstalled and configured. This is how WinMo has to be handled as it is based in the same principles as Windows - and thus needs a clean install every 6 months to a year. I end up doing it much more often as I am a nerd and am constantly trying beta and other iffy software. Now when I kill this, thing I simply reinstall my image then either sync with my PC or sync with the Microsoft MyPhone Beta (awesome software by the way) and it is like nothing ever happened. - That was a LONG PS.
-If they stay gone -