Let's all try to fix the charging issue.. [Archive]

andrew_sh

20th January 2007, 05:36 PM

... since this problem is bugging us with aku3.x and crossbow roms.

Especially with the crossbow rom, this seems to be the only problem. The other issues are already fixed, or are easy to get fixed (since they have already been fixed in earlier roms).
In addition to this, I think that if we work together we have greater chances of solving this frustrating issue.

So this is what I have tried (with no success):

1) replace the battdrv.dll with one from a prophet
I get the common result where the device will charge only when you softreset with the cable inserted. You also get a square in the "Model No" in device information (Module address conflict?) Someone solved the square issue in an aku 3.x rom. I would like to know how it was fixed.
2) replace the battdrv.dll with one from an HTC artemis
No charging/status indication. Model No is reported as "WIZA200"
3) I unloaded camera and keyboard driver to see if there are any conflicts with them - no difference

ikarus

20th January 2007, 06:52 PM

... since this problem is bugging us with aku3.x and crossbow roms.
A possible way is to write a wrapper for the batterydriver, which logs information and try finding the differences in pnp, etc.. between a working rom and a non working rom with the prophet-driver.

You could try following too:
- don't touch the batterydriver in original aku3-rom
- do following while device finished boot and os is running:
- copy battdrvr.dll from prophet and rename it to \windows\battdrvr_New.dll (into the new rom)
- change the registry-value HKLM\Drivers\BuiltIn\Battery\Dll = battdrvr_New.dll
- wait some minutes and do a softreset
-->it will not survive a hard-reset, but i guess this could solve module-overlapps..

hope this helps,
ikarus

andrew_sh

21st January 2007, 01:00 PM

A possible way is to write a wrapper for the batterydriver, which logs information and try finding the differences in pnp, etc.. between a working rom and a non working rom with the prophet-driver.

You could try following too:
- don't touch the batterydriver in original aku3-rom
- do following while device finished boot and os is running:
- copy battdrvr.dll from prophet and rename it to \windows\battdrvr_New.dll (into the new rom)
- change the registry-value HKLM\Drivers\BuiltIn\Battery\Dll = battdrvr_New.dll
- wait some minutes and do a softreset
-->it will not survive a hard-reset, but i guess this could solve module-overlapps..

hope this helps,
ikarus
Thanks for the info.
I just tried it.
Result:
I get the square in the device info.
No charging/no battery status.
Strange isn't it? I wonder why the model no gets f**d up.

MusicMike

21st January 2007, 02:51 PM

To my knowledge, "usbfn.dll" is involved as well, so maybe you gotta play around with that one as well...

andrew_sh

21st January 2007, 04:36 PM

To my knowledge, "usbfn.dll" is involved as well, so maybe you gotta play around with that one as well...

I tried replacing this file. The result is that activesync stops working completely.

ikarus

21st January 2007, 04:39 PM

To my knowledge, "usbfn.dll" is involved as well, so maybe you gotta play around with that one as well...
i do agree.. don't know which dll's, but maybe there are more dll's used for battery..
There is a tool called depends or similar, which can figure this out..

depends is part of free eVC++ (\Program Files\Microsoft eMbedded C++ 4.0\Common\Tools\depends.exe)

ikarus

Jesterz

21st January 2007, 05:47 PM

i do agree.. don't know which dll's, but maybe there are more dll's used for battery..
There is a tool called depends or similar, which can figure this out..

depends is part of free eVC++ (\Program Files\Microsoft eMbedded C++ 4.0\Common\Tools\depends.exe)

ikarus

ahh, thats a handy tool, thanks for the tip !

ikarus

25th January 2007, 11:44 PM

attached is a cab which could fix this issue.
my contribution to the great work of our rom-cooker :D

ikarus

andrew_sh

26th January 2007, 12:09 AM

attached is a cab which could fix this issue.
my contribution to the great work of our rom-cooker :D

ikarus

Thanks ikarus, i'll try tomorrow.
So have you tried this? Did you find out what was causing the problem?

ikarus

26th January 2007, 12:13 AM

So have you tried this?
MusicMike tested it, but it needs more testing hehe

Did you find out what was causing the problem?
not yet... in part yes, but i don't want to write explanations which could turn out to be wrong...

Jesterz

26th January 2007, 12:55 PM

I'm back, testing it now

rvbcrs

26th January 2007, 01:06 PM

I'm back, testing it now

Welcome back! hehe damn it's been a long time ;)

jutley

26th January 2007, 01:57 PM

okay i have the japnease wm6 rc7 both files its all in jap appantly the battrey issue is fixed and all the other problems can someone help me to convert the language into english and then i can test on my prophet we may have a fully working wm6 rom here guys please need help for final stages.

jutley

26th January 2007, 02:40 PM

Hi i just installed wm6 rc7 and i can confirm usb charging and sound all works on prophet flawlesly i need a hero to covert the language into english please can someone help

ikarus

28th January 2007, 09:59 PM

so I was just wondering what does the app change in my phone to make it work... I didn't eve have to soft reset it once...

Hi i just installed wm6 rc7 and i can confirm usb charging and sound all works on prophet flawlesly...
great. i have some thoughts about the cause, but i don't have an verified explanation for the cause.

Actually i don't have enough time to do more investigation for... So i can explain what the cab is doing.

It's a very slight solution.
The cab creates a notification for the "Notification Broker", which in turn starts XDADev_BatFix.exe each time usb gets connected.
(That is there is no extra thread running, there is no dll loaded, there is no system service running and no extra resource needed. It is almost like before.)

XDADev_BatFix.exe does only set a PowerEvent and exits afterwards.

that's it.

Best regards,
ikarus

guitarz

28th January 2007, 11:36 PM

anyone sucess pls post...
i'll try tomorrow

c3l5o

29th January 2007, 12:54 AM

great. i have some thoughts about the cause, but i don't have an verified explanation for the cause.

Actually i don't have enough time to do more investigation for... So i can explain what the cab is doing.

It's a very slight solution.
The cab creates a notification for the "Notification Broker", which in turn starts XDADev_BatFix.exe each time usb gets connected.
(That is there is no extra thread running, there is no dll loaded, there is no system service running and no extra resource needed. It is almost like before.)

XDADev_BatFix.exe does only set a PowerEvent and exits afterwards.

that's it.

Best regards,
ikarus

Ok thanks ikarus! Really is a smart and slight solution ;)

anyone sucess pls post...
i'll try tomorrow

It IS working indeed

hatchet74890

13th February 2007, 09:34 AM

This fix tested and working on Qtek S200! Its one of the 2,2 clean roms from a few months ago. The battery problem has been my biggest annoyance! Thanks!

mewwoo

16th February 2007, 03:36 AM

I also tried XDADev_BatFix on my 818Pro with AKU3.3-Jester-b1 ROM.
Looks like it really solve the battery charge problem.

Thanks ikarus!

colonelbassel

16th February 2007, 09:37 AM

It Worked on I-mate JamIn, Thanks.
some times the device do not wake up after it sleeps

Jesterz

16th February 2007, 03:59 PM

Yes it works, however if you put your phone into sleep mode, and then attached the mains charger, it doesnt start to charge, you have to wake it up for it to start.... back ok, at least it charges :)

qdabean

16th February 2007, 09:59 PM

This fix does not seem to make a difference on my G3 running WM6 (the http://nghianga.4shared.com version). I can't seem to charge it at all (or at least the charge LED does not light up) no matter what I do. Any suggestions What I am going to do when it finally runs out ... how am I going to charge or reflash a flat phone? Should I reflash it with an older ROM (such as 2.20) now?

KoolPal

17th February 2007, 08:11 AM

qdabean

17th February 2007, 09:41 AM

qdabean,

Do a soft reset when connect to your usb / main charger. The charging will start. That how I charge my g4 prohpet using PDAVIET 3.

The cab file posted here does not seem to help me.

Hope this info helps you.

BINGO! After trying what I thought was everything your tip does the trick ... at least I can charge my Prophet now. Thanks.

KoolPal

20th February 2007, 06:22 PM

Hi qdabean,

Glad to be of help. Always glad to give back to this forum!

bootrecord

21st February 2007, 04:12 PM

worked well with my G3, thanx much

R0N1N

21st February 2007, 07:48 PM

Worked on my O2 Neo with WM6

ikarus

23rd February 2007, 12:48 AM

This fix does not seem to make a difference on my G3 running WM6..
yes this is correct. This fix is designed for WM5 making use of prophet-battery-driver in [i guess] wizard-roms :D
(i had only wm5-tester for testing while investigating)

Battery-issue on Crossbow is not the same (i guess) and [fix] will not work for WM6 (it's very likely)...

btw. welcome back Jesterz ;)

Regards,
ikarus

Rayan

23rd February 2007, 01:03 AM

Hi folks!

What exactly is wrong with the battery charging issue?

I just installed NB_Update_nghianga on my G3 Prophet and I don't see any problems charging my device...

Should I expect any problems after some time or is this version already fixed?

I've soft reset (USB unplugged) several times already and still all is OK.

Thanks!
Rayan

P4k1t0

23rd February 2007, 02:47 PM

Rayan

23rd February 2007, 09:26 PM

you have tried whit this rom wm6? Prophet_2007 update Full N2N (20-02-2007).exe

The ROM I installed is NB_Update_nghianga.rar

Which one is better?:

Prophet_2007 update Full N2N (20-02-2007).exe

or

NB_Update_nghianga.rar

TIA,
Rayan

P4k1t0

23rd February 2007, 09:28 PM

The ROM I installed is NB_Update_nghianga.rar

Which one is better?:

Prophet_2007 update Full N2N (20-02-2007).exe

or

NB_Update_nghianga.rar

TIA,
Rayan

i dont know...i have Prophet_2007 update Full N2N (20-02-2007).exe
and is working very well... !!

jangotangos

25th February 2007, 03:40 AM

I used NB_Up_nghianga and I am experiencing the USB charge issue.

Is there a CAB fix for this bug?

s_rajme

25th February 2007, 02:47 PM

The ROM I installed is NB_Update_nghianga.rar

Which one is better?:

Prophet_2007 update Full N2N (20-02-2007).exe

or

NB_Update_nghianga.rar

TIA,
Rayan

Both are basically the same only update methods are different. "Prophet_2007 update Full N2N (20-02-2007).exe" uses RUU (rom update utility) and while "NB_Update_nghianga.rar" uses batch file method for upgrade.

____________________