Database Develop

Wifi Rx speed too low

Dear all,
On TyTN II, I found something strange, either on WM6.0 and WM6.1.
When you go in Setting/Connexions/Wireless network, you can see some technical details, including Rx and Tx speed.
I have tested to improve performance in Power Setting tab, and even after a Restart of the TyTN II, no change on Rx speed : It remains at 1 Mb.
Performance is always :
Tx : 54 Mb
Rx : 1 Mb
Is there a way to increase the Rx speed ?
Thanks in advance.

Did you try on different access points?

Did you try on different access points?
Click to expand...
Click to collapse
Yes... At home (Freebox), at work (D-link access point).
Same results...
Any idea ?

I get the same behavior after the upgrade to WM 6.1. I believe it to be a display issue as it certainly doesn't seem any slower, but that could just be perception. Would need to run a connection benchmark to verify.

On a second look, I noticed that initially the Rx Rate tends to fluxuate between 54Mbps to 1Mbps before settling on 1Mbps. I'm still thinking its a display issue, but I'll do some ore testing today (I noticed the Rate doesn't seem to change with the signal quality).
Edit: I think I see what's going on. This probably has to deal with the power management on the phone. When the phone is idle (not receiving anything) the speed drops to 1Mbps after a period of idle time. If I ping the phone from my system, the Rx Rate immediately steps up to 54Mbps and stays there until some time after the last ping (when it drops back to 1Mbps).
So basically:
Idle (no data being received): 1Mbps
Active (data being received): 54Mbps (or whatever the best speed it can reach is).
Data receive finished: Sits at 54Mbps until a certain amount of idle time has passed, then returns to 1Mbps.

So basically:
Idle (no data being received): 1Mbps
Active (data being received): 54Mbps (or whatever the best speed it can reach is).
Data receive finished: Sits at 54Mbps until a certain amount of idle time has passed, then returns to 1Mbps.
Click to expand...
Click to collapse
Welll... You are right.
After some testing, when data are received, Rx rate change and go back to 1Mb when flow stops !
In fact, no problem... Just a value that is adjusted in realtime
Thank you very much for your help.
Laurent.

I'm looking for an app like this (see inside).

Required:
- Running on N1
- Silently in the background, continuously, doing a very little and bandwidth limited download process
- The download process will not use SD space at all or will use a very little space and not growing in space
Optional:
- Can set the timer of that continuously download process
- Have an icon (widget?) to monitor it
Why do i need that?
Because i want that H "downlink and uplink icon" go online all the time even when my internet is idle. Currently, if my internet is idle, H icon will empty, and then when i'm trying to use internet there is an annoying establishing connection process for like 10 or 20 seconds before i can actually use the internet.
Thanks before.

you want to be connected to hsdpa all the time , hmm i get the point but wouldn't it drain the battery faster?

Yeah. But sometime i need that, for example when i'm tethering it while i'm charging it next to my laptop.

l1k3m1k3 said:
Yeah. But sometime i need that, for example when i'm tethering it while i'm charging it next to my laptop.
Click to expand...
Click to collapse
tethering has priority over sleeping, im pretty sure its supposed to stay on and connected when tethering. If it is losing connection its probably a signal strength/location issue.

Yeah. But also, there are other scenarios where i prefer speed over the battery.
Any idea what app i should look?

Run "ping" from a command line to any server out there (www.google.com for example), and enjoy constant connection
But I suggest looking into your settings, there is no good reason why HSPDA connection initialization should take more than a couple of seconds.

Complaint to your network operator!
The network operator should manage the connections timers to avoid long connections times...
If the amount of data in buffer is below some threshold the configuration in the network shold move you to a low capacity common channel (FACH), after that, if the amount of data is zero, you change to a state called cell_pch, where you still have the connection but don't use physical resources. You should be in this state for a couple of hours before being disconnected.
it shoudnt takes more than 1 sec to be on HSDPA again!!
Complaint to your network operator!

Yeah.
Thanks for the help guys.

[Q] Ghost Data Connection

Hi, I've buy an Italian Vodafone Galaxy Tab about 3 weeks ago so I'm a new users of this device (and Samsung's Android device too).
Two days ago I use the 3G data connection for the first time, and I've noticed a huge amount of data traffic monitoring the connection with traffic monitor (you can find it on the market).
I have an HTC HD2 with android before, and I use about 112 Mb of traffic in a mounth.
In one day with galaxy tab I've used 50 Mb of traffic leaving the connection actived but not in use.
So I monitored the situation and realised that :
when I turn on the 3G data connection and I leave it on stand by it doesn't generate traffic.
If I only open the browser or any application that use data, than I close it with task manager, the GT start to use data on stand by like 1 Mb every 5 minute or less.
All the auto-update of the application installed is turned off, and also the auto sync (I'm not a noob of Android) and I kill all the background app.
Anyone of you knows a solution for this problem?
It's a little bit annoying because I've a limited data plan and I can't use so large amount of data, even if I open a single web page without any plugin it use 4 Mb or even more (like 300Kb for the web page and the rest is ghost traffic).
Thank you in advance for any suggest

Take another look at GrooVeIP

I tried GrooVeIP in January with my Nexus 4 and had all sorts of problems with call quality and connection.
I went back and had another try recently and noticed new settings related to audio APIs for Jelly Bean.
For me, this now works better than the various VOIP apps, even though the G711 codec used by GrooVeIP should not do as well as the other codecs available for the other apps such as G729.
One more point and then I will describe my setup.
I understand that using TCP to connect to a VOIP provider should allow for a setup that is less of a burden on the battery. My experience is that there are so few providers offering this option, and so little testing/refinement of the VOIP apps when used with TCP that it is a struggle to enjoy this benefit. It is easier on one's mental health to carry a backup battery, car charger, etc.
I can add that personally, I did not notice a big difference in battery life when using TCP or UDP.
My setup
Nexus 4, not rooted.
Android 4.2.2
T-Mobile $30 plan
typical cell signal at home: HSPA -95dBm (weak)
wifi: off
Google Voice account
GrooVeIP Feb 9, 2013 version
GrooVeIP settings:
Y = checked
Allow 3G/4G calling Y
Accept calls on answer Y
Native Dialer Options
Built In Dialer Preference - Always use GrooVeIP
Inclusion, Exclusion options - ignored
Audio/Echo Settings
Echo Cancellation - Basic
Speaker Volume 0
Microphone Gain 4
Bluetooth - not using this
Ringtone Override - None
Use Contact Ringtones - N
DMTF Feedback Y
Troubleshooting
Keep Screen On Y
Accept Call Time 30
Audio Processing N
Wifi Tablet N
Synchronize Voice Y
Audio Mode Fallback N
Audio Routing - N
Mic Buffer - Small
Mic Source - Auto detect
Partial Wake Lock - Y
High Perf Wake Lock - N
Disable JB Audio APIs - Y
Starting Audio Port - defaults
Audio Port Count - defaults
Reconnect Interval 1 minute
Override Stun Server N
Miscellaneous
Accessibility Settings - default
Notification Settings - all Y
Startup Autostart Y
Startup Use Time Settings N
Auto-answer N
Allow Rotate N
Default area code- none
Disable Bluetooth - Y
Google Talk Status (managed by GrooVe Forwarder app)
Invisible Status N
GrooveIP Call Log Y
Native Call Log N
Show Invisible Contacts Y
Of course many of these settings have no impact on the problems I had in January. Still, I took a few minutes to create a template that others can copy, edit and paste for other purposes.
Since calling over 3G/4G is never perfect, I recommend adding an app to your home screen that provides real-time cellular signal info, such as
Network Signal Info from Kaibits. At home where I have a weak signal, GrooVeIP works just fine. Moving anywhere else, especially inside buildings and I need to pay attention to the signal. (Not that conventional GSM from T-Mobile is sure to be any more reliable in those situations)

Thanks a lot for this amazing profile. I had some of the options you mentioned, but the "accept call time" was the best. I had this problem and I did't know what to do. Now I know...

hotelalfa said:
For me, this now works better than the various VOIP apps, even though the G711 codec used by GrooVeIP should not do as well as the other codecs available for the other apps such as G729.
One more point and then I will describe my setup.
I understand that using TCP to connect to a VOIP provider should allow for a setup that is less of a burden on the battery. My experience is that there are so few providers offering this option, and so little testing/refinement of the VOIP apps when used with TCP that it is a struggle to enjoy this benefit. It is easier on one's mental health to carry a backup battery, car charger, etc.
I can add that personally, I did not notice a big difference in battery life when using TCP or UDP.
Click to expand...
Click to collapse
1. Glad to hear that GrooveIP works for you. Unfortunately, 3g here can't support GrooveIP. Where do you live?
2. If you have the bandwidth, G711 will always be better than G729. G729 is only good under slow connection such as 3g here.
3. If TCP consumes the same battery as UDP, you didn't set up TCP properly. My TCP battery consumption is 50% of UDP's.
I wish everybody could use GrooveIP reliably over 3g. Then life will be so much better.

Thank you for your efforts i will give it a shot

acegolfer said:
1. Glad to hear that GrooveIP works for you. Unfortunately, 3g here can't support GrooveIP. Where do you live?
2. If you have the bandwidth, G711 will always be better than G729. G729 is only good under slow connection such as 3g here.
3. If TCP consumes the same battery as UDP, you didn't set up TCP properly. My TCP battery consumption is 50% of UDP's.
I wish everybody could use GrooveIP reliably over 3g. Then life will be so much better.
Click to expand...
Click to collapse
1. I am in Richmond VA. The signal varies widely from place to place here.
2. For some reason GrooVeIP likes the bandwidth I have better now than in January. Your point about the merits of the codecs is well taken.
3. I did notice some difference in battery drain, just not enough to push me to a solution more complicated than using an off the shelf app. The off the shelf apps each had their limitations when it comes to addressing this issue (going direct to a VOIP provider). Between the elaborate solutions written up here using pbx intermediaries, and GrooVeIP, I am now content with GrooVeIP.

[Q] Wi-fi Speeds

Hi
Wonder if anyone experienced the same problems as me.
The Wi-fi speeds I am getting is around 30 mb on my nook, although this is a reasonable speed I noticed that it goes down sometimes quite a bit. I belive the nook can only connect to the 2.4g wifi and not the 5g.
In comparison my windows laptop (2.g) gets 50mb
My Iphone gets 55mb and my other Windows tablet gets around 45mb
I now the Nook is quite old now so is it just not able to pick up high fiber-optic speeds or is there a fault somewhere?
Thanks

Yes, the Nook only supports 2.4 GHz 802.11n, with a maximum MCS index of 7.
What does that mean? Wikipedia has a handy table here.
It might look confusing at first, but here is how it works. The maximum data rate depends on three factors (apart from the modulation type):
1. the number of spatial streams (basically antennas, 1-4)
2. whether or not 40 MHz wide channels are supported
3. whether or not short guard intervals (GI) are supported
The WiFi chip in the Nook has only one antenna and supports neither 40 MHz channels nor short GI (at least it's set up that way in our firmwares). Therefore, the maximum achievable data rate is 65 MBit/s.
It can also be lower, if the signal is weak. You can check the current number in Android's WiFi settings, by touching the name of the WiFi you're currently connected to.
However, that's the link speed, the theoretical maximum that also includes WiFi protocol overhead. In practice, you can consider yourself lucky if you achieve about half of that for payload / user data.
So, if your tablet is connected at 65 MBit/s, you can expect a usable data rate of about 32 MBit/s at best (3.8 MiB/s). The final data rate can also be throttled even further by other system components, like bus and CPU speed, etc.
My phone for example also has MCS index 7, but supports 40 MHz, and therefore has faster WiFi with link speeds up to 135 MBit/s. And my notebook has MCS index 15, two antennas, with both 40 MHz and short guard interval, therefore achieving 300 MBit/s (provided of course your WiFi router / access point supports that as well).
Long story short, the relatively slow speed you're getting on the Nook is probably normal and by design.

Thanks for the detailed post.
I am guessing that 30 mb is quite good then in comparison

[email protected] said:
Thanks for the detailed post.
I am guessing that 30 mb is quite good then in comparison
Click to expand...
Click to collapse
Your speed is about all its going to get but in comparison to it being bad? Its rather bad...
Because I'm Bad, I'm Bad-
Come On
(Bad Bad-Really, Really Bad)
You Know I'm Bad, I'm Bad-
You Know It
(Bad Bad-Really, Really Bad)