Helmi Official AKU 3.5 Kitchen 1.0.2 Bugs / Patches

[luv2chill]

OK geeks

BTW These threads are awesome. I'm going to add a big bold link at the top of the sticky asking people to post their bugs here--I'll keep the link up to date as other newer kitchens are released.

1. The Verizon time sync offset issue

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.

2. Phoneext_service.dll debug

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.

3. SPB Pocket Plus issues

I plan to make a new OEM for this app eventually. I've been hoping SPB would update it (seems overdue compared to their other apps) but I know the existing OEM has some problems. I didn't make that OEM (not sure who did) but I will give it a shot and see if that fixes the problems.

4. Eabyte Skin Problem

I vaguely remember someone fixing this skin, but wasn't aware that it had made its way into the R4 kitchen (was probably discussed but I missed it). Will be taken care of for the next release. In the meantime, I have attached the skin taken from R4. You should be able to replace it on your device by copying it with total commander. Otherwise, the best way is to replace it in the Optional_KB_Skin_Eabyte... OEM folder before running buildos.

[swimmrguy]

Originally Posted by luv2chill

Telus is in Canada which isn't subject to new DST rules so may not experience the problem at all.

I am not sure I understand what you mean here. Parts of Canada (ie. Ontario, where I live) changed their DST times to correspond with the US. Is this what you are referring to?

I was assuming that the DST update was built into the kitchen, so I just want to be sure I don't need to worry about the time change in the fall.

[peacock93]

Sorry, I posted this in the 1.0.2 thread instead of here because I missed this thread. Here's my problem

On both 1.0.1 and now 1.0.2 MMS will not send picture mail. I get an instant notification message telling me that the message could not be sent and asking if I want to retry now or later. I am with Sprint and running a blank colonel ext rom with spb software installed to it. I did not run the Sprint ext rom in the kitchen. Below are the oems I have installed;

acbPower, acbToggle, Adobe Reader, BLK Keyboard Skin, HTC Camera, ContactsManager, DictEditor, FileAsFirstLast, Flash 7, VJCandela, Internet Sharing, Esmertec Java, Kevtris, MarkAllAsRead, MobiReader, MsPacMan, O2, O2 Meters, O2 Running Programs, OEM_MMS_3.0.6.24, PIEPlus2.2, PIM Backup, PocketRAR, Resco Explorer2007, Resco Picture View 6.31, Croosbow Dial Skin, HTC Smart Dialer, SmartKey, SoftKeyApplet, SPB Pocket+, SPB Shell, TaskMgr&RegEditor, TCPMP_81, Voice Command US, Windows Live Search, WM5NewMenu, Yuma6700Hacks, X-Scalar.

[phoenx06]

Originally Posted by luv2chill

2. Phoneext_service.dll debug

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.

If you repace file while phone is in operation, replace .dll in windows, delete the phoneext_service.txt file, and soft reset. This should keep it from coming back. If you just replace and not reset, it will keep coming back (I guess the service still runs after you replace the file until restarted)

[kevdawg]

Has anyone noticed that Windows Media Player does NOT freeze your device when you turn it off and back on again when the music is stored on the SD card. It's more than that even. It doesnt drop the connection with the SD card anymore. I can turn it off and on again w/o any problems!!! Just like i could with my Axim X5. Is this a bug? haha.

Anyways it makes me very happy as my phone is my "4GB iPod" as well. I love this new rom.

[schettj]

Nice job on the phoneext thing chill... I just dropped the dll above into my running system, undid my reg hack that disabled it, soft reset...

* no log file
* time sync works

- will keep an eye on battery consumption today.

[TheRocoLoco]

Originally Posted by luv2chill

Telus is in Canada which isn't subject to new DST rules so may not experience the problem at all

Canada changed their time, Mexico didn't =).

[schettj]

Originally Posted by schettj

Nice job on the phoneext thing chill... I just dropped the dll above into my running system, undid my reg hack that disabled it, soft reset...

* no log file
* time sync works

- will keep an eye on battery consumption today.

3 hours in... no change in battery - no sign of a log file... looking good for that fix.

[Matrix]

The updated Verizon extrom provxml fixed the strange offset issues for me.

[bzo]

Originally Posted by luv2chill

bzo-- Try building in the Modem Link OEM as well as wmodem. Modem Link had some additional dlls with it and maybe one of those is needed.

I can't think of anything else at the moment.

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.