yashsingh1/xdaforums huggingface dataset:
[Windows Mobile Development and Hacking General] vijay555:
chris_khho: thanks for the pic.

1. I didn't know where the photo contact was supposed to go (I've never used it), so it seems I haven't fixed it properly. Will do tonight hopefully.

2. Bottom part of the screen: I don't really know why, I tried stretching the dialler but it refuses to fill the screen. I'll have another go, and if it doesn't work, I've got a great idea to make it feel better. :)

3. No, I'm only reformatting the dialler buttons to stop them being all squashed up. The font and text placing is fixed by the dialler software internally. Although there might be ways to do it, it would be quite invasive. I'll consider playing with it, but I don't think it can be done easily.

As I said above, I think making a new front end/"skin" for the dialler would be a better solution then trying to over hack the current dialler if fonts are a major issue. I'll experiment with this idea.

Next version I'll also try to make it more generic so that it works on most more language versions. Can't promise. But this should also help with the contact photo issue.

V
[Windows Mobile Development and Hacking General] chris_khho:
GREAT V!!!!

Thanks for the reply!!!

Cheers,
[Windows Mobile Development and Hacking General] chris_khho:
A new photo to show a video calling problem.

Thanks V for your great work.
[Windows Mobile Development and Hacking General] vijay555:
Chris, I know this sounds like a poor excuse, but I was wondering what those buttons were!

When I was programming I found the 4 buttons, same size, little things, but I had no indication what they were used for (I only see the button's name, "button", which was unhelpful!). The dialler also consists of many invisible buttons, so I didn't want to mess with them until I knew what they were.

I'll get them sorted out. Video calling might be a bit tougher, since I don't have any 3g access. But I'll try to do it by "ear".

Curious thing:

Microsoft did not write its own phone dialler to be high resolution compatible, hence the scrunched up buttons.

But the video calling addon installed by the ext ROM does appear to be in roughly the right position at both resolutions even before I get around to screwing with it. Clearly some of it is high res compatible natively, some isn't!

I'll try to have a play tonight.

V

PS: Chris, can you post a screenshot of a video call in portrait mode as well, so I can verify the co-ordinates?
[Windows Mobile Development and Hacking General] BrettS:
Thanks vijay... the phone dialer issue is pretty much all that was keeping me from using VGA mode all the time. There are still some other minor issues, but this solved the big one for me.

I only have one issue with it... I'm using the resident version and whenever I switch orientations (no matter what program I'm in) the dialer screen is brought up. Is there any way to keep that from happening?

I had a couple of thoughts on that...

If you start the dialer application from another application with buttons on the bottom of the screen (So they show through when the dialer app is running) the buttons don't actually do anything. If I run another app that doesn't fill the whole screen the buttons on the app behind it do actually work. This suggests to me that the dialer app is, in fact, filling the screen, but the image is not. I wonder if it would be possible to replace the background image with a larger one.

Finally, failing that, it seems that the bottom portion of whatever is behind the dialer app simply shows through. Worst case, it might be possible to start another app to display a nice background image there, then start the phone app on top of that. Kind of kludgy, but it may work.

Thanks,

Brett
[Windows Mobile Development and Hacking General] vijay555:
BrettS: I noticed the phone pop up issue. I had a quick look at it yesterday, but it was 5.30am and I was tired so went to bed finally.

I'll have another look tonight though. It's mildly irritating but I'd like to fix it.

I noticed similar behaviour with the dead space at the bottom. I can actually space the buttons out more to fill the whole screen.

EDIT: I've just found this QVGA image:

.

and

Note the placement of the text on the dialler buttons, offset on the bottom right of each button. That's hardcoded I think.

It looks like I've done something wrong and the buttons are supposed to reach the bottom. I'll fix that.

However, try as I might, the backdrop won't fill the 640x480, so I imagine this is a problem with the built in dialler skin. I know some people have made 3rd party skins, so this might be addressed that way.

The current version is beta, worked on far too late into the night... my head was hurting from the number of nested enumerations I had to do to achieve this much :(

Keep the feedback coming in and I'll try and get the release smoothed off.

V
[Windows Mobile Development and Hacking General] zpdy:
1) I dont't care if the dialpad will be in english or hebrew iI just want it fixed, you cant't do version that overwrite the old dialpad (even if it will chage it to english)?

2) you cant't release a dll? cuz iI mad cab with all DLL and ozVGA and iI put it on ExtendedROM...

3) 1 bug but i'm sure you saw it cuz you can see on your screen shots, in vga mode the dialpad not fit all screen (down side).

Thanx anyway dude
[Windows Mobile Development and Hacking General] chris_khho:
Hi V,

2 additional issues...

I disable the spb close button for cprog.exe, vjbigphone.exe and vjbigphoneres.exe already but when I rotate the screen, the VGA phone screen has gone. I can activate by pressing your programme again most of the time (sometimes cannot...)

See the attached screen, the number "3" button seem to be shifted in both portrait and landscape modes.
[Windows Mobile Development and Hacking General] vijay555:
Guys, v0.5 has been posted: see the first post.

It now repositions all buttons. It may reposition too many now, so please test, test with videophone, test with caller id etc.

V0.5 also fixes the wireless manager once it's been loaded (you must load it before VJBigPhoneRes, or force it to be fixed by changing orientation; I only fix the windows on change of orientation).

Some other bugs fixed. Please test and discuss.

V
[Windows Mobile Development and Hacking General] vijay555:
guys, i've just noticed that v0.5 screws up with smart dialler enabled. i'll fix this tomorrow. for now just disable the smart dialer option in your phone menu or wait for next fix.

sorry!

v
[Windows Mobile Development and Hacking General] chris_khho:
Definitely NO sorry....

You've done a great job. Thanks for everything.

Cheers,
[Windows Mobile Development and Hacking General] BrettS:
Thanks for the update:) I'm very happy now that it doesn't switch back to the dialer app every time I rotate the screen.

For some reason, however, the new version doesn't appear to update my Wireless Manager. I'm using the resident version and I've tried to start it before starting Wireless Manager, after starting Wireless Manager. I've tried to rotate the screen with Wireless Manager on top and without it on top, yet it doesn't have any effect. I'm not sure if I'm missing something or if there's another problem.

I was using version .3 last night and a few times while I was on the phone my 'END' button disappeared. If I rotated the screen it came back, however. I haven't seen the problem yet with .5, so it may already be fixed, but i haven't used the phone much with .5 yet either. I'll let you know if I see it happen again.

Thanks again,

Brett
[Windows Mobile Development and Hacking General] Azhad:
To fix the background in landscape mode, put the attached file in \windows\

It replace the original backgroud, work in both VGA and QVGA mode
[Windows Mobile Development and Hacking General] vijay555:
Thanks Brett.

v0.5 has a problem with the Speed Dialler (the 1980's hunk of poo that does predictive dialling). I'll get around to fixing that hopefully tonight.

What concerns me is that the more generic fix I'm using now (to facilitate an international version), rather than the more targetted method used in <0.5, might be "correcting" some other buttons that don't need correcting.

eg, the video call buttons are all provided by a HTC addon, and are not internal to the dialler. However, it seems that as they are an external app, they might already be correctly positioned I think. However, someone needs to make a video call and tell me either way. I have a great face for radio, so no video calls for me until Bladerunner :(

The wireless manager. Hmm.

Ahh, just noticed that myself. It only seems to fix the wireless manager when it's the current app on screen. pooh, will fix that tonight. I'm such an idiot :oops:

How are the other dialler buttons? I've now correctly positioned them (they were shifted up slightly in <0.5, but now comparing them to the QVGA dialler they are in the correct position by ratio).

The backdrop painting issue is a bugger. I can think how to correct it, but it's going to be intensive and require quite invasive programming. I might just live with it. I think it could be corrected if someone makes a new dialler pad skin, which I think Buzzdev.net's boys have done. Will look into this later.

In the words of Johnny-Five, "more input"

V

PS I haven't had much sleep
[Windows Mobile Development and Hacking General] vijay555:
Azhad: great! thank god it was so easy!

Don't you also have to resize the bkgnd_port.bmp file? I did both just to be sure.

Phew, my solution would have been a sledgehammer to crack a nut, requiring hooking and subclassing and blah blah blah!

I never realised skinning the pad was so easy, all the dlr*.bmp buttons. Perhaps if we purposely offset the dialler images to account for the text in the bottom right they would look better. Look into that later.

Thanks again! We're moving in the right direction now. I'll update screenshots later.

V
[Windows Mobile Development and Hacking General] Azhad:
Yup :D

It' just the video call button, hardcoded in phcanrc.dll or tapres.dll I can't remember just now...

The other are in \windows

For the text...

in HKLM\Security\phone\Skin\Landscape\text and HKLM\Security\phone\Skin\Portrait\text I think you can set the font...
[Windows Mobile Development and Hacking General] vijay555:
I edited my post before your reply. Read and bask in my gratitude. I hate subclassing...

V
[Windows Mobile Development and Hacking General] Azhad:
And I edited mine before yours :D
[Windows Mobile Development and Hacking General] vijay555:
hmm, HKLM\Security\phone\Skin\Landscape\text is empty.

The others make for interesting reading.

Can we change the font? That'd be bonzer!

V
[Windows Mobile Development and Hacking General] Azhad:
For now I can make all the text in the dialer disappear, by adding some value in HKLM\ .... \landscape\text, but I don't think it can be usefull :D
[Windows Mobile Development and Hacking General] vijay555:
Perhaps this holds text for foreign languages?

Anyone verify if there's anything under this key?

We really need an offset, not just changing the text though I guess.

V
[Windows Mobile Development and Hacking General] rb32:
vijay555: Thank you for your great work!

I just checked in on my German MDA Pro with all T-Mobile settings.

Under HKLM/Security/phone/Skin/dialer/landscape

are a lot of entries. I believe the most is the T-Mobile Skin.

Currently I don't have an idea how to export them to a textfile. For typing it is to much.

Iwould like to support the german translation. Also there is a question in my head, wether it is possible to use the service which is switching from Landscape to Portrait if you rotate the screen as trigger for rerun of your program?
[Windows Mobile Development and Hacking General] vijay555:
rb32: rotating the screen does trigger my program to fix the phone, call progress screen and wireless manager. If it's not doing it not, there's a bug to fix, but that's the idea. The phone dialler gets reset to broken every time you rotate, so my program starts itself and fixes the phone. In theory!

You don't need to export your registry.

Just check

HKLM\Security\phone\Skin\Landscape\text

and see if there is anything in there.

Can you tell me what the phone is called in german. So when you start the phone program, what is the name in the titlebar?

V
[Windows Mobile Development and Hacking General] Azhad:
DONE!!!!!!!!

Big letter and centered

BEFORE starting to modify the registry, reset in SEvga,

then in OzVga open the settings and add " HKLM\Security\Phone\Skin\ " in Registry (To keep separate settings in Qvga and VGA)

Then reset in VGA mode.

under HKLM\Security\Phone\Skin\Dialer\landscape\dialbutton

create the following DWORD

majorFlags = 5

minorFlags = 5

majorRCMLStyle = 33

minorRCMLStyle = 23

under HKLM\Security\Phone\Skin\Dialer\landscape\text

textRCMLStyle = 33

under HKLM\Security\Phone\Skin\Dialer\landscape\talkendbutton

textRCMLStyle = 33

under HKLM\Security\Phone\Skin\Dialer\landscape\VerbButton

textRCMLStyle = 33

the same for HKLM\Security\Phone\Skin\Dialer\portrait

under HKLM\Security\Phone\Skin\PROGRESS\landscape

create a new key named "text"

and this dword into it

textRCMLStyle = 33

under HKLM\Security\Phone\Skin\PROGRESS\landscape\talkendbutton

textRCMLStyle = 33

under HKLM\Security\Phone\Skin\PROGRESS\landscape\VerbButton

textRCMLStyle = 33

the same for HKLM\Security\Phone\Skin\PROGRESS\portrait

using ozVGA I think we can keep 2 separate settings for VGA and QVGA

Azhad
[Windows Mobile Development and Hacking General] vijay555:
Azhad, amazing. How the hell did you get those keys? If it's top secret, PM me eh? (if you update the reg any futher, can you send me a copy of the reg file so I can cab it up. Thanks)

I've packed the new files up into cabs:

Download this cab to fix the button text (it puts text in the middle) and this file to fix the backdrop painting issue by putting a new backdrop in your \windows\ folder

I'm working on a new version of VJBigPhoneRes...

Amazing work: this is what XDA Dev is about... Thanks Azhad!

I think we still need to increase the size of the numbers on the buttons if possible.

Current look:
[Windows Mobile Development and Hacking General] rilot:
Fantastic work Vijay All of us VGAers owe you a debt of gratitude.

One thing though. Occasionally the app complains that it can't find the phone when I soft reset. I am using an English O2 XDA Exec.
[Windows Mobile Development and Hacking General] vijay555:
I've seen the bug rilot. Working on it :?

V
[Windows Mobile Development and Hacking General] Azhad:
Opsss...

I keeped editing my post...

use the new key, is wayyy better :)

Azhad
[Windows Mobile Development and Hacking General] vijay555:
Ok, latest button fix and backdrop cabs as supplied by Azhad:

this cab to fix the button text (it puts text in the middle) and this file to fix the backdrop painting issue by putting a new backdrop in your \windows\ folder

Current look:

Thanks all.

V
[Windows Mobile Development and Hacking General] SiliconS:
@ vijay: Do these latest versions work correctly if the Voice Dial system isn't installed? I didn't install any of the OEM CAB files after my last reboot, and I don't see a Voice Dial button on my dialler. Just the Call History button.

What will I see if I try this latest version? Just curious to know whether this will put a VD button there even though I don't have VD. ;)
[Windows Mobile Development and Hacking General] Azhad:
BEFORE installing the cabs, reset in SEvga, then in OzVga open the settings and add " HKLM\Security\Phone\Skin\ " in Registry (To keep separate settings in Qvga and VGA)

Then reset in VGA mode and install the cabs.

If you don't do so, the dialer in qVGA get all scrambled

Azhad
[Windows Mobile Development and Hacking General] vijay555:
SiliconS: I've not installed VD on my Universal yet.

I'll have to put it on my list of things to do. I can be fairly sure that it WON'T position the button correctly, but I can only tell you once I've installed it. Sigh, so much to do.

NOTE that the recent cabs are just fixes for the text position, not an update to VJBigPhone, which is currently at v0.5. I'm working on the next version now :(

V
[Windows Mobile Development and Hacking General] Azhad:
To keep settings separated for VGA and qVGA you can also install this two reg file.

Azhad
[Windows Mobile Development and Hacking General] SiliconS:
But your screenshots have the VD button showing? I guess this is why I'm curious. I don't want VD ;) so I guess I'd rather your prog didn't force the (useless) Voice Dial one to appear if the Voice Dial functionality isn't installed.

Just a suggestion, nothing more. :)

Do you think you'll eventually be able to publish an all-in-one solution that fixes the registry, adds the background image, and does the necessary OzVGA tweaks to allow the dialler to work in both QVGA and VGA? Your app is very cool and a great step forward for the community but the dialler layout isn't a problem for me so I haven't bothered installing your latest versions. If it became an all-in-one tool though I think there'd be a beer or two coming your way cos it would be a set-it-and-forget-it sorta thing that just worked. :)
[Windows Mobile Development and Hacking General] vijay555:
Oh sure: I was debating whether to "go public" with a work in progress or just fire it out when it's finished. But this is an app that requires wider testing than most, so I made the early beta available.

Azhad's registry work is genius, so hopefully I'll iron out some bugs tonight and put out the next version. We'll keep working and tweaking until it's all done, and then the whole lot, registry, backdrops and all will be cabbed and packed for clean use.

So obviously the current phase is only for testing if you're available to, but not a v1.0...

I don't drink or smoke (or much else I guess :)) but once we're done, it'll just be nice to get some sleep!

Oh, regarding the voice dial stuff: VD means voice dial right? I haven't installed voice dial. We've got a video button, installed from the ext rom, and that's fixed. Where is the voice dial button?

V
[Windows Mobile Development and Hacking General] SiliconS:
Holy crapola! The backdrop file is 602KB!! Is that correct? Why so big?
[Windows Mobile Development and Hacking General] vijay555:
yeah, that got me too. Shoot, maybe they should be 256 colours?

Let me check and update the cab. Give me a mo.

V
[Windows Mobile Development and Hacking General] Azhad:
ops.. I have already corrected this (photoshop don't save in 8bit mode if you don't index the image) tomorrow, from work, I post the new version (32kb)
[Windows Mobile Development and Hacking General] SiliconS:
The original landscape backdrop that Azhad posted was just 32KB. :?

Page 2 of this thread.
[Windows Mobile Development and Hacking General] SiliconS:
Forgive me so many small posts together. Just trying it all out.

So the install process is:

Import Azhad's registry files (does it make any difference which resolution or orientation the machine is in? Mine's in VGA landscape)

Open backdrop CAB

Open VJBigPhone CAB

Have I got that right?
[Windows Mobile Development and Hacking General] vijay555:
SiliconS, Azhad uncompressed images are the same size as mine. There are two images though, one for portrait and one for landscape. He said the same one can be used for both I think, but I've just scaled up the two originals and resaved at 256 colours. Yep, 300k a piece, give me a jpg any day.

I tried saving with RLE compression but they're not compatible, so 600k it is I think,

I suggest ASAP we all move to a smaller sized backdrop, but that's the original scaled up, nothing more.

Your install routine is correct.

For now VJBigPhoneRes works by trying to fix the phone the first time you load it, and then each time you rotate the screen.

Likewise the Wireless Manager. So ideally you want the phone and the wireless manager both loaded before you load VJBigPhoneRes. It's not lethal, it just won't attempt to fix the Wireless Manager until you load it.

With the phone, I actually load the phone if it's not loaded and fix it in the background.

However, I can't fix the call progress screen until you've gone into that screen once, (because the call progress screen doesn't exist to be fixed until you've gone into that screen at least once). I'll see if I can address this later.

It sounds complicated, but in normal use, it should just work.

Note that it doesn't work with the smart dialler right now. I'll fix that momentarily.

V
[Windows Mobile Development and Hacking General] Azhad:
vijay555 with the cab installation can you append a value to an existing registry value?

For the ozvga reg tweak you have to append to:

HKLM\SOFTWARE\oz\Vga\Registry\BranchesArray the value " ;HKLM\Security\Phone\Skin\ "

Azhad
[Windows Mobile Development and Hacking General] Azhad:
It work like a charm with the smart dialing...

Azhad
[Windows Mobile Development and Hacking General] Azhad:
Uhmmm, I think we can use .png changing the appropriate reg key (bmpNormal)

Azhad
[Windows Mobile Development and Hacking General] SiliconS:
Hmm. I'm confused. I just downloaded the CAB file from your site, vijay (bottom of the VJBigPhone page), and while I get the memory-resident version (i.e. the phone redraws when orientation changes), it doesn't have the bubble buttons and the phone comes to the foreground when the orientation is changed. I thought the latest version had these things fixed. The text size isn't changed either - it's still small, like Azhad's reg fixes haven't worked.

Do I have an old version? Or do I need to import the backdrop CAB as well? I left that out until a smaller version is available. Maybe it's that which sets the button style and allows the text size to be changed?
[Windows Mobile Development and Hacking General] vijay555:
SiliconS: the version on my website was v0.4. I updated to v0.5 yesterday, but didn't update my webpage because internally it was very different and I didn't want people to be left without a marginally working version (0.4), while this thread is more bleeding edge so v0.5 was released here, in the very first post of this thread.

Download 0.5 from here:

http://www.vijay555.com/vj/releases/vjbigphone/VJBigPhonev5.cab

The bubble buttons etc are entirely independant of VJBigPhone. Are your buttons the flat style? I had the same issue, you haven't installed the customisations contained in your Ext rom, which i only did reluctantly when I got told off.

Can't remember which cab it is. If someone tells me I'll host/post it.

After you've installed 0.5, bubble buttons cab from ext rom, and Azhad's reg fixes, you should have the bubble button corrected center font dialler!

I had trouble installing my own reg fix cab. If you've got one, use a registry editor to directly import the registry file that Azhad posted (12k?), or make the changes manually. It's quite easy, just copy and paste the same setting 6 times or so.

The backdrop cab. Hmm, not much I can do about the size. How big are the originals in your windows directory?

V
[Windows Mobile Development and Hacking General] rb32:
The phone is called Telefon on the German MDA Pro.

To the registry, I have under HKLM\Security\phone\Skin only to keys:

Dialer and Progress and below them a i have then Landscape and Portrait.
[Windows Mobile Development and Hacking General] vijay555:
Finally fixed my problematic activesync problem. FYI to all if your having incedible incredible pains and use ZoneAlarm.

Did you remember to set your "Windows Mobile Based Device" network connection to the "trusted" zone.

Sigh.

Should help development along a bit.

V