Related
I just successfully rooted my (non-Fender) MyTouch using the howto at the unlockr website. The whole point of it was so I could use a tethering app like Barnacle, but I am finding that my laptop cannot seem to use the connection it provides, even though it sees it and appears to connect.
Further, my phone is now extremely flaky and is unable to fully sync my Google account (contacts are blank and won't sync at all). It often reboots itself for no apparent reason. I am regretting screwing around with it at this point.
Can anyone recommend a ROM to install that is stable and will give me all the functionality I had before I rooted, plus will work well for Barnacle or another good wifi tethering app? And I still don't see exactly where on this site I go to actually download ROMs.
Thanks in advance for any assistance.
Do you have a 32a or 32b board? do you have your sd card with 3 partitions Fat/ext2-3-4/swap?
What recovery did you flash? newest Amen ra 1.70?
What radio and SPL do you have.
We have to know these in order to choose a rom. But there are many good ones, just sounds liek you found a crappy one or one not made for your phone
Improved things with latest cyanogen ROM
Ok, so after my first post I managed to flash my phone with the latest cyanogen ROM. Now the flakiness has gone away and I have back all the stability of my former phone, plus actually a couple things I like better than before.
Alas, Barnacle still does not work properly. It starts and runs fine right up until my laptop or iPad actually tries to connect with it, then I get the message that "process stopped unexpectedly".
Thanks for your response. I will try to find the right place to post my tethering problem to see if someone can help me with it.
Mod. edit: not dev related, moved to general
Ok.. EVO 4g. New phone bought today. Managed to get it rooted and a custom rom installed(Damage control 3.2.3, updated via DCUpdater) on it that works splendidly other than for some reason I cant seem to activate the SD card anylonger. This could be a serious issue I guess.. haah!
But the main thing i was wanting out of this device tonight was wifi tethering. I have the app. it loads fine, I can adjust all setting (SSID/Passphrase etc) i even went as far as downgrading to the 2.0.2 version to see if that helped via the google.code page. But it still just gives me the stupid error that it is "Unable to start tethering"
I really don't know a way to start trouble shooting this as I am VERY new to android, and if someone can offer a bit of help I would be much appreciative.
I am more than willing to post any info you might need as far as the setup on the phone goes. Just let me know what that info is you would be looking for and I will get it.
And if anyone can shed a bit of light on why I cannot see the SD card anymore that would be delightful as well.
Thanks a bunch.
..........
For the wifi tethering: if the custom rom has it, you may have to remove it completely and download wifi tether from the market, that should fix it.
Hi
Just tried to use usb tethering for the 1st time since 2.1 update.
All still looks like its working but no internet access. Tried under Linux on the same pc that always worked under 1.5
Also tried it on xp although I have never used it on there before I got the same kind of symptoms. Itooks like its all working but no internet, no pings, no nslookup.
So..... can someone try it and let me know if its working for you.
I am on T-Mobile UK. Ota 2.1 update, non rooted, stock Rom.
Thanks
I have exactly the same problem. I have spoken to TMob UK support who have not yet managed to solve it.
I'm wondering if they've not set up the phone right in the 2.1 update.
Glad its not just me. I will report it tomorrow as well.
I have a mate with a desire on tmob - will do a side by side with him tomorrow (and confirm his is working) and see if it is just settings - although it feels like a deeper problem to me.
I'll post findings.
Same here - tethering works fine on my Desire, but the missus Hero doesn't work - hoping for some resolution soon
Just moved house so am without internet for the next week, so tethering is bloody useful right about now!
Have put a 2.2 rom onto my Desire and am using WiFi tethering for now, but doesn't help when I'm not in...
If you are rooted, there is an app that works fine.
But custom roms don't have this issue afaik. VillainROM 12 works fine with tether, as I had to use it at work to test external connectivity to a system.
It's an option and one I will look into.
It worked fine under 1.5 and so far its the only thing that us causing me an issue.
T mobile tech support were able to reproduce, and in their testing they found a factory reset fixed the problem - I have confirmed (as has another user over on the tmobile forums).
Gave me an excuse to clear up the rubbish that had accumulated on phone.
All working now.
its working fine for me :/
nellisere said:
its working fine for me :/
Click to expand...
Click to collapse
and me, just done the Orange OTA 2.1 update and tethering works fine on the phone right after the update... if you need to factory reset to get it working it must be something you have installed on the phone.
Or maybe tmobile did something different to orange. Or maybe the radio roms are different.
Was quite a few tmob users and tmob support so if it was a rogue app then it was a fairly common one
Either way. It's working now.
Wish all problems were resolved as.simply.
Sent from my HTC Hero using XDA App
I certainly think it has something to do with the installed apps on the phone after the update else why would a factory reset solve it, its not the Rom that is the problem... I take it you had heavily customized your phone.
Sent from my HTC Hero using XDA App
Actually no- 5 apps, lastfm, xda, facebook, ambling audio book reader and handcent sms - restore took less than 5 minutes after factory reset, all contacts and calendar info on google.
Given that the functions like handing out dhcp address worked, it was fundamentally was "all there" I can easily imagine a startup routine that says something like
if file exists "some config file" then leave it alone
else make a new one
When you reboot, config file exists so leave it alone in, when factory reset - file doesn't exist, make a new one.
Perhaps the key thing is I was a heavy user of tethering before the update, perhaps when I did the upgrade I forgot to "stop" tethering and just pulled the cable - can't remember, so maybe I had a config file/param that the newer kernel, ip stack etc. didn't expect to see and didn't handle well.
The key thing about factory reset isn't the rom I agree, the code is the code - but it's the wiping of the configuration and volatile data - something got broken for me, and the guys at tmobile, and about 5 other users who reported the same problem - so whilst it obviously works for some without a reset, equally it didn't for others - for at least 3 of us (2 end users and 1 at tmobile) a reset was needed.
If it was a one off, absolutely agree, it must have just been me/my setup - but it wasn't an isolated case.
Personally, I was surprised when the 2.1 update didn't wipe the phone, I was expecting it - so in my case no real problem once suggested to me - others might have more dependency on the installed apps and config but for me this was an easy fix.
Either way, it's back working now - so if it works without a reset - great, and if it doesn't work, a reset looks to fix it - so great as well.
I just got a Samsung Vibrant yesterday from a 3rd party, and I'm very excited. I know I need to read a lot on this site, but since this is my 1st smartphone, please forgive my basic/naive questions, be gentle on me, and give me some directions so that I won't have to walk in the darkness.
1) I haven't done anything essential to the phone yet, and I'm considering to root, unlock and the phone, and upgrade from 2.1-update1 to 2.2. Which one should I start first, root, unlock, or upgrade? Even though I haven't done much on the phone, do I still need to go through the backup before rooting?
2) Between the IMEI and S/N barcodes, there is '10.10' on the phone which I assume is the manufacture time of Oct. 2010. Would the GPS 'fix' be done with my phone (Build Number: Eclair.UVJI6)? Considering the amount of complaints about the GPS on Samsung Vibrant, how does the GPS work with offline applications like CoPilot? Where should I put the CoPilot Map, in internal or external SD?
3) If I want to make phone calls through WIFI connections without eating up my minutes, what kind of VOIP combination should I consider? Google Voice?
4) What web browser do you recommend? Other nice applications should I put in?
5) When I select Avatar, it says "File not found". Is it supposed to be in the external SD (which seems empty)? Where can I get the file?
Thanks a lot for your help!
I would suggest reading the bible in the Development section. or this
get the proper drivers here.
root with Superoneclick found here. There is another version floating around that works better that is called SuperOneClick for Froyo.
fix 3e recovery (if running stock froyo) software found here runs from your computer with your phone connected and usb debugging turned on.
download the Clockwork Recovery Unlock.zip from either Rom Manager or here (put it in your phones internal SD root)
I HIGHLY RECOMMEND TeamWhiskey's Rom Bionix-V 1.2.1 found here
But I would suggest getting to know your Vibrant/android phone if you have never owned one first.
Edit: Calling over wifi uses your plan's minutes. Its meant for poor reception areas where you might have wifi with broadband internet.
Edit2: Most people get rid of the "Avatar" its just the movie and takes up space. I believe it should be on the SD card that came with the phone.
Congrats on the phone
1st is to root it you can use the super-one-click, like the previous post said. There are other rooting but this one is very easy
After that, Read up on the roms the Axura, Trigger, Einherjar, and Bionix are all fine and depending on your need you have really great choices, the Axura has remarkable battery life, for example. So do the reading on which you would like. Once you pick one flash it. Then get Rom manager and Titanium back up. Free from the app store. Then you can start playing. Should you decide that you do not like or just want to try another rom, you can flash over the last most times with out problems. One thing (read the bible) if you do flash over one of the custom roms you will need to disable the voodoo lagfix. This is actually a file conversion. So Read up on that as well. Hope that helps you.
[Q] Newbie Questions
I too got a vibrant yesterday and then upgraded to 2.2 of skies mini. The problem is now I have not found a way to get it rooted with 2.2. Any ideas?
coldasice304 said:
I too got a vibrant yesterday and then upgraded to 2.2 of skies mini. The problem is now I have not found a way to get it rooted with 2.2. Any ideas?
Click to expand...
Click to collapse
There is the super one click or you can get a copy of the update folder that roots the phone.... place it on the internal sd card go to recovery and install update...... that also will do it. LOOK IN THE STICKY/BIBLE
Thanks a lot for the great help, FlyingPoo and oka1! I really appreciate it.
A couple of more newbie questions:
1) When making phone calls, sometimes I need to key in some options after the phone is connected (for example, when you call a customer service 800 number). How can I bring up a on-screen keyboard when the phone is already connected?
2) It seems my Samsung Vibrant has much weaker WIFI reception than my Mac laptop, and I have to bring the phone closer to the router to get detectable WIFI signal. Is there anyway I can boost the phone's reception capability?
Thanks a lot!
This thread is about the 3 types of known wifi-roaming bugs, how to differentiate these and fix at least one of them with a little hack.
Documentation of the bug avioded by this workaround on Google: Click Here
BIG NEWS!! As mentioned by a spanish user above there are newer firmwares, that are correcting the wifi-roaming bug, that was fixed by this fix.
Confirmed by an german OTA-Update. So try upgrading your firmware to fix the bug.
But : Keep in mind that an OTA-Update, official from Samsung wont install on a modified system. This includes also our modified wpa-supplicant. So if you want to use a newer firmware you have to restore the old wpa-supplicant: View attachment wpa_supplicant.zip(From The newest Firmware in Germany[OTA-Eplus, JZO54K.I9300XXELL4)
General facts to know about buggy Wifi-Roaming on Android Devices:
Bugs types that are existing
1.The phone never tries to roam by, unless it completely loses signal. Then it connects to the strongest AP. This is the typical Galaxy S2 bug.
2.The phone never tries to roam, and on top of that tries to reconnect to the specific AP that it knows, even if it is right next to a better one while connecting. This has been observed on some Nexus devices, but is apparently fixed on the Galaxy Nexus running CM10.
3.The phone tries to roam as it can see a better AP, but drops the connection and reconnects to the stronger AP shortly after. That's the typical Galaxy S3 and Galaxy Nexus bug, which is fixed by the hack described in this thread.
Only Bug 3 in this list is fixed by this hack. It will not help for the other two bugs!
To determine which bug you are observing, try this:
- Pick two access points that are within range of each other, we will call them AP1 and AP2.
- Locate the phone close to AP1, turn on wifi, and connect to the network. You should get full signal strength.
- Start listening to a web radio stream using e.g. TuneIn Radio (available on Play Store), configure the buffer size to the minimum possible.
- Slowly walk towards AP2, watching the signal strength indicator.
- If you reach AP2 and the phone still shows a low signal strength (at most one bar) after 10-20 seconds:
You are observing a different bug which is not avoided by this workaround.
- Turn off wifi and turn it back on again.
- If the phone now connects to AP2 and shows a high signal strength, you are observing the Galaxy S2 bug --> Bug 1 in the list
- If the phone still connects to AP1 and shows a low signal strength, you are observing the Nexus bug --> Bug 2 in the list
- If the connection drops before getting close enough to AP2, the access points are too far away from each other. -->Retry with a different set of access points.
- If the signal strength seems to increase while getting closer to AP2, but then the wifi icon disappears briefly and comes back after a few seconds, and the web radio stream drops, you are observing the Galaxy S3 bug, and this workaround will help you. --> Bug 3 in the list
- If the signal strength increases while getting closer to AP2, the wifi icon doesn't disappear, and the web radio stream doesn't drop, everything is working normally --> no bug:
-You might have a device that just doesn't have a wifi bug. Apparently such devices indeed exist.
-You might have a Galaxy S3 or Galaxy Nexus, but you were lucky. Try walking back to AP1 and check if it drops the connection this time.
-You might have already applied the workaround above, or a different fix for the same bug. (However there doesn't seem to be one yet.)
______________________________________________________________________________________________________________________
Now as you know which bug your device has you maybe have noticed that your device has bug type 3, here is the hack to fix it:
IMPORTANT: IM NOT RESPONSIBLE FOR NOT WORKING DEVICES AFTER THIS PROCEDURE. INSTALL AT YOUR OWN RISK!! THIS MOD IS EXPERIMENTAL!!
THIS MOD ONLY IS CONFIRMED WORKING FOR THE SAMSUNG GALAXY i9300 AND THE SAMSUNG GALAXY NEXUS i9250
For the installation procedure i give here root rights are needed. It also is recommended to make a CWM-Backup before. If you are unsure about root rights or dont know how to use a Custom Recovery feel free to ask before you do anything.
Installation Instructions for the Standalone-file(no Custom-Recovery needed):
1. Download View attachment Standalone-file.zip and unzip
2. Search for your original "wpa_supplicant"-file in \system\bin.
You can use any Explorer that offers root-acess but be sure you set the permissions to rwx r-x r-x if you use another file explorer as i mentioned. It is needed for the file to have the permission to be executed
(f.e. Root Browser Lite)
3. Copy your original "wpa_supplicant"-file to any location you will remember in case anything goes wrong.
4. Delete the original "wpa_supplicant"-file from the folder
5. Paste the modified "wpa_supplicant"-file downloaded from here in \system\bin. Make sure the file still is named "wpa_supplicant"
6. Reboot your device
Installation Instructions for CWM Flashable-file(CWM-Recovery needed):
1. Download View attachment 1549825
2. Copy the downloaded file to your sdcard.
3. Search for your original "wpa_supplicant"-file in \system\bin.
You can use any Explorer that offers root-acess but be sure you set the permissions to rwx r-x r-x if you use another file explorer as i mentioned. It is needed for the file to have the permission to be executed
(f.e. Root Browser Lite)
4. Copy your original "wpa_supplicant"-file to any location you will remember in case anything goes wrong.
5. Reboot to recovery and flash the downloaded file.
6. Reboot your device.
Your device should now roam correctly from one AP to another.
Please leave your feedback here in the thread and hit the thanks-button if it fixed your problem. ENJOY
FOR ADDITIONAL INFO: Click Here
______________________________________________________________________________________________________________________
Special Thanks to:
- TheSeven, who created this hack
- querty12, who created the flashable CWM-file
- Gabeloooooo, who was the first to give me feedback about this
I hope this leads to a fix. GS3 is garbage when there is more than 1 AP, makes VOIP useless.
Yeah thats the Main Problem with this.
Also Streaming apps, spotify and so on suffer from this issue
I will add the modified wpa_supplicant to replace with the old on soon
felixchris said:
Yeah thats the Main Problem with this.
Also Streaming apps, spotify and so on suffer from this issue
I will add the modified wpa_supplicant to replace with the old on soon
Click to expand...
Click to collapse
Technically speaking, will someone be able to make this fix available for stock sammy roms as well?
Gabeloooooo said:
Technically speaking, will someone be able to make this fix available for stock sammy roms as well?
Click to expand...
Click to collapse
Actually this fix was tested on Stock Rom and Cyanogenmod It works on official Stock Roms as well Just have to be rooted
Tried it, breaks wifi. Can't enable wifi anymore. (i9300 stock 4.1.1)
And oddly enough, restoring the old file back to system\bin doesnt fix it. Will do a couple of tests than will restore from nandroid.
Ok, the reason it didn't work is permissions. Copying using ES explorer did not give the execute permission. Now both files allow me to enable wifi. Will report back on AP roaming after using for a while.
Thanks for your feedback Gabeloooooo
Can you please, after finishing your tests, tell me which permissions you did to set ? as i can mentione it in the instructions
i only tested with root browser...
Used this: rwx r-x r-x
thx will add it to the instructions
Things seem MUCH better with this fix. It is no longer constantly disconnecting. MAJOR IMPROVEMENT!!
I haven't tested groove ip yet, too many bad experiences in the past, but will try it this week to see how it fares.
So maybe if you like the world you could drag it out to the SGS3 - World as i am normally focused on the SGSL- Forums But thanks gor the feedback
Sent from my GT-I9003 using xda app-developers app
Will this work on the LG Nexus 4?
It has a Murata SS2908001 802.11 a/b/g/n Wi‐Fi and Bluetooth module according to ifixit.
Will this work on the LG Nexus 4?
It has a Murata SS2908001 802.11 a/b/g/n Wi‐Fi and Bluetooth module according to ifixit.
Click to expand...
Click to collapse
First of all: Has the Nexus 4 really this bug?
if yes, there is a chance that it will work as the problem comes from google code itself, so basically every device can have that problem if they dont do anything against.
But this fix isnt a real fix, it an provisoric hack, that solves the problem
So for now its only confirmed working on Samsung SGS 3 and Samsung GN. I recommend just install it according to the instructions and you see if it changes anything. If not revert back
Is it safe to apply to latest 4.1.2 sammy rom, or do they never change the wpa applicant file?
Is it safe to apply to latest 4.1.2 sammy rom, or do they never change the wpa applicant file?
Click to expand...
Click to collapse
It was tested on this Version and till now they never changed it
I was pointed to this thread from SGS2 forum... http://forum.xda-developers.com/showpost.php?p=35143039&postcount=41
Now I read, that this is only for SGS3...
Is there any possibility that this will work on SGS2? :fingers-crossed:
felixchris said:
First of all: Has the Nexus 4 really this bug?
if yes, there is a chance that it will work as the problem comes from google code itself, so basically every device can have that problem if they dont do anything against.
But this fix isnt a real fix, it an provisoric hack, that solves the problem
So for now its only confirmed working on Samsung SGS 3 and Samsung GN. I recommend just install it according to the instructions and you see if it changes anything. If not revert back
Click to expand...
Click to collapse
Hello, brand new to Android and the forum and I was referred here by a thread on code.google.com. The id=22575 (I can't post a direct link).
I can confirm I have the bug on a Nexus 4 with Android 4.2.1.
My home network has 2 different APs with the same SSID and same security. There is a "primary" AP and a wireless repeater, both running DD-WRT. My Nexus 4 will only connect to the primary AP. Even if I forget the network and attempt to connect to the repeater standing inches away from it, the Nexus 4 still associates with the primary AP.
Thank you!
Jard16 said:
Hello, brand new to Android and the forum and I was referred here by a thread on code.google.com. The id=22575 (I can't post a direct link).
I can confirm I have the bug on a Nexus 4 with Android 4.2.1.
My home network has 2 different APs with the same SSID and same security. There is a "primary" AP and a wireless repeater, both running DD-WRT. My Nexus 4 will only connect to the primary AP. Even if I forget the network and attempt to connect to the repeater standing inches away from it, the Nexus 4 still associates with the primary AP.
Thank you!
Click to expand...
Click to collapse
did this fix work on your Nexus 4?
drewski_1 said:
did this fix work on your Nexus 4?
Click to expand...
Click to collapse
I will have to try it some time next week when I learn enough to actually apply it. Again, this is my first Android phone so this is all very new to me.
My workaround was to install another AP using a different SSID and use the app 'Best WiFi' to force switch when the signal drops too low. I just got the phone yesterday.
SGS2 and Nexus4
I was pointed to this thread from SGS2 forum... http://forum.xda-developers.com/show...9&postcount=41
Now I read, that this is only for SGS3...
Is there any possibility that this will work on SGS2?
Click to expand...
Click to collapse
The SGS2 also had problems with WifiRoaming, but they were different as far as i know. This fix shouldnt work for the Galaxy S2.
Quote:
Originally Posted by drewski_1 View Post
did this fix work on your Nexus 4?
I will have to try it some time next week when I learn enough to actually apply it. Again, this is my first Android phone so this is all very new to me.
My workaround was to install another AP using a different SSID and use the app 'Best WiFi' to force switch when the signal drops too low. I just got the phone yesterday.
Click to expand...
Click to collapse
I dont know of what kind the bug of the Nexus 4 is. So i dont know if it will fix anything. As posted above you can just install it and see if it changes anything Be sure to follow the instructions and BACKUP!!