I wish to submit the following Speedtest.Net results.
Can anyone tell me what is going on?
1. Test #1 = Network "W", 1700 AWS, HSDPA
ZTE Axon 7/Android 6 Nexus 5X/Android 7
Down Up Ping Down Up Ping
7.68 1.35 37 5.43 1.51 39
5.36 1.50 39 5.50 1.41 39
3.90 1.49 55 9.87 1.54 39
Averages:
5.65 1.45 43.7 6.93 1.49 39
% Better on the Nexus 5X
18% 3% 11%
2. Test#2 = Network "F", 1700/2100, LTE
Nexus 5X/Nougat Axon 7/Marshmallow
Down Up Ping Down Up Ping
87.75 22.61 29 46.78 7.43 37
79.58 19.85 27 68.33 7.48 38
88.72 14.47 21 54.99 7.36 35
Averages:
85.35 18.98 25.67 56.70 7.42 36.67
% Better on the Nexus 5X
34% 61% 30%
There appears to be a HUGE difference in the speed of cellular data transfer, both on a HSDPA network, and on a LTE network.
WHY???
Related
Mobile Speed Test.com
Thanks for using Mobile Speed test, your results are below:
Free Trial - Unltd dwnlds!
Your speed: 1123.596 Kbps
Your latency: 0.375 seconds
Transferred 500 KB in 3.56 seconds
Share your results with everyone!
28.8 kbps dial-up
33.6 kbps dial-up
40 kbps GPRS
56 kbps dial-up
128 kbps ISDN
144 kbps 1xRTT
236.8 kbps EDGE
384 kbps Low DSL
400 kbps 3G ( EVDO / HSDPA )
768 kbps Broadband
1000 kbps Fast 3G
1124 kbps YOU
1500 kbps Basic DSL
2500 kbps 4G (Wimax/HSPA+)
We recommend you try the 500KB or the 1MB test to accurately test your connection
Test again: 100KB | 500KB | 1MB | 2MB test
Share your results with everyone!
Your ISP is Sprint. How do you compare?
Do we have the wrong ISP? Click here to let us know.
Did anything go wrong during the test? Do you have any feedback? Click here to talk to us.
With 1 bar on 3g I get around 1000-1100 with full bars on 3g I get around 2500-2700
Sent from my PC36100 using XDA App
I just got 1.5 at -85 dBm. So, not bad.
Sent from my iPhone with the bigger Gee Bees.
someone want to move this to the general section.
why on earth would you post this in the Dev section.
After nearly a month of periodic outages and erratic 1x speeds, 4G performance has stabilized at near pre-upgrade levels, but tethering speeds have suffered a near knock-out punch.
Pre-Upgrade
Tower to device average mid day 4.5 mbps / 1.03 mbps
Tethered P.C. (Easytether) 4.5 mbps / 1.03 mbps
Tower to device average evening 2.5 mbps / 1.03 mbps
Tethered P.C. (Easytether) 2.5 mbps / 1.03 mbps
Post upgrade
Tower to device average mid day 4.0 mbps / 0.80 mbps
Tethered P.C. (Easytether) 0.6 mbps / 0.65 mbps
Tower to device average evening 2.5 mbps / 0.80 mbps
Tethered P.C. (Easytether) 0.5 mbps / 0.65 mbps
Now get this sh*t,
Simultaneous speed tests...
Tethered P.C. started first
Tower to device mid day 2.5 mbps / 0.65 mbps
Tethered P.C. 0.8 mbps / 0.70 mbps
Evo started first
Tower to device 3.0 mbps / 0.75 mbps
Tethered P.C. 1.5 mbps / 0.80 mbps
Any ideas how to get tethered speeds up to pre-upgrade levels? My Evo is running the same Myn's RLS 5 w/ SBC 4.1.9. net's before and after tower upgrade. I've done full wipe and fresh install, reprovisioned, the works.
I have played with Filter Proxy to no avail.
Should I roll back to 2.1?
So I have been conducting some testing of data speeds, and specifically started tests between the AT&T 36P and 37P radios. I am finding no difference at all in speeds between either on Jokersax CM9 with Faux 025 1.0GHz kernel, but what is interesting is the following:
Speeds (just outside Boston, MA) just before 9.00am EST (ping/dl Mbps/ul Mbps):
136 5.53 0.92
159 4.24 0.57
134 4.82 1.06
143 5.48 1.10
149 4.35 0.69
Speeds (same location) just after 9am EST:
139 1.86 1.08
136 1.74 1.08
140 1.85 1.10
145 1.83 1.11
138 1.82 1.09
Back to back speed tests. You can see the post 9am numbers are much more consistent across the board. I know we have differences in traffic dependent on time of day/night, but what concerns me here is the definite change in dl speed. Could it be that AT&T throttles data for all users at different times of the day/night which they deem to be high traffic times?
I don't think there is any intentional throttling going on with ATT, odds are it is a direct result of high traffic on the network. Same goes for broadband internet service, speeds are subjected to how many people are trying to get a slice of the same pie.
Sent from my MB860 using XDA App
Interesting.
Here are some of my results, time and dates vary, Location Denver, CO. Using Speedtest.net app (time,date,ping/dl Mbps/ul Mbps)
9:54pm, 02/14 181 2.05 0.62
9:55pm 02/14 157 2.25 0.82
9:33pm 02/18 158 2.25 1.35
7:49am 02/19 159 2.55 1.63
No real pattern I can detect. Download speeds seem pretty consistent. Will update once I get more test results.
consider yourself fortunate. Your lower numbers are the best I ever see here. Really pisses me off how slow they are to getting around to even getting us true 3g speeds, and they are already touting their 4g cause they put it in a few cities.Ma bell all over again.
after the 4.4 upgrade I noticed that my WiFi was significantly (%90) slower
Before kitkat wifi speed was 35 to 40 Mbps max,,After the kitkat wifi speed is 3/5 mbps almost %90 down I try everything reseting the phone,resetting the fibre optic modem nothing works
But i try Ookla speed test on galaxy express 2 connected the same network and speed was 38 mbps
Is this right ?
Hi,
I have a Note 3 SM-N9005 running a Temasek's UNOFFICIAL CM12.1 with an arte97 kernel and the latest bootloader and modem. Yesterday I changed my 18 months old battery with a new Anker 3200mAh battery.
Although, the battery life increased with about 30-40%, I still feel like I don't get enough Screen ON timpe when comparing my battery stats to others I found online. Some people get arroung 6 hours os Screen ON time, while I only got about 3 and a half hours. I also use greenify to freese a lot of apps and I did not use GPS in this session.
Can someone please take a look at my BBS logs and tell me if there's something that eats too much battery, some service that I may not be aware of? I'm asking this here becouse at a first glance, everything looks OK. Or maybe I am mistaken and my battery life is OK...or maybe after a new battery only reaches its full potential after more than one cycle, the attached logs being for my first cycle after the replacement. I am pasting here only the top consumers because the log is really long. For the entire thing, please check the attachment. There are many other parameters like alarms (many), CPU and Network logs.
I would really appreciate any oppinion. Thanks a lot.
BetterBatteryStats version: 2.0.0.0
Creation Date: 2015-06-30 19:29:03
Statistic Type: Unplugged to Current
Since 1 d 3 h 30 m 53 s
VERSION.RELEASE: 5.1.1
BRAND: samsung
DEVICE: hltexx
MANUFACTURER: samsung
MODEL: SM-N9005
OS.VERSION: 3.4.107-arter97-7.0.1-g17147d9-01916-g6f9acf6
BOOTLOADER: N9005XXUGBOEA
HARDWARE: qcom
FINGERPRINT: samsung/hltexx/hlte:4.4.2/KOT49H/N9005XXUENC2:user/release-keys
ID: LMY48B
TAGS: test-keys
USER: root
PRODUCT: cm_hlte
RADIO: N9005XXUGBOD3
Rooted: true
SELinux Policy: Permissive
BATTERY_STATS permission granted: true
XPosed BATTERY_STATS module enabled: false
============
Battery Info
============
Level lost [%]: Bat.: -96%(100% to 4%) [3.5%/h]
Voltage lost [mV]: (4231-3630) [21.8%/h]
===========
Other Usage
===========
Deep Sleep (): 21 h 28 m 31 s 78.1%
Awake (): 6 h 2 m 21 s 21.9%
Screen On (): 3 h 35 m 58 s 13.1%
Phone On (): 18 m 4 s 1.1%
Wifi On (): 14 h 41 m 25 s 53.4%
Wifi Running (): 14 h 41 m 24 s 53.4%
No Data Connection (): 13 h 31 m 15 s 49.1%
No or Unknown Signal (): 13 h 31 m 15 s 49.1%
Moderate Signal (): 10 m 41 s 0.6%
Screen dark (): 1 h 31 m 48 s 5.6%
Screen dimmed (): 1 h 59 m 56 s 7.3%
Screen medium (): 4 m 13 s 0.3%
======================================================
Wakelocks (requires root / system app on Android 4.4+)
======================================================
AudioMix (com.android.gallery3d.Gallery): 28 m 15 s Count:1 1.7%
ProximitySensorManager (): 15 m 6 s Count:784 0.9%
*net_scheduler* (Google Play services): 6 m 42 s Count:3940 0.4%
AudioMix (ro.callromania.callRomania): 5 m 32 s Count:11 0.3%
AudioIn (ro.callromania.callRomania): 5 m 32 s Count:10 0.3%
com.csipsimple.ongoingCallLock (ro.callromania.callRomania): 5 m 30 s Count:126 0.3%
com.csipsimple.CallProximity (ro.callromania.callRomania): 5 m 26 s Count:9 0.3%
AudioMix (1013): 5 m 22 s Count:186 0.3%
WeatherUpdateService (com.cyanogenmod.lockclock.cLock): 4 m 20 s Count:27 0.3%
Icing (Google Play services): 3 m 51 s Count:1798 0.2%
GCM_CONN_ALARM (Google Play services): 3 m 47 s Count:161 0.2%
AudioMix (com.google.android.youtube.YouTube): 3 m 7 s Count:3 0.2%
*alarm* (): 2 m 54 s Count:2459 0.2%
AudioMix (com.android.chrome.Chrome): 2 m 52 s Count:182 0.2%
WakeupEventReceiver (com.skype.raider.Skype): 2 m 41 s Count:1 0.2%
ActivityManager-Launch (): 2 m 29 s Count:768 0.2%
NextAlarmTracker (): 2 m 24 s Count:820 0.1%
AudioIn (com.google.android.googlequicksearchbox.Google App): 1 m 50 s Count:41 0.1%
RILJ (Phone): 1 m 9 s Count:5678 0.1%
sendinactive (com.whatsapp.WhatsApp): 1 m 2 s Count:51 0.1%
ConnectivityService (): 57 s Count:773 0.1%
GsmConnection (Phone): 39 s Count:5722 0.0%
SipWakeLock (ro.callromania.callRomania): 38 s Count:280 0.0%
AWakeLock (1013): 33 s Count:7 0.0%
AudioMix (com.facebook.katana.Facebook): 32 s Count:259 0.0%
================
Kernel Wakelocks !!! wakeup_sources !!!
================
PowerManagerService.Display (): 4 h 12 m 53 s Cnt: (c/wc/ec)120/0/0 15.3%
bam_dmux_wakelock (): 2 h 3 m 23 s Cnt: (c/wc/ec)3360/110/0 7.5%
PowerManagerService.WakeLocks (): 1 h 52 m 50 s Cnt: (c/wc/ec)10290/230/0 6.8%
wlan_rx_wake (): 44 m 35 s Cnt: (c/wc/ec)6497/78/6497 2.7%
wlan_wd_wake (): 44 m 34 s Cnt: (c/wc/ec)11015/182/0 2.7%
radio-interface (): 31 m 36 s Cnt: (c/wc/ec)1496/52/0 1.9%
event0-768 (): 11 m 4 s Cnt: (c/wc/ec)2721/2/0 0.7%
event1-768 (): 11 m 3 s Cnt: (c/wc/ec)2723/2/0 0.7%
event4-768 (): 10 m 53 s Cnt: (c/wc/ec)121859/2/0 0.7%
event15-768 (): 10 m 30 s Cnt: (c/wc/ec)3194/179/0 0.6%
event2-768 (): 10 m 28 s Cnt: (c/wc/ec)2964/2/0 0.6%
event3-768 (): 10 m 28 s Cnt: (c/wc/ec)2738/2/0 0.6%
nfc_wake_lock (): 9 m 59 s Cnt: (c/wc/ec)262/0/261 0.6%
wlan_wake (): 6 m 41 s Cnt: (c/wc/ec)247593/277/0 0.4%
alarm (): 4 m 53 s Cnt: (c/wc/ec)4311/824/0 0.3%
smdcntl0 (): 4 m 34 s Cnt: (c/wc/ec)9633/247/0 0.3%
resume_wakelock (): 4 m 17 s Cnt: (c/wc/ec)2715/2/2715 0.3%
alarm_rtc (): 3 m 20 s Cnt: (c/wc/ec)847/177/0 0.2%
ssp_wake_lock (): 2 m 43 s Cnt: (c/wc/ec)1506/9/30 0.2%
PowerManagerService.Broadcasts (): 2 m 16 s Cnt: (c/wc/ec)242/0/0 0.1%
wlan_ctrl_wake (): 2 m 12 s Cnt: (c/wc/ec)622/1/622 0.1%
sec-battery-monitor (): 58 s Cnt: (c/wc/ec)3403/179/0 0.1%
KeyEvents (): 39 s Cnt: (c/wc/ec)126749/379/0 0.0%
AlexBlomkvist said:
Hi,
I have a Note 3 SM-N9005 running a Temasek's UNOFFICIAL CM12.1 with an arte97 kernel and the latest bootloader and modem. Yesterday I changed my 18 months old battery with a new Anker 3200mAh battery.
Although, the battery life increased with about 30-40%, I still feel like I don't get enough Screen ON timpe when comparing my battery stats to others I found online. Some people get arroung 6 hours os Screen ON time, while I only got about 3 and a half hours. I also use greenify to freese a lot of apps and I did not use GPS in this session.
Can someone please take a look at my BBS logs and tell me if there's something that eats too much battery, some service that I may not be aware of? I'm asking this here becouse at a first glance, everything looks OK. Or maybe I am mistaken and my battery life is OK...or maybe after a new battery only reaches its full potential after more than one cycle, the attached logs being for my first cycle after the replacement. I am pasting here only the top consumers because the log is really long. For the entire thing, please check the attachment. There are many other parameters like alarms (many), CPU and Network logs.
I would really appreciate any oppinion. Thanks a lot.
BetterBatteryStats version: 2.0.0.0
Creation Date: 2015-06-30 19:29:03
Statistic Type: Unplugged to Current
Since 1 d 3 h 30 m 53 s
VERSION.RELEASE: 5.1.1
BRAND: samsung
DEVICE: hltexx
MANUFACTURER: samsung
MODEL: SM-N9005
OS.VERSION: 3.4.107-arter97-7.0.1-g17147d9-01916-g6f9acf6
BOOTLOADER: N9005XXUGBOEA
HARDWARE: qcom
FINGERPRINT: samsung/hltexx/hlte:4.4.2/KOT49H/N9005XXUENC2:user/release-keys
ID: LMY48B
TAGS: test-keys
USER: root
PRODUCT: cm_hlte
RADIO: N9005XXUGBOD3
Rooted: true
SELinux Policy: Permissive
BATTERY_STATS permission granted: true
XPosed BATTERY_STATS module enabled: false
============
Battery Info
============
Level lost [%]: Bat.: -96%(100% to 4%) [3.5%/h]
Voltage lost [mV]: (4231-3630) [21.8%/h]
===========
Other Usage
===========
Deep Sleep (): 21 h 28 m 31 s 78.1%
Awake (): 6 h 2 m 21 s 21.9%
Screen On (): 3 h 35 m 58 s 13.1%
Phone On (): 18 m 4 s 1.1%
Wifi On (): 14 h 41 m 25 s 53.4%
Wifi Running (): 14 h 41 m 24 s 53.4%
No Data Connection (): 13 h 31 m 15 s 49.1%
No or Unknown Signal (): 13 h 31 m 15 s 49.1%
Moderate Signal (): 10 m 41 s 0.6%
Screen dark (): 1 h 31 m 48 s 5.6%
Screen dimmed (): 1 h 59 m 56 s 7.3%
Screen medium (): 4 m 13 s 0.3%
======================================================
Wakelocks (requires root / system app on Android 4.4+)
======================================================
AudioMix (com.android.gallery3d.Gallery): 28 m 15 s Count:1 1.7%
ProximitySensorManager (): 15 m 6 s Count:784 0.9%
*net_scheduler* (Google Play services): 6 m 42 s Count:3940 0.4%
AudioMix (ro.callromania.callRomania): 5 m 32 s Count:11 0.3%
AudioIn (ro.callromania.callRomania): 5 m 32 s Count:10 0.3%
com.csipsimple.ongoingCallLock (ro.callromania.callRomania): 5 m 30 s Count:126 0.3%
com.csipsimple.CallProximity (ro.callromania.callRomania): 5 m 26 s Count:9 0.3%
AudioMix (1013): 5 m 22 s Count:186 0.3%
WeatherUpdateService (com.cyanogenmod.lockclock.cLock): 4 m 20 s Count:27 0.3%
Icing (Google Play services): 3 m 51 s Count:1798 0.2%
GCM_CONN_ALARM (Google Play services): 3 m 47 s Count:161 0.2%
AudioMix (com.google.android.youtube.YouTube): 3 m 7 s Count:3 0.2%
*alarm* (): 2 m 54 s Count:2459 0.2%
AudioMix (com.android.chrome.Chrome): 2 m 52 s Count:182 0.2%
WakeupEventReceiver (com.skype.raider.Skype): 2 m 41 s Count:1 0.2%
ActivityManager-Launch (): 2 m 29 s Count:768 0.2%
NextAlarmTracker (): 2 m 24 s Count:820 0.1%
AudioIn (com.google.android.googlequicksearchbox.Google App): 1 m 50 s Count:41 0.1%
RILJ (Phone): 1 m 9 s Count:5678 0.1%
sendinactive (com.whatsapp.WhatsApp): 1 m 2 s Count:51 0.1%
ConnectivityService (): 57 s Count:773 0.1%
GsmConnection (Phone): 39 s Count:5722 0.0%
SipWakeLock (ro.callromania.callRomania): 38 s Count:280 0.0%
AWakeLock (1013): 33 s Count:7 0.0%
AudioMix (com.facebook.katana.Facebook): 32 s Count:259 0.0%
================
Kernel Wakelocks !!! wakeup_sources !!!
================
PowerManagerService.Display (): 4 h 12 m 53 s Cnt: (c/wc/ec)120/0/0 15.3%
bam_dmux_wakelock (): 2 h 3 m 23 s Cnt: (c/wc/ec)3360/110/0 7.5%
PowerManagerService.WakeLocks (): 1 h 52 m 50 s Cnt: (c/wc/ec)10290/230/0 6.8%
wlan_rx_wake (): 44 m 35 s Cnt: (c/wc/ec)6497/78/6497 2.7%
wlan_wd_wake (): 44 m 34 s Cnt: (c/wc/ec)11015/182/0 2.7%
radio-interface (): 31 m 36 s Cnt: (c/wc/ec)1496/52/0 1.9%
event0-768 (): 11 m 4 s Cnt: (c/wc/ec)2721/2/0 0.7%
event1-768 (): 11 m 3 s Cnt: (c/wc/ec)2723/2/0 0.7%
event4-768 (): 10 m 53 s Cnt: (c/wc/ec)121859/2/0 0.7%
event15-768 (): 10 m 30 s Cnt: (c/wc/ec)3194/179/0 0.6%
event2-768 (): 10 m 28 s Cnt: (c/wc/ec)2964/2/0 0.6%
event3-768 (): 10 m 28 s Cnt: (c/wc/ec)2738/2/0 0.6%
nfc_wake_lock (): 9 m 59 s Cnt: (c/wc/ec)262/0/261 0.6%
wlan_wake (): 6 m 41 s Cnt: (c/wc/ec)247593/277/0 0.4%
alarm (): 4 m 53 s Cnt: (c/wc/ec)4311/824/0 0.3%
smdcntl0 (): 4 m 34 s Cnt: (c/wc/ec)9633/247/0 0.3%
resume_wakelock (): 4 m 17 s Cnt: (c/wc/ec)2715/2/2715 0.3%
alarm_rtc (): 3 m 20 s Cnt: (c/wc/ec)847/177/0 0.2%
ssp_wake_lock (): 2 m 43 s Cnt: (c/wc/ec)1506/9/30 0.2%
PowerManagerService.Broadcasts (): 2 m 16 s Cnt: (c/wc/ec)242/0/0 0.1%
wlan_ctrl_wake (): 2 m 12 s Cnt: (c/wc/ec)622/1/622 0.1%
sec-battery-monitor (): 58 s Cnt: (c/wc/ec)3403/179/0 0.1%
KeyEvents (): 39 s Cnt: (c/wc/ec)126749/379/0 0.0%
Click to expand...
Click to collapse
Upload screen shots of bbs. Don't archive
Here are the BBS screenshots. However, they were taken while the battery was still at 63% - 1 h 34 m Screen ON time.
Again, it's better than before but still worse than other stats I see, especially since this is a new battery and I greenify some things.
Thank you.
Disable nfs using the Disable Service app. If you don't use nfs.
Your issue seems to be bam_dmux wakelock. Just long press any of those stats and they will get copied, then Google them.
Read here for example : forums.androidcentral.com/samsung-galaxy-s3/206481-bam_dmux_wakelock-battery-kill-please-help.html
kenny1991 said:
Disable nfs using the Disable Service app. If you don't use nfs.
Your issue seems to be bam_dmux wakelock. Just long press any of those stats and they will get copied, then Google them.
Read here for example : forums.androidcentral.com/samsung-galaxy-s3/206481-bam_dmux_wakelock-battery-kill-please-help.html
Click to expand...
Click to collapse
bam_dmux_wakelock should be related to your radio signal. I guess you are always on mobile data or you have very poor reception.
Back to kitkat N9005 Tweaked3.95 + LK3.17
Thank you. The bam_dmux_wakelock percentage seem to become bigger and bigger even though I followed your advice and tried to make it somehow less active. I will look into it more in detail.
AlexBlomkvist said:
Thank you. The bam_dmux_wakelock percentage seem to become bigger and bigger even though I followed your advice and tried to make it somehow less active. I will look into it more in detail.
Click to expand...
Click to collapse
You can not "fix" the demux wakelock. It ensures your modem is demodulating data coming through the gsm network.
Charge the phone to 100% and set it to airplane mode. Then observe awake time over SOT.