Helmi Official AKU 3.5 Kitchen 1.0.2 Bugs / Patches

[fitbryan]

Hi guys. Can anyone confirm that the version of Activesync in this ROM Kitchen has changed?

I believe I found another problem. The old trusty Acticesync hack is not possible anymore. The option to make a server manual in settings is greyed out - it only allows automatic. The button for settings is still there but its greyed out completely. The hack Im referring to below:

Create fake server under AS (1.1.1.1) set pw, set user name. These can be random.

After it's done, set the schedule to manual.

Start your phone app, go to MENU>>SERVICES>>TIME SYNCRONIZATION

Click GET SETTINGS

UNCHECK Time syncronize with mobile network automatically

If the above is checked, AS will come on everytime the phone syncs with your providor..

Go back to AS setup, delete the exchange server you created

End task on AS

[JBabey]

Originally Posted by nickm

I am getting an error: gx.dll is a folder not a file. This happen about half way through the buildos.

What is this for? can I fix or simply remove the folder?

u may have a copy of the dll in the folder or the file AND the folder with the file name.

gx.dll is very common in game packages ive noticed, you only ever need ONE copy of it, regardless of size etc.... every game that uses it, i just grabbed the smallest gx.dll i could find, and deleted all the other copies so my builds would not error on that file any longer.

if you have the FOLDER, i would keep that, and remove all the actuall DLL files with that name (unless its IN the folder with the file name... thats normal).

gx.... graphics? dunno, but its used a lot....

EDIT: found it on microsoft technet

+++++++++++++++++++++++++++++++

gx.dll

Brief Description

GAPI is a Game API that is distributed in the Pocket PC SDK. GAPI 1.2 is a bugfix point release that should be used by everyone developing games for the Pocket PC.

[bigdoofus]

Originally Posted by luv2chill

@evans & bigdoofus - The HTC_SMS_Providers.dll file is in the stock Bell ROM, and not only that but more specifically it is in the CE ROM, not the extrom, meaning it is not meant to be carrier-specific.

Therefore if my provxml fix also fixes the problem I would be more inclined to use it, as it actually corrects an error between the kitchen ROM and the Bell ROM (Helmi inlcuded those entries as a test and even mentioned it to me to be aware of them but I forgot). Those entries from that provxml came from a cab in the Bell extrom so I suspect they relate to some peculiarity of how SMS is set up on the Canadian CDMA providers.

It's great that the SMS_Providers.dll file fixes the problem as well, but I don't think I will be making that change in the kitchen since it alters the ROM from stock and could have other consequences we are not aware of yet.

@Kyr (and whomever you quoted in your post) - Your problem is due to the very first thing I mentioned in the Notes section of my sticky post. When you got to the HTC64 Tool encode stage you selected a .prj file from the R4 kitchen (or some other kitchen) and therefore your new ROM file got made in that directory instead of in the new kitchen directory. I knew this would be a major problem for people and that's why I emphasized it in my post.

I spent a lot of time trying to figure out how to automatically clear that "memorized" path to help prevent this problem but never was able to do it. I found the reg entries where it seems the path is stored but deleting them from the registry didn't seem to affect the HTC64 Tool's ability to remember the last place it opened a prj file from.

If anyone can figure out an easy way to clear that memorized path it would make things easier for the noobs.

Understood. I will test provxml when I get the chance. Thanks for workiing on the Kitchen. Other than the SMS wierdness, its been the most stable ROM yet.

[toviaheli]

Sar,

I'm trying to track down which program or tweek is responsible. I suspect it is something I have installed, rather than your r7 ROM. I only have voice mail notifications after a hard reset and prior to my installing my own apps.

I am wondering if you or anyone else using your ROM has encountered this?

This is what I have installed:
Marsware Weatherpanel
IM Plus
Phone Alarm
SPB Moble Shell
Opera Beta
Resco Explorer
Wp-Pilot
IGuidance

-TOV

[nickm]

Thanks J, I found a copy of the gx.dll in the Bejeweled folder and deleted it. That solved that problem.

============================

Next error was; clg_in.gif already exist.

I found that the "New Colonel Dialer(Smartdial included)" gif was conflicting with the "Crossbow Dialer".

I decided to include the "HTC Smart Dial"; that solved that problem. Hope this helps someone.

How can I include colonels and crossbow?

[evans]

Originally Posted by luv2chill

@evans & bigdoofus - The HTC_SMS_Providers.dll file is in the stock Bell ROM, and not only that but more specifically it is in the CE ROM, not the extrom, meaning it is not meant to be carrier-specific.

Therefore if my provxml fix also fixes the problem I would be more inclined to use it, as it actually corrects an error between the kitchen ROM and the Bell ROM (Helmi inlcuded those entries as a test and even mentioned it to me to be aware of them but I forgot). Those entries from that provxml came from a cab in the Bell extrom so I suspect they relate to some peculiarity of how SMS is set up on the Canadian CDMA providers.

It's great that the SMS_Providers.dll file fixes the problem as well, but I don't think I will be making that change in the kitchen since it alters the ROM from stock and could have other consequences we are not aware of yet.

Understood - just wanted to understand the origins of both files. That said, I don't think that SMS_Providers.dll is actually used anyplace (I maye be wrong of course). Maybe some experiements could be done to determine this and then the "other" SMS provier could be listed as an alternate system configuration (or just removed entirely to save space).

...tom

[Ryan07]

I'm receiving an error with Image Converter.exe when trying to create my own boot screen.

Component 'comdlg32.ocx' or one of its dependancies not correctly registered: a file is missing or invalid

I'm also getting an error on boot from the copy of Slide2Unlock posted here. I tried it and tried making my own with the same results. On boot and when the screen goes blank, slide.exe can't be found. Installing the CAB corrects the issue.

Also I'm getting the white screen on my phone with JPLDialer_Vista_Black. The first ROM I built, I was getting white squares over the working JPL skin, but now it's just white. Loading the CAB also corrects the problem.

Thanks!

[Kyr]

Originally Posted by luv2chill

@Kyr (and whomever you quoted in your post) - Your problem is due to the very first thing I mentioned in the Notes section of my sticky post. When you got to the HTC64 Tool encode stage you selected a .prj file from the R4 kitchen (or some other kitchen) and therefore your new ROM file got made in that directory instead of in the new kitchen directory. I knew this would be a major problem for people and that's why I emphasized it in my post.

I spent a lot of time trying to figure out how to automatically clear that "memorized" path to help prevent this problem but never was able to do it. I found the reg entries where it seems the path is stored but deleting them from the registry didn't seem to affect the HTC64 Tool's ability to remember the last place it opened a prj file from.

If anyone can figure out an easy way to clear that memorized path it would make things easier for the noobs.

Sorry, luv2chill. I did read your very clear and concise directions and had no problems with my umpteen earlier flashes. Unfortunately, between dealing with a few recalcitrant non-kitchen OEMs, re-downloading the kitchen, and having surgery the day before, I genuinely thought I had already flashed from 1.0.2 and therefore thought I had the right path. So clearly the thing that went wonky between 1.0.0 and 1.0.2 was ME. Tho, I guess in this case it'd be more accurate to blame the percoset factor than the dreaded noob factor. However, this will definitely teach me not to flash under the influence again.

[rbinkley]

However, this will definitely teach me not to flash under the influence again. Wink

Maybe we should have this added to the tips and tricks sticky?

[Kyr]

Good God...must include posting under the influence as well. Ack.