Related
I don't have enough posts yet to put this on the developers side, but after digging through a lot of posts, I've pieced together how to tether my CM7 Nook to another android device, and figured a few folks would want to try it as well.
The particulars: On the Nook, I am running the nightly build 31 of CM7.
Whichever phone you want to use has to be rooted, and have the 'wireless tether' app installed. It also has to be able to use bluetooth PAN (as opposed to DUN). I think most android phones do, but my friends blackberry only supports DUN.
First, on the phone: Turn on Bluetooth, and then go to settings>About Phone>Status and write down the bluetooth address, which is six hex numbers separated by colons.
Next, still on the phone, launch wireless tether, and go to the settings page. Check the 'Use Bluetooth' checkbox. Make sure the 'discoverable' checkbox is ticked as well, then go back to the main screen, and press the 'press to start tethering'.
On the Nook, start bluetooth, go to bluetooth settings and scan for devices (if needed); you should see the phone appear on the 'bluetooth devices' list. Pair up with it by clicking on it. Both the Nook and the phone will pop up a PIN dialog, accept that, and you should be seeing 'Paired but not connected' status.
Next, still on the Nook, open a terminal window, and type the following commands (substitute the bluetooth address of the phone you wrote down, INCLUDING THE COLONS in place of the xx's below).
EDIT: before pand, you need root access; use the su command
pand --connect xx:xx:xx:xx:xx:xx
netcfg bnep0 up
netcfg bnep0 dhcp
setprop net.dns1 8.8.8.8
you should now have net access via the tether!
The pand is the configuration demon for the PAN protocol, and that first line ties the bluetooth phone to a network interface named bnep0
The netcfg command activates that interface, and gets an address dhcp'd to it.
and the setprop command sets the DNS (in this case to google's DNS server).
I know many have said they only have limited bluetooth range, but either they have fixed that, or I'm one of the lucky ones, I could still get data on my Nook with the phone almost 30 feet away!
Very cool. Do you notice packet slow down in data speeds the farther you are from the device.
My experience with BT audio is I could not listen to my audio file if I was more than 6" away from my device once I was 12" the signal would drop off/on.
Works well. Now to automate it.
Just did it. Works perfectly! Thanks for the tip. Wonder why the range is so much better tethering than with other accessories. Maybe because the nook is receiving instead of transmitting?
Sent from my NookColor using Tapatalk
Anyone know if this would work with an iphone?
From 1.1 Nook Color with 1.1 ghz overclock
Aw, I had pulled out my Blackberry and was looking up the Mac address before I read that it wouldn't work with Bluetooth DUN. Really cool find though!
This works fine for browsing and a few apps but most of the native apps (email, Gmail, Market, Mapps, etc) do not see a data connection.
Yes, it should work with an iphone; I think I saw some other threads talking about it, I just don't know the steps on the iphone to configure the tethering.
DUN and the blackberry; we need the DUN daemon!
Yeah, a firend of mine has a blackberry and a Nook, and was disappointed that there isn't DUN support (yet).
However, the official open source documentation mentions that there is not only the PAN daemon (pand), but also a DUN daemon, dund. It just isn't included in the cyanogen builds.
I still don't have enough posts to post to the developers side; if anyone could put a request in for dund we might be in business!
As for the range, it seems to be very dependent on what you're tethering to. The tether to the phone last night was a long distance, (the data rate did slow down a bit with distance, to answer the question above, but not badly). But, trying to link to a headset (with mixed success, still working on it), the range wasn't as good. And trying another phone, the range was pretty bad, only a couple of feet.
carrc said:
I still don't have enough posts to post to the developers side; if anyone could put a request in for dund we might be in business!
Click to expand...
Click to collapse
If you have less then 10 posts you can not start a new thread in the Dev section, but you can add a reply to an existing thread.
painter_ said:
If you have less then 10 posts you can not start a new thread in the Dev section, but you can add a reply to an existing thread.
Click to expand...
Click to collapse
I don't think this is correct. I tried to reply to the "CM7 with Honycomb features" thread, but was denied because I have less that 10 posts.
So I trolled a couple of General threads to get my count past 10.
=X=
=X= said:
I don't think this is correct. I tried to reply to the "CM7 with Honycomb features" thread, but was denied because I have less that 10 posts.
So I trolled a couple of General threads to get my count past 10.
=X=
Click to expand...
Click to collapse
I have seen people with less then 10 post in the CM development threads.
Who knows??
carrc said:
Yeah, a firend of mine has a blackberry and a Nook, and was disappointed that there isn't DUN support (yet).
However, the official open source documentation mentions that there is not only the PAN daemon (pand), but also a DUN daemon, dund. It just isn't included in the cyanogen builds.
Click to expand...
Click to collapse
This is very cool! Since I have a BB Curve, I'll have to wait until there is DUN support too, like I do with my iTouch and the BB.
Hi,
I was hoping I could use Bluetooth tethering with my non-rooted Android phone.
There is an application called 'PDANet' in the market with Bluetooth tethering, but
it only does DUN tethering. (free partly functional version, paid full function).
Easytether (market) promises Bluetooth DUN tethering in the future sometime.
In the process of trying to get Bluetooth tethering to work, I
found 'GScript Lite' in the market, very easy way to enter and run shell
scripts like the one on the original post from within Android UI. Looks like
it hasn't been updated to run on tablet, but seemed functional.
Hope this helps someone.
Peter
Has anyone had luck in getting the gmail and email app to work on a bluetooth PAN connection? I can use the web browser and some other apps like USA today but not the email apps.
carrc said:
I don't have enough posts yet to put this on the developers side, but after digging through a lot of posts, I've pieced together how to tether my CM7 Nook to another android device, and figured a few folks would want to try it as well.
The particulars: On the Nook, I am running the nightly build 31 of CM7.
Whichever phone you want to use has to be rooted, and have the 'wireless tether' app installed. It also has to be able to use bluetooth PAN (as opposed to DUN). I think most android phones do, but my friends blackberry only supports DUN.
First, on the phone: Turn on Bluetooth, and then go to settings>About Phone>Status and write down the bluetooth address, which is six hex numbers separated by colons.
Next, still on the phone, launch wireless tether, and go to the settings page. Check the 'Use Bluetooth' checkbox. Make sure the 'discoverable' checkbox is ticked as well, then go back to the main screen, and press the 'press to start tethering'.
On the Nook, start bluetooth, go to bluetooth settings and scan for devices (if needed); you should see the phone appear on the 'bluetooth devices' list. Pair up with it by clicking on it. Both the Nook and the phone will pop up a PIN dialog, accept that, and you should be seeing 'Paired but not connected' status.
Next, still on the Nook, open a terminal window, and type the following commands (substitute the bluetooth address of the phone you wrote down, INCLUDING THE COLONS in place of the xx's below).
EDIT: before pand, you need root access; use the su command
pand --connect xx:xx:xx:xx:xx:xx
netcfg bnep0 up
netcfg bnep0 dhcp
setprop net.dns1 8.8.8.8
you should now have net access via the tether!
The pand is the configuration demon for the PAN protocol, and that first line ties the bluetooth phone to a network interface named bnep0
The netcfg command activates that interface, and gets an address dhcp'd to it.
and the setprop command sets the DNS (in this case to google's DNS server).
I know many have said they only have limited bluetooth range, but either they have fixed that, or I'm one of the lucky ones, I could still get data on my Nook with the phone almost 30 feet away!
Click to expand...
Click to collapse
Thank you for posting this. I just had my NC rooted, running cm7; android 2.3.3 and am looking to get a compatible phone (I have a BB bold). I have asked in a different thread about which phone to get...but I wanted to ask you where I can find the "terminal window" you talk about? I believe I will need to do this myself (after paying $178 for the rooting).
midsouth said:
Thank you for posting this. I just had my NC rooted, running cm7; android 2.3.3 and am looking to get a compatible phone (I have a BB bold). I have asked in a different thread about which phone to get...but I wanted to ask you where I can find the "terminal window" you talk about? I believe I will need to do this myself (after paying $178 for the rooting).
Click to expand...
Click to collapse
Wait, hold on a second... you paid what for someone to root your phone? You paid anything at all, you paid too much, you can do this super easy man. Please tell me that was a typo for $1.78 because you bought the person doing your rooting a cup of coffee. Please!
There is an app/widget for BT PAN tethering now: http://forum.xda-developers.com/showthread.php?t=1032834
Anyone else getting routing issues with android and pptp? I connect and its stable, I get an IP, but it doesnt browse. Every once in about 20 attempts it works for a minute or 2, then stops.
Sent from my DROID3 using XDA App
ive been using ipsec and havent had any routing issues. I may not be fully understanding you, but you are connected to vzw, pptp to a ddwrt, and its not assigning you a local ip?
Maybe an MTU problem. What's the name of the pptp interface?
If you're browsing through a proxy it might not work. I ended up getting an un-NATed public IP address to avoid exactly what is happening to you, for some reason I couldn't connect to anything but my home network when I would connect to my VPN setup at home through my Cisco e4200 w/ dd-wrt firmware. Since I couldnt connect to the mobile browsing proxy when connected to my PPTP VPN, I just avoided it entirely by getting the public IP address... now it works great! (Not to mention I don't have to worry about any ports being blocked by my ISP).
Not sure what VZW's stance is on handing out Public IP addresses but it was pretty easy with Bell Mobility, costs me $5 a month but totally worth it IMO.
Sent from my XT860 using xda premium
disable the encryption. Android is known to have issues with mppe encryption.
Sorry I went MIA family issues. I tried without encryption, same thing. I get an ip. 1/10 time it will route some traffic. But when it does it dies in like 3 minutes MAX. I stay connected, just no data.
Sent from my DROID3 using XDA App
As I said, it sounds like it COULD be an MTU problem. I asked you about the name of your pptp interface before. Try this (as root on command line):
iptables -t mangle -A POSTROUTING -p tcp --tcp-flags SYN,RST SYN -o <YOUR_PPTP_DEVICE_NAME> -j TCPMSS --set-mss 1200
Unknown Arg
I tried what you said, I got unknown arg --set-mss
I have found that I can ping IPs, but not route data any other way.
What a pitty, either the stock iptables command doesn't support it or there is a module missing. That makes it much more difficult. I will try to check it out, but cannot promise you a timeline.
Thank you
Thank you for all you've done already
I fear this tcp-mss is a dead end. A module xt_TCPMSS.ko is needed. I compiled and loaded it, however still doesn't work. I think it it's related to the fact that all stock iptables options are built in the kernel, no modules.
However, I have another idea. Very simple, but could work -- tested it with my D3, looked good. On command line, as root, try this:
ifconfig <YOUR_PPTP_DEVICE_NAME> mtu 1200
That command works, but same problem. I used a different pptp server just in case, same issue, connect, get ip, no browse
Sent from my DROID3 using XDA App
OK, then it's most likely not an MTU problem.
If you want, we can do a little bit more troubleshooting. I love to track down that kind of problems.
Is your busybox installed in /system/xbin? Please type the following commands and provide me with the output:
/system/xbin/ifconfig
/system/xbin/netstat -rn
And we can go a bit farther. Please install the app "Shark for Root" from the market.
Then run your pptp, then open a terminal and type the following command:
/data/data/lv.n3o.shark/files/tcpdump -n -i <YOUR_PPTP_DEVICE_NAME> -w /sdcard/tcpdump.dmp
Try to browse until it fails. Then switch back to the terminal and stop the tcpdump with Ctrl-C.
I need the file /sdcard/tcpdump.dmp, please post it here (it's binary data) or provide it otherwise.
doesn't seem to install
I tried to get shark to install, but nothing seems to work. It appears to die when I try to browse. I can ping though. I've also tried without encryption. I can setup a vnc meeting and you can ADB and play with it if you are down.
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
I was playing with it only for one few hours...
and I am concerned with current level of security of rooted Chromecast.
If you
reboot wireless router(wireless access point)
OR
wireless router is down/malfunction
OR
communication between Chromecast and wireless router is jammed
OR
someone used Aircrack-ng suite to disconnect Chromecast from wireless router
your Chromecast just created open wireless network for configuration purposes...
and Team-Eureka http panel is accessible at most likely default IP address 192.168.255.253,
also provides you with an IP adress via internal dhcp.
look a bit at config:
http://192.168.255.249/?page=status
and than
http://192.168.255.249/?page=settings
be sure that telnet, ssh, adb are running.
Just connect with telnet or SSH, privledged user is root, there is no password
cat /data/wifi/wpa_supplicant.conf
Code:
ctrl_interface=/data/wifi
update_config=1
country=US
network={
ssid="my wifi essid"
scan_ssid=1
psk=my password on a silver plate in WPA PSK HEX(64 characters)
proto=RSN
key_mgmt=WPA-PSK
}
You just owned someone's Chromecast and can abuse his wireless network.
Still got time tinker with Chromecast? Maybe plant some android type of backdoor... NSA style...
How to fix this?
1. be sure that internal web server is not vurnelable.
2. https
3. Http panel accessible only after providing password that is by default for instance sha-1 hash of serial number.
(user may take a picture of his own chromecast and use tool/service to generate hash), it should be changed at first login
4. adb, telnet, ssh disabled by default
5. root password
Basic stuff...
First off, if you are worried about our panels security it is open source, so feel free to audit it for any vulnerabilities.
Also, we are working on a new revision of the panel which not only includes password support, but also the ability to set a SSH password. The reason none is set ATM is because by default the root acc on the chromecast has none, so we have a modified dropbear binary that will allow any password to work.
As for HTTPS over the web panel, that will be available, but it will not be "enforced". (at least that is the current plan). We may add a panel option that enforces https though, for users who are concerned about security on their local wireless network.
Now telnets another story, because its generated with busybox its hard to have a password enforced, but you can just disable it. same goes with ADB.
We know right now our services are not the most locked-down, but trust me most of it has already been fixed on our end and these changes will be out with the next OTA
ddggttff3 said:
First off, if you are worried about our panels security it is open source, so feel free to audit it for any vulnerabilities.
Also, we are working on a new revision of the panel which not only includes password support, but also the ability to set a SSH password. The reason none is set ATM is because by default the root acc on the chromecast has none, so we have a modified dropbear binary that will allow any password to work.
As for HTTPS over the web panel, that will be available, but it will not be "enforced". (at least that is the current plan). We may add a panel option that enforces https though, for users who are concerned about security on their local wireless network.
Now telnets another story, because its generated with busybox its hard to have a password enforced, but you can just disable it. same goes with ADB.
We know right now our services are not the most locked-down, but trust me most of it has already been fixed on our end and these changes will be out with the next OTA
Click to expand...
Click to collapse
Thank you for fast and exhaustive answer.
Any "ETA" of build with features you mentioned ?
Is there any roadmap for Eureka-ROM?
Any chance for something dedicated to LAN streaming?
(Chrome full screen is buggy, Plex is $ app, Fling is written in JAVA and no longer in developement.)
If there will be any beta or rc I am willing to participate.(not so many things to test there)
mathorv said:
Thank you for fast and exhaustive answer.
Any "ETA" of build with features you mentioned ?
Is there any roadmap for Eureka-ROM?
Any chance for something dedicated to LAN streaming?
(Chrome full screen is buggy, Plex is $ app, Fling is written in JAVA and no longer in developement.)
If there will be any beta or rc I am willing to participate.(not so many things to test there)
Click to expand...
Click to collapse
We don't really do ETA's but we try to have updates out right after google OTA's, or when there is a severe bug. As for a roadmap, we currently don't have one public due to it constantly changing.
LAN streaming still works with Fling (as we have fling added back to our roms through our whitelist service), but that is all I know of. If other users want to create apps that can utilize fling, that would be awesome.
And last for testing, currently I have more then enough testers for when beta updates roll out. keep your eyes open in the future as I may do open signups again at a later date.
Well the scenarios you set would apply to non rooted CCasts as well...
If they hacked your wireless with Aircrack to set a disconnect, then you were exposed long before they reconfigured the CCast and they can do a lot more damage with that access without you ever noticing than they could through the CCast.
Your would notice the CCast changing but you wouldn't notice someone hacked your Wireless without looking at the Router Logs or noticing a degraded Network performance.
If these things are a concern for you then I suggest you turn on MAC Filtering on our Router, Set Allows for the CCast and all the devices you own and deny all others.
But the concerns you have exist regardless of a rooted CCast. Leaving a CCast unconnected might expose the CCast to be taken over since it will be an open AP anyone can connect to....And they can Airtcrack you router even with a stock CCast.
But if you see that just look out the window because they would probably have to be sitting on your Porch or parked in your Driveway to do it!
I don't know many Hackers who are THAT Brazen! LOL
Asphyx said:
Well the scenarios you set would apply to non rooted CCasts as well...
If they hacked your wireless with Aircrack to set a disconnect, then you were exposed long before they reconfigured the CCast and they can do a lot more damage with that access without you ever noticing than they could through the CCast.
Your would notice the CCast changing but you wouldn't notice someone hacked your Wireless without looking at the Router Logs or noticing a degraded Network performance.
If these things are a concern for you then I suggest you turn on MAC Filtering on our Router, Set Allows for the CCast and all the devices you own and deny all others.
But the concerns you have exist regardless of a rooted CCast. Leaving a CCast unconnected might expose the CCast to be taken over since it will be an open AP anyone can connect to....And they can Airtcrack you router even with a stock CCast.
But if you see that just look out the window because they would probably have to be sitting on your Porch or parked in your Driveway to do it!
I don't know many Hackers who are THAT Brazen! LOL
Click to expand...
Click to collapse
Reconfiguring stock Chromecast is one thing and that's not so much a problem. Attacker don't get password, just info about name of connected network. In that scenario attacker gets essid and handshakes or reconfigure Chromecast wireless settings(essid/password).
Problem is that with rooted attacker has access to adb/telnet/ssh. In that scenario attacker has easy access to essid/password in plain text and may do this unnoticed.
About ranges:
What if someone lives in center of a city? Skyscrapers area?
About suburban area, I am not convinced that people in US live in houses with brick/concrete block walls, this is not EU.
Have you ever used Aircrack-ng suite and some gnu/linux wireless pentesting distro?
You can attach high gain directional antenna to 2000mW wireless card(Alfa brand for instance) and use software tweaks.
Ranges are much higher than you would anticipate.
About Chromecast setting security - yes it is ridiculous.
It asks if you see XYZ9 on a screen. (always click yes - right?)
It should at least ask for some automatically generated password that is visible on the screen...
So for now we may create additional wireless network/VLAN with max one client and connection restrictions...
mathorv said:
Have you ever used Aircrack-ng suite and some gnu/linux wireless pentesting distro?
You can attach high gain directional antenna to 2000mW wireless card(Alfa brand for instance) and use software tweaks.
Click to expand...
Click to collapse
Yes many times and the loopholes you suggest in your scenario are not limited to the Rooted version at all...
Sure there are extra tools in the rooted version that do not exist in the non-rooted....
But the scenario suggested gives you about 30 seconds to get what you want before the router is back up, CCast re-connects and shuts down your session!
And they still have the problem of how to shut down your router or know when it will happen to start working the hack.
Sure someone could probably get what they want in that timeframe..
But someone that good really is not going to be interested in hacking YOU!
Not Unless your some Cartel leader or Bank Executive.
People who have no business rooting anything if they want security....LOL
Asphyx said:
Yes many times and the loopholes you suggest in your scenario are not limited to the Rooted version at all...
Sure there are extra tools in the rooted version that do not exist in the non-rooted....
But the scenario suggested gives you about 30 seconds to get what you want before the router is back up, CCast re-connects and shuts down your session!
And they still have the problem of how to shut down your router or know when it will happen to start working the hack.
Sure someone could probably get what they want in that timeframe..
But someone that good really is not going to be interested in hacking YOU!
Not Unless your some Cartel leader or Bank Executive.
People who have no business rooting anything if they want security....LOL
Click to expand...
Click to collapse
@but someone that good really is not going to be interested in hacking YOU!
World is full of sick people, besides, over the years it has become easy, primary school kid can do it, every hacking soft has a GUI now
@ features - it would be nice to override wifi from panel - sometimes chromecast indicates connecting status. at the same time is connected to secure wifi and has open configuration wifi.
@ alpha builds, I would be glad to flash anything newer that does not totally brake chromecast and is safer for now
Is web panel risky?
Sorry it's even worse:
1. connect to device if its in open network AP state
2. http://192.168.255.249/?page=debug
3. cat /data/wifi/wpa_supplicant.conf
4. SEND
Gone in less than 30 seconds.
mathorv said:
Sorry it's even worse:
1. connect to device if its in open network AP state
2. http://192.168.255.249/?page=debug
3. cat /data/wifi/wpa_supplicant.conf
4. SEND
Gone in less than 30 seconds.
Click to expand...
Click to collapse
Good thing devices only are in AP mode for setup. Besides, once the new web panel is released, this will be a non issue.