New Kitchen (Helmi_APAC_WM3.5_NEW_Kitchen_R2) Bugs

[Kolano]

Here's a bug collection thread for the new kitchen R2. I'm going to try to gather all posted bugs into this first message, so folks don't need to poke all over to find them.

Got a bug, let us know. Please be specific, and please provide steps to reproduce.

Remaining issues...

=#1=== HTC64 Extended ROM Tool/CreateROM.bat

The paths in HTC64 Extended ROM Tool are still off. The paths are set as...
\Upgrade\nk.nbf
\temp\nk.nba

But that would be for a directory structure like...
\temp\Upgrade
\temp\temp

They should be...
..\Upgrade\nk.nbf
nk.nba
...which should get things working with the current CreateROM.bat config.

------

NOTE: The HTC64 Extended ROM Tool remembers the last location it loaded .prj files from. If you have multiple copies of it on your machine be sure to check the directory you are selecting the .prj files from.

Once set things should work smoothly on the next run. But remember to watch out if you are using multiple kitchens.

------

I think "CreateROM.bat" is a bit too complex for it's own good. I don't understand why we are copying everything to the \temp directory on each go. Why not call it directly from \Tools, and set the paths to...
..\Upgrade\nk.nbf
..\temp\nk.nba

Doing so turns...

ECHO Next: Flash the rom...
ECHO Set the device to bootloader mode if necesarry...
ECHO --------------
ECHO !!!WARNING!!!!
ECHO --------------
pause
@ECHO OFF
CD ..\Tools\
COPY Telecom_New_Zealand.prj ..\temp\Telecom_New_Zealand.prj /y
COPY Verizon.prj ..\temp\Verizon.prj /y
COPY Alltel.prj ..\temp\Alltel.prj /y
COPY Bell_Mobility.prj ..\temp\Bell_Mobility.prj /y
COPY Qwest.prj ..\temp\Qwest.prj /y
COPY Sprint.prj ..\temp\Sprint.prj /y
COPY Telus.prj ..\temp\Telus.prj /y
COPY HTC64_Extended_ROM_Tool.exe ..\temp\HTC64_Extended_ROM_Tool.exe /y
ECHO 
ECHO Select encode and select your operator name on the next dialog to avoid country error...
ECHO --------------
ECHO !!!WARNING!!!!
ECHO --------------
pause
REM CALL ..\temp\HTC64_Extended_ROM_Tool.exe 
CD ..\Temp 
CALL HTC64_Extended_ROM_Tool.exe
COPY ..\temp\nk.nbf ..\Upgrade\nk.nbf /y
CD ..\Upgrade\
CALL ROMUpgradeUt.exe

...into...

ECHO
ECHO Next: Encode the ROM...
ECHO --------------
ECHO !!!WARNING!!!!
ECHO --------------
ECHO Select encode and select your operator name on the next dialog to avoid country error...
ECHO
@ECHO OFF
pause
CD ..\Tools\
CALL HTC64_Extended_ROM_Tool.exe
ECHO
ECHO Next: Flash the ROM...
ECHO --------------
ECHO !!!WARNING!!!!
ECHO --------------
ECHO Set the device to bootloader mode if necessary...
ECHO
pause
CD ..\Upgrade\
CALL ROMUpgradeUt.exe

This gives warnings at more appropriate junctures, has fewer steps, and doesn't cause odd things to happen like edits made to the .prj files being forgotten. See the bottom of this post for a patch implementing the changes above.

=#2=== OEM\Optional_TrayLaunch:

Blank icons appear if any of the following OEM packages are not installed...
-Optional_TaskMgr&RegEditor
-Optional_Total Commander
-Optional_acbToggleBT
-Optional_psShutXP

=#3=== OEM\Optional_OneNoteMobile=12.0.4518.1010:

Installing this results in an extra set of Office icons, one in "Program Files" and one in "Program Files\One Note". The icons have different images, but I think thats due to the OneNote ones actually pointing to little "27k" stub executable that calls the regular office exe's.

------

I didn't include the Office that was in the system but included only the OneNote OEM. When I tried to open word/excel/power point, it just throws an error

Win32Eception at System.Diagnostics.Process.StartWithShellExecuteEx ()...

But the One Note doesn't have any problems. Only the other three apps. I guess they are dependent on the Office app.

---

Originally Posted by colonel

Kolano, the OneNote issue is just the way it is. The OneNote thing creates shells for the existing Office apps. The only stand-alone app is the actual OneNote app. Now, people could remove the shortcuts for the standard Office apps and replace them with the OneNote shortcuts, but that is about it.

Couldn't we create an OEM that didn't include the stub exe's or "OneNote Mobile" folder in Programs, but instead just created a "OneNote Mobile" icon in Programs. The only advantage to the stubs seems to be the revised icons, but they aren't even that nice, as they lack transparent backgrounds.

That would cleanly resolve both the multiple icons, and the breakage if other office components weren't installed.

------

See patch below.

=#4=== OEM\Optional_Camera

Originally Posted by johnny2678

The initflashfiles.txt in the optional_Camera OEM is looking to move a HTC_Camera.lnk shortcut file into Start Menu->Programs. HTC_Camera.lnk doesn't exist, but OEMCamera.lnk does. I just copied OEMCamera.lnk to HTC_Camera.lnk to get the camera link in the Start Menu

------

See patch below.

=#5=== OEM\Optional_Flashlight

This install seems to not provide a mechanism to activate the installed program outside of running the executable directly out of \Windows. This is due to an excess commented line in it's RGU...

;[HKEY_CURRENT_USER\SOFTWARE\MICROSOFT\TODAY\KEYS\112]
  @="Flashlight"
  "Open"="VJCandelaLite.exe"

...the first line should not include the ";" prefix.

------

Originally Posted by colonel

It was taken out because I inteneded to relocate the Flashlight. Among other reasons, I hated when I wanted to use the flashlight, but there was a voicemail notification that I could not dismiss.

Originally Posted by colonel

I might stick it on one of the buttons on the left side if anyone has a preference.

Originally Posted by scottishwarrior

What I did was add it in th WM5 New Menu. If you go to settings and open new menu, you can add it to the list because it is an executable. The exe file is in the windows folder, just have to scroll down to it.
Now I can still use it and it doesn't interfere with notifications.

Originally Posted by colonel

Yes, adding it to WM5 New Menu works, but you still have the Notifications issue. Granted it is not that important, but I thought a hardware button assignment would be more useful. I can create different OEMS for different options if necessary.

=#6=== OEM\Optional_InternetSharing:

Originally Posted by gguruusa

I can confirm these Internet Connection Sharing issues:

If USB mode is used and Bluetooth is on, PC will not acquire IP address
If Bluetooth mode is used, PAN can not be established

=#7=== OEM\Optional_O2_Running_Programs

Originally Posted by gguruusa

Additionally, closing the application using O2Plus results in not being able to start it again without a reboot first - this is not the case if you close it with the Memory applet.

=#7=== BT PAN:

Originally Posted by johnny2678

which OEM is the BT PAN RGU entries contained in? Did this OEM change from R0 to R2? If not, then flashing the BTA2DP, BTFTP, and CambridgeBTProfiles did not get BT PAN working on my unit. However, when I installed the above cab, all is fine.

Originally Posted by colonel

In the OEM folder is OEM_BT_PAN. This does not show up on the BuildOS list, but it is installed. However, this OEM does not have the btd.dll in it. The btd.dll can be found in module form in Apache drivers in the OEM folder. I have replaced this for R3.

Originally Posted by colonel

Ok, here is what you need to try. Copy the btd.dll module (folder) out of the Apache Drivers OEM and replace it with the btd.dll file from the patch you posted. That should fix it. Let me know.

=#?===================

If anyone can confirm the resolution / lack thereof of any of the following issues from r1 please post.

MMS: ## codes don't work for non-Verizon phones.
Tweaker: Produces error on Save.
Can't install .cab files

[colonel]

lol, dont list bugs before the upload is complete

[Kolano]

Originally Posted by colonel

lol, dont list bugs before the upload is complete

Didn't realize it wasn't yet. When you had said to try the next release in one of the other threads I figured it was ready to go.

Awaiting upload completion.

[boe]

Walkthrough doc password protected.

[schettj]

note the torrent still has R1... I won't be able to update the torrent until this evening, in the meantime you'll need to stick with FTP

[colonel]

J Babey did that. You can still read it. Just not edit it I guess

I will probably get it up on the wiki at some point so people can add and edit it as need be

[Kolano]

Still minor problems with the Extended ROM Tool paths, details in first post shortly.

[colonel]

did you like the new error messages?

[boe]

Actually the new error message made me wonder if I had a virus!

The path seem to be off - if you don't correct them, you'll get the standard image - no menu changes you have made will effect anything.

[Kolano]

Originally Posted by colonel

did you like the new error messages?

I like that they actually refer to the problematic files now. It's too bad the field names, and file selection dialog still specify .fat files.

Can we alter "HTC64_Extended_ROM_Tool.exe" to address that?

Alternately, could we add something to the CreateROM.bat file to rename the files for each tool appropriately, so the file dialogs would work better?