Database Info

[SOLVED] Reverse VNC Connection

-- SOLVED --> For those who care...
Initial issue/goal: Ports open or blocked over 3G/4g? Getting a reverse VNC connection working on an android phone.
Resolution: Ultra VNC SC basically allows someone behind a firewall or router to, without any configuration required, share their desktop with someone (you) for technical support or any other means. I use it for friends and family and such, and it works great, but the real question and purpose of this thread was about open ports on a 3G/4G connection and what VNC apps allow listening. This is what worked for me: Remote VNC Pro from the market (~$6), DynDNS from the market (free), a dynamic DNS account that is supported by the DynDNS application (like no-ip, dyndns, etc), and a personalized/configured version of Ultra VNC SC (linked below). Port 5900 works, as well as a few others, but 80, 8080, and 443 won't.
VNC Application: Remote VNC Pro (for the phone)
VNC Application: Ultra VNC SC (for the client)
Dynamic DNS: DynDNS (update agent)
Mods/Admins feel free to move this thread and/or lock delete if I am breaking any rules (like advertising?) or something.

Re: [HELP] Reverse VNC Connection
I know with 4G you definitely get a publicly accessible IP without any proxy in the middle. I imagine 3G would be the same so it should be fine in that regards.
As for open ports, any app worth its chops should let you choose which port it listens on so that shouldn't be an issue.
Why don't you just buy one of the apps and give it a try? If it doesn't work you can always return it within 24 hours for a full refund.

Trial and Error
---- ORIGINAL FIRST POST ----
Not sure if this should go here or not, but I'm trying to see if I can get a Reverse VNC Application going. Looking at existing VNC applications for Android, the only one that allows listen mode is Remote VNC Pro v1.7.7 and above. Unfortunately, since it is not free, I cannot test the listening capabilities. Listening aside, I suppose my biggest issue will be open ports. Given 3G/4G addresses (NAT, I assume?) are out of our control, does anyone know what ports are open and what ports are not?
Has anyone else tried? Interested? Suggestions? Here's what I have so far:
VNC Application: Looking at Remote VNC Pro (for the phone)
VNC Application: Ultra VNC SC (for the client)
Dynamic DNS: DynDNS (update agent)
---- END FIRST POST ----
rdude said:
Why don't you just buy one of the apps and give it a try? If it doesn't work you can always return it within 24 hours for a full refund.
Click to expand...
Click to collapse
Well the idea was to see if anyone had already tried this and/or had the application to save me time troubleshooting. Since there has been no response, save yours, I went ahead and purchased it.
rdude said:
As for open ports, any app worth its chops should let you choose which port it listens on so that shouldn't be an issue.
Click to expand...
Click to collapse
Oh, it has the option to specify ports, but which ports are open over a 3G/4G connection is what I wanted to know. I tried 443 and 80, and both gave me permission errors. Surprisingly 1723 (PPTP) works, but VNC Pro on the phone just sits on the 'please wait while listening on <ip address>' screen forever. The computer running the Single Click VNC server says that the connection was successfully acquired, but the icon never changes colors (suggesting I am completely connected). The interesting thing is that when I cancel or close the connection on the computer, VNC Pro on my EVO closes the 'listening' window and gives me a java exception error.
*sigh* any ideas? I'm guessing the connection is going through but other traffic is getting blocked or something. Not sure what other ports to try, but I will fiddle around with it in the mean time.
Edit: I tried the standard ports on a local WiFi connection. I gave the phone a static IP, port forwarded everything appropriately, and then received the same results. I'm going to take a few screenshots and send and e-mail to the developer for now.
Edit: It appears to be an issue with Ultra VNC SC. Ultra VNC and Real VNC both worked by manually adding the viewer client from the installed server while using port 5900. Sort of defeats the purpose for me, but the developer said he would try it out and (hopefully) get it working.
Edit: The dev got back to me really quickly and we figured out the issues and fixed it over the weekend. He pushed out a new version of the application on Sunday. First post has been updated for those who care.

Bumping the thread for those who are interested in what worked for me, now that everything is fixed.

Nice, been interested in this. How is the refresh rate when your phone is on WiFi and also how is it on 3G?
I tried Screencast (http://code.google.com/p/androidscreencast/), but it only runs at 3-5 FPS, so it was pretty unusable.

I've only had it working for a day, and nobody has really needed my help, so my testing of the application has only been to confirm it works. The best thing I can say, for now, is that the reviews all brag about the performance and pinch-zoom, that the developer is pretty cool and was willing to return the application well beyond the 24 hour limit, should the application not meet my needs, and finally that he fixed the issue I was having in less than 48 hours from the time I reported it to him. Overall, as far as the application is concerned, I am pretty satisfied. For example, I wrote (and edited) this post while using it over 3G from my phone. I saw all the text as I was typing, so I would say the frame rate is satisfactory.
Edit: Wait, after following your link, I think you might be misunderstanding the purpose of this application. This allows you to control a PC from your Android, not the other way around. The purpose is to supply people with a pre-configured portable application that allows you to connect to the computer without any port forwarding or security changes on their machine. The application (uVNC SC) also "uninstalls" itself from their computer after the connection is closed. To reiterate, the primary benefit is to allow you (the admin) to connect to someone else (the user) without them having to do anything but double-click on your connection.

You're right. I misunderstood, didn't know what "reverse vnc" really meant.

Sorry, I knew people confused the two, so I could have been more clear. On that note, I am also interested in a... remote connection to my Android phone. Recording, in particular, would be great for demo's and setup instructions, given so many people have android devices now-days. But yeah, this is not the setup for that. =/

brennen.exe said:
Bumping the thread for those who are interested in what worked for me, now that everything is fixed.
Click to expand...
Click to collapse
Glad to hear you got it working! I'll try installing it this week and see how it goes.

Looks to me that I want to do exactly the same. Sorry to bump the thread but seems the best thing to do.
I want to support people OTA, since I don't need high framerates, just a view at some PC settings.
I have Remote VNC Pro and it allows the phone to Listen for incoming VNC connections. But it listens on a 10.20.xxx adress, instead of my WAN 3G/4G ip-adress.
I want to use GITSO (awesome little program) for the http://code.google.com/p/gitso/ support issues.
It works flawless pc-to-pc where I have my own portforward setup, saves tons of hassle with the people I want to support.

Bluetooth DUN on CM 7.1.0

Hi all,
I spent a couple of days Googling around, trying to get Bluetooth DUN working on Cyanogenmod 7.1.0 on my Viewsonic GTablet.
After some hacking around with the source, I got it working. I can connect my GTablet to the internet through my Blackberry Torch on Rogers (in Ontario, Canada).
I've already posted my notes to the CM forums, but apparently since I'm a noob here I can't post the link to it, so here's my notes (direct copied from the CM forums):
Dial-up networking requires the chat binary, which is included in the standard Linux ppp package. For some reason, this binary was omitted from the Android ppp package, so I downloaded the Android 2.3.7 source, copied the chat source in to the Android ppp package and built it from scratch. The instructions for this were found at afewe DOT wordpress DOT com/android-arm-development/use-point-to-point-protocol-ppp-in-android/
Once the chat binary is installed in the proper location on the Android device (/system/bin/chat) it's just a matter of writing a pppd config and chatscript for your given provider. These configs can be found in the berry4all package at berry4all DOT com.
I copied the 'rogers' file from that package and put it in /etc/ppp/peers/rogers, then the rogers-chat file and put it in /etc/ppp/chatscripts/rogers-chat.
I modified the /etc/ppp/peers/rogers so that the last line, which calls the chat binary, reflected the proper locations of the binary and the chat script.
Finally, I removed the 'novj' option from the pppd config. Once the config was all up and ready to go, I went to the terminal and did:
$ su
# rfcomm bind /dev/rfcomm0 <BT MAC> <channel>
# pppd call rogers
And voila! A stable, bluetooth dial-up network connection through my phone.
I just wanted to throw out my notes first to make people aware that its possible and easy. If there's enough interest, I'll write a more detailed and specific step-by-step howto on getting it set up.

Hi,
I see that CM 7.1 includes "bluetooth tether" support now but it's not clear to me what this actually is. Does CM 7.1 include the DUN bluetooth profile? It sounds like you're using reverse tethering, i.e. you are using a Blackberry's data connection so you're using the DUN profile on the Blackberry and are using the CM device as a client?
I have a stock Desire S and am looking for DUN support so I can use the internet access in my car through the Desire's 3G connection. The car supports only DUN and PDANet doesn't work for some reason.
Thanks,
Tim

Looks like you're out of luck.... same story for my Benz with Comand Online Navcom system.
If you drive an MB like me, you'll have to wait for an update later this year (from MB that is)... or buy a BlackBerry.
Sent from my GT-P7500 using Tapatalk

Is it confirmed that mercedes benz are providing this update?
Sent from my GT-I9100 using Tapatalk

I very much doubt it (I'm also trying to get it working with Comand Online).
http://telematicsnews.info/2011/08/...connectivity-options-to-comand-online_ag2223/
Not great news.

tj80 said:
I very much doubt it (I'm also trying to get it working with Comand Online).
Click to expand...
Click to collapse
From the press release:
"An option for customers having phones without DUN support is the Mercedes-Benz “Bluetooth (SAP) telephone module - V4″, available early 2012. The new version (V4) offers UMTS capability, allowing fast data connection using customer SIM card or accessing SIM information from SAP (SIM Access Profile) enabled mobile phone."
and:
"... Furthermore Mercedes-Benz is in close talks with leading Android phone vendors to enable the DUN feature in their phones by default."
(I have Android 2.3 and Windows Phone 7.5 devices)

Yes, so we can pay £400 for a SAP module or buy a new phone if anyone actually launches an Android handset with DUN - remembering that Google appear to have zero interest so it will be manufacturer specific. Oh yes, I nearly forgot - Android doesn't have SAP profile support either!
I'd say the chances of Mercedes updating existing systems to work with phones which don't support DUN is virtually zero. Hardly ideal on a system which cost £2000...
Cheers,
Tim

I agree. It was a huge mistake of MB to go with this dead BT DUN protocol!

I thought Android phones do support SAP, isn't that why the car can dial a contact?

agupta80 said:
I thought Android phones do support SAP, isn't that why the car can dial a contact?
Click to expand...
Click to collapse
'fraid not, that uses PBAP (phone book access protocol).

[Q] usb eth0 works but half the apps cant use it

Hi,
Over the past few days I've tried getting my USB Ethernet cable to work with my Tab 2 10.1 running stock ICS 4.0.4
And now I got it up to the point where my PC and my Tab can ping eachother, but that's about it. Get ready for a long and technical read
Now I know Samsung has neglected to include drivers for commonly used USB to Ethernet cables, so I built my own modules to load into the stock kernel (3.0.8-1060237):
drivers/net/mii.ko - Generic Media Independent Interface device support
drivers/net/usb/usbnet.ko - support for usb network
drivers/net/usb/mcs7830.ko - driver for this specific ethernet cable (moschip 7830 based)
Driver depends on support for USB network, USB network depends on support for media independent interface.
So loading these into the kernel using insmod works. After I plug in the cable the kernel tells me:
Code:
[ 3754.987335] MOSCHIP usb-ethernet driver 1-1:1.0: eth0: register 'MOSCHIP usb-ethernet driver' at usb-musb-hdrc-1, MOSCHIP 7830/7832/7730 usb-NET adapter, 00:60:6e:42:32:8f
And even netcfg agrees eth0 exists:
Code:
[email protected]:/ # netcfg
lo UP 127.0.0.1/8 0x00000049 00:00:00:00:00:00
ifb0 DOWN 0.0.0.0/0 0x00000082 26:d8:ae:9d:18:30
ifb1 DOWN 0.0.0.0/0 0x00000082 3e:2c:67:48:bd:92
sit0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
ip6tnl0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
eth0 DOWN 0.0.0.0/0 0x00001002 00:60:6e:42:32:8f
wlan0 UP 130.161.censored/26 0x00001043 1c:66:aa:50:39:ee
[email protected]:/ #
So for testing I put the device on a simple switch with just my PC.
I gave my PC 192.168.1.253 and the tablet 192.168.1.200 (both netmask 255.255.255.0).
Code:
[email protected]:/ # ifconfig eth0 192.168.1.200 netmask 255.255.255.0
And there was much rejoicing:
Code:
Windows:
Reply from 192.168.1.200: bytes=32 time<1ms TTL=64
Android:
64 bytes from 192.168.1.253: seq=32 ttl=128 time=0.733 ms
Now here is the problem: Half the apps trip over this new eth0 network interface.
For instance:
"kWS - android web server" works great, immediately recognizes eth0 and uses it without any problems.
Android Browser crashes the network driver.
SSHDroid starts up thinking it is an ipv6 interface and crashes the network driver on any incoming connections.
Also when I turn off WiFi (regardless if it is connected to a network or not), eth0 is killed too.
Couple of questions:
What am I missing to make Android treat this as a good, normal network interface?
How can I make the modules load when the tablet boots?
How can set the IP adres so I don't have to use ifconfig eth0 192...etc every time I connect the device?
How can I add the eth0 to the settings GUI of Android?
Can installing a different kernel or something like CyanogenMod fix the problem alltogether?
Many thanks in advance for any answers!
If anyone is interested in the modules I compiled please reply, but note they only work on rooted tablets that have stock ICS kernel version 3.0.8-1060237 because of what Linux calls "version magic".
Kind Regards,

Android has Incomplete Eth0 Support...
baggush said:
Hi,
Couple of questions:
What am I missing to make Android treat this as a good, normal network interface?
How can I make the modules load when the tablet boots?
How can set the IP adres so I don't have to use ifconfig eth0 192...etc every time I connect the device?
How can I add the eth0 to the settings GUI of Android?
Can installing a different kernel or something like CyanogenMod fix the problem alltogether?
Many thanks in advance for any answers!
Click to expand...
Click to collapse
Well, he first thing to know is that Android has incomplete Eth0 support!
As you've seen, it's implemented and correct at the Linux level. Which means programs that are written in C++ and either work at the native linux level or bypass the Android framework will work.
However, the Java implementation is busted. It's incomplete.
I'd highly recommend Ben Zores presentation, "Dive Into Android Networking: Adding Ethernet Connectivity" if you want to understand the issues.
(You'll have to google it, I can't post links yet!)
Basically all the Android API gets you is the ability to see that Eth0 exists. You can't talk to it, set it, get notifications on it, etc. because the Service Manager and the Connection Manager framework components are incomplete.
Some implementations, like Android-IA and Cynogen and Linaro have been patched to work, some better than others.
I ran into this the hard way, because I'm implementing a machine control system using Android as a UI and Control Computer. It's a fixed app, not a mobile/tablet thing. And I'm linking to a WAGO Modbus-based fieldbus system for digital and analog I/O and motion control.
Trust me, it's a real headache. I've gotten around it, but there's no official news or support yet.
Regards,
David Schofield, Hotspot Office LLC, Pittsburgh, PA

Galaxy tab 2 eth0 needed
I need to connect an USB to Ethernet to my Galaxy tab 2 7.0 (GT-P3100) or Galaxy tab 3 7.0 (GT-P3200), is there is a way to add the driver without rebuild the rom (like a patch or update) or if there is a custom ROM that supports Ethernet ? Please help me doing this

Ethernet support for Galaxy tab 2.7.0
MJBLACKEND said:
I need to connect an USB to Ethernet to my Galaxy tab 2 7.0 (GT-P3100) or Galaxy tab 3 7.0 (GT-P3200), is there is a way to add the driver without rebuild the rom (like a patch or update) or if there is a custom ROM that supports Ethernet ? Please help me doing this
Click to expand...
Click to collapse
How to say this gently... umm-m-m,
No.
Each manufacturer has configured Android to their liking, and apparently Samsung DOESN'T like Ethernet.
.
I'm doing just as you did, using a Radio Shack Belkin USB interface to connect to industrial equipment (Modbus/TCP PLC's and fieldbus I/O systems.) I've evaluated a number of tablets, including all Samsung tablets (and Nexus, Lenovo, Curtis, and many, many others.) If they don't fully support wired Ethernet, you can't back-fill it without rooting and flashing the ROMs.
(I wish Toshiba would unroot my original Thrive, which they've orphaned.)
In the end, I've bought cheap tablets like some Proscan's (at BigLots, $80USD ) and the 7" Zeki TBDG773B (K-Mart, $119USD) and in testing them, discovered they supported wired Ethernet. (Note that exact models are important, because I've found ROM differences between almost identical models that make the difference between success and failure. Polaroid-branded tablets are infamous for this.)
To test, go to Settings, Wireless & Networks -> Ethernet, (or sometimes, More...-> Ethernet) then switch Ethernet ON, and click Advanced Configuration or sometimes, Configure Ethernet Device. (Polaroids usually fail at this point, they never included the rest of the module.)
My Zeki gives the choice of DHCP vs. Static IP, .IP Address, Netmask, DNS Address and Gateway Address. Proscan gives you DNS1 and DNS2.
I have tested over 80 Android tablets now... Many are tested, few are worthy.
Check out my video on Android-->Ethernet connectivity on YouTube, search for Hotspot Office modbus, or watch video JCMkvHkeNzw, as in /watch?v=JCMkvHkeNzw
I've got specifics and talk about models and equipment and demonstrate stepper motor control using a WAGO fieldbus system.

Thanks
Hotspot Office said:
How to say this gently... umm-m-m,
No.
Each manufacturer has configured Android to their liking, and apparently Samsung DOESN'T like Ethernet.
.
I'm doing just as you did, using a Radio Shack Belkin USB interface to connect to industrial equipment (Modbus/TCP PLC's and fieldbus I/O systems.) I've evaluated a number of tablets, including all Samsung tablets (and Nexus, Lenovo, Curtis, and many, many others.) If they don't fully support wired Ethernet, you can't back-fill it without rooting and flashing the ROMs.
(I wish Toshiba would unroot my original Thrive, which they've orphaned.)
In the end, I've bought cheap tablets like some Proscan's (at BigLots, $80USD ) and the 7" Zeki TBDG773B (K-Mart, $119USD) and in testing them, discovered they supported wired Ethernet. (Note that exact models are important, because I've found ROM differences between almost identical models that make the difference between success and failure. Polaroid-branded tablets are infamous for this.)
To test, go to Settings, Wireless & Networks -> Ethernet, (or sometimes, More...-> Ethernet) then switch Ethernet ON, and click Advanced Configuration or sometimes, Configure Ethernet Device. (Polaroids usually fail at this point, they never included the rest of the module.)
My Zeki gives the choice of DHCP vs. Static IP, .IP Address, Netmask, DNS Address and Gateway Address. Proscan gives you DNS1 and DNS2.
I have tested over 80 Android tablets now... Many are tested, few are worthy.
Check out my video on Android-->Ethernet connectivity on YouTube, search for Hotspot Office modbus, or watch video JCMkvHkeNzw, as in /watch?v=JCMkvHkeNzw
I've got specifics and talk about models and equipment and demonstrate stepper motor control using a WAGO fieldbus system.
Click to expand...
Click to collapse
Thank you for your reply. As you mentioned, there is a way by rooting and flashing, so Where can we find a ready ROM which we can flash to enable Ethernet on Galaxy tab 2 [P3113]?
Also, is there a way to recompile the kernel of Galaxy tab 2 with enabling the Ethernet module from my side? if there is can you advise me how?
Thanks and regards,

Flashing the Galaxy...
MJBLACKEND said:
Thank you for your reply. As you mentioned, there is a way by rooting and flashing, so Where can we find a ready ROM which we can flash to enable Ethernet on Galaxy tab 2 [P3113]?
Also, is there a way to recompile the kernel of Galaxy tab 2 with enabling the Ethernet module from my side? if there is can you advise me how?
Thanks and regards,
Click to expand...
Click to collapse
There are sources on the internet, if you google for "reflash galaxy 2 ROM" but I don't know if they support wired ethernet.
You'll find sites like galaxys2root.com, etc. Biftor is apparently a popular ROM, and ODIN is a popular facility.
It's an involved process, but not impossible. Strict attention to the right instructions will win you success!
Good Providence!
-d

Bump!
Dear Forum,
has there been any development on this topic?
@Hotspot Office -- kudos for the link!
Like Hotspot Office, We have to build a machine GUI based on the P5110. My application will be bypassing the incomplete Android eth0 support
so most probable baggush's approach could work for us but we ar running Cyanogenmod 11 and the Dhollmen kernel.
I still have to get my legs about this whole issue. So any hints and thoughts will be greatly appreciated.
Martin

Functional Eth0, check out my project vid on youtube!
Well, I got things straight, but it wasn't easy.
Check out my project vid featuring a WAGO fieldbus controlling a stepper motor via a functional Eth0 on youtube
You can google for "youtube android modbus" or search youtube for video JCMkvHkeNzw
Or you can plug it into the youtube url, as in /watch?v=JCMkvHkeNzw
The actual title is "Android Tablet Modbus/TCP Stepper-Motor/Robot Exerciser"
If you like it, be sure to thumbs-up it, and leave a comment!
david schofield
dub-dub-dub dot hotspot office dot net

I'm running 4.2.2 so maybe this won't apply, but did you have to do anything in terms of the Ethernet UI in Settings? I've installed the drivers and it looks like the tablet is detecting it, but the Ethernet settings never show up

diimentio said:
I'm running 4.2.2 so maybe this won't apply, but did you have to do anything in terms of the Ethernet UI in Settings? I've installed the drivers and it looks like the tablet is detecting it, but the Ethernet settings never show up
Click to expand...
Click to collapse
Are you running a full 4.2.2, or a stripped down version? What's its pedigree?

Hotspot Office said:
Are you running a full 4.2.2, or a stripped down version? What's its pedigree?
Click to expand...
Click to collapse
I'm not sure, how can you tell?

diimentio said:
I'm not sure, how can you tell?
Click to expand...
Click to collapse
What kind of device is it? Or try Settings, About?
The thing is, if it isn't under "Settings->Wireless and Networks" or whatever, then you don't have it.
-d

Hotspot Office said:
What kind of device is it? Or try Settings, About?
The thing is, if it isn't under "Settings->Wireless and Networks" or whatever, then you don't have it.
-d
Click to expand...
Click to collapse
Well it definitely says 4.2.2 under Settings, About. I have a Samsung Galaxy Tab 2 GT-P5113 model. I don't know what a "stripped down" version is.
I don't have it under Wireless and Networks but in this video (https://www.youtube.com/watch?v=J-RQwQTjraM) the Ethernet option pops up when it detects a valid Ethernet connection. Obviously it's not the same model but I'm wondering whether I need a UI patch or if it should just work out of the box assuming I have all the correct drivers installed.

diimentio said:
Well it definitely says 4.2.2 under Settings, About. I have a Samsung Galaxy Tab 2 GT-P5113 model. I don't know what a "stripped down" version is.
I don't have it under Wireless and Networks but in this video (https://www.youtube.com/watch?v=J-RQwQTjraM) the Ethernet option pops up when it detects a valid Ethernet connection. Obviously it's not the same model but I'm wondering whether I need a UI patch or if it should just work out of the box assuming I have all the correct drivers installed.
Click to expand...
Click to collapse
In my experience, I've found you'd need the *EXACT* same model. I've checked probably a hundred tablets, and found that the specific model and software version, matters. That's why in my video I detail the exact model number. You need to realize that an Android version, say 4.2.2 isn't the same the whole world over. Like Windows XP Embedded, it's a kit of parts. I can burn a version of 4.2.2 with Ethernet support, and I can burn a version of 4.2.2 WITHOUT Ethernet support apps at the Android level. As the developer, I pick and choose what features and applications I include, and which I leave out--which I customize, and which I leave alone.
Sorry, unless you root your device with a version of 4.2.2. that supports the wired Ethernet applications in the settings, you're at the mercy of the Samsung folks.

[Completed] Identifying my Default gateway and DNS (Rooted Turbo)

Hello geniuses, ( and I mean that literally, you guys are amazing) I have Direct TV and just got my hands on there Cinema connection kit witch allows me to connect to an internet source wireless-ly. Anywho, the error I am getting is asking for my default gateway, and my DNS, and that is way over my head. Can anyone assist? I am running a rooted Turbo. Thanks in advance!

Special~k said:
Hello geniuses, ( and I mean that literally, you guys are amazing) I have Direct TV and just got my hands on there Cinema connection kit witch allows me to connect to an internet source wireless-ly. Anywho, the error I am getting is asking for my default gateway, and my DNS, and that is way over my head. Can anyone assist? I am running a rooted Turbo. Thanks in advance!
Click to expand...
Click to collapse
Hello and thank you for using XDA Assist.
It's unclear what Android-related specific problem you have but if by "Turbo" you mean a Verizon Motorola Droid Turbo, there is a forum specifically for questions about that device at http://forum.xda-developers.com/droid-turbo/help where you may want to ask Turbo-related questions.
That said, if the Direct TV device simply needs information about your internet connection, you would need to know the address of your WIFI router (it'll be something like "192.168.0.1") and your default DNS server (maybe "8.8.8.8" for Google DNS?), something whoever installed your internet connection should be able to provide.
If all else fails, try posting with all relevant details in the general forum at http://forum.xda-developers.com/general/general where someone might be familiar with your specific situation.
Good luck!

I appreciate your reply... and yes I was referring to the droid trubo. The internet service I am referring to, however, is my Turbos hotspot. I figured anyone running 4.4 or 5.1, no matter the device could possibly help. I know its possible, and I came very close last night to getting my Direct TV to connect to my phones hotspot. Everything else in my house is connected to my phone, not sure why this won't. I am certain its an address issue, and the default gateway and DNS is the culprit.

Special~k said:
I appreciate your reply... and yes I was referring to the droid trubo. The internet service I am referring to, however, is my Turbos hotspot. I figured anyone running 4.4 or 5.1, no matter the device could possibly help. I know its possible, and I came very close last night to getting my Direct TV to connect to my phones hotspot. Everything else in my house is connected to my phone, not sure why this won't. I am certain its an address issue, and the default gateway and DNS is the culprit.
Click to expand...
Click to collapse
Hello again.
If you are connecting though your phone's hotspot feature, then you have to use its address. That information depends on your phone, ROM and which and how many other devices are on the local network you establish, among other factors, but it's probably in the "198.162.?.?" range mentioned earlier and you can probably set "8.8.8.8" (Google) as your DNS provider. One simple way to determine your default gateway's address is to use whatever other phone, tablet, or computer you connect to that hotspot and execute a "traceroute" command. The first entry will be the gateway. I'm afraid I can't tell you how to do that specifically for your device/OS but most all operating systems have a similar command.
We cannot provide technical support nor can other members reply to your posts here on XDA Assist but, as suggested earlier, asking in the Turbos' Q&A thread at http://forum.xda-developers.com/droid-turbo/help would be the best way to get help
This thread is now closed.
Once again, good luck!

[GUIDE] Using an Android device as a Mumble (murmur) VOIP server. [No Root] Required!

Tutorial version 1.0 by: Talbot *TBOT* Simons “Monsieurtalbot”
WHY?
I was looking around the internet a while ago for a good tutorial on this. Sadly, after many years no one had released one – and after many hours of testing I have managed install and run a mumble (murmur) server - from an Android device using a Debian compatibility layer app called Debian NoRoot. It took a lot of tinkering over a couple years to discover this working method - and it works really well.
There are many benefits to having your own Mumble server… not to mention one that fits in the palm of your hand and can be transported… Not to mention one that can act independently – INCLUDING a built in WIFI network and battery – but using this method, not only is it possible to take a private VOIP server everywhere you go – it’s possible for it to run really smoothly with any mid-range smartphone made after 2012. Broadcast your own WIFI network and connect with friends in a private offline chat within WIFI range…. Or connect to a WIFI network, forward a port from your router and expand the coverage to all of the internet… All with an old android you probably have lying around somewhere. Use it anywhere a walkie talkie might be needed, but not available. Text chat is also included and working – and it’s all as private as possible really… You are even able to encrypt your connection at that point – or simply host it locally and use it anywhere you have a large local network you can tap off of… Hotels & cruises – speak between rooms via the WIFI… etc etc. I can see this being implemented in places where internet is scarce and communication is needed… It will work on devices many people are discarding – and in a world where privacy is becoming scarce – it’s nice to know that the method of your communication is safe.
DISCLAIMER - MUST READ
I am not responsible for any data loss or device damage. Proceed at your own risk, though none of what we’re doing here should be considered risky. I’m not including pictures as I’m a busy man – but the process is quite simple and the instructions are quite exact. I think you’ll be fine.
This has been tested on several Android devices of various screen sizes and processor architectures going back to 4.0. It should work on most if not all devices. An old Android you have sitting in a drawer is a perfect candidate for this – not a bad thing to just keep installed on your personal device as well if you’re a power user like me. The program we’ll be using is able to run most if not all Linux apps … A lot of possibility here. No root is required for most of the features to work in this tutorial. Root isn’t needed if you are on an unlocked device, or if you have tethering provisioned on your wireless account. Tethering is only needed if you plan on using the device to broadcast a WIFI network to make it truly independent from a WIFI router.
Some features of the server may or may not be broken, I personally don’t require much besides a server with no password. If anyone runs into any issues down the road, please let me know!
Click to expand...
Click to collapse
With that being said – let’s begin.
___________________________________________________________________________________
INSTALLATION -
1. Download the following apps from the Play Store on your Android “server device”.
1. Debian NoRoot – The Debian linux environment (takes about 900MB space on internal SD)
2. Plumble – (mumble client) either free or paid version is fine.
3. Fing – Network tools for scanning IPs and networks.
ALSO EITHER:
Stock WIFI hotspot feature (if you have active wireless service)
OR
WIFI Tether Router – (requires root) allows for WIFI networks to be created without a WAN connection.
OR
If you just want a local server hosted and want to use your home router (with or without port forwarding for WAN access to your server) – you can do that too.
Click to expand...
Click to collapse
2. Open the Debian NoRoot app you just downloaded – let it install and set your DPI and font scale to whatever is best for your device. Typically messing with the stock settings won’t do much good for you.
3. Open the terminal that is found on the desktop of Debian, or open it from the menu if your screen is small. Execute the following commands:
sudo apt-get update
(wait for the process to finish - accept any dependencies with Y)
sudo apt-get upgrade
(wait for the process to finish - accept any dependencies with Y)
sudo apt-get install mumble-server
(accept any dependencies with Y – there will be some errors, ignore them.)
sudo dpkg-reconfigure mumble-server
(Autostart: Yes, High Priority: No, Then set the super user password when prompted.)
sudo nano /etc/mumble-server.ini
(This is where you’ll edit the server info – there is much documentation on setting up a mumble server and configuring this file elsewhere on the web… Things like server name, welcome message, server password – etc etc are located in this setting file. Save the file and go back to the terminal.)
sudo /etc/init.d/mumble-server restart
(That’s it, the server should now be running with your new settings in the background. There is no UI and no icons that pop up.)
Click to expand...
Click to collapse
4. Once this is done – keep in mind even though you set the Autostart it is not going to work in this environment – so you will need to manually start the process via it’s script file – so lets create a shortcut to it on the desktop to make starting the server easier.
The script file is located at:
Code:
/usr/bin/murmur-user-wrapper
“Two finger tap” the file and “send to -> Desktop (create link)”
You will now double click this desktop link to start your server after you open the Debian Environment.
5. You can now press the home button to put the Debian environment in the background. Open the “Plumble” app you downloaded *on the same device* and set up a new server with the following settings:
Label : LOCAL SERVER
Address: 127.0.0.1 - leave the port as 64738 or change it as you like.
Username: Whatever you want – I used ADMIN for the server device.
Password: leave blank unless you set it up in the settings file.
Click to expand...
Click to collapse
Once you save the server if should show as online. Connect to it and change the default audio setting to push-to-talk in Plumble settings… If you don’t see it online, restart the phone, or some devices require to be connected to some form of network before the server will show as online. See the next step.
5. Once the server is running you have a number of options on how you can set it up and connect to it. – if you aren’t seeing the server – attempt the following - either step A, B or C first before ripping your hair out.
A. Connect to a WIFI network – set a static IP for your network in Android WIFI settings… You can then use it locally… or you can forward the port you used in the last step to the static IP you set in your router’s settings.
B. Broadcast a stock android hotspot – if you have active wireless service and tethering provisioned or an unlocked device – if you don’t, some custom Android roms will activate and broadcast a network anyway, some won’t… depends on device – your mileage may vary. This is cool for direct device to device communication but will not allow you to use it over the internet. Wireless carriers block a lot of ports incoming.
C. Open WIFI tether router – set it up based on your device. This app requires root but is the most likely to work in a completely offline scenario with no available external WIFI network or when you don’t have service but want to turn a couple phones into walkie talkies in the grocery store. Option B and C are very similar in function but C works with no service – in a plane, a cruise ship, the middle of nowhere, etc etc.
Click to expand...
Click to collapse
6. At this point – we can start connecting other devices… Either get the mumble client for PC/Mac or download “Plumble” and “Fing” on another android device. iPhone also has free mumble clients and network scanners.
7. Open “Fing” on the server device and run a scan if you are on a WIFI router network. Note your server device’s IP address and confirm that the devices you are trying to have connect have an IP address themselves. You may need to run “Fing” or another network scanning app on the secondary device to determine the server device’s IP address… Especially if you are doing this with option B or C for connection.
8. Open Plumble (Android) or your PC/Mac/iOS mumble client and configure it to the server IP you determined in the last step… As long as they are on the same network you should see the server online… Connect and set the push to talk setting on the second device. You should now be able to chat between the server device and the secondary device… and you should be able to connect multiple others as well.
9. Reboot the device.
10. At this point It’s 100% installed and ready to go. The server boot process to recap is quite simple.
- Connect the server device and secondary devices to the same network, hotspot, whatever.
- Open “Debian NoRoot” from a fresh device boot. Sometimes a fresh boot is needed for the server to run properly.
- Once Debian environment is fully loaded, two finger click the shortcut we created for the murmur server and choose the top option – “execute”
-Open Plumble on the server device and connect to the local server profile you created
- Determine the server’s IP address based on how you connected and set up the client devices.
- PROFIT.
Click to expand...
Click to collapse
I hope you enjoyed this tutorial and find it useful – if anyone takes these steps, please help the community and provide screenshots that I may add to this post. The information was sourced and pieced together from so many places… I’d like to thank… Google search - as well as the developers behind the apps used in this tutorial. I'm amazed that after all this time something just clicked and low and behold - it works!
Cheers and best wishes all!

Just an update - this is surprisingly stable, and I have had a server running on an old android device for over 2 weeks with no downtime.

Awesome work! I've been debating trying to port Murmur to Android for a while now as I have an Android STB sitting around that would make a perfect server.

zyperion said:
Awesome work! I've been debating trying to port Murmur to Android for a while now as I have an Android STB sitting around that would make a perfect server.
Click to expand...
Click to collapse
There's already an armhf distro for murmur on debian... This is actually still working great. It's the only reason this works... Same package for the raspberry pi. =]
Any app for Android that allows you to boot I to a chroot Linux environment this will work on...
Sent from my LG-US996 using Tapatalk

Yeah, it's a very clever solution that seems to be working pretty well. I'll have to give it a try! I've also been looking into trying to get Ubuntu installed on my Minix Neo X5 instead since I don't have any need for it as a media box anymore which makes Android far less desirable than a functional Linux install.