Been trying to figure this out for a while now. I have been able to fix this with a number of apps, but there are some apps that are just frustrating to deal with.
I'm wondering what exactly can keep an app running in the background, regardless of what efforts your take to disable it?
If I don't use an app much and don't want it running, I normally freeze the app. If it is an app I tend to use a bit more frequently, I take other measures such as an app manager that allows me to be extremely precise as to how and when it should run such as on startup, battery level, configuration change, application change, etc. This is a pain in the A** though and I really don't have the time to do this for every application.
With that said, I'm wondering what other methods, other than freezing and the other mentioned above, I can take to prevent an app from running in the background?
I will give you a perfect example...
There are some third-party apps I have downloaded that I know I will use occasionally. One example is CamScanner. For the life of me, I can't get this app to stop running in the background without extensive efforts mentioned above. No matter what I do, it just pops up again in running applications.
How can I ensure the app will not run in background while not resorting to freezing the app, which will prevent me from quickly accessing it when needed?
Some clarification on this would be greatly appreciated...
Thank you,
--mike
pookieguy said:
Been trying to figure this out for a while now. I have been able to fix this with a number of apps, but there are some apps that are just frustrating to deal with.
I'm wondering what exactly can keep an app running in the background, regardless of what efforts your take to disable it?
If I don't use an app much and don't want it running, I normally freeze the app. If it is an app I tend to use a bit more frequently, I take other measures such as an app manager that allows me to be extremely precise as to how and when it should run such as on startup, battery level, configuration change, application change, etc. This is a pain in the A** though and I really don't have the time to do this for every application.
With that said, I'm wondering what other methods, other than freezing and the other mentioned above, I can take to prevent an app from running in the background?
I will give you a perfect example...
There are some third-party apps I have downloaded that I know I will use occasionally. One example is CamScanner. For the life of me, I can't get this app to stop running in the background without extensive efforts mentioned above. No matter what I do, it just pops up again in running applications.
How can I ensure the app will not run in background while not resorting to freezing the app, which will prevent me from quickly accessing it when needed?
Some clarification on this would be greatly appreciated...
Thank you,
--mike
Click to expand...
Click to collapse
freezing is your only bet. definitely a pain but the built in tasking doesn't apply to all apps,especially facebook. can try alternative apps but if none exist then you still need to freeze. I unfreeze a certain batch of apps when I wake up and freeze them before bed. during the day i go along with what i'm running. i'm tryin to link special batches to say toggles or tasking with tasker to make mornings and bed work faster
sent from tapatalk on my htc rezound
Use something like Gemini App Manager. Those programs likely use triggers to auto-run. Gemini shows you the triggers applications use so you can stop them if you don't want them running whenever they want.
I use AppQuarantine for those issues. you can put widgets on the desk that let you unfreeze and start apps with one click.
sent from the desert with xda app
Thanks guys,
I will try some of these options out.
Was really trying to do this without freezing apps though. I can do it through ROM Toolbox but it is quite tedious, as this awesome app has so many options on how to handle the application. Trying to find shortcuts...
Thanks,
pookieguy said:
Thanks guys,
I will try some of these options out.
Was really trying to do this without freezing apps though. I can do it through ROM Toolbox but it is quite tedious, as this awesome app has so many options on how to handle the application. Trying to find shortcuts...
Thanks,
Click to expand...
Click to collapse
Have you tried Autostarts? There's many scenarios an app takes into account before it'll run. You can disable the app from running in each category so the only time its running is when you open it. Unless of course you don't kill it when you leave the app. Its hard to explain but when you look at the app you'll know what I mean
Sent from my SGH-I997 using Tapatalk
.
Thread moved to Q&A due to it being a question. Would advise you to read forum rules and post in correct section.
Failure to comply with forum rules will result in an infraction and/or ban depending on severity of rule break.
This post is about getting great battery life for the average, every-day user. It is not inclusive or exhaustive, so it will reference other posts. What is talked about is what I did, the user-level stuff, explained in a more user-friendly fashion than some of the more diagnostic-focused posts out there (still invaluable reading, though).
Note: I originally wrote this for the Hyperdrive ROM on GS4 thread, but I've had many requests to break it out into a separate [GUIDE] post and update it here for ease of subscribing and discussing. Also note, that therefore, this should be considered sort of Android 4.2 specific and may not apply to all versions of Android. So, here it is. I'll link the old post to here shortly.
Preface
Okay, I'm writing this because I believe that @sbreen94 @eschelon @iceandfire @Imoseyon @TrevE and @ktoonsez all have done awesome, awesome dev work from which I have benefited. There are SO many other devs, as well. These are some from whom I directly benefit, regularly, daily, or did at one time. If you want a name added to the list, I'll update my post. This post, though, is sort of Hyperdrive specific since @sbreen94 has added a few tweaks that make it SO EASY to address some major offenders of ... sucking the life out of your battery.
Why do I mention this? Because does anyone truly think that a ROM dev or Kernel dev, compiles code, puts it on their device, runs it for days/weeks, validates it with experienced, community testers, and then releases it, all the time thinking, "well, the battery life sucks, but I'm gonna push this out anyways."??? NO! So, then, WHY does every ROM/Kernel thread have post after post, of people saying “Hey, I loaded this ROM and my battery life sucks now.” Do you REALLY think it's the ROM/Kernel?
We also have those that think they have no apps loaded, or “only 3, 4, 5, or whatever number” - so it can't POSSIBLY be an app! If you think that, then do this, Wipe your Dalvic Cache, reboot your phone, and tell me the number of apps it says Android is now optimizing. That is the number of apps you have on your phone, not the number you personally loaded. That means each one of those is a potential culprit for causing battery drain.
BTW – at one time or another, I've probably been guilty of every of the above mindsets. So, I'm not calling YOU out, if YOU are reading this and think that I am. I'm just saying, it's not the ROM, and it's not the Kernel.
Background Reading
The below two threads had everything I needed to know to get started increasing my battery life. I, probably like many reading this, had for a long time followed along, envious of screenshots of people getting those 3, 4, 5+ hours of screen time, and day+ or days of battery. After reading these threads, doing the analysis, and basically just changing some app settings, I can now get the 4-5 hours of screen and full day of battery out of my GS4. Kernel doesn't have much effect, ROM doesn't have much effect, most all of them do what they're designed to do, and do it well. Sweet.
In the next section, Real World Battery Saving, I'll explain what I did, so if you want to skip the background stuff, you can.
These two threads contain basically everything you need to know about improving battery life. They have great details about diagnostics, what's what, etc. What many threads/posts like these sometimes lack, is, the straight-forward answer of “This is what you should do after analyzing x, y, z.” That's what's in the Real World Battery Saving section of this post.
[APP][2.1+][09 Sept. - V1.14] BetterBatteryStats
[GUIDE] Wakelocks Definition and how to prevent them
Read those threads, and do some analysis, and the majority of what I've posted below you'll figure out on your own. If you just wanna jump into fixing things without the above understanding, then just go to the next section. Provided there aren't any seriously misbehaving apps on your phone, you should be able to get great results without becoming a Wakelocks, Alarms, Deep Sleep, etc., expert.
Real World Battery Saving
For those of you that don't want to read too much more about the analysis of apps, etc., to get to better battery life, here's the summary of what's in the section below:
Minimize screen brightness
Disable all Push
Disable all system sounds (Dialing keypad tone, Touch sounds, Screen lock sound, Haptic feedback)
Install Xposed Framework and use:
Greenify Donation (Experimental features)
NLPUnbounce
Greenify any app that you don’t need to notify you of things - Note: If you pay for Greenify Donation and use Xposed, you can still get alerts from any GCM-enabled app (look for the blue GCM icon next to apps in Greenify)
Greenify every Google app (except Voice and Hangouts, both of these may significantly delay or prevent proper message notification, despite being GCM-tagged in Greenify, and they seem to behave okay on their own)
Uninstall GMail (use any other client with IMAP)
Disable all GPS (enable as necessary upon use) Note: I really don't do this anymore. With apps under control with Greenify, I just leave my GPS on and let apps use it when necessary. I have noticed that GPS will stay active during Airplane mode, though, so as not to have my phone dead upon landing, I generally always turn off GPS when in the air.
Disable the autostart of almost everything, at almost any time, on an app-by-app basis. AutoStart Check delivers in spades for this function, at no charge, though, I recommend donating (as I do for all apps here, I have either donated or bought them all, Lux, Greenify, etc.). Note: With Greenify, I no longer worry as much about stopping apps/services from auto-starting. I do still use Xposed plugin BootManager to prevent certain apps from starting, mostly just to increase boot speed (or so I feel like it might). I don't use AutoStart Check at all anymore.
Continuing on with details...
Note: Required app functionality. You don't have to use these if you know another way to do it. But, to accomplish what I recommend, there are 3 key apps you absolutely must have. I'm not going to explain them all in great detail, as there are plenty of other places that go into great depth on all of them. The 3 essential apps that I use to increase battery by more than 50% are:
Lux (Pro - I'll explain why below)
Greenify
Xposed Framework
In general:
You want your phone to sleep when not in use.
You want apps to not be doing anything when you're not using them.
You want your screen to only ever be as bright as it needs to be, no brighter (including, off when you're not looking at it).
Display Brightness
Lux – Get it here Lux Auto Brightness
Thread here: [APP][2.3+] Lux Auto Brightness 1.51
Update: After posting this, and getting a lot of questions/comments that Lux doesn't really rock like I think it does, I checked it out on a phone without using the Pro version. Okay, I agree, the free version really doesn't deliver. It doesn't poll right, and you can't really set your custom lighting scenarios and lock them in correctly without using Lux Pro. Basically, if you want to save tons of battery life without a lot of constant manual intervention, you're going to have to purchase Lux.
Screen uses more battery than anything. You can do all kinds of things to address this, for me, Lux has been a (battery) life saver. It's easy, it reads the ambient light in your environment. Open its dashboard, slide the slider to the brightness that works for you at that lumen level, hold down the link button in the middle, and there you have it, locked in for those conditions. You only have to do this a few times and you now have custom lighting profiles that fit your eyes' needs under all conditions. Note, sometimes, when waking the phone in the sun, you'll have to wait a few second for Lux to activate and bring the screen up bright enough. This means that Lux is behaving extremely well and not constantly running in the background (Wakelocks) sucking up battery.
Applications
For applications, firstly, if you have an app that has Push available, disable it. Nothing keeps your phone from deep sleep like a Push-enabled application. If you can't wait 5/10/15 minutes for updates, then you can't achieve maximum battery life. Sorry, I don't make the rules of Android app-physics, I'm just sharing them with you.
In my mind, I think of applications in categories. I guess, I have 4 now.. I started with 2. Point being, there are different apps that behave differently so you treat them differently with different solutions for extending your battery life.
Category 1 Apps I want running and want notifications from them. When configured properly, they generally do not misbehave and eat my phone's battery
Category 2 Apps that I cannot seem to control, regardless of their settings, but I still want to be able to use, but getting regular or instant updates from them is not that important to me
Category 3 Apps behave without any special settings and without any Greenification. Just load them, run them, use them, don't worry about them. I haven't seen them cause any sort of bad battery drain.
Category 4 Apps are apps you DO think are vital/desirable (to you) but cannot control their battery consumption with mere settings. For those, only the developer can help you, or you have to accept the battery loss that app's notifications bring with it.
Category 1 apps, well-behaved when configured properly, along with the settings I used to make them behave well and still deliver their updates to me.
Corporate E-mail: Built-in e-mail, TW or AOSP. Disable Push for any account, use Priority settings for 15 minute interval on work days. Non-prioirty times set to 1 hour.
Maildroid: For every account, you must do this separately, under Preferences / Advanced – Connection Management, select first account, the rule (usually 1. Default), Connection Management, Wi-Fi: Close connection when I exit mailbox, GPRS, 3G: Close connection when I exit mailbox, Interval to check mail: 10 (or to your liking), Check Mail Periodically. Go back, go back in (confirm settings were kept, I've seen it not keep them and have to do this a few times, per account). Alternatively, select Let device sleep, and it will only check when you wake it up. Go back to Accounts and select your next account, do this again. You must do this for all accounts listed.
Note about all mail client: If you have more than 2 or 3 e-mail accounts, Maildroid and all other IMAP clients I have tried get moved to Category 2. Basically, they start to keep enough Wakelocks that they keep the phone from going into Deep Sleep as much as I'd like. This is a difference of 1-3% per hour at idle, but if you're looking for 4+ hours screen time, then you need to Greenify them and just check e-mail manually.
Viber: Just make sure your Wi-Fi sleep policy is set to device and not constantly on, and Viber seems to behave pretty well as far as messaging apps go, but it's probably going to make the Category 4 list, as well.
WhatsApp: This one appears to work well (better than Viber from a wakeup perspective) and not have any sort of unnecessary battery drain. I generally don't use it any more since I feel they bait-and-switched me from free to fee, but I dethawed it to check it out. If anyone sees problems with it, let me know.
Category 2 Apps. These apps were keeping my phone awake at night with nightmares, and no amount of settings changes seemed to fix the problem altogether. If you have a solution of app settings that would move these to Category 1, please let me know. When I say solution, I mean, you've done the Wakelock and Alarm analysis and they're eliminated or minimized. For these, I Greenify them all. None of these apps' updates are so important to me that I can't just check up on them when I have a moment.
Facebook: I didn't play too much with settings here, but it seems that if FB is running, it's keeping your phone awake. I Greenify it and check it manually. I'd be interested in hearing if someone knows settings that will get it to not wakelock / alarm constantly.
FB Messenger: I love the chat heads and ease of use, but it's a big-time battery offender. I keep it installed and Greenified. If I get messages, I'll see them when I open the FB app, and when I reply, FB Messenger takes over and I use it normally until the conversation is done. At some point, Greenify takes over, and FB Messenger's battery damage is contained.
Google Maps: You can't fix this thing. No amount of settings will stop it from going after your phone. I love its functionality, though, so, unlike many guides that say uninstall it, I say Greenify it.
Google Goggles: A fun one to have around sometimes, but it will also chew up battery. Just Greenify it.
Google Play Store: There are plenty of apps and Android wakeups for the Play Store. I'm not worried about missing an update notification, or whatever else it might be sending my way. Greenifying it seems to have fixed the Google Play Services Alarms issue.
Almost everything else: If it's an app that doesn't need to provide you updates, just Greenify it. Why not? One of the first things I do after loading a new ROM and getting most of the configuration stuff done, is I go into Greenify, and I add every mundane app on my phone, for example: Vonage, Adobe Reader, Airbnb, Angry Birds, APN Manager Pro, Google Authenticator, Barcode Scanner, Citibank, Craigslist, Google Drive, DroidVPN, ES Task Manager, Fast Charge, FasterGPS, Flashlight, GasBuddy, GNotes, GooManager, GPS Status, Hyatt, Lucky Patcher, Office Document Viewer, Office Suite, OpenTable, Opera Classic, PayByPhone, SoundHound, Squeezebox, Street View, etc. My list goes on... You aren't going to lose their functionality, they don't suddenly stop when in use, and you don't have to worry about them ever causing problems you weren't thinking you had to look for.
Category 3 Apps that behave, no special settings, no Greenification
Alarm Clock Xtreme: I don't use the built-in Alarm Clock. I like all the features of Xtreme, it's never failed me, and it doesn't show up in Wakelock/Alarm offenders lists in my analyses.
Google Voice: Of all the Google offenders, this isn't one of them in my experience, and I love its features.
Lux: Nuff said.
WhosCall: A caller-ID type app. I don't love it, but haven't gone looking for something better, that said, it hasn't popped up on my battery draining radar, so that's a plus.
Hangouts: While I don't care for the new Google Talk, it sure doesn't seem to be a battery offender, and I use it to chat regularly.
Category 4 Apps are anything that would have gone into Category 2, but you want them as active as possible.
Line: In Settings, Chats and Voice Calls, I turn off Receive Voice Calls. This made Line tolerable (as in, way better), but it's still a Category 4 until (if ever) its devs reduce its number of wake-up Alarms
Exchange Services: Despite Corporate E-mail being a Category 1 now, Exchange Services is still keeping my phone awake more than I'd like. Nothing I can do here, though, so I live with it.
Viber: As stated, it's not a terrible offender, but it's still on the radar for keeping my phone awake. We'll see what their “any day now” major update brings. (someone remind me to update this post if I haven't post-Viber release)
Have Your Google and Your Battery
The Xposed module NLPUnbounce is awesome. I've given it a nice test, and it seems to perform excellent. NLPUnbounce allows you to use Google services as usual, including Android Device Manager features, like Remote Locate and Remote Wipe, but not do the crazy, crippling and disabling of Google Play Services like many guides have you do. It changes the polling rate of NLP (Network Location Provider) to something VERY reasonable. I haven't modified any of its settings, and it's reduced average idle consumption from ~4-5% to ~2-3%. I tested locating my phone and ringing it, all working.
Automatically Launching Applications
Not so much needed anymore. Just make sure you Greenify. For the "big things", use Xposed BootManager module.
AutoStart Check - Get it here https://play.google.com/store/apps/details?id=ro.rbrtoanna.autostartcheck&hl=en
Fire up AutoStart Check (or any other autostart configuration app), set your view to Group by App, and expand every one of them and look at just how many different places some of these apps are set to start. Your Gallery starts with your Camera? ES File Explorer starts when you mount media or remove bad media? Facebook fires itself up just because you plugged in your phone. Google Goggles sees fit to start with every picture you take - and of course, it will then either drain your battery trying to get a GPS signal while your GPS is off, or drain your battery by getting one – fail. If you use S Health, it starts when your time zone changes – that's important. YouTube, seriously, YouTube – change accounts, mount media, connect power, every boot – you obviously need YouTube to fire up. Yeah.
A note here, read some guides on these before turning off too many system services. For example, don't disable messaging, bad idea, bad things happen. But most of this stuff, turn it off. You aren't killing your ability to use it, you're just making sure it isn't turning on all the time. If you've also Greenified well, after using any of these, they'll hibernate in the background without you having to worry.
Disable all system sounds (Dialing keypad tone, Touch sounds, Screen lock sound, Haptic feedback)
This is explained in some of the other threads, but, if you don't want to do the research, basically, the background services in Android that manage these things keep your phone awake. Turn them all off, battery life goes up.
Media Scanner
@sbreen94 included in the Hyperdrive Tweaks tools a one-button solution to turning it off. If it's drainging your battery, or you just want to make sure it doesn't, go click the button. This thing is better than the Staples button!
I'm sure there's probably a more generic way of stopping/managing Media Scanner. Someone please let me know and I'll update this section!
Battery Save Apps
I used to be madly in love with 2x Battery. Others swear by JuiceDefender. I guess if you don't/won't want to take the time to optimize apps and Greenify, they might be beneficial. You know what I found, though, when I started down this path? Some of the biggest offenders of Wakelocks and keeping my phone from sleeping when it should, are these battery saving apps!!! I now get BETTER battery life WITHOUT 2x Battery!
Short thoughts on this and example concepts of what's going on...
It may sound counterinterintuitive, but it seems most of the apps are so vigilant they keep your phone awake when it could be sleeping. And the vigilance isn't so necessary when you've properly configure things to not need this sort of overactive management of things. I'd love to see 2x Battery properly manage my data connection for me, without Wakelocks, but what's to say that the app trying to sync when the data is off won't now stay awake with new Wakelocks trying to get out to the internet? There's a cascading effect of whatever approach you might choose, so try to think about that, and keep it in mind when you look at your Wakelocks and your Alarms and you do your analysis.
The End
Okay, so I think that's aobut it. I may have forgotten some things, and I know this is a long post. But, this leaves very little excuse for people to blame ROMs/Kernels, while at the same time giving you the straight-forward, real world answer to battery savings 101. Yes, there are apps and details I left out. If anyone thinks of some obvoius ones, just let me know and I'll happily update this post.
You don't have to analyze any statistics or logs to do this. The principles are sound, and you'll see a dramatic improvement in battery if you don't already get a day of usage and 3.5 to 4.5 hours of screen time on your GS4. You just make some of these relatively straight-foward, user-level, common-sense changes.
If these changes don't give you the results you'd like, then do the analysis work in the threads linked above and find out what's the real culprit. Profit, enjoy, be happy. And remember... It's not the ROM.
Thanks for the thread, Bill. Here are a few of my questions/comments:
Regarding Lux, I used it for a few days, but could never seem to get a setting that worked for me. Whether using periodic updating or any of the other modes, the brightness level always seemed to adjust either too frequently or too slowly. Then I started experimenting with night mode and it got even worse. Do you have any suggestions to a quick and simple setup that won't drive me insane?
In terms of greenifying different apps, I always make sure that my SMS app and alarm clock are not greenified, and I don't use any widgets on my homescreen, but what about apps like Better Battery Stats, Boot Manager (for Xposed) and Automagic (flow chart based automation app) that are monitoring events and automating my phone? Will Battery Stats stop recording data is I set it to hibernate? Will Automagic miss a trigger I've set if it's hibernating? I would like to greenify EVERYTHING that I know won't cause any issues, but notifications aren't the only thing happening in the background that I want to allow.
Then, expanding on the autostarts, I mentioned that I use the Xposed module Boot Manager. This doesn't seem able to handle all of the situations that you described, like apps being launched based on SD card state, network state, etc. Am I missing something in this app or will I need to go another route to get all the options you've descibed?
Regarding the SD media scanning, my current ROM is a very debloated lean and mean stock Touchwiz ROM that doesn't have a native way to disable media scanner like the AOSP ROMs I used to run. Is there an app that does ONLY this, as I prefer to use dedicated apps rather than giant monsters which can control tons of things I don't need.
Anyway, I already do a lot of the practices you're advocating here, but I'm always looking for ways to do things in a more efficient or streamlined way. Using Greenify, keeping the stock clock speeds, and making sure that nothing is syncing (I keep backgruond sync disabled, but use an Automagic flow to enable it periodically throughout the day and then turn it back off again), keeps my battery life pretty solid. Add to that Deep Sleep Battery Saver which automatically turns off my connections when the screen is off, but will periodically turn them back based on my preferences, keeps my battery level pretty much steady wheen the phone is idle.
I wonder has anyone else felt having a stand-alone alarm on the Gear Fit would be useful using vibration as a wake-up. I really enjoy using the watch as a wake-up device and I know you can set your phone to a silent alarm so it essentially wakes you up by the vibration. But sometimes my phone battery dies during the night or sometimes I want to set a quick day time alarm when I don't have my phone around. The timer I think only goes up to 99 minutes.
Maybe this is only strange to me but not having a built in alarm on the phone seems an oversight. I had the same issue with the Gear 1 and tried a few aftermarket apps such as Zen alarm but found on the phone they often didn't have the alert until hours after it was meant to.
I know these watches are companion devices to a phone but they do include some apps that make sense to have on the phone such as timer, pedometer etc. Always wonder why not an alarm as well.
Agree 100%
Sent from my GT-N7105 using XDA Free mobile app
the problem is, there are no real apps for gear fit only app connections that are in need of the phone to work.
So what you are suggesting with the standalone alarm won't work if your phone is not connected via bluetooth.
Maybe someday it will be possible to include apps in the firmware but i wouldn't wait for it.(since there isn't much free space)
Best way would be to tell samsung directly in boards or customer support or whatever if they could include a standalone alarm.
Like they listen
Seronez said:
the problem is, there are no real apps for gear fit only app connections that are in need of the phone to work.
So what you are suggesting with the standalone alarm won't work if your phone is not connected via bluetooth.
Maybe someday it will be possible to include apps in the firmware but i wouldn't wait for it.(since there isn't much free space)
Best way would be to tell samsung directly in boards or customer support or whatever if they could include a standalone alarm.
Click to expand...
Click to collapse
Good morning everyone. I also am interested in having the alarm on the Gear Fit, because as the partner says above, if we run out of battery in the phone, or even if the Bluetooth connection is lost no would sound us the alarm, and I see no logical we will put both mobile Vibrate as bracelet at a time.
That said I do not understand because if you can make a calculator application, or one in which the screen turns on and then torch, not to have to create multiple alarms. I'm not saying having a hundred but 2 or 3 alarms at a minimum I think is not much to ask.
I think it's the only thing missing from the bracelet. Anyone know where I can get environment or any program to program applications for Gear? I'm looking and looking to try to create an application and see if we can somehow create if only an alarm.
Regards and forgive the inconvenience.
AGree!!!
adjenkins said:
I wonder has anyone else felt having a stand-alone alarm on the Gear Fit would be useful using vibration as a wake-up. I really enjoy using the watch as a wake-up device and I know you can set your phone to a silent alarm so it essentially wakes you up by the vibration. But sometimes my phone battery dies during the night or sometimes I want to set a quick day time alarm when I don't have my phone around. The timer I think only goes up to 99 minutes.
Maybe this is only strange to me but not having a built in alarm on the phone seems an oversight. I had the same issue with the Gear 1 and tried a few aftermarket apps such as Zen alarm but found on the phone they often didn't have the alert until hours after it was meant to.
I know these watches are companion devices to a phone but they do include some apps that make sense to have on the phone such as timer, pedometer etc. Always wonder why not an alarm as well.
Click to expand...
Click to collapse
There should be a better timer and a better stopwatch!! they only go to 99 and that is pretty anoying. I'm thinking someone should also do one of those interval apps, the gear fit is perfect for it so you don't have to be carrying the galaxy device into the gym (which I hate). And of course a standalone alarm with multiple configurations, I can leave with setting it up in the device itself.
Guys, I have come here just to look for such an application. Any developments yet? It seems our device is half baked and using only a small portion of its potential.
SM-G900F cihazımdan Tapatalk kullanılarak gönderildi
yes. the most app I want is an alarm!!!
This sounds like a no-brainer, but the SDK (as I understand it) really only allows an app to respond to touch input and the phone via BT. There's no access to the native clock. I plan on looking into it, pretty much just to tinker, because I lost my fitbit and BT8010, and this was a much less expensive replacement (used). I've got a class to finish, and a kid to raise, so it might not be timely. Don't expect much.
This little guy really does have potential. It's a crying shame the software development didn't support it. Really, Samsung's pretty software sucks like no other manufacturer I've ever seen. And I'm WinMo-3.0 old.
netyang said:
yes. the most app I want is an alarm!!!
Click to expand...
Click to collapse
me too!
a vibrating alarm for gear fit!
There isnt a need for a stand alone alarm, atm its not possible. The Gear Fit isnt designed to have apps loaded on it, just on the phone & used via bluetooth.
I think an Ideal solution to this would be an Alarm App that can be downloaded as usual to the phone, and accessed on the Gear Fit.
For the Alarm to be 100% silent on the Phone (with no vibration either) but to vibrate on the Gear Fit - the settings for the alarm could be edited either on the phone or via the 'App Connect' feature on the Gear Fit....
I think this would give the solution people are wanting???
pinkbellbird said:
There isnt a need for a stand alone alarm, atm its not possible. The Gear Fit isnt designed to have apps loaded on it, just on the phone & used via bluetooth.
I think an Ideal solution to this would be an Alarm App that can be downloaded as usual to the phone, and accessed on the Gear Fit.
For the Alarm to be 100% silent on the Phone (with no vibration either) but to vibrate on the Gear Fit - the settings for the alarm could be edited either on the phone or via the 'App Connect' feature on the Gear Fit....
I think this would give the solution people are wanting???
Click to expand...
Click to collapse
You can do this with the built in Alarm (via the Clock app) on your phone. Just make sure Alarm is checked under Instant Alerts in the Gear Fit Manager. You can even dismiss or snooze directly from the Gear Fit.
How do you get it to appear in the instant alerts? I only see incoming calls
pinkbellbird said:
There isnt a need for a stand alone alarm, atm its not possible. The Gear Fit isnt designed to have apps loaded on it, just on the phone & used via bluetooth.
I think an Ideal solution to this would be an Alarm App that can be downloaded as usual to the phone, and accessed on the Gear Fit.
For the Alarm to be 100% silent on the Phone (with no vibration either) but to vibrate on the Gear Fit - the settings for the alarm could be edited either on the phone or via the 'App Connect' feature on the Gear Fit....
I think this would give the solution people are wanting???
Click to expand...
Click to collapse
http://sleepgenius.com/ could be great maybe it wakes u up with vibrator
adjenkins said:
I wonder has anyone else felt having a stand-alone alarm on the Gear Fit would be useful using vibration as a wake-up. I really enjoy using the watch as a wake-up device and I know you can set your phone to a silent alarm so it essentially wakes you up by the vibration. But sometimes my phone battery dies during the night or sometimes I want to set a quick day time alarm when I don't have my phone around. The timer I think only goes up to 99 minutes.
Maybe this is only strange to me but not having a built in alarm on the phone seems an oversight. I had the same issue with the Gear 1 and tried a few aftermarket apps such as Zen alarm but found on the phone they often didn't have the alert until hours after it was meant to.
I know these watches are companion devices to a phone but they do include some apps that make sense to have on the phone such as timer, pedometer etc. Always wonder why not an alarm as well.
Click to expand...
Click to collapse
If connected via Bluetooth and Alarm is set on the phone the gear fit will vibrate too easy peasy
Yes please!!!!
Somebody just make it real please!!!!
I may add this support in my app: http://forum.xda-developers.com/gear-fit/themes-apps/openfit-source-gear-fit-application-t3005697 but will not work with Gear Fit Manager
jareddlc said:
I may add this support in my app: http://forum.xda-developers.com/gear-fit/themes-apps/openfit-source-gear-fit-application-t3005697 but will not work with Gear Fit Manager
Click to expand...
Click to collapse
I use your application, I am very happy, I miss just the ability to set alarms on the watch. I hope that this feature will appear in the near future (sorry for my english)
Working Alarm for Gear Fit
Just recently got rid of my FitBit and got a Gear Fit but had the same question as you. I tried the different alarm apps and tried to us the Gear Fit Manager app to make them function.
Lo and behold! I did not have to get an app as the Clock app already loaded with my Samsung S5 works just fine. Just set your alarm on this Clock app, go to your Gear Fit Manager app, then go to Notification. Scroll down to Instant Alerts for Gear: 3 and put a check mark on Alarm. Voila!
Of course, I did a test first and yes, my Gear Fit vibrates with the alarm at the exact time NOT an hour later like the Sleep as Android app.
Hi,
its possible prolong time in countdown app ??? i cant set on 90 min. If it´s possible we can use this app like alarm.
Hello @oasisfeng
Ive been using of greenify since the beggining ive rooted my device and now that MM is out which im also using since it was released on my nexus 5 device i still used greenify
Right now i have to uninstall it for one particular reason. It doesnt sync in notifications anymore.
I do know that "doze" limits notifications but opens background sync up in a short time for every minute or hours of interval. I do know greenify forces apps to go to "app standby" mode or forces apps to defer background process without exiting them on 6.0+ this means that the general "wait time" for push notifications are also deffered.
I do know there is a "wake up service" for greenify that intends to wake up device services again when hibernated from time to time but to be honest i think it is inefficient.
So haveyou tried creating an alarm that cuts the hibernation off for a small second to quickly sync in background process and push notifications from apps such as xda labs or messenger? You can do it by creating an alarm with a code of setandallowwhileidle()
Hope you read this and ill be waiting for your feedback, in the meantime ill be uninstalling greenify also its donate package and wait for further improvements
Cheers!
Instant messaging apps should generally be excluded from Greenify unless it supports GCM "high priority" push on Android 6.0+. This is the recommended solution mentioned in the app description and FAQ.
Do you mean the Greenify did sync in notifications in the past but not now? Can you give me a specific version number of Greenify that worked for you?
If I understand correctly, you want to wake-up apps periodically. It has been discussed actively in the early time. That derived a large set of functionality requirements, such as interval settings, settings per app, black-out duration, conditional wake-up, and etc. Even the worse, the longer interval, the less timely notification while the shorter interval, the more battery consumption. It is hard to balance, compared to the real right solution - GCM push. In summary, this idea introduced too much complexity.
As always, if you want to achieve that purpose, I'd suggest using Tasker together with the "wake-up" plug-in function provided by Greenify. Why do you think it is inefficient?
BTW, the solution of setAndAllowWhileIdle() is not the answer you may expect. If you are a developer and have read the documents, you should know this API is strictly limited and it also defeats the purpose of Greenify.
oasisfeng said:
Instant messaging apps should generally be excluded from Greenify unless it supports GCM "high priority" push on Android 6.0+. This is the recommended solution mentioned in the app description and FAQ.
Do you mean the Greenify did sync in notifications in the past but not now? Can you give me a specific version number of Greenify that worked for you?
If I understand correctly, you want to wake-up apps periodically. It has been discussed actively in the early time. That derived a large set of functionality requirements, such as interval settings, settings per app, black-out duration, conditional wake-up, and etc. Even the worse, the longer interval, the less timely notification while the shorter interval, the more battery consumption. It is hard to balance, compared to the real right solution - GCM push. In summary, this idea introduced too much complexity.
As always, if you want to achieve that purpose, I'd suggest using Tasker together with the "wake-up" plug-in function provided by Greenify. Why do you think it is inefficient?
BTW, the solution of setAndAllowWhileIdle() is not the answer you may expect. If you are a developer and have read the documents, you should know this API is strictly limited and it also defeats the purpose of Greenify.
Click to expand...
Click to collapse
I havent tried testing whileidle() to be honest i just read it multiple times on google sources and the likes.
For your suggestion on tasker i would not recommend it. There has been an endless discussion on tasker if it was battery friendly or not and i know for a fact that it is not. The problem with tasker is its constant background monitoring which depends on your "trigger" and "event" so yep i wouldnt use tasker to automate things anytime soon.
And yes. Waking up apps periodically is the thing that i would like to propose though it might contradict M's doze mode. So overall just now im with you that its not a good solution for messaging apps.
I dont remember it was years ago way back when im using kitkat and a non-famous brand phone locally made here in our country, but as far as i remember messenger really still doesnt tickle a notification update.
So bottomline right now theres no solution for messaging apps other than leaving it as it is right? The problem is that those messaging apps have the highest background drain so i guess i had to adjust myself using messenger lol
phantom146 said:
I havent tried testing whileidle() to be honest i just read it multiple times on google sources and the likes.
For your suggestion on tasker i would not recommend it. There has been an endless discussion on tasker if it was battery friendly or not and i know for a fact that it is not. The problem with tasker is its constant background monitoring which depends on your "trigger" and "event" so yep i wouldnt use tasker to automate things anytime soon.
And yes. Waking up apps periodically is the thing that i would like to propose though it might contradict M's doze mode. So overall just now im with you that its not a good solution for messaging apps.
I dont remember it was years ago way back when im using kitkat and a non-famous brand phone locally made here in our country, but as far as i remember messenger really still doesnt tickle a notification update.
So bottomline right now theres no solution for messaging apps other than leaving it as it is right? The problem is that those messaging apps have the highest background drain so i guess i had to adjust myself using messenger lol
Click to expand...
Click to collapse
IM app without GCM push is such a pain, since it usually tries its best to improve the real-time notifications, at the cost of power consumption. In my experience, even a 5 minutes interval wake-up is far from enough for a IM app, but already increases the power consumption a bit.
oasisfeng said:
IM app without GCM push is such a pain, since it usually tries its best to improve the real-time notifications, at the cost of power consumption. In my experience, even a 5 minutes interval wake-up is far from enough for a IM app, but already increases the power consumption a bit.
Click to expand...
Click to collapse
Agreed and again facebook and messenger is to blame for the poorly written codes and the messy services they all have.
Right now my issue is solved and im glad for such a quick and concise response. Ill be waiting for the future beta releases and in the meantime if you need my help for an upcoming feature on M count me in, and ill also throw down "possible suggestions" for you and maybe give you some codes for it
Cheers bud