Database Users

Is Usb tethering still working in 2.1?

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.

Android ported device will not connect to wifi

I have a iphone 2g running a ported version of android 2.2 and I am having problems connecting to wifi (i know it is working correctly as it was working in 1.6). I ran a logcat while i was trying to connect to my wifi at home (wep secured) and proceded to post it on the support website for the iphone port but none of them apparently know what they are doing unless you talk to them in apple terms. Here is my logcat, I would appreciate some assistance in figuring out what is wrong.
http : // pastie . org / 1327486
If anyone can make sense of the logcat, i am thinking it may have something to do with "E/wpa_supplicant( 476): wpa_driver_priv_driver_cmd failed", and help me out it would be greatly appreciated.
Edit : I apparently can not post url to outside websites (kind of stupid if you ask me) but just remove the spaces in the url to the pastie site to see the logcat

Wifi (among other things) aren't working in the iphone port of android. It's still pretty early in it's development.

its working for everyone else and it worked perfect on my ipod touch

It's never worked for me on my 2g; at least not with froyo. Apparently donut on iphone did work with wifi but I never tried it.
I've seen some supposed fixes for the missing firmware/drivers but even the handfull of people that got it working said it was very unstable.

Hate i phone..... Run away..go buy a hTC
JK!

[WiFi] DHCPCD Issues and How To Avoid Them (ROM maintainers please read)

So I've been pulling out my hair due to a specific issue I was having with a work place router.
Some days I'd come in and my wireless would connect, other times the connection would fail on "Obtaining an IP Address". This never happened on stock or other people's phones, which seemed strange to me. I finally got a chance to dig into this.
According to LogCat, the dhcpcd service was ignoring messages due to an invalid server id. While technically this is the router's fault, I'm not able to replace it myself, (like I said this is a work place router). Looking at the dhcpcd included with my ROM it appears to be 4.0.15. So I went hunting down dhcpcd.
Turns out in 4.0.13 they added the stricter checks to dhcpcd:
http://freshmeat.net/projects/dhcpcd/releases
In 5.0 this setting is driven by a conf file, but not in the 4.X.
Stock is using 4.0.1. As root I replaced the /system/bin/dhcpcd (cat /sdcard/dhcpcd > /system/bin/dhcpcd) with the version attached to this post and went forward. The troublesome router connected without an issue, and life is now good. I haven't tried to reboot yet, which may replace the version of dhcpcd that I have.
If you maintain a ROM please do not include dhcpcd 4.0.13 or greater as it causes people grief. dhcpcd 5.* is fine, provided you remove the "requires dhcp_server_identifier" line from the dhcpcd.conf file.

I have this problem on Perception 10.1 (as well as had it with Axura).
Interesting issue.

w00t! This solved the wifi issues on my new kernel!!
I'll give you some hugs and kiss in IRC later Guardian_Bob

Never had this problem, but I am very thankful for guys like Bob. Just wanted to thank you for the work that you do.

rootnik said:
Never had this problem, but I am very thankful for guys like Bob. Just wanted to thank you for the work that you do.
Click to expand...
Click to collapse
The only way I can reproduce what he is talking about is if I don't broadcast the SSID, other then that I never have issues.
That is with my wrt54gl, my E3000 setup that way will connect fine (both have dd-wrt)

designgears said:
The only way I can reproduce what he is talking about is if I don't broadcast the SSID, other then that I never have issues.
That is with my wrt54gl, my E3000 setup that way will connect fine (both have dd-wrt)
Click to expand...
Click to collapse
Just happy to see that you're sticking with Samsung for your next phone. And are you planning to get the new kernel back up after the problem from the other night. I'm still using the build 11 that you posted. I have not run into problems.
Is it possible that you will ever make a uv version? The bootscreen is keeps me from using GB's as ghey as that may be. Haha!

designgears said:
w00t! This solved the wifi issues on my new kernel!!
Click to expand...
Click to collapse
This is awesome news. Thanks for being attentive DG!!! Looking forward to the next release.

designgears said:
w00t! This solved the wifi issues on my new kernel!!
I'll give you some hugs and kiss in IRC later Guardian_Bob
Click to expand...
Click to collapse
So I assume that the Firebird Kernel 2.0 will be revived in the next couple of days?

pinoymutt said:
So I assume that the Firebird Kernel 2.0 will be revived in the next couple of days?
Click to expand...
Click to collapse
That would be nice if everything is working on it....Same for any other ones from DG...
Nice find on the wi-fi issue Bob...
Mac

Haven't had a single dropped connection since dropping this in. Awesome.

whiteguypl said:
Haven't had a single dropped connection since dropping this in. Awesome.
Click to expand...
Click to collapse
Good to hear. I had to think about why this works for you as you're just changing the dhcp client. If the dhcp server has a short lease time, and is implemented badly that might explain why you were getting dropped.

Kudos to GB for finding this, and to DG for being right on-top of things, noticing, and making use of it.
Can't wait to see what you have in-store for the next Perception.

Thank you so much, I've been having intermittent Wifi issues the past few months and this finally fixed it.

phishie said:
Thank you so much, I've been having intermittent Wifi issues the past few months and this finally fixed it.
Click to expand...
Click to collapse
I fully expect this to affect a lot of people, since the router I was having trouble with is a Verizon FIOS router.

Guardian_Bob said:
I fully expect this to affect a lot of people, since the router I was having trouble with is a Verizon FIOS router.
Click to expand...
Click to collapse
hmm i havent had any problems with my FIOS router

I've tried this on Cog 3.01 and unfortunately, my issues remain. Randomly does not reconnect to wireless APs without disabling and re-enabling wireless.

Escape311 said:
I've tried this on Cog 3.01 and unfortunately, my issues remain. Randomly does not reconnect to wireless APs without disabling and re-enabling wireless.
Click to expand...
Click to collapse
Run logcat when the connection is failing to connect and see if there's any messages, it might point to a root cause.

Is this clockwork updateable???
It never wants to install, gives me some sort of error.... Sucks I want to listen to pandora at Xsport!
Sent from my GT-I9000 using XDA App

sremick said:
Kudos to GB for finding this, and to DG for being right on-top of things, noticing, and making use of it.
Click to expand...
Click to collapse
Not the only one, you know.

MikeyMike01 said:
Not the only one, you know.
Click to expand...
Click to collapse
Actually, no I was not aware. I appreciate all ROM maintainers reading and taking the time to fix this, regardless of if they give me a shout out or not.

[Q] Syndicate Rom 1.0.2 wireless tether error

So im on Syndicate rom 1.0.2 and i like it alot. its realy fast and smooth. but ever since moving from 1.0.1 the wireless tether app (3.0.9) doesnt work. When i launch the app and click to start tethering it starts initiating the process but freezes right where its trying to use the hotspot and then it makes the phone reboot. Any other verion of this app will FC. Can some one help please? i have reflashed the rom properly a few times and that didnt help. I also tried the tether fix file that k0nane had on his thread and didnt fix anything either. I tried downloading the hotspot fix from Syndicate page and those links dont work anymore. Can some one please help?
EDIT: i have it set on epic 4g in the settings.
Also does any one have a way to fix the tws bug? (i do know the airplane mode trick but was looking for a fix not a workaround)
thanks eveyone in advance....k0nane, thank you for your hard hard work bro

You mentioned 3.0.9 - I assume you mean -pre9. The version included in SRF is 3.0-pre11. You probably shouldn't have flashed that fix, either, because it was for 1.0.1 only.
I'd suggest you remove any copies of the Wireless Tether app you've installed, and reflash 1.0.2. You won't lose any data. See if it works for you then. If it doesn't, uninstall the preloaded version and try others. Wireless Tether is a finnicky beast, but that's expected - the 3.0 branch is experimental for a reason.

Thanks. I will try that and get back to you. And yes I meant the version that came with rom. I will try and get back to you.

Hey I tried everything in your instructions and still the same thing. I knw this wireless tether thing is in experimental stages but it worked fine on 1.0.1. I actually wasnt able to use the pre10 on that rom version so I had downloaded the 2.0.7 version and that worked fine. Do you think it might have to do with the hotspot app ? because i notice wireless tether freezes and phone reboots when its trying to launch hotspot. I notice from the notification when hotspot becomes activated the phone freezes and reboots..

Issue resolved
Well, thank you for your help again. After trying every thing from flashing the rom to uninstalling and reinstalling the wireless tether app I got tired and almost gave up. Then I started playing with the app settings and it turns out that choosing the LG Optimus under Device-Profile is really stable and works the best for me, so far no issues.

I was going to say i had issues which were resolved by selecting EPic 4G(my phone ) in settings. I was able to launch and see it but did not have internet access until i selected my phone as well.

bryanberlin said:
I was going to say i had issues which were resolved by selecting EPic 4G(my phone ) in settings. I was able to launch and see it but did not have internet access until i selected my phone as well.
Click to expand...
Click to collapse
I also selected Samsung epic but this did not work for me. what worked was LG Optimus! it is strange but it works ;-)

I didn't have to do anything and it worked fine for me. I set up Security on it but that's it. Especially with all the ROM flashing I wonder why your phone seems especially finicky. Good luck.

I had errors similar to this when using the app, my problem was that I had 4G turned on already when launching the app. Turning 4G off, launching the app establishing a connection and THEN turning on 4G works perfectly though.

mine would not work either I went to settings and changed my device profile to epic 4g and my set up method to softtap for samsung. that seem to do the trick.

Wifi Tether BUG - no Internet on newer kernels KG5 and higher on my Lenovo Laptop

I recently encountered a weird bug when SGSII would establish wireless "g" connection at 54mbps (instead of regular "n" at 65mbps) when doing 3G to wifi tether on my Lenovo Laptop.
My other 2 laptops work fine as expected, however after doing some troubleshooting, its concluded that the wifi router IP forms a "black hole" hope because of which the external communication to Internet dies after 4 or 5 hops (internal to the ISP). While doing a Trace route, the first hop (the IP of the phone's wireless router - 192.168.43.1) doesn't respond to the trace route ICMP requests and fails, however it does work for the next 4 hops before eventually dying after that.
This proves that wifi connectivity between the phone and laptop remains good despite it being downgraded as "g" network when my laptop is capable of "n" at upto 300mbps.
Never had this issue before KG5 or higher builds and it seems all the custom kernels and ROMs based on these newer kernels are affected.
As this issue is affecting only my Lenovo Laptop, not sure if it was ever reported.
Fortunately I am able to flash kernels based on earlier than KG5 build like Ninphetamine-2.0.x (till 2.0.5).
All Ninphetamine-2.1.x builds and kernels like "RAGEmod v1-T30" are also affected.
I am currently on "TOUCH X-treme KH3 2.0 'PERFORMANCE'" ROM and fortunately it seems to be working fine on Ninphetamine-2.0.5 as per my preliminary testing.
I have 2 more laptops which seems to be working fine otherwise on any latest kernels.
I would appreciate if someone could shed some light on the reason behind this bug as I am still investigating the cause and on a fix other than older kernel versions.
My primary usage of this phone is completely impacted by this bug and I hope Samsung would be able to resolve this bug before their next official release of 2.3.4 or higher version builds.

Hmm like the battery drain while charging bug on SGS1 I seems to be the only person shaken up by this bug which makes my SGS2 completely useless when using the latest kernels/ROMs.
My laptop has Intel WiFi Link 5100 AGN. Can someone having same/similar Wifi adapter report their experience?

Not surprised that Wifi tether is not used by most of us and hence such bugs go unnoticed and I paid a HUGE price of crashing my laptop which trying to fix the issue as I never thought it is the phone doing something weird which is preventing my laptop to get proper wifi connectivity.

Unfortunately no resolution till date. All the latest kernels and ROMs are affected. Not sure what is the issue as it defies logic why only one series of Wifi adapters are affected by this bug.

No resolution till date. All the recent kernels are still affected except the one on CM7 ROM.
Seems I need to wait for this update to become official in India before raising with Samsung here.

Ahhh.. Finally a respite after several MONTHS! The latest Siyah v2.5 kernel (http://forum.xda-developers.com/showthread.php?t=1263838) with new Wifi Driver has restored Internet access through Wireless Tether though the speed is still limited to g instead of regular n at 65mbps. But atleast I can now switch from the good old Ninphetamine-2.0.5 kernel to this latest kernel I always wanted to keep. Such a RELIEF!

No internet
Prankey said:
Ahhh.. Finally a respite after several MONTHS! The latest Siyah v2.5 kernel (http://forum.xda-developers.com/showthread.php?t=1263838) with new Wifi Driver has restored Internet access through Wireless Tether though the speed is still limited to g instead of regular n at 65mbps. But atleast I can now switch from the good old Ninphetamine-2.0.5 kernel to this latest kernel I always wanted to keep. Such a RELIEF!
Click to expand...
Click to collapse
I still get a no internet access notice on my laptop... Any tips?

Fix
leondb said:
I still get a no internet access notice on my laptop... Any tips?
Click to expand...
Click to collapse
Downloaded the newest beta from their website and installed. Then chose my device, and I am happy to report it is now working

leondb said:
Downloaded the newest beta from their website and installed. Then chose my device, and I am happy to report it is now working
Click to expand...
Click to collapse
I have faced the similar problem. But how my problem was solved is give below:
Update you windows OS using windows update
Then manually switch off the radios and switch on
That's all and now I can use wifi tethering as normal. First check with second option, if doesn't work, then try updating the PC OS too.

grgsiocl said:
I have faced the similar problem. But how my problem was solved is give below:
Update you windows OS using windows update
Then manually switch off the radios and switch on
That's all and now I can use wifi tethering as normal. First check with second option, if doesn't work, then try updating the PC OS too.
Click to expand...
Click to collapse
Latest Siyah 2.6.x kernels have AGAIN brought back the bug on my face!
None of the other options you suggested worked. I have spent hours trying to figure it out and this is what I get when I am affected:
Tracing route to 8.8.8.8 over a maximum of 30 hops
1 * * * Request timed out.
2 164 ms 123 ms 127 ms 218.248.84.5
3 228 ms 68 ms 81 ms 10.42.43.101
4 79 ms 79 ms 80 ms 10.42.43.28
5 * * * Request timed out.
Doesn't make ANY sense on how the first hop is getting blackholed when it otherwise respond to ping requests. I am able to reach till the last hop of ISP before dropping off.
Can any network gurus out here explain this phenomenon? I am unable to locate any logic behind it.
Hope Siyah team fixes it soon for me to enjoy a glimpse of Voodoo Sound on my SGS2.

I have a Lenovo T520 and am using the KK2 stock firmware/rom with no problem whatsoever in tethering...using it at this very moment

It actually seems to be affecting only Intel 5100 adapters like on my R400. I have 3 other laptops and a mobile phone which are working fine otherwise
As I said, it defies logic why only this adapter has compatibility issue when even older Intel 39xx based adapters work perfectly fine otherwise.

Fixed in Siyah 2.6.2 kernel again
Finally got it fixed on Siyah 2.6.2 kernel (to be released shortly) while working directly with the dev "gokhanmoral" in the past few days. All seems to be working now like it was in 2.5.x builds for me.
I sincerely thank gokhanmoral for taking the pain of looking at this isolated bug by Samsung which has fortunately been resolved on the latest drivers (to an extend, still no n mode access).