Hi All,
I'm from Germany, new to the forum and have straight a question about my new Samsung Galaxy Alpha.
Since a month now I'm using the Alpha.
I'm quiet happy with the overall performance and handling and really love that phone.
Of course I rooted the Alpha to remove bloat ware and to tweak the autorun behavior of some apps.
When the phone is sitting there connected to WiFi or/and GSM with the screen off waiting for calls, text and mails coming in, it consumes roughly 1% of the battery per hour. What IMHO is a good performance, compared to the SGS2 I owned before.
Anyway, when checking the details of battery usage with 3C Toolbox Pro I figured out, that
MPL Significant Motion in the Google Play Service eats appr. 40% of my battery capacity in standby.
I'm wondering what that service/process is doing (and who started it) as there is no reason for the phone to detect motion in this state. Or I'm totally wrong and MPL Significant Motion is something different???
Even Google couldn't help in this specific case.
The only motion detection I can think off are the Automatic screen orientation and the Flip over to mute function which I have activated.
To narrow down the options I switched these off, but this doesn't change anything regarding the power consumption. These detections should only be active just when the screen is on or in case of an incoming call anyway.
Could somebody out there check if it is a normal behavior to have that MPL Significant Motion thing running more or less constantly?
And does somebody know what this service/process is doing and how to circumvent an auto start?
The 2 Screenshots attached (Battery01/02) showing the usage of MPL Significant Motion (2% out of 5% are used by this process).
The other Screenshots (Apps01-05) showing all the apps and services running on the phone currently.
Thanx for your help in advance!
Related
I'm starting to see a correlation between absolute crap-for-crap batter life and having the ambient light detector enabled. I'll do a test tomorrow, but I'm pretty sure if I just left my screen on full brightness all day, that I wouldn't get as bad of battery life as I do with the ambient light detector turned on.
Is there a problem with the fascinate's polling period? or possibly how much power is being sent TO the sensor? This might explain the problems on hacked roms where people are noticing a buzzing/hissing noise coming from the phone right around the area of the ambient light sensor when in the middle of a call (and the screen is on).
Has anybody seen where in the code the ambient light sensor is handled? (is it in the kernel, or somewhere in the drivers?).
*EDIT*
Thanks for moving my post. I was pretty annoyed with myself for posting in the wrong section.
*edit* Now that the thread has been moved, This post could probably be deleted.
--------------
Well, since nobody has moved this to the other forum yet and it's received a few views, Has anybody else noticed this before?
My personal experience had been full brightness ate battery fast and low brightness was a combination of hard to read and similar drain to auto. Then again my phone has never hissed at me except for godawful noises using skype wifi sometimes, and I have never messed with brightness under froyo.
My only observation with froyo roms is that "stock" eb01 was awful but superclean and AOSP were pretty good, particularly under EB+ kernels.
Also, I lose more battery than I would like to from signal loss overnight, but turning off 3G seems to help with that.
Swyped grumpily from my advertised as "can be upgraded to Android 2.2" device.
i noticed that the automatic brightness setting is absolutely terrible at choosing the correct brightness.
the froyo roms added the ability to hold down on the status bar and move left and right to adjust the brightness, so i just use this to adjust it on the fly when necessary.
this doesn't really answer your question, but i figured i'd add my 2 cents
lane32x said:
This might explain the problems on hacked roms where people are noticing a buzzing/hissing noise coming from the phone right around the area of the ambient light sensor when in the middle of a call (and the screen is on).
Click to expand...
Click to collapse
The noise comes from having the key backlights on during a call.
If you are referring to the softkeys, there were some assumptions that this was the case, but I have tested this out and have heard the noise even when those lights were turned off.
Also, I ran my phone at about half brightness today all day. I've had it off the charger for 15 hours, made 3 hours worth of phone calls, and it's still at 41% battery life.
2 days ago when I just had my phone in the pocket, not doing anything and leaving the screen off (with auto brightness enabled) my battery was dropping significantly after only 6 hours and no phone calls or Internet usage.
I just got my Alpha SM-G850F last week and I went straight to flashing 5.0.2 on it. After a couple wipes and reset to defaults it's now working fine but I'm still not happy with the battery life, especially while the device is idle.
My idle drain is about 3% per hour, which to me it seems a lot coming from a Z3c which usually has around 1% per hour in the same conditions (on WiFi at work or home).
Deep sleep seems to be active most of the time (according to CPU Spy), no rogue apps seem to be active (I even removed the official FB app for this tests) and I don't know what to look for anymore.
Here are the stats:
https://goo.gl/photos/fC5BbXqfZ8PpZFmy7
Some info on my setup:
- no power saving
- brightens on auto set to minimal
- location ON with high accuracy
- Bluetooth ON paired with G Watch R (switching it off at night does not make much difference)
- WiFi ON and connected
- Google Now OFF
- Nova Launcher instead of TouchWiz
- S Voice, S Health and the rest of S Krap disabled
I was wondering what's the average idle drain on WiFi for you guys.
PS: Is it normal that CPU Spy does not report above 1300Mhz (was it not supposed to go up to 1800) ?
First of all, Sony Xperia Z3 Compact has a bigger battery, 2600 mAh compared to Alpha's 1860 mAh battery. Second thing G850F has 2 processors, one clocked @ 1.3 GHz, second one clocked @ 1.8 GHz. I recommend turning all these settings off when you can (e.g. WiFi, bluetooth, location)
I've got a question though; does your touch screen work at the top left corner of the screen, like you can try swiping the navigation bar slowly from the top left corner and tell me if it goes back to its place (when im playing games buttons sometimes dont function)..
Best regards,
James
Of course there is a battery difference but still there is a big difference. Assuming the Alpha was half size that would still mean at most 2% drain. That's why I was asking for people to share their idle usage so I can compare. At the moment I'm flashing KK and I will report back after the weekend. I'm not about to dumb it down by turning off all the smart features that I use. I also remember I had the same high drain in the first version of lollipop for the z3c, but they fixed it in the meantime.
Regarding your touch screen issue, I saw your thread but I'm not experiencing it. I have no games to try with but in other apps I do not sense this issue.
Perhaps it's related to CPU usage which I assume it's pretty high during gaming ?
Battery is better in KK, idle drain dropped to less than 1.5% per hour, also memory management is way better and most of my apps are always in ram so they resume instantly, tho the system overall does not feel as snappy as with LP.
I miss the lock screen notifications and smart lock but I'm gonna stick with KK until a new version of LP turns out (hopefully 5.1.1).
Here are the stats:
https://goo.gl/photos/nAQuZzLzdyD2imV39
I dont understand your statistics,but obviously Android system & kernel drain your buttery and this is not normally
but we have only first build of 502 jet,and I think newer version of 502 will be much better
Actually that's normal when you don't have any apps wreaking havoc in background when the screen is off. So basically what you're left with are the notifications, communication (WiFi, Bluetooth & GSM), location and the rest of the google/samsung stuff that you can't really control. Overall 26h with 1.5h SoT for such a small battery is reasonable to get you through the day.
Here is my idle drain after full charge and leaving the phone untouched through the night.
View attachment 3365181
Power saving is off and I`m on Ozcan ROM. With my pattern of usage battery lasts for 2/2,5 day with around 2,5h SOT (no power saving and brightnes on auto 5).
93drago said:
Here is my idle drain after full charge and leaving the phone untouched through the night.
View attachment 3365181
Power saving is off and I`m on Ozcan ROM. With my pattern of usage battery lasts for 2/2,5 day with around 2,5h SOT (no power saving and brightnes on auto 5).
Click to expand...
Click to collapse
Looks good. My battery went down about 14% over night from fully charged (as much as 20% on other 5.0.2 roms). Do you have exchange accounts? I've found them a bit of a drain in the past. I'll try again tonight and post some stats.
I have facebook, messenger, snapchat and 4 gmail accounts that have push notifications. I also use greenify with experimental functions enabled - it indeed saves some battery power.
As Samsung declare, to extend battery life of your gear S, never recharge more than 80%!
I don't know why, but a Samsung engeneer teach me that this trick works perfectly on all devices, in SAM laptop, for example, user can choice this function from BIOS!
So charge until 80% and get out more than the original 100%??
Sent from my SM-N910F using XDA Free mobile app
Basically this trick is not to make the battery have a longer period before it drains to 0% but rather to make its entire lifespan longer. It's the same thing with draining if to zero. Ideally, lipo batteries would be kept at their nominal voltage (40-50% on most batteries) in order for them to have the longest life.
Hope that helps.
Thank you for the tip!
m0nz said:
Basically this trick is not to make the battery have a longer period before it drains to 0% but rather to make its entire lifespan longer. It's the same thing with draining if to zero. Ideally, lipo batteries would be kept at their nominal voltage (40-50% on most batteries) in order for them to have the longest life.
Hope that helps.
Click to expand...
Click to collapse
m0nz thank you very much for the tip !
I normally follow these tricks on increase the battery life of Android devices
Adjust the brightness
The display on your watch doesn’t always have to be super bright, especially if you’re indoors most of the time. There are usually five or six levels of brightness depending on the Android Wear watch model, and the default is usually a setting of 4. A setting of 3 is a happy medium, but you can probably get away with a level of 2 most of the time.
Turn off Tilt to Wake Screen
Tilt to Wake will automatically wake your watch when you hold up your arm and tilt it towards you. A very useful feature, but you might find that your display actually turns on a lot of times when you never intended to look at it. This might seem harmless, but it adds up over time and will lower your battery life.
Block unnecessary notifications
Getting notified about new emails, reminders, the weather, and other important stuff are crucial to your experience with Android Wear, but there might be notifications that aren’t as significant. Blocking those that aren’t will reduce the amount of time your watch wakes up.
I normally don't let the battery runs under the 20% of charge for smartphone and smartwatch too....
Rickyzx said:
I normally follow these tricks on increase the battery life of Android devices
Adjust the brightness
The display on your watch doesn’t always have to be super bright, especially if you’re indoors most of the time. There are usually five or six levels of brightness depending on the Android Wear watch model, and the default is usually a setting of 4. A setting of 3 is a happy medium, but you can probably get away with a level of 2 most of the time.
Turn off Tilt to Wake Screen
Tilt to Wake will automatically wake your watch when you hold up your arm and tilt it towards you. A very useful feature, but you might find that your display actually turns on a lot of times when you never intended to look at it. This might seem harmless, but it adds up over time and will lower your battery life.
Block unnecessary notifications
Getting notified about new emails, reminders, the weather, and other important stuff are crucial to your experience with Android Wear, but there might be notifications that aren’t as significant. Blocking those that aren’t will reduce the amount of time your watch wakes up.
Click to expand...
Click to collapse
That's not a batter management tip - its a tip for the Samsung designers to get a clue and improve the detection algorithm. This is a problem on many Samsung devices I have hard - they bungle the face, motion and light detection algorithm, so the phone is always slow to detect you when you do need it, yet there are far to many false detections.
Hi guys,
i used to get more than 7 hours of active screen on my Nubia Z9 (3G browsing) - i have measured it one day during intensive day usage.
Now it's only 3 or so on current firmware.
Wakelocks seem to be ok, i don't have problems in sleep mode.
I don't remember which firmware i used before, i've changed a lot of them.
Battery itself is less than 1 year old and seem to be ok, i've tested it with Battery Monitor widget during several weeks and it almost did not loose capacity by now.
How to find, who drains the battery on this firmware on ACTIVE usage? Radio? CPU on abnormal frequencies? I'm pretty satisfied with new firmware, it's smooth and has a lot of useful features. But so much reduced active mode usage worries and annoys me.
I suspect the problem is Android OS itself, but why only in ACTIVE MODE?
I also want to mention I use two smartphones with identical set of apps and settings (including google syncs, etc.). And that second phone is doing fine in terms of battery drain. Second smartphone uses Snap 615 and this uses Snap 810.
Have migrated a lot of stuff from my S5 901F to the G5 using a LG stock rom.
Most stuff is equal to the 901F or faster in performance, however chompsms is for some reason slower, and not just slower but very noticebly slower, my old galaxy ace is faster using chompsms.
e.g. to load messages from my sister the times are analysed as below using video recordings.
S5 901F 0.2s
Galaxy ace 0.9s
G5 3.7s - yes over 3 seconds
If I do it repeatedly it doesnt speed up, so its not even faster when expected due to caching.
If I force the cpu clock at min speeds on my 901F at 300mhz, it is still faster at 2.1s.
crazy, any ideas?
Try Textra maybe? For me it's always intstantaneous. I used Chomp SMS in gingerbread days, but at some point QKSMS and then Textra won.
https://play.google.com/store/apps/details?id=com.textra&hl=en (Lot's of customisation).
Thanks but that seems a bit of a copout, chompsms isnt the problem. Also I am now noticing more apps/functions are laggier, in some cases way laggier.
The more I use the phone the slower I am noticing it is. Something isnt right, either snapdragon 820 isnt actually faster than 805 for real world use (made to just bench fast) or something is seriously screwed with LG's firmware. To boot it drains 3x as fast when sleeping as well.
Its bad enough I am considering selling the G5, but I can see from comparing screens that my S5 is developing a tint on light colours suggesting the amoled is wearing down, so I am still trying to get it fast. I even seen a video comparing the exynos to the 820 on the s7 and the 820 had issues on that phone as well.
What I like?
usb-c, defenitly better than micro usb.
Always on clock, is very nice.
Speaker placement, also very nice not been at the back.
Better multitasking.
Issues.
Performance, scrolling will randomly stutter, some stuff is just very slow, also wireless is struggling to keep at max strength even tho the router is 1m away and the s5 sitting next to the g5 has full wifi speed all the time.
Display viewing angles, is pretty poor, of course I have been spoilt by amoled.
Back power button feels sometimes not a smooth click and sort of like it will break soon.
Edges of phone not smooth with sharp edges here and there - mitigated by my gel cover tho.
Missing features that are nice in touchwiz such as 2g only mode, silent notifications (not silent mode I mean actual notifications called silent), auto redial when engaged. I downloaded a silent.mp3 file to readd silent notifications/ringtones, 2g only mode I can select with intelli3g but I have to manually set it on boot up which is annoying. No solution for auto redial yet.
Wifi internet keeps dieing, wifi will stay connected but dns lookups start failing, comes back to life when manually reconnecting. No other devices in my home are having this issue.
Oddity
For some reason by default LG configures a 900+meg ram disk for swap, when I dont see the point as with 4 gig of ram nothing needs swapping.
No cpu cores turn off, like the 901f cores do which may explain why phone feels warm when using (even for texting) and faster drain. The big/little cpu core system seems to feel inferior to a normal set of 4 cores.
ok I have found the cause but its weird.
Basically if I remove the sim card, chompsms is snappy, and other apps that lagged also go fast.
Insert sim card it lags again.
Also if I disable AOD the battery life is only slightly worse than the S5.
AOD on auto sync off, amplify, greenify optimised, doze off - average 0.4% drain per hour
As above but S5 - 0.3% hour.
As above but with AOD on with G5 1.3% hour
With the IPS backlight bleed, I can see the entire screen is been powered for the AOD, so seems a poor design in regards to battery efficiency.
12 hours ago I had made the decision to send the phone back to EE, now I have made progress on the lag, I am back in dont know mode. I definitely do prefer amoled, IPS viewing angles and bad blacks are annoying, the AOD is brilliant but is a price to pay for battery life and I dont know about the affect on IPS backlight life with it been always powered up. The power button positioning doesnt make sense, e.g. if the phone is on my desk I have to pick it up to use the power button which is annoying.
chrcol said:
ok I have found the cause but its weird.
Basically if I remove the sim card, chompsms is snappy, and other apps that lagged also go fast.
Insert sim card it lags again.
Also if I disable AOD the battery life is only slightly worse than the S5.
AOD on auto sync off, amplify, greenify optimised, doze off - average 0.4% drain per hour
As above but S5 - 0.3% hour.
As above but with AOD on with G5 1.3% hour
With the IPS backlight bleed, I can see the entire screen is been powered for the AOD, so seems a poor design in regards to battery efficiency.
12 hours ago I had made the decision to send the phone back to EE, now I have made progress on the lag, I am back in dont know mode. I definitely do prefer amoled, IPS viewing angles and bad blacks are annoying, the AOD is brilliant but is a price to pay for battery life and I dont know about the affect on IPS backlight life with it been always powered up. The power button positioning doesnt make sense, e.g. if the phone is on my desk I have to pick it up to use the power button which is annoying.
Click to expand...
Click to collapse
Try Next Sms, it has more features then any Sms. Power button good for out of pocket. For situations like yours use double tap to wake screen up
Sent from my LGE LG-H830 using XDA Labs
Nick216ohio said:
Try Next Sms, it has more features then any Sms. Power button good for out of pocket. For situations like yours use double tap to wake screen up
Sent from my LGE LG-H830 using XDA Labs
Click to expand...
Click to collapse
I think you ignoring the problem, my issue is not chompsms.
It is that the phone slows down significantly when my sim card is inserted.
e.g.
no sim
better battery stats to browse kernel wakelocks and partial wake locks instant
chomp sms to browse text messages instant
with sim inserted
chompsms slow
stock messaging app slow
better battery stats to browse wakelocks about a 4 second pause - this doesnt even read text messages and also affected
the weird stuttery behaviour vanishes when sim is removed
so something is broken in the firmware that when a sim card is inserted the phone runs slower.
I also found a nasty bug in the interactive governor on stock kernel (also exists on xperience custom kernel). The clock will keep staying at highspeed value and not idle well. I fixed this by setting highspeed to same as idle clock but this is a seperate issue and no relation to the big sim card problem.
When sim card is inserted my 7 year old galaxy ace is a faster phone
EE have a 14 day returns policy, today is day 8, so I got 2-3 days to try and find a fix or I am returning phone.
The issue happens with locked bootloader and shipped firmware as well.
I edited title now so not confusing.