Database Users

Using Windows Mobile phone as a USB WiFi receiver?

I was wondering if this is possible. I've heard of people using ICS Control to turn it into a hotspot, but I no longer have a working WiFi card. I just got a new computer with Windows 7 and all I can do is use the built-in Internet Connection Sharing that comes with WinMo until I get a long ethernet cable to wire from my router to my room.
So I was wondering if it's possible to use the phone's ability to receive WiFi to share that connection with the computer. I'm sure there's some way for it to be done. Any suggestions?

I have the same question
same situation here.
After some searching, I've found a program called "Serialtunnel" and "wmtunnel" that is supposed to do just that, however I cannot find any working download link...
Let me know if you find anything.

http://www.wmwifirouter.com/
Will work as wifi to usb, making your phone a WIFI usb adapter. I use it with my desktop when hooked to my TV in the livingroom, rather than a 35 foot cord.
Its as simple as= plug in phone, start Wmwifirouter , touch wifi to usb button.
Battery charges while working so it doesn't kill it.

phone's ability to receive WiFi to share that connection with the computer can only be obtained if your phone allows to do so. check out the official site of your phone developrs. there will definitly be some considerations about this

Two solutions
Found two programs that do just this, both work on Windows Mobile (and unfortunately not on Symbian), but are supposed to do just what you're looking for.
ICS Control
Serial Tunnel
IF anyone figures out how to get this (converted) to run on a Symbian device... Thanks.

Anyone?
Bumping to re-ask question.

WIFI
i didt understand

ravichandrabr said:
i didt understand
Click to expand...
Click to collapse
I'm looking for a program that can "Wifi to USB" on a symbian (Nokia) phone.
In other words, I want to use my phone as a wireless adapter for an old pc without wifi.

would prob get more luck asking in a symbian forum

Help with bluetooth! hci_get_route returns ERNODEV

Hi!
I am developing an application which connects a Wiimote to a bluetooth enabled android phone/device.
I did this by interfacing with the native bluez bluetooth library directly, rather than via the Android API. The reason for this is that Android API doesn't support HID devices, which a Wiimote is.
A problem now is that on some devices, mostly those sold by HTC, my app simply doesn't work. After calling the hci_get_route(NULL), this function should return an id of the first bluetooth device available (most likely 0), but instead returns ERNODEV (-1) as if no bluetooth device is available.
I suspect it has something to do with our beloved HTC grossly modifying something in the libbluetooth library to make this fail to work.
Has anyone ever done this kind of bluetooth interfacing?
How could I make this work?
Rooting the phone and replacing a library or two would be fine too.
For a list of working and non-working devices, check out the 2nd post of this thread.

HTC support
I just sent a customer service message to HTC about this issue. I hope they can get back to me with a "we'll work on it" message, or something. I really want this on my incredible. I'm new to coding like this, but could you disguise the Wiimote as another kind of device?

Just a response from someone equally interested in a solution. I'm trying to set up a bluetooth keyboard (Freedom Pro) with my gsm Hero running the 1.5 based MCR 3.2. Available drivers (Freedom's own, BlueInput & KeyPro) should work with 1.5, but HTC devices, especially the Hero, seem to be lacking something that is present in most 1.5 builds.
Investigating, I find the same issue of no route to device, because there is no known device. AIUI when bluetooth is turned on hciattach is used to establish a link to the hardware. At that point an hciconfig should list the hci0 device as present but down. However I find this list remains empty at all times.

I found this for keyboards.
Since I can't post the link, it's called "KeyPro for Android"
Google "keypro android" and click the first link.
Maybe that could help. It says it works with any android device above 1.5, however, I did read that some keyboards use a different type of bluetooth profile, SPP rather than HID.
I haven't heard back form HTC yet either.
EDIT: Upon reading your post again, you have tried this. Sorry, my bad.

Thanks for looking though The Freedom Pro is switchable between spp & hid profiles, so I figured I was safe, lol. Not with HTC's butchered 1.5 bt it seems.

Did you ever try to use the most likely id 0 on an HTC device? Even though the call to get the id fails?
Maybe you could use also the Android API to synchronize if a device is present and then use the id that Android API gives you?
Just some thoughts since I would love to see that App running on my Desire with Snesoid

Edit: Double post

tobren said:
Did you ever try to use the most likely id 0 on an HTC device? Even though the call to get the id fails?
Maybe you could use also the Android API to synchronize if a device is present and then use the id that Android API gives you?
Just some thoughts since I would love to see that App running on my Desire with Snesoid
Click to expand...
Click to collapse
Believe it or not, I actually tried this. Unfortunately, the next command (to bind the bluetooth adapter) also fails, and of course every command after that one because the adapter is not bound.
Thanks for the idea anyway.

usb
does the wii remote have usb connectivity? could it be possible to have the communication pass through that connection rather than bluetooth? one advantage of this would be increased battery life and probably better compatibility across models.
i'm sure some people would prefer bluetooth, but i figure i'll always be using it very close to my phone so i can see the screen, so the wired option is actually a bit more attractive (considering battery performance).
i know ps3 has usb connectivity as well, you just might need an adapter (mini to micro).

rubber soul said:
does the wii remote have usb connectivity? could it be possible to have the communication pass through that connection rather than bluetooth?
[snip]
i know ps3 has usb connectivity as well, you just might need an adapter (mini to micro).
Click to expand...
Click to collapse
I'm pretty sure the first answer is no - our wii is round at a friend's atm. However even if it was yes, you'd need more than an adapter. USB operates with one device as master & the other as slave. To allow you to connect slave devices to your phone it would need to be in host mode. Some mobile phone hardware implementations support this, however I don't know of any mainstream Android kernels which do. Even if you workaround that, you're left with the huge issue that slave devices can assume it's safe to draw power from the USB bus which could do nasty things (tm) to a lower power device like a mobile. This can be worked around via a powered hub, but it all gets very messy.
I looked into this a few months ago, hoping I'd be able to use a usb keyboard with my Hero. I ended up with a BT keyboard instead. Of course that doesn't work either but for completely different reasons, as hinted at by this thread. Hopefully a 2.1 ROM will solve that, but that's the subject of numerous other threads.

Uh, just throwing stuff out, what if you have a pc with two bluetooth adapters, it connects to the wii mote, and then broadcasts that in someway the android api can understand?
Also please actually try working on something with a rooted phone, the HTC EVO 4g is rootable, and I will make man love(no homo) if you get it working.
Either one works lol.

Using a PC as a proxy is kind of useless. If you have a wiimote connected to a PC, you might as well play games on the PC itself (there are nes/snes/sega/etc emulators for PCs too).
At this moment, rooting doesn't help with the problem either.

@1 True
@2 That sucks.

Do we think that this will/could be fixed in HTC's Froyo update for 2010 devices? Not looking for definite answers, just a ponderin'.

well if you send the null pairing code to the wiimote from the default bluetooth pairing screen.. it will fail to communicate with the wiimote too

waffles004 said:
Do we think that this will/could be fixed in HTC's Froyo update for 2010 devices? Not looking for definite answers, just a ponderin'.
Click to expand...
Click to collapse
Doesn't it work in stock/vanilla Eclair? I thought the main problem was with Cupcake, though HTC seem to have done weird things to every stock firmware. I read that removing Sense from a 2.1 HTC ROM breaks bluetooth. Go figure. And there was I thinking Sense was a gui enhancement

I contacted HTC about their bluetooth issues and just received this response
My name is Courtney, and I would be glad to assist you today. I understand that you are unhappy with the Bluetooth connectivity on your HTC EVO. HTC is aware of the problems occurring with the EVO and Bluetooth. We are currently investigating this issue and are working on a solution. As soon as we have an update, we will inform our customers. Thank you for contacting HTC America Technical Support. If you need further assistance, please feel free to contact us via email or at 1-866-449-8358. We are open 7 days a week from 6 a.m.-1 a.m. EST. You can also check out our Community and Support pages at htc.com/us and our pages on Facebook and Twitter.
Click to expand...
Click to collapse

I contacted HTC about this issue with my incredible and I basically got the same answer except the guy was more knowledgeable and said that other people were complaining about certain bluetooth issues. I think they know what they did and are waiting to fix it in Froyo to be easy for them. No worries though, should be comin' in a few weeks. I can't freakin' wait. I have soooooooooo much Pokemon and Mario to play.

does anyone know if this works on samsung galaxy s, i dont have my phone yet to test, but as soon as it arrives (sometime next week) i will test this.

All I can say is that my wii controller is working really well on cyanogen on my evolution now!

Nexus 7 can pair but won't connect with BT

I had originally paired my Nexus 7 with my DHD such that they were paired with BT, and at any time I can connect to the DHD from the Nexus and I would have internet access on the tablet.
On the DHD, in addition to the blue BT icon, I would also have a BT tethering notification on the top left of the status bar.
This morning, all that changed – for seemingly no reason.
I could connect fine, but the BT tethering icon was not there on the DHD. The tablet would connect, but it reported that the internet connection was not available.
I tried unpairing and pairing, and rebooting both devices.
Since then, the problem has significantly worsened.
I can still see and pair both devices fine. The pairing code comes up on both devices and I am able to confirm that the codes match and the pairing appears to work. That's where my success ends. I tap on the device to connect, and it says "connecting..." for a few seconds, and then returns to the original, unconnected state. If I touch the device again to connect, it will not only flash up for a fraction of a second "connecting..." and revert back.
This happens regardless if I try to connect to the tablet from the phone, or vice versa.
I figured the BT stack must have been corrupted somehow on one of the 2 devices, so I tried pairing the tablet and phone to my dad's Galaxy Nexus and also his Nexus 7. I can pair anything to anything, but can't connect from anything to anything.
I am rooted on both my devices, but neither of his.
I tried the program "Bluetooth fix repair" from play store, which requires root access, which claims to fix some bluetooth problems. I tried it on both the tablet and phone. After a restart, I notice it has reset my bluetooth settings like the device name, etc. It didn't fix the problem. I can still pair the tablet to the phone, but can't connect.
Any ideas what may have happened and how I can fix it?
Tablet is running stock jellybean with root, and phone is running AOSPx BR3 from XDA.

I've run into the same issues! Trying to connect my GN to my N7 over BT shows that they pair, showing the same PIN, but won't connect. Previously, I could connect my GN to my Xoom but no longer.
I've flashed back to stock on both devices (I'll do so later on the Xoom) to eliminate as many variables as possible, and I'm still getting a connection. GN is now back to IMM76K and N7 is running JRO03D, only change is supersu on both. They connect perfectly fine to my laptop but will not connect to each other. I noticed that some people got good results by turning off WiFi but that didn't help me at all. I know BT worked on my GN because I could connect to 2 different BT units in 2 different cars.
Some people are going to ask why not use Wifi. Well, I have poor reception at home and I'd like to retain internet connection on both while using Tablet Talk (which I have yet to be able to use...).

I'm tethering via bluetooth as well. Its frustrating that when I walk away with my phone, the tablet will not auto-connect via bluetooth. I have to go back and connect the two.

nhizzat said:
I've run into the same issues! Trying to connect my GN to my N7 over BT shows that they pair, showing the same PIN, but won't connect. Previously, I could connect my GN to my Xoom but no longer.
I've flashed back to stock on both devices (I'll do so later on the Xoom) to eliminate as many variables as possible, and I'm still getting a connection. GN is now back to IMM76K and N7 is running JRO03D, only change is supersu on both. They connect perfectly fine to my laptop but will not connect to each other. I noticed that some people got good results by turning off WiFi but that didn't help me at all. I know BT worked on my GN because I could connect to 2 different BT units in 2 different cars.
Some people are going to ask why not use Wifi. Well, I have poor reception at home and I'd like to retain internet connection on both while using Tablet Talk (which I have yet to be able to use...).
Click to expand...
Click to collapse
I can confirm I'm having the same issue. Only way to repair is to do a full device wipe. Power on / off doesnt seem to correct.
Confirmed this is the case iwth my N7 and Galaxy Nexus Stock Rooted and CM9 Galaxy Note.
BTW reason people want to do this is because BT tethering has very low battery life cost particularly compared to wifi tethering which will flatten a galaxy nexus in ~3 hrs.
Love to hear if anyone else found a fix for this!

Try This
I had the same issue. I went into the more settings on my phone for Wireless & Networks/Tethering & portable hotspots. Make sure the bluetooth tethering is checked. After i did this i had no issues using my phone internet through BT. I have a T989 running CM9 RC2. My N7 is rooted running the stock rom. Hope this helps.

Ayersa said:
I had the same issue. I went into the more settings on my phone for Wireless & Networks/Tethering & portable hotspots. Make sure the bluetooth tethering is checked. After i did this i had no issues using my phone internet through BT. I have a T989 running CM9 RC2. My N7 is rooted running the stock rom. Hope this helps.
Click to expand...
Click to collapse
I can confirm I was having the exact same problem as everyone else and this fixed it for me. The only other thing I had to do was connect FROM the Nexus, not the phone (an HTC Sensation). Trying to connect from the phone was a no-go. Thanks!

I cant pair my Nexus 7 with my Sony Ericsson MW600 bluetooth headset.
Sent from my GT-N7000 using xda premium

jackkerouac said:
I can confirm I was having the exact same problem as everyone else and this fixed it for me. The only other thing I had to do was connect FROM the Nexus, not the phone (an HTC Sensation). Trying to connect from the phone was a no-go. Thanks!
Click to expand...
Click to collapse
I forgot to add the part about paring through the N7 instead of the phone. Sorry
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

Nexus 10 usable as screen?

Hi xda users,
since the display of the Nexus 10 will be awesome I'm contemplating getting it because I'd really like to use it as a (second) screen for my computer. Does anyone know if this will be possible? Probably not without, but maybe *with* a mod? Can we use this Miracast Screen Share the other way round possibly?
It'd be really cool to play games on it as well, with the power of my desktop. I wouldn't be able to tell the pixels apart/ wouldn't see any pixelisation. Also this will get rid of the need for antialiasing which will boost performance
Woohoooo

There's an app for that
iDisplay or Splashtop 2
I personally haven't tried them out but they might be what your looking for.

Thanks! Well Splashtop2 is only over Wireless, so it's probably going to be to slow at least for gaming. iDevices with USB support looks better. Does anyone know how bad the latency is (with both)?

Anyway to make the tablet as a video monitor? i/e hdmi IN?

Splashtop2 is pretty good and there is hardly any delay so depending on what you are using it for it might be okay, but it doesn't give you an extra screen just mirrors an existing one. If you want an additional screen you could try airdisplay, haven't tried it for gaming but it might be okay.
Also I have played D3 using Splashtop and besides not being a very good game it worked fine.

OMG that's awesome sauce
OMG that's an awesome idea, the Nexus 10 has resolution comparable to my 30 inch monitor... crazy.
please post to tell us if it worked.

Yeah I'm very interested in this. I tried out Air Display and it worked well, but it had low framerates and some lag.

How can I use the Nexus 10 to replace the cracked screen on my Lenovo E420 laptop?
I will not always have access to a wireless network, so I need to find a solution that is either wired or bluetooth.
I assume a wired connection would be best, followed by bluetooth.
Thanks.

tt c6 said:
How can I use the Nexus 10 to replace the cracked screen on my Lenovo E420 laptop?
I will not always have access to a wireless network, so I need to find a solution that is either wired or bluetooth.
I assume a wired connection would be best, followed by bluetooth.
Thanks.
Click to expand...
Click to collapse
I don't think it's possible to do it wired, because the Nexus 10 has no input port for its display.
Bluetooth as far as I know does not have a protocoll for video transfer, so that's not possible either afaik.
However you might be able to connect them per WiFi Direct oder WiFi Ad-Hoc, meaning you don't need WiFi network on it's own because they connect directly or the Nexus 10 to the Ad-Hoc network, respectively. If your laptop supports WiFi Direct (you can look it up on the WiFi Alliance Website, every product is listed there) you might be able to use Miracast. But you need software for it on your laptop for windows or whatever you use. If you got Android 4.2 on it, then you don't need new software ;P (that's probably not easily achieved, but may be soon when there's an official x86 AndroidOSP Version).
If not, try DLNA. I don't know if Windows or Linux supports it, but I think support is achievable through software.
Good luck and report back if it works!

Persistent Wifi / Wifi Direct issues with Shield TV

I created a topic a while back about Wifi being disconnected after waking from standby. I turned off standby mode then and dedicated my 5GHz band to the shield. Problems seemed to go away, but they've been getting worse over the last few weeks. This is xposted on nVidia's forums, but I want to see if the XDA community has any advice as well. Any help is appreciated
--------------------------------------------------------------------------------------------------
I've had my Shield TV since about last November. Overall the unit is great but I'm getting problems with Wifi that seem to be getting worse. When I first had the unit, it seemed like it would disconnect from my wifi after going to sleep and need to be restarted or manually reconnected about once a week or so. I have an ASUS RT-AC68U, and I am using my 5GHz radio. The Shield is the only device I allow to use 5G, and from Wifi Analyzer, there are no other 5GHz routers in my neighborhood. My router and Shield are on the same floor of my house, and only separated by about 20ft with minimal obstruction (Shield is inside a TV stand, router is in the next room with door open.
When the problem first started, I set the unit to not go into Standby mode, which seemed to help (it was always disconnected after coming out of standby).
Now it seems to be getting progressively worse. The unit now needs to be rebooted after not being used for some time. This is typically once when we first get home from work/school and later on in the night after dinner. In addition to Wifi not working, Wifi Direct often stops working as well as my shield controller wont work. I have to resort to a USB keyboard to get the thing to reboot.
I have updated the firmware each time it becomes available which has made no impact on this issue. Currently I'm on 3.1 stock firmware. I have not rooted or unlocked this device. Does anyone have a similar issue? Is there anything I can do to try and fix this? Connecting by Ethernet is out of the question, I don't have a drop near by and I bought this unit because it has wireless AC capability.

I got disconnects from wifi but never seen an issue with the wifi-direct which is for the controller. The 3.1 update did sort the issue with my shield remote though.
Honestly the short answer is to use Ethernet to get the best out of the kit, even a cheap Homeplug networking kit would be better than the wifi. Besides the wifi drop outs, I had no end of grief trying to get SPMC/KODI to access shared folders on my network with wifi (yes even 5GHz).....using Ethernet resolved the headache.

honosuseri said:
I got disconnects from wifi but never seen an issue with the wifi-direct which is for the controller. The 3.1 update did sort the issue with my shield remote though.
Honestly the short answer is to use Ethernet to get the best out of the kit, even a cheap Homeplug networking kit would be better than the wifi. Besides the wifi drop outs, I had no end of grief trying to get SPMC/KODI to access shared folders on my network with wifi (yes even 5GHz).....using Ethernet resolved the headache.
Click to expand...
Click to collapse
*sigh* It's frustrating to buy something for a specific feature (wireless ac - upgraded router as well which I had been mulling for a while)... to have it not work. Thank you for the suggestion though. I was looking at just getting a wireless AC AP or adapter if I gave up on the sheild's network, but the homeplug is in the same ballpark and probably more reliable so I'll keep that in mind if it gets to that point.

jst07 said:
*sigh* It's frustrating to buy something for a specific feature (wireless ac - upgraded router as well which I had been mulling for a while)... to have it not work. Thank you for the suggestion though. I was looking at just getting a wireless AC AP or adapter if I gave up on the sheild's network, but the homeplug is in the same ballpark and probably more reliable so I'll keep that in mind if it gets to that point.
Click to expand...
Click to collapse
No worries...I do realise it's not what you wanted to here. IMHO if a device is static then hard wire it, I use wi-fi only for mobile/portable devices.
I think your best move would be to look at getting a triple pack homeplug kit (dual ethernet ports would be good). One is for the Router, another for the SHIELD TV and the third (if you deem necessary) for your old router. Hopefully your old router can be setup as an AP and extend your wifi further throughout your home or garage/garden even. The kits are dead simple to use, although they can be fussy about the power extensions used...Ideally you want one that has passthrough so you can plug the adapter into the wall outlet, then the power extension into the homeplug adapter (Just a word to the wise in case you go this route and encounter problems).
I've had my SHIELD TV for a little while too and I also thinks it's great....I've been offered silly money for it from friends, once they've seen all I've set it up to do. I've actually got to the point now where I want to do a factory reset. I have done my experimenting and now know what I want on there, so it won't take long to redo and i'll lose the junk in the process...perhaps it might help cure some of the wifi niggles I encountered too...who knows?
Wish you all the best with it

honosuseri said:
No worries...I do realise it's not what you wanted to here. IMHO if a device is static then hard wire it, I use wi-fi only for mobile/portable devices.
I think your best move would be to look at getting a triple pack homeplug kit (dual ethernet ports would be good). One is for the Router, another for the SHIELD TV and the third (if you deem necessary) for your old router. Hopefully your old router can be setup as an AP and extend your wifi further throughout your home or garage/garden even. The kits are dead simple to use, although they can be fussy about the power extensions used...Ideally you want one that has passthrough so you can plug the adapter into the wall outlet, then the power extension into the homeplug adapter (Just a word to the wise in case you go this route and encounter problems).
I've had my SHIELD TV for a little while too and I also thinks it's great....I've been offered silly money for it from friends, once they've seen all I've set it up to do. I've actually got to the point now where I want to do a factory reset. I have done my experimenting and now know what I want on there, so it won't take long to redo and i'll lose the junk in the process...perhaps it might help cure some of the wifi niggles I encountered too...who knows?
Wish you all the best with it
Click to expand...
Click to collapse
Thanks. I switched to my 2.4G wifi and problems seem to have gone away, at least for now. Probably try that a little longer. I too have thought about resetting and using one of the custom roms on here.

Using 2.4Ghz is worse for some users from neighbor's wifi causing it to drop out.
I use 5Ghz and have to occasionally restart the device to fix it.
You would be better off using power off instead of relying on standby mode as that is buggy and prone to causing issues with stuff like audio and a stored media playback glitch.