[Kitchen] WVGA Touch Pro 2 Collaboration

[TMartin]

Originally Posted by william_fold

bump

So...How bout them Reds??

[sc00b4s7eve]

Originally Posted by raiderfan247365

Whos using manila 2019 and wants to post their working files ? Mucho thnks

not my work. mWalt dropping the skills.
Manila 2.5

[Sharkie405]

Are you guys lovin' the shite out of some CHT v2.0?? Simply amazing!! Thanks for that link sc00bs47eve! And of course thank you MWalt2!

Oh, I made some more Tab links that I posted here.

[sc00b4s7eve]

Originally Posted by Sharkie405

Are you guys lovin' the shite out of some CHT v2.0?? Simply amazing!! Thanks for that link sc00bs47eve! And of course thank you MWalt2!

Oh, I made some more Tab links that I posted here.

Hey, nice job on those.
And hellz yeah. santod helped me fix the Lockscreen issue I had... I still like my custom HTC_2018.

It's coming along REALLY well! Can't wait for it to go RC.

[corey1138]

can you guys refresh my memory on the caller ID fix thing. You need to use the dialer fix if you are using a non Huashan dialer 5.* right? Would you need a different fix to use the Huashan dialer 5.* on 21680?

[TMartin]

Originally Posted by corey1138

can you guys refresh my memory on the caller ID fix thing. You need to use the dialer fix if you are using a non Huashan dialer 5.* right? Would you need a different fix to use the Huashan dialer 5.* on 21680?

You need a caller id fix when you aren't using a huashan dialer on 231xx. You need some critical pieces from a 231xx build to get a huashan dialer to work on 21680. You don't need any fixes if you use the huashan dialer w/ a 231xx build.

[mwalt2]

Originally Posted by corey1138

can you guys refresh my memory on the caller ID fix thing. You need to use the dialer fix if you are using a non Huashan dialer 5.* right? Would you need a different fix to use the Huashan dialer 5.* on 21680?

You can also use amarullz's tweak and use any non-htc phone canvas.

http://forum.ppcgeeks.com/1941139-post4013.html

I also wrote a mortscript working so the proximity sensor works without an htc phonecanvas (requires mortscript, obviously ). Just save it to a .txt file and rename to a .mscr file. Then put the .mscr in \windows\startup.

While(1)
If (RegValueExists("HKLM", "System\State\Phone", "Active Call Count") = FALSE)
RegWriteDWord("HKLM", "System\State\Phone", "PSensorStatus", 0)
ElseIf (RegValueExists("HKLM", "System\State\Phone", "Active Call Count") = TRUE)
RegWriteDWord("HKLM", "System\State\Phone", "PSensorStatus", 1)
EndIf
sleep(2000)
EndWhile

What I do is cook in the Sprint default HTC PhoneCanvas, so that I can use ## codes if I ever desire. I then cab install Iconsoft PhonEx, which has an option to disable the WM Phone Canvas (it disables the HTC dialer and saves some memory). Doing this I do not need to worry about taking modules/files from different WM branches and mixing them together (just seems like a good way to get things messed up to me).

[william_fold]

Originally Posted by TMartin

So...How bout them Reds??

Well, they're doing a little better than the Indians lol

[Sharkie405]

Originally Posted by programatix

Hi guys,

One more tweak. If you want to see your carrier, edit this file,

14394200_manila
- Delete the following line

require("cril_svc")
RilWrapper = TwinRilWrapper()

- Replace

  RilWrapper.OnGSMNetworkRegisteComplete:connect(OnGSMChanged)
  RilWrapper.OnCDMANetworkRegisteComplete:connect(OnCDMAChanged)

with

_application.OnBroadcastMessageChanged:connect(UpdateCarrierNetwork)

- Replace

RilWrapper:Init()

with

UpdateCarrierNetwork()

- You can safely delete CRILService.dll from Home package and it's registry value

Anyone got this file already modified that they can post?

[shane6374]

Things sure move fast when your away for a bit! CHT 2.0, Sense 2019. I'm gonna get the TP2 back out and play! Not too much going on in Epic land yet. (I miss Sense)

Originally Posted by TMartin

So...How bout them Reds??

What about the Twins?