Are any of you experimenting with aethercast?
I understand that officially only the Meizu Pro 5 supports it. But I see here a report of it running on the M 10 and here some development on other devices.
I just tried on my Nexus 7 and I can do
Code:
sudo aethercastctl
show
enable
scan
devices
and this actually finds my android phone with WiFi-Display(miracast) sink, but
Code:
connect <mac-address>
never actually causes anything to show up on the phone display, or any noticeable reaction on the android side at all. I have the feeling that the immediate problem lies in setting up a direct peer to peer wifi connection between the two devices. I see the nexus become unreachable for a moment and I have seen it set up a p2p connection with
Code:
ip addr
but not always and it never went further.
Any ideas?
Aethercast relies on some Android drivers that the 4.4.2 LXC container doesn't have on the Nexus 7. They appear to be working on backporting it, but I haven't seen anything about the N7 yet. We'll likely need to wait until they ship an updated Android system image, but that may not come until either the Xenial or Yakkety transition.
Related
I am having an issue at office. The wifi router seems to be blocking all Android Devices (i.e administrator has intentionally done it) except for PC & Notebook. For example we have a access point with the name of "ROLEX", if i connect to this access point using my android device then it never works but if i try with my notebook then it connects without any issue. We are facing this issue with almost all android devices.
So is it a way to fool the wifi router that my android device is actually a PC and allows me to connect.
fear_matrix said:
I am having an issue at office. The wifi router seems to be blocking all Android Devices (i.e administrator has intentionally done it) except for PC & Notebook. For example we have a access point with the name of "ROLEX", if i connect to this access point using my android device then it never works but if i try with my notebook then it connects without any issue. We are facing this issue with almost all android devices.
So is it a way to fool the wifi router that my android device is actually a PC and allows me to connect.
Click to expand...
Click to collapse
Are you sure the router is specifically blocking android devices? Have you tried connecting an iPhone or just about any other Wifi capable device that's from outside of the office and haven't notified the IT department of? It feels more likely that the IT dept. is simply doing mac address restrictions where only devices with specific mac addressed are allowed to connect to the network.There also could be an inherent compatibility issues between the phones and the router, that there is no actual blocking going on at all.
imzjustplayin said:
Are you sure the router is specifically blocking android devices? Have you tried connecting an iPhone or just about any other Wifi capable device that's from outside of the office and haven't notified the IT department of? It feels more likely that the IT dept. is simply doing mac address restrictions where only devices with specific mac addressed are allowed to connect to the network.There also could be an inherent compatibility issues between the phones and the router, that there is no actual blocking going on at all.
Click to expand...
Click to collapse
I did my homework before positing this. Its blocking all the portable devices like Iphone & Android. I also thought it might be a MAC address restrictions but i did spoofed my MAC address of my Android device but still it doesn't seems to be working. I wonder how that Wifi Router is blocking all the portable devices
fear_matrix said:
I did my homework before positing this. Its blocking all the portable devices like Iphone & Android. I also thought it might be a MAC address restrictions but i did spoofed my MAC address of my Android device but still it doesn't seems to be working. I wonder how that Wifi Router is blocking all the portable devices
Click to expand...
Click to collapse
the only thing I can think of is to find out what make and model router they're using and read the instruction manual/google questions like "blocking mobile devices from network MXHA-281" (MXHA-281 being the model number for example).
Are you manually adding in the SSIDs or are the devices finding the router on their own? If they're finding it on their own and can't connect, not sure what to tell you except to find out if that model router supports such features.
Hey Guys,
first post here, so hopefully i don't do anything wrong
Got myself a Freelander PX1 Tablet with Android 4.2.1. Unfortunately I am stuck while trying to use my phone's internet connection via bluetooth. From what it looks like my android system is missing the Private Area Network PAN client support. (no /system/bin/pand)
Is there any way to 'install' this? As the tablet also does not recognize ad-hoc wifi spots I am unable to go online
Thanks!
Cheers
-Daniel
anyone?
I'm wondering the same thing. I just managed to pair an older Lenovo A1 Gingerbread 2.3.4 with a Galaxy S4 JellyBean/CyanogenMod 10.2 by having them pair, then the phone turn on Bluetooth tether (which Gingerbread doesn't support), and connect to the PAN from the tablet using pand.
This works but it's a complete pain that JellyBean doesn't have pand anymore!? Meaning I can't hope to repeat this with 2 JellyBean devices, only older and newer, or some set of in-the-middle Android versions...
underto said:
I'm wondering the same thing. I just managed to pair an older Lenovo A1 Gingerbread 2.3.4 with a Galaxy S4 JellyBean/CyanogenMod 10.2 by having them pair, then the phone turn on Bluetooth tether (which Gingerbread doesn't support), and connect to the PAN from the tablet using pand.
This works but it's a complete pain that JellyBean doesn't have pand anymore!? Meaning I can't hope to repeat this with 2 JellyBean devices, only older and newer, or some set of in-the-middle Android versions...
Click to expand...
Click to collapse
sorry to hear that at least that means its not my fault^^
Ok! I happen to have this this post open in my browser so I thought I would share in my success, however obvious it is.
I managed to get a hold of a 2nd JB device. I tested this with 2 Samsung S4s. On the "master" device go into settings -> Network More... -> Tethering- > Enable Bluetooth sharing. Don't do this on the other device. Then pair the devices like normal. The end device should automatically tether through the 1st "master" device. You'll see a BT icon with brackets around it in the system tray. The BT icon will be lit blue on both devices.
If you get into the adb shell and have iwconfig around, on both devices you'll see a new network called "bt-pan". The "master" device will be a .1 (e.g. 192.168.40.1) while the "slave" will be given a DHCP address from the "master". (e.g. 192.168.40.124)
The "pand" tool set is not longer needed. You can just pair normally with newer devices. If you're pairing an older Android device that has bluetooth but not the bluetooth tether option in setting, like my Lenovo A1 GingerBread (which I keep for testing), you'll need to manually using pand to setup the PAN. There are apps that will do this for you.
Hope this helps.
I have a Nexus 7 (2013) WiFi tablet flashed with Ubuntu touch, there is much unfamiliar to me as a regular Linux user with this distro.
I have been trying to get the tablet to connect to the Nokai N900(Maemo5 Linux) app QT Mobile Hotspot via wifi, it associates but doesn’t grab from an IP from the DHCP as my Ubuntu laptop does. If I run dhclient in the tablet's terminal it just hangs. Any ideas?
The N900 running QT Mobile Hotspot uses ad-hoc mode to make the connection.
Working in shell with the tablet is a bit of a pain as the replacement touch screen makes typing difficult and SSH apparently doesn't work without tweaking.
I see the same with UT on a MX4 and the n900.
Android out of the box disables connecting to ad-hoc networks. I wonder if UT does the same via a driver inheritance?
What issues do you have with ssh?
"Sent from Ubuntu Touch MX using the Forum Browser app"
handaxe said:
I see the same with UT on a MX4 and the n900.
Android out of the box disables connecting to ad-hoc networks. I wonder if UT does the same via a driver inheritance?
What issues do you have with ssh?"
Click to expand...
Click to collapse
Hey handaxe, same from TMO?
From my research Android can go ad-hoc when rooted, in fact my nexus associates in ad-hoc mode with the N900, just that grabbing an IP address fails. Not sure if the tablet uses dhclient, but that fails when I try it in shell.
I got ssh working askubuntu.com/questions/348714/how-can-i-access-my-ubuntu-phone-over-ssh but it is using public key verification, I go through wipes so often and have such low security needs a password is enough and I hate having to worry about key management, I assume a machine will be compromised and just use crypto on private data. Getting the tablet moved to password verification is probably what I need to bootstrap myself into the next step. There is no good gedit like app and I cant very well VI without having Esc, and Ctrl keys.
As an aside if you know how to get a VNC server running, I had been hoping to use the tablet as a big screen for N900/Maemo apps, especially GPS until the Ubuntu Touch selection expands.
biketool said:
Hey handaxe, same from TMO?
...
As an aside if you know how to get a VNC server running, I had been hoping to use the tablet as a big screen for N900/Maemo apps, especially GPS until the Ubuntu Touch selection expands.
Click to expand...
Click to collapse
The same handaxe....
http://www.unixarea.de/bq/bq-aquaris-e45-ubuntu.txt
Item no 7.
Useful info in that page overall. Installing VNC requires setting the filesystem to rw, thus allowing use of apt-get and .deb installation as opposed to clicks. This disables OTA updates.
I test-ran dhclient as root via ssh whilst connected to a WPA AP, and it did not hang, so I assume that ad-hoc is not supported.
But to get back to the most important topic,
has anyone successfully used tethering from an Ubuntu Touch wifi tablet to any phone with an ad-hoc network link?
Just an update, my research shows that it is possible for a rooted android Nexus 7(flo) to connect via ad-hoc just as the Ubuntu Touch flashed Nexus 7 also already can,
I do get a wifi associate on my Ubuntu N7 and can see the MAC address of the Nokia phone on the other side of the connection.
this problem is only an ubuntu touch DCHP hang issue, the connection to the N900 works automaticly and perfectly when I use my Ubuntu laptop.
I do not see a way to post a bug for core OS issues only official Ubuntu Touch apps.
biketool said:
I do not see a way to post a bug for core OS issues only official Ubuntu Touch apps.
Click to expand...
Click to collapse
Bugs go here.
Actually, they go under the app concerned, it this case I imagine network-manager, but bug admin seems to take care of that.
I searched around on ad-hoc and WEP but found nada.
Hey everyone, I wanted to put together a thread focusing on wifi issues of different variety and what we can do to potentially fix or workaround the main issues
I personally have been working on a solution for the discrepancy that disallows me to connect to my enterprise wifi at work, lollipop and previous versions connect just fine. So far ive found this issue. May not be easiest nor even possible for some of the issues some of us are having, but i think its worth working towards solutions.
https://code.google.com/p/android/i... Owner Summary Stars&groupby=&sort=&id=188867
What wifi issues? You might need nrw router.
I was able to connect via guest, then they had lock it due to bandwidth consumption. I have password since im a supervisor and my other phone (5.1.1) connects just fine. The nexus says saved, but when i click connect nothing, doesnt say obtaining ip or authenticating. Credentials are correct and connected before to same network without lock
meltdeck said:
I was able to connect via guest, then they had lock it due to bandwidth consumption. I have password since im a supervisor and my other phone (5.1.1) connects just fine. The nexus says saved, but when i click connect nothing, doesnt say obtaining ip or authenticating. Credentials are correct and connected before to same network without lock
Click to expand...
Click to collapse
Does your nexus connect fine to other wireless networks? How can you blame it on the device instead of going and fixing your work network settings instead? There are no wifi issues. Call an IT guy and he will fix your router.
meltdeck said:
Hey everyone, I wanted to put together a thread focusing on wifi issues of different variety and what we can do to potentially fix or workaround the main issues
I personally have been working on a solution for the discrepancy that disallows me to connect to my enterprise wifi at work, lollipop and previous versions connect just fine. So far ive found this issue. May not be easiest nor even possible for some of the issues some of us are having, but i think its worth working towards solutions.
https://code.google.com/p/android/i... Owner Summary Stars&groupby=&sort=&id=188867
Click to expand...
Click to collapse
Interesting, I just read through a lot (more than I can believe) of that issue log. It sounds like its technically not a Google/Android 6.0 problem even though the problem arose with the upgrade to 6.0. Have you considered doing what Nick suggested and reaching out to your enterprise IT administrators at work to see if they can or plan to do the necessary updates?
anglerstock said:
Does your nexus connect fine to other wireless networks? How can you blame it on the device instead of going and fixing your work network settings instead? There are no wifi issues. Call an IT guy and he will fix your router.
Click to expand...
Click to collapse
Yeah it connects to others but all devices lollipop and older including iphone and blackberry connect fine. And its known that android m has issues connecting to some wifi that works fine with all other devices. If you do a quick search youll see basically all 6.0 devices (nexus 6, etc) have same issues once updated to 6.0 (hit or miss depends on network they try to connect to, but same story just fine before update). The IT dept are not going to change settings on their network that works fine with 99.9% devices that people have there, since im only one so far with a 6.0 device (IT request MAC address when you get pass) it obviously is some sort of security policy within the os or something of that nature
mlin said:
Interesting, I just read through a lot (more than I can believe) of that issue log. It sounds like its technically not a Google/Android 6.0 problem even though the problem arose with the upgrade to 6.0. Have you considered doing what Nick suggested and reaching out to your enterprise IT administrators at work to see if they can or plan to do the necessary updates?
Click to expand...
Click to collapse
Yeah, they are hesitant to change what works for almost everyone that connects to it. Also i think itd be a good thing to work on since most IT admin wont change for the very few with newer devices
On a side note i do feel like its more or less a cop out of them to claim its not 6.0 fault because when push comes to shove it works fine but once 6.0 it doesn't and nothing changed on the network
When I had my Nexus 5X, I had issues connecting to WiFi at home until I used the Network Settings Reset option under Settings > Backup and Reset. I think this issue came from the restore of settings during initial setup. Possibly worth a try.
Still, the issue I'm running into now is that my 6P only connects to one of the two routers at home. I have both broadcasting the same SSID though they're different brands and one's an older G router. On my Moto X running 5.1, the phone would connect to the strongest signal. Seems the 6P will only connect to one and never connect to the other. I've had the phone "forget" that one and connected to the other and then it refused to connect to the original. Very odd.
My point in saying this is that I wonder if there's a similar issue occurring in the OP's office. Though the same SSID is being broadcast, its as if the phone remembers the MAC address of the specific router it originally connected to and refuses to connect to any others. Just a thought.
Sent from my Nexus 6P using Tapatalk
Have you tried turning on developer options, scroll down and turn on legacy dhcp client under networking.
Yeah, ive tried that also
the fix in this thread might work, if you're rooted.
http://forum.xda-developers.com/google-nexus-5/help/android-m-wpa-enterprise-ssl-problem-t3219559
tcchuin said:
the fix in this thread might work, if you're rooted.
http://forum.xda-developers.com/google-nexus-5/help/android-m-wpa-enterprise-ssl-problem-t3219559
Click to expand...
Click to collapse
Just tried and sadly it didnt work
Tell the IT dept to upgrade their radius auth
I'm also having WiFi connection issues with eduroam (an often used protocol in UK universities) amongst other including my home dual band ac network. It locks out and can only be resolved by a reboot, which then takes 30-60 seconds to power off. Not normal or 'just an admin' issue. It seems to be software related as it is not constant nor predictable (ie it's not in certain areas and a reboot always reconnects). I'm unconvinced by the 'speak to your network admin' argument as it is neither useful or realistic and incompatible on my current patterns of usage or the issues being reported more widely.
My 6p works fine on my wi-fi router at home, but when I go over to my son's house, I have to go into Advanced Wi-Fi options and change the frequency band from automatic to 2.4 GHz only. Then I have to cycle my wi-fi off and back on. Then it will work on his router. Otherwise, it with keep trying to connect and fail every time.
Rob
Yeah, these are the issues (including the issue im having) that im talking about. Theres clearly issues with wifi on 6.0. Its not an issue with the hardware, nor is the solution "buy a new router" or "must be the settings on your companys network" granted most people can connect everywhere they've tried but if they tried where we cant connect or have issues they'd have same problem. Im thinking its a problem due to security policies or something along those lines but we should be able to alter, remove, or opt out of them at our own risk. Just thinking out loud.
Which build are you on? Mine ends in k. See: http://forum.xda-developers.com/showthread.php?t=3248499
Hi,
I just discovered that Android 12 update broke my work VPN connection via Cisco AnyConnect app.
Now AnyConnect is opening only links with IP addresses and won't connect to links with local domains such as mycompany.local/something.
On my other phone that still runs Android 11, everything works great.
I tried to reinstall AnyConnect and to clear data and cache for this app, but that doesn't help at all.
Is this another Android 12 exclusive security feature?
@almirsahbaz
At least since the development of mDNS usage of ".local" domains in environments with some degree of infrastructure aren't suggested anymore (i know that there was a time, the ".local" was proclaimes as a security featurer itself... but times are changeing).
Looking around i found a handful of other posts where problems occured regarding resolving .local domains on android 12.
It might be that Android 12 had made some changes on how to deal with mDNS / .local-Domains. I assume that your company network usually uses "normal" dns. And that's where it get's troublesome.
How ever: As far as i can see you might try to take a look with wireshark or something on your device what actually is going on. Another way would to talk to your IT department. If this is an intended behaviour of Android 12, which i personally assume, then it might have some impact on them and they will need to act sooner or later.