Apache WM6 CE OS 5.2.1620 (Build 18125.0.4.2) Bugs/Patches

[saturn2069a]

Originally Posted by kazer

Anyone have any input on how to get the character count back on text messages?

Noticed this too... would love to see an answer.

I did some comparing last night w/ my roommate's 6700 that we hadn't upgraded yet. I found this key on both devices:

HKLM\System\Inbox\Handlers\ComposeBodyCount={c59db 2e9-601c-423b-8bf3-352be01b89ba}

However, the corresponding "{c59db2e9...." Key was NOT in HKClassesRoot on my upgraded WM6 device. So I tried exporting that key from HKCR on his and importing in onto mine, reset the device and still no character count.

Unfortunately he had to work today and took his phone with so I can't keep playing with both... But maybe that will point someone else in the right direction?

[wwalker911]

Originally Posted by saturn2069a

Noticed this too... would love to see an answer.

I did some comparing last night w/ my roommate's 6700 that we hadn't upgraded yet. I found this key on both devices:

HKLM\System\Inbox\Handlers\ComposeBodyCount={c59db 2e9-601c-423b-8bf3-352be01b89ba}

However, the corresponding "{c59db2e9...." Key was NOT in HKClassesRoot on my upgraded WM6 device. So I tried exporting that key from HKCR on his and importing in onto mine, reset the device and still no character count.

Unfortunately he had to work today and took his phone with so I can't keep playing with both... But maybe that will point someone else in the right direction?

Ok, I have a Sprint PPC 6700 with the stock WM5. It also has the same classid listed as above.
The registy entries under HKCR\CLSID\={c59db2e9-601c-423b-8bf3-352be01b89ba} are:

Default = "HTMLNote Compose Body Count Handler"
\InProcServer32\Default = "htmlnote.dll"
\InProcServer32\ThreadingModel = "Free"

My guess would be if you duplicated these entries and copied the htmlnote.dll to the new OS it just might work.

[OMJ]

Firstly, thanks Helmi & all involved for all your hard work, it is much appreciated!

I've been running this WM6 ROM since Fri, and everything is great, only 1 small problem I am having, it's the same problem I had running the 1.0.4 kitchen, where weatherpanel & Windows Live (messenger) do not play nice together. On my first flash I had everything setup & installed (including Live) prior to installing WP, with no problem. The I installed WP, it ran fine until I soft reset, then it would not boot, it would hang @ the WM screen. Multiple resets, never would boot. Hard reset and setup & installed everything w/o Live, all is good.

Thanks again.

[Trident]

Does anyone else notice that this ROM sometimes has a problem recognizing that it is charging in a non-OEM device (namely a car charger). I didn't have a problem until yesterday, when I had to reset no less than 10 times in a two-hour span. I also noticed that if I reset while it was connected to the charger when it finished rebooting the OS determined that the battery was at 10% and gave me critically low battery warnings. At the time, the battery had no less than a 60% charge- probably more.

[hecatomb]

Originally Posted by Trident

Does anyone else notice that this ROM sometimes has a problem recognizing that it is charging in a non-OEM device (namely a car charger). I didn't have a problem until yesterday, when I had to reset no less than 10 times in a two-hour span. I also noticed that if I reset while it was connected to the charger when it finished rebooting the OS determined that the battery was at 10% and gave me critically low battery warnings. At the time, the battery had no less than a 60% charge- probably more.

I had the reset while charging problem on every AKU (even stock) on my 6700; It would recognize the battery level fine after about 5 minutes, but it was kind of annoying.

[InvincibleLiving]

Originally Posted by hecatomb

I had the reset while charging problem on every AKU (even stock) on my 6700; It would recognize the battery level fine after about 5 minutes, but it was kind of annoying.

Ditto, I've experienced this on every AKU and ROM, have yet to see it occur on WM6 yet though.

[thisguyinoc]

Originally Posted by hecatomb

I had the reset while charging problem on every AKU (even stock) on my 6700; It would recognize the battery level fine after about 5 minutes, but it was kind of annoying.

Yes, I noticed this problem as well. I was driving home from Las Vegas this weekend with Live Search tracking my GPS, I had the phone plugged into the charger with the charging status, then all of sudden the phone reboot and when it came back up, it said the battery level was low blah blah blah. After that I couldn't get it to recognize my charger.

[F16Vet]

Originally Posted by Trident

Does anyone else notice that this ROM sometimes has a problem recognizing that it is charging in a non-OEM device (namely a car charger). I didn't have a problem until yesterday, when I had to reset no less than 10 times in a two-hour span. I also noticed that if I reset while it was connected to the charger when it finished rebooting the OS determined that the battery was at 10% and gave me critically low battery warnings. At the time, the battery had no less than a 60% charge- probably more.

MAN am I glad to know I wasn't the only one to have this! Been running the WM6 ROM since Saturday and aside from a few hiccips IT ROCKS! MUCH faster, more stable, more functional etc.

But yesterday I was ready for the ole "PPC6700 MEETS BRICK FIREPLACE MODE". I must have tried for nearly an hour and a half to get any kind of charging to work. I tried 2 different mobile chargers (NON-OEM), the stock cradle, a zillion soft resets and even a HARD reset. Removed the battery-twice. Nothing worked.

I finally left the battery out for about 20 minutes, did a hard reset when it finally came back on (had a black screen for a L-O-N-G time--sweatin' a bricked phone) and got it to charge again. Wierd thing is it ALWAYS charged at home hooked up to my laptop (USB) but I wasn't home at the time.

Still don't know what the deal was, but glad I had (and used) SPB Backup. Didn't lose a thing. BTW SPB Backup fit great into the EXT_ROM2 space. ROM available space, 1107 KB; SPB size: 1047. Still got 60 KB left!

[Trident]

Originally Posted by F16Vet

MAN am I glad to know I wasn't the only one to have this! Been running the WM6 ROM since Saturday and aside from a few hiccips IT ROCKS! MUCH faster, more stable, more functional etc.

But yesterday I was ready for the ole "PPC6700 MEETS BRICK FIREPLACE MODE". I must have tried for nearly and hour and a half to get any kind of charging to work. I tried 2 different mobile chargers (NON-OEM), the stock cradle, a zillion soft resets and even a HARD reset. Removed the battery-twice. Nothing worked.

I finally left the battery out for about 20 minutes, did a hard reset when it finally came back on (had a black screen for a L-O-N-G time--sweatin' a bricked phone) and got it to charge again. Wierd thing is it ALWAYS charged at home hooked up to my laptop (USB) but I wasn't home at the time.

Still don't know what the deal was, but glad I had (and used) SPB Backup. Didn't lose a thing. BTW SPB Backup fit great into the EXT_ROM2 space. ROM available space, 1107 KB; SPB size: 1047. Still got 60 KB left!

I just tried something to see if there was a difference and it worked.
Before I started having this issue, I had switched the advance USB-PC setting off to help make the transition to Activesync work more reliably.
As I have noticed recently that it really wasn't that consistently reliable, I turned it back on and voila- I haven't seen this charging recognition issue again.
I don't know that this is guaranteed, but it seems to be working for now.

[Maxx134]

Originally Posted by Trident

I just tried something to see if there was a difference and it worked.
Before I started having this issue, I had switched the advance USB-PC setting off to help make the transition to Activesync work more reliably.
As I have noticed recently that it really wasn't that consistently reliable, I turned it back on and voila- I haven't seen this charging recognition issue again.
I don't know that this is guaranteed, but it seems to be working for now.

Interesting as I have not only seen this prob in this rom, biut also on different OS and different unit before I had it replaced. I usually get it to recognize its charging by turning unit off for a few seconds, then plugging in while it is off and then charging led goes on...