Apache WM6 Kitchen CE OS 5.2.1908 (Build 18508.0.7.0) 071107_2 Bugs/Patches

[daveedem]

Originally Posted by verizonguy

Please give more info about your card. how big is it? SD or SDHC? Format? Fat or Fat32?
Using an adapter?

Sorry,... should have included that.

SD, 2GB, fat32. Direct slot in device if that's what you mean by adapter.

[verizonguy]

Originally Posted by daveedem

Sorry,... should have included that.

SD, 2GB, fat32. Direct slot in device if that's what you mean by adapter.

Try this please:

first get a soft reset program on your phone, you can get one free here:
http://www.freewarepocketpc.net/s.ph...rds=soft+reset

then get a registry editor for your phone, you can get one free here:
http://www.freewarepocketpc.net/ppc-...tor-v0-70.html

Open the registry editor and navigate to these keys:

[HKEY_LOCAL_MACHINE\Drivers\SDCARD\ClientDrivers\Cl ass\SDMemory_Class]
[HKEY_LOCAL_MACHINE\Drivers\SDCARD\ClientDrivers\Cl ass\MMC_Class]
in each one, find BlockTransferSize.
Change the value to 20 in hexidecimal for each of the two. Soft reset your phone using the soft reset program you downloaded and try again. Let us know how that works for you.

[luv2chill]

Originally Posted by iggy

So far f.... amazing. Do you guys ever sleep.

Just one issue, Extended ROM not visable. Have use the 6700 Hacks and Advanced Settings to enable and show the ROM, SoftReset but still not showing.

Is their a registry hack I need to set??

iggy you can either build your ROM again and this time click the "ExtROM Unlock" checkbox at the bottom of the "Carrier Customize" section or use a registry editor to modify the following entries:

[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\ TRUEFFS_DOC1]
"MountHidden"=dword:00000000

[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\ TRUEFFS_DOC1]
"Bootphase"=dword:00000002

[iggy]

Originally Posted by luv2chill

iggy you can either build your ROM again and this time click the "ExtROM Unlock" checkbox at the bottom of the "Carrier Customize" section or use a registry editor to modify the following entries:

[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\ TRUEFFS_DOC1]
"MountHidden"=dword:00000000

[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\ TRUEFFS_DOC1]
"Bootphase"=dword:00000002

Bloody hell, I can't believe I missed that.

Thanks, you guys are amazing, the registry hack worked fine.

[Lazybones]

luv2chill I see my Simple PIN bug made your list, I have updated my post with better steps to reproduce this bug.

[luv2chill]

Originally Posted by Lazybones

luv2chill I see my Simple PIN bug made your list, I have updated my post with better steps to reproduce this bug.

Kolano is the master of the bug lists but yes I was able to confirm your report by doing a soft reset with password enabled (had similar lockup problems whether it was simple pin or regular password). I could never reproduce that behavior just with a simple inactivity timeout, but I know you said that was random. But it definitely occurred after every soft reset.

I flashed back to every iteration of helmi's wm6 ROM I had and they all suffered that issue. Seems to be some sort of timeout issue... like the device is waiting for "something" once you click unlock, and when it doesn't happen in x amount of time the device gives up and proceeds anyway. That's what it "seems" like anyway--I could be way off base.

I had helmi confirm that it does not occur on the Universal (which is the closest device hardware-wise to the Apache). So it's either a driver issue or something in the registry that's causing it. Hopeully we'll get to the bottom of it soon.

[dannyppc6700]

yep. I have the sprint 6700. Sometimes it acts like that on reset. wait it out, and it goes away.

[Kolano]

There seems to be a leftover ".svn" folder in the Patches directory.

[gguruusa]

Originally Posted by Kolano

There seems to be a leftover ".svn" folder in the Patches directory.

We'll get that cleaned up. It shouldn't cause any harm, but please delete it.

[verizonguy]

Originally Posted by luv2chill

It is the Touch keyboard that is breaking autocompletion (it must be since everyone who has complained about that has installed that OEM). Does it also break if installed as a cab file?

I didn't make that OEM--have never even used that SIP so hopefully someone else who is familiar with it can jump in here. Until then I'd say if you want word completion don't include the Touch keyboard OEM.

I don't use this oem, but just took a look at it to help you guys out. This is the offending part of the package:

 
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Layouts\e0010409]
  "Layout Text"="eT9 IME"
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Layouts\e0010409]
  "Ime File"="\\windows\\eT9Ime.dll"

In order for auto completion/correction to work, you have to use the comp ime, not the et9 ime.

For completion to work, it should read:

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Layouts\e0010409]
"Ime File"="compime.dll"
"Layout Text"="COMP IME"

I'm assuming this would break the touch keyboard's features, but feel free to test it.