Quote:
A new kitchen has been released.
Please check if issues with this kitchen continue on the revised 20071217 version, and post to the new bugs thread if they do. Bugs not expressly indicated as being fixed are likely to carry over, but we will need to confirm that.
|
This is the bug collection thread for the
Apache WM6 Kitchen CE OS 5.2.1908 (Build 18508.0.7.0) 071117_1. I'll gather bugs into this first message, so folks don't need to poke all over to find them. Please note that this thread is for bugs occurring in the ROMs produced via the kitchen, the file contents of it's OEM packages, or problems with their configuration or interaction. Bugs related to BuildOS,the tool used to compile/flash the ROM images, should be posted to
it's bug thread.
Quote:
|
Originally Posted by gguruusa
BuildOS problems are generally these: Kitchen Installation fails, kitchen shortcuts don't work, application fails to start, Application exits with error msg XXX, unexplainable errors during build or startup, added OEMs don't show in BuildOS, visual display problems in BuildOS, Boot issues (white screen on PPC), and corrupt boot splash.
|
=== Bugs ===
If you have a bug let us know. Please...
Be specific.
Provide steps to reproduce, including details of any customizations you have made.
Post your "Apache_Helmi_WM6 Selections.txt" file, so relevant BuildOS selections can be replicated.
Uncomfirmed Bugs- "server cert is wrong"?
Quote:
Originally Posted by obsidian440
I'm having trouble getting my direct push to work again with my exchange server. We are using 2007 with a self-signed ssl cert. On wm5 I was able to use the registry changes along with importing the cert manually to make it work. With my new upgrade I am now getting the message "server cert is wrong". I was unable to find any real answer searching google and these forums. I have tried to manually import the cert and doing the registry change but I'm still running into the same problem.
To be more specific, without the registry change, I get a message stating the server is the wrong name, with the registry it just tells me the certificate is wrong. I have checked all date/time settings on both my server and my phone, both match exactly. I have full access to the exchange server and phone.
|
Confirmed Bugs- Vogue Dialer OEM Causes Dialer to Popup on Application Close
Quote:
|
I have the HTC Vogue dialer and a fairly basic ROM installed from the kitchen. As I was setting up everything it seems the screen kept returning to the dialer view (sometimes the keypad and other times the in call screen).
|
- Simple PIN Locks Up Phone?
Quote:
Originally Posted by Lazybones
Soft reset your device while it is enabled.. then let the password screen fully load. I tested it by just setting the password. It happens nearly every time after a soft reset, and randomly when the device is put to sleep.
Edit:
More detailed Steps to reproduce:
1. Go to settings and lock
2. Select Simple PIN as your password type and set a password of at least 5 digits
3. Soft reset your phone
4. Wait for the device to fully load (IE the tool bar theme has loaded and the phone has found a signal)
5. Now try to unlock the phone with your pin.
|
Quote:
Originally Posted by luv2chill
...yes I was able to confirm your report by doing a soft reset with password enabled (had similar lockup problems whether it was simple pin or regular password). I could never reproduce that behavior just with a simple inactivity timeout, but I know you said that was random. But it definitely occurred after every soft reset.
I flashed back to every iteration of helmi's wm6 ROM I had and they all suffered that issue. Seems to be some sort of timeout issue... like the device is waiting for "something" once you click unlock, and when it doesn't happen in x amount of time the device gives up and proceeds anyway. That's what it "seems" like anyway--I could be way off base.
I had helmi confirm that it does not occur on the Universal (which is the closest device hardware-wise to the Apache). So it's either a driver issue or something in the registry that's causing it. Hopeully we'll get to the bottom of it soon.
|
Quote:
Originally Posted by luv2chill
Hmm I saw the same hang whether I did Simple PIN or Strong Alphanumeric. Have others been able to solve this by choosing Strong Alphanumeric?
|
- HTC Task Manager Interferes with Taskbar Battery Meter
Quote:
Originally Posted by spetrillo
I have just flashed my phone from the new kitchen and noticed that the battery meter in the upper right portion of the phone does not work. When I tap on top of it then it should take me to the battery meter but it does not. This used to work in the VZG kitchen.
|
Quote:
Originally Posted by luv2chill
It's due to HTC Task Manager (X-button) IIRC.
|
Known Resolutions- New bootscreen tools give boot image green tinge
Quote:
Originally Posted by Wizzard
The only problem I have now is with the "Boot Splash." It seems to have a greenish tinge to the picture, even though it is black and white! I used the converter to save it and it worked better than just a plain .jpg, which was all green.
|
Quote:
Originally Posted by gguruusa
Ok, turns out it was broken for both converters, and I had only fixed one before. New build has been posted.
For the curious, it's actually a bug based on the low order Red color bits. Windows manipulated the pixel value on my behalf in order to distribute accumulated error when moving from a low color depth to a higher color depth. My logic assumed the pixel value I put in would be the pixel value I got out (sounds reasonable, doesn't it?), so when it wasn't things went awry. You see the artifact as green because the low order red bits were writing on top of the high order green bits. By pure chance, green does not write on blue because of an election I took in the code. Blue doesn't have a color after it to overwrite. So, the only color getting messed up is green, which explains why all the artifacts were green.
|
Fix available in BuildOS thread.
- PocketCM Theme Issues
Quote:
Originally Posted by reeg420
PocketCM doesnt show the touch skin. It showed up by default in earlier oem rar file. I opened the files up and it shows both touch and theme as cmt files but doesnt show in themes setting in CM.
I ended up just using the oem files from the earlier one which had the skin since most of the newer oems in there I dont use anyway.
|
Quote:
Originally Posted by Kolano
Yes, it appears that the latest kitchen updated to PocketCM .16 (development). In my case only the "Black" and "White" skins seem to do anything, all other themes result in the "White" theme being used.
I'm not sure yet if the issues seen are due to a partially implemented OEM or the developmental status of .16 as of yet. Since we missed listing this in the changelog I'm guessing the former.
|
- HTC Home and HTC task manager conflicts
Quote:
Originally Posted by alpine
|