Rom developers... the BT stack on the Touch works-

[dishe]

Originally Posted by jph8tr

If it doesn't plug the memory leak, it's still useless to me!

Then I suggest you move on to another device, because that's just how WM6 interacts with our hardware. The only "fixes" being addressed officially are the BT stack, and the freezes/lockups.

The Rev A sounds nice somewhere down the road, but I'm very interested in their official stance on the GPS... there have been so many rumors that didn't make sense, it was considered a pretty much dead concept.

[honan]

Originally Posted by dishe

Then I suggest you move on to another device, because that's just how WM6 interacts with our hardware. The only "fixes" being addressed officially are the BT stack, and the freezes/lockups.

The Rev A sounds nice somewhere down the road, but I'm very interested in their official stance on the GPS... there have been so many rumors that didn't make sense, it was considered a pretty much dead concept.

I wonder if all the work done by all you hard working ROM builders made them take notice. If you can/did figure out the problem why is it such a problem for them. I find it interesting that the day after you all come up with a BT fix they annouce they have a fix.

I noticed the GPS also. Question would be is that going to be aGPS? There have been so many people who have po-po'ed the thought of the GPS, I can't even hope,,,,Yet.

[willysp]

I tried the new ROM. BT works much better than other ROMs I've tried, but still a little choppy and compressed. Voices are understandable (for the first time) but still not good quality. It is usable, though - which for this phone is a big accomplishment!

I did a blind comparison by calling my wife (and then listening) from Titan, RAZR2, and Touch. Touch and RAZR2 were clearly better sounding than Titan to both of us. Then left voicemails at home number from all 3 devices. Again, Touch and RAZR2 sounded clear and like a phone call without a headset. Titan sounded artificial, choppy, noticeably compressed.

Headset is an nXZen 6000 (2.0/EDR, DSP).

[jph8tr]

Originally Posted by dishe

Then I suggest you move on to another device, because that's just how WM6 interacts with our hardware. The only "fixes" being addressed officially are the BT stack, and the freezes/lockups.

The Rev A sounds nice somewhere down the road, but I'm very interested in their official stance on the GPS... there have been so many rumors that didn't make sense, it was considered a pretty much dead concept.

WOW, that's a depressing statement! I'll still hold out a glimmer of hope that someone inside M$ is not as accepting as you of WM6's memory handling issues. I'm still keeping the Mogul, albeit with Sampson's clean WM5 ROM.

I'm shocked that Sprint mentioned the GPS at all. Maybe a bone thrown for our troubles? Hopefully, it's not a virtual bone!

Just for kicks, I'm going to play with this ROM over the extended weekend. So far the BT performance is fine and I'm not suffering any screen issues or lock ups. Unfortunately, if it dribbles away memory like all the previous WM6 ROMs it'll be back to Sampson's on Monday.

[winmobilelawyer]

Originally Posted by jph8tr

WOW, that's a depressing statement! I'll still hold out a glimmer of hope that someone inside M$ is not as accepting as you of WM6's memory handling issues. I'm still keeping the Mogul, albeit with Sampson's clean WM5 ROM.

The WM6 Memory system is not a bug nor an issue. It's the fact that HTC released a WM6 device with only 64mb of RAM. You'll notice the touch is doing absolutely FINE with the "WM6 Memory Leak."

As for the new ROM, hopefully you guys won't have to add stuff from the new rom to this fix it up ROM! Maybe the new ROM will actually solve the problems without adding new ones!

[willysp]

Originally Posted by winmobilelawyer

The WM6 Memory system is not a bug nor an issue. It's the fact that HTC released a WM6 device with only 64mb of RAM. You'll notice the touch is doing absolutely FINE with the "WM6 Memory Leak."

You're confusing 2 different things. The amount of physical memory a device contains has no bearing on whether the OS and/or apps have a virtual memory "leak". If the Titan had 1GB of physical RAM and no changes to the OS, it would still have the same "leak" - would just not be as noticeable.

[The_Lunatic]

So far this rom is working well. No bluetooth disconnects, no lock ups no dpad issues. BT quality on my end is acceptable, people on the receiving end says it sounds choppy at times but they can understand me. I use the Plantronics 510. I have a Motorola 820 that my son has been using but I'm going to get my hands on it tomorrow and test throughout the weekend. All of my usual software that I load plays nice. No complaints so far.
If I have any issues I will update. As to upcoming roms I will be happy to load them and test them. My week isnt complete without at least reloading my software once a week...

[winmobilelawyer]

Originally Posted by willysp

You're confusing 2 different things. The amount of physical memory a device contains has no bearing on whether the OS and/or apps have a virtual memory "leak". If the Titan had 1GB of physical RAM and no changes to the OS, it would still have the same "leak" - would just not be as noticeable.

I know this isnt the thread to be having this conversation. But my point was that there is no leak that this is what WinMo6 was designed to do, and I believe it was designed that way because MS assumed the latest phons would be 96mb of ram or higher.

[willysp]

Originally Posted by winmobilelawyer

I know this isnt the thread to be having this conversation. But my point was that there is no leak that this is what WinMo6 was designed to do, and I believe it was designed that way because MS assumed the latest phons would be 96mb of ram or higher.

Oh - so you're saying that it's not a memory leak, but that it's WM6 doing the normal caching that a virtual memory OS is designed to do? Perhaps ... I really don't know.

I haven't really experimented much with it (since my Titan normally gets soft resets often for other reasons), but I tend to disagree with that for the reason that I've had "out of memory" errors from the camera app only if my Titan has been running for awhile (days). If WM6 were just doing normal caching, it would release either the least recently used or oldest cached pages immediately to the camera app. Instead, it appears to think the cached memory is still actively allocated to a running process - i.e. either a mis-behaving app or an OS memory leak. Or maybe WM6 really needs more physical memory. Again, without the proper monitoring tools, I just don't know. I certainly speculate that if it's not a leak, then the problem will be worse with WM 6.1 when EVDO-A and (a)GPS are released since it's safe to assume WM 6.1 will be at least a bit more memory-hungry.

** Any WM developers out there that have access to process/memory monitoring tools in the SDK or at MSDN?

[jph8tr]

Originally Posted by winmobilelawyer

I know this isnt the thread to be having this conversation. But my point was that there is no leak that this is what WinMo6 was designed to do, and I believe it was designed that way because MS assumed the latest phons would be 96mb of ram or higher.

I could accept that M$ allowed WM6 to use more memory because that ASS-U-ME-D that the devices would have more RAM. That just means we have less RAM to use at start up. What I can't accept is a LEAK as a design feature. There is a flaw in WM6's memory management that doesn't recover all the memory used by various second party programs when they quit. For many users this will mean that they will eventually run out of RAM no matter how much RAM the system has. 128mb helps matters greatly, but it doesn't fix things at all.

WM5 phones generally start out with ~30mb and settle in at 20-24mb, WM6 starts at ~24mb and fall steadily to ~3 when a reboot is required.

Getting back to the ROM in this thread. Rock solid so far! Easily the best BT performance I've seen on my Mogul. The problem is my RAM is now at 5mb after last rebooting ~11:00PM last night.