yashsingh1/xdaforums huggingface dataset:
[Windows Mobile Development and Hacking General] TalynOne:
Works as advertised! I ran it for about an hour. No timeout disconnect occurred, and my device didn't idle into standby.

Observations:

* Still need to press "Connect" again when coming WiFi device is coming from a DHCP state.

* Screen toggle button had no effect on my Mogul (Maybe this will help?)

* Sometimes WMWiFiRouter would still focus to itself when trying to switch to "Internet Sharing" window

* Would be nice to change to spinning waitcursor when WMWiFiRouter is loading to indicate to the user something is happening when starting the application

* First time I closed the ICS window, after being connected for an hour, the WMWiFiRouter window didn't exit/close, but I wasn't able to recreate this behavior.
[Windows Mobile Development and Hacking General] xboss:
Instead of GPRS/EDGE/UMTS...

Is it possible to use the USB cable for connect to the internet?

So effectively turning the i600 into a Wifi Access point or Bluetooth PAN access Point.
[Windows Mobile Development and Hacking General] Chainfire:
Guess that still needs some tweaking then! :)

Ok, could you give me a rundown on how to reproduce this behaviour?

That is actually what I am using. However, it uses DPMS which is not actually what I want to use. It uses video card power management to turn of the screen (much like a monitor on the PC); what I want it to do is somehow trigger the normal 'screen off' that happens after X seconds (configured in your control panel), there doesn't seem to be a way to actually do that though :S If I could trigger that, any user operation would bring the screen back, instead of just the button.

You have probably pressed the screen toggle. It doesn't work for you, but when in the 'blank state', WMWifiRouter keeps putting itself in the foreground so it can catch the toggle click again, to turn the screen back on.

That would be nice indeed, but I have no idea to do it. More research :)

Let's call it a fluke then :)

Oh btw, for your MortScripts, you look for a window called "Internet Sharing". That only works in the English roms as the window is named differently in other languages. Try using "MSINTERNET_SHARING", which is the window class name, that should work on all languages, though I do not know if MortScript command takes class name as well as window name (the FindWindow API that I think is behind it does).
[Windows Mobile Development and Hacking General] Chainfire:
Probably, but that is a somewhat different hack. I think it's possible though, but I have no way at all to test it so I can't really help there.
[Windows Mobile Development and Hacking General] Chainfire:
WMWifiRouter v0.5

Just a small maintenance update. In short, the app has simple become more responsive / useable:

- App should be more responsive and load faster

- 'Loading' indicator is now used

- Screen Toggle is disabled, as with further testing it causes too many problems

for the rest, it's still just v0.4.

I really have to figure out a good way to do this "Screen Toggle", lots of searching in tech stuff, but none of it seems to work. My experience is WMWifiRouter doesn't let the phone go to standby, but the automatic backlight dim doesn't work (it should though, according to the technical documentation if the calls I use). Needs more research. The "hard" screen off method I used in v0.4 didn't even work for everybody, and has serious issues coming back 'alive'.

Furthermore I've put a very small webpage online, which is now the official url: http://www.jongma.org/WMWifiRouter/ with the appropriate donate button (better than using KaiserTweak's one, anyways ;))
[Windows Mobile Development and Hacking General] thierryb:
.4 works on the Flame

The ip adress of the pda was not 192.168.0.9 but .1

But the great news is : it works now painless !!!

I was able to surf on the net from my pc.
[Windows Mobile Development and Hacking General] Chainfire:
Congrats!

Oh that's right, the new hack-less v0.4 and v0.5 use .1 again.
[Windows Mobile Development and Hacking General] TalynOne:
Thread updated with new version info. Took me a while to update it, the forum kept complaining the post was too long, so I had to keep moving content down to the next post, :p.

I included info about WMWiFiRouter setting the IP to 192.168.0.1, and how to fix regular USB Internet Sharing if it breaks.
[Windows Mobile Development and Hacking General] TalynOne:
Set the WiFi device to DHCP mode, turn off WiFi, turn on WiFi, start WMWiFiRouter.

Ah, WMWiFiRouter didn't turn of the screen at all on my device. Every "screen off" tool I've used, has only reacted to me pressing the "power button" to turn the screen back on. But it's definitely not in standby mode since I've verified my WiFi stays up, in standby mode my WiFi signal connection goes away.

Yes, this is most likely what happened.

Cool, does I see that v0.5 might already implement this. If not, it looks fairly easy.

I'm good with that.

I'll look into it late tonight, right now I have to start a contract job....
[Windows Mobile Development and Hacking General] thierryb:
Chainfire

Why .5 is 4 time bigger than .4 ?
[Windows Mobile Development and Hacking General] Chainfire:
Because .5 is not UPX'd. In other words, .4 was still compressed even though it was an .EXE. Using the compressed .EXE is slower and more memory-intensive than using an uncompressed one, even if that is bigger on disk.
[Windows Mobile Development and Hacking General] jompao:
Wohoo!! We have liftoff V 0.5 is working nicely now, great work!
[Windows Mobile Development and Hacking General] joshkiddy:
so does the screen toggle button just do nothing now?
[Windows Mobile Development and Hacking General] Chainfire:
Yes. It is temporarily disabled until I can figure out what the problem with it is.
[Windows Mobile Development and Hacking General] joshkiddy:
thats good to hear cause i couldn't get my vario III back on after clicking that on v0.4

nice work
[Windows Mobile Development and Hacking General] dcd1182:
thanks to everyone involved for the efforts on this. just tried the app and it rocks.

just wanted to add that ad-hoc is not required, in fact i havent even tried it. i let wmwifirouter do its thing and turned on my wifi. it looks like wmwifirouter forces the wifi card to 192.168.0.0 net which I do not use here, so I had to assign static ip to my pc. however i was instantly connected via cellular data. my pc doesnt even have wireless, just ethernet to the ap where the mogul connects. you might note that in the documentation, as i would imagine its even easier for some people.

also i might suggest a version that occupies something other than 192.168.0.1 as this will conflict with a device on many peoples home nets. even for the ad-hoc solution, the ppc could sit on 192.168.0.254 for example, anything as long as the desktop uses that as gateway. a less-popular ip address choice might suit both an ad-hoc peer to peer solution, or a phone-as-router-wirelessly solution.

i had hoped to someday be able (given fast evdo) to walk in my house and provide a net connection via ppc in my pocket :) you have made that possible and working flawlessly. thanks

not time to drop my isp, but awesome concept.
[Windows Mobile Development and Hacking General] LoTekJunky:
to add to what DCD had to say... would it be possible to code the exe file to look for a file, like ip.txt, and inside that file would be an IP address to use? if no ip.txt file is found, it could default to 192.168.0.254. This way, we could build an OEM package, or modified cab file that would work on 100% of LAN configurations for supported devices. I personally use 192.168.1.0 /24, so this would be a fantastic option to build in.
[Windows Mobile Development and Hacking General] isaacfinnegan:
Just wanted to chime in on the "THIS ROCKS!" bandwagon. Well, because it does. I first tried out the registry hack when it first came out, and couldn't quite get it to work. But this thing is just user dumb simple! Will donate asap!
[Windows Mobile Development and Hacking General] TalynOne:
An Ad Hoc connection is required between the client and mobile device. The default behavior for the wireless manager on the mobile device is to scan and connect, first, to the first available infrastructure mode wireless access point, and if none are found, then to connect to an available/configured ad hoc connection. In many situations users will be in range of a infrastructure wireless signal, so your observation wouldn't apply in those situations.

The intshare.dll is statically linked to 192.168.0.1. So the solutions would be to use a hacked .dll, which has been found unreliable for some. Or additional registry hacking, that in testing also sometimes caused issues. The better solution, especially long term, if you ever wish to setup/connect to a VPN from your home is to change the subnet of your home LAN, if it's using a 192.168.0.0 network.

Statically setting the IP address of client (eg. laptop) shouldn't be necessary as "Internet Sharing" should be assigning the client (eg. laptop) an IP address via the DHCP server built into "Internet Sharing".
[Windows Mobile Development and Hacking General] Chainfire:
@jompao

I'm happy it finally works right for you!

@dcd1182

Interesting that Ad-Hoc is not required like that. I guess some investigating and experimentation is in order to find out when it does and when it doesn't work like that. I must admit I haven't even tried without the Ad-Hoc network.

One thing that is a possibility though, is that your AP sees the device, discovers it's IP address, and because it is the first IP address in the network address tries it as a gateway. As this is the usual gateway address, it is not uncommon for network to try that.

As for changing the address, I am not sure it is possible. It was with the hacked DLL's, but the IP seems to be hardcoded in there. It will require some testing as well. This is also the reason why we use .0.1 instead of .1.1 .

As for the ISP replacement... I must say I have even contemplated just dropping my hardwired home ISP and using a wireless solution like this, but even HSOPA with it's 40mbps has trouble beating it, and it isn't even out yet ;)

@LoTekJunky

See above, it would first require more testing to see if we can get it to work with different IP's at all, and then possibly if we can get it to work without Ad-Hoc AND different IP's. That would totally rock :D

@isaacfinnegan

Happy it works for you as well!

@TalynOne

I noticed I forget to tell you how my other way of the 10 minute timeout hack works (you asked). You remember "HostConnectTimeout" ? I had noticed it before you put it in the thread as well in the hex editor. However, when you mentioned I should look in detail at your mortscript to set USB as the device, I noticed "hey, there's an ICS key location I haven't seen before". So I tried adding a "HostConnectTimeout" key there and that actually worked! I had already tried HKLM\Comm\InternetSharing and HKLM\Comm\ConnectionSharing but these flunked. This location made the magic happen though!

BTW, you mentioned before about your data connection dropping 'killing' ICS. That doesn't seem to happen for me. If my UMTS connection drops, ICS reconnects it no questions asked. True, existing connections between PC and Internet going through the PPC timeout and have to be reestablished, but I do not need to reinitiate connection manually on my phone. It does it automatically (and keeps trying).
[Windows Mobile Development and Hacking General] dcd1182:
hey guys thanks for the quick responses.

talynone, i think you have me backwards, or im confused (likely). it most definitely is working via infrastructure mode. there are 4-5 infrastructure wlan's within range here (2 are mine) and the device picked up my primary ssid and connected as usual, with the exception of pulling a lease from my local dhcp server. i do not understand why these results would not be observed by users in areas of public infrastructure networks? really, with the wmwifirouter.exe application functioning, my wifi stack on the ppc seems to act as it always did (at a physical level.)

what i think you may be getting at is that the ICS application will only perform NAT for one peer. I hope not, but I'll test - my first test only used one pc on the LAN.

i did not realize dhcp was builtin to ICS on the ppc. thats awesome! i could simply kill my dhcp server and allow the ppc to hand out leases on the 192.168.0.0/24 net.

i had already planned to ( regretfully :) ) move to the 192.168.0.0/24 net if it was possible to move the ppc to 192.168.0.254 (or something). however, it would be just as easy for me to move my default router to 192.168.0.254.

thanks again guys for the help and the info and the awesome app. hopefully i can repay the favor sometime.

btw, my ppc6800 is flashed/hard reset/etc more times a day than youd beleive :) if you need more testing, i am game for anything.
[Windows Mobile Development and Hacking General] TalynOne:
Ah, I think I understand. What you're saying is that the mobile device can connect to an infrastructure AP and still perform as a NAT router. Yes, I don't see why not. The actual limitation is that the mobile device can't function as a infrastructure AP/Router by itself

Nope, look at the FAQ in the beginning of the thread. It works fine and has been tested with multiple clients at the same time.

Haven't had a chance to try em, but I've read many good things about your ROMs.
[Windows Mobile Development and Hacking General] TalynOne:
I feel like a caveman with my paltry 6mbits, :(.

Wow, I was wondering where the heck the value for that came from, nice creative thinking on your part!

I've had it happen to me way too many times for it to be a fluke. I think it may be in the differences between the way UMTS and EV-DO Rev 0 connections work.
[Windows Mobile Development and Hacking General] LoTekJunky:
Another quick question for you...

I was looking at the hacked.dll in a hex editor and found the 192.168.0.9 /24 designation at 0440 (for the titan). I'm not able to test it out right now, but could it be as simple as hex editing that word to get our own custom assigned ip address?
[Windows Mobile Development and Hacking General] dcd1182:
i think he was saying that it is but the dll modifications affect stability.
[Windows Mobile Development and Hacking General] TalynOne:
^^ for some devices people have been having trouble with the hacked .dlls. But I've had no trouble using the hacked .dll on m Titan/HTC Mogul.

This will only work if you use my method. But yes, it should work, it's defined in 3 locations in the file, so you must change all three locations.
[Windows Mobile Development and Hacking General] dcd1182:
you guys want me to cab this?

although for me its just as easy to copy an exe as a cab :)
[Windows Mobile Development and Hacking General] marctronixx:
great work guys.

so let me ask a dumb question...

all i have to do now is just run this .exe off the phone? there is nothing else to install correct? no files to unpack and move?

im using the mogul FYI...

also on the website, is v.5 the one currently there? if so, is there wnyway to , on the next update, label the program v.x? just so i can know im using the latest and greatest?
[Windows Mobile Development and Hacking General] TalynOne:
Make sure you have a WiFi connection setup, but yes, all that's needed is just that to run that one .exe.
[Windows Mobile Development and Hacking General] marctronixx:
thank you. yes i have all of that and i know to switch on WLAN. my has this app come a long way in just a weeks time! you guys are pretty freakin' cool..
[Windows Mobile Development and Hacking General] kingohearts2005:
Help with isp

i've done everything except when i get to the part about assigning the isp addresses i look in my network adapters and my adapter isn't there. I've downloaded the hacked .dll and everything but i don't see mine there. I'm using a Sprint Mogul. Please help
[Windows Mobile Development and Hacking General] bedoig:
With the new tool you don't have to worry about disabling DHCP and setting static IP addresses. All you do is set up an adhoc wifi connection:

Start-->Settings-->Connections-->Wi-Fi-->Add New

Name it whatever you want, just make sure to check "This is a device-to-device (ad-hoc) connection."

Then run Chainfire's program. It will automatically apply all the settings.
[Windows Mobile Development and Hacking General] kingohearts2005:
Well if this is the case then how do i get my psp to find the acces point. I click on wmwifi router and the ics status says that i'm connected but when i search for access point with my psp it says no access points found. oh and also if the ics status says connected but when i go back to my wifi screen with the program still running and it says connecting, am i connected or not?
[Windows Mobile Development and Hacking General] Chainfire:
I do not know if PSP can connect to Ad-Hoc, I've tried (only for a few mins) and couldn't connect the PSP either (it's not my PSP so I couldn't really work with it)
[Windows Mobile Development and Hacking General] marctronixx:
did you setup an ad hoc connection on the psp?

if so, do you have any encryption set up on the psp and your wifi unit? if so, just set it up without the security to make things easier. also, make sure the psp and the wifi unit are set to OPEN and not shared.. the psp does not like shared connections.
[Windows Mobile Development and Hacking General] marctronixx:
didnt see your post chain, but the psp can do adhoc. im going to pull one of mine out and try it now...........
[Windows Mobile Development and Hacking General] marctronixx:
just realized that adhoc connection on the psp is for other psp's only.
[Windows Mobile Development and Hacking General] Menneisyys:
cool, I really need this so that I can access the net from my Nokia N95 through my other SIM card with EDGE speeds (as opposed to the GPRS-only speed at home with another operator).

Given the high speed of development and frequency of updates, it seems I end up having to post an update note every day :) (see my latest WM News)
[Windows Mobile Development and Hacking General] TalynOne:
I don't have a PSP, so I can't try it, but these sites may help:

http://au.playstation.com/support/psp/faqs/psp_FAQ_ng_adhoc.jhtml

http://au.playstation.com/support/psp/wizards/psp_ng_adhoc_wizard_1.jhtml

http://www.sharewareguide.net/article/Tip/troubleshooting---wireless-ad-hoc-mode.html
[Windows Mobile Development and Hacking General] marctronixx:
you wont be able to use the ad hoc setting on the psp for this hack. it wont work.
[Windows Mobile Development and Hacking General] fluxist:
In order to use an adapter string of arbitrary length, I adjusted the pointer in the dll that references the adapter string (in my case, BTPAN1, since I like to preserve USB functionality). I added the new string at some free space at the end of the section and re-adjusted the existent pointer to reference that location. If you take a look at my dll there is an added string (TIACXWLN1 or something) at around 0x0003EF0.

fluxist
[Windows Mobile Development and Hacking General] fluxist:
Anyone want to test out the new Internet Sharing app I posted here.

Ad-hoc connection needs to be set manually. Only difference in functionality I can see with the Chainfire macro is the WINS server needs to be set manually (and this release still turns on BT). But my app has a somewhat different purpose, as it is meant as a replacement for the MS version of Internet Sharing. It keeps USB functionality intact (I personally use USB sharing all the time; I never use BT sharing.) Please correct me if I'm wrong about WMWifiRouter functionality. I've been having trouble staying up to date on a million different WM developments. Gotta love xda-developers ;)

FYI, in my instructions I advise setting IP address to 192.168.1.1 in order to avoid conflicts with Windows Internet Connection Sharing (on the PC). It uses a hard-coded IP subnet of 192.168.0.x just as the default WM6 IS app.

fluxist
[Windows Mobile Development and Hacking General] Chainfire:
I can't take a look at it right now, but I do have some comments ready for ya:

- WMWifiRouter no longer requires _ANY_ hacked files (it just uses your installed IS and should work for any device with a single exe)

- IP changing and using BT instead of USB is being investigated. I don't know if I can pull it off to get the IP changes without using any hacked files, but BT instead of USB I'm 99% sure will not be a lot of trouble

- WINS server is not set at all anymore with WMWifiRouter

Interesting how you modded the DLL though, I thought something like that should be possible :)

Though I do think your app being a replacement would go to far, as it actually limits your options. If you replace the original one with yours you actually lose functionality, my 'add on' only adds functionality.

Nice work, in any case.
[Windows Mobile Development and Hacking General] fluxist:
I suppose it's a matter of personal opinion, but I'm always more inclined to run as few applications as possible on my phone. I think (non-destructively) modifying the current functionality to add new functionality is a more elegant solution. You're right that I removed functionality by removing the BT PAN option, but with the addition of WiFi, the net loss is zero :) Anyway I hope to keep the BT PAN option (plus USB and WiFi) in a later release (though I don't know if I'll get around to it, since I'm losing steam on this project).

Question: I've read this thread but I'm unclear on what are the latest findings on the 10-minute timeout problem/workaround. Some people mention setting an arbitrary WINS server IP, another mentions somehow modifying the adapter string in the dll to fix it (?). What did I miss?

fluxist
[Windows Mobile Development and Hacking General] TalynOne:
There's NO reason to use BT instead of USB, it just adds problems.
[Windows Mobile Development and Hacking General] TalynOne:
There's two 10-minute workarounds, that have been discussed/documented

Method 1 (My method)

In my hacked .dll I replaced EVERY reference to the USB device (RNDISFN1), to the WiFi device in question (TNETW12511 for the Kaiser/Mogul). So if you just perform a registry change with the original version of the intshare.dll, the "Status" messages the "Internet Sharing" app looks for/displays are related to the USB device. In my hacked version, the "Status" messages the app looks for/displays are related to the actual WiFi device. So changing WiFi IP address properties, for the 10 minute workaround, while running the non hacked version will have no effect, because the non hacked .dll version is monitoring the USB device, not the WiFi device.

Changing the WINS address is just a manual way of forcing the WiFi device to update its status so "Internet Sharing" detects it and changes the "Status" to "Connected". Once the status is "Connected" no timeout occurs. Any change in any IP property would have the same effect, all that really necessary is a rebinding/refresh of the IP stack. The WINS change is just one manual way of forcing this refresh.

Method 2 (discovered by Chainfire, used in latest version of WMWifiRouter):

From Chainfire:
[Windows Mobile Development and Hacking General] fluxist:
Nevermind.
[Windows Mobile Development and Hacking General] TalynOne:
Yes, I was/am aware of this, and I note it in my tutorial. It worked as intended, so I released and documented it because I thought it might be of use to others, as it was very useful to me. That's the beauty of a development community, we can all learn and benefit from each others work and findings.
[Windows Mobile Development and Hacking General] fluxist:
Yeah, I read the attribution in the FAQ approx eight seconds after posting. Which is why I took it down approx 4 secs later (you're pretty quick).

My bad.

fluxist