Helmi Official AKU 3.5 Kitchen 1.0.2 Bugs / Patches - Page 5

**luv2chill** · #41 (**permalink**) 07-18-2007, 01:18 PM

Apologies to the Canucks on the TZ thing--was thinking of Mexico I guess. Well any Telus users who are on eastern time and did not make any time zone changes should see the same issue.

In fact I'm so sure this is the problem I'm just going to go ahead and remove all time zone settings from all of the carrier provxml files.

If you want to preset your time zone in the kitchen the best bet is to get your device set up to the correct one, export your HKLM\Time and HKLM\Software\Microsoft\Clock keys and put them in an rgu in your own custom OEM. I've been doing it that way for the last few months with no problems (even since the time change).

To the guy worried about DST fixes, yes they are all there. Don't worry

.

@peacock - I'm glad you gave specific info because the problem is that you did not include the Sprint extrom OEM in your ROM. Please read the first post of the sticky thread, as I specifically addressed that the carrier extrom OEMs contain the MMS server configuration information.

**luv2chill** · #42 (**permalink**) 07-18-2007, 01:33 PM

Quote:

Originally Posted by bzo

Quote:

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.

Oh did you state that somewhere? Sorry if I missed it.

Quote:

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.

Nope that was all OK to do. 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.

Quote:

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.

Hmm, well I swear bluetooth DUN worked just fine on my XP SP2 laptop without the Modem Link OEM, so maybe the files from that are only needed to make BT DUN work in certain instances.

Anyway I will figure something out. Thank you for confirming.

bzo · #43 (**permalink**) 07-18-2007, 02:07 PM

Quote:

Originally Posted by luv2chill

Nope that was all OK to do. 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.

Aha! That must be what's going on. I didn't see an rgu file with this OEM, but since you mentioned it, I figured out that windows was hiding the rgu file until I unchecked "hide operating system files", go figure.

I forgot to mention, that it it looks like both dll files are required. When I built with only bthatci.dll added to wmodem, the DUN profile didn't show up.

Quote:

Originally Posted by luv2chill

Hmm, well I swear bluetooth DUN worked just fine on my XP SP2 laptop without the Modem Link OEM, so maybe the files from that are only needed to make BT DUN work in certain instances.

I wouldn't be surprised. From what I remember, setting up Bluetooth DUN from XP is a bit of a manual process, where as with my Nokia internet tablet and the other guy's GPS are more of embedded systems with automatic and less flexible setup of the connection.

Thanks for looking into it!

peacock93 · #44 (**permalink**) 07-18-2007, 02:18 PM

luv2chill,

i'm cooking a new rom now with the Sprint extrom added. i guess i got confused when i read that sticky post. i thought you meant that we didn't need any of the cabs from them anymore.

EDIT: So what this means for you is that you should NOT allow the cabs from your extrom to install on first boot (just soft reset when you see the "customizing your device in 3 seconds" prompt). Better yet, unhide and unlock your extrom (there is a cab for that), or flash the blank extrom file so those cabs are gone forever. You no longer need them!

ok, mark me for being stupid!! i get it now. i thought that your oem was installing the original Sprint extrom without all of the junk cabs in it. dang i was slow to figure that one out.

do i still need the arcsoft mms with the Sprint oem?

phoenx06 · #45 (**permalink**) 07-18-2007, 02:21 PM

When cooking the rom, select the sprint extrom oem, and finish cooking the rom. After flashing, when it tries to do the carrier customization (3 seconds thing), just soft reset. You dont need the stuff from the extrom anymore if you choose the correct carrier oem while cooking

**luv2chill** · #46 (**permalink**) 07-18-2007, 02:23 PM

Quote:

Originally Posted by peacock93

luv2chill,

i'm cooking a new rom now with the Sprint extrom added. i guess i got confused when i read that sticky post. i thought you meant that we didn't need any of the cabs from them anymore.

EDIT: So what this means for you is that you should NOT allow the cabs from your extrom to install on first boot (just soft reset when you see the "customizing your device in 3 seconds" prompt). Better yet, unhide and unlock your extrom (there is a cab for that), or flash the blank extrom file so those cabs are gone forever. You no longer need them!

What I was referring to was your statement " I did not run the Sprint ext rom in the kitchen." I took that to mean you did not check the box for the Sprint ExtROM in the BuildOS app. By checking that box, it "pre-installs" only the desirable parts of those cab files (which is why I advise not to install the cabs and to just get rid of them).

So when you build your next rom you need to check the box for Sprint as well as MMS in order for MMS to work properly. I did it this way so avoid having to clutter the kitchen with multiple MMS folders. The version of MMS in the kitchen doesn't have any carrier-specific information in it--that now gets added by selecting your carrier on the buildos screen.

Hope that helps to clarify.

brightedge · #47 (**permalink**) 07-18-2007, 02:29 PM

Had my first SD related unresponsive episode just now. Screen off, pressed pwr button, no response. Pressed a few more times, no response. Popped the SD out, and viola, the screen turned on.

I do not have any apps running from SD, nor do I have any today screen programs like cLaunch that pull info from the SD.

Just thought you'd like to know

xv6700ft · #48 (**permalink**) 07-18-2007, 02:47 PM

I've customized a few roms in the past (Unified Rom, Helmi R4) and the 1.0.2 version is consistently giving me this message. I even get this message when it's scaled down without any of my custom OEM's, meaning I just used the OEM's in the package and even minimal at that. No matter what, I get this message. Does anyone know why this is occurring, or does anyone know of a workaround?

xv6700ft · #49 (**permalink**) 07-18-2007, 02:48 PM

In case you can't see the error message in the subject line, the error is "error building default.hv and user.hv"

**luv2chill** · #50 (**permalink**) 07-18-2007, 02:54 PM

xv6700ft

That's not a bug, it's due to an invalid configuration in your mix of OEMs. Go into the \temp folder inside the kitchen after you get that error and look at the bottom of the log file. It will tell you the UUID of the package it barfed on and the approximate line to look at for the error.