Database Info

Let's all try to fix the charging issue..

... 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

andrew_sh said:
... since this problem is bugging us with aku3.x and crossbow roms.
Click to expand...
Click to collapse
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

ikarus said:
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
Click to expand...
Click to collapse
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.

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

MusicMike said:
To my knowledge, "usbfn.dll" is involved as well, so maybe you gotta play around with that one as well...
Click to expand...
Click to collapse
I tried replacing this file. The result is that activesync stops working completely.

MusicMike said:
To my knowledge, "usbfn.dll" is involved as well, so maybe you gotta play around with that one as well...
Click to expand...
Click to collapse
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

ikarus said:
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
Click to expand...
Click to collapse
ahh, thats a handy tool, thanks for the tip !

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

ikarus said:
attached is a cab which could fix this issue.
my contribution to the great work of our rom-cooker
ikarus
Click to expand...
Click to collapse
Thanks ikarus, i'll try tomorrow.
So have you tried this? Did you find out what was causing the problem?

andrew_sh said:
So have you tried this?
Click to expand...
Click to collapse
MusicMike tested it, but it needs more testing hehe
andrew_sh said:
Did you find out what was causing the problem?
Click to expand...
Click to collapse
not yet... in part yes, but i don't want to write explanations which could turn out to be wrong...

I'm back, testing it now

Jesterz said:
I'm back, testing it now
Click to expand...
Click to collapse
Welcome back! hehe damn it's been a long time

HELP
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.

WM6 100% working on prophet
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

c3l5o said:
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...
Click to expand...
Click to collapse
jutley said:
Hi i just installed wm6 rc7 and i can confirm usb charging and sound all works on prophet flawlesly...
Click to expand...
Click to collapse
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

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

ikarus said:
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
Click to expand...
Click to collapse
Ok thanks ikarus! Really is a smart and slight solution
guitarz said:
anyone sucess pls post...
i'll try tomorrow
Click to expand...
Click to collapse
It IS working indeed

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!

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!

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

Tom Tom 6 on WM5

Just loaded a copy of TomTom 6 to my device, the software runs fine but it turns off the backlight as soon as it loads and I can only see it in the sunlight! Anyone have any idea how to fix this?
Thanks
Martin

Try this!
I had the same problem.
Copy it over to the existing EXE. It worked for me!
Make sure you make a copy of the original file just incase it doesn't work and you need to restore it.

There are many post about this try to search!
I have done it by adapting the programm with a hex-editor. This is also discribed in many posts.
Mach2005

Thanks!
Just loaded the file provided by spoonfork, caused the phone to lock up for some reason but a reset got it going again - and I can now find my way home without using a torch!
Great help, thanks again.
Martin

I loaded the latest 6.03 TomTom6 and didn't have to bother with this patch. Was having trouble with the old tomtom6 i was running, just reseting my device randomly and running slow.

does it work for tom tom 5.21 ? I have the same problem too...
@mach2005
I tried to search but could you give specific clue... ?
sorry I am newbie.....

New tool for Rotation display

I make this tool for quickly rotion display in Tornado, it's a part of my cooked ROM.
- Press comm button for rotation and restore. Can set default rotation in settings
- Setting tool is smaller and quickly
Thank all in this thread:
http://forum.xda-developers.com/showthread.php?t=318178
Thank to kartam
Please install sdkcerts.cab or WMtequan.cab first.

nncuong said:
I make this tool for quickly rotion display in Tornado, it's a part of my cooked ROM.
- Press comm button for rotation and restore. Can set default rotation in settings
- Setting tool is smaller and quickly
Thank all in this thread:
http://forum.xda-developers.com/showthread.php?t=318178
Thank to kartam
Please install sdkcerts.cab or WMtequan.cab first.
Click to expand...
Click to collapse
Why dont you post your cooked ROM here too. Is it English or Vietnamese?
Thanks
p/s
I installed the sdkcerts followed with this cab. I get the response "Sorry, your current display driver doesnt support this display mode!"
What's wrong?
thanks

Change driver from ddi.dll to ddivox.dll, It'll support rotation.
My cooked ROM have Vietnamese font only. It has based on shark's rom and has Landscape background (which is removed in orther rom)

nncuong said:
Change driver from ddi.dll to ddivox.dll, It'll support rotation.
My cooked ROM have Vietnamese font only. It has based on shark's rom and has Landscape background (which is removed in orther rom)
Click to expand...
Click to collapse
Yes! I changed it to the ddivox.dll. It responded with a soft reset. Now my phone is dead at the splash screen. I am now re-flashing the ROM. ahhhhhh.....
BTW does your pBAR support Tornado?
Thanks

Hello, i have same problem and i resolve to change the driver to ddivox.dll but in this program the action change joystick in Landscape is grey and in Landscpae mode the joystick no change direction.
What's rong ?
thanks
ps : sorry for my english

LOL, we should have fixed the joystick orientation and screen refresh issue before releasing a new tool. Anyway, good job there.
I wish to remind all of u, if u use vox dll, the screen will not refresh itself, unless u press a button. As in, if your phone goes idle at 5pm, it will show 5pm even at 12am, till u press a button to refresh the screen

karhoe said:
LOL, we should have fixed the joystick orientation and screen refresh issue before releasing a new tool. Anyway, good job there.
I wish to remind all of u, if u use vox dll, the screen will not refresh itself, unless u press a button. As in, if your phone goes idle at 5pm, it will show 5pm even at 12am, till u press a button to refresh the screen
Click to expand...
Click to collapse
Thanks Buddy. I had to reinstall the ROM.

illi said:
Thanks Buddy. I had to reinstall the ROM.
Click to expand...
Click to collapse
Hey illi... Thanks for being the guinea pig on this one! Saved me from crashing my phone! I love testers!

bipinsen said:
Hey illi... Thanks for being the guinea pig on this one! Saved me from crashing my phone! I love testers!
Click to expand...
Click to collapse
You're welcome. Glad you appreciate my guinea pigging that #*$ software. Consoled me though.
Still not finished tweaking my registry and its passed 2 am here.

illi said:
You're welcome. Glad you appreciate my guinea pigging that #*$ software. Consoled me though.
Still not finished tweaking my registry and its passed 2 am here.
Click to expand...
Click to collapse
That's exactly my gripe with trying out new ROMs too. Getting the registry back to it's optimal condition takes longer than anything else in the process. I've gone to using Sprite to do a backup when trying out new software. Problem? Hard reset => run backup => back as new!

bipinsen said:
That's exactly my gripe with trying out new ROMs too. Getting the registry back to it's optimal condition takes longer than anything else in the process. I've gone to using Sprite to do a backup when trying out new software. Problem? Hard reset => run backup => back as new!
Click to expand...
Click to collapse
Yep, I second that - I have tried varius backup programs before, but they were very limited in case of restoring system databases, or locked files. I have bought Sprite Backup, and I can backup - change ROM - restore - continue working in 15 minutes, leaving everything in!

XXX
Never use this software...!!!!!
it makes my 577w crashed
i can't start enter the windows now

Obviously you did not install the sdk or wntenquan as instructed. . .
Its your own fault

yep, smth wrong with your hands.dll or maybe even brain.dll... update them

followed all directions and it work like a charm for me ^^ very impressive app mate good job A+++

Guys please post step by step guide for the installation process. Many people wanna try it but the fear of crash is high enough to wait more

heres a little guide for ya guys:
step 1:download this and this
step 2;instal them on your phone or card wich ever you like
step 3:download the rotation display tool on the first post
step 4: install it
step 5: after installing both certificates and the rotation tool execute the "display manager" app on your phone then go to menu/change driver and select the "vox display driver(experimental)" after that the phone will reboot and then after the reboot, execute the "display manager" app again and select the orientation of your choice and thats it it should work 100% i did this on my tornado and it work first try.
hope it helps guys

rafyvitto said:
heres a little guide for ya guys:
step 1:download this and this
step 2;instal them on your phone or card wich ever you like
step 3:download the rotation display tool on the first post
step 4: install it
step 5: after installing both certificates and the rotation tool execute the "display manager" app on your phone then go to menu/change driver and select the "vox display driver(experimental)" after that the phone will reboot and then after the reboot, execute the "display manager" app again and select the orientation of your choice and thats it it should work 100% i did this on my tornado and it work first try.
hope it helps guys
Click to expand...
Click to collapse
Thank you will try

Could someone please add WMtequan.cab into my TDM or nncuong's pRot so that no more people would need to HR if they forgot. I must say that I myself had to hard reset lately because I forgot to install the WMtequan.

Sadly, it doesnt fix the screen refresh issue, so its annoying especially when I want to know he call duration or the time

strange messages after upgrade to WM6.1 3.2 thingonaspring.5.2.1933.18533.REALVGA

Hi,
I've just upgraded my mda pro to wm6.1, specifically 3.2 thingonaspring.5.2.1933.18533.REALVGA
On start up or reboot, I get two pop up box errors.
ssdamon.exe
"THE FILE "SDDAEMON" CANNOT BE OPENED. eITHER IT IS NOT SIGNED WITH A TRUSTED CERTIFICATE, OR ONE OF ITS COMPONENTS CANNOT BE FOUND.IF THE PROBLEM PERSISTS, TRY REINSTALLING OR RESTORING THIS FILE"
elatepushservice.exe
The file elatepushservice.exe can not be opened .....
I've tried reflashing and cold reboots, but its still the same. The other functions work fine as far as I can tell.
Also I think the mda pro has retained some of my old settings, i.e. it has remembered the outgoing call duration, even after the rom upgrade ! Is there a way of clearing this info ??
Can any one help ?
Thanks
fs

Try finding the cab "sdkcerts.cab" to disable certificate checks and try it else reflash the rom once again and try.
fyi, the rom you're flashing is a WM6.0 build and NOT wm6.1

Fix?
Had the same issue, but it was related to a file that was removed from the windows directory search the ROM thread I think the file was something like olce?.dll to confirm its the same issue try installing isilo and see if the same error happens.

Hi guys where is Thingonaprings 6.1 ROM I didn't relise he'd released on?

No, he’s just confused between WM 6.0 and WM 6.1 it did take me a while to realize I am not superman too.
WizP said:
Hi guys where is Thingonaprings 6.1 ROM I didn't relise he'd released on?
Click to expand...
Click to collapse

firestormer said:
Hi,
I've just upgraded my mda pro to wm6.1, specifically 3.2 thingonaspring.5.2.1933.18533.REALVGA
On start up or reboot, I get two pop up box errors.
ssdamon.exe
"THE FILE "SDDAEMON" CANNOT BE OPENED. eITHER IT IS NOT SIGNED WITH A TRUSTED CERTIFICATE, OR ONE OF ITS COMPONENTS CANNOT BE FOUND.IF THE PROBLEM PERSISTS, TRY REINSTALLING OR RESTORING THIS FILE"
elatepushservice.exe
The file elatepushservice.exe can not be opened .....
I've tried reflashing and cold reboots, but its still the same. The other functions work fine as far as I can tell.
Also I think the mda pro has retained some of my old settings, i.e. it has remembered the outgoing call duration, even after the rom upgrade ! Is there a way of clearing this info ??
Can any one help ?
Thanks
fs
Click to expand...
Click to collapse
Hi,
Just remove sddaemon.lnk from windows/startup folder.
(when in doubt, just paste this file elsewhere)
greetings,
Wout

I am getting the same thing. None of these "fixes" has any effect whatever. I thought this was a thread full of knowledgeable persons. Why all the stab-in-the-dark answers? Doesn't anybody know what REALLY causes this trouble?

Leo Application Unlock

Hello, just received my HD2 ! But with trying to install some software, it mentions the certificates are not ok, so I cannot install. Is this the 'application lock' and how can I unlock it ?

MattRob said:
Hello, just received my HD2 ! But with trying to install some software, it mentions the certificates are not ok, so I cannot install. Is this the 'application lock' and how can I unlock it ?
Click to expand...
Click to collapse
Using a registry editor, set the following values:
Code:
[HKEY_LOCAL_MACHINE\Security\Policies\Policies]
"00001017"=dword:00000090
"00001005"=dword:00000028
"00001001"=dword:00000001
"0000101b"=dword:00000001
"0000101a"=dword:00000001
That should fix it... If the registry editor gives you an error, or you'd rather not use a registry editor, I can whip up a cab/program to do it.

Hm .... I tried that (with the old regeditSTG; but is not working very smooth) but still the same problem. I will try and install another regeditor, to see if that works ... Txs for quick follow up.

I tried it another time, but values seem to be correct now. Still have the application lock issue ... Would you mind making a cab, just to make sure ... ?

MattRob said:
I tried it another time, but values seem to be correct now. Still have the application lock issue ... Would you mind making a cab, just to make sure ... ?
Click to expand...
Click to collapse
Did you soft reset the device?

Yep, a few times already ....

MattRob said:
Yep, a few times already ....
Click to expand...
Click to collapse
Okay... I'll have a look at other things that could be set... What's the exact error it gives?

Unfortunately it is the Dutch version (that one arrived one week earlier here than the UK version), but after installing the software (which I used on my HD (with Dutty's Leo R7 and ALL earlier versions) and I need it to get my server ready for my work exchange server), it says (translated):
The file cannot be opened. It is not signed with a trusted certificate or one of the components cannot be found. U have to install it again or repair it if the problem persists.

MattRob said:
Unfortunately it is the Dutch version (that one arrived one week earlier here than the UK version), but after installing the software (which I used on my HD (with Dutty's Leo R7 and ALL earlier versions) and I need it to get my server ready for my work exchange server), it says (translated):
The file cannot be opened. It is not signed with a trusted certificate or one of the components cannot be found. U have to install it again or repair it if the problem persists.
Click to expand...
Click to collapse
I think that's an issue with the cab/software rather than the certificates... Out of interest, what application is it?

If that would be true, I REALLY have a problem. It is not a 'known' software, I guess. It has been prepared by my company and I have to install it first before I can use our Exchange Server (through Domain Enroll). It is call gprschange.exe
It worked on all former HD Roms and on the XPeria. I will try to set up Exchange server without it. Hopefully it will work .... Will let you know ...

It is not working now ... I cannot connect to Exchange server ... I assume it cannot have anything to do with the 'Dutch' version ? That would be strange, right ? But I cannot understand it worked on all the HD ROM versions, and here it is not working .... And I was so happy I got the HD2 today and now it is not working (for me at least) ...

i don't know if you already have solved the problem, but in some cases, when a cab refuses to install on my tp2, i open it with the wince cab manager on the desktop, remove the setup.dll and repack it again. It might not make any sense at all, but at least you can try it to rule it out.

May be something related to old .net 2?
or have you updated to 3.5 already?

hyellow said:
i don't know if you already have solved the problem, but in some cases, when a cab refuses to install on my tp2, i open it with the wince cab manager on the desktop, remove the setup.dll and repack it again. It might not make any sense at all, but at least you can try it to rule it out.
Click to expand...
Click to collapse
It was the setup.dll causing issues, it's fixed now!
Will move this to Leo Themes and Applications.

i have exactly the same problem with anumber of cabs that worked fine on my touch pro. seems a number of former reg edits are not being picked up as before. the keys i want to change for default folder locations don t work eiter...(see my post)...

oh, that is good...
thanks hyellow ...