NapatC - N2 Space: Technical

Napat's profileNapatC - N2 SpaceBlogListsGuestbookMore

Tools

Help

Blog

Summary

Listed by:

<< First < Previous Next > Last >>

December 14

Dopod 838 Pro - A2DP patch

Recently I bought Jabra BT320s for my dad. It is stereo Bluetooth handfree which is kind of cool except when I tried with my PPC its sound was very crappy & choppy so I went on searching for any clue that might be. So what I have found is the issue with Bluetooth stack in Windows Mobile isn't as good as it should be and there is something must be done to cure to choppy sound.

Most of websites I found recommend to change registry, kind of risky though but it's quite make sense to me. I went on trying many set registry some make it better some doesn't make any difference at all.

Here I come with my final setup, at least with this setting my Dopod 838 Pro A2DP is very stable with chopping of shound.

Open registry and do following steps:

HKEY_LOCAL_MACHINE\Drivers\BuiltIn\BtA2dpSnd
add "Priority256 "= dword:60 (Dword Value - Decimal)

HKEY_LOCAL_MACHINE\ SOFTWARE\ Microsoft\Bluetooth\ A2DP\Settings
UseJointStereo: 2 (Dword Value - Decimal)

after finsh exit from registry then do soft-reset (turn off your PPC might be more effective)

Testing Tools:
Dopod 838 Pro (ROM: 1.23.707.4 - date 21/07/06)
Jabra BT320s

Music Player (on Pocket PC)
Pocket Music (supports AVRCP)

Pocket PC reminder issue fixing

After long time of searching, finally I found one post that sound make sense to me. Here it is:

I registered to this site just so I could help explain why WM5 reminders stop working and how to fix. Like youselves, I suffered the same problem every couple of weeks, had no idea what the root cause was, and sadly had to either hard reset and reload all my apps or if I was lucky enough, restore a previous backup from when reminders still worked.

Anyhow, the problem is quite simply that Windows Mobile 5 runs a little maintenance job every midnight to sync up the clock and the calendar (WM2003 has this feature , incidentally). If you happen to have an alarm set for midnight (like you might have a birthday or other all-day event with an alarm attached) and this maintenance job quits before your alarm does, you're screwed. The maintenance job is scheduled to last exactly 15 seconds, and if you have a lot of PIM data on your PPC you might need 20 seconds, for example, for the device to execute the alarm. The net resulting effect here is an alarm that only half triggered and an alarm notification database (on the device) out of sync with the alarms it was supposed to have triggered in the first place.

There are two fixes for this and neither involve hard reseting your device, fortunately.

(Quick Fix - additional software required)

1. Identify the offending reminder - it's most likely the last reminder you had that was supposed to trigger at midnight. If you have Microsoft Voice Command installed, reboot the device and listen for the first reminder that's announced (probably someone's birthday or other all-day event)

2. Run CLOCKNOT.EXE in \windows (hidden ROM file) - this will resync the clock with the CPU.

3. Run CALNOT.EXE in \windows (hidden ROM file) - this resync the calendar (and notification database) with the clock.

4. Let device sit for a few minutes for both these programs to fully execute in the background.

5. While you're waiting, run SKTools or MemMaid and remove the offending alarm from the notifications database (look for time codes of "month day 0 0 year month next-day 0 0 year) -- the "0 0" represents midnight in zulu/universal/military time. If you don't already, you'll need to install one of these tools, you can get from handango.com or elsewhere.

5. Optionally reboot the device (soft reset). Problem Fixed.

OPTION: Install the freeware app "WAKEUP TWEAK" to bump up the overnight maintenance window up from 15 seconds to 60 seconds to hopefully keep this problem from happening again.

(Overnight Fix - additional software required)

If you don't want to install any more s/w on your device, keep the device on at midnight so that the maintenance routine can properly finish instead of being shutdown after 15 seconds.

Before you go to bed (and before midnight, device time), plug the device into the wall or battery charger, and set the power settings in Control Panel so that the device won't automatically shut down after a specified amount of time (it'll be permanently on when using AC power). You can allow the backlight to switch off if it bothers you to have the backlight on overnight.

The overnight maintenance can now properly finish without being aborted prematurely. Reminders should now work again.