Bug? Loss of focus on switch to landscape

melvynadam · 02-27-07, 01:16 PM

I have an HTC Wizard and there's a bug that annoys the hell out of me. I don't know if it's a WM5 bug, or specific to this device.

Try the following:

In portrait mode, open Contacts.
Press New.
Notice that there is a flashing cursor in the Name field.
Switch to landscape by sliding out the keyboard.

If your device behaves like mine you will now have lost the focus and need to either tap the name field to return to it or press the down arrow followed by the up arrow.

This happens in calendar, notes, and tasks too.

I have two questions: am I the only one? Has anyone got a workaround?

badersk · 02-27-07, 03:49 PM

Mine does not do this, however I have pocket informant installed. I would thing it is a third party software issue. I know there are some phone dialer plugins ( to make the keys bigger) that cause this.

melvynadam · 02-28-07, 03:44 AM

Yours does not do this for the built-in calendar app? Ignoring PI and using that for a test, yours doesn't switch focus?

badersk · 02-28-07, 08:21 AM

No. I turned of PI and did as you described and it does not lose focus. What IPL SPL and OS version are you running? It will display on the splash screen when you soft reset.

melvynadam · 02-28-07, 09:07 AM

It's funny you should ask. I just flashed my ROM and was hoping this would be a side-benefit of the new ROM. No change. I went from a ROM that was a year old to IPL 2.26, SPL 2.26, GSM 02.25.11, OS 3.3.0.0.
You must be right that it's something to do with an app I have installed (although I'm running far fewer 3rd-party apps on my new ROM). Maybe it's PocketBreeze? That interfaces with all of the built-in PIM apps which exhibit the bug.

badersk · 02-28-07, 12:02 PM

Are you running one of the roms from XDA-developers. I have the V2 8page pool faria rom. I do not have any apps added like PocketBreeze. I only have PI, MS reader, ISilo and Voice command. I never use any type of today plugin.

melvynadam · 03-12-07, 10:42 AM

I have exactly the same ROM as you. Furthermore, I'm very sceptical that you've followed my procedure precisely because I've tried this on three separate devices (each running different ROMs) and the bug is present on all three. I'm convinced this is a WM5 bug and it's on every device out there.