View Single Post
  #502 (permalink)  
Old 01-23-2010, 12:02 AM
mswlogo's Avatar
mswlogo
VIP Member
Offline
Location: MA, USA
 
Join Date: Jun 2007
Posts: 1,330
Reputation: 970
mswlogo knows their stuffmswlogo knows their stuffmswlogo knows their stuffmswlogo knows their stuffmswlogo knows their stuffmswlogo knows their stuffmswlogo knows their stuffmswlogo knows their stuff
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: How to get iGo8 run on TP2 with TTS enable and 2009 NA Maps (step by step guide)

For those stuck on TTS I may have found some data on this.

I have been fighting the same problem with iGuidance.

I think there is a finite number of handles to the sound system and there are too many widgets that hold their handle open. Or don't properly release it when done.

Voice Command is one culprit and I disable all Announcements. But Voice Command is not the only trouble maker.

The SMS Messaging also breaks it.

I can freshly boot start iGuidance and it will work perfectly.

Then shut down iGuidance.

Send myself one text message and wait for it to come back.

Then start iGuidance and TTS is broken again.

Shutdown iGuidance

and kill the Process HTC Messaging (Messaging_Client.exe)

Then iGuidance works again.

I have even tried reverting to Sense Ui 2.5 1921 (the one with out landscape) same problem.

I've disabled Native HTC Messaging and went back to Native WM (tmail.exe) same problem. Just kill that task and it works.

I even tried disabling ALL sound notifcations and still persists. I think they still grab the sound handle and use up that resource.

So my current fix is in QuickMenu I removed hiding Messaging_Client.exe from the process list. Before I start iGuidance I just kill it.

If iGuidance grabs it's resources first, Messaging_Client still works fine and so will iGuidance.

Energy ROM didn't used to have this problem but it does on his latest Jan 20th ROM.

I think things are on the edge of just using too many handles.

One person mentioned running cleanRAM first and that makes iGo work. IT may be killing a dormant process holding a handle or two.

I think this proceblem can happen on any of these tools.

But it's odd how it's always TTS that gets hit. They may be using the same TTS software and it may be dumb in how it tries to get a handle if the first attempt fails.
__________________
EVO 4G, Stock Sprint ROM, ProClip in Car, Sony HBH-300.
Reply With Quote
This post has been thanked 3 times.