Treo 700p Maintenance Release Expected June 4
Posted on June 2nd, 2007 by Tadd Rosenfeld
Paul Loeffler has updated the Palm blog indicating that the Treo 700p maintenance release will be available June 4th. Treo 700p users have been waiting for this release for over a year.
“The Treo 700p maintenance release (MR) is expected to be available on Monday (June 4th) for Sprint users via the palm.com website. We will post an update here on the blog with a link to the MR once it is live. We don’t have a specific date for when the 700p MR will be available for Verizon Wireless users at this time.”
Related Links
700p MR Timing message from Palm.
Treo Smartphone and Accessories Store
Filed under: Treo and Palm news
Loading ...
Yeah. 2008.
Thanks Palm. With support like this who needs warranties?
hello 700p users:
i’m in BC, Canada, and purchased the 700p this may from bell mobility. i notice in all the documentation there are references to either sprint or verizon…and this article again mentions these two companies.
i asked the servicepeople at bell which set of rules do i adhere to, sprint or verizon. they never heard such a question before, didn’t know, and claimed i was the only person in 2 years to have read the documentation and contract.
maybe someone from canada can help me in this regard.
thanks,
thewannabees.
I don’t understand why after so long a time there is no definite timeframe for releasing the MR to Verizon users.
Excuse me, what the heck is this? “We don’t have a specific date for when the 700p MR will be available for Verizon Wireless users at this time.” I hope this will end the constant lockups when and if it ever comes out for Verizon. How can something come out for one system and ignore another? Totally incompetent. The fix for this should have been out a week after the problem was discovered.
Excuse me, what the heck is this? “We don’t have a specific date for when the 700p MR will be available for Verizon Wireless users at this time.” I hope this will end the constant lockups when and if it ever comes out for Verizon. How can something come out for one system and ignore another? Totally incompetent. The fix for this should have been out a week after the problem was discovered.