Related
Has anybody found a way to toggle wifi off/on with one click, instead of going through comm manager? Vijay' volubilis responds that "no compatible wifi found" when executed on my prophet.
Anyone? Or Vijay himself maybe shedding some light on this issue?
VJVolubilis's wifi feature has only been tested on the Universal, because that's the hardware I have. The Wizard wifi control is not perfect, because I don't have one.
I'm slowly thinking about how to try to implement a more generic wifi control, but unfortunately this is not really an OS feature, it's OEM specific, so it's something I'm still investigating. I haven't thought about the Prophet before. Let me check it out...
V
If you need any info (registry or what-not), let me know.
Thanks for looking into this.
vjvolubilis can be used for turning on/off wifi on prophet..
but there is one additional step to make it work..
ie after every soft reset, u need to use comm manager to turn on/off wifi 1 time. after which , u can use vjvolubilis to control it..
this issue is the same when u are using phone alarm with skins that can allow one touch wifi on/off... ie comm manager must activate it for at least once before it will respond to oneclick controls from either vjvolubilis or phonealarm..
I own a dopod818 [ singapore's version of prophet ]
Hey, I didn't know it (kind of) works on the Prophet... so it uses the same architecture as the Wizard I guess.
I'll try to think about Wifi control a little more as soon as I get a bit of time.
V
Not quite. Yes, true, I realized now that once Comm manager is employed once, Vijay's app CAN turn wifi on. But it does not turn it off, if you press wifi toggle again...
At least on my Qtek S200 with latest Dopod rom.
solved
Found a solution for this issue
Just put a shortcut to \Windows\WiFiInit.exe into your startup folder and enjoy the quickly activating wi-fi! After a soft reset this vill activate wlan for a second (green led will flash once and a wi-fi icon will appear on a place of network icon — don't worry).
But, as krale said, there is another little bug with VjVolubilis: you have to create both -wifion and -wifioff shortcuts to control wifi on Prophet because -wifitoggle shortcut does not turn off the wi-fi, it just can activate it.
When launched with -status parameter, it says that Wisard wi-fi is activated.
I have a strange problem with my universal. I want to know if it is hardware or software related.
Basically what happens is that sometimes after a softreset the wifi doesnt load (driver issue perhaps ?). Even when removing the battery doesnt load the wifi. The sometimes it does load and when i go into the comm manager and switch it on the wifi on it only starts after the 3rd time switching it on.
I have had it with all the unofficial roms available. Any solutions or work around to get this to work like it is suppose to or is it time to return and replace the hardware ?
Thanks beforehand
This is basically what i experience:
How to load PCMCIA driver after device reset?
I'm testing PXA255 device with integrated Texas Instruments ACX100
WiFI card on PCMCIA bus and I'm facing with BIG problem.
After reseting the device the driver for the card (tiacxwln.dll is not
loaded at the boot time), ok...setting by OEM.
There is an application installed in the device by which wifi card can be
turned ON/OFF.
Once I change the power state of the wifi device by built-in application
from "off -> on -> off" after I can use power management functions to set on
and off the card because then the driver is loaded.
I've tried everything to load the driver but I didn't succeded.
1. I've tried
ActivateDevice(L"Drivers\\PCMCIA\\Texas_Instruments-ACX100-EE1D", 0); but no
sucess.
2. I've also tried with ActivateDeviceEx also without sucess. (As I can see,
the driver has valid needed Registry entries for ActivateDeviceEx):
[HKEY_LOCAL_MACHINE\Drivers\PCMCIA\Texas_Instruments-ACX100-EE1D]
"Prefix"="NDS"
"Miniport"="TIACXWLN"
"Dll"="NDIS.DLL"
[HKEY_LOCAL_MACHINE\Comm\TIACXWLN]
"DisplayName"="LOOX WLAN Wireless Adapter"
"Group"="NDIS"
"ImagePath"="tiacxwln.dll"
3. I simply cannot load the driver with Device Manager. Just for tesing I've
tried to load driver "tiacxwln.dll" mannualy with LoadLibrary function and
I've noticed that loading tiacxwln.dll initiated loading of sequence of
other drivers automatically (ndis.dll, bus... etc). But I don't have any
use of that because after that I have to release allocated HANDLEs
to the system. So HOW I can tell to Device Manager to do that thing for me.
What I'm doing wrong!?
4. I don't want to use this registry key to achive the goal:
HKLM\comm\tiacxwln1\parms\ResetOnResume
P.S. After sucessfull turn on with built-in application I notice that new
entry in registry is created:
[HKEY_LOCAL_MACHINE\Drivers\Active\31]
"Hnd"=dword:00544880
"Name"="NDS1:"
"Key"="Drivers\\PCMCIA\\Texas_Instruments-ACX100-EE1D"
"PnpId"="Texas_Instruments-ACX100-EE1D"
"RegenumParms"=hex(7):\
53,63,6b,74,00,50,6e,70,49,64,00,52,65,67,65,6e,75,6d,50,61,72,6d,73,00,00,\
00,00,00,00,00,00
"InterfaceType"=dword:00000008
P.P.S. I'm changing the device's power state to full power on with this pair
of functions and it is working ok but with drivers loaded:
DevicePowerNotify("{98C5250D-C29A-4985-AE5F-AFE5367E5006}\\TIACXWLN1", D0,
1);
SetDevicePower("{98C5250D-C29A-4985-AE5F-AFE5367E5006}\\TIACXWLN1", 1, D0);
Got it from
http://www.tutorialsall.com/PLATBUILDER/storage-device/
Any ideas on how to get this fixed ?
Any suggestions on this ? my warranty is expiring soon and would like to know if i need to take it back to replace if it is hardware related. Pleaseany comment might help. Currently on helmi wm6 v1.1. Have basically tried all available roms to see if it is rom related.
Thanks for any help !!!
My PDA is O2 Atom Life. In my office, I must use LEAP to authenticate to the access points. As everybody knows that O2 doesn't support LEAP, so I have used Odyssey Access Client to do that.
After installation, I created a new profile in OAC, power on the WiFi, wait few seconds, use IE to navigate on the internet and everything works fine. When I completed to play on the internet, I disable the OAC and power off the WiFi, there is no any error message appeared. After that, I connect and disconnect the WiFi for several times. Then I soft-reset my O2, I found that the phone calling service becomes unavailable. I have tried to disable/enable OAC, power on/off WiFi and power on/off phone service, but no action can wake up the phone calling service again. So I uninstalled OAC, then reboot. The phone service can work again and the original WiFi service also works fine.
Does anybody know the reason for the error occured? Is it that my usage incorrect? What is the order to enable/disable OAC and power on/off the WiFi?
I found a method that can recovery the phone service without uninstall OAC. The method is just run the "OdyIMCEUninstall.exe" in the OAC folder, and then reboot my device. I have used some registry viewing tool to compare the changes made by that program, the difference is in the NDIS device (that program may remove a layer from the networking stack).
After reboot, I run the "OdyIMCEInstall.exe" in the OAC folder and run OAC client program to enable Odyssey and dim the "Connect to" check box. Then power on the WiFi, everything works fine again. Both phone service and wireless service works properly!!
Anyone can tell me why OAC can affect the phone service? NDIS device is also related to phone service?
I think I get something similar on a Polaris I am testing. No simcard so I don't know about the phone, but if I install Odyssey it works, then after any reboot I have to reinstall Odyssey or I have no wifi access. Odyssey cannot even see any networks.
Is this the same? Any idea to try out appreciated.
As per what t2k269 said - I misread this as "uninstall" but running the install file fixes this. Good spot and thanks.
If this is posted to the wrong place please forgive, I am working on an NDIS intermediate miniport driver on WM5/6. Our driver works on all CE platforms ( and all other windows platforms ) and installs and works on WM5 and 6 *EXCEPT* form some strange behavior around WLAN connections.
When we are installed w/ a WLAN, when the machine powers up, or soft boots, or suspend/resumes, the default SSID attempts to connect. Instead of auto-connecting, the 'tower icon' never connects, instead eventually a second 'tower icon' comes up and I get two 'tower' icons connecting. Neither ever connect.
If I manually go into 'network cards' and press 'connect', the SSID will connect and authenticate, and the network works, and the IM works and sees all traffic.
Micro$hit refuses to support anything, and HTC is no better.
If you guys are smart enough the reverse engineer the entire OS, does anyone have any idea what is going on here? Any ideas would be great.
What about an alternative comm manager that would work around this? I wrote a wzc application to try and duplicate the behavior when I manually press connect in comm manager, but it just seems to replicate the 'auto connect' behavior w/ two 'tower icons'
Does anyone know what is happening?
Does anyone have an application that can work around this?
Can anyone write an application for $$$$ to work around this?
Help me please
-Seth
How works Your application which duplicate comm manager behavior?
Did You try functions in ossvcs.dll?
I did not write my own comm manager, this is the standard comm manager, I am relying on the default WM6 one.
I wrote an app using the WZC calls based on WZCTOOL in the CE6 sdk, and when I put the key, and enc type in it will successfully connect to the access point. With my IM installed, however, this WZC app will re-produce the problem described before exactly. Somehow the default windows comm manager can still successfully connect manually... how does it do this, what calls does it use, I need to know how. Can anyone write this? The code in wzctool will not do it ( I don't think, possibly I have bone stuck in my head ).
I don't know ossvcs, please elaborate on how/what functions I might be interested in.
As an aside, does anyone want to try our shim on one of your custom kernels. I am necessarily running on a standard WM6 kernel, if someone would test and see if this problem exists on custom kernels that would be swell. I cannot modify the kernel on this one and only device I have.
Here is the good description for functions in osvcss.dll
http://www.teksoftco.com/articles/article 007/radiodevices.htm
HTH
I tried out the ossvcs sample application, and it caused the same behavior I see with the WZC stuff or when trying to 'auto connect' after a reset. That is, the access point never connects. Manually I can still connect by going into comm mgr, editing the access point, pressing cancel, then connect, and instant connection. What api call is this app using at that point?
It's verry strange behavior.
One tip from other side - did You try call SetDevicePower fo Wifi Driver and intermediate driver?
no special handling
I will look into SetDevicePoPower, but I think NDIS should be handling power events... Any further info on SetDevicePoPower or anything else would be great.
Oh yeah, in case I didn't say so before, you guys *ROCK*! Keep up the good work, and if I ever solve this problem I will be sure to 'let on'.
Does anyone out there in the wide world have an Ndis Intermeidate Miniport driver akin to PASSTHRU working for 802.11xxx on a TyTn ( WM5 or 6 )?
Yes NDIS handling power events, but by using api setdevicepower You can explicitly on/off wifi connection
Please try to write small apllication which turn wifi on and off.
CEDEVICE_POWER_STATECEDEVICE_POWER_STATE devState = D4; //Full power - constant D0 represents NO power state (OFF)
DevicePowerNotify("<WifiAdapeterName> (qualified - example {8DD679CE-8AB4-43c8-A14A-EA4963FAA715}\xxx1:", devState, POWER_NAME);
SetDevicePower("<WifiAdapeterName> (qualified - example {8DD679CE-8AB4-43c8-A14A-EA4963FAA715}\xxx1:", POWER_NAME, devState);
But Maybe You have still problem if wifi driver is not loaded until comm mgr button is pressed...
.
WiFiFoFum
I just tried the WiFiFoFum application that allows one to power on and off the devices. Is this using the same API? WiFiFoFum did not work, I tried powering on and off my device and the real device in different orders, and it does not work.
I will try you API now...
not smart enough
I don't know enough to understand your example. Where do I get the correct GUIDs from? I assume the xxx1, is the device name instantiation.
What about 'devName' and POWER_NAME. Sorry, bone still stuck in head, ughh.
Guid is typically found on this place
\\\registry\HKLM\System\CurrentControlSet\Control\Power\State\Suspend\
Value is
{98C5250D-C29A-4985-AE5F-AFE5367E5006}\
Device name can be found on registry key HKLM/COMM.
Also device name is displayed in wififoforum.
POWER_NAME is constant - see MSDN.
My D2 will automatically disconnect the wifi connection when it goes in standby. My old cruise would always keep the connection alive, so that it would be available immediately after turning it on. Is there a fix for this?
A google search reveals!!
http://forum.xda-developers.com/archive/index.php/t-368241.html
Edit: although that worked on my XDA Orbit 2 (Touch cruise / polaris) it dont seem to work on my Diamond 2
I found this key in the registry:
HKLM\Comm\TNETW12511\Parms\HTCKeepWifiOnWhenUnattended
and changed it from 0 to 1, but that didn't work. After a restart the value was automatically changed back to 0.
Looking around on the HD forum it seems that HD has the same behaviour. People changed that using a program called HD Tweak. I guess we need D2 Tweak...
i would also like to see a solution for this
I have experienced this problem also. If you have push internet scheduled and the phone is on standby, it retrieves the data via data connection/3G as opposed to your WiFi.
Additionally, if you take your phone out of standby, it takes a few seconds for the phone to re-establish the WiFi connection. If you are too quick to access the internet or update weather - again it will start to do this through the data connection.
Does anyone know how to resolve this?
did you try Advanced Configuration Tool? You can enable/disable data connections, set them to always on and enable WiFi on standby.
tomkarb said:
did you try Advanced Configuration Tool? You can enable/disable data connections, set them to always on and enable WiFi on standby.
Click to expand...
Click to collapse
Does it exist for D2 too already?
Yeah got it and it works on D2, the enable WiFi option is there
You could also go to Settings -> More -> Connections -> Wi-Fi -> Wireless networks -> Menu -> Advanced, there you can change how long the Wi-Fi radio should be on if not connected to a wireless network.
Unfortunately, www.touchxperience.com is down, so I can't download it now.
helinus said:
You could also go to Settings -> More -> Connections -> Wi-Fi -> Wireless networks -> Menu -> Advanced, there you can change how long the Wi-Fi radio should be on if not connected to a wireless network.
Click to expand...
Click to collapse
Thanks for the tip. This doesn't solve my problem, but it's good to know.
I found a 3.3 cab elsewhere. What option exactly did you change to keep wifi on on standby? The only logical one I found is Network >Turn off wi-fi if no activity. I changed that from yes to no, but that didn't help...
I know how to do it but it requires some code to accomplish - I actually tested this yesterday on my TD2 (the advanced config trick does not work with TD2). Unfortunately I do not have the TD2 with me right now ... Perhaps I'll muck with it a bit later anyways, else you'll have to wait 'til I have the TD2 in hand again Monday or Tuesday.
It takes a ****load of power to do this though, and I'm not sure if it works in true suspend... it works for unattended mode though.
Well, I found the option in advanced config 3.3, hidden under "More options". But indeed it doesn't work. Wifi still disconnects on standby and starts reconnecting after standby. If you have a solution Chainfire, I'd be happy!
Tomkarb, can you confirm that the Advanced Config trick really works for you?
Isn't there anyone that has a solution? The Schapps advanced config thing just doesn't work
The solution is in here:
http://forum.xda-developers.com/showthread.php?t=524490
Thanks! That works indeed!
Code:
[HKEY_LOCAL_MACHINE\Comm\TNETW12511\Parms]
"HTCKeepWifiOnWhenUnattended"=dword:00000001
I never found that out, because I always soft reset immediately afterwards, thinking that was necessairy for the change to become effective. The soft reset wiped the change away though.
I've made a cab that changes the registry value to 1. It also copies the cab to the installationdir and adds a shortcut to it in the start menu. So you just have to run it from the start menu after each soft reset/restart (if you need wifi on standby). It only works when you execute it when wifi is off. Turn it on after installation.
There's a great freeware that i use called WkTask, which is a launcher, among other things, and it has the option of turning off the screen, but not putting the phone into standby. Disable the automatic power off and turn off the screen, this should solve your problem. However, i'm pretty sure your battery will drain a whole lot faster with the device never entering standby and the wifi on.
For added functionality, create a shortcut in the windows directory called 'long_power.lnk', and point it at the same file that WkTask uses (you'll see the path when you add it to the launcher, its a 'command call' btw). Then you can press and hold the power button to turn the screen off instead of powering off the phone (which is something i never do, does anyone?)
Hope that helps.
Thanks for the tip. I don't use wifi very often, only sometimes to remote control my pc. So most of the times I want it to go in standby and save as much power as possible with wifi off.
BTW, another solution for some of you may be to use a different ROM. I'm using Topaz Essentials 1.6 ROM (TESS1.6) from chef Aman now, and this ROM doesn't have the wifi turning off problem.
deechte said:
Thanks! That works indeed!
Code:
[HKEY_LOCAL_MACHINE\Comm\TNETW12511\Parms]
"HTCKeepWifiOnWhenUnattended"=dword:00000001
I never found that out, because I always soft reset immediately afterwards, thinking that was necessairy for the change to become effective. The soft reset wiped the change away though.
I've made a cab that changes the registry value to 1. It also copies the cab to the installationdir and adds a shortcut to it in the start menu. So you just have to run it from the start menu after each soft reset/restart (if you need wifi on standby). It only works when you execute it when wifi is off. Turn it on after installation.
Click to expand...
Click to collapse
Does not work on my HD2