Hey guys when I use wireless tether whenever I set encryption and a password it won't show that the connection is secure when I try to connect. Anyone can connect to it, and it says "unsecured". I really don't like how other people can connect to my connection is there a fix for this?
I have the same issue, the encryption and password settings in the app seem to have no effect and anyone can connect. I have v1.6 running Fresh 1.1 rom.
What seems to work (prob not too secure though) is the access control function in the app, If you enable it and tether your desired PC(s) and check them off in the access control list, when a unrecognized PC connects you get a warning icon in the notification bar.
When I tested it the PC not checked in the access control list could not connect to the internet, even though it had a wireless connection to the phone. So it seems this may help prevent someone else from thethering to your phone.
Same issue here, never found a fix. Just been using Access Control...
You really just need to turn AC on. This way you have to give connections permission to connect. Its a known issue that the password protection is broken. - really kinda useless on an Ad-Hoc anyways, nativly not the most secure thing made.
Don't ask too much from the devs of that app, they have 5+ phones to support all with different issues/methods/kernels. I think its an excelent App for free.
I used Wireless Tether once before and it worked flawlessly. I then changed the SSID and passphrase and now it shows that i'm connected on my laptop, but it won't connect to the internet it takes forever to stop tething and stays running on the backround, so I deleted it. Where do find it to try and redownload it?
durandetto said:
I used Wireless Tether once before and it worked flawlessly. I then changed the SSID and passphrase and now it shows that i'm connected on my laptop, but it won't connect to the internet it takes forever to stop tething and stays running on the backround, so I deleted it. Where do find it to try and redownload it?
Click to expand...
Click to collapse
http://code.google.com/p/android-wifi-tether/
Make sure you download the 1.60 version
Go with v1.70-pre2, it resolves the overheating issue:
android-wifi-tether.googlecode.com/files/wireless_tether_1_70-pre2_htc.apk
Xerxes321 said:
Go with v1.70-pre2, it resolves the overheating issue:
android-wifi-tether.googlecode.com/files/wireless_tether_1_70-pre2_htc.apk
Click to expand...
Click to collapse
Nice! I was reluctant to try it, due to it saying it was for Donut.
kmartburrito said:
Make sure you download the 1.60 version
Click to expand...
Click to collapse
I redownloaded and it still won't recognize my laptop, could it be that I am using a linksys card and don't have internal wireless? Is there a way to manually enter in a computer into the access control?
As in the title, I'm finding it very annoying just to share my phone's wifi connection to my pc via usb tethering. My oneplus 5t just does it, no need for some stupid workaround. The 7 pro is forcing the wifi to disconnect upon enabling tethering. I found a workaround, but i feel like it's just a stupid bug.
The "bug" is going in the hotspot and tethering settings, first having my usb connected. Then enabling usb tethering (it will kill wifi), then turn wifi back on.. Which still leaves usb tethering on. Not an ideal way just to enable wifi tethering..
In most cases you cannot have both WiFi (on the phone itself) and USB tethering activated at the same time. The reason is quite logical from the standpoint of the phone...it generally uses WiFi for its own internet access...at times...and it uses WiFi to share internet access with an external device like a laptop. So the phone can get confused when you use USB tethering to share an internet connection with a laptop and then turn on WiFi also...the phone is not sure what you are trying to do.
jaseman said:
In most cases you cannot have both WiFi (on the phone itself) and USB tethering activated at the same time. The reason is quite logical from the standpoint of the phone...it generally uses WiFi for its own internet access...at times...and it uses WiFi to share internet access with an external device like a laptop. So the phone can get confused when you use USB tethering to share an internet connection with a laptop and then turn on WiFi also...the phone is not sure what you are trying to do.
Click to expand...
Click to collapse
Try VPN hotspot from play store, it allows you to share your Wi-Fi, I use it for that purpose. Use the repeater option, and you can access configuration in the top right corner.
JhinCuatro said:
As in the title, I'm finding it very annoying just to share my phone's wifi connection to my pc via usb tethering. My oneplus 5t just does it, no need for some stupid workaround. The 7 pro is forcing the wifi to disconnect upon enabling tethering. I found a workaround, but i feel like it's just a stupid bug.
The "bug" is going in the hotspot and tethering settings, first having my usb connected. Then enabling usb tethering (it will kill wifi), then turn wifi back on.. Which still leaves usb tethering on. Not an ideal way just to enable wifi tethering..
Click to expand...
Click to collapse
You can't tether your Wi-Fi through USB, and if you figure that out, let me know
jaseman said:
In most cases you cannot have both WiFi (on the phone itself) and USB tethering activated at the same time. The reason is quite logical from the standpoint of the phone...it generally uses WiFi for its own internet access...at times...and it uses WiFi to share internet access with an external device like a laptop. So the phone can get confused when you use USB tethering to share an internet connection with a laptop and then turn on WiFi also...the phone is not sure what you are trying to do.
Click to expand...
Click to collapse
One would use wifi usb tethering when: You want to share an WIFI (as opposed to usually slower Data) internet connection with a computer that has horrible connectivity.
blas4me said:
You can't tether your Wi-Fi through USB, and if you figure that out, let me know
Click to expand...
Click to collapse
The bug part already shows the workaround i had to use to share wifi through USB.
It's annoying to me because the oneplus 5T does it instantly.
No, not wifi. Apparently I can't do auto wifi tethering in Android 11 (my phone) without root on the phone.
I don't want to have to manually enable hotspot every time I get in the car.
Has anyone figured out a way to get the USB or Bluetooth tethering to work on these units?
My phone says USB tethering enabled. I get the notification in the window shade, but nothing on the unit.
What kind of phone? On my Samsung, I use the Bixby stuff which is like Tasker and Macrodroid. It's built-in so I tried it and works well enough. I have a routine that turns on my Wifi hotspot automatically when the phone connects to my car head unit through Bluetooth. The hotspot automatically shuts of when there have been no device connected for a certain amount of time. I think that's an Android setting.
In another thread, it was suggested that this app was working fine and stable:
Bluetooth Tethering Manager - Apps on Google Play
Sharing the internet connection's never been so easy.
play.google.com
That was for a different head unit. Give it a try and let us know how it works.
mastrv said:
What kind of phone? On my Samsung, I use the Bixby stuff which is like Tasker and Macrodroid. It's built-in so I tried it and works well enough. I have a routine that turns on my Wifi hotspot automatically when the phone connects to my car head unit through Bluetooth. The hotspot automatically shuts of when there have been no device connected for a certain amount of time. I think that's an Android setting.
In another thread, it was suggested that this app was working fine and stable:
Bluetooth Tethering Manager - Apps on Google Play
Sharing the internet connection's never been so easy.
play.google.com
That was for a different head unit. Give it a try and let us know how it works.
Click to expand...
Click to collapse
Maybe I'm overthinking it then. The hotspot option seems to work on my phone fairly well. I set it to never timeout . Only connect to my cars MAC address.
However when I connect to wifi it turns the hotspot off. So I have to manually re-enable it.
I tried using macrodroid once before to turn hotspot on when Bluetooth connects, but it doesn't seem compatible with Android 11's security setup.. Without root and tasker.
The Bluetooth tether sort of worked initially. Once I got to driving, it kept cutting off and then eventually stopped giving the HU access at all, even though both servers were running on the phone and unit.
The other Bluetooth tether I've tried didn't work at all
@watson540 When I'm modifying the Bixby routine for turning on my phone's hotspot, it doesn't let me do anything with the wifi connection. It thinks they're related somehow and that wifi should be off when the hotspot is on. In any case, I have wifi off on my phone when my head unit is connected to my phone's hotspot. All works fine.
mastrv said:
@watson540 When I'm modifying the Bixby routine for turning on my phone's hotspot, it doesn't let me do anything with the wifi connection. It thinks they're related somehow and that wifi should be off when the hotspot is on. In any case, I have wifi off on my phone when my head unit is connected to my phone's hotspot. All works fine.
Click to expand...
Click to collapse
That is default Android (look on Android developer). On a hotspot you create a WiFi hotspot and share via mobile data. That is why you can't use WiFi at the same time.
There are very few phones that really can share the WiFi itself. As such this is logical. If there is WiFi, why can't the other phone connect to that WiFi?
It is designed for places where there is no WiFi, but where at least one phone has mobile data which it can share.
That it works differently on Linux, MacOS, ChromeOS and Windows is something else. These devices mostly don't have mobile data at all as they are not phones.
Yes. A phone only has one wifi chip. It can use it to be a client or a server, but not both at once.
That's why enabling hotspot turns wifi off. Enabling wifi turns hotspot off.
The challenge is.. In Android 11 (without Bixby)... How to enable hotspot through some app. Macrodroid can't do it. The app where you create "flows" isn't capable either. I THINK tasker would do it, but only with root from what I previously read. I can't get root because my bootloader is locked.
That's why I was shooting for Bluetooth or USB tether.
It's frustrating because Bluetooth tether in a baked in option in Android 11,as is USB tether.. But the head unit doesn't recognize it or use it.
watson540 said:
The challenge is.. In Android 11 (without Bixby)... How to enable hotspot through some app. Macrodroid can't do it. The app where you create "flows" isn't capable either. I THINK tasker would do it, but only with root from what I previously read. I can't get root because my bootloader is locked.
Click to expand...
Click to collapse
Since 4-5 months I have Samsung A52 on Android 11. Macrodroid just works fine with enabling the hotspot when my phone connects to the head unit on bluetooth. No root necessary. Thanks to the mentioning about Bixby a few days ago, I am now doing it with Bixby Routines, using an old unit on the bench as I am still waiting for my new unit for my "new" car.
With regard to bluetooth tethering to this unit. Already in 2015 lbdroid (who goes under at least 5 synonyms) wrote his blutoothTethering apks. It works with installing the app on your phone AND on the unit. See his github and his blogpost. I have used it on my first and second unit, and purely out of laziness I simply used WiFi tethering on my 3rd and 4th unit.
(And yes, blutooth is spelled correct when I refer to his apk).
Okay, so I got USB tethering to work and it's beautiful- but bittersweet...
It ONLY works if you reboot the head unit with the USB cable already plugged in. Once you take the cable out, it won't come back if you plug back in. Only with a reboot does it work
@surfer63 - you're the guru around here. How can a trigger be made to enable this on a plug-in of USB?, Or maybe a constant poll every thirty seconds?
surfer63 said:
That is default Android (look on Android developer). On a hotspot you create a WiFi hotspot and share via mobile data. That is why you can't use WiFi at the same time.
There are very few phones that really can share the WiFi itself. As such this is logical. If there is WiFi, why can't the other phone connect to that WiFi?
It is designed for places where there is no WiFi, but where at least one phone has mobile data which it can share.
That it works differently on Linux, MacOS, ChromeOS and Windows is something else. These devices mostly don't have mobile data at all as they are not phones.
Click to expand...
Click to collapse
I agree. I believed that it was supposed to work this way where WiFi can't be used while the hotspot is active. However, on my Samsung A51, I can have WiFi and/or mobile data active at the same time as my hotspot. I turn off mobile data and while my phone is connected to my home router through WiFi, I can create a WiFi hotspot. When I've done this, I can still access the internet and my home network from my phone. I have to connect to my 2.4MHz band in order for it to work as a hotspot on my head unit. If I'm connected to the 5MHz band, my phone shows a warning that some clients, that don't support 5MHz, may not be able to connect to the hotspot.
Having the WiFi active while the hotspot is active only causes an issue for me when I'm connected to my home access point. I have a VPN server running on my home router/network. When I VPN from my phone to my home with the WiFi on, I can't access the internet or my home network. I think the routing gets all messed up. In any case, it's not an issue for me...any longer.
I was trying to set up my head unit to access the internet and my home network through the VPN on my phone. I found out that when you use a hot spot (in Android), you cannot access the VPN and the data does not go through the VPN on the hotspot. I don't know why...it may be an Android or a network thing. So, I set up a VPN client on the head unit instead and it connects to my home network fine through the phone hot spot. Now, I just have to figure out how to automatically set up the VPN client on the head unit to automatically connect when it is started and possibly exclude some apps so that the data for those don't go through the VPN.
watson540 said:
Okay, so I got USB tethering to work and it's beautiful- but bittersweet...
It ONLY works if you reboot the head unit with the USB cable already plugged in. Once you take the cable out, it won't come back if you plug back in. Only with a reboot does it work
How can a trigger be made to enable this on a plug-in of USB?, Or maybe a constant poll every thirty seconds?
Click to expand...
Click to collapse
I never looked into lbroid's code for this blutooth apk, but I suppose it should be possible to add some code to check on the "USB device connected" event, and use that to initialize again. (It would of course also require the request for authorization for that USB event).
Or as a workaround: try it from the other side. Install MacroDroid on your unit. Check if a USB device gets connected and at the same time you have BT connection with your phone, and then start the apk on your unit.
Edit: This might require to first stop the app (if running), pause for a few seconds, and then start the app.
watson540 said:
Okay, so I got USB tethering to work and it's beautiful- but bittersweet...
It ONLY works if you reboot the head unit with the USB cable already plugged in. Once you take the cable out, it won't come back if you plug back in. Only with a reboot does it work
How can a trigger be made to enable this on a plug-in of USB?, Or maybe a constant poll every thirty seconds?
Click to expand...
Click to collapse
Sorry. You put me totally on the wrong track.
I simply overlooked you were taliking about USB-tethering. The previous posts were about Bluetooth tetering.
So my answer might still be interesting for those who want Bluetooth tetering: See also my github where I rebuilt lbdroid's version (nov 2019) with an apk in the releases section.
Nothing creative. Just a copy with an extended readme.
surfer63 said:
Sorry. You put me totally on the wrong track.
I simply overlooked you were taliking about USB-tethering. The previous posts were about Bluetooth tetering.
So my answer might still be interesting for those who want Bluetooth tetering: See also my github where I rebuilt lbdroid's version (nov 2019) with an apk in the releases section.
Nothing creative. Just a copy with an extended readme.
Click to expand...
Click to collapse
I'll take either/or
It appears that my phone doesn't start USB tethering until I unlock it anyway. So it may HAVE to be Bluetooth... which is fine
I did try macrodroid on the HU to try and trigger the USB tether action.
I looked into the logcat and saw some tethering events going on when I plugged the cable in. They get shut down for whatever reason.
I was able to bring the usb0 interface up with a simple ifconfig command in terminal, but no way to assign it an ip and routing (dhcpcd or dhclient) -- Android is just so far removed from Linux anymore, it's all handled in JAVA now, so I can't just write a shell script
I'll look into the Bluetooth method again
surfer63 said:
So my answer might still be interesting for those who want Bluetooth tetering: See also my github where I rebuilt lbdroid's version (nov 2019) with an apk in the releases section.
Nothing creative. Just a copy with an extended readme.
Click to expand...
Click to collapse
I mentioned that I had not looked at lbdroid's blutooth apk, but obviously I have. I simply completely forgot about it. Time flies and so do my memories.
surfer63 said:
I mentioned that I had not looked at lbdroid's blutooth apk, but obviously I have. I simply completely forgot about it. Time flies and so do my memories.
Click to expand...
Click to collapse
It looks promising. Doesn't work on this unit though.
I assume it's because fyt 7862 actually has 2 Bluetooth chips, and the first one is disabled. I guess it's spotty? I reckon the app is trying to attach to the primary Bluetooth, which is disabled through the rom?
watson540 said:
It looks promising. Doesn't work on this unit though.
I assume it's because fyt 7862 actually has 2 Bluetooth chips, and the first one is disabled. I guess it's spotty? I reckon the app is trying to attach to the primary Bluetooth, which is disabled through the rom?
Click to expand...
Click to collapse
I don't know. At this moment I do not have a uis7862 and can't examine it.
surfer63 said:
I don't know. At this moment I do not have a uis7862 and can't examine it.
Click to expand...
Click to collapse
Looks like this app was built for a previous version of Android
BluetoothAdapter mBluetoothAdapter = BluetoothAdapter.getDefaultAdapter();
getDefaultAdapter has been deprecated since jellybean. I'd plug in the appropriate call, but I'm assuming that would just be the beginning of a whole host of other things to rewrite as well.
I'm not that dedicated
watson540 said:
Looks like this app was built for a previous version of Android
BluetoothAdapter mBluetoothAdapter = BluetoothAdapter.getDefaultAdapter();
getDefaultAdapter has been deprecated since jellybean. I'd plug in the appropriate call, but I'm assuming that would just be the beginning of a whole host of other things to rewrite as well.
I'm not that dedicated
Click to expand...
Click to collapse
It was built for Android 5/6.
Since Android 7 and 8, many things have changed. In the access rights area, in the "run as a service" area, etcetera. It might require a complete rewrite.
watson540 said:
I assume it's because fyt 7862 actually has 2 Bluetooth chips
Click to expand...
Click to collapse
Why do you think that?
In all the specs I can find it has only one BT chip being the Realtek 8761BTV (but again: only from theory).
surfer63 said:
Why do you think that?
In all the specs I can find it has only one BT chip being the Realtek 8761BTV (but again: only from theory).
Click to expand...
Click to collapse
I've seen it in my convoluted perusing. If you look on 4pda, people there talk about activating one or the other in build.prop or some other system related file.
I've seen what I believe is it in the Android settings (the real settings). It's named "carbt". I managed to connect my phone to it once. I never checked any hardwire IDs to verify it was indeed different, but I swear I've seen it mentioned over there. It's up to 384 pages now, so it's hard to keep up