Database Develop

[Q] How to access LBSTESTMODE in Froyo?

In the past we were able to get to our GPS settings by opening dialer and dialing the following number. This will not call anyone - it is a code shortcut to the settings:
*#*#1472365#*#*
However, under Froyo 2.2 rooted with SU access, I am unable to get to LBSTESTMODE
I am having issues with my GPS not locking, it started after I rooted the Froyo. I was informed rooting is not what caused the problem in another thread....so been googling to fix the issue and ran into the old code above
Please advice
Regards

There is an app in the market called lbstestmode that works. The dial pad # to enter lbstestmode disappeared in jh7 and was still missing in ji6.

When I go to the market, the app is unavailable to me. I then went to the apps website and tried to get it to download using the samsung captivate browser but it kicked me back to same thing on the Apps Market
So, I am thinking is it possible somewhere in process of my upgrading and rooting the phone got locked accidently since I am new to the whole process of understanding development? (I have superuser access and ability to eliminate apps using titanium back up so its more of an elimination of issues question)
Regards

dayv said:
There is an app in the market called lbstestmode that works. The dial pad # to enter lbstestmode disappeared in jh7 and was still missing in ji6.
Click to expand...
Click to collapse
If you mean LbsTestModeLaunch, this was actually removed per Samsung's request.
As an alternative, you can download "Any Cut" from the Market, then create an activity shortcut for LbsTestMode.

aloant said:
If you mean LbsTestModeLaunch, this was actually removed per Samsung's request.
As an alternative, you can download "Any Cut" from the Market, then create an activity shortcut for LbsTestMode.
Click to expand...
Click to collapse
Thank You for your response
I was able to download the app. Would you please share or link how to create " a activity shortcut" for LbsTest Mode?
I am new to the whole process and dont want to create incidental problems for myself
Regards,

Roism said:
Thank You for your response
I was able to download the app. Would you please share or link how to create " a activity shortcut" for LbsTest Mode?
I am new to the whole process and dont want to create incidental problems for myself
Regards,
Click to expand...
Click to collapse
There seems to be 2 "Any Cut" apps - to be clear, the one I'm using is by "Jeff Hamilton."
In Any Cut, select New Shortcut, then Activity. It may take a while to load... Scroll and find LbsTestMode, then tap OK. You should now have a shortcut in your home screen.

aloant said:
There seems to be 2 "Any Cut" apps - to be clear, the one I'm using is by "Jeff Hamilton."
In Any Cut, select New Shortcut, then Activity. It may take a while to load... Scroll and find LbsTestMode, then tap OK. You should now have a shortcut in your home screen.
Click to expand...
Click to collapse
Thank you for your response. You have lit a path to enlightment for me ;-)
I found and created it. I will post my ability to resolve my GPS issue in next 24 hrs as I am now few beers down......with Oakland Raiders having a close game with San Diego Chargers.....
Regards,

So I was able to access the LbsTestMode based on instruction given and was able to fo through the following steps of "old instructions" that I was able to google......pasted below
•Step 1 -- Open menu > settings > Location & Security. Uncheck the box next to "Use Wireless Networks"
•Step 2 --follow the procedure in the "advice posted in comments above"
•Step 3 -- In the LBSTestMode menu, press “Application Settings” and change “Operation Mode” to “MS Based.”
•Step 4 -- In the LBSTestMode menu, find “SUPL/CP Settings” and change the SERVER & PORT to supl.google.com and port 7276 (DO NOT use www. in front of supl !)
•Step 5 -- Reboot your phone.
•Step 6 -- Open menu > settings > Location & Security. Check the box next to "Use Wireless Networks"
After follwing the steps above still no go? I used an app called GPS test to verify my location
Please advice
Regards,

Turn off SUPL Secure Socket as well. I am using AGPS Mode Control Plane. I've used both, this is where I've set it of late. Also, run the Get Position Test and see if it can lock on a position. Try to do this where you'll get a strong signal from many satellites (i.e., outside). Then leave LbsTestMode running, hit Home and open Maps. See if it can find your location. It should locate you assuming you got a good lock in LBSTestMode.
I've been openingLBSTestMode first and I leave it running in the background and then open Navigation. I haven't yet determined whether this has an actual benefit, is just a habit I don't want to break, or my own superstition, but that's what I do. There was discussion that some of the LbsTestMode settings don't persist after closing LbsTestMode, so this is one way to make sure the settings remain active.

The code in froyo is *#*#3214789650#*#*
this code doesn't seem to be disseminated too widely on the forums, spread the word

Thanks you all who responded on my issue. My issue has now been resolved
I was able to update my location and GPS is working fine
Regards

mobius911 said:
Turn off SUPL Secure Socket as well. I am using AGPS Mode Control Plane. I've used both, this is where I've set it of late. Also, run the Get Position Test and see if it can lock on a position. Try to do this where you'll get a strong signal from many satellites (i.e., outside). Then leave LbsTestMode running, hit Home and open Maps. See if it can find your location. It should locate you assuming you got a good lock in LBSTestMode.
I've been openingLBSTestMode first and I leave it running in the background and then open Navigation. I haven't yet determined whether this has an actual benefit, is just a habit I don't want to break, or my own superstition, but that's what I do. There was discussion that some of the LbsTestMode settings don't persist after closing LbsTestMode, so this is one way to make sure the settings remain active.
Click to expand...
Click to collapse
Hey thanks a lot this really worked well for me. I had just forced the update using mini Kies and still no luck with accurate GPS location but after I followed the steps outlined in lbstestmodelaunch and what you added I found my location was accurate to within a few meters.

The code in froyo is *#*#3214789650#*#*
this code doesn't seem to be disseminated too widely on the forums, spread the word
Spread the word, my GPS with your settings is accurate from 50 meters.. and it locks in 5 secs

The code in froyo is *#*#3214789650#*#*
this code doesn't seem to be disseminated too widely on the forums, spread the word

Original settings:
Operation Mode: Standalone
SERVER: www.spirent-lcs.com
PORT: 7275

oriveradel said:
The code in froyo is *#*#3214789650#*#*
this code doesn't seem to be disseminated too widely on the forums, spread the word
Click to expand...
Click to collapse
Actually, this works on my stock Eclair 2.1.

Working!
m7ia said:
The code in froyo is *#*#3214789650#*#*
this code doesn't seem to be disseminated too widely on the forums, spread the word
Click to expand...
Click to collapse
FWIW - the above didn't work in my 2.2'd Galaxy S, nor did the older code. I eventually got the Any Cut app (great!) and followed the instructions.
For the last 2 weeks, since the 2.2 update, I was basically unable to get any GPS lock. I did manage once - and it took 15 minutes, with 8 to 10 satellites available.
Now, with 2 or 3, I'm getting a lock in a few seconds.
If the main problem is that the web location setting for info is just flat-out wrong, why doesn't T-Mob just issue a fix for that? It seems very strange to me that this would continue to be an issue months after the rollout began.

Umm, there is SGS Tools in the Themes &Apps section that will allow access to it.
Sent from my GT-I9000 using XDA App

After this change, Google Maps = total crash???
So I did the change, and thought things were good. But about 3 out of 4 times, when trying to start Google Maps, it freezes, then the screen goes completely black, and there is a vibration-buzz, a pause, and two more buzzes. The phone appears totally dead. Only pulling the battery wakes it up.
To be clear, I changed the URL and port, and disabled the secure socket mode, as described in this thread. There was also and update of google maps received, which claims to have installed successfully.
So now GPS is great, but the main app I use it with is defunct.

LBSTESTMODE Not On Phone!
Before you say I know this is Samsung Captivate but I have no where else to post this.
I have a Samsung Galaxy Apollo i5801 on Orange UK and I do not seem to have the LBSTESTMODE menu when I create a activity via anycut or ADW launcher. I type in the LBSTESTMODE number on the dialler and nothing comes up, I did find however I had something called "Service mode" when I tried to launch LBSTESTMODE however this application crashed and said "android.something.something has crashed"
Please help me my I would really like to fix my GPS!
Info:
Carrier: Orange UK
Device: Samsung Galaxy Apollo i5801
Operating System: Android 2.2 Froyo
Baseband Version: I5801BVJP1
Kernel Version: 2.6.32.9 [email protected] #1
Build Number: FROYO.BVJPE
Hope That Helps!

Location services

I'm guessing that the reason many apps (i.e. Twitter, Weatherbug etc)won't install has to do with missing location frameworks. In most of these cases, the app even has allowances for functioning without location services. I'm guessing that if this problem has been solved before it's going to be one of the other devices sans GPS which has been hacked (so Pandigital Novel, Cruz tablet etc). Has anyone seen anything along these line? I'm doing some hunting around now.

quietglow said:
I'm guessing that the reason many apps (i.e. Twitter, Weatherbug etc)won't install has to do with missing location frameworks. In most of these cases, the app even has allowances for functioning without location services. I'm guessing that if this problem has been solved before it's going to be one of the other devices sans GPS which has been hacked (so Pandigital Novel, Cruz tablet etc). Has anyone seen anything along these line? I'm doing some hunting around now.
Click to expand...
Click to collapse
In Settings, there should be an option to use wireless networks for Location. Seemed to work fine on my Pandigital.

The NC has a modified settings panel and there's no location setting unfortunately.

Huh....well, I'll start looking into this once I get mine tonight as well.

It does appear to be the location services which were the problem, and this thread has a fix:
http://forum.xda-developers.com/showthread.php?t=861955
I just added a bunch of apps to the "work" list: basically all the stuff that didn't work because it required a location check.

what exactly needs to be done here?
quietglow said:
It does appear to be the location services which were the problem, and this thread has a fix:
http://forum.xda-developers.com/showthread.php?t=861955
I just added a bunch of apps to the "work" list: basically all the stuff that didn't work because it required a location check.
Click to expand...
Click to collapse
I see references to Twitter and a zip file containing many Google apk files but I do not see any explicit instructions on what needs to be installed.

quietglow said:
I'm guessing that the reason many apps (i.e. Twitter, Weatherbug etc)won't install has to do with missing location frameworks.
Click to expand...
Click to collapse
Huh?
My Twitter works fine. I never had an issue with it.

BigBadger said:
I see references to Twitter and a zip file containing many Google apk files but I do not see any explicit instructions on what needs to be installed.
Click to expand...
Click to collapse
Check here:
http://forum.xda-developers.com/showthread.php?t=861955

But does location services work?
I installed the suggested files and was able to install Google Latitude w/o problems. Problem is that location services is not working, and Latitude asks me to enable it via the device's settings. Of course B&N was kind enough to leave location services out of the modified settings page. Anyone have a solution for this?

You could try pulling settings.db (the same settings.db you have to change to enable nonmarket apps), and enable it there manually... then push it on the device again.

ixampl said:
You could try pulling settings.db (the same settings.db you have to change to enable nonmarket apps), and enable it there manually... then push it on the device again.
Click to expand...
Click to collapse
i tried this already. in the "secure" table in settings.db, i changed location_providers_allowed from gps to network. this had no apparent effect.
see http://developer.android.com/reference/android/provider/Settings.Secure.html
and http://developer.android.com/reference/android/location/LocationManager.html#NETWORK_PROVIDER

Have you tried checking the "use mock locations" box found in the development menu?
http://forum.xda-developers.com/showthread.php?t=862531

jazzcat007 said:
Have you tried checking the "use mock locations" box found in the development menu?
http://forum.xda-developers.com/showthread.php?t=862531
Click to expand...
Click to collapse
yeah. no dice.

Too bad there is no Bluetooth on board, would have been great to connect to a Bluetooth GPS !

webvan said:
Too bad there is no Bluetooth on board, would have been great to connect to a Bluetooth GPS !
Click to expand...
Click to collapse
Oh its there (semi-confirmed on Wifi chipset used).. The question is when will it be unlocked

Do not use the files in this thread. Use the one in listed in http://www.nookdevs.com/NookColor_Install_missing_google_geolocate_library
The com.google.android.maps.jar from the .zip in this thread doesn't work. Example: Flickster won't work.. once you use the right one, it does..

norkoastal said:
Oh its there (semi-confirmed on Wifi chipset used).. The question is when will it be unlocked
Click to expand...
Click to collapse
Really? Wow, that would be cool, has this been discussed in another thread?

webvan said:
Really? Wow, that would be cool, has this been discussed in another thread?
Click to expand...
Click to collapse
I believe this is an assumption based on the fact that it uses the same SoC as the Droid X.

ok, let's hope if the smart ones around here can bring BT to life !

Easy GPS bluetoothed from your Android Phones. No ADB needed.

1. Download and install "ShareGPS" from market on your phone.
once the app is installed
make sure in the App's setting, check "Use bluetooth" and "Create NMEA"
2. Download and install "Bluetooth GPS provider" from market on your tablet.
once the app is installed
make sure you have these settings:
in the app preferences
check "Force"
check "Raw HDOP"
GPS type is set to "MTK"
Update rate is set to "10Hz"
SBAS is Enable
Next
on your phone, open sharegps, then bring up the menu, click make discoverable once.
then go to your tablet, bring up the bluetooth gps provider app,
go in to the preference, click chose GPS provider, do a scan, you should see your phone come up.
click on it.
you are all set.
Now setup the bluetooth gps provider widget on one of your home screens.
every time before your run any navigation apps on the tablet just make sure you go back to your phone,
bring up shareGPS,
bring up Menu and click Make discoverable.
then go to your tablet, and click once on the bluetooth gps widget.
if the widget turns "green", you have working gps on your tablet.
if the widget turns "red", meaning that your devices aren't pair correctly, just re-scan/re-pair your devices.
*** Also make sure you have "Allow mock locations" checked as well on your tablet. And that's in menu, setting, application, development.
Enjoy
** edited
Found an issue with share gps, while it works fine on any 2.2 ROM on your phone, but the nmea output is way off in certain area on 2.3 based ROMs. After a little bit of researching, I found that BlueNMEA works very well.
You can find it in market, disregard the rating, the app is very easy to use and just may take a couple of tries to pair both devices.
So use blueNMEA instead of shareGPS on your phone..
Also fo for those who are not able to find these apps, here is how I did it..
Downloaded all apps from market on phone.
Use rootexplorer and look in /data/app
Find those apps, copy and paste onto your sd card.
Then transfer over to the tablet.
Install.

I cannot get my market to find "bluetooth GPS provider" even after preforming the market fix several times. Can you post the apk?

thebrain73 said:
I cannot get my market to find "bluetooth GPS provider" even after preforming the market fix several times. Can you post the apk?
Click to expand...
Click to collapse
Same here I only come up with network info II. But I see it in the market on my phone

I found it here http://www.filecrop.com/54831309/index.html
Working good for me on Vegan 5
thanks inbound
Edited for spelling, for some reason I was giving the western keyboard a second chance.

there is also tetheredGPS which started for the nook - has both client and server widgets included.
Works pretty well, over specific wifi port, and doesnt require both wifi and bluetooth to be on. power saver!

[Q] MY Phone Number

I have been successfully using the Verizon FIOS remote control app to control my TV FIOS STB and it is much nicer to use than the standard IR remote.
To get it to work originally using a nightly (circa 128), I had to persuade the Nook that it had a phone number as this is registered against one set in the STB. I did this by going into Settings/Call Settings/Additional Settings. This gives a network or SIM card error but when OK'd allow me to manually enter a phone number which then worked fine and continued to work through many nightly updates.
Something has now changed (I am currently on nightly 200) as I find that I have to re-register the FIOS app almost daily to get it to work.
On checking I find that the Phone Number setting gets lost periodically and set back to Unknown and I have to manually enter it again.
Does anybody know whether CM7 behaviour has changed with respect to the storage of the Phone Number? I realise it would normally be on a SIM, but it does seem to stick around for quite a while on the Nook before getting lost.

Any luck with this? I've been trying to figure out a way to do this for a while. I am unable to set a number as you described as all settings are greyed out. I'm also on nightly 200+. Seems like there would be a system file we could edit to fake the number, or something like that. Was thinking about setting up a SIP account to try it, but I doubt that will work.

dgibb2000 said:
Any luck with this? I've been trying to figure out a way to do this for a while. I am unable to set a number as you described as all settings are greyed out. I'm also on nightly 200+. Seems like there would be a system file we could edit to fake the number, or something like that. Was thinking about setting up a SIP account to try it, but I doubt that will work.
Click to expand...
Click to collapse
I have made some progress investigating this but have not got a final solution yet.
First, I can set my phone number up even though it is not a phone. I go into Settings, Call Settings, Additional Settings. The screen blurs and brings up a dialog box saying Call settings Error - Network or SIM card error. If I OK that then I see 3 menu items. The first 2 are grayed out but the 3rd "My Phone Number" is enabled. I select that and can enter a Phone Number. Are you saying you get the error and then all 3 options are grayed out?
Once entered I can view the Phone number via Settings, About Tablet, Status.
So far so good. The phone number setting does not normally survive a reboot, and also typically reverts to Unknown after a couple of days even without a reboot.
I have traced the Phone number setting to be stored in com.android.phone_preferences.xml which is in /data/data/com.android.phone/shared_prefs
But when the Phone number disappears it doesn't disappear from this file so there is some more complex interaction with trying to read a non-existent SIM first. So far I have traced the code involved to MyPhoneNumber.java and MSISDNEditPreference.java which are in the CyanogenMod-android_packages_apps_Phone-5d2764c.
I am still working on understanding this to see if there is some work-around to make the setting stick better. Currently I just have to check the phone number manually and set it again when it disappears.

Hmmm. When I go into call settings, all settings are greyed out except for internet call settings at the very bottom. I see the additional settings field you are speaking of but as its greyed out nothing happens if I click it. Weird.

dgibb2000 said:
Hmmm. When I go into call settings, all settings are greyed out except for internet call settings at the very bottom. I see the additional settings field you are speaking of but as its greyed out nothing happens if I click it. Weird.
Click to expand...
Click to collapse
Yes. That is strange. All my settings in Call Settings are enabled even though most are inapplicable. I don't think I have done anything to explicitly enable them and I'm on a standard Nightly 240 with the updated SystemUI.apk which turns off the phone signal bars. But I've never had these greyed out with any nightly build before.
Anybody else comment on whether their whole Call settings are enabled / disabled?
There is also a setting in build.properties in the system folder with a key called
keyguard.no_require_sim
I think this may have effect on how the OS treats calls which access the SIM. On my system this is currently set to 1. I might try playing with other values like true, 0 to see what effect that has.

Another theory as to why your call settings may be greyed out is that it they may get disabled in airplane mode.
Now this could be an issue even if you have set and subsequently cleared airplane mode as I believe the airplane mode setting doesn't go away entirely and can cause problems.
There is a command line way of clearing this setting completely which I did once when I set airplane mode on. Search for something like airplane sqlite to find the instructions.

That was it. I was stuck in airplane mode, and must have been for a long time. I used Android Assistant to clear the setting and it worked. I'm able to set my number and use fios mobile remote now! Thanks for your help.
Where did you get that updated systemui.apk to clear the cell signal bars? Now that I got the airplane mode off I have the signal strength there for no reason.

I got the SystemUI.apk from here
http://forum.xda-developers.com/show...60542&page=547
I just replaced the one in system/app. If you overwrite then you might get status bar forced close but a system reboot will sort that out and I haven't had signal bars since.
I've now put this in a zip that I can use to install after any nightly update I do as I've now found there is a wifi patch to deal with any remaining SOD issues although I haven't had one of those for a long time now.
Hopefully this stuff will get put into the main build before too long.

Looks like your link got clipped. Getting a page not found error.
Also, do you have any instructions on how to put the .apk into a zip for re-install after you do an upgrade? I'm assuming its not as easy as just ziping the file up?

Updated link
http://forum.xda-developers.com/showthread.php?t=960542&page=547
Yes. It is as easy as zipping the file up, but you have to create a matching folder structure to determine where the file goes. So in the case of the SystemUI file you create a folder called system containing a folder called app, put the file in the app folder and zip it so that system is in the root of the zip.
Correction: I thought that zip method was working but it wasn't. I had manually put the files in anyway and that worked OK. Then I was testing the zip, but it was actually failing.You need to put the files in a zip with the meta-inf etc. I think this link gives instructions
http://alldroid.org/default.aspx?g=posts&t=855
No. That doesn't work either as it uses an older method of scripting no longer supported. Apparently it needs to use Edify scripting now. It looks like some people add files to the gapps package, but I'm not clear yet whether it has to be re-signed, and I don't particularly want to redo gapps just to do this minimal patch.

I think I now understand how to produce an update zip that works.
I first took a gapp zip and stripped out all the existing files under system leaving the meta-inf alone. I put in the patch files in the appropriate folders under system. I then modified the updater-script in the meta-inf tree to just mount system, run package_extract_dir("system", "/system"); and unmount system with changes to the ui_print
I then signed the zip using the win-sign utility available here
http://forum.xda-developers.com/showthread.php?t=629151&highlight=sign+zip+files
I tried this out by first updating to nightly 246 and then applying my patch containing the SystemUI and the wifi driver that fixes SOD and that seemed to work OK.

Nexus 7 - WiFi Ad-Hoc fix for wpa_supplicant?

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)