Please be patient with me guys this thread is work in progress...Many thanks to ahalford and with reading and learning from our great kernel devs here i will build this thread up as we go along
Right first up this thread is work in progress. Most of the info is from ahalford. He has been kind enough for me to use the information on his thread and share it here with you guys. Now to start with i will be sharing his info here and then i will be adding my own information as i go along with this thread as i am still learning and i feel i can add my own input here to...So enough of this and lets get going with the thread
What is wakelock and why it may cause battery drain:
Wakelocks or to be more precise partial wakelocks is a pattern (in fact a class) than helps devs to make sure that important pieces of their code do not get interrupted.
Basically the phone has (simplified, kernel devs don't shoot) three states:
1. awake with screen on
2. awake
3. sleeping (that's you phone favorite state)
The transitions are from (1) to (2) and finally from (2) to (3). Now as long as you use your phone it's in (1) and does not leave that state as long as you keep using it interactively. If you stop using it the phone is aiming to go to (3) as fast as possible.
And here's where wakelocks are important: as our phones as smartphones they tend to do background processing. Some of this processing is important like e.g. making a phone call, listening to music or synchronizing your contacts.
As the phone wants to go from (2) to (3) and on the other hand you don't want to hang up while you are in a call the app keeps hold of a wakelock to prevent that transition. When you hang up the partial wakelock gets release and here we go (the phone goes to sleep).
So partial wakelocks is a tool and it's not something that we should forbid for obvious reasons. Now there are cases when the design on an app is not real life proven (conditions of poor of no coverage) and the wakelocks have negative effects because they are held unnecessarily or for too long.
How can we identify it?
BetterBatteryStats app identifies these wakelocks and using your expertise or the once from our users here you can understand what happens and find a strategy to change that for the better.
Link for BetterBatteryStats:
XDA Thread
Playstore Link
New app as well other than BBS is Wakelock Detector..
Link: WakeLock Detector - XDA thread
With this app you can detect applications which are consuming much battery by checking wakelock history.
It simplifies BetterBatteryStats by concentrating more on wakelocks.
No any background services or system bootup events for gathering data.
Brief explanation, about where to look at the wakelocks:
Set your reference as "Since unplugged" in the second line.
Then, in the first line: "Other" - look at the "Awake" vs "Screen on". If it differs a lot, continue with a drill-down.
First line - check under "Partial Wakelocks" and "Kernel wakelocks".
"Menu" - "More" - "Raw kernel wakelocks"
For more help: "Menu" - "Help" - "Getting started" or "How to".
Brief History Lesson
The relationship between embedded system developers and the kernel community is known for being rough, at best. Kernel developers complain about low-quality work and a lack of contributions from the embedded side; the embedded developers, when they say anything at all, express frustrations that the kernel development process does not really keep their needs in mind. A current discussion involving developers from the Android project gives some insight into where this disconnect comes from.
Android, of course, is Google's platform for mobile telephones. The initial Android stack was developed behind closed doors; the code only made it out into the world when the first deployments were already in the works. The Android developers have done a lot of kernel work, but very little code has made made the journey into the mainline. The code which has been merged all went into the staging tree without a whole lot of initiative from the Android side. Now, though, Android developer Arve Hjønnevåg is making an effort to merge a piece of that project's infrastructure through the normal process. It is not proving to be an easy ride.
The most controversial bit of code is a feature known as "wakelocks." In Android-speak, a "wakelock" is a mechanism which can prevent the system from going into a low-power state. In brief, kernel code can set up a wakelock with something like this:
Code:
#include <linux/wakelock.h>
wake_lock_init(struct wakelock *lock, int type, const char *name);
The type value describes what kind of wakelock this is; name gives it a name which can be seen in /proc/wakelocks. There are two possibilities for the type: WAKE_LOCK_SUSPEND prevents the system from suspending, while WAKE_LOCK_IDLE prevents going into a low-power idle state which may increase response times. The API for acquiring and releasing these locks is:
Code:
void wake_lock(struct wake_lock *lock);
void wake_lock_timeout(struct wake_lock *lock, long timeout);
void wake_unlock(struct wake_lock *lock);
There is also a user-space interface. Writing a name to /sys/power/wake_lock establishes a lock with that name, which can then be written to /sys/power/wake_unlock to release the lock. The current patch set only allows suspend locks to be taken from user space.
This submission has not been received particularly well. It has, instead, drawn comments like this from Ben Herrenschmidt:
looks to me like some people hacked up some ad-hoc trick for their own local need without instead trying to figure out how to fit things with the existing infrastructure (or possibly propose changes to the existing infrastructure to fit their needs).
or this one from Pavel Machek:
Ok, I think that this wakelock stuff is in "can't be used properly" area on Rusty's scale of nasty interfaces.
There's no end of reasons to dislike this interface. Much of it duplicates the existing pm_qos (quality of service) API; it seems that pm_qos does not meet Android's needs, but it also seems that no effort was made to fix the problems. The scheme seems over-engineered when all that is really needed is a "do not suspend" flag - or, at most, a counter. The patches disable the existing /sys/power/state interface, which does not play well with wakelocks. There is no way to recover if a user-space process exits while holding a wakelock. The default behavior for the system is to suspend, even if a process is running; keeping a system awake may involve a chain of wakelocks obtained by various software components. And so on.
The end result is that this code will not make it into the mainline kernel. But it has been shipped on large numbers of G1 phones, with many more yet to go. So users of all those phones will be using out-of-tree code which will not be merged, at least not in anything like its current form. Any applications which depend on the wakelock sysfs interface will break if that interface is brought up to proper standards. It's a bit of a mess, but it is a very typical mess for the embedded systems community. Embedded developers operate under a set of constraints which makes proper kernel development hard. For example:
One of the core rules of kernel development is "post early and often." Code which is developed behind closed doors gets no feedback from the development community, so it can easily follow a blind path for a long time. But embedded system vendors rarely want to let the world know about what they are doing before the product is ready to ship; they hope, instead, to keep their competitors in the dark for as long as possible. So posting early is rarely seen as an option.
Another fundamental rule is "upstream first": code goes into the mainline before being shipped to customers. Once again, even if an embedded vendor wants to send code into the mainline, they rarely want to begin that process before the product ships. So embedded kernels are shipped containing out-of-tree code which almost certainly has a number of problems, unsupportable APIs, and more.
Kernel developers are expected to work with the goal of improving the kernel for everybody. Embedded developers, instead, are generally solving a highly-specific problem under tight time constraints. So they do not think about, for example, extending the existing quality-of-service API to meet their needs; instead, they bash out something which is quick, dirty, and not subject to upstream review.
One could argue that Google has the time, resources, and in-house kernel development knowledge to avoid all of these problems and do things right. Instead, we have been treated to a fairly classic example of how things can go wrong.
The good news is that Google developers are now engaging with the community and trying to get their code into the mainline. This process could well be long, and require a fair amount of adjustment on the Android side. Even if the idea of wakelocks as a way to prevent the system from suspending is accepted - which is far from certain - the interface will require significant changes. The associated "early suspend" API - essentially a notification mechanism for system state changes - will need to be generalized beyond the specific needs of the G1 phone. It could well be a lot of work.
But if that work gets done, the kernel will be much better placed to handle the power-management needs of handheld devices. That, in turn, can only benefit anybody else working on embedded Linux deployments. And, crucially, it will help the Android developers as they port their code to other devices with differing needs. As the number of Android-based phones grows, the cost of carrying out-of-tree code to support each of them will also grow. It would be far better to generalize that support and get it into the mainline, where it can be maintained and improved by the community.
Most embedded systems vendors, it seems, would be unwilling to do that work; they are too busy trying to put together their next product. So this sort of code tends to languish out of the mainline, and the quality of embedded Linux suffers accordingly. Perhaps this case will be different, though; maybe Google will put the resources into getting its specialized code into shape and merged into the mainline. That effort could help to establish Android as a solid, well-supported platform for mobile use, and that should be good for business. Your editor, ever the optimist, hopes that things will work out this way; it would be a good demonstration of how embedded community can work better with the kernel community, getting a better kernel in return.
Many thanks firstly to the following:
ahalford: for his awesome thread and his awesome work and a great guy for allowing me to share his work here...please click the thanks for him for all this
chamonix and his team: for his awesome must have app BBS and for all the work they put in it...without that app we would be lost..
Entropy512: guy is a human wikipedia...
To all the kernel devs and those who explained in detail regarding the wakelocks definitions and everything else..
Like i said above i merely put all the info together from ahalford...he is the genius behind this thread and please click here to check his thread out and thank him...I will be adding my own info here as well and make this thread in the long term as my thread to be proud of..
TYPICAL REASONS FOR WAKELOCKS & APP SUCKERS, KNOWN ISSUES:
*Any kind of messengers, social clients – like Skype, Facebook, Twitter, etc. Any of those, who want to be online, receive a push messages, sync every while. If it’s must to have them, disable it in accounts sync settings, and disable notifications in each app’s setting.
*“Energy savers” – Green Power, Timeriffic, etc. They mess with the system power policy, if you choose to enable/disable wi-fi, gps, data, Bluetooth, etc. Especially, Samsung’s one is known as problematic.
*“Soft-buttons”, so called “power button savers” – like ScreenOff & Lock and such. Related to previous group. Let the hardware do the job.
*Task killers - If it kills some services in the middle of their action, it will cause’em start all over again or even stuck, and eat your precious battery resources. If you have to use it (like in case with JB 4.1 memory leak issue, do it manually).
*Your sound settings – screen vibro & sounds on tap, haptic feedback – disable it.
*Media Scan – process, that will run after each fresh install & reboot. Typically takes about 10-15 minutes, runs on high CPU frequency. If stuck more than this, causes no Deep Sleep (can be seen in CPU Spy app) – you have an issue with Media Scan. It can stuck on large files directory – nothing to do here, unless you can reduce files number. Another case – problematic memory cluster, and there is only solution to back your data, format your storages, and start over.
*Startup - Check it – do you really need this entire long startup list? Throw some; it will only make the system act better.
*Accounts sync – again: Minimize your list. Drill down every account setting, Google especially: Picasa, Google Disc, G+, etc.
*App settings – always drill down your app settings – it may be some nasty hidden setting, that enables your app to be in constant action. No concrete advise, treat each app individually.
TIPS:
Always perform clean install! Backup your stuff – App2zip (free on market) app, Titanium, whatever – spend some time for formats and setting up your settings, you will only have profit on this.
Don’t judge your battery consumption right after new rom/kernel install. Especially in the first hour, while Media Scan is busy with scanning your storage. System needs some time to settle.
It is highly suggested, after you installed all apps and made your configurations, to reboot recovery and clean your cache & dalvick.
If you’re installing custom kernel and any .zip flashable files, don’t do it in the same time with rom flashing. Flash the rom, reboot system, let it settle, then reboot recovery again, flash your kernel/mods, let it settle again.
WI-FI sleep policy: leave it on “Always”. Note’s wi-fi chip consumes nearly zero energy, and it would be much healthier to leave it on.
WI-FI home network: if you’re on dynamic IP, set to maximum your DHCP lease time in router setting, and bind your device to the MAC address. Also, fix your WI-FI channel and frequency both on device and router.
Don’t mess with Fast Dormancy app, if you don’t have dormancy related wakelocks, or if you don’t know your cell operator dormancy setting! And, on JB 4.1 it’s sometimes more preferable to leave it on, than to deal with some weird wakelocks, that may appear. Another case – if your operator setting for dormancy is “off”, app won’t discover it, and, actually, you may enable it instead of disabling it.
PWL Bloodsucking apps that drain the battery due to constant wakelocks. (thanks to T.J.Bender)
A note when uninstalling Google built-ins: Google built-ins are often system packages, and deleting them can have unpredictable results. I highly recommend freezing them in Titanium Backup for several days to see how the phone runs before uninstalling them through there as well. Deleting system processes is inherently risky, and I assume no responsibility for your own decisions.
Facebook: Any social networking app will want to sync as often as it can, but you can overrule that by setting notification intervals. Thing is, Facebook doesn't respect those intervals, and wakes up the device for data exchanges pretty constantly (even though your news feed may only update every hour or so when you want it to). This app is no better than bloat, and should be treated as such when you clean house.
Alternative App: Friendcaster. It's as good a third-party Facebook client as you'll find on Android, and it only wakes up when you tell it to.
Gmail: A running theme here will be that if there's a non-Google equivalent to a Google app, you should probably kill the Google and download the alternative. Gmail is an alarm fiend, and one of the main offenders if you have an excessive SyncLoopWakeLock problem.
Alternative App: How many email clients are out there? I've had the best luck with the stock Email app, but K-9, Kaiten, MailDroid, even Enhanced Email and Touchdown for the power users are all great alternatives. Speaking of which...
Whatever email client you're using: Email clients will always be high up on the list of alarms, and that's by their nature. Keep an eye with raw network stats on how long they're connected for, and don't be afraid to experiment. I tried K-9, Kaiten and MailDroid before settling back on the stock Email app as the one that gave me the best balance of battery life and necessary features.
Alternative Apps: Download and try out different clients until you find the one that works for you. Nothing ventured, nothing gained, right?
Google Latitude: Latitude is a tracking service. As such, it tracks you. Beyond the creepiness aspect of that, it holds your phone awake pretty often while doing so. Kill it. Kill it with fire.
Alternative App: Personally, I'm not into the whole stalking thing, but I've heard that Glympse works quite well.
Google Maps: Colossal waste of space and battery. You can do better. An important note on Google Maps: this app will still wake your device up even after being frozen in Titanium Backup. I don't know how it happens, but it does. To truly solve the alarms from Google Maps, you have no choice but to uninstall it. Do so at your own risk.
Alternative Apps: I'm a fan of Waze for navigation and MapQuest for a Google Maps-ish browseable interface. OSMAnd is also a great alternative, but it uses a ton of internal memory because of its offline nature.
Google Play Music & Movies: Updates itself constantly and wakelocks. Even if you freeze it, it still somehow manages to tell you that there's an update available. It's the Google zombie.
Alternative App: There are literally 100+ music and/or movie players out there. I'm sure you can find one that works for you. I'm a big fan of RocketPlayer for music, and I just use the stock video app more often than not.
JuiceDefender: What's that you say? JD sets off tons of alarms and holds the device awake for more time than I'd care to discuss, largely because of its data control settings. More harm than good, in my opinion.
Alternative Apps: JuiceDefender's main goal in life is to minimize the amount of time your device is held awake. Therefore, if you've just gone through all this to clear out wakelocks, do you really need another wakelock-prone app to do what you've already done?
Skype: Occasionally, after a call, Skype will wakelock. This is not designed to happen, and is more a glitch in the app than a forced sync. Force-stopping the app and clearing its cache have solved it for me on the rare occasion that I've seen the wakelock occur.
Alternative Apps: No idea. I don't personally consider this a "replace" situation.
World Weather Clock Widget: Do you have this on your phone? Get rid of it. I installed it as an alternative to SiMi Clock Widget, and while it certainly looks pretty, it ignored my "Update every 3 hours" and tried to update 275 times in that 3 hour window. This drove AlarmManager, GSYNC_ACONN, and NetworkStats off the deep end, and left me at 82% deep sleep with 6% of my battery gone in 3 hours. Kill it. Kill it with flaming nuclear waste.
Alternative Apps: I liked SiMi Clock and wanted to try something new, basically. I'm back to SiMi, but there are literally hundreds of clock widgets out there.
Wakelocks - XDA Developers Wiki - Worth the read trust me
Wakelocks Definition
AlarmManager:
Speaking Name: Alarm Manager
Rationale: AlarmManager provides access to the system alarm services. These allow you to schedule an application to be run at some point in the future. When an alarm goes off, the Intent that had been registered for it is broadcast by the system, automatically starting the target application if it is not already running. Registered alarms are retained while the device is asleep (and can optionally wake the device up if they go off during that time), but will be cleared if it is turned off and rebooted. The Alarm Manager holds a CPU wake lock as long as the alarm receiver's onReceive() method is executing. This guarantees that the phone will not sleep until you have finished handling the broadcast. Once onReceive() returns, the Alarm Manager releases this wake lock. This means that the phone will in some cases sleep as soon as your onReceive() method completes.
Know actions: AlarmManager itself is not generating partial wakelocks but the applications (intents) that were set to be called when an alarm goes off do. Alarms can be listed through the menu "Actions - Alarms".
AlarmManager is a universal process that MANY apps use to update time, push you notifications, etc. In most cases, it is a necessity; in other cases, you should really check it out and disable/uninstall things that have invoked it too much.
AudioOut_1
Speaking Name: AudioOut_1
Rationale: AudioOut is used to play notification and system sounds.
Know actions: From the home screen... Menu -> Sounds -> uncheck "Touch Sounds", uncheck "Screen lock Sounds"
Known conditions of occurence: Each time the screen is touched or locked.
Definition: "AudioOut_1" is a Wakelock that is basically a kernel process that funnels data from audio apps to the audio hardware. It's what processes audio from say, Pandora or Slacker Radio, and passes it to the phone's audio hardware.
AudioOut_3
User Experience
But for those of you that have lockscreen sounds on, touch screen sounds on and dialpad touch tones on then you will have massive wakelock. I had this same problem with my S2.
Only way to beat this. Settings - Sound - system and untick the first 3 options. Reboot and charge your phone and then check the difference. You will see that the wakelock is not as high as it use to be.
More info regarding this you can find here
ConnectivityService
Speaking Name: ConnectivityService
Rationale: Service responsible for tracking data connection / apn, establish and maintain connections. This wakelock is held during transition between data connections.
Know actions: May be conditioned by using a different radio/modem or bad coverage, may be reduced by forcing 2G.
deleted_wake_locks
Speaking Name: deleted_wake_locks
Rationale: In the API available to android drivers it is advised to call wake_lock_destroy before freeing the memory of the wakelock struct that they created. This is done above all on shutdown, but also in a few situations where a driver is unloaded dynamically from the kernel. Whenever it happens, the destroyed wakelocks disappear from the list but their stats are added up to this pseudo-wakelock to the deleted_wake_locks. This allows knowing that a set of old wakelocks had a combined set of stats that this entry shows. The stats of this entry do not increase unless additional real wakelocks that have non-zero stats are destroyed.
Know actions: Since this is merely an entry that combines the activity of all the kernel wake locks that no longer exist, there's nothing that can be directly done to reduce this entry. The best course of action is to identify the wake locks that generate activity and that are later deleted, before that happens and they end up showing in a combined way on this entry.
Known conditions of occurence:
The Wifi driver is one known source for kernel wakelocks that are destroyed whenever the driver is unloaded (when Wifi is disabled manually or as part of the turn-off policy). Wakelocks such as wlan_rx_wake and wlan_wake, when the driver is unloaded, will no longer show up in the list and their stats be added to the deleted_wake_lock previous values.
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservi ce.AndroidEndpoint
Speaking Name: AndroidEndpoint
Rationale: This wakelock has been found to occur under certain non reproducible conditions, showing high wakelock counts and in certain cases high wake times. As the reasons are not exactly known there is no garanty that this wakelock does not occur for other yet unknown reasons.
Know actions: In one case (see ref) this wakelock was successfully removed by changing the proxy / re-creating an APN definition and leaving the proxy blank for that APN. The "faulty" proxy was predefined for the provider Orange but it is not excluded that proxies from other providers show the same effect.
Known conditions of occurence:
Conditions are unclear, to be confirmed
network-location
Speaking Name: Network Location
Rationale: The network location service is responsible for providing coarse grained location information to requesting applications.
The frequency of updates (and of wakelocks) is related to the precision requested by the application (max. time between updates, precision in meters).
Examples of app requesting coarse grained location: weather widgets, latitude, most social tools, google+
Know actions: Actions to reduce wakelocks:
• Find the responsible app: look for all network-location wakelocks and check for the responsible apps on the second line of the list
• Check the settings of the app to see if the precision can be changed
• Use the benefits of Wifi based location (stable location minimizing the update frequencies)
• Look for alternative apps with a better design
Known conditions of occurence: Poorly designed apps with too high requirements on precision will drive the Network Location Service up.
Unstable network conditions (frequent handovers between towers) may trigger location updates.
In some cases updating the radio/modem has effect on the network location: the location is based on the tower information delivered by the RIL.
Related wakelocks: LocationManagerService, NetworkLocationLocator, WifiService, GpsLocationProvider, network-location-cell-update
PowerManagerService
Speaking Name: PowerManagerService
Rationale: This kernel wakelock is a placeholder for all partial wakelocks being held in userland.
Know actions: Use "Partial Wakelocks" to drill down the applications / services causing wakelocks.
Known conditions of occurence: Some devices show userland wakelocks as a total named PowerManagerService
suspend_backoff
Speaking Name: suspend_backoff
Rationale: suspend_backoff is triggered whenever there's a rapid succession of sleep-wakeup-sleep transitions in a short period of time (10 occurrences within x ms IIRC). When that happens, SB makes sure the device is continuously awake for a bit instead of alternating a lot. The KWL count indicator could give a hint about the source of those continuous wakes, but not a definite answer because it doesn't show their time distribution.
Known conditions of occurence: Read here on how to tackle this wakelock and read here to
svnet
Speaking Name: svnet-dormancy / multipdp from the man himself(those are synonyms, depending on android version)
Rationale: svnet-dormancy is a kernel wakelock related to cell data transfers - Fast dormancy or not, you get a 6 second wakelock any time the radio transfers data..In other words, the phone stays awake for 6 seconds for every incoming data packet which effectively prevents it from sleeping.
Know actions: Change the duration of the wakelock (use at your own risk). Reduce the wakelock by reducing the amount / number of data traffic requests
Known conditions of occurence: Caused by data traffic
Sync:
Speaking Name: Account Sync Service
Rationale: The sync service is responsible for syncing all the accounts from "Settings" - "accounts and sync". A wakelock is held while the sync process is running.
The more items are getting synced and the more often the sync occurs the higher the wakelock time will be.
Potentially the wakelock time is prone to raise in case of bad data connectivity.
Examples of accounts are: twitter, google+, linkedin, google mail
Know actions: Actions to reduce wakelocks:
• Remove any unwanted accounts
• Check the settings and remove any unwated options (contact sync)
• Check the frequency of the sync and see if you really need it as defined
Known conditions of occurence: Under bad data connectivity conditions, with poorly designed Sync providers
Related wakelocks: none
References: A known bug related to gmail:Email app wakelock
SyncLoopWakeLock
Speaking Name: SyncLoopWakeLock (Account Sync)
Rationale: SyncLoopWakeLock is the wakelock used by the Android SyncManager (android.content.SyncManager) and was introduced starting in 4.01. The sync service is responsible for syncing all the accounts from "Settings" - "accounts and sync". A wakelock is held while the sync process is running.
The more items are getting synced and the more often the sync occurs the higher the wakelock time will be.
Potentially the wakelock time is prone to raise in case of bad data connectivity.
Examples of accounts are: twitter, google+, linkedin, google mail
Know actions: Actions to reduce wakelocks:
Remove any unwanted accounts
Check the settings and remove any unwated options (contact sync)
Check the frequency of the sync and see if you really need it as defined
Known conditions of occurence: This wakelock is held by the SyncManager while handling sync actions (method handle()). Previously this wakelock was known as sync. Under bad data connectivity conditions, with poorly designed Sync providers this wakelock is held longer.
Related wakelocks: sync https://github.com/asksven/BetterBatteryStats-Knowledge-Base/wiki/sync
Which stated as above both similar and can cause same drainage if not tackled properly.
com.android.phone(under alarms,BBS)
Way to beat it:
1. Choose SETTINGS - WIRELESS CONTROLS - MOBILE NETWORKS -
2. uncheck everything unnecesary ie. "Data Roaming" and "Enable always-on mobile" -
3. Change setting on "Use only 2G networks", wait 10 seconds, then change it back.
4. Now try NETWORK OPERATORS. Here you will get a network error (Not the "com.android.phone" error)
Just continue and you'll get your wanted network.
The reason for this behavior is that android uses a new type of network and supports old ones.
Some countries dosen't use this new network.
When your android phone makes a handshake in these countries it'll accept without error, but when it returns to the new type it won't connect.
This must be a bug and you can solve / workaround this by doing the above
Remember: there is no app, that behaves in same way on different system. While it can drain on CM, it can be rock solid on the TW, and vice-versa. So, don't take those examples too serious and don't run to uninstall your apps just for preventive maintenance. Act per need. Anyways..I already mentioned a few things in the above posts but here is a few more added to what i said above and few new ones..
So, as listed above, our Top Chart leader is Media Scan:
- Media Scan – process, that will run after each fresh install & reboot. Typically takes about 10-15 minutes, runs on high CPU frequency. If stuck more than this, causes no Deep Sleep (can be seen in CPU Spy app) – you have an issue with Media Scan. It can stuck on large files directory – nothing to do here, unless you can reduce files number. Another case – problematic memory cluster, and there is only solution to back up your data, format your storages, and start over.
Stopping the process won't help much, as on next reboot it will resume. Suggestion - charge the battery to 100% before Media Scan starts to rebel, and let it finish.
Another case - stopping any download (browser, market) in the middle. Media scan can possibly stuck until next reboot.
- Media Scan stuck:
You probably have some corrupted files, on which it stuck. Backup, start to restore to the step it was OK, to find the culprit
Folder with many files - likely to stuck or to spend a lots of time to scan it. Do the math. If you have to have this folder (likely to be a cache folder) - disable your media scan.
I/O scheduler - CFQ sometimes being reported as taking longer time to media scan to complete. Try NOOP.
And, of course, sometimes it won't work without formatting emmc and starting over.
- Google apps/services:
- Google Plus - there were cases, when this app, with auto-sync left, was just hanging in the memory and caused drain.
- Google Currents - depends on system, but there were also cases, when the service left active on CPU resource after it was even completely killed in task manager.
- Google Location service - if you choose to update your location by GPS only, expect wakelock, when GPS can't lock on a stellite. Second case - if location being updated from internet, and your mobile data is in bad state (poor signal, etc.). And, of course, it depends on apps, who require location update, and there are a lot of such. Whenever you don't need it - disable your locations service in Settings.
- Google Maps - brightest example of wakelock, caused by requiring your location. If you want to run Google Maps, disable the Location services, and disable Maps in start-up.
- "The Holy Trinity" - Skype, Facebook, WhatsApp. Just be sure to kill the app and & services, when you don't need it.
- Same applies for a clients of a kind: Viber, Twitter, etc.
- “Energy savers” – Green Power, Timeriffic, etc. They mess with the system power policy, if you choose to enable/disable wi-fi, gps, data, Bluetooth, etc. Especially, Samsung’s one (power policy) is known as problematic.
- “Soft-buttons”, so called “power button savers” – like ScreenOff & Lock and such. Related to previous group. Let the hardware do the job.
- Task killers - If it kills some services in the middle of their action, it will cause’em start all over again or even stuck, and eat your precious battery resources. If you have to use it (like in case with JB 4.1 memory leak issue, do it manually).
-Sopcast - very likely to stuck in memory, and to cause multi_pdp wakelock. Worse, it may keep consuming your precious data. Suggestion: reboot right after you ended using Sopcast.
- *new* - Weak network signal. Pretty understable, but still - weak network signal can cause some weird wakelocks. Especially, when you're on autosync on with mobile data, and the signal is weak, you will get "*sync*com.google.android.apps...." wakleock, "genie.widget" is you're syncing "new&weather" thing, RILJ is very likely, etc.
LOL ! Nice one Goku
Mr Hofs said:
LOL ! Nice one Goku
Click to expand...
Click to collapse
thanks Hoff more to come mate:good:
Nice thread kakaroth , this should prevent alot of questions about wakelocks :good:
Shan89 said:
Nice thread kakaroth , this should prevent alot of questions about wakelocks :good:
Click to expand...
Click to collapse
More to come.
Sent from my HTC One X using xda premium
How about the AudioOut_4 wakelock(?
Sent from something that's BETTER THAN YOURS
XxVcVxX said:
How about the AudioOut_4 wakelock(?
Sent from something that's BETTER THAN YOURS
Click to expand...
Click to collapse
same as audioout_1 and audioout_3
EDIT:added a bit more info regarding those 2 wakelocks and provided another link as well if anyone needs to do more reading
http://forum.xda-developers.com/showthread.php?t=1629346
Goku80 said:
same as audioout_1 and audioout_3
EDIT:added a bit more info regarding those 2 wakelocks and provided another link as well if anyone needs to do more reading
http://forum.xda-developers.com/showthread.php?t=1629346
Click to expand...
Click to collapse
AudioOut_4 seems to be different. At least on my phone, it occurs when I leave a game, say NFSMW without actually killing it then turning the screen off.
Sent from something that's BETTER THAN YOURS
XxVcVxX said:
AudioOut_4 seems to be different. At least on my phone, it occurs when I leave a game, say NFSMW without actually killing it then turning the screen off.
Sent from something that's BETTER THAN YOURS
Click to expand...
Click to collapse
So just kill he game before you turn the screen off. Give me time and will add more.
Sent from my HTC One X using xda premium
XxVcVxX said:
AudioOut_4 seems to be different. At least on my phone, it occurs when I leave a game, say NFSMW without actually killing it then turning the screen off.
Sent from something that's BETTER THAN YOURS
Click to expand...
Click to collapse
Right been diving into more regarding this audioout_4 wakelock thing and from reading around the forums here and from searching google it is exactly as i stated from the start..
audio related as it states from its name and you talking about the game..now when you are turning the screen off the game is still running in the background...so of course that will drain your battery and will cause you the massive wakelock..
similar to one that i had...i was watching a video in the browser....i just pressed the home button and left the phone and screen was off..woke up the next day and the battery was flat..why? because in the background the video on the website i was checking out was still running...hence why the massive drain in battery..that is similar to your situation...
solution: always disable or kill what you are playing or watching or listening to on your phone
EDIT: check post 4 for more info
You deserve all my thanks for today
Sent from my HTC One X using xda premium
drali500 said:
You deserve all my thanks for today
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thanks but why
Sent from my HTC One X using xda premium
Goku80 said:
Thanks but why
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
It very good thread I searched for something like this many times and more you manged to sum it all for us... Thanks again
Sent from my HTC One X using xda premium
powerManagerService
Suspend_backoff
Added to post 3. plus added a bit more info as well in few of the wakelocks..more to come
guys if you want to post here your wakelocks and need help feel free to do so...will try my best to help out and see what is the problem..that way i can learn more and help you guys out in the process
Hey Goku80,
Very, very nice work man!
I do have a wakelock for your list, it's the st_wake_lock, like in this screenshot:
{
"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"
}
I already googled it, but couldn't find any useful information.
Could be it's only the name for a set of wakelocks together, I don't know really.
What can you tel me about it, and how to avoid it?
Love your thread man, very good work! :thumbup::beer:
PS: partial wakelocks look like this:
rkuijpers said:
Hey Goku80,
Very, very nice work man!
I do have a wakelock for your list, it's the st_wake_lock, like in this screenshot:
I already googled it, but couldn't find any useful information.
Could be it's only the name for a set of wakelocks together, I don't know really.
What can you tel me about it, and how to avoid it?
Love your thread man, very good work! :thumbup::beer:
PS: partial wakelocks look like this:
Click to expand...
Click to collapse
by any chance do you have volume keys set to wake the phone up?
Anyways to be honest i would not worry about what you have in the kernel wakelocks...mainly be worried what you have the highest in partial wakelocks..and from your second image so far so good....keep me posted when the battery goes to its lowest...
EDIT: just to add. Ignore "Kernel Wackelocks", cause its from the system itself, like connection & other stuff.
Related
There has been so much speculation on battery performance on the Sprint version that I wrote this logging program. This is the first stable Beta Version, Please PM me with bug reports (and as usual use at your own risk).
I know that it works for the CDMA version if someone wants to try it on the GSM version that would be great. Also Using the nuePower Battery driver for the Diamond give better resolution on the battery level.
What it logs:
1. a. Date and Time
b. Is AC Charger Attached
c. Battery Voltage
d. Battery Current (Discharge)
e. Battery Temperature
f. Battery level (%)
g. Pertinent System events:
a. Active Application
b. Speaker Phone Activity
c. Phone Radio Off/On
d. Phone Active Data Call (EVDO/1xRTT Activity)
e. No Phone Service
f. Phone Searching For Service
g. Bluetooth Power State On/off
h. Bluetooth Hands Free Audio in use (BT Headphones)
i. Bluetooth Hands Free Control in use (BT HF Headset)
j. WiFi Power On
k. WiFi Connected
l. Bluetooth Connections Count
m. Bluetooth Connections Descriptions
n. Cellular Connections Count
o. Cellular Connections Descriptions
p. Phone Call (Talking)
I have been unable to locate where HTC has hidden the charging current so if anyone could let me know that I would appreciate it.
Also, It dumps the data into a CSV file that you can pull into excel if you like. Please PM me with Bug Reports. There is a read.me version of the manual in the cab with a caution about logging to a storage card, please be aware of that if you plan on dumping your log to the storage card.
Version 0.2.3.130
New Features:
Support for Windows Mobile 5
Native QVGA Support (Properly Scales the Graph)
Can toggle between F and C for the Battery Temperature
Bug Fixes:
Properly deletes the downloaded file in the Benchmark test
Some additional Exception handling added
VERSION 0.2.1.105+ REQUIRES .NETCF 3.5!
I have uploaded a new version of the utility 0.1.1.58.
Includes the following Bug Fixes:
1) Now throws an update for every event. Previous Logic would drop events if another event occurred prior to the timed update.
2) Now allows the system to drop into Power mode D3 (sleep)
love the idea. will be reporting soon.
I have uploaded a new version with some reported bug fixes...
The following bug fixes are in place:
1) If multiple events occur while saving the log, a file in use exception would be thrown. It is now properly handled.
2) Visibility of the plots is now properly implemented.
After slugging through several long days of debugging and testing I have uploaded ver 0.2.1 of the battery log/diagnostics program.
What's new:
added mAH consumption counters for Data and Phone calls
Added a Battery Benchmark Module
Fixed a few miscellaneous bugs.
Benchmark Module details:
This module places the phone in a standard state (screen and backlight on, data connection active and Bluetooth radio on and discoverable). Then performs a 5 minute continuous data download, followed by a 20 minute telephone call. And saves a final report detailing power usage and AC adapter and charging times.
maybe my comments are silly but after those long discussions about battery draining in Raphael and diamond devices i find curious that nobody has said anything about this tool.
correct me if i'm wrong but this tool seems the best tool i've seen until know to check what the hell is draining our devices when in standby or calling or Data downloading or whatever.
i don't know too much about how it runs but i expect to learn it after some tests i will do.
I think that this tool will let me discover which running process is draining my battery, of course this tool won't tell it to me but after some testsenabling and disabling processes i will be able to see which one/s is/are the guilties.
I guess that the "ma" value that changes over time is per hour right? maybe PalladiumTD, could you explain me how to use this tool as if i would be a dummy, ( you can take out the "as if" if you want...
i don't understand the difference between "average current (ma)" and total usage (mah). The display doesn't change its contents when i switch between these options.
BTW it seems to run in my GSM device with unprotected Proven ROM 1.502. of course i can't install Nuepower driver.
is this tool trustable and accurate?
it doesn't seem to instantly react depending of what is running in the phone. it reacts after a while. ( of course i have it set to one second update)
and apparently it jumps from -78ma to -145ma and to -215ma without doing anything special. The Phone is just flashed with only battlog installed and running and it jumps between these values for no apparently reason.
Also i don't see any difference between having HDSP enabled or disabled (GPRS).
if i turn on Wifi, i see a big difference.
The benchmark test doesn't seem to run. it does not call and it does not download anything. (with wifi turned on)
fourcc said:
maybe my comments are silly but after those long discussions about battery draining in Raphael and diamond devices i find curious that nobody has said anything about this tool.
correct me if i'm wrong but this tool seems the best tool i've seen until know to check what the hell is draining our devices when in standby or calling or Data downloading or whatever.
i don't know too much about how it runs but i expect to learn it after some tests i will do.
I think that this tool will let me discover which running process is draining my battery, of course this tool won't tell it to me but after some testsenabling and disabling processes i will be able to see which one/s is/are the guilties.
I guess that the "ma" value that changes over time is per hour right? maybe PalladiumTD, could you explain me how to use this tool as if i would be a dummy, ( you can take out the "as if" if you want...
i don't understand the difference between "average current (ma)" and total usage (mah). The display doesn't change its contents when i switch between these options.
BTW it seems to run in my GSM device with unprotected Proven ROM 1.502. of course i can't install Nuepower driver.
is this tool trustable and accurate?
it doesn't seem to instantly react depending of what is running in the phone. it reacts after a while. ( of course i have it set to one second update)
and apparently it jumps from -78ma to -145ma and to -215ma without doing anything special. The Phone is just flashed with only battlog installed and running and it jumps between these values for no apparently reason.
Also i don't see any difference between having HDSP enabled or disabled (GPRS).
if i turn on Wifi, i see a big difference.
The benchmark test doesn't seem to run. it does not call and it does not download anything. (with wifi turned on)
Click to expand...
Click to collapse
I guess I really ought to write a manual?? Anyway the top for windows are live readings REPORTED by windows they are (left to right/top to bottom) Battery level, Battery Voltage, Battery Temperature, Current being drawn from the battery. These are realtime numbers.
The display average current and total Usage options on the update log menu apply to the Phone Current and Data Current boxes. (just below the 4 realtime boxes. These all total the current drawn during a voice or data call and allow you to see the average current drawn from the battery and the total power drawn from the battery (in mAH i.e. milliamp hours).
The fluctations in power draw may be real, I see them on the CDMA version when I am in a low signal area. the -78ma is close to what I have seen with the backlight off, the -120 - 150 ma when the backlight is on at 50%, the -215 may be an intermittent radio transmission (just speculation...)
With HDSP or GPRS enabled, you should only see a current draw when the radio is transmitting or receiving (i.e. when you are transfering data).
As far as accuracy, these numbers will be only as accurate as what the phone hardware is reporting. To keep it as generic as possible, I pull the values through the WinMo SystemStatus interface which makes it a bit sluggish in updating if other applications are running.
To run the test you must have .net Compact framework 3.5 loaded, it will not run without it. With that loaded, the benchmark should run (as it call only native WinMo functions). If you have .netCF3.5 loaded PM me and I'll see if we can troubleshoot..
One difference between the CDMA and GSM versions is that the CDMA hardware only reports current draw (as a positive number) I am guessing that The GSM phones report net current draw in the standard WinMo manner ,( i.e. negative for discharge, positive for charging and the number reported is the sum of the discharge and charging currents).
If there is interest (and someone could provide me with a log file from a GSM Phone while not connected to the charger, then when connected to the charger) I will make a GSM flavor of this utility, but will need some willing beta testers as I don't have a GSM Raphael...
Found via freewarepocketpc.net
Your Battlog utility is described on freewarepocketpc.net here: http://www.freewarepocketpc.net/ppc-download-battlog.html
Unfortunately, the download link points to Batti (another good utility) rather than Battlog.
I downloaded Battlog from your link here, and when trying to run Battlog the first time, I got the following error: BattLog.exe MissingMethodException Method not found: get_CellularSystemConnectedEvdo Microsoft.WindowsMobile.Status.SystemState. at System.Windows.Forms.Form.OnLoad(EventArgs e) at System.Windows.Forms.Form._SetVisibleNotify(Boolean fVis) at System.Windows.Forms.Control.set_Visible(Boolean value) at System.Windows.Forms.Application.Run(Form fm) at BatteryStatus.Program.Main() At the time when I ran this, my phone (PPC-6700 running WM5, .Net CF 2.0 & 3.5 installed) was connected to my computer via ActiveSync, the battery was fully charged, and the WiFi was turned on (and connected, I believe). the 1xRTT connection was not connected, as far as I know (no evdo on Cellular South in our area yet).
I'm no programmer (my expertise is in IT: remote access support, hardware, networking, etc.), but I hope this helps you. This looks like a worthwhile utility that has a lot of promise.
*edit*
I verified that I receive the same error if disconnected from ActiveSync, and after a soft reset. I also receive the error if WiFi is turned off and the 1xRTT connection is established.
Maybe I'm digging too deep; is this WM5 compatible, or WM6 only?
Sorry, I guess this could be a "bug report" and should have been PM'd to you. I didn't see that part until after I'd posted this.
*/edit*
TekServer said:
Your Battlog utility is described on freewarepocketpc.net here: http://www.freewarepocketpc.net/ppc-download-battlog.html
Unfortunately, the download link points to Batti (another good utility) rather than Battlog.
I downloaded Battlog from your link here, and when trying to run Battlog the first time, I got the following error: BattLog.exe MissingMethodException Method not found: get_CellularSystemConnectedEvdo Microsoft.WindowsMobile.Status.SystemState. at System.Windows.Forms.Form.OnLoad(EventArgs e) at System.Windows.Forms.Form._SetVisibleNotify(Boolean fVis) at System.Windows.Forms.Control.set_Visible(Boolean value) at System.Windows.Forms.Application.Run(Form fm) at BatteryStatus.Program.Main() At the time when I ran this, my phone (PPC-6700 running WM5, .Net CF 2.0 & 3.5 installed) was connected to my computer via ActiveSync, the battery was fully charged, and the WiFi was turned on (and connected, I believe). the 1xRTT connection was not connected, as far as I know (no evdo on Cellular South in our area yet).
I'm no programmer (my expertise is in IT: remote access support, hardware, networking, etc.), but I hope this helps you. This looks like a worthwhile utility that has a lot of promise.
Click to expand...
Click to collapse
Unfortunately, the many of the systemstate Classes that I use to detect the usage of the cellular radios aren't directly accessible from managed code in WM5. I will have see if I can code around it or remove some of the functionality when run on WM5. Thanks for the Info BTW.
You're welcome!
I know that I'm in a rapidly dwindling minority of WM5 users, but I love my PPC-6700, batter hog though it is, and I'm getting as much use as I can out of it before I choose a replacement from Cellular South's somewhat limited selection. (And I must admit, I am holding out hope that Google Android powered phones live up to their hype.)
Thank you for looking at this, and I'll be watching for a WM5 version!
Palladium, have you taken a look at the HTC-written TBattery app here?
http://forum.xda-developers.com/showthread.php?t=451646
It might help in your further development. Appreciate your work!
Da_G said:
Palladium, have you taken a look at the HTC-written TBattery app here?
http://forum.xda-developers.com/showthread.php?t=451646
It might help in your further development. Appreciate your work!
Click to expand...
Click to collapse
I will take a look at it (in detail that is) on the 7501A chipset it only reads battery level, temp and current. What is interesting is the from what I have read both the 75xx and 72xx chipsets use the PM7500 power management chip which is where those numbers should be coming from anyway. I'll see what I can learn from it... THANKS!!!
TekServer said:
You're welcome!
I know that I'm in a rapidly dwindling minority of WM5 users, but I love my PPC-6700, batter hog though it is, and I'm getting as much use as I can out of it before I choose a replacement from Cellular South's somewhat limited selection. (And I must admit, I am holding out hope that Google Android powered phones live up to their hype.)
Thank you for looking at this, and I'll be watching for a WM5 version!
Click to expand...
Click to collapse
I have just uploaded a new version. This version supports WinMo 5 as well as improved support for QVGA screens. there are a few other bug fixes and the ability to switch between deg F and C for the temperature display.
It works! Nice job; looks good.
A couple of points of constructive criticism (intended in the most positive and complimentary context!):
- I don't think the temperature is reporting correctly, at least on my Apache. It was reporting in C as 8.82 degrees, then when I switched to F it reported 16.94 degrees. As my phone is not currently in a freezer, I'm fairly certain this is off by a bit.
- The readme in the zip file is from the previous version.
I already love this program, and I've only scratched the surface. I've just started it logging and left it running; hopefully this will help me figure out which of the many apps I have is sucking my battery dry.
Thanks again!
TekServer said:
It works! Nice job; looks good.
A couple of points of constructive criticism (intended in the most positive and complimentary context!):
- I don't think the temperature is reporting correctly, at least on my Apache. It was reporting in C as 8.82 degrees, then when I switched to F it reported 16.94 degrees. As my phone is not currently in a freezer, I'm fairly certain this is off by a bit.
- The readme in the zip file is from the previous version.
I already love this program, and I've only scratched the surface. I've just started it logging and left it running; hopefully this will help me figure out which of the many apps I have is sucking my battery dry.
Thanks again!
Click to expand...
Click to collapse
Unfortunately this is a known bug, that has been low on my priority list. Basically the Standard WM Battery Dll report in degrees C*10, However, the Driver provided with the CDMA Touch Pro, reports in degrees C * 100. I just haven't gotten around to having the program check which platform it is running on and adjusting the calculation accordingly. So in the meantime your real temperature is the reported value * 10
on the readme, I'll re-upload with the updated Readme this afternoon.
Multiply by 10, got it. I can do that.
Thanks!
Thanks for this handy little program. I am used to the HTC WinMo battery drain devices but always like to see what might be aiding in the drainage.
HI Palladium,
Thumbs up for nice work.
However I'm not able to run the 0.2.3.130 release on my O2-Graphite w. WM 6. I get: "This app. requires a newer ver. of the microsoft.NET Compact Framework"
Hope this information is of any use to you
Regards
Steen
Sorry, My original post wasn't clear on this point, all versions from 2.1.105 forward require .NET CF 3.5. If you download it here Everything should work fine after you install that.
Palladium TD.....
Thanks to a post on another thread, I found your very nicely done program. I have some 'funny' out of the blue battery drains that your program may help me isolate.
I have v0.2.3.130 beta installed on my US ROM1.93 GSM Diamond. It installed fine, tracks current use and temp (/10) and logs the data. Very easy to pull into excel for analysis. I've only used it for a day now and do note the following issues (which may be me not executing correctly or the beta)
Voltage and temp graphs track exactly together and without a scale value
No response from the two Icons on the left (one looks like a help?)
I don't see any response to the "Display Total Usage mAh
Very excellent work, and if I can support, let me know.
Thanks
If you haven't gone out to get an extended battery, try this and give feedback. I have tried it and it does great wonders for the stock battery for now. You can locate this in the market.
{
"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"
}
Seems counterproductive to have a program running that extends your battery.
JuiceDefender has been doing this for ages. I'll try it out to see how it compares, but I doubt it could improve on it at all. Doesn't look like there are any unique features.
IM trying this on my EVO 4G and I am not sure if it is really SYNCING my account at all with this program... I have left auto-sync turned on and all this program is doing is turning off data when screen is off and back on every 2 hours and also turns it on when I unlock the screen.
However, I dont know how this will sync my accounts.. if I data is off and a scheduled sync comes, will the data come back on?
so far I dont think it does.. I was testing GREEN POWER which had a setting to sync every so many minutes.. but it only went up to every 30 minutes which killed my battery syncing all accounts every 30 minutes..
I want to be able to use one of these battery saver programs but still be able to SYNC account to each accounts time schedule for EMAIL, facebook, weather, etc
some are every 2 hours.. some ever 6, every 8 etc
Thanks...
Hello everyone. My name is Michael and I'm the Product Manager for BatteryXL.
I'm very pleased and pleasantly surprised, to be honest, that someone made a thread about my app on such an awesome site, XDA.
First off, this app is in Beta. It's not perfect nor complete by any means and it will continue to be developed and polished for the foreseeable future.
About BatteryXL's Smart Schedules:
In the Smart Settings menu there is a field called "Smart Schedule"
Here you can select WiFi, Data, and(or) (Auto)Sync.
Then you select a Frequency to connect (15m, 30m, 45m, 1h, 2,h, 5h) and Duration of connection (30s, 1m, etc).
To answer the gentleman's question about Sync:
If Sync is selected, then WiFi or Data (or both) must also be selected. Therefore, whenever a Smart Schedule event occurs including Sync then an internet connection will be initiated (if available).
Hope this clears things up. AutoSync optimization is one of my goals for the future. I want this app to be able to save battery without any unreasonable lag time between emails, social network updates.
Again, please feel free to address any further concerns or questions.
Michael Malley | BatteryXL Product Manager
[email protected]
[email protected]
@BatteryXL
BatteryXL said:
Hello everyone. My name is Michael and I'm the Product Manager for BatteryXL.
I'm very pleased and pleasantly surprised, to be honest, that someone made a thread about my app on such an awesome site, XDA.
First off, this app is in Beta. It's not perfect nor complete by any means and it will continue to be developed and polished for the foreseeable future.
About BatteryXL's Smart Schedules:
In the Smart Settings menu there is a field called "Smart Schedule"
Here you can select WiFi, Data, and(or) (Auto)Sync.
Then you select a Frequency to connect (15m, 30m, 45m, 1h, 2,h, 5h) and Duration of connection (30s, 1m, etc).
To answer the gentleman's question about Sync:
If Sync is selected, then WiFi or Data (or both) must also be selected. Therefore, whenever a Smart Schedule event occurs including Sync then an internet connection will be initiated (if available).
Hope this clears things up. AutoSync optimization is one of my goals for the future. I want this app to be able to save battery without any unreasonable lag time between emails, social network updates.
Again, please feel free to address any further concerns or questions.
Michael Malley | BatteryXL Product Manager
[email protected]
[email protected]
@BatteryXL
Click to expand...
Click to collapse
Still confused. If your program has turned data off but then one of my accounts is trying to sync based on its sync schedule in accounts and sync (in Android system settings), will data be turned back on to sync and then off again? I have the setting in your program to turn on data for 5 minutes every 2
Hours along with sync which i also leave that setting on for screen on and off. Let me know.
Sent from my Touchpad using Tapatalk
Sorry to say this, but this app looks like a Juice Defender rip off: it has exactly the same options (some are still missing) and it has a different interface.
Does it actually bring anything different from Juice Defender?
pedmond said:
Sorry to say this, but this app looks like a Juice Defender rip off: it has exactly the same options (some are still missing) and it has a different interface.
Does it actually bring anything different from Juice Defender?
Click to expand...
Click to collapse
Yeah, it brings a GPS lock that doesn't turn off! Click off GPS in the app, exit and it comes right back up until I turned off GPS with the power widget. Having to bother with turning GPS on and off when I wasn't using any other app that needed it made it an instant uninstall. Honestly, the app seemed shady to me, and don't see a reason to use it over JuiceDefender if you are having battery issues.
cvmaas said:
Yeah, it brings a GPS lock that doesn't turn off! Click off GPS in the app, exit and it comes right back up until I turned off GPS with the power widget. Having to bother with turning GPS on and off when I wasn't using any other app that needed it made it an instant uninstall. Honestly, the app seemed shady to me, and don't see a reason to use it over JuiceDefender if you are having battery issues.
Click to expand...
Click to collapse
Hi cvmass,
The only GPS controls BatteryXL features are a manual on/off (which shares the same functionality as the Power Control widget) and automatic enable/disable based on various events like 'screen unlock'.
If your GPS is turning on or off unexpectedly then that is obviously a bug related to your hardware and not part of the intended user experience. If you want to send me your batteryxl.txt (log) I could work on fixing the problem.
We're not trying to rip-off JD, it's a matter of us trying to create the best app we can to help everyone get more out of their Android devices. Saying we're shady is like saying Android copied iPhone because both has touchscreens, apps, sync, phone, etc... This is a matter of convergent design were in order to save battery power, both apps are regulating your connections based on a series conditions and triggers. I'll be frank, we've used JD here in the lab, frankly we felt like we can do better and that's why we made this app.
dahauss said:
Still confused. If your program has turned data off but then one of my accounts is trying to sync based on its sync schedule in accounts and sync (in Android system settings), will data be turned back on to sync and then off again? I have the setting in your program to turn on data for 5 minutes every 2
Hours along with sync which i also leave that setting on for screen on and off. Let me know.
Sent from my Touchpad using Tapatalk
Click to expand...
Click to collapse
Currently, the smart (sync) schedule only operates while the screen is off. but, this will change as of v1.2.4.
According to your settings mentioned above, BatteryXL will enable autosync every 2 hours for an interval of 5 mins. During this 5 mins, all your apps that have synced information are polled for updates.
The problem with the smart schedule now is with push services that assume you are constantly connected to the web. so sometimes, syncs get missed. we are working on it.
Let me know if you have more questions.
I've used and uninstalled BatteryXL twice now. It currently offers a night mode which juicedefender doesn't (for free anyway). First time I got rid of it due to instability (most likely culprit) the second time is because of the data finesse.
I only want to use cellular data when wifi is not available, but when you enable mobile data BXL first of all uses cellular data then wifi is turned on using that. If you turn off mobile data it actually switches off all mobile data so wifi won't work either for WAN transfers. I need option to keep cellular data disabled but leave mobile data on.
Thank you so much for bringing that to our attention - we'll add that to the features list to be added soon. So BatteryXL will basically disable cellular when wifi connects successfully and enable it when wifi is off or can't find a network.
It might be even better to make the mobile data button actually mean cellular data and not mobile data as this is what I thought it meant so was confused when it was turning off ability for wifi to fetch data. You could make mobile data an optional component elsewhere as I think this is a rarer item.
Or add an additional icon for cell data to the common row you have in every state paragraph. This makes the control more granular and ensures no cell data will ever be used even without wifi (which is what I would want for many scenarios anyway). Re-reading my post I can see how I misstated that! Certainly both scenarios could be provided for. Personally it depends when I need data, I can change my calling plan accordingly from month to month.
EDIT: Mobile data only seems to affect cellular data (as you'd expect) but why when it is disabled in BXL does wifi go 'grey' and not get any data, odd. This is why I thought it throttled any data and the toddle for cell was separate.
Does this app still make the GPS constantly look for a signal? I liked the UI a bit better than JD, but it just didn't work when I tried it.
9kracing said:
Does this app still make the GPS constantly look for a signal? I liked the UI a bit better than JD, but it just didn't work when I tried it.
Click to expand...
Click to collapse
That sounds like GPS partially enabled, like the GPS is on but A-GPS isn't. When that happens to me apps like navigation constantly moan about finding location before they can function.
Fatila said:
That sounds like GPS partially enabled, like the GPS is on but A-GPS isn't. When that happens to me apps like navigation constantly moan about finding location before they can function.
Click to expand...
Click to collapse
I had to set the program to turn off GPS when screen off. The program does something to my GPS that eats battery if I leave it on while using this program.
Sent from my EVO4G using Tapatalk.
BXL Uninstall question
I installed it on my I9000 but it was to complicated for me and could not get it to work along with my Email client so I uninstalled it, rebooted my phone and got something I have never seen before when my phone was booted, a message from Superuser stating that System is asking for superuser permission.
Is that natural or is it something that BXL left that caused this?
I'm using Doc's Master ICS V5 ROM.
Thanks
Ophir
I'm not too sure about this app. Been trying it for a day and can see somewhat of a difference, but nothing drastic..
One thing I do like about BatteryXL over JD or almost all the other similar apps is that it's not only free and not crippleware, but there are no ads. I hope it stays that way!
I have had some issues with the app locking up, but acceptable considering it's in beta - hopefully still under active development and improving.
i just tried this app and uninstalled it after it started to make phone calls all by itself to *22899. i would end the call and then it would call it right back. seems like a good app, and could work but that turned me off of it. not sure about the whole mobile data off option though.
Hello everyone, i see here to collect and post some known and maybe unknown tips and tricks with some important information, hoping this will be useful for users, especially for newbies.
Any more tips, tricks and suggestions from users are always welcomed. And please feel free to make corrections for any wrong or missed information in this post
{
"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"
}
Preface:
Samsung Galaxy Y (Young) (GT-S5360) is an Android-based smartphone by Samsung, announced in August 2011.
Galaxy Y features: Android 2.3.5 Gingerbread OS (upgradable to v2.3.6) with Samsung's proprietary TouchWiz user interface, and has integrated social networking apps and multimedia features, including Google Voice Search, and 5.1 channel audio enhancements.It also has a standard 3.5 mm 4-pin audio jack.
The device sports a 832 MHz ARMv6 processor, 180 MB of internal memory and supports up to 32 GB of removable storage through a microSD card. The phone has a 2 MP camera, a screen with a 240x320 resolution and a multitouch interface with the optional SWYPE virtual keyboard. The phone offers connectivity options such as 3G, WiFi, Bluetooth 3.0 and also GPS. It supports 3G HSDPA speeds of up to 7.2 Mbit/s. The device allows tethering with other Wi-Fi enabled devices, which enables users to share the phone's Internet connection.
The Galaxy Y uses a single-core 832 MHz ARMv6 along with Broadcom BCM2763 VideoCore IV.
The Galaxy Y features 290 MB of RAM and 250 MB of dedicated flash internal storage (190 MB user available).
It has microSDHC slot (up to 32 GB).
The Galaxy Y uses a 76.2-millimetre (3.00 in) QVGA (320x240) TFT LCD capacitive touchscreen which has a Pixel density (PPI) of '133'.
On the back of the device is a 2 megapixel fixed focus camera without flash that can record videos in up to a maximum QVGA Resolution. Galaxy Y does not have a front facing camera.
Click to expand...
Click to collapse
Questions & Answers
Q Can i make a screen shot on stock firmware?
A Yes you can! user doesn’t need to root the device or employ third-party apps just to take a photo of what's happening on screen. Taking a screenshot is simple, To take screenshots you have to first hold down the home key and then press the power/lock key.Don't hold the home key too long otherwise lock button will not work. As you hold the home button immediately press the power/lock button to capture the screenshot.
Q My Young screen is turning on by itself, what is happening?
A It is caused by an application, usually by live wallpapers, try to find it and delete it, or install an antivirus app., i recommend Dr.Web Anti-virus, scan, delete, wipe cache and dalvik (optional).
Q how can i make the volume of my SGY louder?
A Most phones have their volumes limited by local laws to protect our hearing. There is a way to boost your volume however. Go to the Android Market and download an App called Volume+ (Sound Boost). There is also a free version called Volume+ Free (be aware, do not raise it too much, it can damage the speaker).
Q How to remove an icon from the home screen?
A To remove an icon from the home screen, simply press on it, hold and drag to the Trash at the bottom of the screen.
Q How to dial contacts with a quick swipe?
A Instead of tapping on the contact name and then tapping on the option to dial, you can simply swipe right with your finger on the contact's name and it will directly call him/her. By swiping left, you can quickly send a message to the contact.
Q How to hide particular files from showing up in Gallery or Music Player?
A Sometimes there are things that we do not want our friends or relatives seeing,So instead of deleting the particular files or moving them to your computer all of the time, you can hide them in just a few seconds. All you need to do is create a folder called .nomedia wherever you want on your sdcard (you can do this from your phone by selecting Menu button -> Create Folder), then put the particular files on that folder and the files will not appear in media apps. You can also press the Menu key on your phone, then choose More -> go to Settings and untick the "Show hidden files" option if it is enabled. That way you will hide the .nomedia folder from the My Files app as well.
Q Can i make Voice actions?
A Yes you can, if you've got the Google Search widget on your home screen, tap on the little microphone which you see in the widget and speak out your command. Example: Tap on the microphone and say "Send an e-mail". An e-mail popup will appear giving you the options to type in the recipent's e-mail, subject and message.
Q I have forgotten my unlock pattern, what to do?
A If you have forgotten your custom unlock pattern, then don't panic. After 5 unsuccessful tries a button should appear saying 'Forgot pattern'. Press this and you will be asked to enter your Gmail username/password. The phone will then ask for a new unlock pattern. If you don't have a Gmail account, then you might have to either call your carrier or factory reset your phone.
Q How to calibrate my Galaxy Y?
A Device calibration is required when the auto rotation sensor does not work properly. What happens actually that if your galaxy y is not calibrated properly, then screen will not rotate when you turn your device and screen rotate when you do not rotate your device. To calibrate galaxy y steps are given below:
- Go to Settings>Display>Horizontal calibration.
- Place the device on a flat surface and click calibrate. Wait for a few seconds.
Now your galaxy y is calibrated and you won’t get any auto rotation sensor errors.
Q How to quickly delete/uninstall Android Apps?
A You can quickly delete or uninstall an android app from galaxy y with this trick in just one second, as galaxy y task manager will take some time to uninstall large size apps. With this trick you can uninstall any app within one second no matter how big the size of app is. To do this follow steps below:
- Open all apps by clicking the all apps button on home screen.
- Click menu button of your phone and select "Edit".You will see a small minus mark on all downloaded apps.
- To quickly delete any app just click it and that app will be deleted in just one second.
Q How can i use custom ringtones, alarms, sms notifications?
A To use custom ringtones for your phone ringtone, your alarm or your text message notification, simply copy an MP3 file to one of the following folders:
/sdcard/media/audio/ringtones
/sdcard/media/audio/alarms
/sdcard/media/audio/notifications
If they don't already exist, then create a new folder. The file will then show up when you want to change your ringtones.
Q How can i Setup SIM Change Alert On Galaxy Y?
A If you enable the SIM change alert feature then you will be notified by the phone about the one who have your phone or stole it.If this feature is active, then when somebody inserts a new SIM then the phone automatically sends a messages about the thief giving you the information about his phone number on a different phone number that you enter as alert message recipients. To enable SIM change alert do as follows:
- First of all enable data connection (or wifi) and go to Settings>Location and security.
- Under “Find my mobile” check “SIM change alert”.It will ask you to login with your Samsung account.If you do not have a Samsung account then sign up. After signing up, again check "SIM change alert" and enter your Samsung account password to activate this feature.
- Now click “Alert message recipients”. Enter the password and enter some phone numbers with country codes. Click the green plus sign to add numbers and red minus sign to delete a number.
- Scroll down a little bit and you will see “SMS message”. You can edit this message like “Keep this message, My phone has been stolen by somebody”. This text will be forwarded to all the numbers that you entered as alert message recipients when SIM is changed by a thief.
- Now put a check mark in “Remote controls” and enter your Samsung account password to enable it. If this feature is enabled then you can track and locate your lost galaxy y with “Samsung Dive”. With Samsung Dive you can track, locate and delete private data on your phone remotely.
Q Sometimes i lose packet data (3G) when i turn it off then on, i turn off then turn on my Youmg to enable packet data again?
A There is no need to turn your phone off and on to re-enable packet data, just long press on power button, enable airplane mode for 3-5 seconds then disable it.
Q How To Make my Young Run Faster?
A sometime you will find lack of memory due to various applications running in background. These apps waste android system memory. So you should clear them off if they are not used. You can clear them by using taskmanager. Galaxy y has a built taskmanager which will do this work for you. Open taskmanager by holding home button then move on to the RAM tab then click clear memory. It will free the RAM and save memory. Aslo you can download two more applications which are android assistant and app cache cleaner. For quick boost use android assistant and always clean the cache of various apps by using app cache cleaner.These apps are important for your smartphone.
Q How To Backup my Favourite Apps On my Young?
A You can always make a backup of your android apps on Galaxy y downloaded from play store (android market).For this you have to download an app called android assistant.Download it from play store.After downloading it open it and move to tools ,you will see apps and backup.Click on this icon and you will be shown a list of apps you wish to backup.Select the apps you want to backup.The apps will
be backed up to the memory card in apk format. Later you don't need to download them from play store (android market).You can directly install them from memory card.But during installing them your phone will block them as it doesn't allows non market apps to install. For this go to settings, click applications and select allow installation of non market apps. Then your phone will not block them.
Q How can i Switch my Young Network between 2G & 3G?
A In Galaxy y you can switch your phone's network from 2G to 3G or reverse. For this go to settings click wireless and networks, click mobile networks, move to network mode, select GSM or WCDMA(3G). now enable data traffic if you want to use internet.
Q How to Change Contact Picture?
A If you want to put a pic on your phone's contact then you have to move them first to android phone. Make a backup of your contacts because if phone is wiped then contacts will be deleted. To backup contacts on galaxy y open contacts click menu and select "Import/Export", Now choose "Export to SD card".Click yes. The contact list be backed up in "vcf format". And now you can restore the contacts to phone or sim through the import/export option. Now open contacts, click the plus sign to add contacts.Choose phone.Enter all details and click the plus sign on the pic. You can select the pic from album or can take picture from camera. Click save and you are done.
Q How to Restart Samsung Galaxy Y>
A Press and hold home and power key at same time until your phone turns off then release the buttons. Galaxy Y will restart. Restarting may be required if phone is hanged. This trick will let you to restart your galaxy y without turning it off and again starting it.
Q Is there a hidden wallpaper?
A Goto settings > About phone > Android version. Click many times on "Android version" until you see a wallpaper.
Q I rooted my Young, what to do next?
A It is recommended to make a nandroid backup immediately.
Q What is the easiest way to install samsung driver?
A The easiest way is to install Samsung Kies.
Q How can i flash stock firmware on my Young?
A See Doky73 thread.
Click to expand...
Click to collapse
Rooting:
Rooting is often performed with the goal of overcoming limitations that carriers and hardware manufacturers put on some devices, resulting in the ability to alter or replace system applications and settings, run specialized apps that require administrator-level permissions, or perform other operations that are otherwise inaccessible to a normal Android user. Rooting is similar to jailbreaking devices running the Apple iOS operating system. On Android, rooting can also facilitate the complete removal and replacement of the device's operating system, usually with a more recent release of its current operating system. Rooting enables all the user-installed applications to run privileged commands that are typically unavailable to the devices in their stock configuration.
Legality: The Free Software Foundation Europe argues that it is legal to root or flash any device. According to the European Directive 1999/44/CE, replacing the original operating system with another does not void the statutory warranty that covers the hardware of the device for two years unless the seller can prove that the modification caused the defect.
On July 26, 2010, the United States announced a new exemption making it officially legal to root a device and run unauthorized third-party applications, as well as the ability to unlock any cell phone for use on multiple carriers.
Safety: I Have always said that the person should learn the Android OS before rooting. It is a good idea to have an idea of what rooting is doing and what it will affect. I would say spend your time really learning the OS which is not a small task. Then, if you still feel like it, go ahead and root. While rooting can help you learn many things about your device, it also can reap very bad consequences, such as:
-Bricking your phone (or in an easier way to explain, making your phone a pretty paper weight).
-Corrupting core files.
-Voiding phone warranty.
-Have your phone open to malicious software and applications that can do serious harm to your phone.
As you can see, it can reap very negative things. I have read/seen people who have literally had to buy brand new phones because they tried the latest and greatest rom. Rooting is essentially something that you must take at your own risk & caution. Generally, if you follow exactly the procedure of rooting made by developers, you will be more likely on the safe side.
Root process: See Reynaldoj thread
Click to expand...
Click to collapse
Battery Conservation Tips:
-Set Brightness at low level: Brightness can lure a lot of battery if not changed intelligently. if you want to save more battery drain, set brightness manually at low level depending on the external amount of light.
-Remove Live Wallpapers: Using a live wallpaper is another battery sucking feature. If you turn out to be truly saving battery, make sure not to use any live wallpaper.
-Disable Location and GPS services: Keeping GPS ON at all times, decreases your battery life, so its better to disable it while not in use. To disable, go to Settings > Location and Secutity > and switch it off.
-Disable Wi-Fi or Mobile Data when not in use: Try to avoid situations when you keep your Wifi or Mobile Data ON even when the phone is set in standby.
-Manage Sync carefully: Keeping the Sync ON all the time is another reason for decreased battery life. Enable it anytime you want, manage your emails or services and again turn it off. For those who are on work and want real-time push notifications are advised not to follow this tip.
-Turn OFF screen touch sounds: To save a little more on battery, its better to switch off the screen touch sounds. To do so, go to Settings > Sound and untick Audible touch tones and Audible selection and Screen lock sound.
-Turn OFF bluetooth: Disabling bluetooth when you are not using it, is another way to save battery juice.
-Follow the method of full charge and full discharge: Don’t put your phone on charging when there is the battery remaining it for another few hours unless it’s very important. Charge it when your battery is about to get totally discharged and when you put it for charging, let it get charged totally.
-Set sleep time: Check the Sleep setting (under Display) and make sure it is set to 1 minute or less.
Keep calls short: This is obvious, but how many times have you heard people on their mobile phone say, "I think my battery’s dying," and then continue their conversation for several minutes? Sometimes, the dying battery is just an excuse to get off the phone (and a good one, at that), but if you really need to conserve the battery, limit your talk time.
-Turn OFF mobile network when not in range: Its very often that you lose the mobile network when you are travelling, so its advisable to turn OFF the mobile network by switching ON Airplane mode.
- After each month remove your battery from mobile phone and let it rest for an hour, it will give battery a breath and it will last longer.
-You should not have to turn off your phone to charge it. Most battery chargers deliver more than enough current to power your phone and charge it at the same time. Doing so will not lengthen the charge time, and leaving a phone on allows the user to be aware of its fuel gauge, so that you can remove it when the battery is full.
-When using a car charger, do not charge the battery when the inside temperature of your car is hot. Wait until the car has cooled before you plug in the phone.
Click to expand...
Click to collapse
Galaxy Young secret codes:
*#*#4636#*#* Testing menu(Phone, Battery & Wifi Info, Usage Statistics).
*#06# MEID number(Display's your IMEI).
*#272*Phone’s IMEI Here# change phone CSC (NB: it will wipe your data).
*#*#2432546#*#* Checkin(Manually check for System Updates).
*#*#44336#*#* software build date and time.
*#197328640# Service Mode menu
*#7353# Test menu: you can check screen, speaker, sensors.......
*#*#8255#*#* For Google Talk service monitoring.
*#1234# to check software version of phone.
*#12580*369# to check software and hardware information.
*#0228# Battery status (ADC, RSSI reading)
*#32489# Service mode
*#7780# factory data reset
*#*#232339#*#* OR *#*#526#*#* OR *#*#528#*#* Wireless Lan Tests
*#*#232338#*#* Displays Wi-Fi Mac-address
*#*#0*#*#* LCD display test
*#*#0673#*#* OR *#*#0289#*#* Audio test
*#*#0842#*#* Vibration test
*#*#2663#*#* Displays touch-screen version
*#*#2664#*#* Touch-Screen test
*#*#0588#*#* Proximity sensor test
*#*#232331#*#* Bluetooth test
Click to expand...
Click to collapse
Recommendations:
-Too loud wallpapers may sometimes disturb the look of your home screen and make the icons quite invisible, simple or a less-colored wallpapers are always suggested as to be the best choice. But your choice is what matters.
- Disable USB debugging when it is not in use. Leaving USB debugging enabled makes your phone vulnerable (e.g. lock pattern can be reset).
- Use only essential widgets on your home screen - each widget consumes memory and processing power which can slow your down your phone.
- Uninstall apps that you don't use - after awhile your phone can get cluttered as some Apps are designed to always run in the background. If you rarely use an App, then uninstall it to free up memory and CPU resource.
- It is best to avoid task killers such as Advanced Task Killer. Android is designed to automatically pre-load certain applications, even if you don't load them yourself. If it starts to run low on memory, it will smartly unload the oldest running apps automatically. Manually killing tasks will only mean they get loaded in memory again. Task killers can make the phone slow, laggy, or drain battery life more quickly.
- Avoid putting your phone in direct sunlight, it may affect touch screen & your battery performance.
- Check rom/kernel.zip md5 before flashing if it is convenient.
- Always update applications, if available, for better performance.
- Make a backup of your data, applications, contacts...always ready to restore from your computer.
- Read, read and read before you mess with your phone.
- Always be sure that you are flashing the right thing for your Young variant.
- If you do not know what you are doing, so don't do it .
Click to expand...
Click to collapse
Did you finish reading? Please press Thanks & Rating buttons
Pretty much a duplicate of this thread >>> http://forum.xda-developers.com/showthread.php?t=1974338
Thread closed.
Edit: OK, there is some crossover between the two topics but this one has some stuff the other doesn't and vice versa. Thread unlocked.
Jonny said:
Pretty much a duplicate of this thread >>> http://forum.xda-developers.com/showthread.php?t=1974338
Thread closed.
Edit: OK, there is some crossover between the two topics but this one has some stuff the other doesn't and vice versa. Thread unlocked.
Click to expand...
Click to collapse
thx very much
Nice long thread appreciate ur work...
Sent from my GT-S5360 using xda app-developers app
is their a code to know how old is our android phone?? is it written here? i havent read it all..
☆★☆★☆★☆★☆★☆★☆★☆★
deathfalls said:
is their a code to know how old is our android phone?? is it written here? i havent read it all..
☆★☆★☆★☆★☆★☆★☆★☆★
Click to expand...
Click to collapse
see software and hardware information code (I think)
Edit: try *#*#44336#*#* for manufacturing date
thx, very useful post :good:
wy this thread is not stickied?
Nice....really will help newbies
Sent from my GT-S5360 using xda app-developers app
Added to the Roll-Up stickie Useful Thread - Collection Sticky - Everything You Need for Galaxy Y
this is very cool
Nice guide OP
Thanks for this especially for the secret codes :good:
keep the good work :good:
is it safe to change my csc ??? because my csc is not supported by kies.
Thanks, nice guide for a newbie like me
Sent from my GT-S5360 using xda app-developers app
Mostsh said:
is it safe to change my csc ??? because my csc is not supported by kies.
Click to expand...
Click to collapse
Yes. But it will wipe your data
Sent from my Galaxy using xda premium
The kernel build date
samersh72 said:
see software and hardware information code (I think)
Edit: try *#*#44336#*#* for manufacturing date
Click to expand...
Click to collapse
The code shows PDA, CSC and Modem versions. The build date is the date of build of the kernel. With updates, the date will also change
review:
causes eye strain to read,
use
PHP:
[quote][/quote] and [hide][/hide]
next time
good guide although existent but well compiled, you can add more later
SaketJoshi said:
The code shows PDA, CSC and Modem versions. The build date is the date of build of the kernel. With updates, the date will also change
Click to expand...
Click to collapse
you are right about *#*#44336#*#*, forget about it. the manufacturing date of hardware is "RF Cal date" you can find it when you dial *#12580*369#.
or type *#197328640#, This will open the Service Mode menu on your Galaxy device. Select the option N. 2, that is “Version Info”. On the next screen, select ‘HW Version” (here HW means hardware). Now you will see another set of options on the next screen. Now tap on “Read CAL Date”, and bingo!
OP updated
deathnotice01 said:
review:
causes eye strain to read,
use
PHP:
and [hide][/hide]
next time
good guide although existent but well compiled, you can add more later
Click to expand...
Click to collapse
thanks for your advice :good:
Thnx...
Will never move this thread from my subscription list....:thumbup:
Noticing your Galaxy S6 battery is draining too fast? This thread can help.
Part of the problem lies within a memory leak which is a known problem that Samsung is aware of and is reportedly patching in an upcoming update.
The other issue is Samsung attempts to load everything into memory and run several services in the background as well as hard loading the phone with bloatware.
Here is how I gained 30% better battery performance. Guaranteed
*Prerequisites
*Need to be rooted for every tip to work.
1. Disable anything you consider bloatware
2. Go to settings then application manager and disable both ANT radio service apps. You don't need this. Causes massive battery drain. Google it if you don't believe me.
3. Go to the app store and download "Servicely" from Franco. Paid app but worth the money...trust me. (Need root)
4. Once in servicely add running services and apps to your hit list, choose start at boot and run hit list while screen is off.
5. Reboot your phone. Give your phone a full charge and see the difference
Attached is a screenshot of realistic usage. I was on a poor lte signal for 9 hours and conducted several calls and used my phone moderately heavy. As you can see i got through my entire work day and still have 6 hours left at moderately heavy use.
Remember, this is realistic. I could have shown you a screenshot showing 18 hours left after only using it 1 hour. What I'm showing is a legit 9 hours of usage. Before I made these tweaks I would be at 10% battery or less after nine hours of the same usage.
Post your screenshots after 24-48 hours and let's see how much you are saving.
Follow me on twitter @bash_array
I think disabling the ant radios will disable certain low-level bluetooth connections to hrm's and other fitness equipment (among other things). You may not want to disable these.
Your right!
i have havd the ant service disable for some time now and I use a fitbit one that is low bluetooth device and there are no issues.
ant service when i look it up says its for ant devices only not low bluetooth devices but i could be wrong
fachadick said:
I think disabling the ant radios will disable certain low-level bluetooth connections to hrm's and other fitness equipment (among other things). You may not want to disable these.
Click to expand...
Click to collapse
Incorrect. Disabling ANT will not affect wearables or any peripheral. ANT is supposed to save battery while using Bluetooth but it has the opposite affect. Massive drain on battery and not needed.
cyberone3 said:
i have havd the ant service disable for some time now and I use a fitbit one that is low bluetooth device and there are no issues.
ant service when i look it up says its for ant devices only not low bluetooth devices but i could be wrong
Click to expand...
Click to collapse
Correct. Very few devices sold in the US are even ANT compatible
bash_array said:
Incorrect. Disabling ANT will not affect wearables or any peripheral. ANT is supposed to save battery while using Bluetooth but it has the opposite affect. Massive drain on battery and not needed.
Click to expand...
Click to collapse
bash_array said:
Correct. Very few devices sold in the US are even ANT compatible
Click to expand...
Click to collapse
That's interesting - here's the information from the play store. I haven't noticed any ant services using any battery at all on my end, but I don't use s-health which ties into this - it says that ant services only gets used when a compatible service sees it. Here's the full list of devices/apps that make use of ant services.
This service is similar to the system components that enable other forms of wireless connectivity on your phone (ie. WiFi, NFC) and will not run or use system resources unless you start an app that requires ANT wireless communication. It is pre-installed by your device manufacturer to allow the built-in ANT wireless hardware already present in your mobile device to operate. If you do not intend to use this feature there will be no impact to your system and no further action is required.
If this service is not pre-installed on your phone you may still be able to enable ANT+ communication, see http://www.thisisant.com/developer/ant/ant-in-android/ for more info.
What is ANT?
ANT is an extremely power efficient wireless communication technology. ANT allows you to connect to, and make use of various other ANT or ANT+ devices. Today, this service allows you to connect to popular interoperable ANT+ sport/fitness/health devices such as heart rate sensors, fitness equipment, cycling products, weight scales and more. In the future it will be possible to use ANT to enable a myriad of new applications from your mobile device, such as home automation control of lighting, temperature and door lock functions. Visit www.thisisant.com for more info.
How to use:
This system service cannot be launched directly. It will run automatically in the background whenever any application that requires ANT wireless communication is used.
ANT+ enabled applications also typically require downloading the ANT+ Plugins http://play.google.com/store/apps/details?id=com.dsi.ant.plugins.antplus
Some popular apps enhanced with ANT+:
* Samsung S Health
* Garmin Fit™
* SportsTracker by STL
* Endomondo
* My Tracks
* Run.GPS Trainer UV
* IpBike, IpWatts, IpPeloton, IpSmartHr
* Selfloops
* SportyPal
* MapMyFITNESS/RIDE/RUN/WALK+/HIKE/DOGWALK
Click to expand...
Click to collapse
i have found that google location is causing my battery drain i turned it off and charge my phone before it was sleeping less than 50% now at 70% at the moment and going up
As of today, there are apps in development (some in roll-out already) to collect fitness data like heart-rates from individuals to correlate the spreading of the COVID-19 pandemic.
Source: https://www.thelancet.com/journals/landig/article/PIIS2589-7500(19)30222-5/fulltext
Background Summary:
Acute infections can cause an individual to have an elevated resting heart rate (RHR) and change their routine daily activities due to the physiological response to the inflammatory insult. Consequently, we aimed to evaluate if population trends of seasonal respiratory infections, such as influenza, could be identified through wearable sensors that collect RHR and sleep data.
Click to expand...
Click to collapse
(The mentioned study here refers to Influenza, and the principle is now being assessed if it works with COVID-19 as well)
In Germany, a "data donation app" supported by the German government was just released: https://corona-datenspende.de/ (currently available in German only, unfortunately).
Question 1: Could somebody verify if this particular app is compatible with Mi Band 4? (It is currently not listet officially, but might work via Google Fit maybe?)
Update: See post #4. I would be glad if somebody else tries that, too.Question 2: Are there other apps available with the same purpose and compatible with Mi Band 4?
(This thread is about specific apps to collect health or fitness data from consumer wearables, no generic apps regarding the pandemic please.)
Notify & fitness added this feature recently. However it most probably doesn't use resting heart rate, but rather average value. For monitoring of trends it should be more or less accurate, but I wish that developer would implement it properly. I will drop him a message..
"Notify & Fitness app to help you check your daily average heart rate. If a higher daily heart rate is found, this means you probably have a fever. When you have a fever, you may also have the COVID-19. Never trust only data showed on the app. You may get wrong alerts depending on how good you track your heart data. If you are not feeling good, please measure fever and call doctor or local authorities."
Explanation from the N&F dev: "estimating resting heart rate is not easy without support of mi band raw data.
This is why I have looked for alternative solution. First of all, if you track workout sessions correctly on notify app, all this data get ignored automatically. Secondly we compare each day according to time, so compare morning with only other morning data etc..*
So, as described on app, if you are doing the same activities each day, and tracking workout session correctly, you should obtain correct result."
Update
Meanwhile I bought a Band 4 and tested it with the "Datenspende" app together with the original Xiaomi app and Google Fit. Result: The app crashes constantly and becomes unusable :crying:.
Thanks @_mysiak_ for your feedback regarding "Notify & Fitness"! The difference here seems to be that the collected data is used for yourself to identify and warn about a potential infection, while "Datenspende" sends the data to a central server with the idea to identify potential local clusters in a certain area.