Page 6 of 10 FirstFirst 12345678910 LastLast
Results 101 to 120 of 181
  1. #101  
    Using software 1.13-ROW with Firwmare 1.43 I get a faint echo back of everthing I say. It's quite distracting. I'm going back to the latest release firmware 1.31.
  2. #102  
    Quote Originally Posted by theadient
    Can someone please test to see whether "Send Contact" via Messaging has been fixed with this new SW / FW? (This has nothing to do w/ the "Beam your own business card" functionality, which Palm support confuses w/ this issue). It's an incredibly "core" phone functionality that has been broken apparently since the days of the Treo 600 and has still not been fixed.

    To Test: In Contacts, Record Menu->Send Contact->Send With: Messaging

    Unsupported Format
    The messaging application does not support this type of item...
    Nope, this hasn't been fixed, but I've long gotten used to using Call Lookup DA for this function, so I don't miss it that much.
    V > Vx > m505 > m515 > T/T > T3 > TC > 650 > 680
    <script type="text/javascript" src="http://download.skype.com/share/skypebuttons/js/skypeCheck.js"></script>
    <a href="skype:wwgamble?call"><img src="http://mystatus.skype.com/balloon/wwgamble" style="border: none;" width="150" height="60" alt="My Skype status" /></a>
  3. hduty's Avatar
    Posts
    69 Posts
    Global Posts
    84 Global Posts
    #103  
    Quote Originally Posted by khaytsus
    Seriously? You reset as many as 3 times a day? I use my Treo all the time, using Agendus (ugh, trial, I think it's going to get buried soon), DateBk5, several large astronomy apps, TakePhone, and a bunch of little things all day long.

    The *only* time I ever reset is when either the phone goes into slow motion for whatever reason. That happens maybe once a week at worst.

    Of course, I don't run some hacky dbcache thing constantly.
    My unlocked 650 resets once every 2 months or so. I've had the slowdown two times so far. Given the posts, it seems that my 650 is much more stable than normal....
    Palm Vx (a classic) -> Palm m505 (*yawn*) -> Dell Axim (slooow...!) -> Palm TE (great) -> Qtek 9090 (great idea, lousy platform) -> Nokia 6630 (a toy) -> iMate SP3i (not bad) -> Nokia 9300 (can't sync notes!!) -> Treo 650 (awesome!) -> iPaq hw6915 (almost perfect) -> Nokia E51 (un/impressive) -> HTC Touch Enhanced (nice!) -> Samsung i780 (mousepad woes) -> HTC s740 (very good) -> Nokia E72 (RAM starved) -> HTC HD mini (...) -> Palm Pre 2
  4. #104  
    My Treo 650 (Orange UK GSM) is rock solid, with an excellent battery life, and the only resets I've had in the last few months (that I didn't trigger intentionally) have been caused by the latest 0.66h/i/j beta builds of TCPMP (I've gone back to 0.66g for now).

    I upgraded to FW 1.43 / SW 1.14 last night and have had no problems so far, although I'm yet to actually make a voicecall, so I can't pass judgement on any changes to voice quality/mic gain/etc (yet).
  5. #105  
    I did the firmware update first and tried it for awhile then did the full firmware/ROM update. Before the ROM update whenever bluetooth was on the Treo would not wake up on the first button press 95% of the time. Now it wakes up first press everytime.
  6. #106  
    Quote Originally Posted by jgm
    I did the firmware update first and tried it for awhile then did the full firmware/ROM update. Before the ROM update whenever bluetooth was on the Treo would not wake up on the first button press 95% of the time. Now it wakes up first press everytime.
    Spoke too soon. Was good for several hours but has now gone back to needing a second press of the button most of the time. Don't know why, didn't make any changes since that time. From now I refuse to say anything about how my Treo is working.
  7. #107  
    I first tried the 1.14/1.43 combo and had echoing problems so I went back to just 1.13 and 1.43 firmware 2 weeks ago and my phone has been extremely stable with improved volume (I don't use Volumecare) since then.
    I recommend just the firmware with confidence to anyone...you can always go back...and upgrading the firmware alone is not a complicated process.
  8. #108  
    Quote Originally Posted by joolsca
    I first tried the 1.14/1.43 combo and had echoing problems so I went back to just 1.13 and 1.43 firmware 2 weeks ago and my phone has been extremely stable with improved volume (I don't use Volumecare) since then.
    I recommend just the firmware with confidence to anyone...you can always go back...and upgrading the firmware alone is not a complicated process.
    I never installed the 1.14 software. I only loaded the 1.43 firmware in to the phone with the existing 1.13-ROW software release.
    I only ever made 3 calls with the 1.43 softare:
    1. I heard the (faint) echo back of everything I said on my calls.
    2. There was distortion and 'drop outs' (milliseconds), enough to make me have to have the caller repeat things several times. This is talking to someone on a landline. With 1.28 and 1.31 firmware I have nothing by crystal clear no-distorted calls nearly 100% of the time.
    3. There is NO increase in earpiece volume. I've tested it side by side with a 1.31 Firmware handset (same software) and the earpiece volume is identical. I can't comment on microphone as I have no idea. I don't use Volumecare.

    There's something wrong with 1.43. I'm back to 1.31 Firmware with 1.13-ROW software and everyting is great again.
  9. #109  
    There has to be differences in the hardware then. Some are great with 1.13/1.43 others are not. I am not surprised.
  10. #110  
    Quote Originally Posted by taylorh
    I never installed the 1.14 software. I only loaded the 1.43 firmware in to the phone with the existing 1.13-ROW software release.
    I only ever made 3 calls with the 1.43 softare:
    1. I heard the (faint) echo back of everything I said on my calls.
    2. There was distortion and 'drop outs' (milliseconds), enough to make me have to have the caller repeat things several times. This is talking to someone on a landline. With 1.28 and 1.31 firmware I have nothing by crystal clear no-distorted calls nearly 100% of the time.
    3. There is NO increase in earpiece volume. I've tested it side by side with a 1.31 Firmware handset (same software) and the earpiece volume is identical. I can't comment on microphone as I have no idea. I don't use Volumecare.

    There's something wrong with 1.43. I'm back to 1.31 Firmware with 1.13-ROW software and everyting is great again.

    Did people on the other end hear an echo as well or just on your side?
  11. #111  
    Quote Originally Posted by joolsca
    Did people on the other end hear an echo as well or just on your side?
    There was no comment of an echo and nothing on the other end that indicated to me that they noticed anything unusual. But I didn't ask. I was never asked to repeat anything.

    Also when I speak of distortion, I don't know how to characterize it. It's not bad distortion, it's very subtle. It just didn't sound right to me. As soon as I went back to 1.31 I noticed the calls were more clear. And these are calls to people I talk to frquently.
    Treo 750 (AT&T)
    Treo600->Treo650->Cing8525->Blackberry 8700c->Treo750->AT&T Tilt->Treo750->iPhone 3G
  12. #112  
    I experienced shorter battery life a less signal strength.
  13. #113  
    Quote Originally Posted by LewisL77
    Well I waited till the end of the week to post an update on my PATH experience. Remember, I only updated to fw 1.43 and I'm running a modified slimmed down version of ROM 1.13(No versa, real,tutorial,welcome,non-english lang. files).
    before: 1.43, I was running 1.31 and this is what would happen to me:
    Would start the morning with chatter running. Jump on the train, and begin watching a tv show of movie via TCPMP or listen to music via Ptunes. As the train went in and out of reception (from the speed and from the subterrain) it would slow down and freeze a bit and then comeback. Sometimes chatter would act up and try to reconnect to GPRS multiple times. And at least once a week, my treo would totally freeze up or what others call "go into slow motion", because it would respond, but it would take forever to do anything. The same thing would happen going back home, so if I remembered, I would shutdown chatter and disconnect from GPRS, and this would aleviate some of the slowdowns and total freezes, but not completely. If i left toccer running, the same thing would happen.

    After upgrading to fw 1.43, this is what happened this week:
    Started the day with chatter running. Jump on the train, and begin watching a tv show of movie via TCPMP or listen to music via Ptunes. As the train went in and out of reception (from the speed and from the subterrain), I could barely notice any delay. TCPMP would not stutter as usual. As I emerged from the PATH station and switched to Ptunes, I did not experience any total freeze ups the whole entire week. Samething going back home. I was able to just leave chatter running, since It did not complain that the GPRS connection was in and out. Please keep in mind that I have not had to soft reset this entire week(also don't use dbcache tool, I stopped a while back).

    So I think there were some significant changes made to the gsm radio software with this fw.
    This has been my take on fw 1.43 only. Please remember your experience my vary.
    Sounds great

    Thanks
    Ciao.
    Vittore
    ------------------------------------------------------------------------------------------------------------------------------------
    HS Treo 180 -> HS Treo 270 -> Palm Treo 650 GSM (1.71-1.20ENA Custom) + Treo BT Headset + TomTom 5.201 & Holux GPS 236 BT Slim
  14. #114  
    Ok, so I've been running SW1.14/FW1.43 for a few days and I've had complaints about echoing, so can I simply downgrade the firmware to FW1.31 and leave SW1.14 or do I need to drop back down to SW1.13 too?

    In other words, is anyone running SW1.14 with FW1.31 without problems?
  15. #115  
    I tried both the full 1.43/1.14 upgrade and a customized version, and in both cases Blazer behaved strangely, refusing to render certain websites. I followed the advise a of previous post and tried Xiino, with identical results. I then returned to firmware 1.43/software 1.13, and Blazer became operational again. Conclusion: Software upgrade 1.14 disables functionality of Blazer. Therefore, if Blazer is important for you, upgrade to the 1.43 firmware only, keeping software 1.13.
  16. ankur's Avatar
    Posts
    28 Posts
    Global Posts
    57 Global Posts
    #116  
    Did the full upgrade today.

    Solved the big problem i had been having. Was trying to get my unlocked GSM Treo 650 to work with my new mrHandfree Blue Perfection car kit, but the bluetooth connection was dropping after a few seconds and the Treo was hanging.

    After the firmware upgrade i paired again and this time i got a new screen on the phone, i was asked to specify if the device was a headset or a car kit. I chose car kit and then i got an instant connection. Works perfectly and i get both a signal indicator and a battery indicator on the car kit lcd.

    Havent used the phone long enough to spot anything else but the fact the car kit worked has just made me forget everything else .
  17. #117  
    FYI - based on the other thread it looks like the new version will be 1.45 and will be coming next week.

    1.45 - I hope that means they saw the issues you all were having with 1.43 and fixed them.
    Factory unlocked/unbranded GSM 650 - Tmobile; FW: 1.71; SW: 1.20-ENA; Carrier DB: 255; HW: A

    If I'm repeating what someone has already said look at how long the thread is and ask yourself if you really expect me to read the whole thing.
  18. #118  
    Cheers for the heads-up on the 1.45, rbenjami, I hadn't seen that thread. I think I'll leave things as they are (SW1.14/FW1.43) until 1.45 appears...
  19. #119  
    Quote Originally Posted by rbenjami
    FYI - based on the other thread it looks like the new version will be 1.45 and will be coming next week.

    1.45 - I hope that means they saw the issues you all were having with 1.43 and fixed them.
    I didn't say next week, It'll probably be a month
  20. #120  
    Sorry - I thought I read where someone said Nov 1.
    Factory unlocked/unbranded GSM 650 - Tmobile; FW: 1.71; SW: 1.20-ENA; Carrier DB: 255; HW: A

    If I'm repeating what someone has already said look at how long the thread is and ask yourself if you really expect me to read the whole thing.

Posting Permissions