[Kitchen] WVGA Touch Pro 2 Collaboration

[sc00b4s7eve]

Originally Posted by hthomas

I'm confused... what data arrows
Where are they?

oh, back in the day, the dialer used to control whether or not our taskbar's data arrows would grey out on an idle data connection.
I tried one of the older 5.0.612.xxxx.xxxx Huashan dialers and the data arrows in the taskbar never greyed out. Even on idle data, they were solid.

[shane6374]

Originally Posted by hthomas

CID OEM Link and Build 23136 link 6-7 posts above.

Link to Huashan Comm3Dialer

Thanks, I also don't read well while I'm at work.

[mwalt2]

The best thing I have found for phonecanvas's is to use amarullz's 'No HTC Phone Canvas' mod. With it, sense will interact with any phone canvas you want to use. So, you could use the WM default canvas or a 3rd party one. I really like using PhonEx. It has no problems with caller id screen and works fine on any 6.5.x build I've tried.

I've attached the EXT of amarullz's mod if anyone is interested. Basically, the mod changes a manila file to use ManilaDialer.exe (which amarullz wrote I think) whenever the phonecanvas is called from sense and ManilaDialer.exe dials on whatever phonecanvas is present.

[hthomas]

Thanks mwalt2.
This goes in our OEM's?
Does amarullz's 'No HTC Phone Canvas' mod work with the newer manila's (2018xxxx)?

Originally Posted by mwalt2

Yes, it's(Cookie's 2.0) currently being tested and is in a beta state.

I hear it a mind bender as a beta, I for one cant wait.

[mwalt2]

Originally Posted by hthomas

Thanks mwalt2.
This goes in our OEM's?
Does amarullz's 'No HTC Phone Canvas' mod work with the newer manila's (2018xxxx)?



I hear it a mind bender as a beta, I for one cant wait.

I attached it as an EXT package, so you may need to convert it to OEM if that's what you want. It work's fine with 2018 for me.

[Formula84]

Anyone know what I could look for that would cause my rom to act this way: I Flash gets to the RunCC and sits there continuously moving... So i disabled RunCC all together...Then I get to see the start bar at the bottom but a Orange Windows Pic from First boot get static and cursor does not move. At this point if I go to the top bar a touch the area of the taskbar the rom becomes responsive and everything works, reboot and all is perfect with the rom. Its really weird.

I am using the new OSBuilder release and dumped the Stock USC rom as I have done rprior and built with PRB kitchens (RZ and OSKitchen). I am sure my package ordering is correct and building ok, and strangest thing is that after it becomes responsive it runs great even after reboots.

[mwalt2]

Originally Posted by Formula84

Anyone know what I could look for that would cause my rom to act this way: I Flash gets to the RunCC and sits there continuously moving... So i disabled RunCC all together...Then I get to see the start bar at the bottom but a Orange Windows Pic from First boot get static and cursor does not move. At this point if I go to the top bar a touch the area of the taskbar the rom becomes responsive and everything works, reboot and all is perfect with the rom. Its really weird.

I am using the new OSBuilder release and dumped the Stock USC rom as I have done rprior and built with PRB kitchens (RZ and OSKitchen). I am sure my package ordering is correct and building ok, and strangest thing is that after it becomes responsive it runs great even after reboots.

I had the same problem when using runcc/OEMDrivers from another ROM (think it was the same ROM you used). I moved back to the Sprint 2.04 ROM, and haven't had the problem. I never did figure out how I got a progress bar that looks like runcc when I left runcc out of the ROM.

[Sharkie405]

Damn! XDA and MUI are both down...

[raiderfan247365]

whos got a working EXT for the new Opera Mini?

[pavanmaverick]

Originally Posted by raiderfan247365

whos got a working EXT for the new Opera Mini?

Here ya go. Its set up to be the default browser. You can edit the app.reg if you don't want it as default.

Opera Mini.zip

Cheers.