Related
First of all, while this is my first post, I have been a silent browser of xda for some time. This is such a wonderfull site.
My question is, is it possible to somehow get the settings for sideloading and usb/wifi teathering to show up in the settings menus? I assume that these have been removed or hidden somewhere in the source by commenting out or just been deleted. It seems to me that since these functions were built in to other android devices and I assume the I9000, that it sould be possable to reverse there removal. The settings.db has so many referances to other settings that are easily changed that it sould not require root access correct?
Now I must say that I am in no way a developer, and am not very good with linux. These are just some thoughts and conclutions that I have come up with while reading and pondering over countless articals on xda
Finaly , I want to say that I strongly disagree with Att's position on removing these items to increase there bottem line, and I would be with T-Mobile if they had good coverage in my house.
Usb tether is listed - called Pc internet. Sidwloading can be achieved by rooting and changing a settings.db file but no one has a fix for making it show up.
Sent from my SAMSUNG-SGH-I897 using XDA App
I am aware of the option to enable sideloading in the settings.db, all im saying is that there must be a way to but the option back in the settings menus. As for the USB teathering, isnt there an option on other devices to enable disable?
perhaps this thread would be better if it was moved to development?
djpittsford said:
I am aware of the option to enable sideloading in the settings.db, all im saying is that there must be a way to but the option back in the settings menus. As for the USB teathering, isnt there an option on other devices to enable disable?
perhaps this thread would be better if it was moved to development?
Click to expand...
Click to collapse
a) the sideloading thing is ATT and that will never show up in one of their phones (unless they somehow miss it) if you really want it THAT badly, you can flash eugene's vibrant hybrid and it's there
b) USB tether is directly available through the settings menu on stock firmware (looks like ATT missed it, because they had it removed in JH2 and JH3)
c) if you mean the WIRELESS (mobile access point) tethering, that was removed by ATT and we've already found workarounds to have it back.
d) this certainly does not belong in development, thanks for keeping it out of that forum
e) look at SRE, it contains basically all the things you're asking for
I'm sorry if this has already been debated elsewhere. I did search and try to locate threads on this already, but didn't come up with anything which (seemed) relevant to this problem.
If anyone has a link handy for another thread which already discusses this, I'll close the thread if that is wanted.
With that said... Here's my issue.
As stated elsewhere, one of the main things which excited me about Gingerbread was the ability to do native SIP dialing. About time, I say! Now I've flashed Gingerbread on my SGS and so far the results has been below underwhelming.
From what I can tell this is how you get SIP/VoIP/Internet calling on your phone using Gingerbread:
1. Sign up for Google Voice.
2. Install Google Voice and sign in.
3. Voila. Your Gingerbread Android-device now has a bunch of SIP settings and options.
This is ofcourse, unless your manufacturer has somehow crippled your phone's software.
That might be the case with Samsung's firmware, but I wouldn't know because the steps outlined above is absolutely impossible for anyone outside the US. You cannot sign up for Google Voice anywhere else. End of story.
So. Is this for real? Did Google release a smartphone OS for worldwide consumption, touting "native SIP", native internet calling as feature and then implement it in a way which means it will only work in one country, all else be damned?
I seriously find this very hard to believe. There has to be a way to get this functionality up and running otherwise. Seriously? The internet maestros at Google implements a core OS-level function tied to (one) geo-location? Is third-party solutions ala Sipdroid the solution for everyone else?
So... Please tell me I am completely mistaken and that there are steps for getting SIP running on my phone, despite me not have an adress of residency ending in "US".
Any hints or links in any direction so that I can actually get to try this out would be über appreciated.
Bump.
I realize posting this while Europa were getting ready for sleep and only US-people were around might have been bad timing.
Just bumping this again to see if there's any more response. I can't seriously be the only one wondering about this.
If bumping is severely against forum policies, let me know and I'll make a note of it and wont do it again.
http://forum.xda-developers.com/showthread.php?t=1043016
Use this zip as an update from CWM recovery, enables the menu "Internet call settings" under "Call settings".
Works on odex and deodex ROMS [I have the same JVB as the OP]
Problem solved
Thanks Vinnie.
Since I already have some framework-res.apk dependent mods, I just pushed the permissions-file as mentioned in that thread, and now I have "Internet calling options" available.
Yes, I realize this will only work while on wifi and SIP over 3G will be disabled, but at least it gives me something to experiment with so that later I will know if handing over my other mods for 3G VoIP/SIP will be worth it.
Thanks for the response and handy link. Now if XDA had better search, I might not have needed to pollute the forums with duplicates like this
Edit: Checked the entire thread and saw that there is an update.zip with eyecandy as well. Will try it out later.
Yep, I'm a newb.. but what's new? ;p
I will try to keep this as short and informative as possible so that I can get some of you to help this gal out- In need of pro advice and amateur instructions..! I know I know I am sure you all get sick of damn newbies cramping your sexy geeky style..
Anywhoozer,
I purchased an unlocked, rooted, and euro flashed 7 inch Galaxy Tab from Ebay
(Which is likely mistake #1!)
I was ultimately looking for a tab with internet and voice calls- the tab has the calling feature but no internet. Says I am connected to the EDGE network but cannot connect to market, login to email, set up accounts, etc. (Just an added note, I could care less about 3g/2g/10g/whatever! I just want internet, speed is nice but not necessary) So the major issue here is when attempting to use the browser, I am redirected to Tmobiles website.
Yes, I have googled "T-mobile redirect" but let's just save time and space and call me dumb
Moving on..
I contacted the seller, he said to download and install root explorer, I did, correctly, (thankful for kindergarten instructions found online) but it did not change anything.
Perhaps you could help me. Here is what I have collected while browsing relative issues via google..
Apparently I need a modem switcher? (How, what?)
Or do I need to change or "fake" the APN settings? (repeat)
Is my tmobile "phone" sim card (which includes a data plan) compatible?
blahblahblahblahblah.. and everything else you have heard before
P.S HELP?
try to get a config sms from your provider... this could help to set up your apn and browser config
gtUser1000 said:
try to get a config sms from your provider... this could help to set up your apn and browser config
Click to expand...
Click to collapse
How do I do that?
LOL
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)
I tried the old Lollipop trick - using an sql editor to dig in /data/data/com.android.providers.settings/databases/
Now, when I looked in that directory, it was empty. Looks like they moved those settings elsewhere to try to force more people to pay carrier tethering extortion fees.
Anyone know how to get a Marshmallow Nexus 6 to tether? Without paying? Hold the sanctimonious lectures.
yes, i tether every day, no issues. but my tmobile plan includes 7gb tethering. if you want to tether illegally, go back to lolipop. oh, btw, i dont have to pay for tethering, as tmobile lets me tether enough, legally.
What's illegal about tethering? The FCC already told Verizon that tethering was not illegal, nor is it theft. Contrary to popular belief, I too pay my phone bill. What's so magical about tethered bits that makes them such a burden on the carriers compared to non-tethered bits?
meldroc said:
I tried the old Lollipop trick - using an sql editor to dig in /data/data/com.android.providers.settings/databases/
Now, when I looked in that directory, it was empty. Looks like they moved those settings elsewhere to try to force more people to pay carrier tethering extortion fees.
Anyone know how to get a Marshmallow Nexus 6 to tether? Without paying? Hold the sanctimonious lectures.
Click to expand...
Click to collapse
No lectures. Flash Chroma 6.0 As of now if is basically a stock ROM with very very few baked in goodies.
I just edited my build prop... Same as lollipop
meldroc said:
What's illegal about tethering? The FCC already told Verizon that tethering was not illegal, nor is it theft. Contrary to popular belief, I too pay my phone bill. What's so magical about tethered bits that makes them such a burden on the carriers compared to non-tethered bits?
Click to expand...
Click to collapse
its legal unless you have unlimited data. then its legal for the providers to put limits on tethering. tmobile offers all their limited plans unlimited tethering, but their completely unlimited data plans get only 7gb tethering. why only 7gb? because its meant for your mobile devices, not to add data to your home internet. read the law, understand it, instead of just listening to what others are saying. magical, nothing. but those that are tethering for their home internet are ruining the services for others. anyways, im not innocent, but i actually know what the law says. and it is stealing.
I'm on jdx 4.0 on cricket. I tether no problem and cricket says you can't tether.
I tried editing build.prop and changing apn to ipv4 but no luck... Not sure if I was doing it right, I used to do the database edit with sql editor. Can anyone post what needs to be changed/added?
as long as your carrier allows it, Use Root Browser to edit build.prop open with RB Text Editor and add net.tethering.noprovisioning=true at the bottom. Save reboot
jasonftfw said:
I tried editing build.prop and changing apn to ipv4 but no luck... Not sure if I was doing it right, I used to do the database edit with sql editor. Can anyone post what needs to be changed/added?
Click to expand...
Click to collapse
you need to set SElinux to be permissive in marshmellow to edit system files. many dont know this, since their custom kernels have it set to permissive already. but you can get an app(not at the play store) or set it via terminal emulator.
simms22 said:
you need to set SElinux to be permissive in marshmellow to edit system files. many dont know this, since their custom kernels have it set to permissive already. but you can get an app(not at the play store) or set it via terminal emulator.
Click to expand...
Click to collapse
How can I check my selinux? I thought it was supposed to be listed in about device, or did that move to somewhere else in the new OS?
jasonftfw said:
How can I check my selinux? I thought it was supposed to be listed in about device, or did that move to somewhere else in the new OS?
Click to expand...
Click to collapse
its set as enforcing by default. i dont think theres a setting anywhere to check though.
---------- Post added at 04:22 PM ---------- Previous post was at 04:20 PM ----------
i posted a link to a SElinux app in this thread.. http://forum.xda-developers.com/nexus-6/general/issues-editing-build-prop-marshmallow-t3222551
I edited build.prop in recovery and can tether fine.
Sent from my Nexus 6
Works fine on LightRom with T-Mobile for me.
After I edit build.prob and reboot, my tablet will connect to the hotspot, but it had the exclamation over the WiFi icon and won't connect to anything. Any ideas?
meldroc said:
I tried the old Lollipop trick - using an sql editor to dig in /data/data/com.android.providers.settings/databases/
Now, when I looked in that directory, it was empty. Looks like they moved those settings elsewhere to try to force more people to pay carrier tethering extortion fees.
Anyone know how to get a Marshmallow Nexus 6 to tether? Without paying? Hold the sanctimonious lectures.
Click to expand...
Click to collapse
No they are there in the same place, app needs to be updated to be able to see them or something. I tried different apps, was able to see them with one, forgot which one, but wasn't able to edit with the app.