Database Users

PPP does not work...

I've tried a lot of kernel version (n1 and now latest evo and also darkstone hd2, and others mod versions) and builds (Mattc, Darkstone HD2, etc...) but ppp never worked for me.
I write from Italy (I use Wind telecom carrier) and always my phone gets the data connection but after some hours (or minutes) it stop downloading and uploading data but it says that the connection is alive.
Sometimes I solve restarting the data connection but sometimes this trick doesn't work: if I stop data and restart it after more then 10 minutes it works. Often I need to reboot the phone to restore the connection...
After a lor of google search I found that it could be a DNS problem in DHCP ppp implementation: in fact I saw that with the old n1 kernels I could ping google IPs but ping failed to www.google.it (I made these try from Android Terminal).
So I searched for a solution. At first I placed my DNS server in build.prop but it didn't work. Then I found that I can edit the ip-up script (placed into /system/ppp): it is a script that could be executed when ppp starts. The problem is that this script is never executed on my phone (I searched in the log using ppp key with grep...).
The second try I made was using ifconfig from Terminal to restart the ppp0 interface. Sometimes, when ppp stop working I can't get ppp0 device info (using ifconfig ppp0) but the interface is still active... why?
I think that when the mobile operator renew the DHCP release, the Android PPP protocol did not renew DNS server or something similar.
It is a huge problem because without data connection we loose most of Android features...
How can we do?
Thank you!

i have the same problem as you describe. never have a stable data connection with ppp bulit.

I've had almost identical issues with only differences is that didn't work from the start, not after 1-2 hour of work.
At start I've had my Data "said to be connected" but it wasn't actually.
No ping to any site was possible.
I've solved this by a simple action, switched off all wireless interfaces in WinMo, restarted and booted in Android.
I can't say that data is as stable as it was with RMNET, but it works.

same problem here but I can tell it only started with the EVO based builds. I googled around and it's seems a lot of Sprint Evo users have this problem.

Yepp,here to....ppp sucks donkeyballs at the moment with all new builds.....i go back to a old ppp build,or rmnet for a while.
Sent from my Nexus One using XDA App

Wifi problems on G1 - network error after a few minutes

Hi,
Sorry if this has been covered elsewhere but having searched I can't find anything that helps.
I have upgraded my G1 to run on Android 2.2 via all the links and information on here, but seem to be haing some trouble with Wifi.
The G1 finds and connects to my wireless access point no problem, I can then browse the Android Market on the phone but after about 1-2 minutes I get a message saying "A network error has occurred", I click retry repeatedly and sometimes after a few attempts I get it to load the page I want. I also experience the same when browsing the web on the G1.
I have tried manually creating the wifi connection but still no improvement. I have changed the channel of my access point but again still no improvement.
I have tried disabling Wifi on the G1 and using my mobile internet connection from my 3G network and this works fine.
Here are some details from my G1
Android version 2.2.1
Baseband version 62.50S.20.17U_2.22.19.26I
Kernel version 2.6.35.99-cyanogenmod shade(atsign) toxygene #2
Mod version CyanogenMod-6.1.0-DS
Build number FRG83
Any helpwill be greatly appreciated.
Regards
Gavin

Still no joy!!
Still hoping for some help, in the meantime I have updated the radio to 2.22.23.02 but still I am experiencing the same problem.
Help!

I have the exact same problem on my HD2. 3G and internet pass-through work fine, but when I'm on WiFi I get the network error messages. I have tried different WiFi networks, several Rom, radio, Kernel combinations and I still get the same errors. I even tried reverting back to the original T-Mobile Windows Rom. While I can't get the same errors, many web pages didn't load while browsing. In general I got the feeling that the rate of non-loading pages was similar to that of the network error pop-ups that I experienced while using Android. At this point I'm suspecting that I have a hardware problem. I tried opening up the phone and messing with the WiFi antenna connections, but nothing I did made any difference. I'm still looking for a solution, but no one has really addressed this exact problem.
While this may not be helpful to your specific problem I hope it makes you feel better that you are not alone.

What wifi do you run on? b/g/n ? That may also affect your connectivity.

It sounds more like a modem/access point problem to me...not phone.
Could be wifi interference from a cordless phone etc. Also, check you are using 20mhz bandwidth on your wifi access point. Some access points allow setting it to 40mhz which can really cause problems.
Can you try wifi access from a friends house that is known reliable and see if there is any improvement?

I too have this issue
I have jumped through all the hoops to get my T-mobile G1 rooted, updated
(2.6.35.10-TheOfficial-pershoot-DreamSapphire-2708)
and it works great with my voice only sim from AT&T...except that the wifi just doesn't work right. It connected for about 20 minutes, and since then everything I try to do fails after a loooooooong pause "Network Error"
Is there anyone who has any idea what this can be?

[Q] How to allow incoming TCP connections (WebDroid, SSHDroid, etc.)?

Hi all,
Wondering if anyone knows how to make Android open the ports necessary for incoming connections for server apps to work without having to ping the client first under su?
Or failing that, is there a way to run a script that will ping the client IP instead of having to run the command by hand in terminal?
Thanks!

New, clearer, catchier title

This is the dev section not Q&A.

TheATHEiST said:
This is the dev section not Q&A.
Click to expand...
Click to collapse
Sorry, my bad. Mods, could someone please move my question to the appropriate venue?
LOVE your nick and avatar, dude!
Greetings from a fellow damned heathen!

i would really love to see a solution there too!
RemoteSMS over wlan would be awesome

Yom said:
Sorry, my bad. Mods, could someone please move my question to the appropriate venue?
LOVE your nick and avatar, dude!
Greetings from a fellow damned heathen!
Click to expand...
Click to collapse
.............

Any takers?
Posted from My Hacked HD2

Second that! Something's off in 99/100 ROMS, TCP doesn't seem to do anything. Only one Sense ROM by cotulla seems to work.
I disabled the adblocking hosts file to test if it had anything to do with it (e.g. SSHDroid doesn't work with it) but that didn't help anything either

Agreed, does not seem to work on any rom I've tried, only Cotulla's 'Stock Desire' Sense build seems to work (this one: http://forum.xda-developers.com/showthread.php?t=893620).
Too bad Sense's so completely dire, otherwise I'd use that. I want CyanogenMOD.

Having the same question. I am sure here must be someone who knows how to enable inbound connections....

Little update:
I noticed it is possible for me to ping and use all services when using the gateway to access everything, in my case the access point/wifi router.
So it looks like this is some kind of routing/firewall issue but I can't find anything about default blocking or firewalling on android...

Good news. I found out what is causing this on almost every build.
It has something to do with the stock wifi tethering. If you try and enable it in almost every rom it will fail, but now turn on your wifi again and everything works as it would normally do!
The build it does work on also has working stock wifi tethering, so that explains that...
For now it's good to have this workaround and I hop to have a proper fix in the future

im using RAFDROID 3.0 and i dont think i have this problem at all. I tried SwiFTP and it connected without any issues.
Try to update the busybox version mine is 1.15.2

SantanaNL said:
Good news. I found out what is causing this on almost every build.
It has something to do with the stock wifi tethering. If you try and enable it in almost every rom it will fail, but now turn on your wifi again and everything works as it would normally do!
The build it does work on also has working stock wifi tethering, so that explains that...
For now it's good to have this workaround and I hop to have a proper fix in the future
Click to expand...
Click to collapse
I tried this on Frankinstine's awesome ROM, but no cigar. There has to be a firewall rule or setting we can tweak to allow this kind of traffic...

Yom said:
I tried this on Frankinstine's awesome ROM, but no cigar. There has to be a firewall rule or setting we can tweak to allow this kind of traffic...
Click to expand...
Click to collapse
It works for me, but it's not 100% foolproof. It seems to work for a while, but not permanently. However, it's still better than the ping method. The ping method would never work for me, since I use Wifi at least 4 different places a week. Even when done automatically, how would I know what to ping on what Wifi network?! Random DHCP on workstations notwithstanding...
This does it for me:
turn on normal Wifi
wait around 10 seconds (for Wifi to 'start')
turn on Wifi hotspot (normal wifi should turn it self off automatically)
wait around 20 seconds (the hotspot takes a while to 'start', it actually fails (error) for me, but still does the trick)
turn normal Wifi on again
At that point it "works" for me, at least for a while.
At the very least this seems to indicate that the broken Wifi hotspot and this problem are related -- on Cotulla's build (where stock Wifi hotspot WORKS), this problem is non-existent.

Unfortunatly your steps do not work for me :-(
strikernl said:
It works for me, but it's not 100% foolproof. It seems to work for a while, but not permanently. However, it's still better than the ping method. The ping method would never work for me, since I use Wifi at least 4 different places a week. Even when done automatically, how would I know what to ping on what Wifi network?! Random DHCP on workstations notwithstanding...
This does it for me:
turn on normal Wifi
wait around 10 seconds (for Wifi to 'start')
turn on Wifi hotspot (normal wifi should turn it self off automatically)
wait around 20 seconds (the hotspot takes a while to 'start', it actually fails (error) for me, but still does the trick)
turn normal Wifi on again
At that point it "works" for me, at least for a while.
At the very least this seems to indicate that the broken Wifi hotspot and this problem are related -- on Cotulla's build (where stock Wifi hotspot WORKS), this problem is non-existent.
Click to expand...
Click to collapse

engst03 said:
Unfortunatly your steps do not work for me :-(
Click to expand...
Click to collapse
That's unlucky. Those steps seem to "work" for me on CleanDroid 1.30. Maybe we can just hope it works again when the stock wifi hotspot is fixed.
Alternate "solution":
Get Cotulla's "Stock Desire" ROM: http://forum.xda-developers.com/showthread.php?t=893620
It definitely works on that. Too bad sense is dog****, and your battery will last for a day max.

strikernl said:
This does it for me:
turn on normal Wifi
wait around 10 seconds (for Wifi to 'start')
turn on Wifi hotspot (normal wifi should turn it self off automatically)
wait around 20 seconds (the hotspot takes a while to 'start', it actually fails (error) for me, but still does the trick)
turn normal Wifi on again
Click to expand...
Click to collapse
Just tried this and it worked. As soon as I started the wifi the second time my computer started pinging HD2.
My usual procedure for fixing this was to start wifi, see assigned IP address and then ping my computer from 'Net Ping' app. This can be faster sometimes.
Is there a way to port hotspot from Cotulla's build to a nonSense build? No way for me to come back to sense again

clyder said:
Just tried this and it worked. As soon as I started the wifi the second time my computer started pinging HD2.
My usual procedure for fixing this was to start wifi, see assigned IP address and then ping my computer from 'Net Ping' app. This can be faster sometimes.
Is there a way to port hotspot from Cotulla's build to a nonSense build? No way for me to come back to sense again
Click to expand...
Click to collapse
Don't know, it's probably in the kernel, so shouldn't be too difficult, but then again, I haven't really got a clue about building ROMs.

agarp said:
im using RAFDROID 3.0 and i dont think i have this problem at all. I tried SwiFTP and it connected without any issues.
Try to update the busybox version mine is 1.15.2
Click to expand...
Click to collapse
RAFDROID is also a sense build, we want it to work on all builds, stock and CM

[Q] Wifi WPA disconnections

Hello, I have an EU HD2 running Hyperdoid 2.1.0, but I've had this problem no matter which rom I tried and I'm at my wits' end trying to solve it.
When I connect to WPA wifi routers, the connection starts out fine, but after a short while my connection to the router seems to get cut off. The delay before this happens could be seconds or it could be 1 or two minutes and seems to depend on the amount of data passing over the interface - when I view a streaming video for example, I get disconnected almost immediately, when I browse pages with few graphics it lasts a bit more. I tried this with 3 or 4 different routers with identical results.
Notwithstanding that no data is getting through, the phone still indicates that I am connected to the wifi router and when I ping the router it gives me a "no route to host". WEP and open networks work fine, so I had to change my home network to WEP, but I'm not conforable with it due to security concerns. I also have problems connecting to public wifi ap's because they are usually secured by WPA.
I suspect that this is related to the wpa_supplicant supplied with tytung's kernel, but I really have no way of knowing what's going on and I haven't been able to find anything in the logs.
Can anybody give me a hand with this? Solving this problem would make the hd2 the perfect phone for me.

please post this in the Q&A section NOT the dev section
i do not suffer from these issues and my router is wpa2 secured

white-energy said:
The problem in this world is... FLAMING coming from people that are kinda stupid to help.. no offense as i haven't mentioned any of you.. I just can't understand, none of those flamers are mods/devs.. maybe i can say trolls since its a hobby..
Well i might help, i remember such a question before and i think i know the solution of WIFI connection disappearance.. there's an application (which you can find it in market) that survive's or something your WiFi connection.. i'll try searching it and if i find it.. i'll post the link..
Good luck with those flamers =)
Click to expand...
Click to collapse
Thanks white-energy. I use wifi fixer when I need to connect to a wpa network, but it's a less than satisfactory solution because it doesn't stop the connection from dropping - it just reconnects automatically. That means that I can browse almost normally, but streaming video or downloading is still almost impossible.
If you know of better software I would be very much obliged.

etibon said:
Hello, I have an EU HD2 running Hyperdoid 2.1.0, but I've had this problem no matter which rom I tried and I'm at my wits' end trying to solve it.
When I connect to WPA wifi routers, the connection starts out fine, but after a short while my connection to the router seems to get cut off. The delay before this happens could be seconds or it could be 1 or two minutes and seems to depend on the amount of data passing over the interface - when I view a streaming video for example, I get disconnected almost immediately, when I browse pages with few graphics it lasts a bit more. I tried this with 3 or 4 different routers with identical results.
Notwithstanding that no data is getting through, the phone still indicates that I am connected to the wifi router and when I ping the router it gives me a "no route to host". WEP and open networks work fine, so I had to change my home network to WEP, but I'm not conforable with it due to security concerns. I also have problems connecting to public wifi ap's because they are usually secured by WPA.
I suspect that this is related to the wpa_supplicant supplied with tytung's kernel, but I really have no way of knowing what's going on and I haven't been able to find anything in the logs.
Can anybody give me a hand with this? Solving this problem would make the hd2 the perfect phone for me.
Click to expand...
Click to collapse
While I agree that this the wrong forum, should be moved to the right forum et all, here is my $0.02
Have you tried Tytung's NexusHD2 build (not just the kernel)? try 2.8 or 2.9, in my experience his implementation is the most reliable. So reliable that I use the Wifi/BT drivers and related files in my CM7 nightly build. And it works like a charm.
If you are having troubles even in his ROM, something else is wrong. Top of my head, try a different radio. I toggle between 2.12 and 2.15, both with varying degrees of reliability.

ph03n!x said:
While I agree that this the wrong forum, should be moved to the right forum et all, here is my $0.02
Have you tried Tytung's NexusHD2 build (not just the kernel)? try 2.8 or 2.9, in my experience his implementation is the most reliable. So reliable that I use the Wifi/BT drivers and related files in my CM7 nightly build. And it works like a charm.
If you are having troubles even in his ROM, something else is wrong. Top of my head, try a different radio. I toggle between 2.12 and 2.15, both with varying degrees of reliability.
Click to expand...
Click to collapse
Hi ph03n!x,
Thanks for the tips. I haven't tried NexusHD2 because I like the cm7 mods. But I will presently, just to make sure. I'll also try switching radios.

Well.. i guess i have found it... here
It looks like it has some special things.

etibon said:
Hi ph03n!x,
Thanks for the tips. I haven't tried NexusHD2 because I like the cm7 mods. But I will presently, just to make sure. I'll also try switching radios.
Click to expand...
Click to collapse
Give NexusHD2 a shot just to find the Wifi stability.
You can try the latest of the CM7 nightlies released by Arif Ali, along with Tytung's kernel (available in his thread).
I can upload my custom CM7 build based on Arif Ali's CM7 nightlies with Tytung's Kernel and Wifi/ BT drivers and related files somewhere, but am a cLK user. And of course I will have to remove my paid apps from it before sharing

white-energy said:
Well.. i guess i have found it... here
It looks like it has some special things.
Click to expand...
Click to collapse
Hi white-energy. I gave it a test drive but no luck. This software seems to be intended to maintain wifi while the Device is sleeping, but this problem I have occurs while the device is being used. Thanks anyway for your help!
Sent from my HD2 using Tapatalk

ph03n!x said:
While I agree that this the wrong forum, should be moved to the right forum et all, here is my $0.02
Have you tried Tytung's NexusHD2 build (not just the kernel)? try 2.8 or 2.9, in my experience his implementation is the most reliable. So reliable that I use the Wifi/BT drivers and related files in my CM7 nightly build. And it works like a charm.
If you are having troubles even in his ROM, something else is wrong. Top of my head, try a different radio. I toggle between 2.12 and 2.15, both with varying degrees of reliability.
Click to expand...
Click to collapse
I'm about to switch the radio. Let you know what happens .
Sent from my HD2 using Tapatalk

Ok, so I tried switching radio to .12 - no joy. I also tried Tytung's NexusHD2, but it does exactly the same thing.
I don't know what else to try. If there weren't other people with this problem, I would suspect that my phone is defective, but would that make sense given that open networks and wep networks work fine??

Cannot connect to WiFi with EAP (CM7.1)

I use CM7.1 and generally my ZTE Blade works really well. But I do have a problem connecting to the WiFi network at my workplace. It uses WPA2 with EAP (every user has a user name and a password), and no matter what I try to set it up, it just does not connect.
There is a tool called XpressConnect, which configures the WiFi for you. And that works.
I think that leaves only two plausible explanations: either the configuration data I am given is wrong (and that is unlikely, because it works on my computer), or the settings menu for WiFi networks is broken when it comes to EAP. Does that make sense? And is there a way to check the configuration files that are written by the settings tool, and compare them to what XpressConnect does?
I am not in a big rush to solve this issue, but given that WiFi problems seem to rank pretty high with CM, it may be worth tracking down.

MrPuddington said:
I use CM7.1 and generally my ZTE Blade works really well. But I do have a problem connecting to the WiFi network at my workplace. It uses WAP2 with EAP (every user has a user name and a password), and no matter what I try to set it up, it just does not connect.
There is a tool called XpressConnect, which configures the WiFi for you. And that works.
I think that leaves only two plausible explanations: either the configuration data I am given is wrong (and that is unlikely, because it works on my computer), or the settings menu for WiFi networks is broken when it comes to EAP. Does that make sense? And is there a way to check the configuration files that are written by the settings tool, and compare them to what XpressConnect does?
I am not in a big rush to solve this issue, but given that WiFi problems seem to rank pretty high with CM, it may be worth tracking down.
Click to expand...
Click to collapse
I'm not sure about cm7 but in cm 9 there is a option for it

saaransh9 said:
I'm not sure about cm7 but in cm 9 there is a option for it
Click to expand...
Click to collapse
Well there is an option to configure it all right, but it does not connect. Instead it sits around "connecting" for ages, and then disconnects.
If I use XpressConnect to configure it instead, it works as it should. I think that should help to narrow down the problem, but I do not have a lot of experience with how WiFi encryption works internally.