Does anyone know of the best way to get serious technical attention from Google or Samsung? To put how serious this is (not to start a flame war), I will be purchasing an iPhone 5S on Monday and never another Android device unless either they solve this issue or I get another job (I LOVE my job, so unlikely).
If you search Android Wifi Constantly Downloading, you will find results from people who have this issue. Some people say its sync, some its apps updating, but it is not. It is a bug with the Android kernel in how it doesn't filter multicast packets, resulting in the system staying awake and receiving packets most of the time. Some people have been able to solve it by purchasing a new router or turning off multicast on computers, but this is not an option in an enterprise location like a hospital. I have been stuck with this issue since I got my Note 2 last year.
The Note 3 exacerbates this problem even more because the processor low power states are not as efficient as the Note 2's. On the Note 3 I lose 12-15% per hour idle, on Airplane Mode with Wifi on. I did a test on my Note 2 and in 1 day and 7 hours of complete idle, radios off, and wifi on the battery drained fully.
Normally I carry my phone and a 9000mAH external battery. It takes the entire phone's battery and 80% of the external to get through a normal day. Last week, with the major ice storm, power was out for days and I was stuck at work. Generators provided only power to essential services, so my phone was dead days before the power was back. I do have UL data but Verizon's signal does not penetrate at all. I am tired of worrying about battery and if something like this happens again, I will be out of luck. No iOS devices have this issue and as a result I will be switching, keeping my Note 3 only for rare travel use.
This is a thread for reference: http://forum.xda-developers.com/showthread.php?t=1738171&page=6. Every Android 4.0+ device I have ever encountered (S3, S4, Nexus 4, Nexus 5 [drains even faster], Note 2, Razr, etc.) has this issue (why I want Google to solve it) but it can be solved with kernel mods (why I want Samsung's attention) as it was on the GNex in franco's kernel.
changt34x said:
Does anyone know of the best way to get serious technical attention from Google or Samsung? To put how serious this is (not to start a flame war), I will be purchasing an iPhone 5S on Monday and never another Android device unless either they solve this issue or I get another job (I LOVE my job, so unlikely).
If you search Android Wifi Constantly Downloading, you will find results from people who have this issue. Some people say its sync, some its apps updating, but it is not. It is a bug with the Android kernel in how it doesn't filter multicast packets, resulting in the system staying awake and receiving packets most of the time. Some people have been able to solve it by purchasing a new router or turning off multicast on computers, but this is not an option in an enterprise location like a hospital. I have been stuck with this issue since I got my Note 2 last year.
The Note 3 exacerbates this problem even more because the processor low power states are not as efficient as the Note 2's. On the Note 3 I lose 12-15% per hour idle, on Airplane Mode with Wifi on. I did a test on my Note 2 and in 1 day and 7 hours of complete idle, radios off, and wifi on the battery drained fully.
Normally I carry my phone and a 9000mAH external battery. It takes the entire phone's battery and 80% of the external to get through a normal day. Last week, with the major ice storm, power was out for days and I was stuck at work. Generators provided only power to essential services, so my phone was dead days before the power was back. I do have UL data but Verizon's signal does not penetrate at all. I am tired of worrying about battery and if something like this happens again, I will be out of luck. No iOS devices have this issue and as a result I will be switching, keeping my Note 3 only for rare travel use.
This is a thread for reference: http://forum.xda-developers.com/showthread.php?t=1738171&page=6. Every Android 4.0+ device I have ever encountered (S3, S4, Nexus 4, Nexus 5 [drains even faster], Note 2, Razr, etc.) has this issue (why I want Google to solve it) but it can be solved with kernel mods (why I want Samsung's attention) as it was on the GNex in franco's kernel.
Click to expand...
Click to collapse
Have you seen this?
http://www.amazon.com/dp/B0047E0EII/ref=cm_sw_r_udp_awd_6Fxatb0KT9CDC
Sent from my SM-N900V using Tapatalk
changt34x said:
Does anyone know of the best way to get serious technical attention from Google or Samsung? To put how serious this is (not to start a flame war), I will be purchasing an iPhone 5S on Monday and never another Android device unless either they solve this issue or I get another job (I LOVE my job, so unlikely).
If you search Android Wifi Constantly Downloading, you will find results from people who have this issue. Some people say its sync, some its apps updating, but it is not. It is a bug with the Android kernel in how it doesn't filter multicast packets, resulting in the system staying awake and receiving packets most of the time. Some people have been able to solve it by purchasing a new router or turning off multicast on computers, but this is not an option in an enterprise location like a hospital. I have been stuck with this issue since I got my Note 2 last year.
The Note 3 exacerbates this problem even more because the processor low power states are not as efficient as the Note 2's. On the Note 3 I lose 12-15% per hour idle, on Airplane Mode with Wifi on. I did a test on my Note 2 and in 1 day and 7 hours of complete idle, radios off, and wifi on the battery drained fully.
Normally I carry my phone and a 9000mAH external battery. It takes the entire phone's battery and 80% of the external to get through a normal day. Last week, with the major ice storm, power was out for days and I was stuck at work. Generators provided only power to essential services, so my phone was dead days before the power was back. I do have UL data but Verizon's signal does not penetrate at all. I am tired of worrying about battery and if something like this happens again, I will be out of luck. No iOS devices have this issue and as a result I will be switching, keeping my Note 3 only for rare travel use.
This is a thread for reference: http://forum.xda-developers.com/showthread.php?t=1738171&page=6. Every Android 4.0+ device I have ever encountered (S3, S4, Nexus 4, Nexus 5 [drains even faster], Note 2, Razr, etc.) has this issue (why I want Google to solve it) but it can be solved with kernel mods (why I want Samsung's attention) as it was on the GNex in franco's kernel.
Click to expand...
Click to collapse
If you are sleeping and your Samsung phone melts and catches your pillow on fire, and then you take pictures and post it on Reddit, you will probably get the attention of someone at Samsung.
Other than that, if you are worried about what your phone is doing with the data it is downloading, you can go to Settings > Data Usage and see what apps are using data and how much in whatever time frame you would like. If an app is using too much data, turn off its sync in account settings and disable notifications from within the app. If you are concerned that your phone is using data that it is not telling you about, set up a packet sniffer and see what's going on. Be sure to let us know what you find!
Wile i don't know how to answer your question, you may want to try giving yourself a static IP address at your work and see if the helps with the broadcast battery drain.
adoublearonn said:
If you are sleeping and your Samsung phone melts and catches your pillow on fire, and then you take pictures and post it on Reddit, you will probably get the attention of someone at Samsung.
Other than that, if you are worried about what your phone is doing with the data it is downloading, you can go to Settings > Data Usage and see what apps are using data and how much in whatever time frame you would like. If an app is using too much data, turn off its sync in account settings and disable notifications from within the app. If you are concerned that your phone is using data that it is not telling you about, set up a packet sniffer and see what's going on. Be sure to let us know what you find!
Click to expand...
Click to collapse
Exactly what I figured, but I would rather not burn the apartment down yet. I have done packet analysis and it is the Android kernel. All sources of packets are from local IP addresses on the same enterprise network. No way to stop data from that so far, too bad the obvious solution of using android firewall and blocking kernel from all networks doesn't work.
pdtp said:
Wile i don't know how to answer your question, you may want to try giving yourself a static IP address at your work and see if the helps with the broadcast battery drain.
Click to expand...
Click to collapse
Thank you for trying to provide a solution, but I have tried that before and it doesn't work.
Just like the poster on the other thread said, probably will never get fixed. Well, until Android 5 or 6 comes out. Check out my incredible battery life of 8 seconds screen on, airplane mode, sync off, and wifi on below.
{
"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"
}
You know you might want to talk to your IT department at work, they may not be aware that they have so much broadcast traffic going on & they may have an Android device with the same issue. I'm the system administrator at a hospital and have completed special requests for people with phone issue, esp ones that cause me issues.
pdtp said:
You know you might want to talk to your IT department at work, they may not be aware that they have so much broadcast traffic going on & they may have an Android device with the same issue. I'm the system administrator at a hospital and have completed special requests for people with phone issue, esp ones that cause me issues.
Click to expand...
Click to collapse
I have had a case going on with them for 4 months, but unfortunately it requires changes to a large number of the systems and networking equipment, so it is unlikely to be fixed until we revamp connections to our research facility in 2015. Glad you have been able to help out others in your position though. I would still hope for Google to solve this as the user shouldn't have to change things on the network side when other client devices have no issue.
Something seems a bit odd here, which is:
(3200 mA-hr + 0.8*9000 mA-hr) * (1 A / 1000 mA) * ~3.8 V ~= 39.5 Watt-hrs
Put another way, over a "day" of 12 hours, that's well north of a continuous power dissipation of 3 W.
That is abnormal power dissipation for a phone which is merely awake (not staying in deep sleep) but doing little. That's "screen-on, active game playing on multiple cores at max clock" kind of power usage territory.
Last night I set up a IPv4 multicast sender/receiver pair (with "mint" using two different nodes) on a 802.11g wlan (80 pps @512 bytes -> ~40 kBs), put my N3 in airplane mode, and then connected it to the same WiFi network. In 3 hrs I saw the battery drop only 2%. That seems a bit higher than it should be, but nowhere near the horrid 15-20%/hr you are reporting.
The latter point doesn't prove to much, other than it can be difficult to replicate pathological behaviors that are uncommon.
I believe you are experiencing what you report; but are you sure that it is not merely a case of defective hardware?
Also - you didn't mention: does your phone have installed on it an app which registers for a particular multicast group? (And also - is this IPv4 or IPv6 multicast?)
.
bftb0 said:
Something seems a bit odd here, which is:
(3200 mA-hr + 0.8*9000 mA-hr) * (1 A / 1000 mA) * ~3.8 V ~= 39.5 Watt-hrs
Put another way, over a "day" of 12 hours, that's well north of a continuous power dissipation of 3 W.
That is abnormal power dissipation for a phone which is merely awake (not staying in deep sleep) but doing little. That's "screen-on, active game playing on multiple cores at max clock" kind of power usage territory.
Last night I set up a IPv4 multicast sender/receiver pair (with "mint" using two different nodes) on a 802.11g wlan (80 pps @512 bytes -> ~40 kBs), put my N3 in airplane mode, and then connected it to the same WiFi network. In 3 hrs I saw the battery drop only 2%. That seems a bit higher than it should be, but nowhere near the horrid 15-20%/hr you are reporting.
The latter point doesn't prove to much, other than it can be difficult to replicate pathological behaviors that are uncommon.
I believe you are experiencing what you report; but are you sure that it is not merely a case of defective hardware?
Also - you didn't mention: does your phone have installed on it an app which registers for a particular multicast group? (And also - is this IPv4 or IPv6 multicast?)
.
Click to expand...
Click to collapse
Thank you very much for your insight. I am 90%+ sure that it is not a hardware problem because I have epic standby time when connected to LTE only (1% drain every few hours) or my own wireless network (Netgear WNDR3700, obviously not available at work). This also occurs on my Nexus 5 (man that thing drained fast, but don't have it with me anymore to test), Note 2, and others' S4s and G2s. Surprisingly, it doesn't happen on my 2.3 Droid Inc. I don't have an incredible number of data points because everyone has an iPhone 5 or 5S, but its 100% for all Android devices I know here.
I have a screenshot of Network Log (sorry, accidentally made some stray marks when covering up the IP). All of the packets are generally from all those local IP addresses. There are an incredible number of them, likely over a thousand. They come from that 238 subnet, other subnets, and sometimes from different ports on the same IP. The bandwidth fluctuates, but I would say averages around 3-4Mbps.
I'm not sure if I have any app that registers for a multicast, but I am running CleanROM with all Samsung Hub/AllCast/Share stuff disabled and just productivity apps. I assume this is an IPv4 multicast judging by the IP addresses.
View attachment 2589419
I ran a different multicast experiment yesterday.
I moved both the multicast source and the receiver so that they were both on the the same WiFi segment (with the N3 connected to the same AP/SSID). I did this mostly to try to pump up the traffic rate. (The way I did it in the first trial, the sender was on one subnet, and multicasts had to traverse *two* ancient routers to get to the receiver along a wired path. I was having a significant throughput issues of unknown origin - maybe because the sender was in a VM, or maybe because "mint" sends all it's packets per second in an immediate burst instead of pacing them). In that trial, I couldn't do much better than 40 kbps.
The best I could do with both sender/receiver on the same WiFi segment was with the sender emitting about 1 Mbit/sec of traffic, and the receiver successfully getting about 0.7 Mbit/sec of multicast traffic. So anyway, this meant that the N3 would be sitting there (passively) listening to about 1.7 Mbit/sec of radio traffic most all of which was multicast.
I ran this way for about 3 hours, and the N3 lost 6% of battery (Airplane mode, but WiFi on) - 2%/hr. That is substantially more than when my home WiFi network is quiet, but still nowhere as bad as you are seeing. I also had a WiFi-only Nexus 7 tab sitting there the same way, and it lost a similar amount of battery. I didn't see any evidence that the N3 was "staying awake" at that time.
So, I don't know what to make of it. It sounds sort of reasonable, but the question is - why 3 watts of power dissipation? (For comparison, the PA - Power Amplifier - chips at the front end of cell radio transmitters are usually spec'ed to max out around 2W - and everybody knows how fast a cell phone will drain if it is left on in a zero-service area, or how much shorter "talk time" is than standby time - and your device seems to be using even more power than that!) I certainly believe you are experiencing exactly the symptoms that you describe. But it also does sort of sound like it is something a bit more subtle than just simply "is multicast in use?" - probably it is also something specific about the way your employer's network is utilized or configured or the exact nature of the traffic in use. (Some protocols are incredibly noisy when it comes to broadcasts - the old Novell netware comes to mind)
In IPv4 multicast the destination MAC address can be either individual hosts' MACs or a MAC constructed from a IANA prefix plus a slightly-ambiguous mapping of the IPv4 group multicast address. Interestingly, the Wikipedia page for "IP multicast" makes this comment:
If two hosts on the same subnet each subscribe to a different multicast group whose address differs only in the first 5 bits, Ethernet packets for both multicast groups will be delivered to both hosts, requiring the network software in the hosts to discard the unrequired packets.
Click to expand...
Click to collapse
and then goes on to describe circumstances (dumb switches or dumb routers that don't understand IGMP) how multicast can lead to traffic flooding.
I asked about an App on your phone because there was the possibility that you were using a BYOD device with an institution-supplied App (that might be a multicast receiver).
Anyway, I can't help you get Samsung/Google's attention; about the only way I know that I can help personally is the following: I recently built tcpdump for ARM (tcpdump-4.5.1 plus libpcap-1.5.2) - I can provide it for you via PM if you want a copy (let me know). You'll have to run it from a terminal emulator (as root I suppose). But by doing that, you can capture the output to a file (tcpdump -i wlan0 -s 1600 -w packet_logfile.pkts) and then move that file afterwards to a honest-to-goodness computer and look at the packet capture using Wireshark. I tried this last night with a small sample, and it seems to work correctly. (In my experience, trying to use a Android device for reviewing massive amounts of data - like packet logs - is a horrible experience; you can't see the forest for the trees.)
Note: I don't know if the WiFi radio in the N3 can be operated in "monitor" mode... meaning that you might only see traffic that the radio is collecting based on it's own MAC plus however it deals with multicast... but that latter condition might just be exactly what you need to figure out what exactly is going on.
$.02
Related
- turn off 3G
phone screen > ##778 > "000000" > modem settings >
preferred mode- should be on auto as default, switch it to cdma only
menu > commit settings > (auto reboots)
poof 1x only mode!!!
(much slower data speed but much smaller data authentaction overhead - hence less power usage, good for low signal or good signal with fringe 3g coverage)
also be careful what you change in the settings, one of the modes will give you data only and no voice call(+sms) ability
- also "rev A." enable/disable has no reason to be off unless your network engineer so leave it on, turning it off will just limit you to evdo(3g) rev.0 vs allow both rev.A and rev.0
- dont clear your MRU, if you do you will need to hit a native verizon tower to get data to work
- preferred serving system - home/auto A/auto B
B is default and works best in roughly 90% areas, auto A looks at same preferred list but starts in reverse order before goign to none preferred towers, sometimes phones gets confused between two preferred towers and grabs one with lower signal or just switched to much, occasional it might help to tell the phone to start searching for ID's in reverse order, this is little over simplified and prl's contain signal frequencies as well which is more of what a/b switch will look to, but thats the way i like to explain it so tough cookie
also if your ambitious and your phone keeps jumping between good 3g signal and tower with poor coverage or data, you could grab the sID's of the tower with good connection and put phone in home only mode and alter the nam settings home sid to match that, also your allowed to enter more than one sid in the settings if you wanted to build a mini prl list of sorts
warning:-altering home sid will give roam indicator false info and roaming will still be network side regardless of what miss programed phone shows
also if you put prl files on root of sd card you can also update prl from a file
Prove the lower power usage.
Lino. said:
Prove the lower power usage.
Click to expand...
Click to collapse
i'll skip how signal strength effects radios power output and B band penetrates buildings better in general and alot of boring electromagnetic theory
i'm guessing your referring to the 1x mode vs 3g/1x mode(3g/2g), if its not let me know
it was my assumption that it is general knowledge and accepted that evdo has alot higher power usage just maintaining network authentication with no data transfered for user purposes, it takes longer to acquire a 3g aka EV signal signal when booting phone or when its recovering from lost signal, the network packet overhead is larger between the phone and the cell tower, just like analog or cable modem has MTU that is basically the available space - used for network = info space, now imagine you had OCD and had to call your VM once ever min to make sure it didn't get deleted or someone change your password to check your messages, now say 1x would be listening just to make sure the greeting starts for maybe 10 seconds and your 3g would listen to say 30 seconds of the greeting before being satisfied the vm hasn't been lost or hacked, obviously the person broadcasting an open cell channel for less time will be able to use phone longer without charging, now these are made up numbers for illustration purposes and the authentication process takes fraction of a second, but it is done continuously over and over as long as the 3G icon is showing on the top of the phone
now actions speak louder than words and i would be more than happy to make some real world test to give you hard evidence and if this is what you want then you will have to wait because i'm changing alot of the apps on my phone and my usages is not consistent enough for test atm but i'll happily make one if you wait for my usage to settle down, now if someone wants to send me second htc incredible i'd happily make time dilated web video and post it to youtube so everyone can see first hand evidence of power difference
now if you are impatient and want proof right this second without a propper test conducted i can refer you to google but on more serious note the EVDO effect on moto razor is well know and modes have been done to edit, also the battery life of the v3a and v3m are very different, the largest difference in these two razors is one is evdo capable and the other is not, also cases have been documented of v3m users having less than half the battery life they had before after the EV icon starts showing up on the screen related directly to cell tower upgrade in the area they use the phone
now i know this is alot of nothing about the razor but it was very common phone, i have altered the data on lg wave, glimmer, htc touch diamond and few blackberrys and noticed power differences on all of them, its just the way modern cdma phones work and its effect is magnifed by lower signal levels, people that live few feet from cell towers will notice least difference while thous with 1 bar of coverage or around the -90 dbm or lower range will notice greatly magnified effects of this inefficient with data authentication process
seriously thou, anyone want to send me a second phone! lol
-----
couple googled links for you
http://www.hacktherazr.com/guides/verizon.disable.evdo.php
http://www.wikihow.com/Extend-the-Battery-Life-of-Your-Verizon-Wireless-RAZR
runkittyrun said:
seriously thou, anyone want to send me a second phone! lol
-----
couple googled links for you
http://www.hacktherazr.com/guides/verizon.disable.evdo.php
http://www.wikihow.com/Extend-the-Battery-Life-of-Your-Verizon-Wireless-RAZR
Click to expand...
Click to collapse
Thats pretty good, but good luck with this one.
Coming from a G1 I was not expecting anything better on the battery for this phone, we get a phone like this because of it's features and everyone should know that features like this phone has are going to consume more power.
If battery is a persons problem and they will always complain about it, then they should not have a smartphone.
Also chargers are cheap.
I wander with the same amount of use, 2 identical phones one running 3G the other running slower, what would be the difference and how could this be done, the phone with 3G would be waiting on the other to load a webpage 90% of the time.
Sorry I left T-Mobile because of their lack of 3G service, I'll be dammed if I put my phone back to Edge speeds.
Lino. said:
If battery is a persons problem and they will always complain about it, then they should not have a smartphone.
Also chargers are cheap.
I wander with the same amount of use, 2 identical phones one running 3G the other running slower, what would be the difference and how could this be done, the phone with 3G would be waiting on the other to load a webpage 90% of the time.
Sorry I left T-Mobile because of their lack of 3G service, I'll be dammed if I put my phone back to Edge speeds.
Click to expand...
Click to collapse
this definitely is not targeted for normal use
this is more for the person that cant make it threw 5 hours with the phone idle the whole time, if you want to start larger amount of data then switch it back and wait 40 seconds?? for reboot
2g will load web pages and email and all other data, except view vcast videos and thats blocked on network side, also voice chat programs like skype would take quality hit do to smaller bandwidth, if you used two phones in active data sessions the 3G would quickly become more efficient as session size and length increased, like you said it would finish loading larger websites and videos while 2g is still broadcasting an active session working on transferring the info, but if you set two phones with same apps on them in same place with one in 1x and other evdo and watched them in standby mode the 1x will have longer battery, now ideally if your going somewhere with low signal it is much easier to turn off all data threw normal menu and will give you even better battery but no emails updates or other data
I live in a poor Verizon signal area. Every phone I have ever had gets easy better batt life when set to 1x only so thanks for this tip.
Any easy to automate this with a macro or widget somehow?
lexluthor said:
I live in a poor Verizon signal area. Every phone I have ever had gets easy better batt life when set to 1x only so thanks for this tip.
Any easy to automate this with a macro or widget somehow?
Click to expand...
Click to collapse
thanks, makes my post all worth while
would be a sweet widget if you could change the phone mode on the fly dont know enough about the android system to know if its possible, but maybe someone can look at the phone settings and make customized epst program and make widget just for this setting without the programing forcing a reboot, have seen some phone that can change nam programing without reboot but most phone do it automatically so be interesting to see if changed without a reset if it takes effect or not, hmm or even epst mod at commmit to bring up reboot yes/no instead force reboot on commit would work then we know widget should be possible
What it the point in having a top of the line media phone if you are going to cramp it's style by limiting it's functions. If you "need" this top of the line phone you should be able to pony up for an extra batt. The Incredible is a COMPUTER you talk on. Can your laptop last all day with heavy use unplugged ? ? NO.
I plug my phone in at work and in the car. I also keep an extra batt in my briefcase for out of the office emergencies. These are not flip phones that last all day. I have been using media phones since they came out and they have yet to make one that will last all day using all the features like you want to.
Why restrict what the phone can do , when all you need is an extra batt.
jbh00jh said:
What it the point in having a top of the line media phone if you are going to cramp it's style by limiting it's functions. If you "need" this top of the line phone you should be able to pony up for an extra batt. The Incredible is a COMPUTER you talk on. Can your laptop last all day with heavy use unplugged ? ? NO.
I plug my phone in at work and in the car. I also keep an extra batt in my briefcase for out of the office emergencies. These are not flip phones that last all day. I have been using media phones since they came out and they have yet to make one that will last all day using all the features like you want to.
Why restrict what the phone can do , when all you need is an extra batt.
Click to expand...
Click to collapse
your right, why dont we all carry around backpacks or napsacks with batterys and portable charges and spare parts for our smartphone, batterys are cheap
and people should not be allowed to buy tv screens over 32" if they can't show proof of owning blu-ray player, i mean come on, no top line device unless your gonna use it to best potienal, and in reality they are just making large screens more expensive for thou that do have blu-ray, yep, no big screens for people with dvd's and stander cable
OMFG!
why are people so quick to force their frame of reality on to everyone, is their a Hitler award i dont know about?
i get that smartphones are computers first and phones second, but that doesn't mean everyone using one has the same needs, some people need the phone part of the smartphone to, well actually work, i know what a strang concept why dont they just get an old bag phone, better signal, better battery life, and you can get them with shoulder straps!
android is about ability to customize our phones, why? because we all use them differently so you can change your home screens, pick the apps you download, the experience is aimed at being user driven
your example laptop is way off base, what you should be saying is if your laptop is full charged and its completely off or in a hibernate mode for 2-5 hours can you even at that point turn it on? that is what this post is about, not the time your using the smartphone but the time that its self-destructing between uses
look, i admit this is not for everyone, infact for 90+% i would recommend not even trying this, but the point is some people are effected by this and shouldn't they at least have the option or ability for this? there was post requesting this before i even brought it up
do you know how many people i've talked to over 80 that have smartphones these days, now i'm not saying these should have them or that it wasn't incredibly frustrating talking to them and i didn't want to bang my head on wall saying why did someone sell this person a smartphone we should have test to who can buy smartphones, if you cant figure out how to turn it on by yourself you cant' buy one! but the reality is smartphones are becoming mainstream
- why would anyone need top line media phone and then cramp it?
> because they dont use their smartphone the same way you use smartphone
i.e. my father runs poker tournament for a large company and bigger events are normal held at casinos, i dont know if you been to poker tournament lately but they are long events, also most casinos are bad on cell signal, partly cause of the building and partly cause they have areas with signal equipment that interferes, he also needs to have his email on the device because he's general contractor and works with larger companies that demand a quick response, now one could suggest blackberry in this case as of smartphones they in most cases do better with battery life, but honestly at the rate android apps are growing and how much for fun and enjoyment i get from it i cant dream of not recommending a android phone to him, now their is one degree of separation that shows an example where this is useful, and i could go on all day long with completely different examples where this is helpful
can we all agree to disagree about how people are stupid people are to modify how their phone functions? and try to keep to subject of re-enforcing this works or providing examples that contradict this, or question to how it works or expands on its helpfulness
jbh00jh said:
What it the point in having a top of the line media phone if you are going to cramp it's style by limiting it's functions. If you "need" this top of the line phone you should be able to pony up for an extra batt. The Incredible is a COMPUTER you talk on. Can your laptop last all day with heavy use unplugged ? ? NO.
Why restrict what the phone can do , when all you need is an extra batt.
Click to expand...
Click to collapse
I hear you on all of that and I fully understand what I have. I just came from a Touch Pro and, I'll tell you, battery was probably good for 14-16 hours if set to 1x and 10 hours on 3G. That a huge difference.
I'm on Wifi both at home and work and use Opera Mini, which works very well on 1x, plus I had a pretty quick way to go from 3G to 1x and back. It didn't limit me *that* much, but sure, there were plenty of times I needed to check something fast, wasn't near wifi and didn't want to use my macro to change to 3G and back. Yes, it's a bit of a pain.
Plus, I barely get a 3G signal in my house anyhow. It's 1x 75% of the time.
Now that I have my incredible, which does even so much more than the Touch Pro, yes, I'd like to keep it to 3G and I have chargers everywhere and an extra battery and might get an external battery charger too.
Still, I'd love to see an app or widget that can quickly set the phone to 1x mode and back.
runkittyrun said:
your right, why dont we all carry around backpacks or napsacks with batterys and portable charges and spare parts for our smartphone, batterys are cheap
and people should not be allowed to buy tv screens over 32" if they can't show proof of owning blu-ray player, i mean come on, no top line device unless your gonna use it to best potienal, and in reality they are just making large screens more expensive for thou that do have blu-ray, yep, no big screens for people with dvd's and stander cable
OMFG!
why are people so quick to force their frame of reality on to everyone, is their a Hitler award i dont know about?
i get that smartphones are computers first and phones second, but that doesn't mean everyone using one has the same needs, some people need the phone part of the smartphone to, well actually work, i know what a strang concept why dont they just get an old bag phone, better signal, better battery life, and you can get them with shoulder straps!
android is about ability to customize our phones, why? because we all use them differently so you can change your home screens, pick the apps you download, the experience is aimed at being user driven
your example laptop is way off base, what you should be saying is if your laptop is full charged and its completely off or in a hibernate mode for 2-5 hours can you even at that point turn it on? that is what this post is about, not the time your using the smartphone but the time that its self-destructing between uses
look, i admit this is not for everyone, infact for 90+% i would recommend not even trying this, but the point is some people are effected by this and shouldn't they at least have the option or ability for this? there was post requesting this before i even brought it up
do you know how many people i've talked to over 80 that have smartphones these days, now i'm not saying these should have them or that it wasn't incredibly frustrating talking to them and i didn't want to bang my head on wall saying why did someone sell this person a smartphone we should have test to who can buy smartphones, if you cant figure out how to turn it on by yourself you cant' buy one! but the reality is smartphones are becoming mainstream
- why would anyone need top line media phone and then cramp it?
> because they dont use their smartphone the same way you use smartphone
i.e. my father runs poker tournament for a large company and bigger events are normal held at casinos, i dont know if you been to poker tournament lately but they are long events, also most casinos are bad on cell signal, partly cause of the building and partly cause they have areas with signal equipment that interferes, he also needs to have his email on the device because he's general contractor and works with larger companies that demand a quick response, now one could suggest blackberry in this case as of smartphones they in most cases do better with battery life, but honestly at the rate android apps are growing and how much for fun and enjoyment i get from it i cant dream of not recommending a android phone to him, now their is one degree of separation that shows an example where this is useful, and i could go on all day long with completely different examples where this is helpful
can we all agree to disagree about how people are stupid people are to modify how their phone functions? and try to keep to subject of re-enforcing this works or providing examples that contradict this, or question to how it works or expands on its helpfulness
Click to expand...
Click to collapse
Why would someone need a backpack to carry a 2oz, battery ?
The more I read on this tread the more I understand.
That was an option on my G1 to turn off 3G, I never did, I hardly had 3G with T-mobile.
Anyway you can turn off Mobile network on the fly, you can also put the phone in airplane mode, but both of these you will have to internet, also you could turn off Auto Sync, or turn the phone OFF for best battery life.
[Complete rewrite 26/10]
I'm writing this since the abundant misinformation about it coming across many many threads, and all other Android OS threads are too big and real information is easy to overlook.
After several weeks of analyzing and monitoring of the behavior of the device, things are starting to clear up and we can come to a conclusion.
What's the Android OS usage?
Many have noticed that on our Galaxy S2's and various other variations (Epic 4G Touch, etc) that in the Android battery stats the Android OS entry is supposedly eating away a large percentage of the battery used.
{
"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"
}
There's been many threads old and new discussing it and theorizing and many users magically fixing it by doing god knows what changes.
The Android OS package is a bundle of processes, in this case, all root processes used by the system kernel. Please remember this when continuing to read on, as there is much more to it than meets the eye and only once specific aspect of the whole story will be treated.
A diagnosis of the main problem:
Download [APP] BetterBatteryStats adds battery history back to Gingerbread. It is your #1 friend on finding out what uses up CPU power and causes problems.
Note: The CPU time in BetterBatteryStats is normalized, meaning 100% load during full frequency for a minute will show up as 1 minute CPU time, 100% load at half-frequency for a minute will show 30 seconds CPU time. Keep this in mind when monitoring processes. The CPU time shown in the Android battery stats is useless.
As you can see in the screenshot, "suspend" and "events/0" pop up as the big consumers of CPU power. Red means it's a system/kernel process and blue means it's a user process.
The suspend process is the program that's in charge of telling the hardware to go into deep sleep mode and reawaken from it.
The events/0 is just the general events manager for the system kernel.
You can monitor this with Watchdog Task Manager. Set it up so that it monitors system processes and raises notifications. Depending on the severity of the bug at the time and some black magic, you'll see the 99% load on the system.
Due to how the hardware of the phone is designed, the default kernel settings of the phone lock its frequency to 800MHz before falling into deep sleep. This is believed to be one of the main problems as to why so much battery is drained. Compared to other the devices the Exynos 4210 in our Galaxy S2's takes a much longer time to enter deep sleep (suspend) and wake up again from sleep (resume). This can be seen in the device message logs:
<6>[ 749.242666] PM: suspend of devices complete after 171.413 msecs
<6>[ 749.250855] PM: late suspend of devices complete after 0.396 msecs
<4>[ 749.250864] Disabling non-boot CPUs ...
<7>[ 749.250909] s3c_pm_enter(3)
<7>[ 749.250916] s3c_sleep_save_phys=0x40d9fe80
<7>[ 749.250959] sleep: irq wakeup masks: 000fffdd,cb37b97f
<6>[ 0.000000] WAKEUP_STAT: 0x80000001
<6>[ 0.000000] WAKUP_INT0_PEND: 0x80
<6>[ 0.000000] WAKUP_INT1_PEND: 0x0
<6>[ 0.000000] WAKUP_INT2_PEND: 0x0
<6>[ 0.000000] WAKUP_INT3_PEND: 0x0
<7>[ 0.000000] s3c_pm_enter: post sleep, preparing to return
<7>[ 0.000000] S3C PM Resume (post-restore)
<7>[ 0.000000] Wakeup from sleep, 0x80000001
<6>[ 0.000000] L310 cache controller enabled
<6>[ 0.000000] l2x0: 16 ways, CACHE_ID 0x4100c4c5, AUX_CTRL 0x7e470001, Cache Size: 1048576 B
<6>[ 749.251252] PM: early resume of devices complete after 0.255 msecs
..
..
<6>[ 749.748189] PM: resume of devices complete after 496.599 msecsThe fact that these operations are done at a higher frequency, together with the fact that a suspend-wake cycle takes around anything from 0.6 to 0.8 seconds, while doing nothing else, will drain more power than actually needed.
The screenshot on the right is a period of 15 minutes where the processes were bugged, the timers in CPU Spy were reset, and the screen immediately turned off to collect the statistics. A screen-off profile was used to limit the maximum frequency to 200MHz, so theoretically any standard process is not allowed to use any of the frequency-states above that. Nevertheless, There you can see the device being in the 800MHz state for roughly half the time. This means that half the time the device is spending on being awake is being wasted on just entering and leaving the deep sleep state.
Note: The deep sleep state is a state in which the CPU isn't clocked anymore and caches are no longer kept coherent, basically it's turning off most of the CPU, and thus conserving a lot of power.
What's the cause of high Android OS usage?
This is where things get interesting.
Network usage
The most common cause of the device waking up often enough to cause a problem and raise the suspend process up, and thus also the AOS usage, are incoming and outgoing network traffic. These will be attributed to the operating system rather than the service or application at cause of the problem.
Wild wakelocks
Second most common cause are high-frequency wakelocks caused by some application or service. Refer to the next section for this topic.
Incorrect statistical interpretation
One has to keep in mind that when generating the percentages shown under the battery stats in Android, that those values are just an estimate. The ROM has a file called power_profile.xml in which power drain values for different uses are listed. These values are coming from Samsung. For example, the CPU running at 1200MHz is listed as using 577mAh of power, so when a task is running for 10 seconds at 1200MHz, then it means that that process will be getting attributed a power consumption of 1602µAh (577mAh/3600s *10s). ASOP ROMs like MIUI will actually list these values in the battery stats. Each entry in the battery usage as such has an estimated power consumption value, and out of which the percentages are calculated from.
The problem is, that these are all just estimates and wether they are calculated correctly is up to debate. There are issues if either dual core use is taken into account in these estimates, or not, and even if the values provided by power_profile.xml are representative of real use or not. One issue for certain is that power consumption will be wrong for people who underclock/overclock, and undervolting. There are no entries for states above 1200MHz or below 200MHz, and the ones already present are meant to be representative of default/stock voltages. If you're running 100MHz in idle, the system will use the 200MHz estimates and thus overestimate your power consumption, if you're overclocking and using 1400MHz for example, the system will underestimate your power consumption.
This part is also what causes kernels which claim to fix the problem to be nothing but red herrings: somewhere in the patching of the kernels to 2.6.35.12 there is a change which makes the whole suspend and wakeup process no longer visible to the system and thus is no longer registered. Because of that, there are no statistics of these and the drain can not be calculated. Tests have shown that this is nothing other than just hiding of the problem rather than a tangible fix.
What you can do:
First of all you need to find the cause of the problem; study your wakelocks. You can do this by using BBS as mentioned above but this will only show part of the story as it will not tell you about system wakelocks, but only user wakelocks. If there is no obvious villain listed there, then you must do some more advanced troubleshooting:
Dump your wakelocks file using a terminal or over ADB if you are familiar with it, as follows:
cat /proc/wakelocks > /sdcard/wakelocks.csvTo read this data you need to import it into a spreadsheet application like Excel or OpenOffice and you'll end up getting something like this: (Read the thread around here on how to format your spreadsheet)
You need to mainly look for high-duration wakelocks, and the wake_count frequency, meaning how often your device has woken up.
While this is all a bit advanced and all, you can do it simpler:
Avoid using application and services that use a permanent internet connections. Avoid using applications which use polling for their connectivity and instead use those who support C2DM push-notifications. This will vastly increase your battery life by vastly decreasing network traffic. If this all doesn't help, try doing a network analysis (packet capture) to inspect the source of it, please refer to discussions later in the thread for this.
What your device can be capable of:
In the first screenshot you can see two periods of around 18 hours where the battery drain is relatively flat. In this period the suspend process gained merely a few seconds of CPU time. Then I use the phone for a bit, it goes haywire, and then calms down again and then starts draining again. You can see this in the step-wise drain in the curve. It should be smooth and not like that.
In the second screenshot it's after a full charge where it didn't trigger for 8 hours. My battery is perfectly calibrated so those are real 4% of battery. So if things were to go smoothly on the software part then the phone is idling at around 0.4% of battery per hour on Wifi, and other people have been reporting down to 0.8% or even less with a good 3G signal.
Left side: low network usage, how it should be; Right side: high network usage, how it behaves sometimes in severe cases.
Same network, same location, same signal strength, same ROM (Changing my font maybe fixed it....) , same wakelocks between them, same background apps running. Not even 5 minutes screen time on the two. The only difference with .14 patched kernels I'm experiencing is that it's not showing up anymore in the stats, but it drains just as much as in the right screen, showing the same CPU state behavior. It's also happening less often, and many say it's not happening at all anymore, but how would they know it it's hidden now?
"tvout resume wo"
One might have noticed the high usage of the "tvout resume wo" (wo = work, btw) in BetterBatteryStats. This is part of the TVOut functionality/driver, and it seems that every time the CPU resumes it goes through this work wether you use TVOut or not. Due it being a kernel process it's also part of adding up to the Android OS package usage. If you are suffering from high frequency wakeups, then this will also go up as system routines for this functionality are called every time the device wakes up.
<6>[ 749.251252] PM: early resume of devices complete after 0.255 msecs
<3>[ 749.251350] [MHL]mhl_int_irq_handler() is called
Last words
The device is still superb. Even with this bug the battery is equivalent to many other high-end devices out there. The thing is, it could be much better. If you want to squeeze out most of your device read on the discussions in this thread to try to find out what's keeping the phone from wasting power. Forward this to people so they're informed and aware of it.
I really appreciate all the effort you've put into researching this!
AndreiLux said:
Summarized quick-facts:
It's caused by a bug in the drivers.
Click to expand...
Click to collapse
While I certainly do believe this, what leads you to believe it is a driver issue? And what particular driver have you found is the culprit?
AndreiLux said:
We can just hope that Samsung will fix this issue soon. For all we know they're aware of it and are working on it. The original Galaxy S had this very same issue and it has been supposedly fixed in a firmware update earlier this year. The Galaxy S2 is not the only phone having this issue, but it's the one that has it guaranteed most of the time.
Click to expand...
Click to collapse
I know that the 2.3.4 update for the original GX2 was supposed to have fixed this exact bug. You're saying that it is not in fact fixed? Shouldn't Samsung be alerted to this blunder?
AndreiLux said:
What your device would be capable of.
In the first screenshot you can see two periods of around 18 hours where the battery drain is relatively flat. In this period the suspend process gained merely a few seconds of CPU time. Then I use the phone for a bit, it goes haywire, and then calms down again and then starts draining again. You can see this in the step-wise drain in the curve. It should be smooth and not like that.
In the second screenshot it's after a full charge where it didn't trigger for 8 hours. My battery is perfectly calibrated so those are real 4% of battery. So if things were to go smoothly on the software part then the phone is idling at around 0.4% of battery per hour on Wifi, and other people have been reporting down to 0.8% or even less with a good 3G signal.
Basically Android OS should not be even showing up in the battery stats, like on many other devices. Lowest people are getting on the Galaxy S2 is about 5-10%. There's also some other issues like high usage of "tvout resume wo", but that's something irrelevant compared to the elephant in the room that is "suspend" & "events/0".
Click to expand...
Click to collapse
So you're saying it was just dumb luck and you happened to not trigger the bug? So this could account for people finding "solutions," but they were only coincidental of the bug randomly not manifesting itself?
Very weell explained.
As far as the first SGS, I can confirm that the bug was solved from the first 2.3.4.
I was experiencing a fantastic battery life with my SGS, and I was quite shocked when I had to watch helpless as Android OS went up on the S2.
That was a fantastic explanation. It does explain the vast difference in AOS between my Nexus S and SGSII. Hope this thread gets pinned to help put away the vast number of AOS threads present. And hopefully it'll help get more people to star the issue and get it the attention it badly needs!
xak944 said:
While I certainly do believe this, what leads you to believe it is a driver issue? And what particular driver have you found is the culprit?
Click to expand...
Click to collapse
It's been confirmed by a Samsung person on the original Galaxy S where it had the very same issue. Which driver exactly it is, I don't know. Supposedly it was the Wifi-driver but the bug also happens to some extent without Wifi, so I don't know. If you want you're welcome to go through 120MB of kernel source code to find the issue and change it.
xak944 said:
I know that the 2.3.4 update for the original GX2 was supposed to have fixed this exact bug. You're saying that it is not in fact fixed? Shouldn't Samsung be alerted to this blunder?
Click to expand...
Click to collapse
Look. There's Android, and then there's a complete phone firmware. People tend to call firmware versions by the Android version they're on. Android version itself is completely meaningless and it's not Google's job to fix this, the manufacturers are the ones who deliver the drivers and everything that makes Android run on the phone. There's been for example about 8 leaked firmware versions for 2.3.4 on the Galaxy S2.
xak944 said:
So you're saying it was just dumb luck and you happened to not trigger the bug? So this could account for people finding "solutions," but they were only coincidental of the bug randomly not manifesting itself?
Click to expand...
Click to collapse
Yes. Go wave a dead chicken over the phone and practice voodoo magic on it and you'll be just as successful at changing the behavior. The issue goes way too deep for the user to have any reproducible impact on it.
Thanks for great explanation and having a bit more light on the issue. I'm going to star those as soon as it goes off maintenance.
Good post thanks for your research.
AndreiLux said:
It's been confirmed by a Samsung person on the original Galaxy S where it had the very same issue.
Click to expand...
Click to collapse
Was this in a support case you opened with Samsung? A forum? Where and how?
AndreiLux said:
Look. There's Android, and then there's a complete phone firmware. People tend to call firmware versions by the Android version they're on. Android version itself is completely meaningless and it's not Google's job to fix this, the manufacturers are the ones who deliver the drivers and everything that makes Android run on the phone. There's been for example about 8 leaked firmware versions for 2.3.4 on the Galaxy S2.
Click to expand...
Click to collapse
Then why are we flagging the issues on the Android project? Shouldn't we be hammering on Samsung support channels for a fix if the problem is located in their proprietary drivers?
xak944 said:
Was this in a support case you opened with Samsung? A forum? Where and how?
Click to expand...
Click to collapse
Galaxy S XDA thread ; post in question ; response by Todd who is a Google employee.
xak944 said:
Then why are we flagging the issues on the Android project? Shouldn't we be hammering on Samsung support channels for a fix if the problem is located in their proprietary drivers?
Click to expand...
Click to collapse
You're more than welcome to show me the proper non-Korean Samsung channels. You're the one who said in big bold red letters to flag it to Google. In any way, Google forwards big issues directly to the manufacturers themselves.
AndreiLux said:
Galaxy S XDA thread ; post in question ; response by Todd who is a Google employee.
Click to expand...
Click to collapse
Oh good grief. We've really gone full circle now. That entire thread claims it was fixed in 2.3.4!
AndreiLux said:
You're the one who said in big bold red letters to flag it to Google.
Click to expand...
Click to collapse
Yeah, you're right. I should've done my own research and not assumed you knew what you were talking about.
AndreiLux said:
You're more than welcome to show me the proper non-Korean Samsung channels
Click to expand...
Click to collapse
http://www.samsung.com/us/SUPPORT/
http://twitter.com/SamsungSupport
http://facebook.com/SamsungSupport
Very good post probably the best on the subject to date.
Personally running 2.3.5 i don't find it as bad but there can be no denying the problem is still there and until Samsung sort it out it will continue to be there.
xak944 said:
Oh good grief. We've really gone full circle now. That entire thread claims it was fixed in 2.3.4!
Click to expand...
Click to collapse
It was... for the Galaxy S, we're on another phone. XXJVP fixed it, not 2.3.4. I said it earlier, firmware version != Android version.
xak944 said:
http://www.samsung.com/us/SUPPORT/
http://twitter.com/SamsungSupport
http://facebook.com/SamsungSupport
Click to expand...
Click to collapse
Well I'm not that stupid and have been that far myself. The US site doesn't even let me select my model because it doesn't officially exist there, and the international site where I'm rerouted to doesn't even have a report feature and the only contact is a phone number. And I'm not going to start FB'ing or Twittering about driver issues to a mega-conglomerate coorporation, I'll leave others to do that. Hardly a "proper" tech support channel as Google Code. Only the Korean site has that, but sadly, I can't speak Korean.
Thanks for the research.
Lets all star this so we cant get it to Samsung and they can fix this ASAP.
Great post. Lots of people are talking about battery life but without understanding how the stats work and how to interpret them.
The battery usage screenshot is funny though. Yeah, I understand it shouldn't have those steep fall-offs. But still, must be pretty nice to have 40% battery left after 2.5 days!
Thanks for your explanation, I often wondered what the android os bug was and now I know. I'm quite fortunate by the sound of things my android os is usually around 15%. Is this issue likely to be resolved with ICS?
Sent from my GT-I9100 using Tapatalk
Here's what I don't get. I've had the phone since week one back in may and from may to September - no os bug. So why now? Have I done something to trigger it? Can we isolate the cause to prevent others getting it? I can list what I've done different recently to previous months if it helps?
And if it's drivers then why doesn't it access the CPU when the charger is plugged in?
I share everyone's frustration over all this.
Sent from my GT-I9100 using XDA App
We have the same problem on the US Galaxy S II/Sprint Epic 4G Touch :\
This thread should be stickied!
Shafty said:
Here's what I don't get. I've had the phone since week one back in may and from may to September - no os bug. So why now? Have I done something to trigger it? Can we isolate the cause to prevent others getting it? I can list what I've done different recently to previous months if it helps?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
I have no idea.
I've tried it on half a dozen ROMs, wiped everything clear, removed every app to the point of the ROM being pretty naked, and still didn't get to change it. There's a lot of people like you who say they don't have the bug and suddenly have it. It may be a hardware fault that doesn't trigger until some certain circumstances are fulfilled. Maybe it's just some stupid bug in the drivers and it's some synchronization problem between registers. It may be cosmic rays who change a bit in the memory. Who the **** knows.
All I know is that nobody has been able to isolate it to any common cause, and I sure haven't managed in the last 3 months, and I've had it since July myself. At the same time you ask yourself why there's such a wide variety of devices having the same issue, but different hardware. If I would be paid full time to look through the source code and find the bug then I'd do it. But until then, I just wanted to share it with everybody and just tell them to stop wasting their time.
Shafty said:
And if it's drivers then why doesn't it access the CPU when the charger is plugged in?
Click to expand...
Click to collapse
Because when the device is plugged in then a wakelock is active and the device doesn't go to deep sleep at all. Since the going to deep sleep process is what is bugging, then wakelocking it prevents it from bugging out. I mentioned this already in the post. Since you have MIUI, you can for example tell it in the battery setting to not go to deep sleep at all (there's a checkbox), and see the results for yourself.
I'll just say i got my SGS2 recently and it came with 2.3.4 - there was no AOS bug at first then oneday started noticing it. I upgraded to 2.3.5 via XXKI3 and it's better as it's "only" 11% now rather than 29-40%.
Guess i should check with CPUspy to see if the phone is actually deep sleeping - I would however assume so as it's been getting better battery life since i upgrading to 2.3.5.
Uhh, I cannot post this in development as I am still a newby :-(
However:
Hello,
I came from Symbian (Nokia C7-00) and liked the phone very much. Everything worked the way it should. (I was especially interested in office functionality.)
Now I bought a Galaxy Note and I really love the hardware.
But I discovered that it uses much energy and it doesn't like to sleep as often as it could. (I already returned to Android GB, which gives a better experience, but there still is room for improvement.)
1. Sometimes even though the phone simply lies around and does nothing, the last app that I forgot to close is hindering the CPU from sleeping. Why? The is no need.
2. At night I am used to turn the phone into flight mode. However I found out that this isn't the best thing for Android. In the morning, when the email app goes to push phase, the phone leaves sleep mode and seems to excitedly wait for the flight mode to get switched off. This uses *quite* a bit of battery!
These things seem strange to me. My impression is that Android is not really optimised for cell phones. If the screen is off, there is no need for CPU time, doesn't it? There is nothing urgent to do; everything could be done slowly; no hurry.
I guess the battery could last *much* longer if this would be improved.
Greetings,
corcov
corcovo said:
Uhh, I cannot post this in development as I am still a newby :-(
However:
Click to expand...
Click to collapse
Which is handy, because this thread has nothing to do with development and thus saved you from some abuse!
Regards,
Dave
Sent from my GT-N7000 using Tapatalk 2
But I already know how to click the "thanks" button
corcovo said:
But I already know how to click the "thanks" button
Click to expand...
Click to collapse
Doesn't matter.
Development, if you did not create IT, then it does not belong in development. Remember that. Otherwise you will get flamed.
Android is a mobile OS, so of course it is optimised for smart phones - not ordinary cell phones. Android acts like a computer and, if you keep a computer running Crysis 2 for example, it would burn more power than a computer just playing some music off of iTunes.
In terms of improving your battery, check your brightness. You can download widgets to adjust the brightness right from the home screens. I use these to set my brightness to its lowest whilst at home (perfectly adequate for night and indoor use away from sunlight) and turn it onto automatic when I go outside. This has saved my a bunch of battery.
If you are running a stock Samsung ROM, turn on power saving mode. I always leave it on and, frankly, I have no idea as to what it actually does. I haven't noticed a performance drop in the slightest, but if it saves a bit of battery it is worth it. Also, you could try Juice Defender or some other battery saving apps which work for some people - others not.
Finally, ensure you haven't left GPS, Bluetooth or WiFi on when not needed. Try downloading CPU Spy to check your phone deep sleeps, yet mine even without it ever deep sleeping gets around 16 hours of battery life which is still the best I have ever gotten on a smart phone. Bettery Battery Stats can show you wake-locks (apps that are keeping your phone active) also.
Brad387 said:
Android is a mobile OS, so of course it is optimised for smart phones - not ordinary cell phones.
Click to expand...
Click to collapse
I see. Well it might be a nice feature if one could add an "now be a cell phone"-option for energy enhancement, which means: if screen if off, sleep.
c.
corcovo said:
1. Sometimes even though the phone simply lies around and does nothing, the last app that I forgot to close is hindering the CPU from sleeping. Why? The is no need.
Click to expand...
Click to collapse
There are some legitimate needs for keeping the CPU from sleeping for a short period of time - such as finishing a sync operation (otherwise, the radio power spent beginning the sync is wasted). Unfortunately, some poorly written applications (Facebook for example) abuse the wakelock mechanisms and hold wakelocks when it is not justified.
2. At night I am used to turn the phone into flight mode. However I found out that this isn't the best thing for Android. In the morning, when the email app goes to push phase, the phone leaves sleep mode and seems to excitedly wait for the flight mode to get switched off. This uses *quite* a bit of battery!
Click to expand...
Click to collapse
This is not something I have ever encountered myself. "push" relies on the server to trigger something - in airplane mode, this trigger can't happen.
These things seem strange to me. My impression is that Android is not really optimised for cell phones. If the screen is off, there is no need for CPU time, doesn't it? There is nothing urgent to do; everything could be done slowly; no hurry.
I guess the battery could last *much* longer if this would be improved.
Greetings,
corcov
Click to expand...
Click to collapse
Android is well optimized for cell phones - However, it assumes that third-party applications follow Google's recommendations for power management. Unfortunately, many of them do not. The number of IM applications which choose to use their own proprietary and poorly optimized network protocols (such as Skype, it's atrocious) as opposed to Google C2DM (optimized and efficient) is astonishing.
An interesting note was that I believe much of the focus at Google I/O was on reminding app developers that they need to play nice with the system and other apps.
There are some cases where there are device-specific nonoptimalities. Compared to most Nexus devices, Exynos devices have an absurdly long time to resume from wake (1000 milliseconds), and during that resume cycle CPU frequency is locked to 800 MHz and cpuidle is disabled. This is one of the #1 causes of power drain on our device. This is also exclusively a Samsung kernel/hardware architecture problem that does not affect the Nexus S (similar CPU, but completely different modem interface) or the Galaxy Nexus (different CPU/modem interface).
In the case of our device, the modem is hung off of the CPU on a USB bus - this makes for very long resume times.
Here are obvious reasons the CPU should occasionally turn on when the screen is off:
1) MP3 playback in the background
2) Handling of background syncs - e.g. when an email or Google Talk IM comes in, wake the CPU, handle it, and pop a notification sound, then go back to sleep. Normally, this means the CPU sleeps while waiting for an interrupt from the WLAN chipset or the cellular radio. Unfortunately, some apps drive incoming data to the device far too frequently. (See my above rant about Skype's network protocols being crap compared to Google's C2DM protocol.)
3) Handling of scheduled wakeups (alarms, calendar events, etc) - these are rare and almost never consume power
Most power drain is from item 2, with third-party apps frequently behaving extremely poorly compared to Google's own application suite and sync protocols.
Now this an extensive answer which is very informative and helpful for me since insights are always soothing. Love it. Thanks!
not much to add after Entropy, but if you feel the need to get some control over battery usage you could try betterbatterystats app (and the thread) to identify battery eaters, besides that, there are few apps to check what is going on with your system when it sleeps:
- CPU Spy to show cpu states time
- Autorun Manager or Autostarts to disable triggers causing apps like FB to run without reason (those which you will find with betterbatterystats)
- Battery Monitor Widget, to check battery current consumption (mA) - this app is generally not recommended, because Note's hardware does not report the actual current, so the readings are highly estimated and because when poorly configured it can drain your battery faster, BUT otoh with refresh rate set at 5 minutes or more, it can give you some approximate orientation on how much battery you lose (better than counting %/hour by yourself) at negligible battery usage
- also, if you feel the need to disable net and sync during night, you could automate it using "lama", which is free, and in my experience does not eat much battery by itself
- and last but not least, avoid taskillers, those apps may have adverse effect, i.e. self restarting apps (by the triggers mentioned above), will get killed then restarted and so on and so on, leading to much higher battery drain
My wife's nexus 4 has started having very poor call quality with a big amount of the calls she makes/receives. People sometimes can't bear what she's saying and vice versa.
It's been on 4.4.2 for a while and didn't notice any issues at the time so i dont think the update caused it.
There hasn't been anything significant that i can think of such as any particular apps installed recently that could be causing it.
Any ideas of what could be causing it and any solutions?
no one got any ideas on what is causing the problem and what i could try to do to sort it?
If you assume it's app related: look at the power consumption list. Apps that consume too much CPU (thus causing lag on the system) should appear in the power consumption list
If you know how to debug a system you could try to use top or latencytop via adb over tcp/ip.
Also note that cell-towers can become overcrowded. It is thus possible that you are using a different tower recently. There are several apps in the Market and on f-droid that can show you detailed information about the currently used celltower. You might want to watch out for time-patterns (e.g. evening calls dropping yet morning calls working) as those might indicate a cell tower problem (tower A overcrowded during evening hours).
Turning Airplaine mode on and off will cause your modem to pick the currently best tower. This might help, too (e.g. if swapping rooms means you should use a different tower, yet your modem thinks differently).
So I've had my S5 for a few months now. It's basically been a dream for the time being.
Now the phone is pissing me off the same way the S4 pissed me off...
Battery life is totally fine, absolutely no complaints at all. My phone lasts for ages except for when I play tons of games on it.
Performance however is quite slow (probably due to lack of RAM).. despite running fstrim, cleaning cache on a weekly basis and using apps like Greenify etc.
The worst thing however is the ridiculous issues I am having with 3G/Data.
I am unsure if it is just my carrier (The largest network in Finland (SONERA)) or if it is my phone.
I made a video here of the EXACT SAME issue with Wifi (data is even WORSE):
http://youtu.be/2zNBV63Dk0U
Basically you see the first 2 pages load up pretty fast. Then what's with the wait on the rest of those pages whilst they are loading?
The speed of my network is 10MB/s up and down. It's a symmetric connection. It shouldn't be slow at all, and ping times are tiny. So why is it taking so long for my phone to resolve the website, regardless of the browser and method of connection (data or wifi) that I use?
Basically my phone will just switch between 3G and H/H+ continuously without actually being connected, or loading pages etc.
So basically I'll be in the middle of the capital city, on Finland's LARGEST network connected to 3G with FULL bars and not have a connection. Yet all around me, people are using their phones without remotely any issue at all on the same network..
Some information about my phone:
Galaxy S 5 (SM-G900F). Stock ROM, never flashed. Towelrooted.
4.4.2. - Baseband G900FXXU1ANE2
Build - KOT49H.G900FXXU1ANE4
Stock Kernel
80+ User Apps installed
Xposed Framework installed
The biggest issue I have is the fact that the Data connection just sucks in 2G or 3G. There's just this huge lag between loading any webpage, where there is literally ZERO data being transferred (I have the speed indicator xposed app), yet the icon just flashes back and forth from 3G to H to H+ and back. No matter what browser I use, and even often on Wi-Fi it's just terrible and there is STILL a huge wait time between pages actually loading. However apps at least seem to download totally fine.
I have my Buffalo N300 router on Wireless N. I am NOT running at 5Ghz, because it drains more battery. My 3G plan is set to 21Mbps, and I should have no throttling or cap. However I RARELY seem to see speeds over 250KB/s and in the centre of Helsinki or anywhere in the outlying (2-3km areas) there's just no data transfer at all. Full bars, but in some cases the entire network will just cut out and say that it is unavailable.
Could it be an issue with my phone's Modem? Could I just flash a newer modem over the current one that I have? The phone is running stock and it shouldn't be so slow, no matter what.
My stupid provider just suggested that I change to a more expensive 4G plan (yeah right, 3G on other providers was never remotely laggy)
Any ideas guys? I'll give you any information that you need to help me out...
..
Well what info do you want from me?
I posted a video of how the pages load so slowly even on Wifi. I told you my router. It's a Buffalo N300. I don't have 5Ghz mode on. It's set to Wireless N. My internet speed is 100/100mbps. I think that is plenty of information.
I also gave my complete phone specs. My knox is 1x1 yes. I gave my baseband etc. above.
What exactly do you need to know about my configuration? It's set to use 3G always. I always seem to have bars of 3G (even if it won't connect) but there is NO data transfer at all. You can see in the video that the speed indicator in the taskbar doesn't show any data being transferred. There's just this large amount of time that it does nothing. The page loading/connection stalls and I have to wait. I've tried multiple browsers too like I said, and more than 1 Wi-Fi network.
If I swap back to 3G or 2G (WCDMA/2G) mode. Then the phone still stays on 3G 99.99% of the time, but there's still NO data transfer. On 2G it will work just slow enough that I can send a whatsapp message. But it won't load a webpage, not even slowly.
My carrier I also explained.. Sonera, the biggest carrier here in Finland, I also even explained the data plan I am on. 3G, 21mbps, no throttling, etc.
P.S. The speedtest in my signature, is my HOME WIFI connection. It has NOTHING to do with my data connection. I'm not talking about my DL speed or throughput, besides those are the speeds I get on my COMPUTER. I get slower speeds on my phone. I am talking about the LAG that I get when I try to open a page. I.E. Why does my phone just stall loading something and make me wait for ages for it to finish? Why does my connection just stop, and page loading just stop 40%-60% or whatever through loading something?
What extra info do you need? You keep saying 'phone congifuration' but I just gave you basically everything. What specific 'phone configuration' info do you need to know?
You know what phone I have, exactly what version, how it is rooted, etc. You know my data provider, my wifi and data speeds. You know the issue that I am explaining that I am experiencing and how it happens. Plus a bunch of other information, what is installed on my phone, my router and its set up. etc. etc. etc.
What more do you need?
Thanks for your reply but. Frankly I think I provided more information than most people do about their problems here.
P.S. Here's another video which shows me getting 12.5x slower speeds than I should be:
http://youtu.be/N0aTikEPbPM
Excuse the exasperation and that accompanies my Australian accent
I got some data issues too.in H+ data just won't move like it should.
I'm using saunalahti.
When i open a web page my 3g turns to h+ . I think that's the way i should work
because nothing happens with 3g.
Nothing mostly happens with my 3G either, it has to be on H to do anything. I am starting to think it's an issue with 'Fast Dormancy' and I might go ahead and disable that.
..
fffft said:
Yes, you provided considerably more information than most people. Kudos if that makes you feel any better. However as I explained at length it still isn't nearly enough to effectively troubleshoot much. I also spelt out what would be useful to have. Having 60% of the details doesn't complete a puzzle significantly more than 40% would. It narrows things down a bit but you're still in the land of guessing and throwing out common issues hoping that one of them will turn out to be the problem at hand.
There are lots of people who will be happy to pseudo-randomly guess at the problem. And you can try each suggestion in turn until you hopefully hit upon the right one. I'm more interested in methodical troubleshooting which requires much more detailed information. As I described what would facilitate that and you still ask what do I want, I can only assume that you missed reading part of my earlier reply.
Regardless you can either post the details I requested or wait for others to point out how to address commonplace issues that may or may not help your situation.
Click to expand...
Click to collapse
Are you for real? Practically all of your replies here are "You haven't given us enough information"
You practically know my phone and my data and Wi-Fi as well as I do, from what I have explained.
Now your reply is just paragraphs of you blabbering on about how I still haven't given you enough information for you to help me. If you think you're being constructive here or something replying like this to other people, you really aren't mate. Yes you did explain at length, three times that I didn't give you enough information. Yet you failed, to explain even ONCE exactly what information you want. Except to say "phone configuration" I mean seriously what? That's the most broad term you could possibly use on the forums here. I've explained my phone config, and- actually you know what, I won't do it again. I've explained everything so much and posted TWO VIDEOS of the issues that I am facing. If you seriously don't know enough about my problem then, with all due respect you are of absolutely no help to me what-so-ever.
The worst thing is, I'm usually a patient person and I am grateful for the help I get from other people in the forums here and anywhere else. But every-so-often someone like you comes around and I can't, for the life of me, even fathom as to how to even communicate with you. All of the information is right there in front of you to provide a second opinion or give your personal advice. Yet you're sticking with "You haven't provided enough information". There's nothing else I can do buddy, save actually giving you my phone and letting you look at it.
Also the way at which you seem to post in that I only seem to have 2 options here is really quite ridiculous. That I can either choose to give you more information (What information EXACTLY?) or basically just wait for other people to guesstimate what the issue could be (which I was totally fine with).
If you mean this information:
Or do any testing that might have revealed patterns in your data and wifi rates e.g. speed and latency tests at different times of the day
- What's the point? I explained here and in the videos that this has been happening all the time, for the past month.
with different providers
- I don't have another data provider to test with, I'm not made of money
direct comparisons to other phones on the same connection
- How the f*ck can I get stuff like this? I'm one person on my own, do you suppose I go stand out on the side of the road with a sign on a highway?
ping plots, service menu details about which bands are active and actual signal strengths or anything like that
- Do I look like a scientist to you? How am I supposed to know, and the phone doesn't give me any sort of way natively to even know any of this information
did you do any searches of forums dealing with specific providers e.g. BBR, Hofo, to see if anyone else is having provider issues?
- Yes and lots of people are having the same issues, even someone else replied to this thread stating he had the same issue
Click to expand...
Click to collapse
That is a ridiculous amount of stuff to ask from someone and I have either given you the details already, or you're asking something that isn't physically possible for me to do.
Personally, I think you're going about this whole 'helping people' thing the wrong way. Like there is some choice between getting your 'professional' advice or something or basically just taking hints and suggestions here and there. I don't remotely agree with the way you post on the forums here. I've provided umpteen times more information than just about anyone else on the forum here, and no, that isn't a compliment to myself. It's a fact.
Ugh, this whole situation is just absolutely ridiculous. It's one thing to wrestle with a phone that isn't working correctly, but then when I come to the forums here for advice, I get replies like yours. Supposed helpful replies that are really just basically spam, constant reiteration of a moot point with equally absolutely no clear, or distinct point, subject or purpose to them at all.
Maybe you should take your own advice and be more specific with what information you want from people if you are going to bother to reply to them at all. Rather than just responding continuously with "We need more information". You represent 1 person on the forum here, and your ideas or advice are no more important or relevant than anyone else's. If you're going to try and help someone, don't confuse a person into thinking that they only have 1 source from which they can receive assistance and that they must first comply with your vague requests before they can get any assistance.
As for this now failure of a thread and my now wasted time replying and taking videos perfectly illustrating the problems I am facing with my phone. I am subsequently going to abandon this thread, unsubscribe from future replies and leave it here as both a documented source that there is an on-going issue (as many others have stated) with data and wifi lag and that for anyone else to perhaps understand your methods of posting better. Because I sure as day don't.
Thanks anyway I guess.
As for anyone else with the same issue. I am going to disable 'Fast Dormancy' and see if that solves my problem. Good luck to others facing the same issue.
..
ignore fffft he has issues.
have you tried your sim in other phones? do they get good data speeds? if i were you i'd flash a modem update and see if that fixed anything. maybe try a prepaid carrier on your phone and see how its network speeds are.
Happened to me too - could be an app on your phone. Check settings to see which apps or using most battery and background services.
Or do what I did, and get an uninstaller to uninstall 70% of your apps you don't use - could make a massive difference!
https://play.google.com/store/apps/details?id=com.cleanmaster.mguard
Try this
Sent from my SM-G900W8 using XDA Free mobile app
Gosh.... Can you tell us own many more phone are connected to the same cell as you? This is already a difficult issue to troubleshoot, I guess your videos and long posts are useless. How can you distinguish between a mobile provider problem and a s5 problem?
fffft warned you!
Did you tried the cleanmaster solution?
Having the exact same problems in the US with sprint, I can have 3 or 4 bars of signal and apps report network failures and no data connection, I do not usually have an issue on wifi, but it does happen from time to time.
Rooted with towel
no custom recovery
Multiple frozen system apps
Purchased launch day from Sam's club
Xposed installed, I've disabled most of the modules I installed as they don't seem to work, especially any listed as Samsung specific
Still using TW
Often when the data loss issue occurs the 3g or LTE icon in the notification bar completely disappears, but the signal bar stays in 3-6 bars.
Current battery life seems to have no effect on the issue.
Mine is not just data, there are times the entire phone freezes and becomes unresponsive, taking 20-120 seconds to respond to pressing back or home even, and I get no response to pulling down the notification bar.
I do not use any task killers or battery mods or apps, I did notice a significant increase in occurrences approximately 3 weeks ago and the only thing I recall that I did then was to install hangouts dialer.
The troubleshooting I've done makes me believe the device is "detecting" high temps and turning off or slowing the CPU /GPU cores, thereby causing the apparent 'Lag'.
One incident happened last night, where no part of the phone felt hot, my game did not lose connection, but was on Wi-Fi, but I was getting 1 frame every 2+ minutes for 6 or 7 minutes, then the phone rebooted.
I have started making it a habit of opening Rom toolbox and checking the CPU current settings, during these issues I have never seen the CPU max over 1728 MHz.
The only information I located in a cat log was that frames were dropped and how many. Nothing about temperatures, many lines about IP addresses failing to respond. I do not have a saved catlog handy, but attached are a couple screenshots of data fails with good signal.
If you look, you may notice the warning notifications, those are sync errors with Google photos wanting sign in information for alternate accounts I have on the phone and don't want duplicating my phot backup too (some of my games I play 3 or 4 different accounts).
I will be happy to do any testing suggested as soon as I can and provide additional requested info without insults.
Necropost... Still having this issue, I've been on MOAR, Pac ROM, and Slim. 4.1.1, 4.2, & 5.1.1 android versions. Same problem, on Wi-Fi and Sprint. Phone is about to hit 2yrs old in April. Will be my first and last Samsung I guess... I've had a lot, Nexus is next I think...
Sent from my SM-G900P using Tapatalk