Greetings
I have a Nexus 7 (wifi only) with JB 4.2.1 and I'd like to know if there is any custom rom or kernel that supports ad hoc connections, I want to connect the N7 to joikuspot on my nokia 808.
BTW I already tried bluevpn and not all android apps supports it, and already got connectify-me on my desktop computer, I need to connect the N7 with my phone since I travel very often and not everywhere I can find wifi spots.
Thank you in advance
CARUPANBOW said:
Greetings
I have a Nexus 7 (wifi only) with JB 4.2.1 and I'd like to know if there is any custom rom or kernel that supports ad hoc connections, I want to connect the N7 to joikuspot on my nokia 808.
BTW I already tried bluevpn and not all android apps supports it, and already got connectify-me on my desktop computer, I need to connect the N7 with my phone since I travel very often and not everywhere I can find wifi spots.
Thank you in advance
Click to expand...
Click to collapse
Hello? anyone can help me out?
Ad Hoc for Nexus 7
First, being a noob I want to say thanks for all the great info provided on this forum. It's a big help to someone like me who's just learning.
CARUPANBOW,
I need this also. I’ve spent several hours searching for a solution and have found nothing. It’s already been discussed here http://forum.xda-developers.com/showthread.php?t=1787680&page=7 on XDA so maybe that why no one has responded. The links below are to other discussions about this, but so far I have not found a way to force my Nexus 7 to connect to an Ad Hoc network. I’m still hopeful.
http://www.thriveforums.org/forum/t...ment/15959-ad-hoc-patch-3-x-4-0-4-1-cm10.html
http://www.pcadvisor.co.uk/how-to/google-android/3372947/connect-android-phone-ad-hoc-network/
http://szym.net/2010/12/adhoc-wifi-in-android/
https://bugs.launchpad.net/ubuntu-nexus7/+bug/1077704
Maybe someone that’s really experienced can use the information in the links and find a solution.
Thanks,
Ken
Thank you
emgo said:
First, being a noob I want to say thanks for all the great info provided on this forum. It's a big help to someone like me who's just learning.
CARUPANBOW,
I need this also. I’ve spent several hours searching for a solution and have found nothing. It’s already been discussed here http://forum.xda-developers.com/showthread.php?t=1787680&page=7 on XDA so maybe that why no one has responded. The links below are to other discussions about this, but so far I have not found a way to force my Nexus 7 to connect to an Ad Hoc network. I’m still hopeful.
http://www.thriveforums.org/forum/t...ment/15959-ad-hoc-patch-3-x-4-0-4-1-cm10.html
http://www.pcadvisor.co.uk/how-to/google-android/3372947/connect-android-phone-ad-hoc-network/
http://szym.net/2010/12/adhoc-wifi-in-android/
https://bugs.launchpad.net/ubuntu-nexus7/+bug/1077704
Maybe someone that’s really experienced can use the information in the links and find a solution.
Thanks,
Ken
Click to expand...
Click to collapse
Thank you very much for answering my post, I'm a noob too and besides I felt ignored, I have to confess this is my first android device, and I have spent many hours too to figure out a solution.
I checked the post you mentioned, some of those websites too and also checked the android issues #82 and #35629 at code.google.com
So far i've been able to connect to my nokia 808 via joikuspot, but like in bluevpn some apps are not working, here is what I did:
1) I have the JB 4.2.1 rooted on my device
2) I downloaded this kernel and applied it https://github.com/monk-dot/SPAN/blob/master/kernels/ASUS%20Nexus%207/myupdate-nexus7.zip
3) Since the nexus stock rom doesn't include the wpa_cli command I found this one http://pic-e-bank.com/android/Droid/Kernels/Froyo/Slayher/slayher_wifi_fix.zip Extracted the file and copied it into the folder /system/bin (set permissions to 755).
4) Found this patched wpa_supplicant file from this post "[JB] wpa_supplicant for adhoc wifi networks" and copied it into the folder /system/bin (made a backup first of the original file and set the permissions of the new wpa_supplicant to 755).
5) With a terminal app (using adb also works) I followed this guide: http://www.olsr.org/?q=olsr_on_android to set up the ad hoc network to my nexus 7 manually.
And Eureka! I could connect my nexus to my nokia 808 hotspot, however I couldnt see any infrastructure networks anymore, the solution was to revert back to the original wpa_supplicant, so I'm thinking about making two command scripts to set up my ad hoc connection and revert it back whenever I need to connect to a different network (you can check this guide).
BTW, there are some custom roms that include the wpa_cli command, but I tried some of them and they didn't detect my hotspot until I replace the wpa_supplicant file with the patched one.
I'm no android expert but I think the problem with ad hoc connections is a kernel/wpa_supplicant issue, i guess at some point google decided to take out the support for IBSS networks, however the linux kernel still supports it, i really wish some expert could take a look into it.
I hope you find this info useful, but this is not a final solution and I'll still work into it whenever I can.
Ad Hoc for Nexus 7
CARUPANBOW said:
Thank you very much for answering my post, I'm a noob too and besides I felt ignored, I have to confess this is my first android device, and I have spent many hours too to figure out a solution.
I checked the post you mentioned, some of those websites too and also checked the android issues #82 and #35629 at code.google.com
So far i've been able to connect to my nokia 808 via joikuspot, but like in bluevpn some apps are not working, here is what I did:
1) I have the JB 4.2.1 rooted on my device
2) I downloaded this kernel and applied it https://github.com/monk-dot/SPAN/blob/master/kernels/ASUS%20Nexus%207/myupdate-nexus7.zip
3) Since the nexus stock rom doesn't include the wpa_cli command I found this one http://pic-e-bank.com/android/Droid/Kernels/Froyo/Slayher/slayher_wifi_fix.zip Extracted the file and copied it into the folder /system/bin (set permissions to 755).
4) Found this patched wpa_supplicant file from this post "[JB] wpa_supplicant for adhoc wifi networks" and copied it into the folder /system/bin (made a backup first of the original file and set the permissions of the new wpa_supplicant to 755).
5) With a terminal app (using adb also works) I followed this guide: http://www.olsr.org/?q=olsr_on_android to set up the ad hoc network to my nexus 7 manually.
And Eureka! I could connect my nexus to my nokia 808 hotspot, however I couldnt see any infrastructure networks anymore, the solution was to revert back to the original wpa_supplicant, so I'm thinking about making two command scripts to set up my ad hoc connection and revert it back whenever I need to connect to a different network (you can check this guide).
BTW, there are some custom roms that include the wpa_cli command, but I tried some of them and they didn't detect my hotspot until I replace the wpa_supplicant file with the patched one.
I'm no android expert but I think the problem with ad hoc connections is a kernel/wpa_supplicant issue, i guess at some point google decided to take out the support for IBSS networks, however the linux kernel still supports it, i really wish some expert could take a look into it.
I hope you find this info useful, but this is not a final solution and I'll still work into it whenever I can.
Click to expand...
Click to collapse
That’s great! At least you have provided something that works. It’ll take me some time to replicate what you did. I am going give it a try.
Thanks,
Ken
Thank you very much
Also I found out the networks settings are stored in /data/misc/wifi/wpa_supplicant.conf instead of /system/etc/wifi/wpa_supplicant.conf
reading this post Edit wpa_supplicant.conf instead of wpa_supplicant I managed to manually edit my ad hoc network settings, so the wpa_supplicant.conf would be like this
Code:
ap_scan = 2
network={
ssid="JOIKUSPOT"
scan_ssid=1
priority=10
mode=1
wep_key0="12345"
key_mgmt=NONE
}
And you have to give the ownership back to system.wifi using abd/terminal:
Code:
#chown system.wifi data/misc/wifi/wpa_supplicant.conf
For now im trying some customs roms to see if they can detect the ad hoc network out of the box, but so far I can only do it by replacing the wpa_supplicant and flashing the custom kernel from my previous post.
I'll keep posting my findings and try some other custom kernels as well.
So far this is what I got
Hi
So far this is my method to get (partial) ad hoc support for my N7 (wifi):
1) Start by rooting your device (you can use the Nexus 7 Root Toolkit).
2) Install CWM Recovery so you can install custom kernels.
3) Download and install this kernel https://github.com/monk-dot/SPAN/blob/master/kernels/ASUS%20Nexus%207/myupdate-nexus7.zip
4) Download and copy this wpa_supplicant file http://forum.xda-developers.com/showthread.php?t=1806937 into the /system/bin folder, be sure to set your wifi connection off, make a backup of the original file and after copying the file check the permissions to be 755
5) Create a text file with the following commands:
Code:
wpa_cli -p/var/run/wpa_supplicant scan
wpa_cli -p/var/run/wpa_supplicant scan_results
wpa_cli -p/var/run/wpa_supplicant remove_network 0
wpa_cli -p/var/run/wpa_supplicant ap_scan 2
wpa_cli -p/var/run/wpa_supplicant add_network
wpa_cli -p/var/run/wpa_supplicant set_network 0 ssid '"JOIKUSPOT"'
wpa_cli -p/var/run/wpa_supplicant set_network 0 scan_ssid 1
wpa_cli -p/var/run/wpa_supplicant set_network 0 frequency 2412
wpa_cli -p/var/run/wpa_supplicant set_network 0 mode 1
wpa_cli -p/var/run/wpa_supplicant set_network 0 group WEP40
wpa_cli -p/var/run/wpa_supplicant set_network 0 key_mgmt NONE
wpa_cli -p/var/run/wpa_supplicant set_network 0 wep_key0 '"12345"'
wpa_cli -p/var/run/wpa_supplicant set_network 0 wep_key1 12345
wpa_cli -p/var/run/wpa_supplicant set_network 0 wep_tx_keyidx 0
wpa_cli -p/var/run/wpa_supplicant save_config
wpa_cli -p/var/run/wpa_supplicant reconfigure
wpa_cli -p/var/run/wpa_supplicant enable_network 0
wpa_cli -p/var/run/wpa_supplicant select_network 0
Replace JOIKUSPOT with the ssid of your ad hoc network and set your password on the wep_key0 and wep_key1 variables, if you are using an open network just delete this lines:
Code:
wpa_cli -p/var/run/wpa_supplicant set_network 0 wep_key0 '"12345"'
wpa_cli -p/var/run/wpa_supplicant set_network 0 wep_key1 12345
wpa_cli -p/var/run/wpa_supplicant set_network 0 wep_tx_keyidx 0
6) Save the file "adhoc.sh" (be sure to save it in UNIX format, you can use notepad++ for this) and copy it into your device (I saved my script in /sdcard).
7) Turn the wifi connection back on and with a terminal emulator/ADB run the scrit
Code:
#cd /sdcard
#sh adhoc.sh
And now we're done!
You can see in your wifi settings your ad hoc network connected. But there are some issues, I cant see other networks on the list, even when I try to search for new networks, I can browse the web but cant connect to the play store, and with BlueVPN you could browse the store but couldn't download apps, the wifi icon in the notification bar is also gray color, after searching the forums this could mean I cannot connect to google services, but I still receive gmail notifications.
Well, I'll have to research more, but at least I think we're in the right way, to me this is a kernel/wpa_supplicant issue, I really wish some expert could help us out, or else I'll have to get into kernel compiling, I have a little linux experience and its been a while I dont get my hands into programming, but I'm not giving up just yet.
P.S: After checking with the terminal emulator, I started the command wpa_cli and this is the output I got:
Code:
[email protected]:/ # wpa_cli
wpa_cli
wpa_cli v2.0-devel-4.2.1
Copyright (c) 2004-2012, Jouni Malinen <[email protected]> and contributors
This software may be distributed under the terms of the BSD license.
See README for more details.
Using interface 'wlan0'
Interactive mode
<3>Trying to associate with SSID 'JOIKUSPOT'
<3>Association request to the driver failed
>
There seems to be a driver problem, I'll take a look into it too as soon as I can.
BTW I found this wpa_supplicat / wpa_cli files from this post http://forum.xda-developers.com/showthread.php?t=1980021 since the stock rom doesnt come with the wpa_cli command, these files seem to be for ICS but I tried them on JB and they work too.
Just a quick heads up
I've updated my n7 to rootbox v2.0 (comes with JB 4.2.2) and now I cannot connect it to my hotspot with my previous method, after checking my /data/misc/wifi/wpa_supplicant.conf file now shows this line:
network={
ssid="JOIKUSPOT"
.
.
disabled=1
}
What the heck does this mean? seems to be that the more I update my tablet the harder is getting to connect it to my ad hoc network, this makes me think maybe google wants to erradicate ad hoc wifi support from the OS, to me this is dumbest thing I ever heard since this tablet is WIFI only, isn't supposed to support ANY wifi network it finds in order to work properly? other OS like iOS or Symbian does still support it. Just the fact that i cannot use my tablet the way I want it to is very disappointing, and now I face two options: 1) Downgrade the tablet and never let it update again. 2) Install ubuntu and never again install android.
Im very sorry to say this but this is my first android device and my experience with it is very unsatisfactory, sometimes I wish I could get a refund and try the iPad mini or wait for any decent windows rt tablet.
For now I think i'm going for my option 2, tomorrow ubuntu will release the tablet version of their OS for the nexus 7, ill check it out and ill tell you my experience with it.
Please, if someone knows any of the senior contributors/developers of this community, please make them notice this issue, its almost unbelievable that ad hoc support haven't been fixed from android since issue #82, the original linux kernel supports it, and then google stripped it out and nobody got a response about this in the forums/groups, I know this is not an easy task, cause the android SDK doesnt support it either, also that you have to add the IBSS driver into the kernel and patch the wpa_supplicant file to stop filtering ad hoc networks, I still dont know if many people have requested this feature why even the modding community for android havent come with a concrete solution for this, there are a lot of kernel modders out there and I could find only one kernel that would work for me. I have to say that the most frustrating part of this situation is the lack of answers from the forums, I know this post already reached 1000 views, this means there's people still looking for an answer like me.
I have been trying lots of things on my new nexus 7 running 4.2.2 to try and get ad hoc networking working.
I have tried all the wpa_supplicant files I can find and even tried patching and compiling (using modified patches from h t t p://szym.net/2010/12/adhoc-wifi-in-android/) my own with no luck.
There are some musings at h t t p://szym.net/2010/12/prospects-of-ad-hoc-wifi-in-android/ saying we may never got it
I'll keep trying different things as this is something I really want
finally!
I found this custom rom (cm10 - 4.2.2 based) that has full IBSS support:
http://b-real.org/2013/ad-hoc-ibss-mode-support-for-android-4-2-2-with-cyanogenmod/
http://www.thinktube.com/android-tech/46-android-wifi-ibss
Here we provide information, patches and a few system images to support Ad-Hoc (IBSS) mode. We base our additions on CyanogenMod 10.1-M2 (Android 4.2.2 JDQ39).
Our goal is to bring the missing Ad-Hoc (IBSS) mode to Android, in a way that is completely integrated into the Android system API and user-interface. Users should be able to create and connect to Ad-Hoc networks from the standard user interface (Settings – WiFi) and Applications should have an API to configure their “own” Ad-Hoc network. We believe this will help people who need more capability than WiFi Direct and can extend diverse usages of Android mobile devices.
To achieve this, we have modified the WLAN driver “bcmdhd”, extended the Android framework, the public Android API and added the missing parts to the “Settings” application. At this moment only Nexus S, Galaxy Nexus and Nexus 7 devices are supported and tested, but the same kernel modifications can be made to a number of devices and the UI will automatically show Ad-Hoc mode options when the driver supports it.
We have submitted these changes to CyanogenMod and Google AOSP Gerrit and provide this page for further information.
Click to expand...
Click to collapse
I have tested it on my nexus 7 and it can detect my nokia hotspot (joikuspot) flawlessly
Downloaded and installed this last night and it works great. I can connect to my nokia 808 using ad-hoc wifi now from my nexus 7.
Today my Cyanogenmod made an automatic update to 10.1.0 RC1 and the ad hoc wifi works fine
Related
Hi, all.
I'm using my laptop in AdHoc mode, all device based on winmobile, detect normally my adhoc point and connected so good.
But my g1 do not find AdHoc point
Someone tried to link android + adhoc?
If you still got the Problem and your phone is rooted take a look here:
http://blog.joint.net/2009/07/connecting-android-phone-through-adhoc.html
G1 does not support ad-hoc out of the box. There are solutions for rooted phones but none of them are perfect at this point.
Hi
I have found the solution. I am using Ubuntu 10.04 and Using superfroyo2.2 on my HTC dream. I can connect to wifi adhoc network of my PC and enjoying internet on it.
I have attached the zip file. Please extract the file to get tiwlan.ini and wpa_supplicant.conf file. Replace your mobile's file with these ones and enjoy ad-hoc wifi.
You can use below commands, with mobile connected to PC via usb to replace the files:
adb shell
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# exit
> adb push tiwlan.ini /system/etc/wifi/tiwlan.ini
> adb push wpa_supplicant.conf /data/misc/wifi/wpa_supplicant.conf
> adb shell
# mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
# exit
I was using ubuntu bash and I placed both files in the tools folder of SDK. and then I ran the commands from that directory so that no path issues arise.
One more thing, You should create adhoc wireless with SSID iBM and leave it open without security key.
NO ROOT required!! - I am using MyTouch 4g with android 2.2.1
This is for anyone using Android who wanted to use Ad Hoc network to connect to internet (Android device connects to PC/laptop which is connected to internet) and couldn't because android doesn't support it ( Not rooted ). Here is a solution that DOESN'T require rooting the phone. I am running Android 2.2.1 and have no knowledge on compatibility despite my 2 days of research and eventual success.
Things you need: Windows 7, Android device and Connecitfy software ( link below... free version works just fine )
1. Update drivers for Ethernet and WiFi adapters in device settings... windows virtual WiFi miniport adapter should show up in the device list
2. Now startup Connectify: Create hotspot and choose password (uses WPA) and then start hotspot.
3. Now on your android device this network name should show up because its not Ad Hoc anymore. Its like a virtual router or hotspot.
4. NOTE: If google services fail on the android device. Go to account and settings and then sync now for your google login. Once synced, try opening android market and if it says authentication failed, try opening market two or three times more and it should eventually accept. If it doesn't... go find a solution and add to this post or create a blog.
5. Enjoy...hey hey wheres my treat!!
Links that helped me:
www(.)connectify(.)me --- The software -- I AM NEW SO IT DOESN'T LET ME INSERT LINK!!
erratasec(.)blogspot.com/2009/11/windows-7-includes-soft-ap(.)html -- Main source for solution (Remove dots)
Collapse this post
Hi folks,
can i change the device name of my HTC Hero anyhow, so that in my router's overview it shows the name of it, like it does with laptops / PCs?
I know its possible with bluetooth, but i havent found any option for doing that concerning WLAN.
I didnt root my device, otherwise i would have probably tried the commands which i would use for my Ubuntu laptop:
sudo echo "newname" > /etc/hostname
sudo hostname -F /etc/hostname
and edit /etc/hosts accordingly.
Anyone knows a solution for me?
Best regards,
kapen
Please, anyone?
Or could anyone, who has a rooted Hero, go and take a look whether the files /etc/hostname, /etc/hosts and the command "hostname" exist? Or perhaps even write something in these files, i mean it wont do any harm as you are just writing sth to an ordinary text file.
If i'd have root, i'd do it myself, but for now there are no benefits for me which would push me to root and i don't want to lose my warranty for nothing.
Help is very much appreciated!
most routers let you do this on the router....
I know when i hook up to my thompson router and set a static IP address, it lets me name the device... Hardly worth hacking the device for really.
Bump
I'd like to be able to do this as well, without having to use a static IP. This can be done with symbian, winmobile, java and other types of phone not to mention internet tablets, laptops etc. Why not an Android phone?
rhedgehog said:
most routers let you do this on the router....
Click to expand...
Click to collapse
True. But most routers isnt my router, its not able to do that. And neither do i want to set a static IP on my Hero, because i'm using it with several other WLANs.
fair enough.
I just thought as there is no way that anyone seems to know of on the device, that it may be an alternative.
Ya your right.
I just thought anyone knew a solution for me. I mean its a system running on linux and i ought to be able change that kind of stuff... just don't know how :\
Heureka! It worked just the way i suggested
If you have a rooted device with busybox!, get that handy adb file and do:
Code:
1. adb root
2. adb remount
3. adb shell
3.1 cd /etc
3.2 echo "Hero" >> hostname
3.3 echo "127.0.0.1 Hero localhost.localdomain localhost" > hosts
3.4 echo "127.0.1.1 Hero" >> hosts
3.5 hostname -F /etc/hostname
Voila. Though, you'll get an error when you do "hostname" now, because something in busybox is wrongly linked against a library which doesnt allow resolving hostname by IP, but other devices (such as my router) will now display "Hero" as device name.
Side note: my only intend for doing this was, that my router WAG54G2 (Linksys by Cisco) didnt work correctly with my Hero, meaning i got a lot of connection aborts in WLAN and often could not reconnect afterwards. That seems to be solved now!
Edit:
With the method above, you''ll lose your Wlan name after reboot. You need to add a line to the init startup scripts to perform a "hostname -F /etc/hostname" on every boot. This can be done in the file /init.rc or, if you have the MoDaCo Rom, in /data/init.sh
OK.. my knowledge of Tablets and rooting are limited.
I have an ACER A500 and my current android system is 3.0.1. I am rooted with clockwork MOD... No Custom ROM as of yet.
I have a Samsung Galaxy SII (Epic Touch from sprint), which is also rooted... no custom ROM
All I want to do is have my Tablet connect to my phones hotspot... does my tablet need the ADHOC fix/patch to do this?
I downloaded the wifi tether app for my phone and the tablet was UNABLE to see it, however my tablet can see, connect and use my wifi network at home.
Not sure if this is a questions for the Samsung Forum or ACER. I did a few searches for "Adhoc" and "what is adhoc" to get a better understanding of what it is... So far i can only come up with that its one of two methods of wifi networking.
What is needed to allow my A500 to connect to my cell phones wifi tether ?? I wasnt sure if i needed to download a ROM that had ADHOC integrated in it or not.
First off: A WiFi Adhoc network is basically a normal WiFi network, only it doesn't use a dedicated AP (like those WiFi router & AP devices you'll normaly use to create a network), but the WiFi network adaptor of a computer (or tablet, or cellphone).
In your case, the AP is the cellphone, so it will need some kind of software to switch its WiFi adaptor into AP mode. Your tab can then connect normally to the AP, no patches needed. The reverse way (only interesting to A501 users, as we have 3g / 4g network) is best done with the patch you mentioned, as this gives us the settings Acer removed back (they left the entire WiFi stack untouched, but removed access to the tethering settings).
As for switching your Phone's WiFi to AP mode: It may be that Samsung left the neccessary parts in their Android distribution. In this case you can activate it under settings -> Wireless and Networks -> tethering & portable hotspot. If they didn't, you can use apps like barnacle WiFi tether to achive the same effect... though encryption might be a problem if wpa_supplicant (the linux way of managing secure WiFi connections, which runs as a part of the WiFi stack) is missing.
Here is the file you need flash with cwm or ra as normal or follow these instructions.
1. navigate to system/bin and copy wpa_supplicant
2. past this to your sd card as a backup
3. rename wpa_supplicant to wpa_supplicant.old
4. extract the file from the download and past it into the system/bin folder. (should be wpa_supplicant)
4. Long press on the file once copied
6. select Permissions and set to User: RWE, Group & Others:RE only
again a big big thank you to the original poster/fixer the original thread is
http://forum.xda-developers.com/showthread.php?t=1056188
erica_renee said:
Here is the file you need flash with cwm or ra as normal or follow these instructions.
1. navigate to system/bin and copy wpa_supplicant
2. past this to your sd card as a backup
3. rename wpa_supplicant to wpa_supplicant.old
4. extract the file from the download and past it into the system/bin folder. (should be wpa_supplicant)
4. Long press on the file once copied
6. select Permissions and set to User: RWE, Group & Others:RE only
again a big big thank you to the original poster/fixer the original thread is
http://forum.xda-developers.com/showthread.php?t=1056188
Click to expand...
Click to collapse
Thank you, i'm going to try this, but I wonder if its my phone rather, not my tablet. Because My laptop can't see my phones wifi tether either. They make a patch for my phone..so I may try that first.
Sent from my SPH-D710 using Tapatalk
I have rooted my Nexus 7. Currently, the only way to change my MAC address is the following:
Code:
$ echo -n <MAC> > /persist/wifi/.macaddr
Using busybox ifconfig seems to work because new HWaddr is shown but in fact it doesn't - Settings->About tablet->Status shows old Wi-Fi Mac address. Additionally I cannot connect to AP any more. OpenWRT says:
deauthenticated due to local deauth request
Click to expand...
Click to collapse
I can write a script to automatically write new MAC to /persist/wifi/.macaddr and reboot, no problem, but I would prefer to avoid rebooting.
Kernel version 3.4.0-g03485a6, Android 4.4.4, Nexus 7 2013 Wi-Fi only.
Is this possible?
Has anyone ever got this to work? I'm searching on a way to have my MAC address changed upon booting the device and keeping it that way. Using ifconfig/busybox just allows you to change the MAC on that "boot session" and reverts back when you disconnect from an AP. I want to change my "stock MAC" from the get-go so that if I disconnect from an AP, it wont go back to the actual one. There is no /persist/wifi dir on my Nexus 7. Anyone who has done this before who can tell me how to do it?
Hi,
I just had the problem of being behind a Http/Https proxy and there is currently no option available to set this on the fire TV Stick.
Android offers this option at least since version 4 by default but they must have deactivatetd this feature intenionaly (region rights and such things).
But it is still possible.
1. Setup your AFTVS on a normal Wifi with internet connection ( if not already done)
2. Activate Apps from unkown sources and ADB
Settings --> System --> Developersoptions
3. Make sure your are connected to the same network as your pc.
4. Sideload following app:
Code:
AndroidProxySetter:
github.com/jpkrause/AndroidProxySetter/releases
How To sideload:
aftvnews.com/sideload/#more-7959
5. Start the App over adb on your pc:
Code:
//connect to device
adb connect 192.168.1.184:5555
//check the connection
adb -s 192.168.1.184:5555 get-state
//start app
adb -s 192.168.1.184:5555 shell am start -n tk.elevenk.proxysetter/.MainActivity -e host 192.168.56.1 -e port 8080 -e ssid PrivateWifi -e key Passw0rd
Where u would replace the device ip, host, port, ssid and key with the settings of your network.
Please mind that ur on a linux based system and everything is case sensitiv.
For more options look here:
Code:
github.com/jpkrause/AndroidProxySetter
5. Now, if everything is fine some little popups will be displayed and at last it should say connected.
6. Going back to the home screen and Done.
Known issues: After some major updates you will need to set the proxy again, so just repeat step 4
It should also run on the normal AFTV but i got none so i can't test it.
All Credit goes to JPKrause who wrote that little app, I just happend to find it
Update 21.06.2016:
With Fire Os 5.2.1.0 it seems like you cant start adb on the device itself so you have to start the proxysetter over adb on your pc.
This "new" way doesnt require to install the terminal emulator anymore and its actually more comfortable.
best regards N4b0
how to setting up proxy using pac file?
N4b0 said:
Update 21.06.2016:
With Fire Os 5.2.1.0 it seems like you cant start adb on the device itself so you have to start the proxysetter over adb on your pc.
This "new" way doesnt require to install the terminal emulator anymore and its actually more comfortable.
best regards N4b0
Click to expand...
Click to collapse
how to setting up proxy using pac file?
zcrself said:
how to setting up proxy using pac file?
Click to expand...
Click to collapse
Hi,
well I guess the AndroidProxySetter doesn't cover any way to use PAC files.
But you can actually open your pac file with an editor of your choise and extract your proxy settings from the containing functions.
bg N4b0
Hello, I have this working on a Fire Stick, I ran the commands on a Fire TV and is not working. Anyone has this working on a AFT (no stick)?
Any help is appreciated.
Thanks.
edit: it not working anymore on my fire tv stick, I see the connection going to the proxy but in the screen it says invalid_geo_ip, somehow they manage to get my original ip. My gf is american, and we are abroad, this was the only way to watch amazon content. Sad. I'll try to get a vpn instead, but this proxy setting was easy configuration.
Hi mastodonian,
in my case it still works like a charm on the AFTVS. I just tried it over a vpn that my home server provides, but the tv stick then says something about geo restriction even though its a german vpn. I suppose they are doing some kind of deep packet inspection or they got an ip blacklist.
Can't say but eventually the proxy you are tring to connect uses internally a vpn or is on a blacklist.
Cheers n4b0
can someone help me with this one im a bit slow on following instructions especially codes like these
gjhech said:
can someone help me with this one im a bit slow on following instructions especially codes like these
Click to expand...
Click to collapse
its pretty simple just do the following
Download adblock plus and install it on your firestick - use the power of google or an app store on your fire stick to get it
Download this app to your pc - https://github.com/jpkrause/Android...d/v0.1.3-alpha/proxy-setter-release-0.1.3.apk
Adb this app to your firestick by (assuming you have adb installed if not google howto)
enable adb on the fire stick in dev options if not already done so
adb connect 192.168.1.1 (change the ip address to your firesticks)
adb devices (you should see a list of devices connected if adb is working with your firestick ip address and port number)
adb install (then drag and drop the apk file into the command window - This will auto complete the path of the apk to save you entering it manually)
once the apk is installed
Code:
adb -s 192.168.1.1:5555 shell am start -n tk.elevenk.proxysetter/.MainActivity -e host localhost -e port 2020 -e ssid MyWifiName -e key MyWifiKey
Starting: Intent { cmp=tk.elevenk.proxysetter/.MainActivity (has extras) }
Change the ip address in the above code to your firestick ip address - the numbers after the : is the port address - it should match what you saw when you typed adb devices
Change the ssid to your wifi name and key to your wifi password
you will get some pop up windows on the firestick telling you if it has succeeded or you have errors
next open adblock plus and enable adblocking
restart the firestick
open adblock plus again and you shouldnt see the warning about it cannot manually set the proxy at the top of the screen
load up an adblock test website to test its working
Thank you for making this method clear and easy. However, even though I get the successful messages and the proxy chnages to localhost and the Port to 2020, Ad Block Plus still shows the "please configure manually" message after reboot.
Testing on some apps, the ads are most definitely not blocked!
Any suggestions?
Thanks for malking this app , I just have a problem , netflix connects directly and not through the proxy , any idea how to force connecting through proxy ,
It works perfect
I bought FireStick today and it wouldn't let me connect to Amazon as my ISP has made mandatory to use HTTP proxy.
I followed your step wise instructions and it worked. Thanks a ton
Hello,
Thank you for this! One issue: I'm unable to disable to proxy via adb... is there a specific way to do this? I've attempted to uninstall the apk file and clear data, but it still remains connected to the host.
Any assistance would be greatly appreciated!
pdesai91 said:
Hello,
Thank you for this! One issue: I'm unable to disable to proxy via adb... is there a specific way to do this? I've attempted to uninstall the apk file and clear data, but it still remains connected to the host.
Any assistance would be greatly appreciated!
Click to expand...
Click to collapse
Hi,
I actually had to do this myslef recently so what i did was just remove the network via the GUI and add the network again.
If you have to do this over ADB you should try to remove the network and add it without proxy flag
Cheers N4b0
xbarsasy said:
Thanks for malking this app , I just have a problem , netflix connects directly and not through the proxy , any idea how to force connecting through proxy ,
Click to expand...
Click to collapse
Well I have to clarify i did not make this app i just found it and put it to good use
On the issue i cant really say how to force him using the proxy. This method just configures the android intigrated Wifi network stack that supports proxys since 2.X is suppose. If an app like Netflix detects this, then u need an other method.
For windows i got an app called Proxifier, but until now i didnt find anything similar for android.
Only alternativ solution for your problem I can think of would be to configure your Accesspoint with a VPN on a second virtual network (well that's how i would do it).
Cheers N4b0
Hi All,
-I posted as a guest but didnt see my message, so posting again. sorry if it will be duplicate-
After Fire OS 6.2.1.3 upgrade, this wonderful proxysetter app doesn't seem to work anymore. I tried both 0.1.3 and 0.2 versions and it can not set the proxy.
Poareq said:
Hi All,
-I posted as a guest but didnt see my message, so posting again. sorry if it will be duplicate-
After Fire OS 6.2.1.3 upgrade, this wonderful proxysetter app doesn't seem to work anymore. I tried both 0.1.3 and 0.2 versions and it can not set the proxy.
Click to expand...
Click to collapse
Facing the same issue, unable to connect to Amazon after October update.
Any workaround available?
Not working for me too
uj812 said:
Facing the same issue, unable to connect to Amazon after October update.
Any workaround available?
Click to expand...
Click to collapse
I recently bought a fire tv stick. But unfortunately unable to make http proxy work. Kindly advice.
Solved... I think
phildani7 said:
I recently bought a fire tv stick. But unfortunately unable to make http proxy work. Kindly advice.
Click to expand...
Click to collapse
Not sure if anybody is still interested in this, but I recently uninstalled the apk and was unable to install it again getting the following error: Failure [INSTALL_FAILED_SHARED_USER_INCOMPATIBLE]
The solution is simple! The latest version of the FIreTV OS includes a proxy setting!
Just follow Step 1. in the instructions here: Blocked
The original instructions are posted on the Amazon appstore -> Appstore Blogs -> Viewing Secure (SSL/HTTPS) Traffic From Your App on Fire TVs Running Fire OS 6 on November 02, 2018
Since I've been blocked from posting a URL, here are the slightly modified instructions:
Setting a proxy on Fire TV
Bring up the Developer Tools Menu by one of the following two ways:
Remote: 1) Press and hold the Select and Down buttons for five seconds release and then 2) Press the menu button
ADB: adb shell am start -n com.amazon.ssm/.ControlPanel
Select Network Proxy
Select Manual
Enter your proxy IP address
Enter your proxy port
Click Save
Enjoy!
Hi All,
These proxy setting were working for me until the last update on OS 6.x and OS 7.x. The Developer setting app crashes on selecting save on the Network settings and the IP/port info is not saved.
Is someone else facing same issue.. Any work arounds?
Try this. It worked for me.
Use this .apk AndroidProxySetter. Install and follow the commands. It will route Network traffic to Charles proxy.
https://github.com/manadream/AndroidProxySetter