View Single Post
Old 11-24-2010, 06:01 PM   #6
sahmad88
Zealot
sahmad88 will become famous soon enoughsahmad88 will become famous soon enoughsahmad88 will become famous soon enoughsahmad88 will become famous soon enoughsahmad88 will become famous soon enoughsahmad88 will become famous soon enough
 
sahmad88's Avatar
 
Posts: 120
Karma: 567
Join Date: Feb 2009
Device: nook color
Quote:
Originally Posted by LoganK View Post
I don't know what the issue is or how to fix it, but my personal opinion is that it is likely related to the use of an ad-hoc wireless network as opposed to infrastructure mode. I would advise trying to figure out what modes the custom Galaxy S ROMs use for sharing, and, if I'm right, look for suggested workarounds.
You are correct, I believe. Thanks for your input. I had no idea where to even start looking for answers to this problem. But thanks to your post I did a little more digging and found my answers. Unfortunately, this also means that it looks like I am out of luck. At least for now.

I am running Android 2.1 right now. It sounds like 2.2 might support infrastructure mode (?). I am not sure about that. And even if it does, will it work when rooted or only with the paid 3G hotspot app that Verizon will include? Because then the Barnacle or Wireless Tether have to be rewritten to support that, right?

Or maybe B&N will update the NC to support ad-hoc mode? But for now, no wi-fi tethering to my phone. Oh well, no big loss. But at least my question has been answered. Karma to you.
sahmad88 is offline   Reply With Quote