Related
So we've got a smartphone that's connected to the Internet 7/24 and its IP address usually does not change, thanking to mobile IP.
From my PC, I can ping to my phone and my phone responses, even during the period of standby (dark screen).
What if someone ping my phone continuously? I think the battery will run out in an hour or so.
What we can do about this? You know hacks are probing ports all the time and they sure will find my phone. While they mostly cannot do any hack, but they'll drain out the battery.
Someone would really specifically want to annoy you or do you harm to ping your phone constantly, it is not as easy as it sounds. They would have to specifically want to do it to your phone.
About battery: I am not sure that sending a 1kb ping continuously would drain your battery that much quicker, as you're already connected to the internet and a similar process is already taking place to keep you that way 24/7. Even Direct Push Email will ping your phone once at least every 15 minutes, and Microsoft apparently found that an acceptable process.
We live in a world of hackers. Try watching your smartphone for a while and you'll see the data access is quite often (I have no push mail going on). Note: data activities use lots of power/battery.
ping dont hack the phone
i suspect that changing reception and therefore reinit with the service would be a bigger suspect
There's no risk on ping but if you need security then you can try a mobile firewall called 'ProtectStar Mobile Firewall'
This is not about hacking, it is about port probing that will drain the battery.
There might not be many of us out there, but for those of us using unlocked and rooted mytouch on the ATT network I've found after some research a way to almost double my Edge speed. This information has been posted before in various pieces on various sites but not directly related to ATT/Edge only. Ive tested this on cyanogen 5.0.8 built will include instructions here that you can give this a shot depending on your rom. Prior to this tweak I ran three download tests, 63/38 84/41 81/41. After, I got 191/102, 133/114, 123/95.
Note that it seems that for me the speed increase takes about 10 seconds to kick in from sleep once the data connection is active.
Under the system directory, look for three files. Open each file and find a section called #GPRS class or #RIL settings. When you find the file containing this, this is the file to edit. Below I'm using system.prop. Also, when editing, do not use notepad or wordpad, I personally use EditPad Lite.
using the android sdk, and connecting your phone to pc ->
adb pull /system/build.prop build.prop
open build.prop with a unix compatible text editor
Change the following sections below:
# Default network type.
# 0 => WCDMA preferred.
ro.telephony.default_network=1
# RIL settings
ro.ril.gprsclass=32
ro.ril.hsxpa=0
ro.ril.hep=1
ro.ril.enable.dtm=1
eliminate all other lines that start with ro.ril if they exist.
then go back to your command prompt, and type
adb remount
adb push build.prop /system/build.prop
reboot phone twice after this.
The idea here is that these lines will force only searching for Edge networks, and improve the full use of multislot data/voice thoroughput on ATT Edge network. I would think technically that this would also maximize data thoroughput for those that want to save battery life from the sucking power of 3G.
I'm posting this because I'd like some feedback from ATT people that can try this. As I'm in metro Atlanta I'm not sure that these settings work for every area, and I've only tested in two spots here within a mile of each other in the three tests. I'm also at this point concerned about battery life outside of my one day testing and other areas.
I'll try this on two different G1's running on AT&T this next week and report back. Thanks
Update 8/31/10: Testing with Super D I see a difference. Was 0.07 mbps Down/ 0.08 mbps up. Now 0.18 mbps Down/ 0.16 mbps Up. Every little bit helps I guess. Thanks for posting this thread.
Which ROM are you using this on? I'll try this out on my phone at the end of the week. Also where did you find this exact same set up. I want to read more about it. I see other posts with different values but not with this same exact set up.
http://forum.xda-developers.com/showpost.php?p=5123531&postcount=46
As I mentioned I'm using Cyanogen 5.0.8. I didn't read where anyone is using this exact setup, I researched the values and put them together based on my best understanding of them.
As of now I'm seeing battery life unaffected to actually improved. Things like facebook and my MLB At Bat are majorly improved, takes much less time for the stats to populate so I'm spending less time in the apps and in turn I'm assuming that lends to battery life. I also used to drop a call in one particular spot and I'm not dropping that call so far. I've been in various parts of the city and the download speed is fairly consistent witht he 130-180k range.
Any word on this working with CM6? There only seems to be these in the RIL section:
ro.ril.hsxpa=1
ro.ril.gprsclass=10
Should the other two values be added?
SRDMizzou said:
Any word on this working with CM6? There only seems to be these in the RIL section:
ro.ril.hsxpa=1
ro.ril.gprsclass=10
Should the other two values be added?
Click to expand...
Click to collapse
As far as what should be added/removed, please more carefully read post one.
In answer to whether it works with CM6, these values directly support the gprs code of the phone so it should in theory work on any android based device.
I appreciate the time you've spent, thanks. I'm trying this asap. I have to test before and after, tho. I'll let you know. I never even considered looking into this, and what I see looks very promising. Thanks for the work.
BEFORE
Test 1: ping- i forgot to look
download- 79
upload-109
Test 2: ping-772
download- 90
upload-79
Test 3: break in between 2&3, for fun. it was asleep for a while.
ping- 767
download-51
upload-95
Test 4, another pretty long break
ping:927
download:23
upload:116
Test 5, no break
ping 16
download 44
upload 100
test 6, no break
ping 39
download 46
upload 111
AFTER
Same physical location, 2 reboots, cable unplugged as before.
Test 1: ping 551
download 33
upload 122
test 2 soon after
ping 541
download 27
upload 104
test 3 with an asleep break in between for a while
ping 428
download 47
upload 105
test 4 right after
ping 429
download 39
upload 102
Test 5 right after
ping 422
download 28
upload 116
Test 6, after a break with screen off/sleeping and a 30 second break with screen on before test
ping 430
download 26
upload 105
In conclusion, no it didn't make any benefit to me. In fact, there was a decrease in speed after applying the mods.
I used a nightly of cyanogenmod 6 from 2 days ago (right before rc3)
I will try donut soon. Eclair sucks. Note that cyanogenmod did not have the last two ro.ril lines, but it did have the telephony one. I added the necessary ones, of course.
i updated my post above.
Hi Jcarrz, thanks for the post. I think something is wrong with your location/configuration if you are getting 100% upload speed over download. It should be the reverse, but even before my config change I was getting double your download speed. Also, a ping time of <100 ms into an edge network is a bit unheard of as far as I know, what speedtest are you using? Did you delete the existing lines? the two most important lines to add are the dtm=1 lines and the grprsclass=32.
One thing about this is that not every city may support class 32 download. Also it may take some time for GPRS to establish 5 timeslots to get the full download speed. Another thing to follow up on my post, as I mentioned 10 seconds or so at least before starting the speedtest, but I've found that even 1-2 minutes after coming from sleep I'm occasionally getting 215k down in some places. But in your case there's definately something else going on....
hongkongpheoy74 said:
Hi Jcarrz, thanks for the post. I think something is wrong with your location/configuration if you are getting 100% upload speed over download. It should be the reverse, but even before my config change I was getting double your download speed. Also, a ping time of <100 ms into an edge network is a bit unheard of as far as I know, what speedtest are you using? Did you delete the existing lines? the two most important lines to add are the dtm=1 lines and the grprsclass=32.
One thing about this is that not every city may support class 32 download. Also it may take some time for GPRS to establish 5 timeslots to get the full download speed. Another thing to follow up on my post, as I mentioned 10 seconds or so at least before starting the speedtest, but I've found that even 1-2 minutes after coming from sleep I'm occasionally getting 215k down in some places. But in your case there's definately something else going on....
Click to expand...
Click to collapse
yea, that ping was pretty crazy. I live really close to los angeles, I don't think a crappy network is the problem. What do you mean by delete existing? i edited two that were there, and added two that weren't. I am using the ookla labs speedtest.net application. I have always had a higher upload than download. Everywhere. I waited for long periods of time between tests. And after waking up from sleep. The highest speed test I have seen is a 250, on htcclay's superfast 1.3.3. I'll have to take a look on the values in that rom.
Thanks for your help, prehaps you could upload the EXACT build.prop for, say, a cm6 build that I could use?
Jcarrz1
ro.ril.hsxpa=2
ro.ril.gprsclass=12
ro.telephony.default_network = 0
I seem to get the best speeds i've seen with this config. Namely the hsxpa=2, because that one, when changed to 1 or 0, dents my speeds.
jcarrz1 said:
ro.ril.hsxpa=2
ro.ril.gprsclass=12
ro.telephony.default_network = 0
I seem to get the best speeds i've seen with this config. Namely the hsxpa=2, because that one, when changed to 1 or 0, dents my speeds.
Click to expand...
Click to collapse
Thanks for reporting back. I think this shows that indeed the edge network in your location just isn't a class 32, or at least it is and is allocating more timelosts for upload than download. Here's how the classes should in theory work. Edge can alot 2-6 timeslots to transfer data. a class 10 or 12 is 5 slots data, 10 says that in theory up to 4 of those slots could be download and 2 could be upload, while 12 is up to 4 down 4 up (but only 5 max in any config). A class 32 can allocate 6 slots data, 32 also says that 5 could be download or 5 could be upload. Try setting the class at 30. This will give you a shot at 6 slots guarantee that no more than one timeslot can be set for upload (5 download 1 upload). If that doesn't work, in theory actually then moving to a class 10 setting may overall benefit you (4 download 2 upload).
hsxpa setting should technically do nothing for you on AT&T unless your phone supports HSPDA 850/1900, I set it on my magic 32B because it forces UTMS99 which is not implemented and therefore should in theory guarantee my radio never finds something to scan. I understand that turning on 2G only doesn't work in all roms, so I set that just in case.
Just so you know, the values in gprsclass can be 10,12,30,31,32,33,34.
I don´t think that ro.ril.hsxpa=0 deactivates 3G. AFAIK it just limits the phone to plain normal 3G (=UMTS) and ensures that it does not attempt to switch to 3.5G (HSDPA/HSUPA) connections.
From what I see in wikipedia, UMTS99 is nothing else than the first release of UMTS, therefore definately being supported.
Better set it to =2, just in case you travel to a country where you have 3G (and 3.5G, etc.) connectivity.
Hellek said:
I don´t think that ro.ril.hsxpa=0 deactivates 3G. AFAIK it just limits the phone to plain normal 3G (=UMTS) and ensures that it does not attempt to switch to 3.5G (HSDPA/HSUPA) connections.
From what I see in wikipedia, UMTS99 is nothing else than the first release of UMTS, therefore definately being supported.
Better set it to =2, just in case you travel to a country where you have 3G (and 3.5G, etc.) connectivity.
Click to expand...
Click to collapse
EDIT: Sorry I just looked up the specs on the phones again and I never noticed UMTS support, still in essense you still want to keep this at hsxpa=0, unless you want 3G on roaming coverage as mentioned. This article is about ATT users and more geared to only ATT bands, ATT does not offer HSDPA over the bands this phone supports so disabling it should keep it from scanning roaming networks for it. I'm removing the other ril values from the phone to keep the phone happy with the fastest edge connection it can get.
So I just tried updating the settings on Superfly TCBY Froyo 1.2. It didn't have the same exact setting lines so I just added the lines manually. All tests done on a fresh reboot, SpeedTest the only app open:
Before
Time of day: 1:10 PM
Run 1
Server: Los Angeles, CA
Latency: 829 ms
Download: 10.3 kB/s
Upload: 9.3 kB/s
Run 2
Server: Los Angeles, CA
Latency: 121 ms
Download: 14.7 kB/s
Upload: 12.1 kB/s
After (2 reboots):
Time: 1:25 PM
Run 1
Server: Los Angeles, CA
Latency: 423 ms
Download: 19.9 kB/s
Upload: 13.7 kB/s
Run 2
Server: Los Angeles, CA
Latency: 394 ms
Download: 18.3 kB/s
Upload: 14.6 kB/s
So it did improve speeds a little. How much is due to the settings is unsure. It could be related to the time of day and traffic during the time of day. I will keep the settings and see how they hold up.
I have been using the normal settings without modifications for Google Nav and it works perfectly fine. I will see how these settings hold. I'll attach my build.prop. Just remove the ".txt"
dawgpound, can you report what city you are in. I do agree that time of day and tower can play into this, this is why my before and after tests were done about 2-3 miles apart from each other. They were also done during daytime hours.
To update on my end, I'm still testing in various areas of atlanta and I'm finding that I actually connect "G" in some areas. I'm assuming UMTS99 since the phone only supports this. The download speeds were terrible, worse than edge for me though. I know this implementation is older and probably not omptimized.
Using Speedtest I'm still not getting any worse than 40k download anywhere in metro atlanta. But, one thing I've found is that in some cases I would get a upload speed greater than download, running Speedtest again even immediately after would produce much higher downlad and upload speeds and maintain these. I think this goes back to my theory that when you initiate the data transfer that it takes a while for the phone to build all the timeslots to the carrier when you enable them in some situations.
Sorry for responding so late. I'm doing the tests in LA. I went to Universal Studios the other day with the modified settings and my phone failed badly when using data. I was getting full signal on my phone with the EDGE sign but it wasn't sending or receiving data most of the day.
Unfortunately, I wasn't able to switch back and forth to see if it was just in the theme park or not. I've noticed in crowded areas, it lags pretty bad compared to the stock settings. I also was connecting to G speeds in some areas but only for a few seconds before switching back to EDGE. Right now, I'm back on stock settings to compare. I will say though, with the modified settings, download speeds increased by average 5 kB/s but upload speed was on avg 5 kB/s less than dl speeds. Stock settings, both download and upload speeds are close to each other.
High Level Symptoms:
- I notice battery has drained very quickly in a short time even when I have not been using phone (i.e. idle with display off)
- Phone feels noticeably warm/hot even when I have not been using phone (e.g. like it does while charging)
- Issue only seems to happen when running in 4G LTE mode
- I have gathered detailed usage statistics and do not believe there are any miss-behaving apps or system processes responsible
- I have noticed issue start most often near my office (in midtown NYC)
Note: This is where I use the phone on battery the most, so it may just be sampling bias
- I can temporarily stop the rapid power burn by switching out of 4G LTE mode (i.e. to 3G mode, or disabling radio)
- I have not found a way to stop the issue in 4G LTE mode once it starts except by restarting phone
(things I tried without success: toggling airplane mode, switching to 3G and back to 4G, radio off/on, and moving to different location/tower; rapid burn starts back up again as soon as 4G LTE mode is re-enabled)
Power Burn Rate:
- Data captured using Battery Monitor Widget which I have set to sample/log battery available % and usage every minute (this is a great app!)
- Available % dropping at a rate of about 20% / hour while phone is idle w/ screen off (my normal is about 5% / hour)
- Usage shows a very flat baseline of about 1000 mW / 250 mA (normal baseline is more like 100 mW / 40 mA)
(by baseline I mean many samples are equal to that baseline value with the rest being spikes up to greater values; no observed values are less than the baseline)
Background Info:
- My phone is unrooted and running stock firmware w/ the Verizon OTA upgrade (installed ~2011-05-19)
- I have noticed this issue many times since first getting the phone (~2011-04-12), and this issue is still present even with the newest LTE radio FW in the OTA update
- I am new to Android (~2 months in) but I am diving in deep with all the amazing tools both built-in and via add-on apps; I have collected a range of data/observations from numerous sources that are detailed in this post
My hypothesis is that the LTE radio hardware is responsible for this power burn. Most likely due to a software/firmware bug, but I'm not sure how to confirm that.
I wonder how common this issue is. I remember reading other posts on the forum that sound like the same thing. For example: http://forum.xda-developers.com/showthread.php?t=1008761
Can anyone else confirm they have seen this issue? If this issue is wide spread, I think it may be a contributing factor to the wide spread reports of 4G LTE a lot of battery.
I do not think this is the only factor that causes 4G LTE to use more power than 3G. I have read the reports, and personaly seen, higher 4G LTE power consumption when in low signal areas. However, I belive that to be independant from the burn issue I am describing here. The worst case power consumption I've seen that I think was "low LTE signal" related was only about 500 mW / 130 mA. The burn issue I'm refering too consumes power at about twice that rate and happened when I had strong signal. I had three to four of four possible bars. Also, I grabbed more detailed information:
----------
Phone info
reached using "LTE OnOff" app, "Network" app, or by dialing *#*#4636#*#* -> Phone information
Signal strength: -67 dBm to -80 dBm, 3 to 4 asu
Location: BID = 39b SID = 16 NID = 4
LAT = 7fffffff LONG = 7fffffff
Network Type: CDMA + LTE/EvDo auto
I believe this is good signal (e.g. issue not due to a low signal condition)
==================
Usage Data Capture
I briefly connected to power to reset the statistics after noticing the issue had started and and captured about an hours worth of data. My understanding of the data is that the display was off for almost all the time, and no apps or system processes are listed as using any significant amount of CPU/sensors in comparison to the hour data collection window.
-----------
Battery Use
reached using Settings -> About Phone -> Battery Use, or Battery Monitor Widget -> Usage
When last unplugged for 57m 12s
Display 30%
* Time on 1m 11s
* Auto Brightness
Cell Standby 21%
* Time on 57m 12s
Phone idle 19%
* Time on 56m 1s
Foursquare 11%
* CPU total 8s
* CPU foreground 6s
* GPS 26s
* Data sent 13.59 KB
* Data received 379.93 KB
Android System 7%
* CPU total 41s
* CPU foreground 2s
* Data sent 12.09 KB
* Data received 20.27 KB
Android OS 6%
* CPU total 39s
* Data sent 20.11 KB
* Data received 136.25 KB
Pandora 6%
* CPU total 35s
* Data sent 1.83 KB
* Data received 27.16 KB
---------------
Battery History
reached using Battery Monitor Widget -> Statistics, or by dialing *#*#4636#*#* -> Battery history
since last unplugged
CPU usage
* Android System (Total time:39s)
* Pandora (Total time:35s)
* suspend (Total time:31s)
* Foursquare (Total time:7s)
... (Note: more apps listed but with smaller total times)
Sensor usage
* Android System 29m 47s
* AccuWeather.com 28m 36s
(Note: after this capture I uninstalled AccuWeather.com app and retested. It wasn't listed anymore, but power drain behavior was unaltered)
Partial wake usage
* K-9 Mail 7m14s
* Android System 5m 4s
* Seesmic 9s
... (Note: more apps listed but with smaller times)
Other Usage
* Running (27.6%)
* Screen on (2.1%)
-------------------
CPU Spy v0.3.0 beta
Note: timers reset at begining of measurement interval
Time in state
1024 MHz 4:21 7%
768 MHz 0:54 1%
368 MHz 0:35 0%
245 MHz 12:11 20%
Deep Sleep 41:34 69%
This is a typical distribution I see when the phone is mostly idle (CPU sleeping for most of the time).
=================
Variation testing
After the data capture I systematicly tried several methods to see what it took to stop the abnormal drain in 4G LTE mode. In the end only rebooting the phone did it.
Set preferred network type: "CDMA auto (PRL)" (i.e. 3G mode) -> normal power usage (5:00pm-5:18pm)
Set preferred network type: "CDMA + LTE/EvDo auto" (i.e. 4G mode) -> abnormally high power usage (5:18pm to 5:43pm)
Set airplane mode (i.e. radio off) -> very low power usage (5:43pm to 6:54pm)
Turned off airplane mode (i.e. 4G mode) -> abnormally high power usage
Set preferred network type: "LTE mode" (i.e. ONLY 4G mode) -> abnormally high power usage
Set preferred network type: "CDMA + LTE/EvDo auto" (i.e. 4G mode) -> abnormally high power usage
Moved to a new place:
Signal strength: -65 dBm 4 asu
Location: BID = 23c SID = 16 NID = 4
LAT = 7fffffff LONG = 7fffffff
-> abnormally high power usage
Phone info "Turn off radio" button -> very low power usage
Phone info "Turn on radio" button -> abnormally high power usage
Restart phone -> normal power usage
I experience the same problem. My guess is that the radio firmware gets into a bad state when you are in an area with bad coverage.
I have been in a state where disabling data didn't stp the battery drain, only entering airplane mode would stop it.
crpalmer said:
I experience the same problem. My guess is that the radio firmware gets into a bad state when you are in an area with bad coverage.
I have been in a state where disabling data didn't stp the battery drain, only
entering airplane mode would stop it.
Click to expand...
Click to collapse
I originally thought the same thing about the issue starting while in poor coverage, but since I have seen it occur multiple times in a good coverage area I began to doubt that was the case. The extra power consumption I usually get while in poor coverage is less in magnitude, and varies much more, and goes away when I have good coverage again. This issue feels distinctly different to me.
When you say disabling data didn't stop the drain you experienced, do you mean turning off Settings -> Wireless & networks -> Mobile networks? I haven't tried playing with that option. I'll give it a try next time I see the issue too.
You said entering airplane mode would stop it. Did you have the same experience that when you turned airplane mode off that the drain started back up again until you restarted?
Thanks
Excellent post, I would venture a guess that your background is in one the sciences.
One thing I noticed you didn't try was connecting through wifi. I believe this will render the 4g radio on but not in use. If the issue persists, it could help narrow down the cause.
As far as attempting to fix it, you can factory reset it or go to verizon for a replacement.. but that doesn't do much for others with this problem.
I have been having the same issue, both on stock and BAMF 1.6. Thanks for looking so thoroughly at this problem. It appears not everyone is affected. Can someone confirm? If so, exchanging the could be the solution.
Sent from my ADR6400L using XDA App
To test your hypothesis, I'd recommend turning off LTE somehow. My suggestion for non-rooted phone:
Dial ##778#
Chose edit mode, password: 000000
You should be able to turn off LTE in Modem Settings->Preferred Mode
Please let us know your finding.
Nice work on the research!
The scenario you described happened to me yesterday.
I was in a building where I didn't get any reception at all. I noticed the phone started to warm up. By the time I got outside and the phone re-established a connection with the 4g network, it was extremely warm and the phone was at 7% life begging to be charged.
This has happened to me on two other occasions but I don't recall being in an area of zero to poor reception.
My bolt is also rooted running the BAMF Remix 1.6.
agdaniels said:
Excellent post, I would venture a guess that your background is in one the sciences.
One thing I noticed you didn't try was connecting through wifi. I believe this will render the 4g radio on but not in use. If the issue persists, it could help narrow down the cause.
As far as attempting to fix it, you can factory reset it or go to verizon for a replacement.. but that doesn't do much for others with this problem.
Click to expand...
Click to collapse
Thank you. Your guess is spot on; I did my Ph. D. in computer science.
I have not tried switching to WiFi. Next time I see the issue I will put that to the test. I find I haven't been using WiFi much with this phone since I have lower standby power consumption in 3G mode when I don't need the speed. When I do want more speed, I find here in NYC 4G LTE is actually significantly faster than either my home or work Internet connection (Cable and DSL respectively) (Crazy!). Also, here in NYC the 2.4 GHz band is VERY crowded so WiFi can slow down at times even on a good wired Internet connection. I wish this phone was 5 GHz WiFi capable to help avoid this particular issue.
My intuition is that this is a radio firmware issue so I have my doubts that a factory reset or even a replacement would fix anything. Factory reset would help if there were misbehaving apps or screwed up settings on my phone, but this seems unlikely. I'll probably need to root my phone so I can back it up before I try a factory reset. A replacement would only help if there was a hardware fault. Part of the purpose of this thread is to help gauge if many other people have this problem. The more that do, the less likely it is an abnormal HW fault with only my phone, and more likely a bug or other HW errata issue that hasn't been worked around correctly.
I think it is still too early in the game to make the call that it is not fixable in FW. I was aware that this LTE network/chipset is quite new and this phone was likely to have some rough spots at the start. Verizon/HTC/Qualcomm have only made one OTA release so far, and even that release has major bugs that were not present in the original stock FW (e.g. the frequent spontaneous rebooting when in 3G mode). Forums like this seem like great places for us users to publicly characterize issues we encounter. I hope it helps the engineers involved in making fixes and that we get updates not too far down the line.
cuguy said:
To test your hypothesis, I'd recommend turning off LTE somehow. My suggestion for non-rooted phone:
Dial ##778#
Chose edit mode, password: 000000
You should be able to turn off LTE in Modem Settings->Preferred Mode
Please let us know your finding.
Click to expand...
Click to collapse
Thanks for the suggestion.
If you look at the last part of my post under the "Variation Testing" heading, I believe I did try a number of configurations with LTE off. Each case where LTE was off I saw normal or low power consumption. This is why I grew to suspect the LTE radio in the first place.
The technique I used for switching between 3G and 4G modes was actually the "Set prefered network type" drop down on the "Phone info" menu that can be reached using "LTE OnOff" app, "Network" app, or by dialing *#*#4636#*#* and selecting "Phone Information".
I have used the dial ##778# to get the ESPT menu before, but that was to modify the "Rev. A" setting from "eHRPD" to "Enable" as a work around to re-enable 3G EVDO during the few days of nation wide 4G LTE & 3G SVDO outage we had a month or so ago. BTW, it looks like I had by phone set to the non-stock "Enable" setting rather than "eHRPD" for the original data capture. I switched this back to "eHRPD" and I'll report if I have the issue again. I was last playing with this setting to see if had any effect on the random reboots after the OTA while on 3G, but it did not.
In the ESPT -> Modem Settings -> Preferred Mode drop down I only see the options for:
- Automatic
- HDR Only
- Digital Only
- CDMA Only (selected by default)
- CDMA HDR Only
There is also a a Preferred Mode(9k) drop down that has these options:
- Automatic
- HDR Only
- LTE Only
- HDR LTE only (selected by default)
I believe that these are settings for the voice radio and the data radio respectively. See the third page of the excellent Anandtech review of the HTC Thunderbolt: <Sorry, I am a new xda-developers forum member so it won't let me post external links yet.>
Do you have suggestions on how to set these? I am unfamiliar with the HDR acronym and haven't turned up anything that seems relevant in my Google searches.
I had another instance of the 4G LTE power burn issue today. I tried a few of the above suggestions.
I enabled WiFi and logged on to an access point. This did not stop the abnormally high power burn. Instead it went up slightly; I assume this was the extra power for the WiFi radio.
I also tried turning off Settings -> Wireless & networks -> Mobile networks. That resulted in the 4G LTE icon going away but the signal bars were still showing. I couldn't use the Internet but a SMS came through in this mode. This mode did not stop the power burn either.
The burn stopped only when I rebooted.
The reboot happened when I dialed ##778# to get the ESPT menu and switched the "Rev. A" setting from "Enable" to "eHRPD" and this time remembered to commit the changes (forgot to when I posted above). Committing the changes auto-rebooted the phone, which returned me to normal power consumption. I will report if I have the problem again now that I have confirmed I am back in the stock eHRPD mode.
Most of today I was in very good signal conditions, judging by the time the drain started, I could have been out on a errand in the neighborhood. So I can't 100% guarantee that the 4G signal was high the whole time.
Does anyone know of an app that works on the Thunderbolt that can log signal strength over time and preferably graph it too (e.g. similar to Battery Monitor Widget). I have tried to download and use a few without success including: Open Signal Maps, Network Signal Info, RF Signal Tracker, and Signal Finder. Some of these apps didn't work at all (I suspect 4G signal is reported a bit differently and this confuses some of them). Some work in general but I can't seem to get the logging I'm looking for.
Thanks!
OdinGuru said:
I originally thought the same thing about the issue starting while in poor coverage, but since I have seen it occur multiple times in a good coverage area I began to doubt that was the case. The extra power consumption I usually get while in poor coverage is less in magnitude, and varies much more, and goes away when I have good coverage again. This issue feels distinctly different to me.
When you say disabling data didn't stop the drain you experienced, do you mean turning off Settings -> Wireless & networks -> Mobile networks? I haven't tried playing with that option. I'll give it a try next time I see the issue too.
You said entering airplane mode would stop it. Did you have the same experience that when you turned airplane mode off that the drain started back up again until you restarted?
Thanks
Click to expand...
Click to collapse
By disabling data, I was actually using the notification tools in most rooted roms. That should be equivalent to what you said.
Toggling airplane mode toggled the battery drain problem until it failed to enter airplane mode and I had to reboot.
I see the same thing
Where I live at home we only have 3G at work I have 4G. The phone will get itself into some kind of mode at work and burn through the battery in 4-5 hours. So I keep it charging on my desk all day. If I didn't, some days it wouldn't make it till lunch.
OdinGuru said:
Thank you. Your guess is spot on; I did my Ph. D. in computer science.
I have not tried switching to WiFi. Next time I see the issue I will put that to the test. I find I haven't been using WiFi much with this phone since I have lower standby power consumption in 3G mode when I don't need the speed. When I do want more speed, I find here in NYC 4G LTE is actually significantly faster than either my home or work Internet connection (Cable and DSL respectively) (Crazy!). Also, here in NYC the 2.4 GHz band is VERY crowded so WiFi can slow down at times even on a good wired Internet connection. I wish this phone was 5 GHz WiFi capable to help avoid this particular issue.
My intuition is that this is a radio firmware issue so I have my doubts that a factory reset or even a replacement would fix anything. Factory reset would help if there were misbehaving apps or screwed up settings on my phone, but this seems unlikely. I'll probably need to root my phone so I can back it up before I try a factory reset. A replacement would only help if there was a hardware fault. Part of the purpose of this thread is to help gauge if many other people have this problem. The more that do, the less likely it is an abnormal HW fault with only my phone, and more likely a bug or other HW errata issue that hasn't been worked around correctly.
I think it is still too early in the game to make the call that it is not fixable in FW. I was aware that this LTE network/chipset is quite new and this phone was likely to have some rough spots at the start. Verizon/HTC/Qualcomm have only made one OTA release so far, and even that release has major bugs that were not present in the original stock FW (e.g. the frequent spontaneous rebooting when in 3G mode). Forums like this seem like great places for us users to publicly characterize issues we encounter. I hope it helps the engineers involved in making fixes and that we get updates not too far down the line.
Click to expand...
Click to collapse
You are absolutely correct on all three points, my main focus with the two suggestions were background data for the factory reset and faulty hardware for the replacement.
If you have the ability to disable all background data syncing while on 4g- on the application side, sense ui side, and the android side you could completely rule out software being the cause. My thoughts with this are some background service is keeping the radio active, causing the burn.
The replacement device would help to narrow down whether the issue lies on the device side, or if its more related to the towers/the way lte functions. The latter is bad news for you. My thoughts on this are that some people report no issues running lte, while others are having similar problems as you have reported; I doubt that it is faulty phone hardware, but its possible.
I share your conclusion that this is a firmware(baseband) issue. Actually going in and manipulating it would require root, a considerable understanding of how the interaction between hardware and software works, and the abilty to make tweaks and test them. I will also contact some people more knowledgable then myself and see if they want to chime in on the matter.
crpalmer said:
By disabling data, I was actually using the notification tools in most rooted roms. That should be equivalent to what you said.
Toggling airplane mode toggled the battery drain problem until it failed to enter airplane mode and I had to reboot.
Click to expand...
Click to collapse
Excellent idea. I then I was able to execute the test you suggested yesterday when I re-encountered the issue. I saw the exact same behavior you reported: even though I disable applications data over LTE, the drain did not stop. This is strong supporting evidence that it is not an issue with some kind of rouge app / sync settings.
Drain toggling with airplane mode is the exactly consistent with my observations as well. Sounds like we have confirmed you having the exact same burn issue.
Thank you for the feedback and confirmation.
mcargil05 said:
Where I live at home we only have 3G at work I have 4G. The phone will get itself into some kind of mode at work and burn through the battery in 4-5 hours. So I keep it charging on my desk all day. If I didn't, some days it wouldn't make it till lunch.
Click to expand...
Click to collapse
This is consistent with my observations of the burn issue. The baseline power consumption I observed is about 20% of the battery per hour while phone is idle with screen off. That would correspond to the phone burning through a full charge in 5 hours even if you didn't use it at all. Add any extra actual usage on top of that and 4-5 hours of life sounds very plausible. That assumes you have the problem right away though (the worst case).
I typically see a variable amount of time of normal consumption before the issue starts. For instance, let's say I've been running normally for 3 hours and am at 80% before the issue starts. Then I'd quickly burn through the last 80% in 4 hours or less. In that case I'd get less than 7 hours of total battery life (e.g. not making it through the day). If my normal usage had continued, it should be more like 15 hours (e.g. more than enough for a long day and needs charging every night).
There is still the question if this issue is related or not to 4G signal levels. What do you normally see in the office? Number of bars is useful, and also the more detailed dBm number can be found in Settings -> About Phone -> Network.
Thank you for your report.
agdaniels said:
You are absolutely correct on all three points, my main focus with the two suggestions were background data for the factory reset and faulty hardware for the replacement.
If you have the ability to disable all background data syncing while on 4g- on the application side, sense ui side, and the android side you could completely rule out software being the cause. My thoughts with this are some background service is keeping the radio active, causing the burn.
The replacement device would help to narrow down whether the issue lies on the device side, or if its more related to the towers/the way lte functions. The latter is bad news for you. My thoughts on this are that some people report no issues running lte, while others are having similar problems as you have reported; I doubt that it is faulty phone hardware, but its possible.
I share your conclusion that this is a firmware(baseband) issue. Actually going in and manipulating it would require root, a considerable understanding of how the interaction between hardware and software works, and the abilty to make tweaks and test them. I will also contact some people more knowledgable then myself and see if they want to chime in on the matter.
Click to expand...
Click to collapse
In the most recent test I disabled "Mobile Networks" which effectively shutdown data service. I also tested switching to WiFi which should have redirected all data away from the 4G LTE radio. Neither one of these stopped the power burn. Do you agree this is sufficient enough to rule out apps/services?
I noticed on the Phone info screen there are some counters for number of bytes sent over the radio. Next time I have the issue perhaps I'll keep track of how those change when I'm having the issue vs not.
I agree that trying replacement HW would be a useful data point to help identify if the issue is inherent or tower related. I'm not quite ready to jump through all the hoops with Verizon to do it myself yet. I'd want to root first to create a backup of my current setup first to reduce the pain of the procedure. And I'll probably give them the benefit of the doubt and wait for the next OTA to give them another shot at fixing the issue with FW.
Part of our questions would be answered if there was indeed a user out there that runs 4G LTE and can document that they do not have this issue. Does anyone out there run Battery Monitor Widget or similar and can say they have never seen the tell-tail pattern of power burn I am talking about?
I really wish Android had a built in screen capture feature. I need to get adb installed and setup on my computer so I can post examples of what the graphs look like; I think that would help other users to identify the issue as it happens so they know when to re-boot to save what is left of their battery.
I agree there is very little we as users can do to fix the issue if it is in the radio FW. As you say, it would indeed take very detailed knowledge of the HW. Also, I think it would be impossible without the radio FW source code. Although I haven't looked through the HTC released code, I would be very surprised if this was included. It wouldn't be covered under the Android or Linux open source licenses as it likely originally came from Qualcomm and is considered proprietary. Without that, we can only hope that Qualcomm/HTC/Verizon work together to get it figured out. The good news is that they all have a good business case to do so. This LTE chipset is likely to be used in several phones so they need these issues resolved before it affects their whole lineup.
Anyone know if the new Samsung Droid Charge has this issue too?
After experiencing all the same issues myself, I have noticed that this seems to have been addressed in the leaked Gingerbread radio. Might be worthwhile to repeat testing using that radio and then somehow compare code.
Sent from my ADR6400L using XDA Premium App
I would have to agree you've sufficiently ruled out software, the point about the gingerbread build not having issues is worth noting though. Can someone confirm the 2.3 release has new radio firmware? It wouldn't be difficult at all to pull it out and flash it if it does
My thunderbolt will be in hand Monday, I don't have the phd you have in c.s (mines just a bs) but I've been in the business long enough to throw some graphs together. We'll compare notes then if we don't find resolution sooner.
I experience the same problem in North Phoenix when running 4GLTE in a weak 4g signal area. It doesn't happen too often if I'm in a heavily blanketed 4g area.
EDIT. I'm running rooted. OC to usually 1400 mhz. I'm constantly being synced with the Exchange Server. My phone gets super hot when running navigation plus 4GLTE. Temperature gets up to around 110 degrees Fahrenheit.
When I notice my phone heating up, I'll switch to CDMA prl and immediately my battery temperature starts dropping to normal levels, ie. 86 degrees Fahrenheit.
At the time I was running on different radio combinations. Such as, CDMA. 6 and lte. 7 radio combo. I have recently switched to Gingerbread so more testing is needed.
Had a spare minute to look up the radio, looks like its bricking certain devices after flashing. Not completely ruling it out, maybe you can flash it, test it, then flash it back, but there is some risk involved.
Whatever the case, its reassuring to know updates are coming eventually.
Here is a link for reference:
http://forum.xda-developers.com/showthread.php?t=1098363&page=70
I performed a cursory search and was not able to find much on this board, but feel free to point me in the right direction if I missed something.
I have always wondered why the MTU is set to 1428 in System>>Build.prop file. Knowing that my desktop computer does just fine using an MTU setting of 1500, I decided to test the impact that setting the MTU to 1500 would have on 4G LTE and Wifi speeds.
The results were surprising, but may not be repeatable for those who wish to try this. I live in Southeast Houston, which may help some of you to decide whether or not to try this. I accept no responsibility for damage to your phone, business, life or anything else if you do.
MTU 1428 (90+ Days)
4G LTE: Average 7-13 Mbps Down, Record 18 Mbps
Wifi 802.11n (Asus RT-N56U): Average 10-20 Mbps Down, Record 27 Mbps
MTU 1500 (24 Hours, Limited Data)
4G LTE: Consistent 17 Mbps Down
Wifi 802.11n (Asus RT-N56U): Consistent 13 Mbps Down
I realized a 5+ Mbps boost on 4G LTE Download speeds (Results will vary)
Standard Caution - back up your phone in case something goes wrong
Step #1 - Use Root Explorer or equivalent to create a copy of System>>Build.prop and place copy on SD Card (I use the Download folder)
Step #2 - Open the copy of the Build.prop you created and locate the default MTU entry, which should be 1428, change this entry to either 1492 (DSL) or 1500 (Cable) and save the change
Step #3 - Use edited copy of the Build.prop file to overwrite the one in System>>Build.prop
Step #4 - Reboot your phone and test your 3G/4G and Wifi speeds for improvement/degredation and repeat steps above to find optimal setting (Max=1500)
My buddy works at the Columbus Vzw building and is a 4G engineer. When I spoke to him last week he JUST mentioned the MTU as well and said its going to be changed with an OTA radio update. He said theyre always working on radio updates but whether or not they are all released is another question ha.
biglipps66 said:
My buddy works at the Columbus Vzw building and is a 4G engineer. When I spoke to him last week he JUST mentioned the MTU as well and said its going to be changed with an OTA radio update. He said theyre always working on radio updates but whether or not they are all released is another question ha.
Click to expand...
Click to collapse
I forgot to mention that my 4G LTE upload speed average increased and became consistent as well. I am now seeing 8 Mbps Upload in a location that had averaged 3-5 Mbps before I changed the MTU to 1500. My Wifi is limited to 2-3 Mbps Upload, so I am not sure how my Upload speed would be on a connection with more bandwidth.
I've been running 1492 since you posted it and giving it a try out. Doesn't seem to help the tether speed, but helps the phones speed of loading pages in the browser, tapatalk to servers, and loading news much quicker.
savagebunny said:
I've been running 1492 since you posted it and giving it a try out. Doesn't seem to help the tether speed, but helps the phones speed of loading pages in the browser, tapatalk to servers, and loading news much quicker.
Click to expand...
Click to collapse
Glad to hear! I have used this tweak for years on Windows computers, so it makes sense that it should work on our phones as well. My only concern was data fragmentation, but that does not seem to be an issue for me. Mileage will vary though, so improvements are not guaranteed for all.
Been using stock since day one, today just broke 60mbps here in NYC:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Been seeing 40's and 50's on a daily basis. Never changed the MTU.
Maybe once I root the device I'll mess with it.
Yep, web browser seem to load qicker than usual, tether is no changed, speed test many times ;/ buddy, how u config that on your window pc anyway?
Sent from my ADR6400L using Tapatalk
davidkim99b said:
Yep, web browser seem to load qicker than usual, tether is no changed, speed test many times ;/ buddy, how u config that on your window pc anyway?
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
The easiest way to do this on a Windows computer is to visit Speedguide.net and run the TCP/IP Analyzer utility (Link on Bottom-Left of site's main page), then, if needed, download the TCP/IP Optimizer. This utility is a portable app, so there is nothing to install. Just remember that a reboot is needed for changes to take effect.
Here is the manual method for setting MTU on a Windows computer:
1. Open a command line window as an Administrator (ie. Right-Click on All Programs > Accessories > Command Prompt and select Run as administrator)
2. Type the command 'netsh' and wait for prompt
3. Type the command 'interface' and wait for prompt
4. Type the command 'ipv4' and wait for prompt
5. Type the command 'set subinterface "Local Area Connection" mtu=xxxx store=persistent'
6. Reboot
Hope this helps. I know a lot of Windows tweaks, including many Registry settings that are not well known. Perhaps I will put together a self-help document if there is any interest.
Here is a good starting point: http://www.speedguide.net/articles/windows-7-vista-2008-tweaks-2574 (Mods, please remove this link if it violates the TOS here)
milan03 said:
Been using stock since day one, today just broke 60mbps here in NYC:
Been seeing 40's and 50's on a daily basis. Never changed the MTU.
Maybe once I root the device I'll mess with it.
Click to expand...
Click to collapse
Using the newly leaked 906 radios, my download speed jumped from 17 to 40 Mbps yesterday on 4G LTE! Upload & Wi-Fi Speeds remained unchanged for the most part.
I didn't believe it at first, so I reset the MTU to 1428, rebooted my phone and my Download speed returned to the 13-20 Mbps range. Changed the MTU back to 1500, rebooted and jumped right back to 40 Mbps.
I encourage others to try changing the MTU setting to 1500 (For those using Cable) or 1492 (For those using DSL)
stupid question here, but would this increase speeds while in a 3g area or the mtu specifically for 4g data rates?
vdChild said:
stupid question here, but would this increase speeds while in a 3g area or the mtu specifically for 4g data rates?
Click to expand...
Click to collapse
MTU is not specifically tied to either 3G or 4G. In fact, this setting is used on Windows based computers all the way back to the early versions of Windows. MTU is used to optimize the connection between the host and client. If MTU is set too low, bandwidth is reduced because more packets of data are managed. If MTU is set too high, fragmentation will occur and there will usually be a need for more re-transmissions of data. As a rule, 1500 is the Maximum MTU setting for cable based internet, while 1492 is the maximum for DSL.
"A larger MTU brings greater efficiency because each packet carries more user data while protocol overheads, such as headers or underlying per-packet delays, remain fixed; the resulting higher efficiency means a slight improvement in bulk protocol throughput. A larger MTU also means processing of fewer packets for the same amount of data. In some systems, per-packet-processing can be a critical performance limitation."
http://en.wikipedia.org/wiki/Maximum_transmission_unit (Mods, please remove this link if it violates the TOS here)
Lyondellic said:
MTU is not specifically tied to either 3G or 4G. In fact, this setting is used on Windows based computers all the way back to the early versions of Windows. MTU is used to optimize the connection between the host and client. If MTU is set too low, bandwidth is reduced because more packets of data are managed. If MTU is set too high, fragmentation will occur and there will usually be a need for more re-transmissions of data. As a rule, 1500 is the Maximum MTU setting for cable based internet, while 1492 is the maximum for DSL.
"A larger MTU brings greater efficiency because each packet carries more user data while protocol overheads, such as headers or underlying per-packet delays, remain fixed; the resulting higher efficiency means a slight improvement in bulk protocol throughput. A larger MTU also means processing of fewer packets for the same amount of data. In some systems, per-packet-processing can be a critical performance limitation."
http://en.wikipedia.org/wiki/Maximum_transmission_unit (Mods, please remove this link if it violates the TOS here)
Click to expand...
Click to collapse
Everything you said is correct, but just to elaborate for those that might get mixed up, MTU has *nothing* to do with windows itself nor did Microsoft create the protocol. MTU predates Windows by some years and was set up as part of the greater Internet Protocol and OSI Model by DARPA in the late 70s/early 80s.
In theory, a larger MTU is a good thing, assuming the connection can handle the larger MTU. Slower connections trying to handle a high MTU can cause a bottleneck and lead to less efficiency than greater though. When that happens, it has to slice up the data units into smaller pieces (fragmentation).
Think of it as like having to carry a stack of bricks from one end of your yard to the other. Sure, if you're strong, you can carry a ton at once, but if you're not and you try to do so, you're going to have a heck of a time getting them from point A to point B and probably end up having to split up the load, slowing yourself down as you do so.
yareally said:
Everything you said is correct, but just to elaborate for those that might get mixed up, MTU has *nothing* to do with windows itself nor did Microsoft create the protocol. MTU predates Windows by some years and was set up as part of the greater Internet Protocol and OSI Model by DARPA in the late 70s/early 80s.
In theory, a larger MTU is a good thing, assuming the connection can handle the larger MTU. Slower connections trying to handle a high MTU can cause a bottleneck and lead to less efficiency than greater though. When that happens, it has to slice up the data units into smaller pieces (fragmentation).
Think of it as like having to carry a stack of bricks from one end of your yard to the other. Sure, if you're strong, you can carry a ton at once, but if you're not and you try to do so, you're going to have a heck of a time getting them from point A to point B and probably end up having to split up the load, slowing yourself down as you do so.
Click to expand...
Click to collapse
Thanks for filling in the gaps. I sometimes skim over information that requires a little more clarity, so I thank you for chiming in.
Edit: Nevermind. I changed to 1492 cause I use DSL at home so we shall see if I can get some better speeds with this change.
Mustang302LX said:
Edit: Nevermind. I changed to 1492 cause I use DSL at home so we shall see if I can get some better speeds with this change.
Click to expand...
Click to collapse
Guys you're forgetting your LTE service is not DSL. If you're changing MTU which by the way is "maximum transmission unit" and have been in existence way before Windows, use 1500. LTE is a flat IP based technology, and it doesn't matter if your home (WiFi) connection is DSL, you're using Verizon's 4G LTE and that's where you're applying MTU. 1492 is used on home computers that are wired connected to a DSL modem.
milan03 said:
Guys you're forgetting your LTE service is not DSL. If you're changing MTU which by the way is "maximum transmission unit" and have been in existence way before Windows, use 1500. LTE is a flat IP based technology, and it doesn't matter if your home (WiFi) connection is DSL, you're using Verizon's 4G LTE and that's where you're applying MTU. 1492 is used on home computers that are wired connected to a DSL modem.
Click to expand...
Click to collapse
I'll change it to 1500 then. Thanks.
btw I've been using stock since the launch date, and am seriously considering rooting for the first time after seeing this post. MTU can definitely help the throughput and I've been wondering for a long time if tweaks are possible on Android platform.
I know it's sounds noob (and when it comes to rooting I am) which leaked radios currently give the best data performance?
this is what I'm currently seeing on my Bolt: http://www.youtube.com/watch?v=RTwRm3QMqUs
I wonder if I can get closer to that 73.6mbps maximum theoretical throughput.
Thank you.
You must live underneath a cell tower. Lol. Highest ive seen on my phone is 25 down and 10 up.
Sent from my HTC ThunderBolt using Tapatalk
It's NYC lol. Every corner has some kind of pico cell and it's usually fed by preexistent fiber. NYC is loaded with dark fiber.
Still trying to figure out if I should just root and flash with that latest Gingerbread RUU or should I just keep it stock. I'm just trying to get the best possible data performance, don't really care too much about the features of the ROM.
milan03 said:
Guys you're forgetting your LTE service is not DSL. If you're changing MTU which by the way is "maximum transmission unit" and have been in existence way before Windows, use 1500. LTE is a flat IP based technology, and it doesn't matter if your home (WiFi) connection is DSL, you're using Verizon's 4G LTE and that's where you're applying MTU. 1492 is used on home computers that are wired connected to a DSL modem.
Click to expand...
Click to collapse
This is true for 3G/4G, but not when the phone is connected to Wi-Fi. A max MTU setting of 1492 is needed when connected to a Wi-Fi network that originates from DSL.
I have a Samsung galaxy a70, my WiFi speed is pretty fast but it keeps loading games forever (unless I use mobile data or VPN). Although I still have yet to try another wifi network. But anyway, I play only two games, honkai impact 3rd and mobile Legends. Honkai impact 3rd just keeps showing me the loading icon for long after which it dissappears and comes again after like 2 seconds, and if I try online in the game, it doesn't let me join at all. As for Mobile Legends (it's a MOBA) the loading screen takes sooo long (it shows everyone's loading percentage) and I'm always the last one to load, the inside of the game is so smooth, my ping is usually 8ms. Even when I'm browsing Instagram, videos and comments will load as if my WiFi speed is 1kb/s. This doesn't affect any browser tho. Didn't try with Facebook. This only happens on my phone in the whole house.
Forgot to add: This randomly starts happening and goes away after pretty long
Maybe cause the server you're trying to connect is far away? idk i don't know about games that much.
Shiro124 said:
I have a Samsung galaxy a70, my WiFi speed is pretty fast but it keeps loading games forever (unless I use mobile data or VPN). Although I still have yet to try another wifi network. But anyway, I play only two games, honkai impact 3rd and mobile Legends. Honkai impact 3rd just keeps showing me the loading icon for long after which it dissappears and comes again after like 2 seconds, and if I try online in the game, it doesn't let me join at all. As for Mobile Legends (it's a MOBA) the loading screen takes sooo long (it shows everyone's loading percentage) and I'm always the last one to load, the inside of the game is so smooth, my ping is usually 8ms. Even when I'm browsing Instagram, videos and comments will load as if my WiFi speed is 1kb/s. This doesn't affect any browser tho. Didn't try with Facebook. This only happens on my phone in the whole house.
Click to expand...
Click to collapse
Wireless networks use two main frequency bands: 2.4 GHz (gigahertz) and 5 GHz. These frequency bands affect how far and how fast data can travel over WiFi. The 2.4 GHz band gives you slower speeds at a longer range, while the 5 GHz band gives you faster speeds at a shorter range.
So, if you want the fastest WiFi speeds, you should always use the 5 GHz band. However, the more devices you have on one band, the slower your WiFi will be.
Wifi connection has nothing to do with loading screen .. what is your performance rating on Mobile Legends?
With regards to a Wi-Fi connection many aspects come into play, such as bandwidth, Internet speed and latency, among others.
When the mentioned games get launched they at 1st thing of all things fetch data / resources from Internet what will take some time which depends on the 3 above mentioned criteria. The progress typically gets shown on game's loading screen.
Same is the case when you from within the games try to establish a further Internet connection.
BTW: An Internet speed of 1KB/s indeed is really inacceptable. Normally the Internet speed is in the range of 700-800 KB/s.
goto Setting then Network Test then Performance Test and let Mobile Legends rate your device also fast loading screen have disadvantage you will never have time seeing enemy team hero selections and decide what equipment to buy to counter them ...
here's mine MediaTek Heli P20 rating on Mobile Legends not that fast but it's decent
It's not only on games, Instagram does not load videos at all, and my WiFi download speed is 5 mbps so I'm pretty sure it's not my WiFi at fault. As for mobile Legends, now that it added the data optimization thing at the start of the game, the loading speed is back to normal now. But honkai impact 3rd and Instagram remains the same, ESPECIALLY Instagram.