Database Users

Froyo ROM

Hi there,
I made a preliminary port of Froyo for the Liquid.
It needs the Donut radio rom, so it won't work on LiquidE.
You can test it on an Eclair radio, but usb and GSM/3G won't work.
IHMO, It works fine for daily use (I do use it daily.), current known bugs:
-Random lines appearing on the screen on refresh
-No wifi
-Wiping data kills radio
-No tethering
-Unsigned
Hint: to enable App2SD to all apps (by default, only some apps accept it), do
Code:
pm setInstallLocation 2
This will install all apps to SD, you can move them back to phone.
Please use http://code.google.com/p/acer-liquid-froyo/issues/list as bugtracker
(Donate link in my sig also works for my Liquiid's work )
Here's the downlink link:
http://code.google.com/p/acer-liquid-froyo/downloads/detail?name=Froyo.zip
Update:
Full: http://www.megaupload.com/?d=S9P799GO
Update: http://www.megaupload.com/?d=UPAF7YD8
-880MHz
-ramzswap
-USB OTG (seems not fully working)
-working iptables (droidwall works)
-usbnet (tethering kind of works)
-changed H264 resolution limit to 720p
To get tethering working, do echo 1 > /sys/class/usb_composite/rndis/enable
Then go in the appropriate menu and tick the usb tethering option.
The results are random, I don't know why yet. The released sources might help understanding that.

How can I enable apps2sd? Where have I to insert code? I'm a noob and don't understand, I need a step by step sequence.
Thanks.

akira.pwr said:
How can I enable apps2sd? Where have I to insert code? I'm a noob and don't understand, I need a step by step sequence.
Thanks.
Click to expand...
Click to collapse
Install connectbot
Launch it on the "local" protocol, do
su
(the su manager will ask for permission, allow it)
pm setInstallLocation 2
And it's done.

Ok, i'm doing it, it create a partition for apps?
After doing what you posted above, all apps go in my sd automatically?
Connectbot asked me a nickname, i put su, then un screen i writed pm setInstallLocation 2, then i saw the word "killed", is normal?
Superuser never asked me permissions.
Edit: retried more times and finally su requested permissions, i allowed but after insert the code, i read "killed"...

akira.pwr said:
Ok, i'm doing it, it create a partition for apps?
Click to expand...
Click to collapse
Apps go to the normal vfat partition
After doing what you posted above, all apps go in my sd automatically?
Click to expand...
Click to collapse
It should
Connectbot asked me a nickname, i put su, then un screen i writed pm setInstallLocation 2, then i saw the word "killed", is normal?
Superuser never asked me permissions.
Edit: retried more times and finally su requested permissions, i allowed but after insert the code, i read "killed"...
Click to expand...
Click to collapse
You must put su on the console, not as a nickname, the nickname doesn't mean anything.

sorry, but i'm not good, i don't understand how to do it, i put code, but when i put "2", i read proces denied. I give up...

akira.pwr said:
sorry, but i'm not good, i don't understand how to do it, i put code, but when i put "2", i read proces denied. I give up...
Click to expand...
Click to collapse
Giving up is always a lot easier than to keep on trying, \0/(stole the emote from phh lol)

rafyvitto said:
Giving up is always a lot easier than to keep on trying, \0/(stole the emote from phh lol)
Click to expand...
Click to collapse
But i'm a real noob, i tried and retried, but connectbot tells me action denied, any suggestion? When/where have i do su? It never ask me permission.

akira.pwr said:
But i'm a real noob, i tried and retried, but connectbot tells me action denied, any suggestion? When/where have i do su? It never ask me permission.
Click to expand...
Click to collapse
Weird..check on malex recovery to see if your device is rooted, without root you cant run superuser command's, but since your running phhfroyo it should come already rooted...

Easiest 4G Wimax Fix [Possibly]

I'd been having problems with 4G being stuck in scanning mode after 1.47 ROM updates and almost lost all hope when no solutions seemed to work.
UNTIL!!!!!!
1. Flash your 1.47 based ROM of choice.
2. Make sure 4G is turned off and boot into recovery and install latest Radio (http://forum.xda-developers.com/showthread.php?t=715485) and update profile then update PRL.
3. Make sure 4G is turned off and boot into Recovery and install latest Wimax Radio (http://forum.xda-developers.com/showthread.php?t=715485) and update profile then update PRL.
4. DELETE TREE.XML FILE IN THE FOLLOWING DIRECTORY: /data/misc/wimax/
How you delete this file is totally up to you. I personally deleted using adb shell, but Root Explorer from the Market should work as well.
5. Reboot & Turn on 4G
At this point the tree.xml file will be automatically generated and hopefully you will have full functioning 4G.
Good luck!

I will second this!
After i updated to Fresh's newest this morning I ran into this is as well. I used root explorer to delete the tree file and voila, functioning 4g goodness.

Worked for me as well! I'm glad it's this easy! Although, I just used ADB instead of Root Explorer, but they both work the same.

I thought the easiest way was to use Whitslacks start over method?

can someone post the adb commands for us cheap (don't want to spend the $ on root explorer) n00b's?

tx_jaycee said:
can someone post the adb commands for us cheap (don't want to spend the $ on root explorer) n00b's?
Click to expand...
Click to collapse
adb shell [enter]
cd /data/misc/wimax/ [enter]
rm name_of_your_tree_file.xml [enter]
[enter] = hit the enter key on your keyboard

tx_jaycee said:
can someone post the adb commands for us cheap (don't want to spend the $ on root explorer) n00b's?
Click to expand...
Click to collapse
here you go:
To figure out what your mac address is/file name is called:
Code:
adb shell
ls /data/misc/wimax
this will list all the files and folders in the wimax folder. look for the one ending with .tree.xml
Then to remove the file (assuming you're still in shell-denoted by the # sign):
Code:
rm data/misc/wimax/############.tree.xml

I wish someone could find a fix for the less common problem of 4g dropping and not reconnecting:
http://forum.xda-developers.com/showthread.php?p=7206162&posted=1#post7206162

Thanks initial. I'll have to wait till I head into town tomorrow. No 4G in the burbs yet.

If you say 4G works, can you say if you can connect, leave the 4G area for a little while, re-enter the 4G area, and have the phone re-connect 4G without getting stuck on "Scanning" or "Obtaining IP?"

I did the whitslack method flash DC 3.2.3 everything works great only problem I'm having is everytime I leave 4g area I have to reboot for 4g to work this goes for wifi wont start unless reboot Bluetooth wont conect unless reboot. Can someone please confirm if this is only on rooted roms or both stock and rooted.
Sent from my PC36100 using Tapatalk

initial said:
here you go:
To figure out what your mac address is/file name is called:
Code:
adb shell
ls /data/misc/wimax
this will list all the files and folders in the wimax folder. look for the one ending with .tree.xml
Then to remove the file (assuming you're still in shell-denoted by the # sign):
Code:
rm data/misc/wimax/############.tree.xml
Click to expand...
Click to collapse
If you want to delete the tree you can just use a wildcard without listing the directory first:
Code:
adb shell
rm data/misc/wimax/*.tree.xml

Good call, this is even easier. no need to list the directory anymore.

ewilson said:
I did the whitslack method flash DC 3.2.3 everything works great only problem I'm having is everytime I leave 4g area I have to reboot for 4g to work this goes for wifi wont start unless reboot Bluetooth wont conect unless reboot. Can someone please confirm if this is only on rooted roms or both stock and rooted.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
I don't think you're alone:
http://forum.xda-developers.com/showthread.php?t=717307

Holy ****ing ****. I've tried everything, and this actually worked? I ****ing love you. Kudos, man.

Posted here: http://forum.xda-developers.com/showthread.php?t=717307&page=3
swatspyder said:
I need someone to confirm, but I believe I found a FIX!!!
Requirements:
Your MSL code (See Here: http://forum.xda-developers.com/showthread.php?t=697487)
Instructions:
Turn OFF your 4G radio if it is turned on!
1) Click on phone and dial ##DATA# (##3282#)
2) Click on "Edit Mode"
3) Type in your MSL code (see above if you don't have it yet)
4) Click on the menu entry "WiMAX"
5) Scroll down the list and click on "WiMAX_Scan_Retry(s)"
6) Enter the number 15 and click "OK" (This equals 15 seconds instead of 300 seconds)
7) Scroll down the list and click on "WiMAX_Entry_Delay(s)"
8) Enter the number 0 and click "OK" (This equals 0 seconds instead of 300 seconds)
9) Press the "Menu" key and click on "Commit Modifications"
10) Grab a cup of coffee, get a bite to eat, or sit back and wait for your EVO to restart
Testing:
1) Go to your phone's settings and click on "Wireless & networks"
2) Scroll down and click on 4G settings
3) Click on 4G to turn it on and wait for the status to change to "Connected to Sprint"
4) Without touching any of the menu items, cover the top half of your phone with your hands until the status changes to "Scanning..."
5) Uncover the top of the phone and count the seconds until it says "Connecting to Sprint"
6) Realize that you no longer have to cycle the 4G radio to reconnect
Result:
After modifying my EVO and my girlfriend's EVO and inputting these changes, the phone will reconnect to the 4G tower in as little as 20 seconds!
Yes, 20 seconds, the most I have seen so far is 30 seconds after dropping the connection. This is a HUGE improvement over the 5+ minutes to reconnect (300+ seconds).
Click to expand...
Click to collapse

mrkmrk said:
Holy ****ing ****. I've tried everything, and this actually worked? I ****ing love you. Kudos, man.
Click to expand...
Click to collapse
Ditto.
I tried to skip a step because I was lazy and didn't work. Started from the begining and IT WORKED.

Just to clear things up, this will not fix any bad MAC addresses.
This is just a soft fix to get roms working (given that your MAC has not been corrupted)

Neotelos_com said:
Just to clear things up, this will not fix any bad MAC addresses.
This is just a soft fix to get roms working (given that your MAC has not been corrupted)
Click to expand...
Click to collapse
How do I fix the corrupted mac address? I think that may be what my problem is.
Edit: Nevermind, this fixed the problem; I have a weak signal in my house and it's still as bad as before the original wimax radio.

I have tried the method of the original poster and still have no luck. I rooted my phone after the OTA update using the simple root method. Prior to root my 4G was working.
I then installed BakedSnack 9.6 and since then 4G just sits on scanning. I have installed the latest radio/wimax roms multiple times and done everything else to no luck.
Can someone with a now working wimax post their output from logcat when they enable it. There is a thread in Q&A here: http://forum.xda-developers.com/showthread.php?t=725773 that explains the issue some of us are seeing.
For me and others with issues Logcat showing the error: E/Wimax ( 274): <DCP> Bad return status 0xffffffff
To capture a logcat connect do the following in adb:
Code:
adb shell
logcat > \sdcard\logcat.txt
immediately start wimax and leave it until it connects
You can now hit CTRL+C to kill logcat
The output of the logcat will be written to a text file called logcat.txt on the root of your sdcard instead of just scrolling by on your screen.
If someone here could do this it would be much appreciated and might help those of us still having issues.

[Mod] Native WiFi Tethering MobileAP port from Galaxy S i9000 - Infrastructure AP!

According to the Vibrant forums, Jr33 has fixed and ported the MobileAP (native Infrastructure Wifi Tethering AP) from the Galaxy S i9000 to the Vibrant:
http://forum.xda-developers.com/showthread.php?t=756804
Why this is important and better than the Wifi tethering apps (Barnacle and android-wifi-tether):
This is REAL infrastructure mode. Not the hacked up ad-hoc mode (which android-wifi-tether and barnacle uses) which A LOT of devices (other android phones, ps3, wii, corporate laptops included) cannot connect to.
Because it being infrastructure mode, it supports WPA, a much more secure protection than WEP.
This is natively built into the Galaxy S i9000 phones. But taken out by AT&T and T-mobile. It just works, and works well - because it was MADE for our phones!
android-wifi-tethering hard crashes a lot on start, forcing you to do a battery pull, and may lose connectivity every so often.
Barnacle requires you to change the MTU of your client device, not possible in a lot of cases (consoles, phones, etc), and may cause conflicts when moving to a different wifi AP.
-------------------------------------------------------------------------------------------------------------------------------
Update 8/22:
Designgears has figured out a way to automatically launch the wlp2pservice on boot, therefore, no more manual entry is needed (but requires kernel flashing). Please see:
http://forum.xda-developers.com/showthread.php?p=7785171
The reason why it requires flashing the kernel (while Vibrant did not) can be explained by Jr33:
i know the stock kernel for the vibrant had the iptables included as well as wlp2pservice. what i have been finding is all these different features have just been commented out in different places. the same source was used for all three phones. you can see this when you start decompiling the odex files and comparing files, it is all the same. just needs a little tweaking here and there to activate certain features
Click to expand...
Click to collapse
-------------------------------------------------------------------------------------------------------------------------------
Update 8/20:
With the help of Jr33 (person that did the port to Vibrant), we *kind* of got it working with a few hoops. Jr33 should be given credit as he created and repackaged the captivate MobileAP update.zip; I was merely a test dummy. This thread will be locked when a solution is made and Jr33 will create a new thread with the final version. Go buy him a red bull!
REQUIREMENTS
Update.zip downloaded below
Rom Manager
ClockworkMod Recovery flashed on your phone (using Rom Manager)
Busybox
An Android Terminal App (ex: http://www.appbrain.com/app/jackpal.androidterm)
DOWNLOAD The Captivate mobileAP update.zip:
http://www.mediafire.com/?ownoqzgo6cbtmoj
File is also attached at the end of this post.
INSTRUCTIONS
Rename to update.zip, put it on your INTERNAL SD card root
Boot into ClockworkMod Recovery (using Rom Manager) and reinstall/update packages.
Reboot - note: first time boot after updating this will take a little while.
Now go into an Android terminal app and type the following:
Code:
su
busybox nohup /system/bin/wlp2pservice &
This starts the wlp2pservice. (Props to designgears for finding out this new command)
Old command (just typing in /system/bin/wlp2pservice in terminal (does not require busybox)) works BUT you will need to keep Terminal open during the duration, if force closed, you will have to retype that command in again.
5. Now you can go into Settings -> Wireless and Networks -> Mobile AP Settings to start your Access point.
Note: if you change any of the settings (AP name or WPA password) it may crash wlp2pservice. Use a task manager to force close "MobileAP Settings." Do step 4 again and your settings should be there.
This works until you reboot your phone. If you reboot, you need to go back into terminal and manually start wlp2pservice again (do step 4 again).
If you do not manually launch wlp2pservice, when you open up MobileAP settings, it just sits there on a black screen and if you check logcat, you see the looping message pasted below. We are currently trying to fix the necessity of manually launching wlp2pservice. This is not how it was intended to be.
-----------------
Developers with a Captivate, we need your help:
Upon opening MobileAP settings WITHOUT manually launching wlp2pservice in terminal, yields the following (from logcat):
Code:
I/ServiceManager( 3459): Waiting for service WLP2PService....
It loops until you force close "MobileAP Settings" in your task manager. Something is not calling wlp2pservice to execute.
Also, rebooting the phone or closing/ending terminal (on the pc or phone) requires you to go back into terminal and execute wlp2pservice manually, otherwise opening MobileAP settings yields the same loop above.
I am guessing that wlp2pservice is not launching on boot, or not executing at all when you open up MobileAP settings. I'm not sure which is supposed to happen.
This *seems* like an easy fix, and because Jr33 does not have a Captivate it is hard for him to help troubleshoot this. This is why we need other people to help figure out a way.

According to the front page: Update: This is a mod to add in the Samsung version of Mobile AP intended for the Galaxy S, but was removed by T-Mobile.
It was also removed by ATT, so wonder if it is possible :/

andy2na said:
According to the front page: Update: This is a mod to add in the Samsung version of Mobile AP intended for the Galaxy S, but was removed by T-Mobile.
It was also removed by ATT, so wonder if it is possible :/
Click to expand...
Click to collapse
This would be excellent to be ported over. While the current wireless tether (found in the associated thread) works... it does it in ad-hoc mode. This apparently supports infrastructure mode which would make it even more useful.
Go mods go!

rickgrob said:
This would be excellent to be ported over. While the current wireless tether (found in the associated thread) works... it does it in ad-hoc mode. This apparently supports infrastructure mode which would make it even more useful.
Go mods go!
Click to expand...
Click to collapse
wireless tether and barnacle "work" but still require you to go through hoops.
Wireless tether hard crashes A LOT.
Barnacle requires you to change MTU in your OS.

Please see OP for Update.

andy2na said:
wireless tether and barnacle "work" but still require you to go through hoops.
Wireless tether hard crashes A LOT.
Barnacle requires you to change MTU in your OS.
Click to expand...
Click to collapse
Yeah i changed my mtu (took like 30 seconds) and barnacle works great now. I was able to register for my fall semester from disneyland last weekend

I hope this isn't too far off topic, but would it then be possible to use a similiar techique to restore usb tethering to captivate ROMS in which AT&T has it removed/disabled?

jsmith8858 said:
I hope this isn't too far off topic, but would it then be possible to use a similiar techique to restore usb tethering to captivate ROMS in which AT&T has it removed/disabled?
Click to expand...
Click to collapse
When did it get removed? And i doubt the mobileAP is anywhere near related to the USB tethering samsung includes.

I currently have the stock rom, it has usb tethering. Mobile ap is related since they're both tethering.
Perhaps I can extract the file out of my phone where I to be instructed how.
Sent from my SAMSUNG-SGH-I897 using XDA App

Bowsa2511 said:
I currently have the stock rom, it has usb tethering. Mobile ap is related since they're both tethering.
Perhaps I can extract the file out of my phone where I to be instructed how.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I guess if you want to be completely broad they are both tethering solutions....
But their implementation i would assume is different and dont affect each other.

thanks Andy for bring this to Jr33's notice to get this implemented for Captivate.
was wondering if there is any app which wld start this service on boot or something like Tasker if it can start a system service.
Thnx

when i boot into recovery......theres no update option. I have the reinstall packages but it just says installation aborted.
Does the update.zip need to have lowercase "u"?? i did upercase, maybe ill try lowercase
Nope.......i ran into a problem i guess. I named the file to update and i boot into recovery with rom manager but when i get to recovery, there is no updates buttom (im guessing there never was?) I click reinstall packages and it seems to start installing the update.zip but then it says "Installation aborted"
help??

Edit: removed

pewpewbangbang said:
when i boot into recovery......theres no update option. I have the reinstall packages but it just says installation aborted.
Does the update.zip need to have lowercase "u"?? i did upercase, maybe ill try lowercase
Nope.......i ran into a problem i guess. I named the file to update and i boot into recovery with rom manager but when i get to recovery, there is no updates buttom (im guessing there never was?) I click reinstall packages and it seems to start installing the update.zip but then it says "Installation aborted"
help??
Click to expand...
Click to collapse
It's not a signed .zip bro. You need to download rom manager off the market if you don't have it, then reboot recovery from it and it will put you into clockwork recovery mode and then run the update.zip from that. It also lets you run other .zips even if they aren't named update.zip.
Hope that helps ya!
Sent from my GT-I9000 using Tapatalk

anilkuj said:
thanks Andy for bring this to Jr33's notice to get this implemented for Captivate.
was wondering if there is any app which wld start this service on boot or something like Tasker if it can start a system service.
Thnx
Click to expand...
Click to collapse
I thought about that, but because it has to start your terminal program and execute the wlp2pservice (and leave it running), I'm not sure if it had a large impact on battery life.
I setup Better Terminal Emulator to have a shortcut key to type out "/system/bin/wlp2pservice" for me, so its a few taps and Its ready. The amount of tethering I do right now is not that often that this is a big deal, but would be nice..

pewpewbangbang said:
when i boot into recovery......theres no update option. I have the reinstall packages but it just says installation aborted.
Does the update.zip need to have lowercase "u"?? i did upercase, maybe ill try lowercase
Nope.......i ran into a problem i guess. I named the file to update and i boot into recovery with rom manager but when i get to recovery, there is no updates buttom (im guessing there never was?) I click reinstall packages and it seems to start installing the update.zip but then it says "Installation aborted"
help??
Click to expand...
Click to collapse
My bad, it should be "Reinstall Packages" then after selecting it, it makes you scroll down past all the No's to Yes, install package.
Make sure when you open up when you open up Rom Manager you see:
Current Recovery: ClockworkMod 2.5.0.4, if not tap Flash ClockworkMod Recovery. (maybe reinstall it just incase) Then tap reboot into recovery.

Ahhh yes got it. Thank you, I didn't flash my rom before. Got it to work now. Thanks =)

As a quick note:
Please mod alert the Original Post to get this moved back to the Captivate development forum, so more developers that know what they are doing can see this thread and hopefully chime in.
This *seems* like it would be an easy fix. wlp2pservice just needs to launch at boot.

New problem. When I try to run the command in android terminal is says
/system/bin/wlp2pservice
not found

Ok I ran into the same problem because my clockworkmod was borked, so I had to reflash Clockwormod Recovery. When you tap Flash Clockworkmod recovery, it replaces update.zip in your root of the SDCard, so when you hit reinstall/update packages, it just reinstalled clockworkmod recovery again, no harm done.
So what you need to do is redownload the mobileAP zip and replace the current update.zip with the one found in this thread.
Go back into Rom Manager and reboot into recovery (dont hit flash clockworkmod), then update/reinstall packages, it should work then.

gps conf ... HELP !!!

Hello. I am too having problems with the GPS fix. I googled, i have read fora, i wrote on fora, i have read even the facebook desire hd page where people from all over the world have the same problem with the GPS.
I have tried EVERYTHING, now the last chance is to change the region from the gps conf file....which i can remember being northamerica, while i live in europe. Maybe changing that to EUROPE will help me fix the gps problem.
To save changes to that file, i would need root access. I don't have root access. I don't need root access, i just want to change that file and see if the gps gets the fix faster than before....other than that, i have never wanted root access.
So, knowing my target....which is the most simple way to change that .conf file? I know that the visionary tool doesn't work anymore with froyo desire hd....so i can't root the phone...other methods look really complicated to me. there should be a way to edit the GPS file without doing a mess with roms and downgrades and everything...
please help !!!

You need root access to edit the file, there's no other solution that I know of. If you decide to root, use FasterFix from market to change the region.

Unable to use Visionary due to your build number is more than 1.3xxxxxxx?
You do not have any other option other than to root your device in order you to alter system files. Even if you download FasterFix in the market, you will need to have Superuser permission before the app can directly change system files for you.
If your build number is higher than 1.3xxxxxx, then you have to do a downgrade.
GPS performance has been affecting me in the past, but now i have found a solution(not sure yet, but it works for me until now). Now I got a fix within 5-15 seconds. At most is 30 seconds for the first fix.
Anyway, you should consider rooting. You can have full access throughout your device. My phone previous, battery life can last for a day, now at least two days. I am running different ROM and Kernel thats why.
Cheers dude. =)

It is a part of \etc, definately will need a root access to grant you access to the file.

ok could you link me to a really SIMPLE tutorial to do that? of course i think i'll have to do a hard reset? lose all my saved games and screen configurations.... sigh i just did a hard reset for the same reason (gps)....
and what about new rom and so on? do i have to use another rom in order to root the phone? what does that change ? any rom to recommend?

You don't need root access to modify gps.conf.
Use FasterFix.
Use it two times (open Fasterfix, select europe, apply, then do these steps once again).
Fasterfix will return an error both times, but if you open gps.conf from a file manager like ASTRO) you'll see that file had been changed.
After a while, Android reverts automatically gps.conf to notrh america ntp.
Didn't pay much attention to this, so i don't really know if Android reverts file on reboot or even without reboot.

giegi_dc said:
You don't need root access to modify gps.conf.
Use FasterFix.
Use it two times (open Fasterfix, select europe, apply, then do these steps once again).
Fasterfix will return an error both times, but if you open gps.conf from a file manager like ASTRO) you'll see that file had been changed.
After a while, Android reverts automatically gps.conf to notrh america ntp.
Didn't pay much attention to this, so i don't really know if Android reverts file on reboot or even without reboot.
Click to expand...
Click to collapse
i actually used faster fix, but as soon as i do anything, it says 'required root access' and doesn't do anything !! is that the error you're talking about ?
EDIT: i tried again...start faster fix: can't get root. change to europe = root access required. the gps.conf (i checked) is still on north-america.pool server ((

giegi_dc said:
You don't need root access to modify gps.conf.
Use FasterFix.
Use it two times (open Fasterfix, select europe, apply, then do these steps once again).
Fasterfix will return an error both times, but if you open gps.conf from a file manager like ASTRO) you'll see that file had been changed.
After a while, Android reverts automatically gps.conf to notrh america ntp.
Didn't pay much attention to this, so i don't really know if Android reverts file on reboot or even without reboot.
Click to expand...
Click to collapse
What are you talking about? You can't change system files without root and the app description clearly states that you need root access and busybox. It's not there to fool people is it?
@rogermorse
btw, are you using a case?

I AM using a case but even without case no difference, i tried many times.
i'm trying to root the phone...already on the first step i'm blocked: android developer kit doesn't find java SDK 64 bit....i googled and other people have this problem, i can't fix it, it just keeps saying that java was not found....OMG i had never thought rooting a phone would have been that difficult....i think i'll surrender and never use the gps in my life.
the installer of android SDK stops because it doesn't find java SDK. if i unzip the SDK, at the exit it says the same thing. I was able to make windows recognize the phone in debug mode as ADB interface....but then the
adb shell /data/local/tmp/psneuteradb shell
says 'not found'. anyway the java has something wrong with the android SDK that, as i said, keeps telling me that cannot find the java. i already entered the path in user variables...

rogermorse said:
I AM using a case but even without case no difference, i tried many times.
i'm trying to root the phone...already on the first step i'm blocked: android developer kit doesn't find java SDK 64 bit....i googled and other people have this problem, i can't fix it, it just keeps saying that java was not found....OMG i had never thought rooting a phone would have been that difficult....i think i'll surrender and never use the gps in my life.
the installer of android SDK stops because it doesn't find java SDK. if i unzip the SDK, at the exit it says the same thing. I was able to make windows recognize the phone in debug mode as ADB interface....but then the
adb shell /data/local/tmp/psneuteradb shell
says 'not found'. anyway the java has something wrong with the android SDK that, as i said, keeps telling me that cannot find the java. i already entered the path in user variables...
Click to expand...
Click to collapse
while downloading the SDK, Don't download the exe, go with zip...I think that's what I did when I faced the issue last time.....

[GUIDE] Enable ad-hoc tethering on your Transformer (needs root!)

Update: If you are using the official firmware 8.6.5.9 (and obviously above) or any custom ROM based on it, you don't have to do anythink described here, because ad-hoc works natively. Thankfully ASUS fixed Googles unintelligible inability to enable connection to ad-hoc networks.
This renders this thread pretty much obsolete, but I won't delete it, just in case anyone doesn't want to or cannot update his device for whatever reason
Hi!
As there are only [Q]uestion threads about ad-hoc tethering by now, I thought I'd write a little guide how to enable it on our Transformer.
edit: If you are using Prime v1.5 (and above I guess), you don't have to do this. Roach2010 already included the modified wpa_supplicant, so you can already use ad-hoc tethering.
All credits and many thanks go to szym for the edited wpa_supplicant that makes ad-hoc possible for us!
!!! Always make a nandroid backup via recovery first! You can then reflash your backup if something fails !!!
I. Via root explorer (obviously requires root access):
If you bought root explorer from the market, you should be able to easily copy and replace the file.
1.) Go to /system/bin and copy the file „wpa_supplicant“ to your sd card as a backup.
2.) Then copy the „wpa_supplicant“ from the attached zip file and paste it into /system/bin.
3.) Long press the file and set permissions to rwxr-xr-x, like this:
User: read, write, execute
Group: read, execute
Others: read, execute
4.) Reboot
Finally tried it myself and works fine
II. Alternative method via adb (requires root access):
This is a forwarded guide from the Xoom section. I tried it myself and it works like a charm. You can find it here.
All credits for the following guide go to kelvie !
1.) Your Transformer has to be rooted! (you'll find a guide how to root here)
2.) Make a backup of your system/bin/wpa_supplicant first!
3.) Unpack the attached wpa_supplicant_xoom_wifi_adhoc.zip file to your adb folder. (if you don't know how to use adb, google for one of the many guides, or look below for another option via root explorer )
4.) push the file to system/bin/wpa_supplicant:
Code:
adb remount
adb push system/bin/wpa_supplicant /system/bin/wpa_supplicant
5.) Because zipfiles don't store permission, you have to make it executable as well:
Code:
adb shell chmod 755 /system/bin/wpa_supplicant
6.) You also have to change the permissions on /data/misc/wifi/wpa_supplicant.conf for some reason:
Code:
adb shell chown system.wifi /data/misc/wifi/wpa_supplicant.conf
7.) reboot
Again, many thanks to kelvie for the guide!
III. Easiest method (requires ClockWorkMod recovery and root):
1.)Download the attached CWM_adhoc_wpa_supplicant_TF101.zip to your sd-card. Make sure to copy it to /Removable/MicroSD, because /mnt/sdcard cannot be accessed from CWM
2.) Boot into CWM recovery.
3.) Hit "install zip from sdcard" --> "choose zip from sdcard", select the zip and confirm.
4.) Reboot
Done. You should now be able to tether your ad-hoc connection
This method doesn't seem to work because I missed an option and don't know right now how to fix it. So if somebody knows how to do this via edify script, please help me out:
Code:
chown system.wifi /data/misc/wifi/wpa_supplicant.conf
Use one of the methods above in the meantime, they works flawless.
__________________________________________________
Q&A
Q: Which app should I use for tethering on my phone? Do I need root access for tethering apps?
A: If your phone doesn't support native tethering, just search the Android Market for 'Wifi tether'. There are a lot of apps for that . I tested Barnacle Wifi Tether on my Sony Ericsson Xperia X10 with 2.3.4 MIUI ROM, which worked fine, but I guess all/most tether apps should work fine now. And yes, unless you have native tethering, your phone has to be rooted.
Q: Barnacle gives me the following error on the phone: "DHCP could not bind to DHCP port, address already in use", and my TF is stuck at "obtaining IP Address from barnacle". What should I do?
A: rpavich has found a solution for that. Thanks rpavich!
rpavich said:
1. Change SSID to whatever you want
2. Change Channel to 6
3. Custom Wifi Ad-hoc to none
4. Skip wpa_supplicant checked
5. Restart your phone (just to make sure...)
Click to expand...
Click to collapse
__________________________________________________
Regards
qwer23
Edit: I wasn't sure if this belongs in General or Android Dev section, so mods feel free to move it where it fits best.
Edit2: Attached original wpa_supplicant files for 3.0 and 3.1 (don't know if there's a difference, but I doubt it) if someone wants to reset to stock.
If you find this guide helpful, consider pressing the thanks button
Click to expand...
Click to collapse

awesome. a few more working confirmation from the others and i wont have to kiss my nokia e71 goodbye

philsuf said:
awesome. a few more working confirmation from the others and i wont have to kiss my nokia e71 goodbye
Click to expand...
Click to collapse
No need to wait, you could just try it. If you back up your original wpa_supplicant first, you can always undo your changes. I also added an easier way via root explorer that should be easier.

i just tried it, it connected to barnacle wifi but i couldnt get the internet to work. ill try again tomorrow, it may be my phone.

Skeldave said:
i just tried it, it connected to barnacle wifi but i couldnt get the internet to work. ill try again tomorrow, it may be my phone.
Click to expand...
Click to collapse
Did your phone show the barnacle symbol in the notification bar and tell you that a device is connected?
Sent from my rooted X10i using awesome custom roms

I've done this last week and noticed when stopping my hotspot on the phone the connection on the transformer shows it is still connected. So you have to manual disconnect if you want to reconnect again for later use. This is on my Nokia N8 Phone using JoikuSpot.

I tried to do this via the root explorer and it said "you cannot paste here because the file system is read only"

rpavich said:
I tried to do this via the root explorer and it said "you cannot paste here because the file system is read only"
Click to expand...
Click to collapse
On the top of your system directory in root explorer is a button, that says r/w. Push it and you'll get read/write mode.
Sent from my rooted X10i using awesome custom roms

thank you VERY much....I'll let you know how my tethering goes.

qwer23 said:
Did your phone show the barnacle symbol in the notification bar and tell you that a device is connected?
Sent from my rooted X10i using awesome custom roms
Click to expand...
Click to collapse
Yes, the barnacle symbol was in the notification bar and my TF appeared on the 'client' tab, also the TF said that it was connected to barnacle wifi.
I'm going to try again now
EDIT: Worked perfectly this morning, thanks!
I did it via root explorer FYI

This seems like a rather minor change to wpa_suppliant.conf; any clue if google will fix this in honeycomb? Not sure I understand why it isn't enabled by default...

Ok...trouble getting this to work.
1.) On my Xperia X10; message in Barnacle:
"DHCP could not bind to DHCP port, address already in use"
2.) On my TF: it's stuck at "obtaining IP Address from barnacle"

Ok....found the solution (on another XDA forum section)
I did the following and connected just fine!
1. Change SSID to whatever you want
2. Change Channel to 6
3. Custom Wifi Ad-hoc to none
4. Skip wpa_supplicant checked
5. Restart your phone (just to make sure...)

rpavich said:
Ok....found the solution (on another XDA forum section)
I did the following and connected just fine!
1. Change SSID to whatever you want
2. Change Channel to 6
3. Custom Wifi Ad-hoc to none
4. Skip wpa_supplicant checked
5. Restart your phone (just to make sure...)
Click to expand...
Click to collapse
Mind if i add this to the op? There might be others with this issue.
Sent from my rooted X10i using awesome custom roms

jake21 said:
This seems like a rather minor change to wpa_suppliant.conf; any clue if google will fix this in honeycomb? Not sure I understand why it isn't enabled by default...
Click to expand...
Click to collapse
I don't have a clue either why this isn't enabled by default, but I think they'll add this in the 3.1 update. But it's just a suggestion, didn't read anything about it though.
Sent from my rooted X10i using awesome custom roms

qwer23 said:
Mind if i add this to the op? There might be others with this issue.
Sent from my rooted X10i using awesome custom roms
Click to expand...
Click to collapse
Not at all....as i said...I got that from another part of the XDA forum...

I used this method from my rooted OG Droid and the Xoom and it worked perfectly. I have to wait for my son in law to root my TF to try it out. Would I only need to root the TF for this to work?

sanfaz said:
I used this method from my rooted OG Droid and the Xoom and it worked perfectly. I have to wait for my son in law to root my TF to try it out. Would I only need to root the TF for this to work?
Click to expand...
Click to collapse
At the moment you need to root both your TF and your phone. But if you use Clockworkmod, you probably don't need a rooted TF, because I'm preparing an update.zip to flash via CWM
Your phone has definitely to be rooted, ecxept it supports wifi tethering from stock.
edit: darn, amend scripting is no longer supported in Honeycomb. Anyone knows how to change the zip for edify scripting?
edit2: ok, probably got it solved. we'll see...

Ok, I added a zip file for easy install through ClockWorkMod to the OP. It installed fine on my TF101 and tethering works, but please backup your wpa_supplicant before installing this and report any errors. I didn't work with edify scripts before
I also restructured the guide itself, from easiest to most complicate method
Cheers
qwer23

Would this mod work with an old TP2 windows mobile phone? Will the TF then be able to use it's wifi signal?
Also, if the TF is rooted, will we be able to accept the 3.1 HC update?