yashsingh1/xdaforums huggingface dataset:
[Windows Mobile Development and Hacking General] ryancurnow:
Omnia HELP

I have conntected my Samsung Omnia 02 UK to my MAC 10.4 via wifi but it is running at only 90KB and keeps droping. Can any please help it is so slow and painful.

Thanks Ryan
[Windows Mobile Development and Hacking General] firecat:
What's the device's signal speed on it's own?
[Windows Mobile Development and Hacking General] ssuurrss:
does anyone have a link to the trial version?
[Windows Mobile Development and Hacking General] dayden:
ICS Internet Connection Client Issue

Howdy!

Been around for a while but never post... I can usually find any info I want from previous posts.

I have been searching and browsing for a while and maybe I'm blind or slow but... Still can't seem to get internet from the connection.

I am using a HTC TouchPro, with unlimited usage, the attached files with the proper hack. I'm able to connect to the "peer-to-peer" network, asigns an IP address... Just can't get the net to load on the laptop... I must be missing a step somewhere.

I appologize in advice incase this topic has already been adressed!!

Many thanks!!!
[Windows Mobile Development and Hacking General] 2175202304:
Can someone help me het around the boost app and get back on. Android 8.1 i believ
[Windows Mobile Development and Hacking General] fluxist:
No SSID.

Ad-hoc wireless does not use SSID. It uses BSSID. It would be non-trivial to change the WiFi driver to function as an Access Point in Infrastructure mode versus a peer in Ad-hoc mode. The functionality just isn't there.

fluxist
[Windows Mobile Development and Hacking General] TalynOne:
Create a subfolder named "CheetahSDN1" under the folder you have WMWifiRouter located, and place the attached "intshare.dll" in that folder. Let me know if it works.
[Windows Mobile Development and Hacking General] TalynOne:
Ah, just a correction in terminology then, have the WMWifiRouter connect to the specified BSSID. Ad-hoc mode is fine, since it has been verified to work with multiple clients. I don't think we're attempting to get it to work in Infrastructure mode.
[Windows Mobile Development and Hacking General] thierryb:
Same result.

WifiRouter stopped after witing

Starting ICS

Waiting for connection.

But ICS is not started by wifirouteur

if I start ICS before, but not connect. Then start WifiRouteur, Wifi Roufeur do not exit and wait I connect with ics. But when I connect, the device freese. It was not the case before I put the file in the CheetahSDN1 directory in WifiRoufeur directory.
[Windows Mobile Development and Hacking General] TalynOne:
Try running it with the ".dll" in the WifiRouter folder, but not starting "Wifirouter" at all, but instead running "intshrui.exe" from that folder directly, and pressing "Connect". If that doesn't work my want to try fluxist method (try the non hacked .dll method):

http://xdaforums.com/showthread.php?t=332360

The problem is that your WiFi identifier is longer than the longest previously tested string, and it may be causing problems.
[Windows Mobile Development and Hacking General] TalynOne:
Hi chainfire,

In response to thierryb's issues, to make a more universal tool....

You may want to have two options (maybe specified by config file?). One that enables/disable the Mortscript auto reconnect behavior. And another that activates an alternate method that does the reg hacks, runs/monitors the original .dll/.exe "Internet Sharing" app, and does not perform the 10 minute workaround (pretty close to the first version of your app). Also if the WiFi identifier string is too long, or unretrievable using the primary hacked method, display a message to the user that should try the alternate method.

Edit:

Maybe have a config switch that similiar to:

ConnectMethod (0, 1 or Auto)

0 uses the hacked .dll with 10 minute workaround.

1 uses original version, with regedits, but no 10 minute workaround.

Auto uses method "0" when WiFi identifier string is "10" characters or fewer, and uses method "1" when there are more than "10" characters.
[Windows Mobile Development and Hacking General] thierryb:
Fluxist + Xiou tutorial works.

I am able to connect to internet from my pc, to an adhoc wifi connection with my flame, that is connected to my operator.

Great !
[Windows Mobile Development and Hacking General] jompao:
Well I have TyTN with WM6. When connected ipconfig says (translated from swedish):

Ethernet-card wireless networkconnection:

Connection specific DNS-suffix.:

Autoconfigured IP-adress...: 169.254.192.39

Netmask..........................: 255.255.0.0

Standard-gateway.............:
[Windows Mobile Development and Hacking General] rod422:
the wifi adapter of my O2 Atom LIFE is CF8385PN1. could you build another dll for this? I'll very appreciate it
[Windows Mobile Development and Hacking General] Chainfire:
I had been thinking about something similar, but I'm afraid my bag of tricks isn't empty yet! I have an idea that might work and make the hack 'instant-universal'. Needs some testing though, I'll keep you posted.

Hmm that looks like your computer is not receiving an IP address through DHCP at all, which it should. Are you sure you have your computer's TCP/IP settings for wireless set up to dynamic/DHCP ?
[Windows Mobile Development and Hacking General] Chainfire:
I finally fired up my hex editor to see at what you did, and you mucked up with this one. There's a #0 char too much between N and 1. Further more looking at the format, I guess USB Interface + BT Interface + IP Address + Network Mask is in single multistring definition format, leading me to believe we could reach more characters for the USB (WLAN) Interface name by shortening the BT Interface name. We must keep that at one character length minimum though, else the list will get only 3 entries instead of 4, likely wreaking havoc all over the place. 15 characters is ultimate max length for the WiFi interface, as I see it.

So essentially we could make the list definition (in unicode):

- WiFi Interface (max length = 15)

- (16 - Length(WiFi)) * X

- 192.168.0.9

- 255.255.255.0

Could you up me the original intshare.dll so I can confirm this and use it for the 'automated' hacks? (I can't get it out of my foolish ROM! - yap yap call me n00b ;))

I've also tried dissassembling the DLL, adjusting the reserved size and reassembling it, but so far no luck on that (not something I do everyday ;)). Also, the trick I tried to do to get any interface name working didn't work out either, I can't get it to work in combo with the 10-minute hack and it doesn't connect half the time, so that's out as well. But 15 chars "should be enough for everybody" :)

Probably in a couple of more hours I'll have a new version of WMWifiRouter that won't need it, if you can wait :)
[Windows Mobile Development and Hacking General] jompao:
Wireless settings attatched
[Windows Mobile Development and Hacking General] Chainfire:
Those settings are correct. Still somehow your PC is not getting a network address from your phone. I'd almost say your PC still has DHCP disabled somehow, but that is obviously not the case, or else you could not connect through the USB cable either. I have noticed these settings you saw in 'ipconfig' are the same settings I get when an interface is not bound correctly on the phone, but if that we're the case, you wouldn't see the 'Connected' status in ICS. What a weird situation! Please try it again with WMWifiRouter v0.3 that I will upload in approximately half an hour.
[Windows Mobile Development and Hacking General] Chainfire:
WMWifiRouter v0.3

Alright, new version out!

Changelog

Compared to v0.2 the following things have changed:

- 'intshare.dll' is now hacked 'on the fly'. All WLAN hardware with a Device ID string of up to 15 characters should now be supported

- Redundant WLAN power cycling removed

- The phone's WLAN IP address is set to 192.168.0.9 instead of 192.168.0.1, hopefully preventing IP address conflicts as seen by some users

Upgrading

If you have an earlier version of WMWifiRouter on your device,

completely remove it

and follow the installation instructions below

Installation

- Download the new package here.

- Unpack the zip file on your PC somewhere

- Create a folder on your device somewhere (For example: "\Storage Card\WMWifiRouter") and copy all the files from the zip to that new folder

- Create an Ad-Hoc WiFi network as per TalynOne's instructions in the opening post of this thread (skip if you already did this, obviously)

Usage

- Run WMWifiRouter.EXE

- ICS will pop up, select USB and click connect

- Do NOT exit WMWifiRouter, exit ICS when you are 'done', and WMWifiRouter will exit automatically (after some cleaning up is done)

- Do NOT run ICS manually

Note for users of phone's that have a hardware WLAN switch:

- Put the WLAN switch in the ON position before starting WMWifiRouter

----

TalynOne, FYI, I've found 'issues' with a few other of your hacked DLL's as well.

----

I would like to ask specifically jompao, rod422 and thierryb to see if this version works for you!
[Windows Mobile Development and Hacking General] TalynOne:
Hi Chainfire, awesome will test new version soon.

I put in three hex "0"'s between the WiFi ID and "BTPAN1", because when I put in any fewer and checked the string in the registry, the private interface seemed corrupt/mucked up. So I thought I had to have a minimum of three hex "0"'s between he IDs.

I also thought the "BTPAN1" could be moved over more, but thierryb results were discouraging.

If you want to see fluxist's dll, which are quite a bit different from the original "intshare.dll", visit his thread, they're attached in the first post.

I'm curious what other problems did you find in the .dlls?

I've attached an original unhacked "intshare.dll" here from the latest HTC Mogul ROM (2.16).

Edit: Wow, after looking at the most recent .dll I modified again, I see where I screwed up, the damn wordwrap in my hex editor threw me off, my bad. This is the danger of doing any type of precision work on 2 hours of sleep... This is the exact thing I was worried about, that's why I rechecked the file 4-5 times before sending it off. But it looks like I missed it every time because of the location of the wordwrap, :(.
[Windows Mobile Development and Hacking General] Chainfire:
This is correct. We are talking zero-terminated unicode strings here (most likely UTF-16). All characters are two bytes, as we're using normal ASCII characters here, it's just the normal character followed by #0. The terminator is two times #0. The 1st of your three #0's is actually still part of the string, and the two following are the terminator. The program will stop reading the string there.

I think it can still be moved over more and this is what I did with the 'auto-hack'. The problem for thierryb was just the #0 in the wrong location (as I stated before, I think the limit is 15 characters)

I'll probably take a look at those as well :)

I'm not 100% sure they are incorrect, but I'm seeing 'stray' #0's here and there. It does seem like not all DLL's are hacked from the same original version, and it doesn't seem like that 'original' DLL is the DLL you uploaded at all :)

It happens :D
[Windows Mobile Development and Hacking General] TalynOne:
I didn't use the same .dll for every WiFi identifier. I based each one on the corresponding .dll from Fluxist's thread to be on the safe side. Especially since I had to move over BTPAN1 for the Mogul/Kaiser, but not for other identifiers, so to be on the safe side I based them on their counterparts from that thread.

I will probably double check my .dlls in about an hour or so, and see if I can fix em, but they're probably not necessary now that your version is out. Still I guess they couldn't hurt for debugging purposes.

I'm having a hard time finding time to actually test your new version, it seems I'm spending the time updating content here, and on another message board (for general Mogul related questions/discussion). Will test soon...
[Windows Mobile Development and Hacking General] Chainfire:
Well that explains some things. I hope there aren't too many inconsistencies between the DLL's that this one that is hacked on-the-fly will not work on other devices.

Could indeed be useful, if only I had writting down which ones they were!

Take your time, there's no rush. Interest in this is only mediocre anyways ;)
[Windows Mobile Development and Hacking General] thierryb:
Result with version 0.3 :

I need to start ICS before WifiRouter. If I do not do that, WifiRouter stops itself.

I need to start Wifi before WifiRouter. If I do not do that, WifiRouter does not find my device.

So if I start ICS and Wifi, then start WifiRouteur, I am able to connect with ICS, that starts Wifi.

When I try to connect to my pda from my PC, I get the connection but my PC do not receive an IP address.
[Windows Mobile Development and Hacking General] TalynOne:
I hope that's sarcasm. For a lot of people, including me, this is one of those holy grail features. In fact one of the main reasons I'm not getting the HTC Touch is because it has no WiFi and it would prevent me from, among other things, using your app. As more people find about how easy it is to do with your application, you'll see much more response. The only reason I didn't jump on this version in half a second is because your previous version already worked so well for me, :).

---------

Observations on version v0.3

Works great, the on the fly detection/patching seemed to work as advertised on my Mogul!

I noticed a bug quirk (which I noticed in v0.2). If the Ad Hoc WiFi connection starts off DHCP mode before running WMWifiRouter for the first time, the first connection attempt after pressing the "Connect" button fails. I have to press the "Connect" button again for it to connect properly, this problem doesn't occur on subsequent connection attempts, since at this point a static IP has been set on the WiFi adapter.

The WiFi turns off on exit of Internet Sharing/WMWifiRouter, is this necessary? Maybe make it an option?

I don't know if you ever examined my new MortScripts, but one of the things I do in the start script, is this:

Internet Sharing (both hacked/non hacked version) check the registry string value of "LastHostConnection" in the key "HKEY_CURRENT_USER\Software\Microsoft\InternetSharing". This determines what is selected in the "PC Connection:" combo box when "Internet Sharing" starts up. Normally this registry key is only changed once a connection occurs with a particular connection type. So if a user used the non hacked "Internet Sharing" app and connected via "Bluetooth PAN", then closed it out and started "WMWifiRouter" then the registry key value, and subsequently the selected entry would be "Bluetooth PAN".

In my Mortscript I simply read in this registry value, and if it's not set to "USB", I set it to "USB" before starting "Internet Sharing". You may want to implement something similar in your app to reduce the chances of user error.
[Windows Mobile Development and Hacking General] Chainfire:
Thanks for the info.

Seems like it's back to the drawing board :(
[Windows Mobile Development and Hacking General] TalynOne:
Thierry, try the following attached .dll file. Put it in the same folder "intshrui.exe". Make sure you have a ad hoc connection, start "intshrui.exe", and see if you get a different result.

Edit: If you downloaded in the last 30 seconds from the last edit, redownload, the wrong file was attached.
[Windows Mobile Development and Hacking General] hamstarz:
start wifirouter and press connect, dont touch anything else = works fine

start wifi router and press connect, then i switch to the wifi router window = wifi router auto closes and it disconnects
[Windows Mobile Development and Hacking General] thierryb:
What do you mean exactly ?

1/ put the attached file in the WifiRouter directory

2/ launch intshrui.exe that is in the WifiRouteur directory

That's right ? and then ?

I will try later when my children and my wife will be sleeping.
[Windows Mobile Development and Hacking General] Chainfire:
Device + WM version?
[Windows Mobile Development and Hacking General] TalynOne:
And then make sure "USB" is selected and press the "Connect" button. The status should display "Check USB cable connection". Test it out with your client (laptop, etc..).
[Windows Mobile Development and Hacking General] hamstarz:
htc mogul/wm6 rom 2.09...i don't care that wifirouter closes though, it's fine as long as i dont switch to that window. still a brilliant hack!
[Windows Mobile Development and Hacking General] Chainfire:
Hmm well that was not my observation, but hey, whatever :)

Something else I'm seeing is, the device jumps on standby after a while, and then WLAN disconnects. Are you seeing this as well? Do I need to build something in that keeps the phone 'awake' ?

If only everyone was so lucky!

I'm trying to implement a workaround for this. Unsure if it'll work though!

It was auto-detect for a while (e.g., it put WLAN back on after reverting settings if WLAN was on when you started WMWifiRouter). That got lost in the debugging, I'll put it back in later!

Ah yes, this will be in next update.

---

There is another thing though, I think I just hit JACKPOT. As in, I think I have beaten the 10 minute timeout issue. If that is no longer an issue, there is also no longer a need to use the hacked DLL's, the normal ICS could just be used (like in v0.1). If this works out, all this work of the past few days have been for nothing :( But then again, if this works out, it'll finally be the cross-phone solution I want it to be :D Who cares if the things _says_ connected or not, as long as it works, no?

I have been able to get it down from 10 minutes to 1 minute and 5 minutes, I'm currently having it on 68 years. Obviously I can't test it for 68 years, but if it runs for 20 mins, I'm happy and will upload that version for 'overnight' testing (I'm currently at 8 minutes... *crosses fingers*.. damn, waiting stinks!)

If that works out, I can finally progress to the more advanced settings, like auto-connect to a BSSID (if I can manage it), keeping the data connection alive, etc.
[Windows Mobile Development and Hacking General] TalynOne:
Exciting news!

Yes, I've noticed a Wifi connection loss when the mobile device goes into standby.

If the status is "Check USB cable connection" then yes, the mobile device will go into standby, after a certain amount of time, as determined by the Start->System Tab, Power Icon, Advanced Tab settings.

If the status is "Connected" then the mobile device will NOT go into standby.
[Windows Mobile Development and Hacking General] jompao:
Hi! Just tested new version and I'm sorry but no difference here.
[Windows Mobile Development and Hacking General] Chainfire:
Ok so I will have to fix the suspend thingy :) I've been happily connected for over 30 mins now without connection drop! HURRAH! Let me just fix this up!

Damn. I'm still thinking you have a configuration error somewhere. I guess one last test with the upcoming 0.4 would be in order for testing though.
[Windows Mobile Development and Hacking General] jompao:
I uninstalled the wireless and rebooted computer before the test. Also deleted the adhoc setting on Tytn and made a fresh one. But no go.
[Windows Mobile Development and Hacking General] Chainfire:
WMWifiRouter v0.4 - Back to Basics!

Ok folks, here is v0.4, and we're back to basics. No hacked files necessary at all! Let's just hope this one works for everyone!

Changelog

- Back to basics, all 'hacked files' removed. The name of your WiFi interface _should_ no longer matter.

- New way to get around the 10 minute time out problem

- Screen Toggle function added. Turns the screen off without disconnecting WiFi

- WLAN state is recorded on start and restored on exit. So if you had WLAN turned on before you started WMWifiRouter, it will be turned on again after WMWifiRouter is done cleaning up after itself

- More beers drank while making this version than during any other version!

Upgrading

- Remove any old WMWifiRouter files you have

- Follow the installation instructions

Installation

- Download the zip from my site

- Unpack it somewhere

- Copy the WMWifiRouter.exe files to your mobile device

Usage

- Make sure you have an Ad-Hoc WiFi network configured. If not, follow TalynOne's instructions in the start of this thread.

- Run WMWifiRouter.exe

- Wait. WMWifiRouter does it's best to start ICS and initiate the connection, but this can take a few seconds. If the "ICS Status" label at the top if the WMWifiRouter screen says "Connected!", all should be well.

Usage Notes

- You may close either ICS or WMWifiRouter, and the other will also exit. HOWEVER, you should not close WMWifiRouter through the task button in the Today screen. Either close ICS with that, or use the normal way of exiting WMWifiRouter.

- The "Screen Toggle" option is activated by the left soft key, and also DEACTIVATED through the left soft key. WMWifiRouter does it's best to react to it, but it COULD happen you need to soft-reset your device. Hasn't happened to me so far, but just a warning anyway. Save your things before using it!

- During development of v0.4, I had the issue a couple of times that WMWifiRouter wouldn't start if I didn't soft-reset first. I think I got that bug out, but if you still encounter it, please let me know.

- WMWifiRouter does it's best to launch ICS and initiate the connection, but I have noticed once or twice it didn't actually connect. When this happens, just task-switch to ICS and click "Connect" manually.

- As a different hack is now used to prevent the 10-minute timeout problem, no hacked DLL's are used anymore, and your normal ICS tool is used. This does however lead to the ICS program screen saying you should "check your usb-cable" instead of it saying "connected". Don't worry about it :)

- If your phone has a hardware WLAN switch, put this in the ON position before starting WMWifiRouter

So get testing all!
[Windows Mobile Development and Hacking General] dreamteam:
it hits leftsoft key in WMWifiRouter other than ICS's as it's supposed to do, so it just turns screen off.

i have to press power button to bring it back to life, and enter ICS to connect manually.
[Windows Mobile Development and Hacking General] TalynOne:
Just updated thread with new version info.

Will try to test v0.4 tomorrow morning, I just made a breakthrough in another hack that I'm writing a tutorial for (you probably won't be interested, because I think it only applies to the Mogul), no rest for the wicked.....

For personal use I think I'm going to stick with v0.2 of your app for now, that version, coupled with my Mortscripts, provides a one tap solution that seems to achieve everything I want, with the least amount of processing.

May I ask what you did to achieve your 10 minute fix?

------

I updated my original package to v0.2:

Changelog:

v0.2

Added hacked dll for "CheetahSDN1" (O2 XDA Flame)

Added hacked dll for "CF8385PN1" (O2 Atom LIFE)

Changed IP address in hacked intshare.dlls from 192.168.0.1 to 192.168.0.9 to prevent possible conflicts.

Changed "Share&KeepSharingViaUSB" Mortscript.

Added "StopSharingViaUSB" Mortscript.
[Windows Mobile Development and Hacking General] thierryb:
On the pda, everything goes well.

I turn wifi on.

I launch wifi router.

Wifi Routeur detects the wifi card.

It stops wifi.

It starts ICS and connect.

It starts wifi.

I just need know to test with a pc. But it is already a big improvement.

Great. Thanks Chainfire.

I will tell you if I am able to connect from a Pc.