NexusHD2 Android Forum

I just migrated from Dynamics WM 6.5.3 to this awesome ROM, thanks alot for putting this out! I can't believe my HD2 is playing 720p H.263 videos in smooth frame rate. Since I don't use Google Play or Market, I even figured out what services to stop, to keep the phone from doing those "Checkins" with Google.

Just one question, does this kernel support TCP_NODELAY? Because OpenVPN for Android claims it doesn't.

Background: I am tunneling everything over TCP-VPN, because my 3G provider enforces a UDP rate limit that kicks in after about five seconds into a session. Which of course breaks everything with modest UDP traffic e.g. OpenVPN in default mode or RTP. So I have to use TCP, but the phone is using Nagle's algorithm, which sends a handful of 20ms RTP packets in one big TCP packet alot of times. Interactivity could be better with TCP_NODELAY.

Since I am booting from SD in NativeSD mode, I saw that kernel ist just in a FAT32 directory where MAGLDR picks it up, so would be easy peasy to replace. But don't lose any hair over this.

Amazing ROM as always Tytung, came from XDA following your job cause is the everyday use ready ROM for our beloved HD2, congrats and thanks for another awsome job.

I was on 2.1 ROM having issues with the incoming call, sometimes shows, sometimes got black screen, and when i separate the phone off my ear the screen always show the dropdown taskbar very annoying btw hope its fixed for me in this new version im playing it on NAND with EXT data... 300MB NAND sys partition 4GB on 4EXT fresh install

Keep up the good work

+QuePPC wrote:Amazing ROM as always Tytung, came from XDA following your job cause is the everyday use ready ROM for our beloved HD2, congrats and thanks for another awsome job.

I was on 2.1 ROM having issues with the incoming call, sometimes shows, sometimes got black screen, and when i separate the phone off my ear the screen always show the dropdown taskbar very annoying btw hope its fixed for me in this new version im playing it on NAND with EXT data... 300MB NAND sys partition 4GB on 4EXT fresh install

Keep up the good work

I'm using v2.5 with your same NAND space and DataOnEXT, but using EXT3 respect EXT4. All works very very very smooth! I don't want change for another phone. Also using JuiceDefender Pro, i can reach 21h without AC cable, with normal battery, low brightness and Wifi/3G turned always on!

I have a question. I've tried to format my SD in EXT4 using Eseaus Partition, but my CWM 8 touch doesn't want recognize my SD. Only if i format EXT3 using CWM's tool, i can do everything. But i'm still on EXT3!

What i can do for allow SD EXT4 reading? i need another recovery?

devilpera64 wrote:I'm using v2.5 with your same NAND space and DataOnEXT, but using EXT3 respect EXT4. All works very very very smooth! I don't want change for another phone. Also using JuiceDefender Pro, i can reach 21h without AC cable, with normal battery, low brightness and Wifi/3G turned always on!

I have a question. I've tried to format my SD in EXT4 using Eseaus Partition, but my CWM 8 touch doesn't want recognize my SD. Only if i format EXT3 using CWM's tool, i can do everything. But i'm still on EXT3!

What i can do for allow SD EXT4 reading? i need another recovery?

You could try the new Paragon version which may help...

I've discovered a bug that appears to exist in at least the last three versions of this ROM that causes 3G connectivity instability and thus slower data connection speeds. I discovered it by accident and spent the last three days franticly looking for solutions all over the net, but perhaps Tytung or one of the other helpful folks here can come up with a workaround.

I've been noticing for quite some time that whenever I download of any type of data stream to my phone it drops from 3G to H and sometimes even E. At idle the phone nearly always shows it's at 3G then the moment I begin to download any type of data the fluctuations occur. (It's not related to MAGLDR or cLK as it occurs with both.)

I chalked it up to T-Mobile being inconsistent in my area and even contemplated switching providers. It's not related to T-Mobile throttling my service as I've never exceeded my 2.5GB allotment. This past week I've had my Mom and Step-Dad's spare phone so I could unlock it for their upcoming trip to the Islands. They use AT&T so it was simply a matter of me calling them up inserting my T-Mobile SIM card and inputting the unlock code. The thing is I noticed how much faster their phone was with my SIM then mine is even though the HD2 is supposed to be faster. So I decided to investigate further.

I've been wanting to unlock my phone for some time, but I've been too lazy to reflash back to Windows and didn't have a non T-Mobile SIM to initiate the unlock process. I figured now was as good a time as any. So I backed up everything and reinstalled the latest T-Mobile OEM Windows ROM and unlocked my phone. Out of curiosity I checked my download speeds on AT&T and noticed my phone was significantly faster. Then I shut down my phone put back in my T-Mobile SIM and noticed that my speeds remained significantly faster than what I'm used to with the NexusHD2 ROM. I drove all over my area here in South Florida and tested in places that my phone normally receives poor reception and quite to my surprise speeds there remained consistently faster than what I'm used to.

I flashed back into this ROM trying it with MAGLDR and 3 different versions of cLK including Black LK and still experienced inconsistent connections with all. Over the course of the last three days I've tried the last three versions of this ROM and all had this issue. I also tried the GB ROM (which doesn't appear to be affected). So something has been introduced in the latest ROMS that negatively affects data speeds that wasn't present with the much older ROM.

To work around this I've tried adjusting just about every setting in my build.prop affecting the radio, but with no success. I even spoke to T-Mobile tech support to trouble shoot but with no luck. However we did discover several things that could be negatively impacting network performance. For one these ROMS are setup to use the Google DNS servers by default. T-Mobile suggests setting to their local servers but I couldn't figure out how to make this change.

We also found that there must be a problem elsewhere in the network configuration because when I use the 'Testing / Phone Information' applet *#*#4636#*#* and run the ping test most result look good, however, Ping IpAddr: results as either "unknown" or "IP addr not reachable". Also when the connection is idle it shows 'Network type: UMTS' which is 3G, However while pinging or whenever any data download is occurring, it reads 'Network type: HSDPA' as can be seen in the second screen shot. The T-mobile tech suggested that when I'm able to get that resolved my network instability will probably be resolved too.

Any help would be greatly appreciated!!!! TIA

Here are screen shots:

Odysseus wrote:However we did discover several things that could be negatively impacting network performance. For one these ROMS are setup to use the Google DNS servers by default. T-Mobile suggests setting to their local servers but I couldn't figure out how to make this change.

You can easily use SetDNS to change DNS servers to one that you like better.
For example, I use OpenDNS on all my devices. ROM Toolbox also has an option to set this.

@Odysseus, some clarification for you:
When your phone shows E (data type: EDGE), you are using 2g network (or 2g connection).
3g (data type: UMTS) means... 3g
H (data type: HSPA) means, that your phone is using High Speed Packet Access, fast internet connection based on 3g network.

In fact HSPA is faster than 3g

Android 4+ when in range of 3g/HSPA capable network, use 3g and switch to HSPA when connection is active. So in your case this looks exactly as intended

NYLimited wrote:
You can easily use SetDNS to change DNS servers to one that you like better.
For example, I use OpenDNS on all my devices. ROM Toolbox also has an option to set this.

I've got ROM Toolbox installed and have issues with it too. Perhaps I'm not understanding how to properly use that feature. When I go to 'DNS Changer' and set to a different DNS (OpenDNS for example) I tell it to override on both Wifi and Mobile however the settings don't seem to take, and doesn't last across reboots. For when I reboot and check in ROM Toolbox it's always reset to Google. For example here is the screen shot of Rom Toolbox:




However it makes no difference to my download speeds and the issues mentioned above as evidenced by this screen shot below, which was taken after changing the DNS server in ROM Toolbox: Notice that the Hostname is till showing as Google and that the IP addr is sill not reachable.

Odysseus wrote:I've got ROM Toolbox installed and have issues with it too. Perhaps I'm not understanding how to properly use that feature. When I go to 'DNS Changer' and set to a different DNS (OpenDNS for example) I tell it to override on both Wifi and Mobile however the settings don't seem to take, and doesn't last across reboots. For when I reboot and check in ROM Toolbox it's always reset to Google.

However it makes no difference to my download speeds and the issues mentioned above as evidenced by this screen shot below, which was taken after changing the DNS server in ROM Toolbox: Notice that the Hostname is till showing as Google and that the IP addr is sill not reachable.

I am not convinced that changing to OpenDNS (or similar) will result in a significant speed increase although there are other/different benefits to doing this.

The settings must be re-written during each boot and, at times, even during use (i.e. you change to/from wifi or lose and re-gain data connectivity). ROM Toolbox *should* be doing this automatically. Can you tell if it runs during the boot process? I use SuperSU and the log will show each time ROM Toolbox runs and makes a change.

DNS Changer may work better for you, don't know.


Alternately, you could create a script and run it from your iniit.d folder. However, this does not fix the possible problem of reverting between boots. This is also a bit more elaborate. There are probably a number of scripts around you could try. I found this old one in one of my folders but I am not certain it is still accurate or not so use caution:

Code: Select all

#!/system/bin/sh
setprop dhcp.tiwlan0.dns1 208.67.222.222
setprop dhcp.tiwlan0.dns2 208.67.220.220
setprop net.ppp0.dns1 208.67.222.222
setprop net.ppp0.dns2 208.67.220.220
setprop net.dns1 208.67.222.222
setprop net.dns2 208.67.220.220
setprop net.rmnet0.dns1 208.67.222.222
setprop net.rmnet0.dns2 208.67.220.220
setprop net.pdpbr1.dns1 208.67.222.222
setprop net.pdpbr1.dns2 208.67.220.220

Lastly,you could locate and overwrite the file(s) that ROM Toolbox modifies. You will have to double check this as I am quoting from memory (which is not perfect) but it should be something like "/system/etc/ppp/ip-up" and change the lines specified to the DNS server you want to use. That should allow the changes to stick through a reboot, and will take effect anytime you enable/disable the data connection.

Lots of choices!

donblazello wrote:@Odysseus, some clarification for you:
When your phone shows E (data type: EDGE), you are using 2g network (or 2g connection).
3g (data type: UMTS) means... 3g
H (data type: HSPA) means, that your phone is using High Speed Packet Access, fast internet connection based on 3g network.

In fact HSPA is faster than 3g

Android 4+ when in range of 3g/HSPA capable network, use 3g and switch to HSPA when connection is active. So in your case this looks exactly as intended

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 while connected and downloading. However ICS and JB ROMS do signify H connection type and indicates as it switches.

Was this also the case with default Windows ROMS? If so, it would explain why I never saw 'H' while I was in any of those operating system. 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