Adhoc Solution(ish) (need some help)

I don't have an answer for you. However, I believe that entire issue is one that should be brought to the attention of Pandigital. The device should be keeping track of the access points that it connects to so that you don't have to re-enter information every time you change access points.

It does still remember the adhoc, it just can't see it or connect to it anymore.

you could write an .apk to modify or overwrite that file and run it on the PDN when you need to enable.orperhaps push the file to the same dir with a different name, then copy/rename it from Terminal on the PDN?

I was thinking the same thing. Basically, all it needs is a simple program that, when you want to connect to adhoc, you execute and it will copy the fixed file over the standard file. You would have to run it everytime you want an adhoc after using a standard AP, but it is a decent fix. Unfortunately, I have no idea how to write a program like that. Any help would be appreciated.

nchntrman;30431 said:

<snip>....then copy/rename it from Terminal on the PDN?

Click to expand...

What do you have to do to get the keyboard to pop up when in the Terminal on the PDN? That issue has been driving me batty!

The terminal in the development tools application doesn't have a soft keyboard. Download terminal emulator from the market.

Thanks for the reply. So far, every terminal emulator that I have gotten has refused to install. I'll keep trying to find one that works, and if I do, I'll post it in my online archives!

[quote name='sasherm13;30324]I managed to get my PDN to connect to my adhoc wifi network from my iPhone. However' date=' if I connect to a different network access point (my home network), the adhoc no longer works once the PDN network settings "remember" the second network. Here is how I did [URL=it:1)]it:1)[/URL] Pull the wpa_supplicant.conf from "/data/misc/wifi/wpa_supplicant.conf"2) Edit wpa_supplicant.conf in WordPad to look like this:ctrl_interface=data/system/wpa_supplicantupdate_config=1eapol_version=2ap_scan=2fast_reauth=1WiFiAdHoc=1network={ ssid="Network Name" key_mgmt=NONE mode=1}3) push the wpa_supplicant.conf back to "/data/misc/wifi/wpa_supplicant.conf"I have tried using chmod to prevent android from editing the file to remember new networks, but that prevents wifi from turning on.Pretty much, I can get the adhoc network to work, but I cannot connect to any other network after that for fear of losing the adhoc and having to repeat the steps above.Can anyone figure ourt how to make this permanent.[/QUOTE'] Try adding this curly brace, as it will cover all the cases (adhoc and infrast)# Catch all example that allows more or less all configuration modesnetwork={ ssid= scan_ssid=1 key_mgmt=WPA-EAP WPA-PSK IEEE8021X NONE pairwise=CCMP TKIP group=CCMP TKIP WEP104 WEP40 psk="very secret passphrase" eap=TTLS PEAP TLS}

sasherm13,I think this will enable it to connect to adhoc netowrk.In file: RT2870STA.dat file change the parameter:NetworkType=Infrato NetworkType=Adhoc

I was tinkering briefly with an app that would let you swap between two sets of config files. One for infrastructure and the other for adhoc. The main problem I ran into was that the system.img is mounted read-only. I could only change wpa-supplicant and RT2870STA.dat after I did a remount with adb. I don't know how to get root permissions for my app so that it can do a remount, copy (cat and redirect script to file since there is no copy), then remount ro. I think this should still be able to be done with two shell scripts if nothing else.

Okay, I think I might have a solution.I will put the fixed wpa_supplicant.conf file in the /data/misc/wifi folder and name it wpa_supplicant.conf.fixed alongside the standard wpa_supplicant.conf file.Then, using GScript Lite, I created a script that when executed will delete the standard conf and copy the fixed conf in place of the removed standard. This way, after connecting to a standard AP and losing the ability to use adhoc, I only need to run the script and the PDN is ready for adhoc. The script will look like this:cd /data/misc/wifirm wpa_supplicant.confcat wpa_supplicant.conf.fix &gt wpasupplicant.confI will try this once I am home from work and let you know how it goes.

I think this solution will let you change to adhoc mode, but you probably also want to change back. I think you want two scriptsadhoc-mode.shcd /data/misc/wificat wpa_supplicant.conf.adhoc > wpa_supplicant.confinfra-mode.shcd /data/misc/wificat wpa_supplicant.conf.infra > wpa_supplicant.confDo you need to do anything with RT2870STA.dat? Also, is wpa_supplicant supposed to be in /system/etc/wifi/wpa_supplicant.conf?If it's in the writable /data partition, I can write an apk that will switch this.

The wpa_supplicant.conf is in /data/misc/wifi. I think the one in the /system tree is purely a template as I have tried messing with it to no avail. Switching back to standrad APs is not an sisue. I can be hooked to the adhoc and the connect to an AP, but not the other way around. But I think that having the ability to switch back and forth would be great as well, just in case there is a problem. If you can make an apk that will do that on the fly that would be great. Also, I think you might have to turn off wifi when switching to the adhoc config then turn it back on in order for it to work. Not really sure about that yet.

what is the absolute true fix for this? Would the driver for the wireless card need to be rewritten to support ad-hoc?

what is the true fix for this ad-hoc issue? would the driver for the wireless card have to be re-written to support ad-hoc?

Th true fix would be to have pandigital fix the problem in new firmware.

geebekazoo;30452 said:

What do you have to do to get the keyboard to pop up when in the Terminal on the PDN? That issue has been driving me batty!

Click to expand...

press and hold the menu button. again to close keyboard. this is a function of the volume keys hack.

walscobry;31018 said:

press and hold the menu button. again to close keyboard. this is a function of the volume keys hack.

Click to expand...

With the basic, built-in terminal, doing that only gets you a 4 entry menu screen. There is no keyboard popping up, and no menu option to make a keyboard available.