Hi everybody.
I would like to know if someone is working on a hack for our NOOKs tablet to access ad-hoc networks. I saw there is some movement on other devices, as android, at least the latest version, does not include support to ad-hoc network. The reasons are obvious, Google team will not implement this in the next version as they are going further to offer mobile services an they would you require that you purchase a new data plan.
So, it is time to have a hack for our android(ed) NOOK devices in order to access ad-hoc networks from our mobile phones.
Does anyone know about a similar movement on NOOK community ?
Regards.
Angelo
I'm not sure what you are trying to accomplish here based on your statement. Ad-hoc networks only allow two individual computers to connect without one being configured as an access point, sort of like bluetooth in terms of functionality. The reason it is unavailable is probably more to do with security as it is a dangerous connection to use or enable. If you are talking about tethering to for instance your phone, that works fine, use it all the time. This doesn't require ad hoc, only a tethering app (e.g. pdanet) or it is built in for many phones.
If you have an old Nokia device, I've noticed that when they tether via JoikuSpot, they create ad-hoc networks. If this is the reason you want ad-hoc networks enabled (to tether), I guess this is a valid reason. To pair two devices together, that may become troublesome (I doubt it'll be working any time soon).
Tethering via ad-hoc is perfectly fine, I'll take a quick look at it for the Nook HD+, and I'll reply back with what I find; hopefully a solution. I'll try and take a look some time this Wednesday or weekend.
I've not fully tested it, but doesn't Cyanogenmod enable ad-hoc networks by default? So, I guess you could go down that route (of course, I do accept that CM10 isn't for everyone).
P.S. If I do, or anyone else enables ad-hoc networks on the Stock ROM, you'll need to be rooted, and with CWM (since you'll need to apply a .zip) to hopefully enable ad-hoc networks.
All the best.
HiddenG said:
If you have an old Nokia device, I've noticed that when they tether via c, they create ad-hoc networks. If this is the reason you want ad-hoc networks enabled (to tether), I guess this is a valid reason. To pair two devices together, that may become troublesome (I doubt it'll be working any time soon).
Tethering via ad-hoc is perfectly fine, I'll take a quick look at it for the Nook HD+, and I'll reply back with what I find; hopefully a solution. I'll try and take a look some time this Wednesday or weekend.
I've not fully tested it, but doesn't Cyanogenmod enable ad-hoc networks by default? So, I guess you could go down that route (of course, I do accept that CM10 isn't for everyone).
P.S. If I do, or anyone else enables ad-hoc networks on the Stock ROM, you'll need to be rooted, and with CWM (since you'll need to apply a .zip) to hopefully enable ad-hoc networks.
All the best.
Click to expand...
Click to collapse
Yes, you are 100% correct. I do have a Nokia and Joikuspot.
The other problem is that I am a complete newbie to android, cyanogenmod etc.
I have rooted my Nook HD, but I dont know if it is using cyanogenmod. I just purchased a microSD card that rooted and installed gapps..
Thank you for your help....
Rooting stock does not add CyanogenMod. You must install that separately by installing it to a bootable SD.
Sent from my Nook HD+ running CM10 on Hybrid SD
I looked around and didn't see ad hoc in my CM10, and there's this: http://forum.cyanogenmod.org/topic/62183-ad-hoc-was-disabled-in-cyanogenmod-10/ Apparently CM has followed google here.
Maybe this can help:
http://forum.xda-developers.com/showthread.php?t=872521
It seems that for NooK Color, this is already done.
AngeloGomes said:
Maybe this can help:
http://forum.xda-developers.com/showthread.php?t=872521
It seems that for NooK Color, this is already done.
Click to expand...
Click to collapse
It does not help on HD+ (included wpa_supplicant binary complains in logs that it does not support wi-fi n spec).So wi-fi does not work at all on Nook HD+ with this hack.
We need a newer patched wpa_supplicant (that supports ad hoc and wifi mode n). Hacked version for any recent android device should go. I'm going to try that http://androidtablethacks.com/android-tablet-hacks/how-to-enable-adhoc-wifi-on-android-tablets/ once have a spare time.
I was talking about the idea of that topic.
But I think you got it.
About to have support to wifi n: I suppose that wifi g support is enough, right ?
AngeloGomes said:
I was talking about the idea of that topic.
But I think you got it.
About to have support to wifi n: I suppose that wifi g support is enough, right ?
Click to expand...
Click to collapse
It would be enough, but supplicant fails to start
I've dedicated some time to study this problem. Here is the result:
Dmitriusan said:
Is there any chance the rom will include the ad-hoc patch? Or maybe there is anybody with configured build environment who can recompile wpa_supplicant binary?
The most recent patch version I've found is http://www.verydemo.com/demo_c131_i18097.html
Old patch discussion http://forum.xda-developers.com/showthread.php?t=754961 and the old patch itself http://szym.net/android/wpa_supplicant-ibss.patch
I've tried downloading few patched wpa_supplicant binaries for another devices, but they all use another wi-fi drivers. Nook HD+ has wl1271l chip and uses wl12xx driver.
Many people seem to use Joikuspot to share GPRS/EDGE/3G to another devices via wifi (mobile ad-hoc spot), but Android does not see any adhoc network and it's really annoying...
EDIT:
Or at least maybe anybody has compiled tun.ko module for the latest kernel? I'm trying to get BlueVPN working (to connect my N78 phone as Dial-up Networking device via bluetooth)
UPD
Finally got Internet tethering working with N78. The tun module is present, but for some reason not autoloaded at startup. So, I performed
$ su
# modprobe tun
and managed to connect via BlueVPN to N78 (EDGE). The name of program is a bit misleading, it just connects to phone with BlueDUN installed or to any (?) cell phone that can work as bluetooth modem. I'm using the second option.
Click to expand...
Click to collapse
Joikuspot is told to discharge Nokia device in ~40 minutes of active usage. So tethering over bluetooth seems to me not only the only available, but also the prefered solution. Almost any phone with bluetooth should feet this purpose.
So, here is the final procedure:
- You need the rooted firmware with any terminal emulator (I use CM10 and build-in Terminal Emulator)
- Install BlueVPN
- pair your devices over bluetooth (may need to repeat pairing from scratch after installing BlueVPN)
- Start terminal emulator and type
su
- type
modprobe tun
- no output is okey. If you get the module not found error, I have bad news to you You need the tun.ko kernel module built exactly for your ROM. But at verygreen CM10 firmware tun.ko is present.
- disable wifi
- Start BlueVPN. Go to the settings and configure you connection options (I've enabled auto-resume and lcp compatibility, yo may need to play with another options to may things work) and GPRS settings (may be found at mobile provider web-site. At least Phone number, Access point need to be configured, in my case I've also set an Authentification to none)
- press back. On your screen you should see the paired device name. Click on it (probably at the button on the right)
- If confirmation appears, say "trust"
- If the text "BluVPN is connected with ..." is displayed on the bottom of your screen, congratulations: you are connected. Otherwise wait for some time and try selecting your device in a list again. Maybe you will have to play with settings / reboot and repeat the whole procedure/reboot your cell phone.
In my case, it takes 1-2 tries to connect, but connection seems to be stable. Don't forget that bluetooth distance is limited
Few notes: you have to run commands su/modprobe tun after every reboot.
Related
I am scheduled to Deploy to Iraq later this fall and will be taking my trusty N1.
In Iraq you pay an incredible amount of money for the internet it is something like $75 for 96k. One on the down falls is you link up via cat5. I had my HTC Touch Pro last time and I was able to update data etc surf the internet using active sync via miniusb while it was plugged in to my laptop. Any ideas? Thanks in advance.
Not sure if this will work on the N1 (do any custom ROMs support ad-hoc WiFi?), but worth a shot: http://modmymobile.com/forums/491-jailbreak-root-access/544146-connect-g1-ad-hoc-network-solved.html (skip to "Step 3" for instructions on changing the tiwlan.ini file).
P.S. Needs root for obvious reasons.
If you run Windows 7 check out www.connectify.me It will turn your current connection into a wifi access point on through your computer's wireless device
ManticoreX said:
If you run Windows 7 check out www.connectify.me It will turn your current connection into a wifi access point on through your computer's wireless device
Click to expand...
Click to collapse
Thanks for that link, I'll have to try it out!
[Edit]
Unfortunately Connectify's Access Point mode is only supported on a limited number of WiFi cards, as seen here. My fairly new (1 year old) Lenovo X61 Tablet can only do Ad-Hoc, which still requires modding the wpa-supplicant on the N1. At that point Connectify becomes useless, since you can enable ICS in Windows on your own.
sweet and thanks. i am using this in-flight on gogo so i have access to two devices and only pay for one.
Sorry you are having issues, but yea not all cards are supported. Luckily, both my desktop and laptop have been compatible. My laptop initially had issues because I was not on the newest drivers for the wireless card. If your card isn't directly listed on the unsupported list, it might be worth it to try and upgrade drivers and test one more time.
Unfortunately I am running Xp on my laptop.
http://www.brighthub.com/computing/windows-platform/articles/7785.aspx
https://review.source.android.com/#change,13291
Hope that helps.
Devastatin said:
http://www.brighthub.com/computing/windows-platform/articles/7785.aspx
https://review.source.android.com/#change,13291
Hope that helps.
Click to expand...
Click to collapse
The first link is a guide for setting up an ad-hoc connection on Windows XP, the second is a link to a change to the Android source code that's been abandoned 2 months ago.
The good news is that according to the comments on the 2nd link Google is working on implementing Ad-Hoc support. The bad news is that it's not in FroYo, so we might have to wait for Gingerbread to see it. Of course, there's nothing preventing CyanogenMod team from implementing this change into CM6, so they would be the best people to ask about it.
In the network settings on my mac you can 'broadcast' your connection. The tutorial I read showing me how to do that said windows has a similar feature.
You can use travel router and setup internet sharing...
Source: you have to right-click the connection source->properties->advanced and setup the internet sharing.
Destination: If you have a spare ethernet jack, GOOD! Use it.
I know some Ralink-based wifi cards support virtual AP mode (the best bet are Hawking and Asus and I have both).
perhaps somebody here could be tolerant enough to assist or direct me to concise clear info to such a likely passe situation.
Phone again, stock from VZW and fully updated.
Barnacle installed from market.
I have a few questions;
1)Superoneclick seemed to only install "superuser" on my phone. Does this mean the busy box and abd things, of which I have no idea what to do with, is only accessible via my win7 64 bit pc while the phone is connected to it via usb?
2)How do I optimize this phone with stock rom and remove "bloatware" as well as eliminate intrusive programs? Are there any threads which ID these as well as their functions?
3) Jrummy Droid Overclock installed, several versions in fact, and the best I could do was make the phone extremely laborious and finally reverted back to stock settings before uninstalling. I did have to click the "experimental" box to make it able to scale the stock rom.
Any thread or info as to some failproof settings to make this stock thing work much better/faster?
4) Can this phone, usb tether the data connection without any paid apps or limitations regarding secure sites and such?
Interestingly enough, I'm finding the search functions on this forum to be impossible on my handheld and just about the same from my pc. From the handheld, it wanted me to assemble pix which my touchscreen or keyboard didn't seem to allow.
From the pc, 'no matches found' or something to that affect.
Also, when I was having problems recalling my login info, had almost given up deciding instead to reregister, I got a denial message based on having a verizon wireless IP. Weird.
I'm rereading the beginners info and it would be nice to be able to simply make my stock rom'd droid better.
Feel free to tell me if I'm pissing in the wind and need to just do different roms and or kernals. However, I'd like to just keep it simple for now.
You are able to download Busybox straight from the Android Market: https://market.android.com/details?id=stericson.busybox&feature=search_result
You can tether your phone to create a wireless hotspot, but I'm not 100% sure about USB tether.
skadude66 said:
You are able to download Busybox straight from the Android Market: https://market.android.com/details?id=stericson.busybox&feature=search_result
You can tether your phone to create a wireless hotspot, but I'm not 100% sure about USB tether.
Click to expand...
Click to collapse
Yes and thanks, I snagged barnacle for that. It works fine although I'm either too green to make it secure, or the WEP stuff is broken.
That is why I'd like the option to have a more secure hardwire tether.
I know I can do pda.net and some other apps, it seems to me that it should be able to do that perhaps just with some tweaks.
So when I extracted superoneclick on my pc, I see busybox and such in that file. I just did the one click and nothing else, not even on my phone.
It is interesting how fast such basic topics become inundated with miles of confusing info to bewilder a virtual computer twit.
It looks like what you want to do is basically create a wireless hotspot with your phone? Because I use Wireless Tether for Root Users and I am able to encrypt it and set up a secure connection.
Here's what I pulled from the Barnacle website:
How do I use WEP?
Barnacle support 40 and 104-bit WEP. In Settings find Wireless Security and enable WEP, then type in the key. For 40-bit WEP, type in 5 ASCII characters or 10 hex digits. For 104-bit WEP, type in 13 ASCII characters or 26 hex digits. Passphrase is not supported.
Click to expand...
Click to collapse
skadude66 said:
It looks like what you want to do is basically create a wireless hotspot with your phone? Because I use Wireless Tether for Root Users and I am able to encrypt it and set up a secure connection.
Here's what I pulled from the Barnacle website:
How do I use WEP?
Barnacle support 40 and 104-bit WEP. In Settings find Wireless Security and enable WEP, then type in the key. For 40-bit WEP, type in 5 ASCII characters or 10 hex digits. For 104-bit WEP, type in 13 ASCII characters or 26 hex digits. Passphrase is not supported.
Click to expand...
Click to collapse
Phone Settings? "no "Wireless Security" to be found nor did I readily find anything to do with WEP under the Wireless sections.
Barnacle? Again, no "Wireless Security" section found. There is a "Wireless Encryption" settings section. I did enable it with the app stopped and set a five digit alpha code. Restarted Barnacle and my pc completely disregarded it, connected to it with no input required and the signal still shows as unsecured and public.
I'm pleased that it tethers, I would like to make it secure and I would also like to easily usb it to any laptop or pc sans having to load software on them unless said pc/device was older and didn't automatically recognize this phone, as this new win 7 pc did, where upon loading some drivers would be seem reasonable.
I'm not pc/droid knowledgeable enough to know if this is dreaming but, it seems reasonable that it's usb output could be toggled and be seen as a modem connection.
I'm sure it can, but people use Wireless tethering more than a physical USB tethering.
I've never actually used this, but I've heard of people using it when they need to tether via USB: https://market.android.com/details?id=com.mstream.easytether_beta&feature=search_result
Yes and thanks, I truly appreciate your efforts to help and your tolerance for my ignorance.
I am aware of those various usb tethering programs and I suppose my question is why must software be loaded on a device capable of seeing other usb plugged connections and run them 'plug and play'?
I'll see if somebody with barnacle can assist me with the WEP issue. I've tried it several ways and have had no success. Possibly related, my droid no longer will send MMS. It still receives them, just no longer sends. I wish I could say if that occurred after rooting or after attempting overclocking, but, it happened after one or both.
Wait, does the Easy Tether not require software to be installled on usb tethered device? I was sure it did and after reading the page, it doesn't mention it.
It's still bizarre that I can wirelessly tether now that soc rooted it, but I still have to buy an app to usb tether it, and I was pretty sure, install stuff on device to be tethered.
No problem, anytime!
Honestly, I don't know much about Easy Tether, I've heard about it, but have not delved much deeper into it.
What ROM are you using (if any)? I know that I had some issues with CM7 and a little bit less with Cronos right now, where I send a text message and it hangs with "Sending..." for hours at a time.
How much did you overclock your phone by? What vsel?
Sent from my Milestone using XDA Premium App
phone is stock other than being rooted
I used JRummy's Droid Overclock as it is supposed to overclock a stock rom'd A855 droid.
I tried several several many settings, mostly what was recommended, but none of them seemed to make it better, and if they did, I couldn't seem to make them stick upon rebooting.
Kept all attempts at or below 800MHz.
I'm sure it's my lack of understanding and likely there are some simple settings that will speed it up with just a few clicks as well as save thru a fast and speedy reboot.
Brand, spanking new NC, came with updated software version already installed. Freshly rooted. Won't recognize ad hoc networks, of course :-(
Already tried the most up to date wpa_supplicant file fix, to absolutely no avail. Using rooted droid 1, with well-functioning wireless tether. Barnacle also a no go.
Any suggestions would very appreciated. Pulling my hair out, one by one, getting balder...balder.......
mjf0000000 said:
Already tried the most up to date wpa_supplicant file fix, to absolutely no avail.
Click to expand...
Click to collapse
What does this mean?
Thanks for your help. What I mean is that the wpa supplicant fix (as described in previous threads - I'm using the Droid 1 browser or I would link back to that xda thread - sorry!) produces no effect. When the NC scans for wireless sources it recognizes many hotspots. Including my home wifi router. It simply will not list the phone's ad hoc signal (called either android tether or barnacle, depending which turned on.) The winbox connects just fine, so I don't think it's the phone's signal.
Others have used the wpa supplicant fix and their NC has worked well, but from what I can tell, they have NC's that were not upgraded to latest version, or had upgraded themselves. I wonder if brand new NC with the upgrade installed, needs a different fix. Not to be paranoid, but the wireless tethering apps have fallen out of favor with the powers that be. Maybe there is more disabling going on --- or I could just be doing something wrong. (Would not be a surprise)
Has anyone with a NC that came with the update pre-installed been able to get wifi tether? Using a phone with the paid wifi hotspot function will work with the NC. However, the droid 1 does not have a paid wireless hotspot option (it's too ancient, apparently). I had to sideload the wireless app to my phone, as it's not available on the market anymore, andit works well - just not with NC, even with the standard wpa supplicant fix.
Would upgrading the NC to CM7 take care of this issue? I'm a children's doc with skimpy hacking skills, & am a little afraid to try the procedure. Like doing an appendectomy with without knowing human anatomy
mjf0000000 said:
Has anyone with a NC that came with the update pre-installed been able to get wifi tether? Using a phone with the paid wifi hotspot function will work with the NC. However, the droid 1 does not have a paid wireless hotspot option (it's too ancient, apparently). I had to sideload the wireless app to my phone, as it's not available on the market anymore, andit works well - just not with NC, even with the standard wpa supplicant fix.
Would upgrading the NC to CM7 take care of this issue? I'm a children's doc with skimpy hacking skills, & am a little afraid to try the procedure. Like doing an appendectomy with without knowing human anatomy
Click to expand...
Click to collapse
Wireless tether is working perfectly for me with CM7 right from the get-go, however....It does not work with Honeycomb at the moment (and I have not done the supplicant fix yet).
Thanks, hockeyfamily. I should probably go ahead and do the CM7 ROM.
update
Still have rooted v 1.2, not yet CM7. What finally worked for enabling ad hoc wifi, was deleting everything i had done previously, redoing it over again, & using Barnacle. The Wireless Tether app just giving a message to the effect that it was 'connected, but no internet.'
I updated to 1.2, rooted with an early version of MN, have an Eclair phone running Barnacle and this http://forum.xda-developers.com/showthread.php?t=872521 works great for me.
Ok,
So, I, along with a few others, pay for the Unlimited Mobile HotSpot and want this app to work as other (root) tethering apps only allow Ad-Hoc.
Here's what I did to get it to work on my Windows 7 x64 Computer as of just a few moments ago and I do plan to work on this issue to get this figured out.
I've discovered that the /data/misc/dhcp/udhcpd.conf file is what controls the DHCP addressing for the 4gMobileHotSpot App. Within this app, I discovered (in the Modded ROM (as of now, I have Gingervolt1.1)), that the "Option DNS" addresses were completely wrong. This was apparent from the get go as they were internal IP address starting with 192.168.x.x.
The steps to get this app working on Windows is:
0 - Be Rooted (Sorry, just had to point the obvious out in Step 0)
1 - Use the market and download/install the Text Edit (Paul Mach) App
2 - (TESTed and Working), Use AntTek (root) Explorer and navigate to:
/data/misc
3 - Long Press the udhcpd.conf file and select to open with the Text Edit App
4 - Change the 'option dns' from 192.168.x.x to 66.174.92.14 69.78.96.14 and save/exit
5* - In Windows, set the IPV4 Properties to:
Use Following Address:
IP Address: 192.168.1.5 (or anything in between start and end range in text file)
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.1.1
Use Following DNS server addresses:
Preferred DNS Server: 66.174.92.14
Alternate DNS Server: 69.78.96.14
6 - Start 4gHotSpot App
7 - Tell Windows to Connect and you should be connected.
NOTE: It is late and I know that this will become clearer as time goes on and since I have to work in the morning, this is the best I came up with in a few minutes after figuring out that the hang up was with this file, in which I knew it's been a DHCP issue all along. Why this file is changed with the Modded ROMs is beyond me and I doubt MT changed this, so likely it is something to do with the DE-odex or some other modification of this app and it's initialization. Just deleting the CONFIG file will only cause it to write a new one with the wrong values again.
For those who do use this app, it is known to stop responding at times and I am going to look into that. I'm thinking this is a DNS issue and will try some other DNS Servers (8.8.8.8 I believe is a Google public DNS)..
In the meantime, this is a start for anyone to add to this that has more DHCP/DNS/Network experience. I don't have another android device handy to test the connectivity, so will have to get that figured out.
Key point here is, is that the 4gHotSpot App gets corrupted with the Custom ROMs and for some reason sets up wrong DNS servers in the Config file.
Hope to see some thoughts, additions, fixes, to this problem with this being pointed out, from others. I will continue to work on it throughout this next week after work.
Last Note: The DNS server numbers came from the original Config prior to rooting/modding. Also, I do know that is it redundant to have them in the config file AND the Windows Properties. It's just that setting Windows to 192.168.1.1 (option router in the Config file) didn't work. Again, will work on cleaning this method up and simplifying.
-Cybie
Thought I would give this a try today after re-rooting. I had no luck getting connected with the 4g hotspot app.
On my phone the file was in /data/misc/dhcp/ and the values were already correct in the file.
I tried changing the dns to a public one and back - neither worked.
I tried moving the file to /data/misc and it didn't work.
My ipad seems to connect ok but hangs trying to lease an ip address. Reloaded v6 tot and upgraded to non-rooted gingerbread and the app works again.
Is it possible you changed something else?
I'm glad it's working for you. Wish I could get it working as this is the only thing keeping me stuck on a non-rooted phone.
displacedbuck said:
Thought I would give this a try today after re-rooting. I had no luck getting connected with the 4g hotspot app.
On my phone the file was in /data/misc/dhcp/ and the values were already correct in the file.
I tried changing the dns to a public one and back - neither worked.
I tried moving the file to /data/misc and it didn't work.
My ipad seems to connect ok but hangs trying to lease an ip address. Reloaded v6 tot and upgraded to non-rooted gingerbread and the app works again.
Is it possible you changed something else?
I'm glad it's working for you. Wish I could get it working as this is the only thing keeping me stuck on a non-rooted phone.
Click to expand...
Click to collapse
Ok, so here's what I did after reading your post:
1 - Corrected the path (Sorry, it was late and I missed that /dhcp portion of the path).
2 - Deleted "option router 192.168.1.1" from udhcpd.conf file
3 - Deleted "option dns x.x.x.x x.x.x.x" from udhcpd.conf file
Set Windows up with the Following:
Static IP : 192.168.1.2
Subnet : 255.255.255.0
Gateway : 192.168.1.1
DNS Servers : 4.2.2.1 & 4.2.2.2
That worked.
So, what I am seeing if I try to use DHCP on Windows is that the 4gHotSpot gives the computer 192.168.16.x addressing even though the config file is set to give out 192.168.1.x addresses (x=2 through 254). It also gives Windows 3 DNS servers that are local IP addresses and will never go anywhere.
What to do now? Figure out what is being changed with the Custom ROMs that is causing the app to act like that. In fact, it will act like that when I restore back to Stock GB Rooted via restore from backup in CWM, but I have yet to test deleting the config file and restarting 4gHotSpot to test. I will do that over the weekend as I don't have a lot of time I can have my phone down during week. But I do plan to up to the GingerVolt1.3 tonight.
As of right now, I am using my windows machine connected to the 4gHotSpot App to write this post. Also, I don't know about the iPhone/iPad and possible settings. If you can Force (Set a Static IP) then follow what I did up above, but you will also need to set the DNS servers and not sure you can do that on an Iphone/iPad.
The DNS Servers I listed are found on a public list and are also said to be Verizon DNS servers...
The other problem I found and is an issue with the app, is using auto b/g/n will cause the hotspot to lose connectivity. When in that mode, I connect at 65Mbps, but it drops down to 6Mbps and stalls and fluctuates. I set it to 'g' only and get a SOLID 54Mbps connection just like the tether apps.
SPEED TEST Results: 18.35 Mbps Down, 10.66 Mbps Up without a glitch.
Obviously this app works with DHCP addressing as STOCK. So, I will begin my Android Development with figuring out one of two things. Either get this app to work as it's supposed to, or create a root app with 'Infrastructure' based on whatever I can find in the coding for this app if I can figure out a way to decode it.
I personally hate the idea that you can't connect other android devices to AdHoc and also annoys me to have to manually connect Windows since it doesn't seem to have the ability to automatically connect to AdHoc Networks. Linux does perfectly fine with auto connect AdHoc, go figure. Android is Linux Based, yet can't AdHoc, but provides an AdHoc as an access point for other devices. weird, lol.
Let me know if any of this helps, but do know I am going to continue to figure this out. I'm sure de-odexing the app had something to do with it as I'm sure Verizon did their best to keep this app from being hacked for free HotSpot service.
-Cybie
Thanks for the detailed response.
I'm going to try again. I won't be able to try until tonight or tomorrow morning when I have time to play with it and roll back if necessary.
I'll let you know if it works or I find out anything else.
Before you install a ROM and have the app working, try connecting your computer and get the values (ip, dns, gateway, etc.) That the app dhcp assigns and post that. Rooting the phone alone shouldn't break the app either. By getting those values posted, would help and also save me from downgrading just for that purpose. Knowing that it works with without a mod is one thing,. So my focus is working on getting it to function with a modded ROM.
It's strange that i can get the app to work if i force the connecting device to values (static settings), but this doesn't help with certain devices and needs to connect via dhcp.
-Cybie
Sent from my VS910 4G using XDA App
from unrooted:
ip: 192.168.1.2
subnet: 255.255.255.0
router 192.168.1.1
dns 66.174.95.44, 69.78.96.14
search domains: local
Still haven't retried the root and may need to wait another day or so until I have some more time
displacedbuck said:
from unrooted:
ip: 192.168.1.2
subnet: 255.255.255.0
router 192.168.1.1
dns 66.174.95.44, 69.78.96.14
search domains: local
Still haven't retried the root and may need to wait another day or so until I have some more time
Click to expand...
Click to collapse
These number are from your connected device? What device are you connecting that give you such numbers? I'm not familiar with the iPad and how it displays connection details. Is that what that is from?
I'm still able to connect after updating to GingerVolt1.2 and manually installed 4gHotSpot app. I just got home with little time to work on this project for the night, so I will update what I can if any changes in getting things to work.
-Cybie
those numbers were from an ipad connected via dhcp.
I'll see if I can use a laptop at work today to see the values I get connecting from a laptop. Should be the same I would imagine.
I will retry rooting the stock rom tonight and see what happens.
displacedbuck said:
those numbers were from an ipad connected via dhcp.
I'll see if I can use a laptop at work today to see the values I get connecting from a laptop. Should be the same I would imagine.
I will retry rooting the stock rom tonight and see what happens.
Click to expand...
Click to collapse
Sounds good. Those numbers will help.
I will add, though, that someone posted a way to get the wifi tether to work with the Revolution, here in the forum. The problem, though, is that it's connection via 'n' mode, which would be great, except it drops out. If you try to download something that's fast (or going to speedtest sites), you will find that that happens and what everyone is complaining about the HotSpot app not working. All that needs to be done is changing it to 'g' only mode and a solid connection.
Anyhow, I will see if I can figure out how to get that app working on 'g' only mode also, and if I do, then I will just use that app instead. Otherwise, I plan to continue to figure out the 4gHotSpot App
-Cybie
Cybie,
Glad to see someone's tackling this...I don't suppose your work here could be applied in a way that would make this app work for those who don't pay for the mobile hotspot?
I am waiting on a replacement Revo to arrive in the mail, should be here tomorrow or Saturday. Any values I can pull that might be of use to you before I get happy with flashing roms, rooting, etc?
I find that the OpenDNS nameservers tend to work pretty well everywhere I use them, if you wanted to give them a try:
Primary: 208.67.222.222
Secondary: 208.67.220.220
jamRwoo said:
Cybie,
Glad to see someone's tackling this...I don't suppose your work here could be applied in a way that would make this app work for those who don't pay for the mobile hotspot?
I am waiting on a replacement Revo to arrive in the mail, should be here tomorrow or Saturday. Any values I can pull that might be of use to you before I get happy with flashing roms, rooting, etc?
I find that the OpenDNS nameservers tend to work pretty well everywhere I use them, if you wanted to give them a try:
Primary: 208.67.222.222
Secondary: 208.67.220.220
Click to expand...
Click to collapse
Sorry for the delay. Been working extra hours at work and haven't had the energy to do much with this past couple days.
Anyhow, no, I don't intend to try to get it working for those who do not pay. Why? There are apps out there for this and the only reason I was trying to get this to work properly was for the fact that it would be nice to have the proper connection for those who do pay. I say that because the HotSpot app actually has a faster wifi connection (using n mode) than the tether (root) apps out there, with the exception of the one posted at:
http://forum.xda-developers.com/showthread.php?t=1339150
Unfortunately I am having the same issue with the HotSpot and that app (using infrastructure mode) when connecting. They both to link up at 65Mbps. In fact, I got 72Mbps with the wifi Tether app from the link, but like the HotSpot app, I have issues with the connection dropping out using 'n' mode.
The HotSpot app will allow you to set it to 'g' only mode, though only get a 54Mbps link speed, but sustains a solid connection with no drop outs. Others say they don't have that issue, so it may just be my wifi adapter??? I am going to test it on my laptop, but if I remember, I did have that same issue with the laptop, so maybe it's just my phone??
Either way, I am going to be doing what I can to get 4gHotSpot to work correctly with rooted/modded ROMs. Strange thing is, rooted, it still works fine. After installed modded ROM, it fails to work. And if I restore back to factory rooted via CWM, it still doesn't work. You actually have to restored/flash back to total stock. After that, you can root with it working, but not after installing a ROM.
-Cybie
Any luck with the fix?
OK, so I read that your hotspot worked fine after rooting, but stopped with the ROM was changed.
I rooted my phone yesterday, using the one button method. I have not modified the phone beyond this change. As far as I can tell the only functionality problem I have is with the hotspot.
The tether method continues to work (as I am using it right now). The hotspot does make a wifi connection to my devices but there never is any received data from the network.
Please help, any ideas on what I should look at or change?
Thanks ahead of time.
Steve
ALTANertive said:
Any luck with the fix?
Click to expand...
Click to collapse
I've been doing testing. Please read below for some more of my findings.
sgschwend said:
OK, so I read that your hotspot worked fine after rooting, but stopped with the ROM was changed.
I rooted my phone yesterday, using the one button method. I have not modified the phone beyond this change. As far as I can tell the only functionality problem I have is with the hotspot.
The tether method continues to work (as I am using it right now). The hotspot does make a wifi connection to my devices but there never is any received data from the network.
Please help, any ideas on what I should look at or change?
Thanks ahead of time.
Steve
Click to expand...
Click to collapse
I've noticed something very strange with the HotSpot and Rooting.
If you root, the HotSpot continues to work. But, if you reboot after rooting, that's when the failures begin. So, I am thinking that the files are being overwritten. I've been able to test with clean root, root with tether app, and restore without root.
Without root, the HotSpot continues to work fine as I have been using it for the past two weeks as I need it for my new WiFi Tablet. There is the WiFi app the allows for Infrastructure, but that also allows devices to connect via N-Mode, where I have issues of the data dropping out. Forcing b/g only on my HotSpot app, I have very reliable service.
I am planning (after my trip) to root my phone, copy some DHCP files before ANYthing can be changed and before rebooting. Comparing these files and seeing if anything changes there. If so, that will allow me to create a simple app to restore these files back to stock, either automatically, or through 'starting' of the app.
I haven't forgotten about this issue and It's something that I am needing to figure out. The problem is time right now. For the past few months, I had to work a job in order to keep bills paid. That job took a lot of my hours I used to have to figure things out. I am going to be having limited time available, but do plan to work on it some more in the next few weeks, especially since i want my Tablet to work flawlessly with my phone, as that is my ONLY source of internet and I DO pay for the HotSpot service.
-Cybie
Thanks for the update.
Like you I also pay for the 4g hotspot. I jumped on it when they offered the unlimited for $30.
Now that I've tried the gingervolt rom and the supercharger script I don't think I can go back. It just feels like a totally different phone.
I haven't had as much need for it recently so I haven't tried one of the other tethering apps.
Thanks for plugging along on this.
Yes, thanks for looking at this.
Here is some more observations:
Using your set ip and other setting I can get the hotspot to work. Two of my devices are not able to set a fix address without rooting them. So they do connect but only my PC will download a web page.
Here is the address my Revo is setting on the other two devices: 192.168.16.30 and .31.
Ok, so here's an update to this issue.
I have tracked the problem down to a failure to write to the udhcpd.leases file within the /data/misc/dhcp folder.
So, I did some searches on the net about a few things, but there's not much information regarding the "paid" HotSpot feature vs the (Root) Tether Apps.
What I did comes across, though, is there seems to be some sort of issue with certain versions of busybox relating to the udhcpd.conf. I also found the file that gives the 192.168.16.x addresses. But, by the time I found it, the phone already goofed up the HotSpot app settings and things weren't working. So, next round of factory restoring via LGNPST/Tot, I will seek into that and see what I can find out.
It's weird that the 4g HotSpot app will work flawlessly on the initial boot (Rooted, ROM'd, and even OC'd). But, after a reboot of the phone (once or twice), it becomes corrupted and non-working. It's going to be related to some sort of permissions issue and some file that is able to be corrupted/changed with the root/superuser access. I had similar results with fresh restore and JUST root, so the ROM's have nothing to do with it as far as I am concerned at this point.
In case you might ask. I Refreshed phone to total stock, rooted, and then, all at one shot, installed Gingervolt 1.3, OC, and Hotspot before rooting phone. HotSpot worked fine until the next reboot, where it did work for a few minutes then Kaboom! Nodda.
If someone can access (pull) the /system/var/lib/misc/udhcpd.leases file from a fresh stock phone, or even first-time booted, rooted phone, I would appreciate that as this file may be something in question, but my file was already changed by the time I found it.
-Cybie
I love to help but mine isn't working either. Can you get me started on returning the phone back to stock? I did install a backup util, and ran it first thing after rooting. But I am guessing that wasn't soon enough.
I will take a look at the file I have, I will try the two viewers I have, not sure if they will work.
I did run a restore, and the hotspot did work afterwards. My signal is very weak -110 dBm right now so if you can tell me how to copy/view the file I can get it for you (I did check my tools and could find the file but could not view it, I tried to email it to myself but the encoder couldn't handle it).
By the way, are you aware of a bug in the hotspot, tethering. When you turn off the hot spot and start tethering the hotspot comes back on and tethering will not start. It take a phone power turn to fix it.
sgschwend said:
I love to help but mine isn't working either. Can you get me started on returning the phone back to stock? I did install a backup util, and ran it first thing after rooting. But I am guessing that wasn't soon enough.
I will take a look at the file I have, I will try the two viewers I have, not sure if they will work.
I did run a restore, and the hotspot did work afterwards. My signal is very weak -110 dBm right now so if you can tell me how to copy/view the file I can get it for you (I did check my tools and could find the file but could not view it, I tried to email it to myself but the encoder couldn't handle it).
Click to expand...
Click to collapse
EDIT: When you copy these files, Don't view them until you zip up a copy first. They could potentially get corrupted. not likely, but with the way it's going with this 'project', who knows.
adb pull /data/misc/dhcp datadhcp (This will copy files from phone to a created directory called datadhcp)
Also, and more importantly, this is what I am really wanting:
adb pull /system/var/lib/misc varmisc (copies to created varmisc folder)
AND
adb pull system/etc/dhcpcd dhcpcd (copied to dhcpcd folder)
The created folders and files will be in the same 'dos' directory you have adb in. You can use the folder in which the all in one root is from MT if you are wondering where to get that by any chance.
Those would be a big help in getting thing figured out. At least, if those are the culprits.
NOTE: In order to have non-corrupted files, these have to be pulled from a fresh restore via LGNPST / Tot method. A restore via nandroid backup will not work. those files, once corrupted, seem to remain so, even after a restore for some odd reason, unless you were lucky enough to not have them corrupted prior to backing up, which would likely mean you rooted, rebooted into recovery and backed up before rebooting into your phone.
By the way, are you aware of a bug in the hotspot, tethering. When you turn off the hot spot and start tethering the hotspot comes back on and tethering will not start. It take a phone power turn to fix it.
Click to expand...
Click to collapse
Please clarify on this. Are you referring to starting the 4gHotSpot, shutting it down, and then starting a (root) Tether App??? If so, I haven't really had that issue because once I have to use the root apps to tether with, that usually means my HotSpot won't work at that point. I will say, however, I have had an issue where the HotSpot didn't want to shut down. I just go into Services/App Management and force a shutdown instead of a reboot. A bit quicker....
-Cybie
I will take a run at copying this stuff later today.
On the hotspot bug. Even before rooting, or upgrading to GB there was this bug, and it is still there after GB.
Once the hotspot has been started and then the user shuts it down it appears to shut down. Then the tethering (the application that came with the phone) is initiated it looks like it is tethering but the hotspot icon comes on after the phone has finished tethering and indeed it is running that way too.
I tried this five time last night: Restored the hotspot both application and data (titanium app), installation part of the application would fail but T said it was complete. Launched the application and two of the five times the PC had the correct IP address, the other three times it had the corrupted ones. Also when the PC did come up correctly the second device's IP address was corrupted. So I may need to fiddle a bit to fine the uncorrupted files after restore.
Perhaps someone else could help with copies the files too?
Hello All,
My tethering hasn't worked since the upgrade, regardless of root, method or hack. It appears to set up the network fine and the laptop connects, but I can't pull up a site and troubleshooting points to DNS errors.
So it seems (after loads of research) that this is a known issue... But it's not an issue so much as a "feature" for our carriers: Apparently Jelly Bean allows Carriers to recognize and block tethering. That's why some folks lose tethering, and some don't. The "issue" is a switch that was enabled at the carrier's end.
For those of you who know that you are supposed to be able to tether per your agreement, the solution should be as easy as calling your provider and having them enable tethering.
For those (like me) who have been sneaking in the back door and wish to continue to do so, the fix seems to lie in iptables (root required). The simplest version I found was entering this in terminal:
Code:
su -c "iptables -tnat -A natctrl_nat_POSTROUTING -s 192.168.0.0/16 -o rmnet0 -j MASQUERADE"
...where "rmnet0" is replaced with the interface specific to your device. Apparently after this, one should be able to tether normally.
(Reference Android Google Code reported issue 38563, see comments 122, 125 & 131. Sorry... too noob to be able to post links)
Unfortunately this didn't work for me, but more than likely because I haven't a clue what I'm dabbling in. I sought out my "interface" by running "netcfg" in terminal with tethering disabled, and chose qmi0 (the one with a xx.xxx.xx.xx format IP address, the same as shows for the phone when it's successfully online). Does anyone know enough to see my mistake, or otherwise be able to help me with this?
Thanks in advance!
Actually FoxFi released an update that supports usb tethering and wifi hotspot for the Droid 4. No root required.
You have to uninstall earlier versions of FoxFi and it's certainly worth it to get the paid version!
You do have to establish a password/pattern unlock for your phone which I find slightly annoying, but that's the workaround FoxFi found to make it work under JB and certainly worth the minor inconvenience.
Works great! I am writing this from my tablet tethered through hotspot to my Droid 4.
I had a custom rom installed because I need the wifi hotspot, but now I can thankfully go back to the (extensively TiBu cleaned) stock rom since the CM roms all have unacceptable bugs and/or instabilities IMHO.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Thanks for your response berndblb... I must admit, you got my hopes up!
Alas, it seems my problem runs deeper than FoxFi's solution. I downloaded, installed and gave it a shot, but basically got the same stuff I'd acco mplished already with root: I can build a network, I can connect to it (really adds to the optimism), but I can't reach the DNS server. No joy. My guess is that FoxFi still only manages to bypass Verizon's block, but not the switch that's the problem inherent to JB.
And so I maintain my hope to find a resolution via iptables as described here https://code.google.com/p/android/issues/detail?id=38563.
Help?
Strange, I can tether just fine on my Droid 4 (Verizon) with unlimited data using the SQL database edit and the stock Mobile Hotspot app.
I'm not supposed to have tethering but just browsed the web on my tablet tethered to my Droid 4 with no issues.
Who is your carrier? Every other Verizon Droid 4 owner who has done the SQL edit has been able to tether....
tcrews said:
Strange, I can tether just fine on my Droid 4 (Verizon) with unlimited data using the SQL database edit and the stock Mobile Hotspot app.
I'm not supposed to have tethering but just browsed the web on my tablet tethered to my Droid 4 with no issues.
Who is your carrier? Every other Verizon Droid 4 owner who has done the SQL edit has been able to tether....
Click to expand...
Click to collapse
Thanks for your response.
I'm with Rogers here in Canada (AT&T's counterpart). Agreed about the SQL database edit having been the trick. That's all it took to get me rolling in ICS with the stock hotspot app. When I upgraded to JB, I removed the entitlement check in the SQL database and thought I was set... but no joy. Everything looks good right up until I try to pull up a website. That's when I realize I'm not getting to the DNS Server, and therefore unable to surf. I know nothing's changed on Rogers' end, because I can still tether if I drop my SIM back in my old D2G.
My research led me here: https://code.google.com/p/android/issues/detail?id=38563#c122. Previous comments explain that tethering is now blockable at the carrier's end (what Verizon was attempting to add with their "entitlement check"). Comment 122 narrows down the source of this block as IP address related, and suggests a fix that worked for him. To quote:
I'm not sure exactly what it means for the device to "properly flag when data is for tethering purposes" (comment #105). My own observation was that the outbound data on the 'rmnet0' interface wasn't being NATted. The phone's IP address on that device was (for example) 10.182.48.29 and all its *own* data was coming from that address. And responses from the Internet were coming back just fine.
The phone assigns IP ranges in the 192.168.0.0/16 range to its clients on the USB and wifi tethering. And those 192.168.x.x addresses were being seen on the outbound rmnet0 interface unmolested. Perhaps that's how we're *supposed* to indicate that it's tethered data, and we let the carrier perform NAT for us at their end?
Either way, running this command seems to have 'fixed' it for me, and with my Samsung Galaxy S3 on Orange UK I now get functional tethering again:
su -c "iptables -tnat -A natctrl_nat_POSTROUTING -s 192.168.0.0/16 -o rmnet0 -j MASQUERADE"
Obviously there's nothing preventing your carrier from assigning addresses in the 192.168.0.0/16 range to the device itself, and I have no idea what the various rmnet[012] devices are, so this isn't a "fix" for the general case but most people with a rooted phone should be able to work it out from here...
Click to expand...
Click to collapse
Assuming I'm on the right track (symptoms are the same), I'm looking to figure out how to adapt this to work for me. Unfortunately messing with iptables is well over my head. Sigh...
Yeah i had the same problem FoxFi Worked for me as well
this will forcefully allow tethering no matter what...
If this is over your head, do NOT do it! You can permanently brick your phone!!!
http://forum.xda-developers.com/showpost.php?p=15931904&postcount=1
This goes to the hardware level and mods things to make it look just like your phone is pulling the data not tethering.
Technically this will work on any and every motorola phone
je2854 said:
this will forcefully allow tethering no matter what...
If this is over your head, do NOT do it! You can permanently brick your phone!!!
http://forum.xda-developers.com/showpost.php?p=15931904&postcount=1
This goes to the hardware level and mods things to make it look just like your phone is pulling the data not tethering.
Technically this will work on any and every motorola phone
Click to expand...
Click to collapse
Thanks for your recommendation je2854.
Good news: successfully made the changes, and phone is not bricked.
Bad news: same trouble as before. I can create a network and connect to it, but can't get a DNS server (for either USB tether or WiFi Hotspot).
Really frustrated here. I've reverted to a trashy LG L7 as my primary phone. Slow and no hardware kb, but at least it works. Sigh... Droid 4 going back in the drawer until someone figures out how to rewind to ICS.
Just an FYI about the method posted above.
It is only for legacy 3G CDMA/EVDO devices like the Droid 3 and does not work at all on any LTE capable device with SIM based authentication.
But the good news, as stated by tcrews above, is that wifi tethering works just fine under 4.1.2 using the SQLite Editor entitlement check mod and also
WiFi Tether for Root available in the Play Store works very well under 4.1.2.
Use the Generic JB wlan1 profile and netd-ndc(master) setup method and it works as it always has under previous OS versions.
I am tethered to my D4 right now posting this with the latest cdma_maserati_9.8.2O-72_VZW-18-2_1ff.xml build released a week or so ago flashed on it.
It works!
cellzealot said:
Just an FYI about the method posted above.
It is only for legacy 3G CDMA/EVDO devices like the Droid 3 and does not work at all on any LTE capable device with SIM based authentication.
But the good news, as stated by tcrews above, is that wifi tethering works just fine under 4.1.2 using the SQLite Editor entitlement check mod and also
WiFi Tether for Root available in the Play Store works very well under 4.1.2.
Use the Generic JB wlan1 profile and netd-ndc(master) setup method and it works as it always has under previous OS versions.
I am tethered to my D4 right now posting this with the latest cdma_maserati_9.8.2O-72_VZW-18-2_1ff.xml build released a week or so ago flashed on it.
It works!
Click to expand...
Click to collapse
speaking of flashing... I have purchase one of your OTG adapters.... b-e-a-utiful work you have there!
works amazing! even on the HP TouchPad! (it charges faster like it should)
Also you are correct, I used to have a D3 and that hack works well...
could you kinda point me in the right direction of the SQLite hack? I have that and would like to try it...
(Although I already have tethering enabled via family share)
WaHoo!! Consider yourself kissed!
I'm typing from my tethered laptop. Not sure what did the trick, as I've tried WiFi Tether before with no joy.
I did flash the 18_2 JB, though, and tried the WiFi Tether settings you recommended. Up and running. And grinning.
THANKYOUTHANKYOUTHANKYOU for bringing my Droid4 back out of the drawer it was banished to a couple months ago!
cellzealot said:
Just an FYI about the method posted above.
It is only for legacy 3G CDMA/EVDO devices like the Droid 3 and does not work at all on any LTE capable device with SIM based authentication.
But the good news, as stated by tcrews above, is that wifi tethering works just fine under 4.1.2 using the SQLite Editor entitlement check mod and also
WiFi Tether for Root available in the Play Store works very well under 4.1.2.
Use the Generic JB wlan1 profile and netd-ndc(master) setup method and it works as it always has under previous OS versions.
I am tethered to my D4 right now posting this with the latest cdma_maserati_9.8.2O-72_VZW-18-2_1ff.xml build released a week or so ago flashed on it.
It works!
Click to expand...
Click to collapse
Yay!! Congrats! Glad to help out...D4 is still a great device and for better or worse it is still "best in class" of all the hardware qwerty keyboard phones.
Good luck!
none of above work for me.
verizon build # 9.8.20-72_vzw-18(debloated with script)
entitlement check edit works and keeps thru reboot
sqlite editor (install in play store)
goto:
settings storage: (hammer and wrench icon. says "com.Motorola.Android.providers.settings" below it)
settings:
66 entitlement_check:
long press over the 1, change to 0 and click save
exit and reboot
native hotspot works