NexusHD2 Android Forum

Odysseus wrote:Notice that the Hostname is till showing as Google and that the IP addr is sill not reachable.

It will always show Google - this the hostname ping uses, not the one used by DNS.

Odysseus wrote:
So if I'm understanding you correctly, HSPA is faster than UMTS and the older Froyo and GB ROMS didn't differentiate these in the connection icon. This is why they show 3G and never H when connected and downloading, however, ICS and JB ROMS do signify H connection types and display this in the connection icon as the connection switches between them.

Was this also the case with default windows ROMS? If so, it would explain why I never saw 'H' while I was in that operating system. However, this wouldn't explain why there is always a failure to connect to the IP address when I run ping tests. This is something I don't understand and haven't been able to find a solution.

Yes, yes and yes:)
I've jus pointed it's unrelated to problem you definitely encountered an we have to look somewhere else

Turns out TCP_NODELAY is supported by tytung's kernel and Arne incidentally fixed this two days ago:
https://code.google.com/p/ics-openvpn/s ... 66b36a30a6
Or maybe he is reading this thread. God bless the Internet. Network of Android device now sending
out smallish TCP packets like it should.

Odysseus wrote:However this wouldn't explain why there is always a failure to connect to the IP address when I run ping tests in any JB ROM, but successfully in GB. This is something I still don't understand and haven't been able to find a solution for. Any help would be greatly appreciated. TIA

Ah, but things are not as complicated as they seem.. I may have missed it or you didn't say - how are you executing ping? Is it via Terminal? If yes, it likely is residing in the system partition.

Next question - are you running any kind of firewall or some other way to block internet access?

If yes, you need to allow root access to the Internet.

Since ping is likely not seen as an individual command most firewalls will consider it only as "root". If root is blocked ping will fail.

If ping succeeds you will see:

Code: Select all

 root@android:/ # ping -c 3 www.yahoo.com
PING ds-any-fp3-real.wa1.b.yahoo.com (98.139.183.24) 56(84) bytes of data.
64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=1 ttl=47 time=266 ms
64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=2 ttl=47 time=694 ms
64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=3 ttl=47 time=343 ms

--- ds-any-fp3-real.wa1.b.yahoo.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 266.310/434.888/694.825/186.487 ms

NYLimited wrote:
Ah, but things are not as complicated as they seem.. I may have missed it or you didn't say - how are you executing ping? Is it via Terminal? If yes, it likely is residing in the system partition.

Next question - are you running any kind of firewall or some other way to block internet access?

If yes, you need to allow root access to the Internet.

Since ping is likely not seen as an individual command most firewalls will consider it only as "root". If root is blocked ping will fail.

If ping succeeds you will see:

Code: Select all

 root@android:/ # ping -c 3 www.yahoo.com
PING ds-any-fp3-real.wa1.b.yahoo.com (98.139.183.24) 56(84) bytes of data.
64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=1 ttl=47 time=266 ms
64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=2 ttl=47 time=694 ms
64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=3 ttl=47 time=343 ms

--- ds-any-fp3-real.wa1.b.yahoo.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 266.310/434.888/694.825/186.487 ms

I'm executing via the 'testing' / 'telephone info' applet invoked by dialing *#*#4636#*#* then selecting 'phone information' / then pressing the 'Run ping test' radio button. I assume the dialer has root.

Odysseus wrote:
I'm executing via the 'testing' / 'telephone info' applet invoked by dialing *#*#4636#*#* then selecting 'phone information' / then pressing the 'Run ping test' radio button. I assume the dialer has root.

I have not tried that so am not sure but I wonder if the dialer can actually perform a ping or calls another module.

As for the dialer proper it would not normally be given internet access since it is, after all, only a dialer...

If you have a firewall or XPrivacy check the logs. If you don't have, install one, try the ping again and see what shows in the firewall log as denied.

NYLimited wrote:
I have not tried that so am not sure but I wonder if the dialer can actually perform a ping or calls another module.

As for the dialer proper it would not normally be given internet access since it is, after all, only a dialer...

If you have a firewall or XPrivacy check the logs. If you don't have, install one, try the ping again and see what shows in the firewall log as denied.

I gave up trying to figure out a way to make ROM Toolkit keep DNS server settings across reboots.

So I went to the market and installed "Set DNS" as suggested and it works fantastically!!! With OpenDNS permanently set lookups are now significantly faster on both Wifi and Mobile. It works so well I just spent 3 bucks for the "pro" version to support its developer.

I also found a couple of build.prop tweaks that actually seem to work though they shouldn't. I changed

Code: Select all

ro.ril.hsdpa.category=8
to
ro.ril.hsdpa.category=10
and
ro.ril.hsupa.category=5
to
ro.ril.hsupa.category=7

I Don't understand why these two tweaks seem to be working because both are beyond what should be supported by the HD2, but they seem to be working for me nonetheless.

I don't have a firewall installed anymore. I used to use "Android Firewall", but uninstalled it when I noticed that most of its functionality such as enabling and disabling certain apps to only transmit on wifi and disable on mobile, and something similar to "privacy guard' was incorporated into CM-10.1.x.

Now if I could only find out why "Ping IpAddr: Fail: IP addr not reachable" and how to resolve it, I think I'd be good to go. TIA

Odysseus wrote:
I gave up trying to figure out a way to make ROM Toolkit keep DNS server settings across reboots.

So I went to the market and installed "Set DNS" as suggested and it works fantastically!!! With OpenDNS permanently set lookups are now significantly faster on both Wifi and Mobile. It works so well I just spent 3 bucks for the "pro" version to support its developer.

I also found a couple of build.prop tweaks that actually seem to work though they shouldn't. I changed

Code: Select all

ro.ril.hsdpa.category=8
to
ro.ril.hsdpa.category=10
and
ro.ril.hsupa.category=5
to
ro.ril.hsupa.category=7

I Don't understand why these two tweaks seem to be working because both are beyond what should be supported by the HD2, but they seem to be working for me nonetheless.

I don't have a firewall installed anymore. I used to use "Android Firewall", but uninstalled it when I noticed that most of its functionality such as enabling and disabling certain apps to only transmit on wifi and disable on mobile, and something similar to "privacy guard' was incorporated into CM-10.1.x.

Now if I could only find out why "Ping IpAddr: Fail: IP addr not reachable" and how to resolve it, I think I'd be good to go. TIA

Hey, at least one thing worked!

Try ping from the terminal window...

Odysseus wrote:
I gave up trying to figure out a way to make ROM Toolkit keep DNS server settings across reboots.

So I went to the market and installed "Set DNS" as suggested and it works fantastically!!! With OpenDNS permanently set lookups are now significantly faster on both Wifi and Mobile. It works so well I just spent 3 bucks for the "pro" version to support its developer.

I also found a couple of build.prop tweaks that actually seem to work though they shouldn't. I changed

Code: Select all

ro.ril.hsdpa.category=8
to
ro.ril.hsdpa.category=10
and
ro.ril.hsupa.category=5
to
ro.ril.hsupa.category=7

I Don't understand why these two tweaks seem to be working because both are beyond what should be supported by the HD2, but they seem to be working for me nonetheless.

I don't have a firewall installed anymore. I used to use "Android Firewall", but uninstalled it when I noticed that most of its functionality such as enabling and disabling certain apps to only transmit on wifi and disable on mobile, and something similar to "privacy guard' was incorporated into CM-10.1.x.

Now if I could only find out why "Ping IpAddr: Fail: IP addr not reachable" and how to resolve it, I think I'd be good to go. TIA

Google DNS server 8.8.8.8 is set in init.htcleo.rc

Code: Select all

    # Wireless properties
    setprop net.dns1 8.8.8.8
    setprop net.dns2 8.8.4.4


You may overwrite it in build.prop

Rumpelteazer wrote:I did report the fp from the phone and from my machine at home. Usually avast is rather quick with changing their definitions. But apparently they still think there is something wrong with it.
Besides none said "Hey Tytung, go fix this!" He Dled the source in an attempt to make sure it's ok. I personally was wondering why this started with V2.4.

I scanned V2.5 settings.apk out of a fresh DL from DepositFiles (checked the MD5 too) and got 8 out of 44 positives :
https://www.virustotal.com/de/file/2638 ... 375878577/

I Uled the settings.apk to avira (who also detected it as obad) as possible fp and would gladly post the answer I get.

Some news on the FalsePositive matters:
I noticed today Avast is no longer bickering about settings.apk beeing an obad-trojan. Apparently someone there took a good look at it.

So I took the time and rescanned settings.apk at Virustotal to make sure https://www.virustotal.com/de/file/26388d210cd60bc87f01f4bc5369ab52d1807149962230463e7ad6c2fe7407b4/analysis/1376752751/ Yay only 7/43

This week I got a reply from the Avira-guys stating settings.apk truly

... does indeed contain malicious behavior, the detection is correct.

but since V2.5 is smoothly running the past weeks on my HD2 I decided to bug them some more. Altough I doubt I'll get any information since I'm using an Avira Free Licence for testing.

V2.6 (Aug. 18, 2013)

• Updated CM-10.1.2 source code.
• Fixed the partial display of date in the lock screen (framework-res.apk: set navigation_bar_height to 24dp)
• Added file systems support (NTFS and exFAT) for SD card (Credit: CM)
• Updated to Google Calendar 201306302
• Updated to Google Maps 7.1.0
• Updated to Google Play Store 4.3.11
• Updated to Google Play services 3.2.25

Downloads:

• ROM: NexusHD2-JellyBean-CM10.1_V2.6.zip (MD5sum: C4F577FD2920181328D72D7819A24C89)
• Tool: NativeSD Recovery v1.0 for NativeSD users.

If you need help with an issue, please post it in the Q&A and troubleshooting topic:
Q&A and Troubleshooting for "NexusHD2-JellyBean-CM10.1"
Let's leave the development topic (this one) for the developers!