WM 6.5 Kitchen QVGA and VGA Developer Edition

[dsi76]

I am getting frustrated with getting the Lock Screen CPR to show the information the correct way for QVGA.

Can someone upload their 240x320 and 320x240 LockScene CPRs that do the following:

- Slider on bottom, Time on top
- Upcoming appointments show below the time.

I had this working, but when there were no appointments, the time ended up being in the middle, along with a calender icon below it.

Thanks!!!!!!!!

EDIT: Actually, here is the 240x320 LockScene CPR. It seems to do what I want it to.

[gguruusa]

Originally Posted by AndrewSh

Sorry that we had necessitated you to waste your time and to disavow the messages of totally dumb outsiders
But usually I think before I write about rom cooking. And usually it's not only my private experience.....

If you want to make brash statements and sound intelligent, provide some verifiable data to back your statements up. It is understandable that the performance of a poorly designed rom can vary dramatically, boot to boot, but it is unreasonable and irrational to suggest that multiple builds of the same rom base yield different roms. In the case at hand, you can verify that your proposition (build to build makes different roms) is false by simply comparing two builds of the same rom base. Aside from different timestamps, you should find the builds are identical.

A good craftsman never blames his tools.

[bbsandkm]

Originally Posted by gguruusa

A good craftsman never blames his tools.

im a good craftman, and if i mess up ... i would blame the tools lol j/k

[focus-pl]

Hi,
Do you solved camera problem in Kaiser with wm 6.5? I'm stuck on this issue since early 211xx realses (now I use 21501). What I have: When camera works fine, Opera don't. When Opera works ok, camera don't. I've tried different OEMs, changing ddi.dll but still have the same (camera or opera).. Any solutions?

[focus-pl]

There is plenty of VGA mods.. So, time to do something in QVGA .

My QVGA .cpr mods:

Lock mod (S2U2 alike):


Honeycomb mod:



Just click thanks or/and answer my question above .

[dsi76]

Here's another issue...

Because I'm using the default WM6.5 dialer, I now have to use the default WM volume control as well. Otherwise the in-call volume will not work if you use the finger-friendly HTC Volume.

The problem is that in the Settings menu (or any menu other than the home screen), if I use the volume control, it is shifted too far to the right:




Is there a solution for this? Maybe moving the taskbar speaker icon over to the left will help (although I don't know how to do this.. will need to search!)

[jdume]

Originally Posted by focus-pl

There is plenty of VGA mods.. So, time to do something in QVGA .

My QVGA .cpr mods:

Lock mod (S2U2 alike):


Honeycomb mod:



Just click thanks or/and answer my question above .

Can you say S2U2!! JK!! Looks good man, great job!

[Zecanilis]

Originally Posted by dsi76

Here's another issue...

Because I'm using the default WM6.5 dialer, I now have to use the default WM volume control as well. Otherwise the in-call volume will not work if you use the finger-friendly HTC Volume.

The problem is that in the Settings menu (or any menu other than the home screen), if I use the volume control, it is shifted too far to the right:




Is there a solution for this? Maybe moving the taskbar speaker icon over to the left will help (although I don't know how to do this.. will need to search!)

My workarround was to change the reg key:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\TaskBa r]
"ConsistentClockOrBattery"=dword:1

This way you will get more contact space to ok/close button and you will not have that problem because the battery icon will be in every window.
I know that this was a registry key for people that whould like to click at the battery icon to see the power metter. But i like this way better...

Cheers

[vickylife007]

Originally Posted by gguruusa

If you want to make brash statements and sound intelligent, provide some verifiable data to back your statements up. It is understandable that the performance of a poorly designed rom can vary dramatically, boot to boot, but it is unreasonable and irrational to suggest that multiple builds of the same rom base yield different roms. In the case at hand, you can verify that your proposition (build to build makes different roms) is false by simply comparing two builds of the same rom base. Aside from different timestamps, you should find the builds are identical.

A good craftsman never blames his tools.

Wow! That was very harsh, yet very true. I have always get me water to boil at a hundered degree centigrade, ceteris paribus. Does anyone else have this experience?

[anryl]

Originally Posted by gguruusa

Nonsense. ROMs built from the same base are the same, regardless of what you use to cook them (errors in assembly aside).

Do u know what are u talking about ?
Did u see how are the roms coocked with the new tools .
Do u know all the new settings ?
Do not comment what u did not tried .
TY.

No more comments on this matter.

Waiting for new releasess (leaks)