Re: Titan WM 6.1 build 20748 GPS kitchen
 

Type it in Google and it will come up....

EDIT: here is the link.....took me 2 seconds....
http://www.microsoft.com/Downloads/d...displaylang=en

Re: Titan WM 6.1 build 20748 GPS kitchen
 

Follow the tutorial in my sig from GAMedic.....

Re: Titan WM 6.1 build 20748 GPS kitchen
 

I responded to the person helping that the link they referenced was not in the thread as stated. Remember that some dont have the field of knowledge as you. We are all in need of advice/assistance thats what this forum is for. Thanks for the link

Re: Titan WM 6.1 build 20748 GPS kitchen
 

Is there a reason I'm missing that I can't click the "Battery Performance" box under the Registry category?

Re: Titan WM 6.1 build 20748 GPS kitchen
 

thanks! that worked! :)

Re: Titan WM 6.1 build 20748 GPS kitchen
 

It is automatically in the build.....

Re: Titan WM 6.1 build 20748 GPS kitchen
 

I have a new problem, I just reflashed again and everything seemed fine, but when I tried to install .net 3.5, it tells me its not intended for my device. Any help on this?

Re: Titan WM 6.1 build 20748 GPS kitchen
 

how did you try and install? did you connect your ppc to your pc and run the .exe? or copy to your device and try to run the .exe? First one is the one that should be done.

Re: Titan WM 6.1 build 20748 GPS kitchen
 

will there ever be a fix for the voicemail icon on the top bar of my xv6800, VZW. when ever i get a voicemail the notification icon pops on the top bar, however when i click it, it does nothing. before cooking a custom rom, i was able to click that icon and my phone would dial my VM. can this ever be fixed?

Re: Titan WM 6.1 build 20748 GPS kitchen
 

i am not able to connect to the data automatically. ex. i set up my mail to check every 5mins. i noticed the mail attempting a connect, but i never see the antenna icon turn into arrows. i am not useing any dialers and am aware that NONE of them working correct with the arrows. i updated the BuildOS to the latest everything, and it was only after this latest round of updates that this is happening. i'll repeat, i didnt have this issue when this rom version first came out, but since the update today, i now have this issue.