Quote:
Originally Posted by Thesian
I'm an instore tech for a corporate store.
The memory leak is the caching program and I have no issue with it after using my phone all day with a Stock ROM (2.09) and running the touch today screen app.
I use my bluetooth all day. Talk for hours on it.
No customers come into my store or any of the other stores I work with experiencing this issue.
Does that mean its in your head? No. Does that make it Sprints fault or issue? Not necessarily.
I don't have your money. I'm one guy. I'm not on the phone with you. I'm talking to you outside my capacity at Sprint.
I'm sorry to say that I think some of you are off base.
For those of you that think your justified, well, thats your right.
I say buy something else if your not happy.
Thats all I'm saying. Make your money speak for you. Stick it to Sprint. Go to Verizon, or Altell. Show Sprint how they messed up.
I think you'll only be happy that you acted, but not satified with the outcome.
But who am I. I'm just some dude. So what do I know. Really? Nothing.
|
You can continue to deny that there are legitimate shortcomings based on what was advertised and with respect to the running software, but that doesn't change the fact that the issues are recognized by *Sprint* and *HTC* as problems.
Tier 1 and Tier 2 have both acknowledged to me on the phone that the horrible BT audio is a *known* issue and were both shocked with the fix for it was "no solution at this time". Tier 1 had to look it up, Tier 2 knew off of the top of his head. This was addressed in 2.16 and listed as a fix on the HTC website.
The alarm not functioning when the device goes to sleep - a know issue and a real PITA when traveling. An issue that was addressed in 2.16 and listed in the HTC website.
Lack of Rev A. when promised in Fall 07 - I know "It's coming".....we shall see when/if it does indeed come.
As we all know - 2.16 was an unmitigated disaster and was pulled from the HTC website. I spoke with Sprint regarding the new issues in 2.19 and their solution was to reinstall 2.09 and wait for a new image (Advice from Tier2 after Tier1 could not assist with the issues).
That's absolutely *outstanding* that your phone miraculously works flawlessly for you. As you can see, there are *many* people who experience terrible Bluetooth audio and obvious memory management issues.
I understand that memory is being cached for faster subsequent access to shared libraries - but when it reaches the point that I can't answer the phone if it happens to ring while I am opening / closing the screen (stuck on the redraw) then there's a problem with the scheduler not giving sufficient priority to the phone processes or not properly caching so that it has to swap out dirty pages and reload the necessary functions for the phone software.
If the BT driver from the touch can be ported over to the 6800 then we obviously have an issue with the BT driver / stack included with the 6800 ROMs. This isn't rocket science - it's software.
So far most of the techs I have spoken to on the phone have at least owned up to the fact that the device is *not* doing what I paid $585 for. It is mostly successful but has some significant flaws (BT and the memory management being the biggest) that make using the device a pain rather than a pleasure a lot of the time.
So, please, bury your head in the sand and continue to maintain that everyone else is messing up their devices and causing their own issues (although you can find them documented on phones with *zero* tweaks or changes after a hard reset here and on XDA) - I will hope that Sprint is still actively working with HTC to resolve these issues with the ROM.
In spite of your assertion - someone is at fault here. If HTC has provided flawed hardware, then it's HTC. If Sprint cannot create a truly functional ROM on the Windows Mobile base then it's Sprint (The Cingular 8125 works fine for 2 people in our office and this is a device running WM6 (came with WM5) with very similar hardware).
Regardless, Sprint has provided the phones and is the one who has to deploy them working as they were sold. Currently that is not the case for many users.