Is there a way to disable the wifi direct broadcast while leaving normal wifi/bluetooth operational?
Alternatively, is there a way to switch the channel that wifi-direct is broadcast on?
Currently, it defaults to the same channel that my router is broadcasting on. This is annoying for a number of reasons:
1) My router's signal overpowers my remote and it often takes fiddling to make it reconnect. I switched to a bluetooth solution.
2) Aside from being useless, the wifi-direct signal could potentially be causing wifi interference with my other devices.
3) I live in an apartment complex so wifi overcrowding/noise is already a problem that doesn't need adding to. I'm not using the signal - I may as well turn it off.
I have a rooted fire TV 2 and I'm at least somewhat familiar with adb-shell. I assume there's some config file that I can pull, edit, and push - I just have no idea where it's located.
Been digging into this as well. It keeps causing other devices to loose connection.
@ExaltedVanguard
Fire TV 2 Gen use Wi-Fi Direct for communicate with own remote
Search https://forum.xda-developers.com/fire-tv/general/total-mod-playing-fire-complete-t3629990 (OP and other posts)
Thanks, I found the information I needed in that post. I've condensed the relevant instructions here:
Connect to rooted FireTV via adb
Pull the file /system/etc/permissions/android.hardware.wifi.direct.xml to your computer so you can edit it.
Code:
adb pull /system/etc/permissions/android.hardware.wifi.direct.xml
Comment out the <permissions> group (all 3 lines) by putting a # at the start of each line.
Code:
#<permissions>
# <feature name="android.hardware.wifi.direct" />
#</permissions>
Push the file back to your firetv (somewhere you have write permissions)
Code:
adb push /local/path/android.hardware.wifi.direct.xml /sdcard/android.hardware.wifi.direct.xml
open up adb shell and use the following commands (requires root, you may be prompted to grant permissions on the firetv itself):
Code:
su
mount -o rw,remount /system
cp /sdcard/android.hardware.wifi.direct.xml /system/etc/permissions/android.hardware.wifi.direct.xml
chmod 644 /system/etc/permissions/android.hardware.wifi.direct.xml
chown root:root /system/etc/permissions/android.hardware.wifi.direct.xml
What this does is switch to root, remount the /system drive with read/write (rather than read-only), overwrite the old file with our edited one, and correct the read/write access of the file itself.
Reboot. Watching through wifi analyzer, wifi direct will turn on very briefly during boot, then be disabled.
I have 2 fire sticks with same issues, both are on 6.0.0.2 so no way to be rooted right now. Any other ideas to disable wifi-direct?
It worked!
ExaltedVanguard said:
Thanks, I found the information I needed in that post. I've condensed the relevant instructions here:
Connect to rooted FireTV via adb
Pull the file /system/etc/permissions/android.hardware.wifi.direct.xml to your computer so you can edit it.
Code:
adb pull /system/etc/permissions/android.hardware.wifi.direct.xml
Comment out the <permissions> group (all 3 lines) by putting a # at the start of each line.
Code:
#<permissions>
# <feature name="android.hardware.wifi.direct" />
#</permissions>
Push the file back to your firetv (somewhere you have write permissions)
Code:
adb push /local/path/android.hardware.wifi.direct.xml /sdcard/android.hardware.wifi.direct.xml
open up adb shell and use the following commands (requires root, you may be prompted to grant permissions on the firetv itself):
Code:
su
mount -o rw,remount /system
cp /sdcard/android.hardware.wifi.direct.xml /system/etc/permissions/android.hardware.wifi.direct.xml
chmod 644 /system/etc/permissions/android.hardware.wifi.direct.xml
chown root:root /system/etc/permissions/android.hardware.wifi.direct.xml
What this does is switch to root, remount the /system drive with read/write (rather than read-only), overwrite the old file with our edited one, and correct the read/write access of the file itself.
Reboot. Watching through wifi analyzer, wifi direct will turn on very briefly during boot, then be disabled.
Click to expand...
Click to collapse
Many thanks for the above guide - I joined XDA so I could pass on my gratitude, worked like a charm
Rich LD said:
Many thanks for the above guide - I joined XDA so I could pass on my gratitude, worked like a charm
Click to expand...
Click to collapse
Thanks so much guys for this solution and running through it.
I'm about to attempt the root method on the Fire TV 2 stick that requires shorting pins. Before I do I thought I'd ask and see what the other effects of doing this were. Does your remote still work? Bluetooth was unaffected right? So I assume that even if the wifi remotes stopped working I could get a Bluetooth one and use that. After having done this about a month ago any other unintended consequences?
Thanks
Disable Amazon Fire TV stick Direct WiFi instructions for not a programmer.?
ExaltedVanguard said:
Thanks, I found the information I needed in that post. I've condensed the relevant instructions here:
Connect to rooted FireTV via adb
Pull the file /system/etc/permissions/android.hardware.wifi.direct.xml to your computer so you can edit it.
Code:
adb pull /system/etc/permissions/android.hardware.wifi.direct.xml
Comment out the <permissions> group (all 3 lines) by putting a # at the start of each line.
Code:
#<permissions>
# <feature name="android.hardware.wifi.direct" />
#</permissions>
Push the file back to your firetv (somewhere you have write permissions)
Code:
adb push /local/path/android.hardware.wifi.direct.xml /sdcard/android.hardware.wifi.direct.xml
open up adb shell and use the following commands (requires root, you may be prompted to grant permissions on the firetv itself):
Code:
su
mount -o rw,remount /system
cp /sdcard/android.hardware.wifi.direct.xml /system/etc/permissions/android.hardware.wifi.direct.xml
chmod 644 /system/etc/permissions/android.hardware.wifi.direct.xml
chown root:root /system/etc/permissions/android.hardware.wifi.direct.xml
What this does is switch to root, remount the /system drive with read/write (rather than read-only), overwrite the old file with our edited one, and correct the read/write access of the file itself.
Reboot. Watching through wifi analyzer, wifi direct will turn on very briefly during boot, then be disabled.
Click to expand...
Click to collapse
I've been dying to disable the Direct WiFi being broadcast from my Amazon Tv fire sticks! So mad that there isn't a setting to turn it off! I'm not a programmer...wondering if you could please explain what a rooted FireTV stick is? Thanks!
I have an Amazon fire stick and it shows up as an available wifi connection. It shows DIRECT-7z-FireTV_4ba2. And it says to enter password but I don't know what it is. Does anyone know how to sign into this?
Cathyapn said:
I have an Amazon fire stick and it shows up as an available wifi connection. It shows DIRECT-7z-FireTV_4ba2. And it says to enter password but I don't know what it is. Does anyone know how to sign into this?
Click to expand...
Click to collapse
No idea. it is for a WiFi direct remote. What are you trying to do?
Cathyapn said:
I have an Amazon fire stick and it shows up as an available wifi connection. It shows DIRECT-7z-FireTV_4ba2. And it says to enter password but I don't know what it is. Does anyone know how to sign into this?
Click to expand...
Click to collapse
That wifi connection is for the remote. It's not meant to be signed in.
lol
ExaltedVanguard said:
Thanks, I found the information I needed in that post. I've condensed the relevant instructions here:
Connect to rooted FireTV via adb
Pull the file /system/etc/permissions/android.hardware.wifi.direct.xml to your computer so you can edit it.
Code:
adb pull /system/etc/permissions/android.hardware.wifi.direct.xml
Comment out the <permissions> group (all 3 lines) by putting a # at the start of each line.
Code:
#<permissions>
# <feature name="android.hardware.wifi.direct" />
#</permissions>
Push the file back to your firetv (somewhere you have write permissions)
Code:
adb push /local/path/android.hardware.wifi.direct.xml /sdcard/android.hardware.wifi.direct.xml
open up adb shell and use the following commands (requires root, you may be prompted to grant permissions on the firetv itself):
Code:
su
mount -o rw,remount /system
cp /sdcard/android.hardware.wifi.direct.xml /system/etc/permissions/android.hardware.wifi.direct.xml
chmod 644 /system/etc/permissions/android.hardware.wifi.direct.xml
chown root:root /system/etc/permissions/android.hardware.wifi.direct.xml
What this does is switch to root, remount the /system drive with read/write (rather than read-only), overwrite the old file with our edited one, and correct the read/write access of the file itself.
Reboot. Watching through wifi analyzer, wifi direct will turn on very briefly during boot, then be disabled.
Click to expand...
Click to collapse
What are the consequences of this? Will the remote will work? If yes, what will stop working?
ExaltedVanguard said:
Thanks, I found the information I needed in that post. I've condensed the relevant instructions here:
Connect to rooted FireTV via adb
Pull the file /system/etc/permissions/android.hardware.wifi.direct.xml to your computer so you can edit it.
Code:
adb pull /system/etc/permissions/android.hardware.wifi.direct.xml
Comment out the <permissions> group (all 3 lines) by putting a # at the start of each line.
Code:
#<permissions>
# <feature name="android.hardware.wifi.direct" />
#</permissions>
Push the file back to your firetv (somewhere you have write permissions)
Code:
adb push /local/path/android.hardware.wifi.direct.xml /sdcard/android.hardware.wifi.direct.xml
open up adb shell and use the following commands (requires root, you may be prompted to grant permissions on the firetv itself):
Code:
su
mount -o rw,remount /system
cp /sdcard/android.hardware.wifi.direct.xml /system/etc/permissions/android.hardware.wifi.direct.xml
chmod 644 /system/etc/permissions/android.hardware.wifi.direct.xml
chown root:root /system/etc/permissions/android.hardware.wifi.direct.xml
What this does is switch to root, remount the /system drive with read/write (rather than read-only), overwrite the old file with our edited one, and correct the read/write access of the file itself.
Reboot. Watching through wifi analyzer, wifi direct will turn on very briefly during boot, then be disabled.
Click to expand...
Click to collapse
I followed the above instructions and executed them on rooted firestick (tank). After reboot, it couldn't connect to any wifi network. In fact, under settings>network section, there were no wifi related options. There it was just showing the text as wired ethernet (disconnected). And after I revert to the original xml file, everything returned to normal.
Please let me know, how to disable only the wifi direct and keep the wifi feature as it is.
Related
I noticed this in the Evo forums. The Desire uses the bcm4329 wifi chipset, exactly like the Evo. We should be able to enable Wireless-N using this method. Has anyone tried this already?
http://forum.xda-developers.com/showthread.php?t=707218
Summarised below:
chuckhriczko said:
Update: Thanks to Calkulin there are now flashable zips on my blog post as well as just the driver. Just flash them like any other update.zip file.
So the Evo's WiFi chip supports Wireless N technology, which allows for faster throughput on your WiFi connection. To use this you obviously need a Wireless N capable AP or router. Basically, for some reason (I am going to assume battery life?), HTC decided to disable the wireless n capability of this chip but this can be fixed. Since we don't have the source for the driver we need to use a hex editor. Note, if using AOSP wireless n will already be enabled using the AOSP driver. But if you are using a Sense rom then you will need to do the following. Also I am including a download link with the driver that you can just push if you don't want to get dirty with a hex editor. Anyway, here we go:
1. Download a hex editor (I just googled hex editor and downloaded this one: http://www.chmaas.handshake.de/delphi/freeware/xvi32/xvi32.htm)
2. Go into a command prompt or shell and perform:
Code:
adb pull /system/lib/modules/bcm4329.ko ./bcm4329.ko.old
adb pull /system/lib/modules/bcm4329.ko ./bcm4329.ko
This will pull the file and make a backup in case you need to replace the backup.
3. In your hex editor open the file you just pulled. Now, in two spots HTC added 'nmode' in here to disable Wireless N. All we have to do is modify this string to be any other 5 character string and wireless N will be enabled. I did a search and replace and replaced 'nmode' with '-----' (Note: Do not include the single quotes).
4. Save the file.
5. Perform the following in a command prompt or shell:
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
adb push bcm4329.ko /system/lib/modules/bcm4329.ko
Now wireless N should be enabled on your device. If not, restart it and try. If you ever want to restore your original just perform the following:
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
adb push bcm4329.ko.old /system/lib/modules/bcm4329.ko
.
Below is the download link for the already modified wireless driver.
http://objectunoriented.com/android/?p=35
Click to expand...
Click to collapse
I suspect this was disabled as it puts a further drain on the battery, but I would certainly like to get wireless-n working on my Desire.
Never mind. I just found this was already posted in the development forum.
http://forum.xda-developers.com/showthread.php?t=707516&highlight=wireless-n
Long post but, hopefully an easy answer that someone can walk me through. I have fully rooted my EVO along with the NAND. I'm trying to move/install (?) Power Manager Pro into the /system/app folder to get full rights so it can turn GPS on/off. The website for the app says that I need to do the following:
After root is obtained you need to install the application into the /system/app directory so that it has enough permission to change the location settings. Open a Terminal Emulator app and execute the following command to copy the application to the sdcard (for the full version the name of the application is /data/app/com.acme.android.powermanagerpro.apk):
su
cp /data/app/com.acme.android.powermanager.apk /sdcard/PowerManager.apk
If you can't find the application in /data/app try /data/apps-private/
Then, un-install Power Manager from the device
Execute the following commands in the terminal emulator to remount the /system directory as read/write and to install the application into the /system/app directory:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/PowerManager.apk /system/app
If you prefer to use adb from your computer, execute these commands:
adb remount
adb shell cp /sdcard/PowerManager.apk /system/app
Several users have utilized root explorer from the Google marketplace to simplify this process.
I have Root Explorer so I would like to do it through there is possible, but I can't seem to get it to work without it getting a FC when it opens after trying to move it.
hmmm, it might be force closing because the system is not mounted as read/write. Never used the app before so I dont know. But you can search the market for terminal emulator and then follow the steps the showed above. It looks like it should work.
...or you could do it through adb shell if you are connected to your 'puter
Trying it in Terminal Emulator with no luck... Wondering if the path is right or if i need to change that? It says:
xport PATH=/data/local/bin:$PATH
$su
cp /data/app.acme.android.powermanagerpro.apk /sdcard/PowerManager.apk
cp: not found
the path seems right (I assume you mean export and not xport). I dont think you need anything special on the rom to access cp through terminal emulator...
Have you tried hooking it up to a computer and entering it through adb shell to see if that works?
Someone has managed to connect to an ad-hoc access point? I tried but I failed, also I have not heard of anyone who has achieved
Try the Connectify application to achieve the same thing.
Sent from my HTC Desire using XDA App
This transforms the pc (with windows) in AP, but i want this feature to connect Android phone to other Android phone, [with Wireless Tether] sharing the connection between two phones (really i dont need, but i like to experiment xD)
Thanks for fast reply an sorry for my english
I am also very much interested in this topic for quite a while and i have collected some information about it:
1. Ad-hoc wifi is not a desire specific issue but it affects all devices running android. There is a ticket asking to add it but its just in the state "reviewed" by now. See http://code.google.com/p/android/issues/detail?id=82
2. Some workarrounds exists but they depend on the device beeing addressed.
3. szym.net (author of barnacle wifi-tether) gives a very good explanation why ad-hoc actualy does not work with stock android:
Unfortunately, the WifiManager in stock Android ignores ad-hoc networks.
Click to expand...
Click to collapse
He offers a patch to hack wpa_supplicant which lets ad-hoc networks look like regular access points and thus make them accessable from the phone. See http://szym.net/android/adhoc-wpa-supp.html
HTH
I try your link says, and i try this other pretty way: racheado.blogspot.com/2009/12/conexion-ad-hoc-en-android-posible.html (is in spanish)
but when go to remount in "-ro" the phone resets and don't save the changes.
Also i try this way: ott.net/knowledge/htc-desire-adhoc/ but when go to execute "iwconfig" the "better terminal" or "adb shell" says "permission denied".
And yes, I have root access
ghiki said:
I try your link says, and i try this other pretty way: racheado.blogspot.com/2009/12/conexion-ad-hoc-en-android-posible.html (is in spanish)
but when go to remount in "-ro" the phone resets and don't save the changes.
Also i try this way: ott.net/knowledge/htc-desire-adhoc/ but when go to execute "iwconfig" the "better terminal" or "adb shell" says "permission denied".
And yes, I have root access
Click to expand...
Click to collapse
You can't gain Read/Write access to /System, Read-Only Access.
You can get access in Recovery Mode though.
Unfortunately the fix does not work after boot anyways, due to the /data/misc/wifi/wpa_supplicant.conf being defaulted to not show AdHoc by the original wpa_supplicant.conf in /system after a visit in WiFiManager. I suggest you modify that one instead to always remember your network and settings. Tricky, but works.
Hello to all,
I have just tried to overwrite the wpa file in data/misc/WiFi with the one patched and I changed the name but nothing works!!!
Please help!
Sent from my HTC Desire using Tapatalk
No Answers?
Help us
Found another solution.
Get hold of the iwconfig / ifconfig binaries.
Shut off WiFi first!
Code:
su
insmod /system/lib/modules/bcm4329.ko
iwconfig eth0 mode ad-hoc
and there you go. A interface you're free to do what you like with.
Got it working with my laptop by following up with
Code:
iwconfig eth0 essid [U]ad-hoc_test2[/U]
If coded, use:
Code:
iwconfig eth0 key [B][U]your passkey here[/U][/B]
Then a bunch of stuff for the IP, SubNet, GW, DNS
Code:
ifconfig eth0 [U]192.168.1.10[/U] netmask [U]255.255.255.0[/U]
route add default gw [U]192.168.1.1[/U] dev eth0
setprop net.eth0.dns1 [U]208.67.222.222[/U]
Adjust underlined with your own config.
I need help with this.
First, I should mention that I am a Noob in this, so please be patient.
I have rooted my HTC Desire with unrevoked 3.1 and do get a popup whenever an application is trying to get superuser permissions.
Also, I downloaded the Android SDK and can connect to my device by
Code:
adb devices
adb shell
su
What does not work for me is the
Code:
adb remount
command in the PC command prompt but I managed to mount the system directory rw with
Code:
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
chmod 777 /system/bin
So, when I the try to
Code:
adb push iwconfig /system/bin
I get a
Code:
failed to copy 'iwconfig' to '/system/bin/iwconfig': Out of memory
What is going wrong here?
P.S.: I found also other solutions like http://szym.net/android/adhoc-wpa-supp.html but have no idea how to apply the patch and the linked solution on the same site http://www.olsr.org/?q=olsr_on_android doesn't work either for me, as the used /system/bin/wpa_cli is simply not on my phone.
I am using stock rom Android 2.2 build 2.11.832.2
OMG: why couldn't anyone mention that one needs to boot the phone into recovery to be able to put files into the system directory.
Now it works, I can run iwconfig.
I can see ad hoc networks now but can't connect.
Hi All,
I'm trying to use the custom_backup_list.txt file to preserve my hosts file after a flash of a new nightly.
However, when i put /etc/hosts into custom_backup_list.txt it ignores it and deletes it anyway.
Also, if i use adb and type
adb pull /etc/hosts
or
adb pull /system/etc/hosts
or
adb remount
+ above
It doesn't see the hosts file, i get
"remote object '/etc/hosts' not a file or directory"
which makes me think im getting the path wrong.
If i use File expert and navigate to /etc/ the hosts file is there and populated with adfree updates.
So, what am i doing wrong here?
u have to populate the custom backup list in this way
Code:
etc/hosts
app/TheAppYouwant.apk
...
without the / at the beginnning of each line
about the adb command to save it on ur computer
Code:
adb remount [hit enter]
adb pull /system/etc/hosts C:\TheFolderYouWant\ [hit enter]
(this after 2 minutes searching on google)
andQlimax said:
u have to populate the custom backup list in this way
Code:
etc/hosts
app/TheAppYouwant.apk
...
without the / at the beginnning of each line
about the adb command to save it on ur computer
Code:
adb remount [hit enter]
adb pull /system/etc/hosts C:\TheFolderYouWant\ [hit enter]
(this after 2 minutes searching on google)
Click to expand...
Click to collapse
Well maybe you should have spent longer searching on Google because it doesn't work,, also if you checked my post above you would see i already tried adb pull /system/etc/hosts after adb remount.
In case your wondering , if you don't specify C:\TheFolderYouWant\ etc it assumes pwd (present working directory).
I can for instance pull custom_backup_list.txt from etc by specifying
adb pull /etc/custom_backup_list.txt
with no problem whatsoever, it seems to be specific to hosts.
Can i also ask how you know about
Code:
etc/hosts
app/TheAppYouwant.apk
...
I have other apps in the custom_backup_list.txt file that start /etc/ that are preserved fine which again points to a specific issue with hosts and hence why i think these two point may be connected.
Hello everyone.
I have been able to modify the framework-res.apk file to enable bluetooth tethering for UAMDL from T-Mobile
While I was making the changes in there I also removed from it the call to tethering provisioning and changed the csc files needed too.
So this is for stock UAMDL T-Mobile rooted roms.
I have included the files below to install it if you want.
It does go without saying to backup everything first.
Download from Google Drive
Use the following ADB commands to successfully copy over to the framework folder. Does need to be done via ADB.
Copy new framework-res-mod.apk to root of internal sd card.
adb shell stop (this will cause the screen on your phone to go black that is fine)
adb shell mount -o remount,rw /system
adb shell cp /sdcard/framework-res-mod.apk /system/framework/framework-res.apk
adb shell chmod 644 /system/framework/framework-res.apk
adb shell start (screen will come back on and look like phone is booting again)
after that you can use your favorite root file brower to copy and replace the files customer.xml and feature.xml in the system/csc folder.
If after this you are having problems with getting google play to install apps you might need to master reset.
I want to thank elesbb for help with getting this thing to be able to be compiled and also with the adb instructions to get it copied to the phone without needing a custom recovery but just root.
Awesome man. One question though, so wireless tethering works or only bluetooth tethering?
Yes.
Wireless hotspot, bluetooth (my main goal) and wired tether are working.
Ooops I goofed in the customer.xml file with the APN used for tethering.
I used apn epc.tmobile.com when it should be epc.t-mobile.com
For the time being you can adjust that I will upload a fixed copy tomorrow when I can be at my computer again.
Actually was able to edit and reupload from phone.
It is fixed now.
Apk File not shared for download.
Sorry about that.
Should be fixed.
Give it a try again.
this is what I get
c:\windows-sdk\platform-tools>adb shell stop <<<< phone screen doesnt go black
c:\windows-sdk\platform-tools>adb shell mount -o remount,rw /system
mount: Operation not permitted
c:\windows-sdk\platform-tools>adb shell cp /sdcard/framework-res-mod.apk /system
/framework/framework-res.apk
cp: /system/framework/framework-res.apk: Read-only file system
c:\windows-sdk\platform-tools>adb shell chmod 644 /system/framework/framework-re
s.apk
Unable to chmod /system/framework/framework-res.apk: Read-only file system
am i missing something here?
Sounds like the kernel is not running in insecure mode.
Try installing and enabling insecure adbd with this app and try again
http://forum.xda-developers.com/showthread.php?t=1687590
TheArtiszan said:
Sounds like the kernel is not running in insecure mode.
Try installing and enabling insecure adbd with this app and try again
http://forum.xda-developers.com/showthread.php?t=1687590
Click to expand...
Click to collapse
Thanks man we'll give it a shot after I get off work tonight and let you know how it happens
Sent from my SGH-M919 using xda premium
So far I thought I had bluetooth working on this since it shows as a option in the tethering program but when go to pair with something it does not see or be able to use that profile for internet even though it is enabled on the phone.
Wasn't able to test at the time since I had to send in my tablet but have came to find out that this was not working.
I will continue to try and see what I missed or what I can find.
If anyone has a idea that would be helpful thank you.
Is it possible to implement mod on this Framework mate
http://www.mediafire.com/download/z98oy0q9axmcavv/framework-res.apk