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
Related
I'm sure this is a noob question, but I can't find the answer on the forum.
I've seen a couple people reference automatically ending the data connections when they're idle. Can someone explain how this is done?
Is the desire to disconnect the data to save on battery life? Just curious. Thanks.
That's the main reason I want to do it...not sure about others...
I figured out two ways to do this for anyone else that's interested.
1) Using Advanced Config Tool (V3.3): Menu > More Settings > Connections. Check "Disconnect After" and set the timeout you want. This seems to work well for activesync connections (my mail is set to recieve every 5 min), but doesn't always work for on demand connections (Internet).
2) Comm Manager Pro. No instructions for this since I'm not using it (yet). But everything I've read looks like it does it.
Like I mentioned, I've got my email configured to sync every 5 minutes and I have a connection timeout of 30 seconds set in Advanced Config. This setup has drastically improved my battery life. Before this change, I got maybe 12 hours on a good day. With this timeout set, I could probably get 2 solid days. The only thing I haven't figured out is if the timeout is and idle timeout or an overall timeout. What I mean, is will the connection end after 30 seconds even if it's in use?
I'm interested in this as well, it would be even better if outlook or msn live would make a connection and disconnect after synchronizing.
I've been looking for the same solution. So far using advanced config settings will force disconnect no matter if it was idle or not. I'm looking for a solution to disconnect only when idle.
As of proof, set auto disconnect to 1 minute and using latest skype v3.0 start transferring a large file. After 1 minute data connection will be forcibly disconnected.
Any solutions for this?
Thank you.
Can someone help me find the timing setting in Advanced Config? I've looked through everything - using Energy 3.0 Rom (WM6.5) and don't see anything related to data disconnect other than under "Data Connections:" "GPRS disconnect:" and my settings are "Enable button and timer"
I don't see where the timer comes into play; don't really care if the connection gets cut off - I'd rather see a battery life improvement.....
I'm an absolute idiot. I just skimmed through the thread and didn't read the post above... *smacks forehead*
Its been posted in this very topic, and its only 5 replies long
xawen said:
I figured out two ways to do this for anyone else that's interested.
1) Using Advanced Config Tool (V3.3): Menu > More Settings > Connections. Check "Disconnect After" and set the timeout you want. This seems to work well for activesync connections (my mail is set to recieve every 5 min), but doesn't always work for on demand connections (Internet).
2) Comm Manager Pro. No instructions for this since I'm not using it (yet). But everything I've read looks like it does it.
Like I mentioned, I've got my email configured to sync every 5 minutes and I have a connection timeout of 30 seconds set in Advanced Config. This setup has drastically improved my battery life. Before this change, I got maybe 12 hours on a good day. With this timeout set, I could probably get 2 solid days. The only thing I haven't figured out is if the timeout is and idle timeout or an overall timeout. What I mean, is will the connection end after 30 seconds even if it's in use?
Click to expand...
Click to collapse
In advanced config the settings you are looking are not located in the list on first screen, the are in separate menu as described above.
And now I'll quote myself so my question will not get burred:
[email protected] said:
I've been looking for the same solution. So far using advanced config settings will force disconnect no matter if it was idle or not. I'm looking for a solution to disconnect only when idle.
As of proof, set auto disconnect to 1 minute and using latest skype v3.0 start transferring a large file. After 1 minute data connection will be forcibly disconnected.
Any solutions for this?
Thank you.
Click to expand...
Click to collapse
guys, found this
http://www.andrewsayshello.com/windows-mobile/auto-disconnecting-idle-data-connections-in-wm6/
hope this helps in some way
Thanks for the link, unfortunately it still disconnects even if data connection is in use.
WMLongLife can do this for you.
About the registry tweak that does this, I must warn you: it disables the ability to do voice and data simultaneously.
Chainfire said:
WMLongLife can do this for you.
Click to expand...
Click to collapse
Just checked WMLongLife and it seems that program does not quiet work if one doesn't use opera or wifirouter...
Chainfire said:
About the registry tweak that does this, I must warn you: it disables the ability to do voice and data simultaneously.
Click to expand...
Click to collapse
This is new for me...I thought that data connection cannot co-exist with phone call, period..
[email protected] said:
Just checked WMLongLife and it seems that program does not quiet work if one doesn't use opera or wifirouter...
Click to expand...
Click to collapse
Yes it does require a certain way of using your phone (current test version has specific settings - you can change this in next version). Just saying.
This is new for me...I thought that data connection cannot co-exist with phone call, period..
Click to expand...
Click to collapse
Yes it can, but it depends on several factors. Under ideal (and never actually occuring) conditions it can be done with 2G GSM (GPRS/EDGE). Normally, however, either GPRS/EDGE connection suspends ('pauses') during voice call, or with 2G CDMA voice call may not work at all while data connection active (depends on exact 2G CDMA network type).
With 3G GSM (UMTS/HSPA) it is quite possible (and normal) to do data and voice simultaneously, however for some reason the auto data disconnect registry tweak breaks it. I'm not quite sure why, but it does.
3G CDMA (EV-DO) behaves the same as 2G GSM with regards to simultaneous voice and data (data drops), however, EV-DO Rev. A behaves the same as 3G GSM (possible but broken by registry tweak)
Aside from this, it is also needed that your provider/network has the correct hardware to handle this. I'm not sure how common it is for this properly operating on EV-DO Rev. A, but for UMTS/HSPA early tower equipment was bugged and did not allow this. In Europe, most UMTS/HSPA towers have since been upgraded to allow simultaneous voice and data (and HTC handsets support this perfectly), but how this is in the USA I cannot say.
Hope that explains it (it is a bit messy explenation I know)
if this dowsn't work then i have no ideea what will )
http://forum.xda-developers.com/showthread.php?t=484084
tell me if worked for you
!!!!!
I had it set to disconnect (via Diamond Tweak software) after 1 minute of activity. I did this to preserve battery life, BUT BUT BUT
With 3g on, and even with 3g disabled all day and edge on, the battery still died in 8, 12 hours (3g, edge) with the connection disabling. i use the phone for a good number of calls, text, and some data every day.
AFTER i reenabled it to NOT disconnect after every 1 minute, i pulled over 24 hours on a SINGLE charge.
am i the only one that's experienced this??
Introduction:
So there has been a lot of bugs & glitches coming out as we get to use the phone more and more and they just seemed to be all over the forum and the forum is looking very unorganized.
Request: Can any of our G2x forum Mod's made this a sticky?
Here is the list of bugs and glitches that i have compiled from the whole forum:
**Added 04/23/2011**
Media Scanner bug
After leaving a 4G area phone will say that is connected to 4G but in reality there is no data and will not change to 3G/2G
When pressing home button or just navigating the home screens, screen flashes/flickers (Happened to me too)
Kinetic scrolling could be improved and the screen shakes when holding a position with your finger:
http://forum.xda-developers.com/show....php?t=1044179 and http://forum.xda-developers.com/show....php?t=1046473
No System UI sounds nor a System Volume setting
Bleeding LCD mostly 2 upper corners
Overheating when playing games, tethering, HDMI mirroing.
WiFi not connecting with some routers. Seems to happen with Dual band routers
WiFi Profiles keeps getting disabled
Phone connected to UMTS but displaying 4G notification icon
4G turning on when WiFi is supposely "On"
4G disconnects too much and randomly switching between Edge/3G/4G in same area with 4G
4G is not as fast as other phones with same hardware http://forum.xda-developers.com/show....php?t=1043716
Battery draining fast possibly due to this connection glitches
Freezes and Reboots
Connecting Headphones, or any Input will make Mic mute. When connected to car input, caller can the other person but person called can't hear caller.
Music turns off when opening camera
Phone screen brightness gets really dark when opening camera and auto-brightness is enabled
GPS works but sometimes slow to lock (Work around: http://forum.xda-developers.com/showthread.php?t=1009529&highlight=gps Thanks Mitta from LG 2X forums for getting a working fix and to the many other work around offered)
Cannot adjust brightness or Screen timeout settings anywhere only with market apps
Email signature keeps changing to default even after modifying it or removing it.
Bluetooth stops working after using WiFi or Wireless tethering
Audio would randomly stop working after having it plugged in to a TV via HDMI cable.
Lock screen sound won't work
SD card not been able to be mount
I know there is a Poll with an "Issue Summary" but it is lacking a list of bugs and glitches in the Original Post.
Anyways, So this thread is really to compile a list of the known bugs and glitches to make it easier for the Devs to determine what they should be looking at to fix and for everyone to look for known issues and make the G2x Forums neater.
I strongly believe that this forums are visited by manufacturers and by phone companies, almost 99% sure about this. So let's make the issues known to get them working on hardware optimizations and software.
Here is the link to the Issue Summary Poll: http://forum.xda-developers.com/showthread.php?t=1043500&page=10
I read all 10 pages and could say that the most common issues posted in that thread are reboots and freezes.
I will be updating this post as bugs and glitches comes out.
Please post your glitches if they are not mention in this thread. so that I can add those
Thanks for posting. Good work!!!!!!!!!!!!!!!!!!!!!!
tenbeau said:
Thanks for posting. Good work!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
For a better G2x!
I have had the phone since release day on the 20th and have had none of these problems *knocks on wood* although I did come across something really weird. I had the phone in my pocket and I don't know if I accidentally turned it on or whatever but I took it out of my pocket at one point and it was kind of hot on the back. When I hit the power button I got nothing so I had to battery pull and then power it on and that worked. When it booted the battery was under 5% (battery was over 50% when I initially put it in my pocket which was only about an hour or so when I noticed it was off and felt hot). So I plugged it in charged it back to 100% and have been fine since that. Has anyone else had this happen to them?
Nice work on getting this thread started. Is there any way you can also put links to the threads that these issues are talked about? I would be great to be able to read the thread easily if you have that issue with your phone. May help the devs find things easier too!
I am having an issue with my screen. if I am on a web page that is not designed for mobile phones and I push my finger on the screen and don't move it all, the screen will shake endlessly until I remove my finger. It will also do it if I hold when flipping between home screens. Does anyone else have this issue?
Please forgive my ignorance if these aren’t really bugs or are simply repeats of the above, but I discovered two new items with both my wife and my G2x’s that I’d like some feedback on.
I had zero data in WI tonight where T-mobile shows as having data coverage. The phone display shows that I am connected to AT&T for voice with a GPRS signal. Additionally, neither navigation or Google maps give me my location when both of these features had worked when I had data.
I’d be interested in learning if these items are actually bugs of if they are simply related to the available networks and G2x hardware. If bugs, does it sound like they could be fixed through a software update?
Thanks in advance.
I have 2 more bugs to add. Both of them being pretty damn major.
1. Once you leave a 4G tower it will not downgrade to 3G or Edge for data but voice will still work. The 4G icon is still there but you will have no data connection. In order to get your data working again you have to manually disable then re-enable it through network settings.
2. After removing the device from my pocket, it is in car mode. (Had to freeze the app so it stopped)
One other minor bug people are experiencing is upon awaking the device it will flash your home screen before your lock screen.
I can't see myself keeping this device after the sensation comes out. In my opinion, the G2x is possibly the buggiest device I have ever had and was not ready for launch. I will keep exchanging my G2x until I get one that works 100%.
By the way, I had to freeze "My Account" app and "Wifi Calling" because they were accessing data constantly.
Kinetic scrolling could be improved and the screen shakes when holding a position with your finger:
http://forum.xda-developers.com/showthread.php?t=1044179
http://forum.xda-developers.com/showthread.php?t=1046473
Some are reporting slower data speeds than normal:
http://forum.xda-developers.com/showthread.php?t=1043716
http://www.mobilecrunch.com/2011/04/20/review-t-mobile-g2x-optimus-2x/
No System UI sounds nor a System Volume setting.
OP Updated!
Xeyro said:
Please forgive my ignorance if these aren’t really bugs or are simply repeats of the above, but I discovered two new items with both my wife and my G2x’s that I’d like some feedback on.
I had zero data in WI tonight where T-mobile shows as having data coverage. The phone display shows that I am connected to AT&T for voice with a GPRS signal. Additionally, neither navigation or Google maps give me my location when both of these features had worked when I had data.
I’d be interested in learning if these items are actually bugs of if they are simply related to the available networks and G2x hardware. If bugs, does it sound like they could be fixed through a software update?
Thanks in advance.
Click to expand...
Click to collapse
Thanks for posting Xeyro, few questions for you,
Did you had a T-Mobile phone before and did you used in this area?
Was it 4G? If yes, where you able to connect fine to the network?
If your answers are yes then your G2x should be connecting just fine as well if not then there is a glitch/bug with the phone. Try rebooting to see if that helps.
Xeyro said:
I had zero data in WI tonight where T-mobile shows as having data coverage.
Click to expand...
Click to collapse
Figured it out; user error. Apparently there's a check-box in the wireless and network settings to allow data roaming. Apparently this box is unchecked by default, and checking the box has restored data connection to the phone.
Thanks for the response Moshe.
Looks like we were posting at about the same time, but I figured out my error. The phones are set by default to not allow data roaming, and you have to manually make the change in the settings. Everything seems to be working as expected at this point.
Xeyro said:
Figured it out; user error. Apparently there's a check-box in the wireless and network settings to allow data roaming. Apparently this box is unchecked by default, and checking the box has restored data connection to the phone.
Click to expand...
Click to collapse
If I understood your problem correctly, that is no fix at all. Data roaming is turned off by default because data roaming charges are massive. The reason it started 'working' is because you allowed the phone to roam data over the AT&T network instead of connecting to tmobile towers. Watch out because your next bill is going to be a whopper.
dasbin said:
If I understood your problem correctly, that is no fix at all. Data roaming is turned off by default because data roaming charges are massive. The reason it started 'working' is because you allowed the phone to roam data over the AT&T network instead of connecting to tmobile towers. Watch out because your next bill is going to be a whopper.
Click to expand...
Click to collapse
Thanks for the heads up dasbin. I decided to give T-Mobile a call to make sure I wasn't being charged an arm and a leg and this is what I learned.
The T-mobile coverage in this area is actually provided through 3rd party networks, so while the maps show data coverage, it may not be T-mobile directly providing the data. Therefore, the option to roam data needs to be turned on. T-mobile only charges for international data roaming, so there are no extra fees as this is how the network is designed to work.
I think then the "bug" isn't as much of a bug as an understanding that the phone is not configured by default to allow non T-mobile data networks. I wonder how often this has caused some of the dropping of data that others have experienced?
I only have the bleeding issue and reboot issues. If I exchange, it could be a lot worse.. decisions decisions..
You should include the Media Scanner bug.
If I put any substantial amount of media (more than 3mp3s) on my sd card, media scanner glitches and never finishes scanning, making camera, music, video, gallery, etc unusable.
I've seen at least one other poster with this issue.
ericc191 said:
I only have the bleeding issue and reboot issues. If I exchange, it could be a lot worse.. decisions decisions..
Click to expand...
Click to collapse
Yea, same here, and when I have some free time I want to look at the kernal source, I'm thinking the frezzing/rebooting is caused by it, its acting the same as my mt4g did using custom kernals until those were fixed, so I think once we can get some custom kernals out we'll be good to go on that issue.
Sent from my LG-P999 using XDA Premium App
OP Updated with the Media Scanner bug and some other ones
dasbin said:
If I understood your problem correctly, that is no fix at all. Data roaming is turned off by default because data roaming charges are massive. The reason it started 'working' is because you allowed the phone to roam data over the AT&T network instead of connecting to tmobile towers. Watch out because your next bill is going to be a whopper.
Click to expand...
Click to collapse
T-Mobile only charges for international roaming.
Just got my TB - loving everything about it except the battery. My iphone 3g had an exceptional battery.
During the recent 4g outage - I checked out the settings at *#*#4636#*#* to get the 4g radio to switch to cdma auto.
While there I noticed that both my 4g and 1x speed icons on the notification bar would light up the send arrow every three seconds (barring any other kind of network activity) when idle. I noticed on the phone info area it lists PPP sent and PPP received. Every three seconds my sent data numbers increased by 241 bytes.
EVERY. THREE. SECONDS! Thats 20 times a minute, 1200 times an hour. Every hour, my phone sends 289,200 bytes somewhere. During the course of a 24 hour day (if my battery can last that long) - that's 6.6 megabytes a day or 200 megs a months just sitting idle.
While not a lot of data - I'm sure 28,800 transmissions from the cell radio a day can have a drain on the battery.
Is there a way of seeing which app is transmitting data and where? I read a similar bug was found on Win Phone 7 devices.
If this has been discussed before I'm sorry. Searching for "241 bytes" showed no hits.
Also on a side note - just noticed on my TB that when a calendar reminder appears on my lock screen, when you slide down to dismiss the event, you go right into the phone even though there is a security lock (lock pattern for me) enabled. So you can gain access to any TB by simply waiting for a calendar event. Not cool!
Network keep-alive?
is your sync turned on?
that would be great if it was a bug and we could figure it out.
well I sync using the minimum settings - disabled stocks and twitter sync. Most others are set to the lowest sync settings.
Even if this is just a keep alive ping - 1/4 gig a month can cut into data limits if you don't have an unlimited plan. And this is when the phone is sitting idle.
I Noticed My Phone Randomly Submitted 3g Data (No 4g Here) when rooted on custom rom and when I was Stock. Idk Why. I have Only Mobile Network Checked. No Auto Sync. No Background Data on. Idk Why I randomly see that Arrow go up. Maybe its an app I have..hmm..
Went To Battery Stats and checked Network Usage in Battery History. Then Check all Time. Shows Internet as the Most, Then 0 (Idk what this is) Then Media (What Media?) then Dialer, Then Android System then Market, then all Others (Rest dont matter because usage is so low.)
I'm having this issue also, except more data is being used each time than what you posted in OP. I had background data turned off and it still happens. Would like to see this worked out.
Sent from my ADR6400L using XDA App
Hello,
as you may or may not know fast dormancy is by now a mature technology implemented by all major networks worldwide. It involves 3G (HSPA) technology only and it allows the phone AND the network to keep the connection on using different levels of state (RRC) so that when you finish transferring data at high speed the state goes to a lower energy one or even idle using much less power, saving battery life significantly.
It has been explained by XDA website 2 years ago, you can also find more info on wikipedia.
What's the point of this topic? With my i9505 International I've always used Google Edition ROMs since the first edition was released. Battery life has always been fine while using 3G data on standby.
When I upgraded to KitKat Google Edition I noticed the battery would drain much, much quicker (when the screen is off mainly). I got used to it that I assumed it was how things worked until I ended up reading about people with much battery life on 3G and KitKat (but CM11 or AOSP) so I started investigating and trying different ROMs/configurations (I asked devs on their respective threads but I have been completely boycotted! ). At the end I concluded fast dormancy was not working (on the phone part) in anyway on KitKat ROMs made by Samsung.
How do you know if FD is active on the device?
- install apps to detect wakelocks like BetterBatteryStats (you don't need root)
- turn on 3G data and disable WiFi
- keep the screen off for about 1 minute (make sure you're not downloading anything)
- turn on the screen on check "kernel wakelocks". If you have "fast_dormancy" anywhere in the list then it's on otherwise it is not active
What ROMs did you test and how?
This is what I did: I made sure to have the same configuration and apps on every test, same location and signal strength.
I charged the phone to 100%, turn on 3G data, unplugged and left it idling with sync on for 4 hours. I noticed (via betterbatterystats logs) that with fast dormancy off I would lose about 2.5%/h, while with fast dormancy on the drop would be about 0.7%/h!!
And let's not talk about when you move around or drive, for instance with FD off with my usual drive to class I've always lost 3-4% in 15 minutes, I mean ALWAYS. With FD on the battery wouldn't move at all! That is a HUGE difference!
The ultimate test for me was a real life test. I went studying for two consecutive days at college in the same spot using the phone the same way (browsing, tapatalk, facebook messenger), with FD off I would come back home after using the screen for 1h30m at about 15% (mainly because I would lose power just on stand-by!) but FD on repeating the same steps the following day with FD on I went home at the same time and after using the screen for 2h20m I still had 45% of battery, WOW!
ROMs where FD works:
- 4.2.2, 4.3 TW
- 4.2.2., 4.3 GE (untouched and customized)
- CM10.2, CM11
- AOSP 4.4.2 ROMs
ROMs where FD doesn't work:
4.4.2 GE (untouched and customized)
4.4.2 TW (leak)
I used only one modem during these tests, the latest from the KITKAT leak.
What have you tried to force it?
Well I can tell you for sure that ro.ril.fast.dormancy.rule has no effect on TW/GE ROMs, I also tried to change the database as described here http://www.androidnz.net/2012/06/at-your-own-risk-how-to-disable-fast.html to set it to ON but you should know that FD on every ROM is on by default. I have no proof of this but with FD off even if your network seems to go to lower energy states on the network side (you can see all this using Samsung Service Mode), on the phone side the radio keeps using a lot of power as if it remains "active" thus draining battery like a b*tch
So has Samsung forgotten to include this feature? What do you think?
Also do you know where I can ask support for this to be fixed? Should I ask Google on the play store (even if I don't technically have a GPE phone!) or via Samsung website even if it's not sold on their site? Even worse KK TW is not even out yet officially.
Mod Edit
Please incorporate this in the KitKat thread HERE
Thank you
Thread closed
malybru
Forum Moderator
Two weeks felt like two years when my phone suddenly started acting odd. High CPU usage, 2x battery drain compared to before, phone heating up while doing simple tasks drove me insane. I thought there might be something wrong with the phone but couldn't find anything so I sent it to the customer service center. All they did was factory reset, installed the latest stock OS, and sent it back which didn't solve my issue.
So I rooted the phone, installed a custom ROM and the problem was still there. I lost the tiny bit of hope I had left and concluded that it's a hardware issue and I might have to buy a new device. Two days later I installed the Better Battery Stats app and kept my phone idle overnight with wifi on.
The next day I finally found out what's been eating my battery. In BBS under Kernel wake-locks, I saw qcom_rx_wakelock was on for 8 straight hours, as long as my wifi was on. Checked the CPU states on the FK Kernel manager and found out the phone never went to deep sleep, not for a second! Also, there was that idle wifi usage.
So I downloaded the Network Log app and kept logging on the next night. 9 hours passed, none of my apps used the internet but the kernel used almost 500 mbs in 9 hours! So that's where my wakelock was coming from.
I went to my friend's house and used his wifi for a few hours to identify what's going on and I was surprised to see there was no battery drain, low CPU usage, and zero idle wifi usage. For a moment there everything seemed to went back to normal. When I came back to the school dormitory the nightmare started again.
I started scouring on the internet and I found this which led me to this terrific post!
This comment explains everything!
To summarize, the phone was going crazy because of wifi multicast, and arp flooding. I couldn't do anything about it as I was in the university's public wifi. You can disable multicast by going to the router page and turning off wifi multicast from IGMP snooping setting. But it was impossible for me cause school won't allow me to change anything and even if I complain they won't care.
So I decided to fix it by adding some of the Pixel 3's WCNSS_qcom_cfg.ini properties to my phone's WCNSS_qcom_cfg.ini which I located in the vendor/etc/wifi/ as r/skanadian recommended in the second post which took my qcom_rx wakelock to 19%, way less compared to 86% before.
This is a step-by-step guide to reducing battery drain -
• Backup your phone's WCNSS_qcom_cfg.ini in case something go wrong. I found it in system/vendor/etc/wifi/here
It might be different for you depending on what Rom or device you are using. The filename will be the same but the location might be different.
• Get a text editor. Mixplorer is recommended as it helps to search properties quickly with its find feature.
• Open your devices WCNSS_qcom_cfg.ini using Mixplorer and keep it open. Alternatively, you can copy it to a different folder on your phone. I suggest the second one cause it's better than directly editing the file from the system.
• Go to this page
• Go to your browser option and select find in page to search. Search for the word "offload" on that page.
• Copy all the lines related to offload one by one and replace them on your devices WCNSS_qcom_cfg.ini that you opened using Mixplorer.
• If there isn't anything to replace simply add those lines. Don't forget to hit the save button while doing that.
• After that, search for these properties on your WCNSS_qcom_cfg.ini and set them as I did below
RoamRssiDiff=3
g11dSupportEnabled=0
gEnablePowerSaveOffload=5
gRuntimePM=1
RTSThreshold=1048576
gMCAddrListEnable=1
gActiveMaxChannelTime=40
gActiveMinChannelTime=20
gMaxConcurrentActiveSessions=2
If you don't see one of these to replace in your WCNSS_qcom_cfg.ini you should add it.
• Now reboot your phone, give it some time and see if the battery improves. If everything remains the same then go to WCNSS_qcom_cfg.ini using Mixplorer again, find BandCapability, and set it like this -
BandCapability=1
It will disable 5ghz from your phone. I found out most companies release their phones with bad wifi drivers which don't handle the 5ghz wifi band appropriately. Lack of power-saving and not blocking multicast requests properly leads to higher CPU usage and bad battery life.
Again you can set the BandCapability=2 if you want to use 5ghz mode only. If you have a good wifi driver, the battery drain might come from switching between 2.5 and 5ghz so keeping on one of them helps.
• Why qcom_rx wakelock and what is the best fix?
It can occur for several reasons.
- Wifi multicasting. Multicasting can be disabled from IGMP snooping on router settings. You don't need multicasting in your home network at all. But when you're on office wifi or school wifi, it does improve the speed slightly by reducing data loss and interference. It also can be solved the same way but if your school management is like mine, then they might not care if your laptop or phone burns.
- DHCP timers
- A software bug from server-side
- Band switching
- Even interference, if you have a public network with a lot of phones and PCs
There are some more reasons I can not remember now. The best way to fix it is to build a custom kernel with WLAN and qcom_rx blockers/limiters e.g. Franko Kernel.
But sadly a lot of us will never have that unless we make a kernel for ourselves. So as of now, this is the solution I could come up with.
My knowledge of this sector is very little. It would be great if you all could help me get rid of this problem.
I would love it if there was a feature built-in on Android OS to block some kernel wake-locks.
OnePlus phones allow you to turn off multicasting from Developer Options but that makes little to no difference depending on what wifi you are using.
• Very Important :
Depending on you wifi, you can try setting hostArpOffload=0 and hostNsOffload=0
or you can try setting both to 1. Use whichever improves the battery backup. Don't forget to reboot after changing anything.
If you are an expert, please help us. Cause these wakelocks aren't going anywhere. They will give some of us many more sleepless nights.
Thank you for reading. Have a good day!
For those who don't want to change settings they don't understand:
RoamRssiDiff: The difference in signal strength required before phone will switch to a new Access Point. Measured in -dbs. 3 means it will switch APs if the signal strength is 3dbs better than the one in use.
g11dSupportEnabled: WIFI 802.11d
gEnablePowerSaveOffload: Level of Powersave
gRuntimePM: Runtime Powermanagement
RTSThreshold: How long to wait before asking to send wifi packets. Should be as high as possible, only lowered if you have wifi dropouts.
gMCAddrListEnable=1: Drops all Multicast frames except for ARP. You don't want to disable ARP entirely or your internet will break, so don't lower this to 0.
gActiveMaxChannelTime: Time spent scanning.
gActiveMinChannelTime: Ditto
gMaxConcurrentActiveSessions: Self-explanatory
While looking this up I also found gNeighborLookupThreshold or RoamLowRssiThreshold: The signal strength at which the phone starts looking for a new AP (the step before RoamRssiDiff becomes relevant). Typical values are 65-80. Changing this might help too if your phone is switching AP too often or not often enough.
Thanks for this, my device was also affected by this (though not as badly as yours) I've just disabled Multicast from my router.
TrenchFullOfSlime said:
For those who don't want to change settings they don't understand:
RoamRssiDiff: The difference in signal strength required before phone will switch to a new Access Point. Measured in -dbs. 3 means it will switch APs if the signal strength is 3dbs better than the one in use.
g11dSupportEnabled: WIFI 802.11d
gEnablePowerSaveOffload: Level of Powersave
gRuntimePM: Runtime Powermanagement
RTSThreshold: How long to wait before asking to send wifi packets. Should be as high as possible, only lowered if you have wifi dropouts.
gMCAddrListEnable=1: Drops all Multicast frames except for ARP. You don't want to disable ARP entirely or your internet will break, so don't lower this to 0.
gActiveMaxChannelTime: Time spent scanning.
gActiveMinChannelTime: Ditto
gMaxConcurrentActiveSessions: Self-explanatory
While looking this up I also found gNeighborLookupThreshold or RoamLowRssiThreshold: The signal strength at which the phone starts looking for a new AP (the step before RoamRssiDiff becomes relevant). Typical values are 65-80. Changing this might help too if your phone is switching AP too often or not often enough.
Click to expand...
Click to collapse
Cool!
There are some other wakelocks that's bothering me more than qcom_rx and I have no idea what they are!
Could you please tell?
Mario3DS said:
Thanks for this, my device was also affected by this (though not as badly as yours) I've just disabled Multicast from my router.
Click to expand...
Click to collapse
Sadly I'm on school wifi and can't do anything about it!
lpass is a Qualcomm audio subsystem for things like voice based wakeup, and IPCRTR (inter-process communication router) is just how different processes on your phone communicate with each other.
Others have reported these wakelocks too, almost always when they have a wifi/cell connection. Maybe it has to do with voice assistants communicating with their home servers?
TrenchFullOfSlime said:
lpass is a Qualcomm audio subsystem for things like voice based wakeup, and IPCRTR (inter-process communication router) is just how different processes on your phone communicate with each other.
Others have reported these wakelocks too, almost always when they have a wifi/cell connection. Maybe it has to do with voice assistants communicating with their home servers?
Click to expand...
Click to collapse
Well
I asked a kernel dev and he gave exactly the same explanation you gave me. He also said these are necessary and doesn't drain battery too much.
I am on a custom kernel now and wlan, qcom_rx wls are gone.
Thanks for the help
With the new kernel, I'm not seeing Lpass wakelocks much. They are there but limited.
TrenchFullOfSlime said:
lpass is a Qualcomm audio subsystem for things like voice based wakeup, and IPCRTR (inter-process communication router) is just how different processes on your phone communicate with each other.
Others have reported these wakelocks too, almost always when they have a wifi/cell connection. Maybe it has to do with voice assistants communicating with their home servers?
Click to expand...
Click to collapse
I see you've gained quite some knowledge regarding wakelocks. Your explanation was simple and easy to grasp. Could you please guide me to a thread where I can learn more about it?
Thank you so much
I just googled all the terms. Qualcomm publishes some of its stuff (source code and .ini files) with comments, others were referenced in AOSP sources.
Thanks for posting this, with my pixel 4a setting "hostArpOffload" to 0 solved it. NETLINK wakelok are much less and no battery drain.
Although on onePlus 7 pro which I've rooted few days ago none of this is working and NETLINK wakelok is draining battery at 2-3% per hr.
I'll try flashing a different ROM and If found any fix will post it here.
Device1 : Pixel 4a | LineageOS 18.1 | microG
Device2 : OnePlus 7pro | LineageOS 18.1 | microG
Edit : There are many multicast requests and NETBIOS requests too and looks like NETBIOS requests are coming from all the windows machines which are connected via Access point.
Edit:
Tried packet capture and Router is just flooding network with Multicast and ARP traffic.
I'm in the same situation as you since I live in University Campus so no router access, Have no idea how to solve this now.
A viable option is maybe buy your own router then use it as an extender and block all these garbage requests but no idea in extender mode will you be able to block stuff or not.
seated_singer said:
Thanks for posting this, with my pixel 4a setting "hostArpOffload" to 0 solved it. NETLINK wakelok are much less and no battery drain.
Although on onePlus 7 pro which I've rooted few days ago none of this is working and NETLINK wakelok is draining battery at 2-3% per hr.
I'll try flashing a different ROM and If found any fix will post it here.
Device1 : Pixel 4a | LineageOS 18.1 | microG
Device2 : OnePlus 7pro | LineageOS 18.1 | microG
Edit : There are many multicast requests and NETBIOS requests too and looks like NETBIOS requests are coming from all the windows machines which are connected via Access point.
Edit:
Tried packet capture and Router is just flooding network with Multicast and ARP traffic.
I'm in the same situation as you since I live in University Campus so no router access, Have no idea how to solve this now.
A viable option is maybe buy your own router then use it as an extender and block all these garbage requests but no idea in extender mode will you be able to block stuff or not.
Click to expand...
Click to collapse
OP 7 pro is the device you mentioned? I think it has custom kernels with bult in wakelock blockers that automatically blocks wlan, netlink and qcom rx.
Edit: Netlink can be blocked by using Custom kernel others wakelocks are due to ARP network flood. Turning it off from WCNSS_qcom_cfg or blocking introduces another problem of few seconds delay in connection ( due to ARP Resolving issue ) when switching from one access point to another ( only when automatic ) and since I do it quite often when roaming my University campus it's a hassle.
One way to mitigate this ( if you need to keep ARP offloading off ) is by using static IP, worked for me and my roommate too, but not viable since you need root. Finally I have set up my own router, checked and there were no wakelock.
Few of my friends are also facing this battery drain issue not on all Access points but some maybe after complaining authority will fix this.
Note : Netlink is only showing on Android 11/12 with other versions there are other wakelocks.
seated_singer said:
Netlink can't be blocked nor does it show since It's a part of kernel itself, here now about other two they are due to ARP network flood. Turning it off from WCNSS_qcom_cfg or blocking introduces another problem of few seconds delay in connection ( due to ARP Resolving issue ) when switching from one access point to another ( only when automatic ) and since I do it quite often when roaming my University campus it's a hassle.
One way to mitigate this ( if you need to keep ARP offloading off ) is by using static IP, worked for me and my roommate too, but not viable since you need root. Finally I have set up my own router, checked and there were no wakelock.
Few of my friends are also facing this battery drain issue not on all Access points but some maybe after complaining authority will fix this.
Note : Netlink is only showing on Android 11/12 with other versions there are other wakelocks.
Click to expand...
Click to collapse
I have NetLink blocked from kernel.
Some of this problems are impossible to fix from phone. So I contacted school management. They didn't believe me at first then I went to the head office and showed them with Network Log app that records every single packet.
A week later they fixed it. Contact your authority and see if it helps.
Thanks for the info mate, edited. Never thought I have to deal with this stupid WiFi problem.
RyanCr7 said:
Two weeks felt like two years when my phone suddenly started acting odd. High CPU usage, 2x battery drain compared to before, phone heating up while doing simple tasks drove me insane. I thought there might be something wrong with the phone but couldn't find anything so I sent it to the customer service center. All they did was factory reset, installed the latest stock OS, and sent it back which didn't solve my issue.
Thank you for reading. Have a good day!
Click to expand...
Click to collapse
Thanks for sharing, same thing happened to me..
Reading this post and turning off Multicast on both my wifi APs worked!
Just wanted to say that following this advice with all the Offload parameters, my wifi wakelocks have pretty much vanished so far on my nexus 4, i was getting something like 14000 wakelocks in battery guru. Thank you.
I can't understand why they don't specify what commands work for what Qualcomm chipset, since even though that is a newer phone, they still work on an older WiFi chipset, I've been mixing and matching for years.
KitsuneFoxy said:
Just wanted to say that following this advice with all the Offload parameters, my wifi wakelocks have pretty much vanished so far on my nexus 4, i was getting something like 14000 wakelocks in battery guru. Thank you.
I can't understand why they don't specify what commands work for what Qualcomm chipset, since even though that is a newer phone, they still work on an older WiFi chipset, I've been mixing and matching for years.
Click to expand...
Click to collapse
I'm glad it worked for you.