Apache WM6 Kitchen CE OS 5.2.1908 (Build 18508.0.7.0) Bugs/Patches - Page 16

cjbreisch · #**151** (**permalink**) 11-07-2007, 05:57 PM

I installed the acbToggleBT module, but there doesn't appear to be a shortcut for it in Programs.

**luv2chill** · #**152** (**permalink**) 11-07-2007, 06:07 PM

Quote:

Originally Posted by bobonit

I have a Sandisk 6gb microSDHC card. Using the SDHC.777.cab I installed on my phone running Helmi_C's rom everything was fine. Using the new kitchen to cook a rom with SD and SDHC Support, transfer speeds to and from the SDHC card are slow and playing music files from the card skips. If I cook a rom with only SD support, flash it to the phone, boot the phone, I can then install the SDHC.777.cab and I have no skipping of the audio files and the transfer is as it used to be on Helmi_C's ROM. I have verified this by flashing between the 2 several times.

I belive verizonguy may have fixed this bug previously. I hope he will share his fix so that we can get it integrated. I too have seen the skipping with Windows Media Player in combination with the SDHC drivers. I believe using a different media player (such as TCPMP, PocketPlayer, or another that is lighter on resources) is a workaround for now until this can be sorted out.

**luv2chill** · #**153** (**permalink**) 11-07-2007, 06:08 PM

Quote:

Originally Posted by cjbreisch

I installed the acbToggleBT module, but there doesn't appear to be a shortcut for it in Programs.

It installs as "Audio Gateway" in \Programs.

cjbreisch · #**154** (**permalink**) 11-07-2007, 07:36 PM

Quote:

Originally Posted by luv2chill

It installs as "Audio Gateway" in \Programs.

Ah. Silly me. Thanks.

I was all set to complain that I can't get bluetooth working at all with a ROM built from this kitchen. Then I realized I'm using my new (refurb) from Asurion that I got yesterday and I've never tried bluetooth on it before. So, I flashed back to a stock ROM, and yep...no bluetooth. I'm off to the Sprint store again.

I wonder if they'll give me a Mogul. I'm not sure I want one. A few weeks ago, I would've said yes, absolutely, but I'll miss this kitchen.

jspenc3 · #**155** (**permalink**) 11-07-2007, 07:48 PM

I just had my first showstopper issue with the original wm6 kitchen. It is a fairly basic build with the Vogue dialer. I was talking on the phone with a wired headset and a vzw oem car power cable connected. I got home so I pulled the wired headset out and put the phone to my ear, but it seems the audio didn't switch over (it did with verizonguy's wm6 kitchen or previous wm5 builds). All I got was dead silence. I then tried speakerphone, but the button just flashed and it didn't turn on.

So I soft reset the phone with the stylus (forgot to use the software method) and it stuck at the windows mobile boot screen. Soft reset again and it booted, but when I tried to call the person back it was still no incoming audio. She then tried to call me and I couldn't answer it, the phone didn't respond to pressing the soft or hard keys to answer. So I rebooted several more times and it still didn't work. So I hooked up the headset again and that finally got it working again.

Not sure if this is yet another issue with the vogue dialer (which included the smartdial from the kitchen) or something else...

**luv2chill** · #**156** (**permalink**) 11-07-2007, 07:55 PM

Quote:

Originally Posted by jspenc3

I just had my first showstopper issue with the original wm6 kitchen. It is a fairly basic build with the Vogue dialer. I was talking on the phone with a wired headset and a vzw oem car power cable connected. I got home so I pulled the wired headset out and put the phone to my ear, but it seems the audio didn't switch over (it did with verizonguy's wm6 kitchen or previous wm5 builds). All I got was dead silence. I then tried speakerphone, but the button just flashed and it didn't turn on.

So I soft reset the phone with the stylus (forgot to use the software method) and it stuck at the windows mobile boot screen. Soft reset again and it booted, but when I tried to call the person back it was still no incoming audio. She then tried to call me and I couldn't answer it, the phone didn't respond to pressing the soft or hard keys to answer. So I rebooted several more times and it still didn't work. So I hooked up the headset again and that finally got it working again.

Not sure if this is yet another issue with the vogue dialer (which included the smartdial from the kitchen) or something else...

Not sure about your freezing issues (doubtful they are related to the headset--but please post a list of what OEMs you included and what other programs you installed), but issues with the wired headset are numerous and are not ROM specific. The jack gets "stuck" thinking that a headset is still plugged into it, so no sound will come out of your earpiece/speaker. The "cure" (for who knows how long) is to plug in and pull out your headset plug repeatedly until the jack gets "unstuck".

**guitardoc64** · #**157** (**permalink**) 11-07-2007, 09:51 PM

Quote:

Originally Posted by luv2chill

Not sure about your freezing issues (doubtful they are related to the headset--but please post a list of what OEMs you included and what other programs you installed), but issues with the wired headset are numerous and are not ROM specific. The jack gets "stuck" thinking that a headset is still plugged into it, so no sound will come out of your earpiece/speaker. The "cure" (for who knows how long) is to plug in and pull out your headset plug repeatedly until the jack gets "unstuck".

Yes the little 2.5mm jack problem....the jack contacts can get stuck open because of lint, dust etc. or just get worn or oxidised. The plug and unplug method will work by moving the contacts until they connect to redirect the audio, but a better method is to use the core of a #2 pencil. Tne "lead" is really carbon and clay, and will burnish the dirt off and clean the contacts. I got the idea from a tool I use at work called the "conductool" which is for the 1/4" jacks used in guitars and amps. It's basically a 1/4" stick of carbon, and is a lifesaver! I suggest being very gentle with the pencil core since it's quite easily broken but it might save a trip to the Sprint/Verizon/Alltell store for somebody.

synaptyc · #**158** (**permalink**) 11-07-2007, 10:12 PM

BUG: MobiTV2 (v4.4.1.15863) doesn't load tv stations if you build a ROM that includes HTC Touch Keypad.
Quite a shame too. I really like that SIP, but I REALLY like MobiTV2 better.
... better that SprintTV due to the frame rate... Anyway... back on topic:
I tried many different builds of the ROM, from stripped down, to fairly loaded. Same result. If HTC Touch Keypad was included... No MobiTV2.
Hope this helps someone.
~Syn

jspenc3 · #**159** (**permalink**) 11-07-2007, 11:38 PM

Quote:

Originally Posted by luv2chill

SPB apps can be resource hogs and I am unfamiliar with the other app. If you have time, please build a ROM without any additions to it (use the stock selections.txt) and see if you still get the same issue. If not then it is a problem relating to one of those applications (or the combination of them).

But MS has gone on record saying that there are performance issues when you have a very large contacts database (more than 100 or so), so that could come into play as well.

It hasn't happened again so far, but I don't think my list of 275 contacts and less than a hundred appointments is excessive. If the cause is the SPB or calendar+ software, then it is caused by either WM6 or the kitchen, because it never happened with any version of WM5 in the 1.5 years I've had the phone. I have seen the calendar+ program pause on occasion (but never slow down activesync or the PPC), but since it's not being developed anymore that I know of it is just WM5 certified so who knows...I'll keep watching it.

jspenc3 · #**160** (**permalink**) 11-07-2007, 11:44 PM

Quote:

Originally Posted by luv2chill

Not sure about your freezing issues (doubtful they are related to the headset--but please post a list of what OEMs you included and what other programs you installed), but issues with the wired headset are numerous and are not ROM specific. The jack gets "stuck" thinking that a headset is still plugged into it, so no sound will come out of your earpiece/speaker. The "cure" (for who knows how long) is to plug in and pull out your headset plug repeatedly until the jack gets "unstuck".

Yea, figured it was something with the jack. Surprised it could be a hardware issue though, I figured that would be all software controlled. I think it may have happened once before, but not in a long while. I still find it strange that rebooting didn't fix it, and then it kept locking up and not answering when I hit any of the normal answer buttons.

Oh well, I'll flash again in another week after we get through a few more kitchen refinments. I want to get rid of the Vogue dialer anyway but can't waste the time rebuilding more than once a week

As for my OEMs, it was mostly stock. I have the file saved at work, but I tend to keep it simple in order to install software updates more easily. Off my head, I think I selected .net 2/3.5, vogue dialer, office 2007, eten keypad, voice command, verizon, and a few other little apps like wm5storage.