Helmi Official AKU 3.5 Kitchen 1.0.2 Bugs / Patches

[Kolano]

Here's a bug collection thread for Helmi Official AKU 3.5 Kitchen, Release 1.0.2. I'm going to try to gather bugs into this first message, so folks don't need to poke all over to find them.

If you need help with something, or want to offer thanks see the sticky thread.

If you have bug please let us know...
Please be specific.
Please provide steps to reproduce.

======================
=== Updates from 1.0.1 ===
======================

1.0.2 - 7/16/2007
1. Added reg to OEM_WLanMgr to enable tapping on tray comm manager icon
2. Fixed ringtone files and rgu in OEM_Additional_Ringtones to reflect needed space between file name and file extension.
3. Removed InClose OEM. It is a fantastic app, but doesn't work well from \Windows. Install the cab instead.
4. Added back in acbpower OEM (inadvertantly left out)
5. Verizon extrom OEM to version 1.0.1 to add in verizon provisioning application
6. Added HTC_default and Grass_b2 tsks into Optional_Additional_themes OEM, Set HTC_default as default
7. Added msvcr71.dll to \tools folder for Vista compatibility
8. Removed rgus from all keyboard skin OEMs. This was causing issues with dialers, arrows, and ## codes.
9. Updated ClearTemp+Quickclear OEM to latest version per request.
10. Updated dicteditor OEM to latest version per request.
11. Made crossbow dialer selected by default so users realize they need to have one selected.
12. Added Phone Codes OEM to give an alternative way to perform ## codes.
13. Added updated HTC X-button OEM from Colonel.
14. Added Adobe Reader OEM from col containing a small file name change to avoid dupe file conflict with another OEM.
15. Added File Dialog Changer 1.66 OEM from schettj.

============
=== Bugs ===
============

Optional_SPB Pocket Plus 3.2.0 QVGA Extended Themes Broken

Originally Posted by Wisdom3G

With the new rom or any rom for that matter, with sbp pocket plus installed, it seems as though Theme files with EXT in the name have no affect when selected on my ppc.

=====================
=== Bugs /w Corrections===
=====================

SpbServices.exe conflict

Originally Posted by gguruusa

SPB Weather shares a common file with SPB Diary (SpbServices.exe), so here are modified OEMs and a new OEM with just spbServices.exe in it (include it in your ROM if you include either Weather or Diary). Weather was modified from JBabey's OEM, Diary is modified from 1.00 of this kitchen.

In order to keep the OEMs as close to the originals as possible, I haven't modified options.xml or the oem names. For clarity, I suggest changing the OEM name of spbweather to match the other spb oems, and putting weather and diary in their own group (in BuildOS) so it's clear you have to select spbcore too.

See gguruusa's post for the related OEMs.

SPB Weather freezes when clicked on using Pocket Plus tab

Originally Posted by xv6700ft

Also, I found a fix to SPB Weather. If anyone is having the issue I described above of Weather freezing when you click on the Pocket Plus tab, you need to find SpbWeather.PopupIcons.zip in \Windows. Then you need to copy it to the \Windows\default folder and rename it to PopupIcons.zip. Reboot, and Spb Weather works. This is assuming you have the same OEM I have running.

OEM_PhoneExt_Service.dll Creates Needless, Eventually Large Logs

Originally Posted by theedon

Does anyone know how to permanently delete this log file.

\PhoneExt_Service.log

I have deleted it but it comes right back and it seems to grow quite rapidly.

Originally Posted by schettj

It is that dll for sure, and that dll is in the OEM_PhoneEx_Service.dll folder

Interestingly, that dll (and OEM, and service) is NOT in the previous Helmi kitchen.

Sooooo.... guess we don't need it? It sure doesn't like to play with my phone.

Edit: Seems to have something to do with BT DUN tethering/data service?

Originally Posted by Jeff Kirvin

Of note, disabling the PhoneExt service with SKTools also prevents the Apache from updating time automatically from the carrier. So either trust your internal clock, or delete the .log file regularly. Pick one.

Originally Posted by luv2chill

This is a weird one. Indeed it doesn't seem to create that log file on the the stock Bell ROM. Furthermore, in the latest Verizon extrom (from their April AKU 2.2 maintenance release), there is a cab file-- "ITS_560_TimeZone.CAB" which contains this exact same version (same file size and MD5 hash) of Phoneext_service.dll. Incidentally there are no reg entries or anything that appears to directly relate to time zones.

OK now, going back to the "Unified ROM" a few months ago I had a look for that file and found it (same UUID and RGU information). And it's got the same version info (1.25.0.0) but it's a lot smaller--62,328 bytes. Not sure what to make of this but I copied that file over to \Windows (replacing the problematic version in ROM) and so far so good. The log file has not come back, and time sync works (Sprint with 1.41 radio and extrom OEM built in). Not sure what else to test but I'll run with this for a while, and will upload the file for anyone else who wants to test it.

Another possible "solution" to this (credit to kdoweb) is to write-protect the log file (you can use total commander to do it). He did that and noticed the log file size stayed the same and no new file was created. I do not know of any other consequences to this, but it's something else for people to try.

See luv2chill's post for an alternate dll.

Initial Timezone may not fully apply on Verizon
The timezone you select during initial boot may not set all the needed registry keys to enable all timezone functionality. Selecting an other timezone and then reselecting your timezone via the Clocks & Alarms settings panel seems to correct this.

Originally Posted by luv2chill

I believe this is due to entries in the Verizon provxml that "pre-set" the time to Eastern. It is possible that it is not properly setting the eastern time zone in BOTH registry keys. Those people who select a time zone other than eastern at the Welcome wizard shouldn't have this issue--only those who accept the default choice of Eastern time. There are two other carrier extroms with identical entries (Midwest Wireless and Telus) but there have got to be very few (if any) MW Apaches out there currently and Telus is in Canada which isn't subject to new DST rules so may not experience the problem at all.

The solution may just be as simple as removing these "preset" TZ entries from the provxml altogether. By default the kitchen (like a normal stock rom) goes to Pacific time and has entries set properly by default to make that TZ work if it is not changed in the welcome wizard. So if I remove the custom entries from the provxml everything should be great. Verizon users interested in testing can try substituting the provxml I have attached (just replace the existing one inside the Optional_Extrom_verizon folder in \OEM before building.

See luv2chill's post for a patch to remove the Verizon tz customization.

Optional_FileDialogChanger 1.66 Can Break Apps

This OEM will break certain apps, including:
-PHM Regedit (Can't export registry)
-?

OEM patch available below. If you know of others effected applications let us know.

Optional_KB_Skin_eaByte_OEM1_0_0 Mislabeled Keys

Originally Posted by Matrix

eaByte keyboard skin, go to options, set it to "Large keys" and check "Use gestures for the following keys" press OK, and you'll see an error in the qwerty labeling. Instead of "asdf" it says "atsf". Pressing the erroneous "t" results in "s" and pressing "s" results in "d".

Originally Posted by Matrix

For those interested, I got the eaByte skin to work by coping the files from "Optional_eaByte_KB_Skin_OEM1_0_0" in the RC4 kitchen, then reflashing.

See below for the alternate OEM.

Bluetooth Dial Up Networking

Originally Posted by bzo

Please add Bluetooth DUN via Wmodem to the issues. I've reported in another thread that this does not work with the Nokia 770 and mikee4fun reported that it wasn't working with his tom tom 910. When I pair the phone to the Nokia, the only available profiles is OPP.

I flashed to the official 3.3 rom, and Bluetooth DUN works perfectly right away. DUN and OPP are listed as available in the profiles.

I just built another ROM from the kitchen and selected internet sharing, wmodem and modem link application. Interesting, this fixes the problem with wmodem. Perhaps there are some missing pieces from the old modem link oem that wmodem needs?

Originally Posted by bzo

ok, did some more tests. Like I said, if you build both the Modem Link and Wmodem OEMs into the ROM, Bluetooth DUN seems to work. I tried copying the dll directories from the modem link oem to the wmodem oem and rebuilding the DSM. When I build a ROM like this, the bluetooth DUN profile shows available, but gives you an error when you actually try to connect. I don't know this is a oem package building error on my part or whether all the files from the modem link OEM are necessary.

So, I guess bottom line is, currently both the Modem Link OEM and the WModem OEM need to be included in the ROM for bluetooth DUN to work.

Regarding the combined OEM file...

Originally Posted by luv2chill

The problem is that you didn't include the registry entries from the Modem_Link rgu. You may not need them all but at a minimum you probably need the BTHATCI.dll port entry.

Correction expected in a future release. For now, always select all three Tethering options to ensure functionality.

OEM/Optional_WeatherPanel

Originally Posted by gguruusa

One of the buttons doesn't call the right panel in this file (always bugged me, finally fixed it). Replace the same named file in OEM/Optional_WeatherPanel.

See gguruusa's post for details

Spb Backup v1.6.1 doesn't integrate into today plugins correctly

Originally Posted by DopeWeasel

I downloaded your RGU file. Looks like there may be some issues with it. You have some extra slashes in the HKEY lines I.E. :

[HKEY_LOCAL_MACHINE\\Software\Spb Software House\Spb Backup]
should be
[HKEY_LOCAL_MACHINE\Software\Spb Software House\Spb Backup]

While you use \\ in the String values... it is not necessary in the HKEY location.

I corrected those inconsistencies in my OEM here as well as adding all missing reg keys. This OEM should be fully functional and latest version as of now

See DopeWeasel's New Core OEMs for the new OEM.

Can't send SMS between carriers / From and SMS Message Concatinated

Originally Posted by luv2chill

OK Verizon users affected by this SMS thing, can you please replace this file in the OEM_Helmi_Addition folder in \OEM and build a ROM to test to see if the problem is resolved?

Are users on any other carrier experiencing this same issue? I encourage everyone (who has a text messaging plan, anyway) to test the ability to send and receive SMS to and from your own carrier and other carriers. If you are having the same issue the verizon users are experiencing you can try this file as well, but please report in here so I can know which carriers are affected.

See luv2chills post for patch.

==================
=== Enhancements ===
==================

Optional_Slide2Unlock.1.7

Originally Posted by gguruusa

Here's Optional_Slide2Unlock.1.7. Let me know if you have any errors on startup (iLock not starting before slide.exe). I upped the GUID so no conflict in BuildOS between 1.6 and 1.7.

Originally Posted by Ryan07

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.

Originally Posted by gguruusa

Could be because the .rgu GUID is wrong (doesn't match the .dsm or options.xml GUID) Razz

Atttached is 1.18 (totally untested, use at your own risk). According to A_C, it has some fixed memory leaks and CallerID support. check the readme for more details and info on CallerID support - it's has it's drawbacks.

See gguruusa's post for updated OEM.


Optional_HTC_Audio_Manager Size Reduction
The images in the "Optional_HTC_Audio_Manager" OEM are encoded as 32bit PNGs, but can be losslessly encoded as 24/8bit PNGs. The patch below provides updated files that save 401k.

OEM_Comm_Manager_New Size Reduction
A second PNG reduction patch for OEM_Comm_Manager_New saving another 287,170 bytes.

Carrier Customizations /w Cellular Data Disabled
The Carrier customization OEMs have entries similar to the following in the mxip_ExtROMVerizon_100.provxml file that enable the cellular data network...

<characteristic type="Data Network Connect">
	...
	<parm name="Enabled" value="1" />

This may be undesirable if one does not have a data service plan. The patch below provides additional carrier OEMs that disable the cellular data network via the option shown above.

Note: These still need the other carrier OEM fixes listed here applied.

===================
=== Old Bug Threads ===
===================
1.0.1 Bugs

=============
=== Patches ===
=============

[Kolano]

=================
=== More Patches ===
=================

[schettj]

I'll get to reflashing this one in a day or so... will see if that pesky phoneex service/logging thingie is still there, unless someone beats me to it.

Nice work as always - this is going to be the perfect 3.5 rom

[jnjn]

X-button is no where to be found after flashing to 1.0.2

[luv2chill]

Originally Posted by jnjn

X-button is no where to be found after flashing to 1.0.2

Yeah the control panl is called "Task Manager" now--in Settings->System.

It confused me too.

[roro]

will verizon MMS still work with the No Data patch?

[Kolano]

Originally Posted by roro

will verizon MMS still work with the No Data patch?

Yes, SMS should continue to work just the same as without the No Data patch. The only noticeable difference should be that applications will not be able to make Internet requests over the Cellular Data Network.

This is specifically useful when...
-You do not pay for Verizon's data plan, and may be charged exorbitant rates for even small amounts of cellular data network usage.
-You load apps in your ROM, such as WeatherPanel, that attempt to establish a data connection at first boot prior to one being able to disable the cellular data network.

I want to provide similar updates for other carriers if needed, but still need to investigate how to do so in each carrier OEM package.

[blazingwolf]

Umm, the question was about MMS and not SMS. MMS will not work with out the data side working (unless someone else knows better). So no, MMS would not work until you go in and set up the data side.

That would not be an enhancement for me.

[Kolano]

Originally Posted by blazingwolf

Umm, the question was about MMS and not SMS. MMS will not work with out the data side working (unless someone else knows better). So no, MMS would not work until you go in and set up the data side.

That would not be an enhancement for me.

Sorry, missed the distinction at first. I haven't explicitly tested MMS, I'm guessing it won't work unless you are on a Wifi network, but I'll try it out later. If you don't pay for a data plan, it not working via cellular may be a good thing.

[blazingwolf]

I think the best way to handle this would be to include both options in the kitchen. Otherwise, someone is going to have some sort of changes to be made.