|Victor|¯`·.¸¸.·´¯`·.¸¸.- Energy ¯ |July 4| 21916|29022 | Sense 2019 / 2.1 / Titanium

[Minnesota]

Any word on the next update? Been a while

[siptang1227]

Originally Posted by Minnesota

Any word on the next update? Been a while

+1 on that lol.
I know he's like the wind and all but god darn it, I need a fix soon!!

[ST1N6R4y]

I just noticed (After using Juicy's ROM) that the stock tab isn't right. When you click a specific stock, you are supposed to see at the bottom 1D, 5D, 1M, 3M, 1Y etc but they are off the screen and I can scroll to them. I have to force it into landscape mode and then i can just see the edge of the buttons. Anyone have a fix for this or is there a different version of the stock tab that can be used in future roms?

[cesium]

hm, i got a call today, and the normal S2A screen came up. but no matter what, i wasn't able to slide the little bar. it just stayed there. it registered that i was touching the screen, as the little answer text glowed white when i touched it, but i still couldn't answer teh phone

why???

[farhaat2007]

Had a request for the next update. Can u add the fix for games on 6.5. For example, I love NFS, but doesnt work on your rom. Thanks

[yearn]

Originally Posted by farhaat2007

Had a request for the next update. Can u add the fix for games on 6.5. For example, I love NFS, but doesnt work on your rom. Thanks

BIG +1 on that, NFS is my favorite game also.

[occhris]

Originally Posted by avhokie

This utility works great for me:

http://www.freewarepocketpc.net/ppc-...ay-unlock.html

I think I figured out this screen locking bug. If you use the default screen locking mechanism which comes customized in this ROM, there appears to be an issue. I suspect a memory leak, but unable to validate because the device becomes unresponsive. I switched to the stock locking screen and no more issues for the past 3 days.

It appears some things are best left un-customized.

[brc64]

Originally Posted by occhris

I think I figured out this screen locking bug. If you use the default screen locking mechanism which comes customized in this ROM, there appears to be an issue. I suspect a memory leak, but unable to validate because the device becomes unresponsive. I switched to the stock locking screen and no more issues for the past 3 days.

It appears some things are best left un-customized.

Can you expound on this?

I use the Windows Mobile 6.5 lock screen (with the nifty slider) and an app called AutoLock or something to automatically lock the device when it goes into standby. By and large, this works fine, but I've noticed a couple of interesting glitches that seem to stem from it.

For one, 6.5 seems to have its own slide-to-answer thing that it wants to use when the phone is locked. It seems like the white s2a and the 6.5 s2a compete for each other when a call comes in. This also results in my ringtone being choppy for the first couple of seconds a call comes in. Whichever answering mechanism is actually used seems to be random.

The 6.5 lock screen isn't all bad, though, and appears to actually FIX a bug with the alarm clock. If the device is left unlocked when an alarm goes off, it seems to just immediately go into the notification area and leave you no quick way to dismiss or snooze. If the phone is locked, however, you get a similar slide-to-snooze and slide-to-dismiss pop up over the locked screen. This is good.

If there's a way to keep the 6.5 dialer from competing with the HTC dialer (I think?) when the screen is locked, I think that would solve my single biggest issue with this ROM.

[occhris]

My work enforces regular 1 hour timeouts on the device associated with its exchange policy. So when I set active sync to synchronize my work email, their policy forces me to set a regular lockout password. Even if I manually change the registry key to bypass this, upon the next scheduled active sync, the phone requires me to set a password.

After using this ROM for about two days (without adding additional software), out of the blue, when you go to use the phone, the lockout pad changes to the stock windows theme pad. The phone is unresponsive to any touch entries to type in your password so that the device will unlock. Your basically forced to reset the phone, and if you do the phone does a hard reset wiping everything out. (Simply remove and replaced battery)

By using the stock lockout mechanism, instead of the themed "WINDOWS DEFAULT" lockout screen, I don't encounter this condition. Here is how I changed the lock screen:

START -> SETTINGS -> LOCK -> type in your password -> click on the DISPLAY tab -> change to WINDOWS CLASSIC.

Originally Posted by brc64

Can you expound on this?

I use the Windows Mobile 6.5 lock screen (with the nifty slider) and an app called AutoLock or something to automatically lock the device when it goes into standby. By and large, this works fine, but I've noticed a couple of interesting glitches that seem to stem from it.

For one, 6.5 seems to have its own slide-to-answer thing that it wants to use when the phone is locked. It seems like the white s2a and the 6.5 s2a compete for each other when a call comes in. This also results in my ringtone being choppy for the first couple of seconds a call comes in. Whichever answering mechanism is actually used seems to be random.

The 6.5 lock screen isn't all bad, though, and appears to actually FIX a bug with the alarm clock. If the device is left unlocked when an alarm goes off, it seems to just immediately go into the notification area and leave you no quick way to dismiss or snooze. If the phone is locked, however, you get a similar slide-to-snooze and slide-to-dismiss pop up over the locked screen. This is good.

If there's a way to keep the 6.5 dialer from competing with the HTC dialer (I think?) when the screen is locked, I think that would solve my single biggest issue with this ROM.

[wmdunn]

When I'm in the phone app, and press menu ... one of my options is the call history. If I click on call history, it takes me to "Device Information" in settings. Any idea how to correct this? Thanks.

Edit: Well, on my fifth hard reset, using clear storage ... it started working correctly. Crazy ... lol.