Helmi Official AKU 3.5 Kitchen 1.0.3 Bugs / Patches

[jacksplat]

Originally Posted by mbial

Well PocketCM 0.6 just came out, so I added a new OEM to the ftp:


Best,
MJB

same thing...when I include this in the OEM folder, BuildOS errors and won't run. Take it out, everything is fine.. Any ideas?

[Kolano]

Originally Posted by borntochill

In BuildOS, I unchecked the option to install Windows Media Player because I prefer the TCPMP player, which I checked. Then I discovered that when I went to the phone settings to change my ring tone, the only available ring tone was "Windows Default". All the other ring tones (including the other OEM ring tones) were simply unavailable. When I reran BuildOS and rechecked the Windows Media Player option, all was well again with all of the ring tones showing again in the phone settings. I reflashed multiple times and found this behavior was true regardless of whether I checked or unchecked the additional ring tones option.

I don't think this is a bug in the kitchen per se, but if others experience this problem it probably should be mentioned in the release notes. Maybe there is a workaround, but I haven't been able to find it scanning the forum.

Yes, that functionality requires a few of the DLLs that are included in the Windows Media Player OEMs. I believe even TCPMP requries these DLLs to play certain content. It would be nice if someone could seperate these into a seperate OEM, so we could maintain this functionality without bringing in the full WMP package.

[luv2chill]

@jacksplat - you need to be very specific about what the exact error message that comes up is. Type the exact wording of it.

As for the guy with the error building .hv message, that is fairly easy to narrow down. Go into the ktichen folder and look for the \temp folder. In there is a log file. Open it up in notepad and scroll all the way to the bottom, where buildos will tell you what UUID it didn't like and even what line (approximately depending on if you have word wrap on) it couldn't parse. If it says line 1 then most common causes are:

a. You did not encode the rgu file in unicode
b. You did not place the REGEDIT4 header on the first line of the rgu

If the error comes in a higher line number there is some syntax error on that line.

[mbial]

JackSplat -

I'm guessing the problem is one of two likely things:

1. One of your other OEMs uses the same UUID as this one.
2. One of your other OEMs has a file with the same name as that of a file in this OEM.

Builds perfectly for me.

Best of luck,
MJB

[nickm]

Originally Posted by luv2chill

@jacksplat - you need to be very specific about what the exact error message that comes up is. Type the exact wording of it.

As for the guy with the error building .hv message, that is fairly easy to narrow down. Go into the ktichen folder and look for the \temp folder. In there is a log file. Open it up in notepad and scroll all the way to the bottom, where buildos will tell you what UUID it didn't like and even what line (approximately depending on if you have word wrap on) it couldn't parse. If it says line 1 then most common causes are:

a. You did not encode the rgu file in unicode
b. You did not place the REGEDIT4 header on the first line of the rgu

If the error comes in a higher line number there is some syntax error on that line.

Thanks Boss,
Its the stowaway OEM from another member. He was working on making the key board side work. The stowaway OEM in the kitchen only allows the mouse to work. I am thinking Ill just use the cab.

Failed to parse HKEY_CLASSES_ROOT\stwymouse\DefaultIcon!!!
InitRegistry FAILED in file ".\Registry\273a1dff-3c50-11dc-8314-0800200c9a66.rgu" within a few lines of line 9.
ImportFromPackageListStrict: (RGUComp) !ERROR failed importing ".\Registry\273a1dff-3c50-11dc-8314-0800200c9a66.rgu"
wmain: (RGUComp) !ERROR failed building DEFAULT hives

[Pir8Man]

im running great on 1.0.3. using the nk.fat from 1.0.2.
very basic with the necesities for my work and some games.

here were my options:

Enterprise
Games
Windows Live Mobile
Net Compact Framework II SP2
Office Mobile
SqlCe Mobile
Windows Media
Firmware Update
Remote Desktop Mobile
HTC Camera
1Calc 3.0.0 Lite
Additional Themes
Adobe PDF Reader
Contacts Manager 1.6
HTC Streaming Media Player 2.10
HTC Voice Recorder 1.10
HTC X-Button 1.51 (Build 29977)
WIndows Live Search 2.0.2739.29907
Arcsoft MMS 3.0.6.24
Running Programs Link
WiFiFoFum
WM5torage v.1.7.5
PPC/XV7600 Hack
Net Comm Manager
AllMobileMines 4.0.0
Dopewars 1.0
Freecell 1.1
Microsoft Hearts 1.0
Kevtris
Microsoft Voice Command 1.6 US
Default Windows Blue Dialer
HTC Smart Dial
Esmertec Jeodek Java
Sprint ExtROM version 2.06.300
Adobe Flash Player 7
Wireless Modem (Wmodem)
eaByte Keyboard Skin
SPB Mobile Shell 1.5
ExtRom Unlock
VJCandela (Normal Install)

[CheezWiz]

After the help above and testing a new battery (reboot), my caller ID is working again...

Only issue I am still seeing is the non-responsive data icon in comm manager. So is this also a pebkac error? I am showing 8 buttons and all of them respond to a push by changing from color to grayscale with the small x indicating they are off. Data just stays grayscale but with no x.

I could have sworn that the original ROM would allow me to disable data so that if I hit PIE, it would not dial out to #777 or am I just remembering it all wrong? Currently the icon just shows if data is active or not and will allow the termination of a data connection. Is that the way it always was?

[luv2chill]

Yes CheezWiz that's the way CommManager works. All it does is let you disconnect the active data session if one is active.

There's a modaco app called NoData that should do what you're looking for though:

http://www.modaco.com/FREE-Utility-t246171.html

[luv2chill]

nickm

Ok I had a look at that rgu and saw the mistake (it's a very common one). In reg files, when specifying a path in the file system, you must use double backslashes--this stems from the fact that the backslash character does other things in reg files--so to tell it you REALLY mean a backslash you have to put two. I know it's somewhat non-intuitive. It's one of those things you have to just accept and do it the way they want to see it.

So here's what was in the file on line 8 and 9:

[HKEY_CLASSES_ROOT\stwymouse\DefaultIcon]
@="\Windows\Stowaway.exe,-2"

what it should look like is this:

[HKEY_CLASSES_ROOT\stwymouse\DefaultIcon]
@="\\Windows\\Stowaway.exe,-2"

There were several other lines in that rgu with the same problem. Also, whoever made it did not put a blank line in at the end. That's another one of those things you just have to remember to do.

Err I had attached a "fixed" rgu but tried to build with it and there were other problems. I'm just going to go ahead and remake the OEM from the cab file on the ftp ("Think Outside PPC5 En.rar.CAB", right?). It seems to have a complicated setup.dll so would be a pretty tricky one for a new user to do. I'll post it here shortly.

[luv2chill]

OK nickm, please test this ASAP.

And I'm disappointed to not have heard any more reports on the SPB apps. No one else has tested them? It's not that I don't trust the guy's work, but everyone has different combinations of OEMs that could cause different behaviors. Please consider testing those apps if you own them (since they won't work as trials).