The region of the galaxy note firmware you have installed on your Note determines, among other things, what 5GHz frequencies (channels) are available for 802.11a wifi. Most of the custom firmware posts here are based on European region releases, and therefore have the EU channels.
In the US, we have a few higher channels (149-161/165) that are not permitted in the EU. As well, US users can use those higher channels at a much higher power rating than those in the EU. That makes those channels a better choice for us.
Lucky for us, the channel configuration for the wifi is done in a simple text file. I've copied that configuration file from my AT&T Samsung Galaxy SII (SGH-i777) which uses the identical wifi chipset (broadcom 4330) and merged it into the file used on my own Galaxy Note (checkrom v5) and attached it here.
The file should be unzipped and the file within (named nvram_net.txt_semcove_b2) should be copied to /system/etc/wifi. You should, of course, make a backup of that file before overwriting it with this one.
(If you don't know how to overwrite files in the /system partition, please wait until someone creates an update.zip to do it for you. I'm a horrible teacher.)
As with any other change, I'm not responsible if this breaks something, etc. I'm simply explaining the steps a person would take to reproduce what I've done on my own galaxy note - for purely educational reasons.
I wouldn't suggest that people outside the US use this configuration file, as it really won't do you any good if your other equipment can't use these frequencies. In addition, this configuration file will disable 802.11b/g (2.4GHz) channels 12-14 (as they aren't permitted in the US.)
I hope this proves useful to the other importers here.
UPDATE: (April 2nd, 2012)
Yes, there IS a mac address inside that file. However, it doesn't seem to be the same MAC address actually used by the phone for anything.
This change hasn't worked for a few people, and I suspect that the firmware those people are using references a different nvram_net* file. For those people (and anyone wanting to play with the wifi), I'll give you a place to start: In the directory where this file is located, there are SEVERAL files that start with "nvram_net.txt." Do a nandroid backup and then start editing each of those files. There's a line in there that starts with "ccode=" In the US, that line should be "ccode=US" and there should also be a line (search for it - if it doesn't exist, create it - if it does exist, change it) with "regrev=5" After you edit those files, reboot and recheck your ability to access the high 5GHz channels. (I don't support this.. it's just a hint to get people started on doing their own thing...)
Take care
Gary
good job. keep it up.
Had wondered why I couldn't see the second band on my router.
Thanks a bunch!
Thanks for the file garyd9, it works perfectly..
Well, no matter what I tried this made no difference to my Note. It wont even show my E4200's 5Ghz SSID, much less let me join it. I've got Open Germany ROM N7000XXLC1 but no luck getting 5GHz to work here.
Would you have any ideas on what else to try?
abalakersky said:
It wont even show my E4200's 5Ghz SSID, much less let me join it. I've got Open Germany ROM N7000XXLC1 but no luck getting 5GHz to work here.
Click to expand...
Click to collapse
What 5GHz channel is your E4200 set to use? Given that info, I can set my own to the same channel to test...
It might be related to the firmware version (I'm still using an LA4, I think), but I somehow doubt that...
Gary
Mine is set to Auto channel width and Auto (DFS) for the channel selection.
Sent from my GT-N7000 using xda premium
abalakersky said:
Mine is set to Auto channel width and Auto (DFS) for the channel selection.
Click to expand...
Click to collapse
If you can't tell me what channel its using, then I really can't help you... I'd suggest setting it manually to a non-DFS channel.. one of the higher ones is usually better in the US.
Take care
Gary
I have gone through checking every single channel and setting 5GHz to each one of them. I did not see any signal on channels 149, 153, 157, and 161. I did get a signal on lower channels 36, 40, 44, 48. However the signal I was seeing with WiFi analyzer was a bit less then my 2.4GHz of the same router on channel 11.
Does that help?
abalakersky said:
I have gone through checking every single channel and setting 5GHz to each one of them. I did not see any signal on channels 149, 153, 157, and 161. I did get a signal on lower channels 36, 40, 44, 48. However the signal I was seeing with WiFi analyzer was a bit less then my 2.4GHz of the same router on channel 11.
Click to expand...
Click to collapse
Sounds like your note is still set up to be compatible with the EU or most non-US countries. Either there was a mistake made making the fix on your device, or the fix isn't completely compatible with the lc1 firmware. Feel free to figure out what should be done differently for the neweer firmware floating around.
Take care
Gary
Sent from my GT-P6210 using Tapatalk
Would it be possible to add channels 12, 13 and 14 on the G band? My router and devices are hacked to use them. My condo complex is completely saturated with wifi and being out of the band helps a lot.
there is no file named that in my wifi folder.
there is one with the name, sans the _b2 on it, though...
should i just put the file in there or rename it or what?
now that i look...there are several files with almost the same names which have essentially the same content...wtf?
gedster314 said:
Would it be possible to add channels 12, 13 and 14 on the G band? My router and devices are hacked to use them. My condo complex is completely saturated with wifi and being out of the band helps a lot.
Click to expand...
Click to collapse
It is possible, and those channels are likely enabled for most EU regions. Of course, those regions are much more restricted on 5GHz (which why this thread exists.) I don't know of any region that allows both the expanded 5GHz channels and expanded 2.4GHz channels at the same time....
Even if there is such an area, I live in the US and it'd be illegal for me, so I wouldn't be able to play around with the files to get it working.
(I'm sure most people reading this think I'm nuts to worry about such things, but we all have our quirks...)
derrick_ said:
there is no file named that in my wifi folder.
there is one with the name, sans the _b2 on it, though...
should i just put the file in there or rename it or what?
now that i look...there are several files with almost the same names which have essentially the same content...wtf?
Click to expand...
Click to collapse
What you haven't told me is what firmware version you are running. Is it something cooked up on XDA or something direct from Samsung? Which version? What CSC are you using?
Of course, it likely doesn't matter anyway. If you aren't running the same firmware I'm running, I really can't help you much. (Well, I could do the investigative work for you, but that wouldn't actually be helping you - only doing the work for you.) One of those files IS being used by your system, and it'll be up to you, as a member of a developer forum, to figure out which one and make the proper changes.
Take care
Gary
garyd9 said:
What you haven't told me is what firmware version you are running. Is it something cooked up on XDA or something direct from Samsung? Which version? What CSC are you using?
Of course, it likely doesn't matter anyway. If you aren't running the same firmware I'm running, I really can't help you much. (Well, I could do the investigative work for you, but that wouldn't actually be helping you - only doing the work for you.) One of those files IS being used by your system, and it'll be up to you, as a member of a developer forum, to figure out which one and make the proper changes.
Take care
Gary
Click to expand...
Click to collapse
Oops lol. I'm running code name android 1.5.5
Sent from my GT-N7000 using Tapatalk 2 Beta-4
garyd9 said:
Sounds like your note is still set up to be compatible with the EU or most non-US countries. Either there was a mistake made making the fix on your device, or the fix isn't completely compatible with the lc1 firmware. Feel free to figure out what should be done differently for the neweer firmware floating around.
Take care
Gary
Click to expand...
Click to collapse
So, after replacing all files in that directory with yours, and and even getting files from ATT version of the note I still cannot see the higher bands on the 5G.
One thing I have not tried is replacing firmware bin files with the ATT copies. I have a feeling that, at least Germany firmware, has those bands fully disabled in the hardware. But I don't want to brick my note so for the moment I am hesitating.
Sent from my GT-N7000 using xda premium
abalakersky said:
. I have a feeling that, at least Germany firmware, has those bands fully disabled in the hardware.
Click to expand...
Click to collapse
I wasn't aware that different regions had different firmware on the internation note. Everything I've seen is that the firmware files are the same, but are configured differently per region and CSC. How they are configured, however, might be different. Instead of blindly copying files around, you have to figure out what is going on. One of the config files in that directory is being used.. The question is "which one?"
Not having any luck recognizing my 5GHz band on an Asus RT-N66U
Anyone?
Sent from my GT-N7000 using Tapatalk
UPDATE: (April 2nd, 2012) (OP updated with the below)
Yes, there IS a mac address inside that file. However, it doesn't seem to be the same MAC address actually used by the phone for anything.
This change hasn't worked for a few people, and I suspect that the firmware those people are using references a different nvram_net* file. For those people (and anyone wanting to play with the wifi), I'll give you a place to start: In the directory where this file is located, there are SEVERAL files that start with "nvram_net.txt." Do a nandroid backup and then start editing each of those files. There's a line in there that starts with "ccode=" In the US, that line should be "ccode=US" and there should also be a line (search for it - if it doesn't exist, create it - if it does exist, change it) with "regrev=5" After you edit those files, reboot and recheck your ability to access the high 5GHz channels. (I don't support this.. it's just a hint to get people started on doing their own thing...)
garyd9 said:
UPDATE: (April 2nd, 2012) (OP updated with the below)
Yes, there IS a mac address inside that file. However, it doesn't seem to be the same MAC address actually used by the phone for anything.
This change hasn't worked for a few people, and I suspect that the firmware those people are using references a different nvram_net* file. For those people (and anyone wanting to play with the wifi), I'll give you a place to start: In the directory where this file is located, there are SEVERAL files that start with "nvram_net.txt." Do a nandroid backup and then start editing each of those files. There's a line in there that starts with "ccode=" In the US, that line should be "ccode=US" and there should also be a line (search for it - if it doesn't exist, create it - if it does exist, change it) with "regrev=5" After you edit those files, reboot and recheck your ability to access the high 5GHz channels. (I don't support this.. it's just a hint to get people started on doing their own thing...)
Click to expand...
Click to collapse
@ripee this is where I first found reference to regrev=
Related
There is an iPhone 3G app called VOiPover3G that tricks other iPhone apps into thinking that they are on Wi-Fi even though they are on 3G/EDGE/GPRS.
Is anything like this being looked at/developed for Android phones??
Please post questions about apps in the correct subforum. This will probably get locked...
This probably is the right subforum. Apps forum is for apps that have been compiled and released. This forum is for dev including apps dev.
Anyway, what would be the point in a program like that? What programs could benefit from it?
JaboJG said:
This probably is the right subforum. Apps forum is for apps that have been compiled and released. This forum is for dev including apps dev.
Anyway, what would be the point in a program like that? What programs could benefit from it?
Click to expand...
Click to collapse
It would allow programs like sipdroid (the market version) to think it was on wifi and when we finally get something like Fring for Android that would also be able to use the data package to make voip calls, even "real" skype calls.
It is in the wrong part of the forum, but I might as well answer it...
While the iPhone doesn't allow certain services over 3G (e.g. VoIP stuff), the current Android handsets + apps don't do such a thing.
e.g. Sipdroid works fine over edge/umts/wifi (as good as those networks can support VoIP).
It's really kind of a strange question to be honest. If there isn't a problem, don't ask questions about it
JaboJG said:
This probably is the right subforum. Apps forum is for apps that have been compiled and released. This forum is for dev including apps dev.
Anyway, what would be the point in a program like that? What programs could benefit from it?
Click to expand...
Click to collapse
Not to harp on the point made by Diceman4, but it really isn't the correct sub-forum. If you look at the Stickies in the Apps/Games sub-forum, you will see that one of them is regarding request/ideas for applications.
JaboJG said:
This forum is for dev including apps dev.
Click to expand...
Click to collapse
I don't see any development going on in the first post though. This seems more like a post for the "ideas for apps" thread in app subforum. Although if the op came back with a chunk of code that needed debugging, that would be a different story.
MOD EDIT
Moved to Applications & games forum
The main reason for asking was because of problems with Tmob in the UK blocking sipdroid (port 5060) and preventing it using 3G etc.
If we had an app like VOiPover3G it may very well allow us to bypass that problem, I don't know
robiom said:
The main reason for asking was because of problems with Tmob in the UK blocking sipdroid (port 5060) and preventing it using 3G etc.
If we had an app like VOiPover3G it may very well allow us to bypass that problem, I don't know
Click to expand...
Click to collapse
Why? a better bet would be to ask the sipdroid creator to include a user configurable port setting. The point of android is that the workarounds don't need to be workarounds on the phone, but rather workrounds for interfacing with the network.
robiom said:
The main reason for asking was because of problems with Tmob in the UK blocking sipdroid (port 5060) and preventing it using 3G etc.
If we had an app like VOiPover3G it may very well allow us to bypass that problem, I don't know
Click to expand...
Click to collapse
The technique described by the op routes traffic internally from the wifi interface to the cellular interface. That will have no effect on the protocol or port used. In other words, it will only be of use if the app is hardcoded to use wifi only and you want to work around that. If the cellular carrier is blocking the data, this method will not get around that.
As for sipdroid, you can manually configure the port used.
jashsu said:
The technique described by the op routes traffic internally from the wifi interface to the cellular interface. That will have no effect on the protocol or port used. In other words, it will only be of use if the app is hardcoded to use wifi only and you want to work around that. If the cellular carrier is blocking the data, this method will not get around that.
As for sipdroid, you can manually configure the port used.
Click to expand...
Click to collapse
If you use pbxes there are a handful of different ports that will work but I haven't been able to get any to work. Saying that, up till recently I was using Gizmo5 but pbxes have blocked it's use after they (Gizmo5) allegedly stole/used sipdroid code and renamed it as if it was there own.
If any one has had success with sipdroid on 3g etc on t-mob UK please post the sip provider and the settings used.
Have you guys tried using the FULL version of sipdroid.. the one on the market didnt allow for 3g calls but this one does http://code.google.com/p/sipdroid/
turboyo said:
Have you guys tried using the FULL version of sipdroid.. the one on the market didnt allow for 3g calls but this one does http://code.google.com/p/sipdroid/
Click to expand...
Click to collapse
Been there, done that, even got the T-shirt.
The problem is T-mob in the UK are a pain in the neck and are blocking the port 5060.
As someone has already mentioned in this thread, what is needed is a user configurable port so that T-mob UK can't block.
Let's hope sipdroid developers can do something along those lines.
I don't get it... have you tried all the alternative ports listed in pbxes website?
53, 69, 80, 135, 161, 443, 500, 1433, 1701, 1812, 3389, 4500, 5061, 5900, 16999, 26999 and
36999 (recommended)
Note:
Because of the DNS entries for pbxes.org your device may be selecting port 5060 automatically. If you want to use an alternative port enter 188.40.65.148 as SIP server.
Click to expand...
Click to collapse
Both of them work as UDP or TCP.
TCP is recommended as it will help with battery life.
If none of these ports work, then It has to be that T-mobile has a Layer 7 filter in place looking for the SIP signaling traffic, and there should be no workaround possible unless you can wrap your sip traffic in a VPN. Nothing can be done to stop that, unless they filter the whole L2TP,PPTP,IPSEC or OpenVPN protocols.
I have tried most if not all of the ports specified and still no joy BUT I'll give it another go. What SIP provider do you use?
If T-mob are killing all SIP traffic how is it possible to use sipdriod over VPN?? Surely that is a major undertaking?
If it was done though, it would be the most robust and bulletproof VOIP app and would never be stopped Brilliant
I have just tried every single one of the alternative ports and every time I had a registration failure (timeout) so I guess T-mob are filtering for SIP traffic.
That leaves only the VPN route OR change providers OR change phones.
robiom said:
I have just tried every single one of the alternative ports and every time I had a registration failure (timeout) so I guess T-mob are filtering for SIP traffic.
That leaves only the VPN route OR change providers OR change phones.
Click to expand...
Click to collapse
Changing phones WILL NOT work since it isn't the phone that is causing the problem, it is the provider.
VPN should be fine, but you'll need a VPN server somewhere to connect through, i.e., your home computer.
There is nothing a carrier can do to block SIP over VPN. Everything is tunneled over the VPN connection so they can't know what goes in there.
As soon as we have a reliable VPN service (Donut seems to have PPTP or L2TP, although I'd love to see OpenVPN there) , you'll ve able to set-up your own voip and vpn server and pipe all the voice through it.
There is a couple of VoIP providers who can do that for you. One that comes to mind is callwithus.
On the connection issue with t-mobile, I suggest you try this:
If you have a DMZ linux/cygwin (altough a windows box might make it) host or a shell anywhere you can test if your provider is locking those ports, the pbxes ip or maybe even the SIP traffic.
Listen in a port using netcat:
netcat -n -l -vvvv 5060
Click to expand...
Click to collapse
Launch the Terminal Emulator in your android phone and test if you can connect to your host:
nc <your_hostname> 5060
Click to expand...
Click to collapse
Type something... if you can see the text, they have a L7 filter in place.
If you can't see anything, they are blocking the port.
Now change the listening port to 36999 for instance.
Try to connect again. It should work.
Now in Sipdroid, add your hostname, give it any username, any password, use the 36999 port and select TCP connection and keep the netcat running on your listening host.
If you see a connection in your listening host and some signalling traffic, pbxes should work for you.
If you don't, then there's a really advance L7 filter between you and the internet and they can block anything they want to.
In this case, the only solution (and there's nothing they can do unless they also block it), is to use a VPN.
Thanks guys for all your suggestions. I'll try and go through all the procedures you've suggested stickman and I'll post the results
Update March 25, 2013:
Solved!! The folks over at Thinktube Inc. have developed a fix and submitted it to CyanogenMod and AOSP for merging into their code:
http://b-real.org/2013/ad-hoc-ibss-m...h-cyanogenmod/
http://www.thinktube.com/android-tech/46-android-wifi-ibss
Essentially the EASIEST solution is to ROOT your phone, and install the CyanogenMod nightly as of March 25 or later (note: you will have to wait until the nightly is actually BUILT, since as of today it is not ready yet).
I have not tested this solution out myself, however others within this thread have confirmed it working.
Please if anyone develops a easier patch or a step-by-step for people who do NOT want to use CyanogenMod, post and I will update the OP
Cheers!
WiKiD24
-------------------------------------------------------
Update Oct 9, 2012:
- Nexus 7 v4.1.2 did not add Wi-Fi Ad-Hoc Support with the stock update from Google.
To do: Check if any WPA-Supplicant changes previously tested in v4.1.1 now work in 4.1.2
- Workaround (Recommended): Bluetooth Tethering to Nexus 7 Tablet (via Bluetooth DUN Profile). "BlueVPN" from Google Play Store.
Tested successfully on many Nokia Symbian phones (N7, E71, E72), and others.
However, many applications on Nexus 7 Tablet do not support it (without fixes from the developers)
Confirmed working applications:
- Pulse
- Google Chrome
- Dolphin Browser
- Facebook
- Ebuddy
- Youtube
- Others (I am too lazy to add them all)
Confirmed NOT working applications:
- Gmail
- Email
- Google Search
- Google Play Store
- Dropbox
- Words with Friends
- Scramble with Friends
- Others (I am too lazy to add them all)
More details can be found here: http://forum.xda-developers.com/showpost.php?p=29763582&postcount=27
Issue: Sometimes the phone/tablet do not connect (randomly), due to issues with either the phone or the tablet.
To resolve: Turn on and off bluetooth on phone, Turn on & off bluetooth on tablet. Try again. If does not work, reboot phone and tablet and try again. Should work.
-Workaround: Android Phone to Nexus 7 Tablet (via "FoxFI" App on Phone, "FoxFi Addon" App on Tablet, or via "PDANet", or via "Wireless Tether App")
http://forum.xda-developers.com/showpost.php?p=29763582&postcount=27
- Workaround: USB Tethering ANY Phone to Nexus 7 Tablet (via "PPP Widget" App on Tablet, requires rooted Nexus 7)
http://forum.xda-developers.com/showpost.php?p=32431103&postcount=51
- Workaround: Windows WiFi Laptop Tethering to Nexus 7 Tablet
http://www.youtube.com/watch?v=klHzMyYFGeQ
-------------------------------------------------------
Hi All,
I've just recently gotten a Nexus 7 and need to be able to enable Ad-Hoc wifi on the tablet.
I also own a Asus TF101 and previously had the same problem however there was a fix for that.
The solution was to replace the wpa_supplicant file in the /system/bin folder, however I do not know the code to change it.
If anyone has the technical know-how, they would be able to reverse-engineer it and apply the same fix.
http://forum.xda-developers.com/showthread.php?t=1370955
http://szym.net/2010/12/adhoc-wifi-in-android/
http://www.slatedroid.com/topic/2752...less-hotspots/
http://www.olsr.org/?q=olsr_on_android
http://hostap.epitest.fi/gitweb/gitw...upplicant.conf
I posted a possible solution in QnA section. Thread title is similar to this one. Check it out. Doesn't involve any coding. Prime had a similar issue on a few firmware updates. This was solved for us(before Asus came around to enabling it themselves) by adding in a wifi supplicant file and renaming an older one. Then setting permissions on the new file. Here is the link to that thread. There's a good chance it will work without the file needing to be modded. It came from a galaxy tab LR something and worked fine on prime. Its worth checking out.
http://forum.xda-developers.com/showthread.php?t=1438297
thanks for the tip and I tried it out, which is essentially the same type of solution but it didn't think work as there is no wpa_supplicant2 file in the nexus 7.
http://forum.xda-developers.com/showthread.php?t=1777413
here's some more useful information for enabling ad hoc:
http://szym.net/2010/12/adhoc-wifi-in-android/
http://www.slatedroid.com/topic/27522-howto-connect-to-ad-hoc-wireless-hotspots/
http://www.olsr.org/?q=olsr_on_android
http://hostap.epitest.fi/gitweb/git...ob_plain;f=wpa_supplicant/wpa_supplicant.conf
I'm doing what I can right now to try and enable it.
Some more experienced android users whom know what they're doing would be better than me trying it out, though!!
Did any of those sources of information get you any closer to enabling ad-hoc?
Just FYI that Nexus S "ad hoc enabling file" doesn't work on NS with Jelly Bean.
nexususer0101 said:
Did any of those sources of information get you any closer to enabling ad-hoc?
Click to expand...
Click to collapse
None yet, I need some help to do so. There is a file called "wpa_cli" that I need copied from another device, because I can't find it on the internet.
If anyone could find it in their "/system/bin" folder and attach it to this tread, I could certainly try it.
I've also requested the same thing in the Q&A forum here: http://forum.xda-developers.com/showthread.php?t=1793437
Bumping; I have the same condition. I'm in Italy and bought an internet package for my laptop--I'm sharing it with all my other devices but the N7 doesn't see the adhoc connection. Like OP said, I had a Transformer TF101 and remember flashing a file to fix it.
Thanks in advance.
Just an FYI: Also checked my GNex for a wpa_cli and came up empty.
Just wanted to give quick update, i have not been able to find anyone to help me and also my life is kinda hectic right now... Hopefully someone will be able to pick up where I left off, in the meantime my nexus 7 is pretty much useless to me until resolved.
One more "me too".
I'm here to share my sympathy to everyone else's pain as I have a nexus 7 that I can't connect to my phone's adhoc Hotspot. I have also posted my query in Android Central, but no one seems to have been able to know a fix as of yet. (topic can be found here: Android Forums at AndroidCentral.com > Google Nexus 7 Tablet Forum > Nexus 7 Rooting ROM's & Hack's > *** CONNECTING TO Adhoc WiFi WITH THE NEXUS 7 ***)
As I said in that thread.. not being able to connect to phones hotspot makes my beautiful nexus 7 feel like a handicapped tablet.
wikid24 said:
Just wanted to give quick update, i have not been able to find anyone to help me and also my life is kinda hectic right now... Hopefully someone will be able to pick up where I left off, in the meantime my nexus 7 is pretty much useless to me until resolved.
Click to expand...
Click to collapse
I haven't seen any reports/posts of people checking out or trying what I mentioned in post #2..lol. on prime we had this exact same problem. Then we found the supplicant file to replace one we had and then adhoc tethering worked after that. You only need to be rooted to do this as you need to rename a file and insert new supplicant in there and set permissions. You can always backup and rename original file. So if it doesn't work, you can easily revert back to stock file. I have a feeling this new file will work. Just haven't tried myself yet as I haven't brought tablet outdoors yet to need tethering. I might eventually see if it works if no one else does.
Look at the thread I linked in second post and you will see prime owners had exact same problem and we solved it. It worked for the transformer 300 also. Will likely work for nexus 7 also. The file is, in a sense, universal.
demandarin said:
I haven't seen any reports/posts of people checking out or trying what I mentioned in post #2..lol. .
Click to expand...
Click to collapse
I have tried. It does not work -- WiFi refuses to turn back on with this new supplicant file. And yes, I made sure to follow your instructions exactly as described in the procedure.
With the N7, there is no such thing as a wpa_supplicant2 file originally in /system/bin (only the one without the '2' exists in the N7 which is the one running the show here, I know this for a fact as when restoring this file, the WiFi in the N7 becomes functional again). So I tried this same file you provide both with and without the '2', with no better results.
I suspect that only a developer that knows what he's doing would be able to come up with a new wpa_supplicant file specifically tweaked for the N7 (as opposed to using one that did the trick for the Prime or for the Xoom or whathaveyou).
Thanks for the suggested idea though... anything else you think we should try?
rdelfin said:
I have tried. It does not work -- WiFi refuses to turn back on with this new supplicant file. And yes, I made sure to follow your instructions exactly as described in the procedure.
With the N7, there is no such thing as a wpa_supplicant2 file originally in /system/bin (only the one without the '2' exists in the N7 which is the one running the show here, I know this for a fact as when restoring this file, the WiFi in the N7 becomes functional again). So I tried this same file you provide both with and without the '2', with no better results.
I suspect that only a developer that knows what he's doing would be able to come up with a new wpa_supplicant file specifically tweaked for the N7 (as opposed to using one that did the trick for the Prime or for the Xoom or whathaveyou).
Thanks for the suggested idea though... anything else you think we should try?
Click to expand...
Click to collapse
They likely will implement it through a future update. Hopefully that's sooner than later. Ill ask motley, kernel developer.
I toyed with this for a while...
If you install Power Controls (Power Controls) you can add a button that turns on the Wifi Hotspot.
Problems:
you cant change any settings in current settings UI
Appears to be default "Android_AP" SSID and whatever the default password is (i dont recall if this is a random code or not)
Its a start!
Demented-Idiot said:
I toyed with this for a while...
If you install Power Controls you can add a button that turns on the Wifi Hotspot.
Problems:
you cant change any settings in current settings UI
Appears to be default "Android_AP" SSID and whatever the default password is (i dont recall if this is a random code or not)
Its a start!
Click to expand...
Click to collapse
Could you explain exactly what this does? I didn't understand what it is being implied with this being a start? with this you can actually connect to adhoc?
idk if anyone has looked...but has anyone looked into editing the Wifi-Direct api to make adhoc networks visible in there? Since wifi-direct is made for p2p connections. it's android.net.wifi.p2p.WifiP2pManager info about it is here http://developer.android.com/guide/topics/connectivity/wifip2p.html like I said...don't know if it's much help
I also wanted to post a quick reply, since I've been an insomniac yesterday.
From my previous posts I posted this link here as well, I edited the wpa_supplicant.conf file from the /system/etc/wifi folder and modified with the following settings, however I don't think that it even reads the wpa_supplicant.conf file either. Can anyone either confirm or deny that the wpa_supplicant.conf file is being used on the N7??
-------------------
update_config=1
ctrl_interface=wlan0
eapol_version=1
ap_scan=2
fast_reauth=1
network={
ssid="Bondphone"
mode=1
frequency=2412
key_mgmt=NONE
wep_key0="1234567890123"
wep_key1=1234567890123
wep_tx_keyidx=1
priority=3
auth_alg=SHARED
}
------------------------
wikid24: I don't know if N7 (or my NS) reads this file but it definitely reads /data/misc/wifi/wpa_supplicant.conf. Only problem is that I can't turn wifi on after ANY change in this file. Sometimes even if I revert my backup file, wifi won't launch and I must delete it to make wifi working again.
I found this thread on XDA
http://forum.xda-developers.com/showthread.php?t=1806937
It is edited wpa_supplicant file for Asus Transformer but it allows me to turn on wifi even on NS. But it doesn't show me any ad hoc networks. Maybe with non-stock kernel...?
And I also found ad hoc patch for source code of older version of wpa_supplicant. But I'm not able to try if it is possible to apply it on JB version too.
http://szym.net/android/wpa_supplicant-ibss.patch
jenda.69 said:
wikid24: I don't know if N7 (or my NS) reads this file but it definitely reads /data/misc/wifi/wpa_supplicant.conf. Only problem is that I can't turn wifi on after ANY change in this file. Sometimes even if I revert my backup file, wifi won't launch and I must delete it to make wifi working again.
I found this thread on XDA
http://forum.xda-developers.com/showthread.php?t=1806937
It is edited wpa_supplicant file for Asus Transformer but it allows me to turn on wifi even on NS. But it doesn't show me any ad hoc networks. Maybe with non-stock kernel...?
And I also found ad hoc patch for source code of older version of wpa_supplicant. But I'm not able to try if it is possible to apply it on JB version too.
http://szym.net/android/wpa_supplicant-ibss.patch
Click to expand...
Click to collapse
jenda, I think you may have solved a big piece to the puzzle!!
You can copy the file to another directory, and THAN you can open the file! I noticed I had all my pre-saved wifi addresses in this file!
If someone can please copy the "/data/misc/wifi/wpa_supplicant.conf" file to another directory, modify it, than overwrite the old file, it should work!! *fingers crossed*
(unfortunately I am busy for a few days, don't know if I'll be able to make the change for a while)
Hi, as the title of the thread says I am trying to figure out how to edit certain settings via build.prop, rather than ##PROGRAM.
This is because of two things: I flashed my bionic to page plus, using the stock rom, then I installed Carbon ROM in slot1. To make 3G operate correctly, you have to change certain settings using ##PROGRAM. The stock rom works great after using the program menu. Unfortunately, the Carbon Rom, although fantastic, does not have this menu.
One of the settings is to change Sim type to 3G. The other is to set lte bppanic to disable. Then disable class 1 and class 2 apns.
If anyone knows how to do this, I would be thrilled, as would other Page Plus users, I imagine. Thanks.
Bump
This may be off by a long shot, but relating to radios..
http://www.droidrzr.com/index.php?/topic/22660-help-pls
typed on my Bionic
Hi, I think that is the right direction. However, so far I cannot find out how to change sim type to 3g or set lte bppanic to disable using a database.
There are similar "name" inputs there, like network mode, etc, but nothing indicating those exact settings. I wonder if I find the settings under the stock rom, can i import them into carbon? Or are they motorola-rom-specific?
I think that these are actually important questions for flashed users, and we will see this becoming more and more of an issue as 3G phones become obsolete, and the only way for a Page Plus or other Verizon MVNO user to have a workable smartphone is to flash a 4G one,
On the Bionic (and I imagine on other models), the only option for now will be the stock rom; any rom without access to the ##PROGRAM menu will be left short as far as advanced network settings goes. Of course, I think this might vary depending on how you flashed in the first place. I used a free tutorial that was quite simple.
chrisp6825 said:
This may be off by a long shot, but relating to radios..
http://www.droidrzr.com/index.php?/topic/22660-help-pls
typed on my Bionic
Click to expand...
Click to collapse
I honestly couldn't input much on this, as I've never had to dabble with this area ( well just once, quite a long time ago), but I'd imagine you could check out the data bases ( maybe take a "snapshot" or copy/download it) from a stock rom, make your changes using that ##program menu, then compare the new/changed database to the prior one.
That would be a quick way to detect if any values are being affected there, and where. Then you may as well check if those values exist on other roms, and try them out. Couldn't hurt, with safestrap/recovery backups and all.
typed on my Bionic
I believe that you should check out the setup for page plus on howard forums. It goes thru the changes to make the bionic 3g and turn off 4g completely. But the links to the apps and basic principles should still apply. Good luck, if you can't find it let me know. I'll send you a link.
Cruzin' tha Galaxy SIII via Obsessed Rom / "INAPPROPRIATE" Kernel
Hello dear fellows.
I've updated my S2 LTE today through OTA from version 5.0.2 to version 6.0.1.
While in 5.0.2, I contacted Samsung about a procedure to make the S2 to forget obsolete networks, since the usual method does not work, because networks not in range are not shown!
Except for another guy asking the same question (somewhere), I didn't found anything in the net about this issue, I don't know if people already realized the problem... (seems all people is quite busy getting root and/or the new firmware).
So, Samsung told me the feature is not available, that I should backup with Kies and do a factory reset! UNACCEPTABLE!!!
I wait for the 6.0.1 hopping that the problem was solved in this version, but NOOO, they MEAN it. IT IS NOT available!
So...
- Does anyone one of you manage to find a way to make the S2 to forget / delete old unused networks?
- Does anyone find acceptable the actual status quo of the problem?
- Is there someone with a reasonable explanation for this feature being removed from S2 firmware? (At least some explanation I can swallow)?
Thank you all.
I think it's just sloppy thinking from the developers. Of course one should be able to get a list of known/saved WiFi networks and delete from the list accordingly. I can do it on my Nexus 6P running N preview 3. Maybe this app can be used to achieve this: https://play.google.com/store/apps/details?id=com.mdroidapps.wifimanager
One should also be able to see the password for saved WiFi networks without having to be rooted. Yes, it's a security risk but Windows and Linux let you see the password in clear text.
Android still have a bit of maturing to do.
And while we're at it - what I really want is being able to change DNS servers while on mobile data. When limited to your carriers DNS servers you are unable to connect to DNS blocked sites like in example some torrent sites. I would like to set my DNS to my Raspberry Pi running pi-hole and get DNS adblock even though I'm on mobile data. But this is only possible using a VPN app.
Sendt fra min SM-T815 med Tapatalk
LosserKlosser said:
I think it's just sloppy thinking from the developers. Of course one should be able to get a list of known/saved WiFi networks and delete from the list accordingly. I can do it on my Nexus 6P running N preview 3. Maybe this app can be used to achieve this: https://play.google.com/store/apps/details?id=com.mdroidapps.wifimanager
One should also be able to see the password for saved WiFi networks without having to be rooted. Yes, it's a security risk but Windows and Linux let you see the password in clear text.
Android still have a bit of maturing to do.
And while we're at it - what I really want is being able to change DNS servers while on mobile data. When limited to your carriers DNS servers you are unable to connect to DNS blocked sites like in example some torrent sites. I would like to set my DNS to my Raspberry Pi running pi-hole and get DNS adblock even though I'm on mobile data. But this is only possible using a VPN app.
Sendt fra min SM-T815 med Tapatalk
Click to expand...
Click to collapse
Thank you for the reply.
I've tested the app "wifi manager". It did not work as expected!
- The app indeed show the list of all networks even the ones not in range / obsolete.
- The app indeed allow the 'forget' procedure.
I use then the 'forget' procedure in a old network. The app says "wait....", but after that, the old network is still showing in the list no matter how many times you apply the procedure, no matter if you close and reenter the app. That means, the app is useless for the purpose to delete old networks, at least in the Tab S2 device.
I don't know it this issue is just a developer's sloppy thinking, or if this is Samsung stink over all of us. I think it is the later...
Sorry I do not know any way to change connection DNS the way you need, or any other way for that matter.
Still looking.
LosserKlosser said:
And while we're at it - what I really want is being able to change DNS servers while on mobile data. When limited to your carriers DNS servers you are unable to connect to DNS blocked sites like in example some torrent sites. I would like to set my DNS to my Raspberry Pi running pi-hole and get DNS adblock even though I'm on mobile data. But this is only possible using a VPN app.
Sendt fra min SM-T815 med Tapatalk
Click to expand...
Click to collapse
Touch VPN will bypass those blocks.
This module *should* hide you data usage while tethering, allowing you to have, in theory, unlimited tethering. I just threw it together and it is NOT fully tested to see if it 100% prevents monitoring of data usage. Let me know you thoughts.
dustintinsley said:
This module *should* hide you data usage while tethering, allowing you to have, in theory, unlimited tethering. I just threw it together and it is NOT fully tested to see if it 100% prevents monitoring of data usage. Let me know you thoughts.
Click to expand...
Click to collapse
Might be a good idea to share the methodology basics you are using instead of folks needing to install and stress test their limited tethering. From what I have seen on my T-Mobile account, creating a noprovisioning custom prop like this https://forum.xda-developers.com/pixel-3-xl/how-to/how-to-native-tethering-rooted-pixel-3-t3858662 is working and continues to work on Android 10.
sliding_billy said:
Might be a good idea to share the methodology basics you are using instead of folks needing to install and stress test their limited tethering. From what I have seen on my T-Mobile account, creating a noprovisioning custom prop like this https://forum.xda-developers.com/pixel-3-xl/how-to/how-to-native-tethering-rooted-pixel-3-t3858662 is working and continues to work on Android 10.
Click to expand...
Click to collapse
The method used is my module is exactly the same as your link, with the addition of also editing the T-Mobile APNs to add "dun" to the APN.
dustintinsley said:
The method used is my module is exactly the same as your link, with the addition of also editing the T-Mobile APNs to add "dun" to the APN.
Click to expand...
Click to collapse
Good deal. I have been hesitant to add DUN to the apn type since I am seeing no tethering charges. Mind you, I also use it so infrequently that even if they were to see my usage it wouldn't exceed my cap.
sliding_billy said:
Good deal. I have been hesitant to add DUN to the apn type since I am seeing no tethering charges. Mind you, I also use it so infrequently that even if they were to see my usage it would exceed my cap.
Click to expand...
Click to collapse
it seems to work very well with it added...
dustintinsley said:
it seems to work very well with it added...
Click to expand...
Click to collapse
Since I have everything else done already, can you send me the value string you have saved in the APN type?
Hey @dustintinsley, first I appreciate this little mod. Thank you.
I just flashed via TWRP, I will do some testing to see if it's working, but one thing you mentioned, it also adds dun. Well after I flashed and booted, I went to settings mobile data apn and reset the apn, and I'm not seeing ,dun under apn type. Should it be there? Or no?
Thanks Dustin
EDIT: ok, few hours later, after I flashed your mod in twrp.
I watched YouTube for like an hour straight, and I just got a notification saying I used a certain % of my hotspot data. So unless I did something wrong, it's being reported as hotspot and it's definitely not working for me..
I'm on the OnePlus 7 pro, Android 10 on T-mobile. With TWRP 3.3.1-70 by muaranofrio and magisk canary.
Please advise. Thank you again Dustin
No need to reset your APN after flashing. Can you take a screenshot of your APN settings? DUN should be there but I may have missed some APNs so a screenshot could help
dustintinsley said:
No need to reset your APN after flashing. Can you take a screenshot of your APN settings? DUN should be there but I may have missed some APNs so a screenshot could help
Click to expand...
Click to collapse
No problem, appreciate your time.
Ok I didn't reset. Here is the screens of the apn after I flashed your zip in twrp.
Is the module creating a new APN or attempting to modify the existing (grayed out) one?
Sheetzie03 said:
No problem, appreciate your time.
Ok I didn't reset. Here is the screens of the apn after I flashed your zip in twrp.
Click to expand...
Click to collapse
Odd. I will have a look at it. I am also on a OnePlus 7 Pro, but on Android 9 still. Maybe it is something with Android 10? I will have to install 10 and have a look.
sliding_billy said:
Is the module creating a new APN or attempting to modify the existing (grayed out) one?
Click to expand...
Click to collapse
Neither. Flashing the mod doesn't change anything in settings apns.
It's greyed out b4 I flash the mod, and greyed out after, with no changes either.
Understand?
---------- Post added at 09:35 PM ---------- Previous post was at 09:29 PM ----------
dustintinsley said:
Odd. I will have a look at it. I am also on a OnePlus 7 Pro, but on Android 9 still. Maybe it is something with Android 10? I will have to install 10 and have a look.
Click to expand...
Click to collapse
Thank you , sorry for trouble.
One other thing that I'm thinking might be important to mention, after flashing ur mod, while there are no changes made to the apn in settings, I did notice there are a bunch of different changes in the apns xml file in system-etc
Thanks again, I'll wait to hear from you. Later
Sheetzie03 said:
Neither. Flashing the mod doesn't change anything in settings apns.
It's greyed out b4 I flash the mod, and greyed out after, with no changes either.
Understand?
Click to expand...
Click to collapse
Yeah, that is exactly why I asked. Unless it is editable in the first place, the workaround I thought was always to create a new APN. Your screenshots looked like the module was trying to make in-place edits unsuccessfully.
sliding_billy said:
Yeah, that is exactly why I asked. Unless it is editable in the first place, the workaround I thought was always to create a new APN. Your screenshots looked like the module was trying to make in-place edits unsuccessfully.
Click to expand...
Click to collapse
Yeah I see what you mean.
But this mod is specifically for TMobile and the op has the same device as I do. Maybe it's Android 10. Although didn't you say earlier that on Android 10 there is a way to get it working?
Hope Dustin can work his magic anyway. ?
Sheetzie03 said:
Yeah I see what you mean.
But this mod is specifically for TMobile and the op has the same device as I do. Maybe it's Android 10. Although didn't you say earlier that on Android 10 there is a way to get it working?
Hope Dustin can work his magic anyway. ?
Click to expand...
Click to collapse
Yes, I am also on T-Mobile and Android 10 just with different phones (Pixel 3 and Pixel 3 XL). I guess I will stick with what is working. The link is further up in the thread.
Any update on this? Followed another thread here, but looks like there are known issues. I'm on OP6T Android 10 TMobile. Thanks!
SavakSYN said:
Any update on this? Followed another thread here, but looks like there are known issues. I'm on OP6T Android 10 TMobile. Thanks!
Click to expand...
Click to collapse
Same. Also Waiting for Dustin to update hopefully.
As far as the other thread, ill pm you.
Used it while at work today, and can confirm it's working on the OOS Q beta! Ran through about ~20GB of data today, and none was reflected in my hotspot usage. I will note, however, I was using a VPN on my phone all day as well, and everything still worked like a charm (don't know why it wouldn't). Thank you!!
Termux Bypass
I've done this for ever and it's not going to be restricted to who you have but it will 100 percent get around any data throttling.
Download Termux app and install openssh-server on it. Go ahead and hotspot your phone, then run ifconfig inside Termux to get your current tethering local IP. It will be the only 192. spit out when you run ifconfig. Save this. Run sshd -dD inside Termux which starts an openssh server waiting to be connected to in debug mode to audit traffic. Now pop onto a PC or router you can SSH into, whatever and connect it to your hotspot from your phone. Now SSH tunnel all the traffic from the device back through the openssh server your running on the Termux app. Now that you are on the same local network you can SSH tunnel into that IP address you saved earlier. As long as you make sure all your traffic passes through the tunnel it 100 percent shows that all your internet is being used by Termux app not your hotspot app so you need no other spoofing of hops or anything because to your phone and carrier you are just using a bunch of data in termux, you do it right you will never be throttled I've used 150GB data multiple times.
Step by step > https://github.com/RiFi2k/unlimited-tethering
RiFi2k said:
I've done this for ever and it's not going to be restricted to who you have but it will 100 percent get around any data throttling.
Download Termux app and install openssh-server on it. Go ahead and hotspot your phone, then run ifconfig inside Termux to get your current tethering local IP. It will be the only 192. spit out when you run ifconfig. Save this. Run sshd -dD inside Termux which starts an openssh server waiting to be connected to in debug mode to audit traffic. Now pop onto a PC or router you can SSH into, whatever and connect it to your hotspot from your phone. Now SSH tunnel all the traffic from the device back through the openssh server your running on the Termux app. Now that you are on the same local network you can SSH tunnel into that IP address you saved earlier. As long as you make sure all your traffic passes through the tunnel it 100 percent shows that all your internet is being used by Termux app not your hotspot app so you need no other spoofing of hops or anything because to your phone and carrier you are just using a bunch of data in termux, you do it right you will never be throttled I've used 150GB data multiple times.
Step by step > https://github.com/RiFi2k/unlimited-tethering
Click to expand...
Click to collapse
I've never used this before. I checked the instructions you linked, but they really don't add to the clarity of this part:
"Now that you are on the same local network you can SSH tunnel into that IP address you saved earlier."
Do you know of any video tutorial or anything that might help with this?